Content

Methodology

SAST

For Static Application Security Testing (SAST), we have implemented SonarCloud within our CI/CD pipeline. Our integration via GitHub Actions ensures continuous inspection of code quality and security vulnerabilities, automating the review process for every commit to the repository.

DAST

In our approach to Dynamic Application Security Testing (DAST), we have chosen to utilize OWASP ZAP, a widely recognized open-source web application security scanner. OWASP ZAP is specifically designed for testing web applications and offers a variety of features and tools to identify potential security vulnerabilities.

Introduction to OWASP ZAP

OWASP ZAP (Zed Attack Proxy) is part of the OWASP (Open Web Application Security Project) tools, known for their reliability and effectiveness in the field of web security. It is designed to automatically find security vulnerabilities in web applications while they are running, making it a suitable choice for DAST.

Utilization of OWASP ZAP in Our Testing

For our testing purposes, we adhere to the following procedure:

1. Use of Default Policy:

   • For our DAST process, we use the default scan policy of OWASP ZAP. This policy covers a wide range of typical vulnerabilities found in web applications, ensuring our scanning process is thorough and effective. For further details about our scanning approach, please refer to the "SAST/DAST Requirements" article, which provides more comprehensive information.

2. Dedicated Repository for Testing:

   • We have established a separate repository, openimis-dynamic-application-security-testing, specifically for conducting Dynamic Application Security Testing. This repository is central to our DAST process.

   • The application build process occurs in the openimis-dist_dkr repository. Here, we pull the latest version of the application, configure the necessary environment (including setting up the .env file), and deploy the application using Docker Compose.

   • This approach allows us to maintain a clear separation between the application building and security testing processes, ensuring a structured and focused DAST workflow.

3. Performing the Analysis:

   • Once the application is running in its dockerized environment, OWASP ZAP performs an automated security analysis on it.

   • The target for the analysis is the running instance of the application, typically accessed at http://localhost:80.

   • This setup ensures that the security analysis is performed in an environment that closely mirrors the production setup, providing accurate and relevant security insights.

Conclusion

By integrating OWASP ZAP into our DAST methodology, we aim to proactively identify and mitigate security vulnerabilities in the openIMIS application. This approach aligns with industry best practices for web application security and contributes to the robustness and reliability of our application.

Result Summary

SAST

The results summary for each module, as analyzed by SonarCloud, is accessible at the openIMIS organization level. Detailed insights into the code quality and security postures of the respective modules can be reviewed using the following link: SonarCloud openIMIS Projects.

DAST

The Dynamic Application Security Testing (DAST) conducted on the openIMIS application using OWASP ZAP has yielded significant insights into the security posture of the application. Below is a summary of the results from the tests performed.

Summary of Alerts

The DAST identified 9 security alerts in total: three medium, three low, and three informational risks, with no high-risk vulnerabilities or false positives detected.

Alerts

Conclusion

The overall security posture of the application is quite robust, as evidenced by the absence of high-risk vulnerabilities in the DAST findings. The issues that were detected fall within the medium and low-risk categories, which, while important, do not indicate critical security flaws. These results suggest that with targeted remediation of the identified issues, the application's security can be further strengthened.

Remediation

SAST

Remediation efforts for identified issues in SAST have been partially addressed by adhering to the OWASP Top 10 compliance report for openIMIS, which can be found here. Furthermore, we have set up an agreement that requires us to resolve any concerns raised by SonarCloud as part of the ongoing development process, assuring continual improvement in code quality and security.

DAST

While the security assessment has returned favorable results, indicating a sound security framework, there are areas identified for improvement. Addressing the issues outlined in the DAST findings will refine the application’s defenses and enhance its resilience to potential threats. The remediation steps will be guided by solutions proposed by the OWASP ZAP report, ensuring that the enhancements are in line with recognized security practices.

Report

SAST

For the SAST analysis, there is no single overarching report; instead, multiple reports exist for every analyzed module. These reports can be accessed and reviewed on the SonarCloud platform, offering a granular view of each module's code quality and security analysis. The reports are available at the following link: SonarCloud openIMIS Projects.

DAST

OWASP ZAP generates a comprehensive report detailing the analysis performed on the application. This report provides an in-depth review of each identified issue, complete with evidence, possible repercussions, and recommended remediation strategies. For full visibility into the security assessment, the complete OWASP ZAP report will be attached to this document, enabling a thorough review and follow-up action planning.