NOTICE: You are accessing jubeen.sh as guest. All content governed by author's build specifications. Proceed with good faith.

you@jubeen.sh:~/projects/security$ ls -la --group-directories-first#series

-rw-r--r--  jubeen  staff  3 min  May 31, 2020  medjay-defending-offensively-capstone-project.md

you@jubeen.sh:~/projects/security$ cat -b medjay-defending-offensively-capstone-project.md

Content

• Abstract
• Tools and Technologies
• Milestones
• Test Planning & Exec
• Fuzz Testing
• Interactive Testing
• Penetration Testing
• Why the name?

Project Medjay

Abstract

This project focusses on securing OpenMRS — a Java-based open source project to develop software to support the delivery of health care in developing countries. The project is divided into four parts, including, but not limited to - static & dynamic analysis, fuzzing, dependency checking, test coverage, and penetration testing. The project’s main goal was to identify vulnerabilities in OpenMRS system using different techniques and implement fixes.

Tools & Technologies

Several popular proprietary and open source tools such as Fortify, Defensics, Seeker, ZAP, Snyk, and Coverity were used to identify vulnerabilities in the OpenMRS system, adhering to the OWASP Application Security Verification Standard 4.0

Milestones

Milestone 1 - Security Test Planning & Execution

• Familiarized myself with black box testing, and writing repeatable test cases for verification of vulnerabilities
• Carried out static analysis with Fortify and Coverity helped understand common security mistakes, and helped develop a sense, and a need for secure coding practice

• Mapped vulnerabilities found, to OWASP ASVS 4.0

• Maintained an average of finding one vulnerability per hour, for 24 hours worth of testing, combining both manual testing, and static analysis

Milestone 2 - Fuzz Testing

• Performed Fuzz testing on OpenMRS using ZAP and Defensics to find vulnerabilities of the following types, including but not limited to, Injection, Buffer Overflow, XSS, and SQL Injection.
• Also created a report for finding vulnerable dependencies using OWASP Dependency Check, RedHat Victims, Snyk, and Github’s Checker and compared the tools to find the best suit for the requirements
• Maintained an average of finding one vulnerability per three hour, for 24 hours worth of testing, combining both ZAP, and Defensics analysis.

Milestone 3 - Interactive Testing & Test Coverage

• Performed Interactive Security Testing using seeker to and vulnerabilities in OpenMRS
• Identified several logging related security vulnerabilities in OpenMRS

• Maintained an average of finding two vulnerabilities per hour, for ten hours worth of testing

• Calculated test coverage, as a result of all the vulnerabilities found through the three milestones.

Milestone 3 - Penetration Testing

• Carried out Penetration Testing in OpenMRS
• Identified several (15) additional security vulnerabilities in OpenMRS in three hours worth of penetration testing.
• Proposed and Implemented security fixes for few vulnerabilities found in the application

Why Medjay?

While deciding the name, I wanted to focus on security and highlight its significance in ancient times. Medjay was a demonym used in various ways throughout ancient Egyptian history. The most prominent use was to describe an elite paramilitary police force during the initial times and later just policing in general. Since this project is about protecting assets and learning to defend against malicious activities, the term Medjay was found to be most fitting.