PV-7 Conduct regular red team operations
Conduct red team operations and penetration testing on a regular basis to simulate real-world attacks and reveal risks that vulnerability scanning does not surface.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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
- Test reports with findings and severity · Document repository
governing documentDocuments that govern the control
- Test scope, rules of engagement and provider notification where required · Policy repository / GRC workspace
- Remediation tracking for findings through to closure · Document repository
- Cadence showing tests repeated on a defined interval · Document repository
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
- a single test performed at launch and never repeated
- scope narrowed until the test cannot find anything
- findings reported but not tracked to closure
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 sheet