RV.3.3 Review SDLC to Prevent Recurrence
Review the software development process and update it as appropriate to prevent the root causes of vulnerabilities from recurring in future releases.
1
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
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
none for this control
governing documentDocuments that govern the control
- SDLC process updates to prevent recurrence · Policy repository / GRC workspace
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
- Root causes not fed back into the SDLC
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.3.2 Identify and Fix Similar Vulnerabilities · RV.3.4 Document Lessons Learned