RV.1.2 Review and Analyze Code for Vulnerabilities
Review, analyze, and/or test the software's code to identify or confirm the presence of previously undetected vulnerabilities.
1
artefacts
0
held by a system
1
at each review
hard
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Code review/test results identifying vulnerabilities · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
none for this control
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- No proactive vulnerability discovery
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetRV.1.1 Identify and Confirm Vulnerabilities on an Ongoing Basis · RV.1.3 Vulnerability Disclosure Policy