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.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), PV-7. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Test scope, rules of engagement and provider notification where required · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
- Test reports with findings and severity · Document repository
governing documentDocuments that govern the control
- Remediation tracking for findings through to closure · Document repository
- Cadence showing tests repeated on a defined interval · Document repository
First move
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