Provide Public documentation for DAST CWE Checks
Problem to solve
The Browser Based DAST scanner is in the process of implementing the vulnerability checks described in the dast-cwe-checks project, and over time these checks will be used to replace those that are implemented by ZAP and used in the DAST scanner.
Because both dast-cwe-checks and browser based DAST scanner are private projects, there's no way to describe the new vulnerability checks to DAST users.
Proposal
Create a public directory of vulnerability checks implemented by the Browser Based DAST scanner so DAST users can easily check details. The directory could look like ZAPs vulnerability check directory https://www.zaproxy.org/docs/alerts/
Intended users
Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
- Parker (Product Manager)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Sam (Security Analyst)
- Rachel (Release Manager)
- Alex (Security Operations Engineer)
- Simone (Software Engineer in Test)
/cc @rdickenson @idawson
Implementation plan
-
Create vulnerability check documentation in GitLab. !72354 (merged) -
Update existing vulnerability check YAML definitions. https://gitlab.com/gitlab-org/security-products/dast-cwe-checks/-/merge_requests/35 -
Update Browser-Based Scanner with new YAML definition. https://gitlab.com/gitlab-org/security-products/analyzers/browserker/-/merge_requests/361 -
Update DAST with new version of DAST Browser Based Scanner gitlab-org/security-products/dast!521 (merged) [ ] Automate the generation of the documentation.-
Document the generation process. https://gitlab.com/gitlab-org/security-products/dast-cwe-checks/-/merge_requests/36 [ ] Update documentation generator to create all docs, not just passive ones.