Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/Accruent/owasp-zap-historic
Store ZAP reports historically and compare current ZAP results against the most recent for changes in alerts.
https://github.com/Accruent/owasp-zap-historic
owasp owasp-zap owaspzaphistoric reporting reporting-tool reports zap
Last synced: 21 days ago
JSON representation
Store ZAP reports historically and compare current ZAP results against the most recent for changes in alerts.
- Host: GitHub
- URL: https://github.com/Accruent/owasp-zap-historic
- Owner: Accruent
- License: gpl-3.0
- Created: 2020-05-18T18:38:29.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2024-11-20T15:45:50.000Z (22 days ago)
- Last Synced: 2024-11-20T16:39:58.873Z (22 days ago)
- Topics: owasp, owasp-zap, owaspzaphistoric, reporting, reporting-tool, reports, zap
- Language: HTML
- Size: 245 KB
- Stars: 12
- Watchers: 5
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-hacking-lists - Accruent/owasp-zap-historic - Store ZAP reports historically and compare current ZAP results against the most recent for changes in alerts. (HTML)
README
# owaspzap-historic
OWASP-ZAP-Historic (OZH) is a free, custom html report which provides historical ZAP execution results by storing execution results info in MySQL database and generating html reports from the database using Flask. It borrows heavily from the work done by adiralashiva8 for https://github.com/adiralashiva8/robotframework-historic
> MYSQL + Flask + OWASP Zed Attack Proxy
---
[](https://badge.fury.io/py/owasp-zap-historic)
[](https://github.com/Accruent/owasp-zap-historic/actions/workflows/run-tests.yml)
[](https://pepy.tech/project/owasp-zap-historic)
[](http://hits.dwyl.com/neiljhowell/Accruent/owasp-zap-historic)
[](https://bettercodehub.com/)
[](https://lgtm.com/projects/g/Accruent/owasp-zap-historic/alerts/)
[](https://lgtm.com/projects/g/Accruent/owasp-zap-historic/context:javascript)
[](https://lgtm.com/projects/g/Accruent/owasp-zap-historic/context:python)
[](https://coveralls.io/github/Accruent/owasp-zap-historic)
## UPDATE Release 0.2.0
This release incorporates False Positives from the newer ZAP reports into the application. If you are an existing user
user of owaspzap-historic, you will need to make the following changes to your MySQL database:
- The following script will need to be ran on your TB_PROJECT table:
> ALTER TABLE owaspzaphistoric.TB_PROJECT ADD COLUMN Recent_False INT
> NULL DEFAULT 0 AFTER Recent_Informational;
- The following script will need to be ran on any project's TB_EXECUTION table:
> ALTER TABLE [project_name].TB_EXECUTION ADD COLUMN False_Alerts INT NULL DEFAULT 0
> AFTER Informational_Alerts;
## OZH Overview
> 
---
## Features
- Store ZAP results historically
- Visualize ZAP results over time, by app version, by environment, etc.
- Search historical ZAP records by name / environment / scan type / execution id / etc
- Export results (Excel, CSV, Print, Copy)
---
## Why OZH?
- It is open source
- Made by QA
---
## How OZH Works:
- ZAP job runs in __Jenkins__ and produces report.html artifact and published HTML (stored in MySQL as URL_Link for access between OZH and published ZAP report)
- __Parser__ stores results for one or more applications in local / remote hosted __MySQL__ database and creates a delta report for __Jenkins__ to email out to recipient list.
- Generate report tables / reports using __Flask__
> 
## Requirements
- Python 3.9
- MySQL DB
## Installation
- __Step 1:__ Download and Install MySQL Server - [guide](https://bit.ly/2GrUUZ9)
- __Step 2:__ Install owasp-zap-historic
> Case 1: Using pip install
```
pip install owasp-zap-historic
```
> Case 2: Using setup.py (root)
```
python setup.py install
```
> Case 3: Using git (latest changes)
```
pip install git+https://github.com/Accruent/owasp-zap-historic.git
```
- __Step 3:__ Create *owaspzaphistoric* default user with permissions - [guide](https://bit.ly/2PIOTfI)
- __Step 4:__ Create *TB_PROJECT* table
- CREATE DATABASE `owaspzaphistoric` /*!40100 DEFAULT CHARACTER SET latin1 */;
- USE owaspzaphistoric;
- CREATE TABLE `TB_PROJECT` (
`Project_Id` int(11) NOT NULL AUTO_INCREMENT,
`Project_Name` text,
`Project_Desc` text,
`Project_Image` text,
`Environment` text,
`Scan_Type` text,
`Created_Date` datetime DEFAULT NULL,
`Last_Updated` datetime DEFAULT NULL,
`Total_Executions` int(11) DEFAULT NULL,
`Recent_High` int(11) DEFAULT NULL,
`Recent_Medium` int(11) DEFAULT NULL,
`Recent_Low` int(11) DEFAULT NULL,
`Recent_Informational` int(11) DEFAULT NULL,
`Recent_False` int(11) DEFAULT NULL,
`Version` varchar(50) DEFAULT 'Not Captured',
PRIMARY KEY (`Project_Id`)
) ENGINE=InnoDB AUTO_INCREMENT=14 DEFAULT CHARSET=latin1;
- __Step 5:__ Create *TB_USERS* table
- CREATE DATABASE `accounts` /*!40100 DEFAULT CHARACTER SET latin1 */;
- USE accounts;
- CREATE TABLE `TB_USERS` (
`id` int(6) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(255) NOT NULL,
`email` varchar(255) NOT NULL,
`password` varchar(255) NOT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=latin1;
- __Step 5:__ Install robotframework-historic-parser
```
pip install owasp-zap-historic-parser
```
> _Note:_ All actions above are one time activities
### Help / Know More
To know more on available commands refer to cmd help
```
owaspzaphistoric --help
owaspzaphistoricparser --help
```
---
## How to use OZH
- __Step 1:__ Create user in OZH
> You may have to bypass the security for the first time you create a user. Any user created has the authority to create another user beyond that.
- Remove / comment out lines 57 & 97 ({% if session['name'] %} and {% endif %}
- (from CMD) python setup.py install
- (from CMD) owaspzaphistoric
- (localhost:5000/register) enter a valid username and password
- Lines 57 & 97 can be uncommented / replaced now
- __Step 2:__ Create project in OZH
- Login to OZH
- Click the *New Project* button
- Enter a valid name for the project (it must meet __MySQL__ db naming standards
- __Step 3:__ Push data to OZH using owasp_zap_historic.py and owasp_zap_historic.bat
- These were built with processing from Jenkins in mind. At Accruent, the OWASP ZAP job can be ran as a standalone job or as a child job. In Jenkins, the parameters that OZH needs are defaulted for the standalone job (environment, version)
- The parameters that owaspzaphistoricparser expects from the CMD / bat file are:
- s --> mysql hosted machine ip address (default: localhost)
- t --> mysql port (default: 3306)
- u --> mysql user name (default: superuser)
- p --> mysql password (default: passw0rd)
- n --> project name in owasp zap historic
- e --> environment name (default: Not Provided)
- i --> type of scan (active, passive, etc) (default: Not Provided)
- l --> URL for published ZAP report (default: Not Provided)
- v --> version of application tested by ZAP (default: Not Provided)
- f --> filepath & report.html produced by ZAP
- In order to not store the production username/password in the repo, localhost entries are referenced in the repo. These can be hidden in the .bat file.
- Example call from Jenkins:
```
email_body = bat returnStdout: true, script: """@cmd /c c://Jenkins/Scripts/owasp_zap_historic.bat "${html_file}" ${tag} ${targetURL.toUpperCase()} ${scan_type.toUpperCase()} "${url_link}" "${version}" """
```
- This returns the delta email body back to the email_body variable in Jenkins, which then emails the report to a recipient list.
- Here is the basic process for owasp_zap_historic.py:
- The ZAP file is scraped for alerts
- The data is pushed to the *TB_EXECUTION* and *TB_ALERTS* tables in MySQL in the project's db
- The row for the project in *owaspzaphistoric.TB_PROJECT* is updated with recent data to display on the landing page
- It looks for a previous row in *TB_EXECUTION* to compare results to and produces a delta report
- More information at [owasp-zap-historic-parser](https://github.com/Accruent/owasp-zap-historic-parser)
- __Step 4:__ View results on the OZH app!
- Click the *View* button for any project to view its dashboard
- From here, you can click the *Historic* tab to view all executions for a project
- From there, you can dive into individual executions to see the ZAP alerts, or click the link to view the published ZAP report, or even delete executions
- Clicking the *Alerts* tab will show you all alerts for the project, which can be sorted or filtered as needed to help you determine how your application is performing over time.