OPS-22 Testing and Documentation of known Vulnerabilities
Check production system components automatically for known vulnerabilities at least once a month under the vulnerability handling rules, assess severity against defined criteria and initiate remediation or mitigation wit
4
artefacts
2
held by a system
1
at each review
easy
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
- Authenticated scan schedule together with the most recent coverage report · Vulnerability scanner / patch tooling
- Reconciliation between scanned targets and the configuration management database · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Patch deployment record for a sampled critical finding · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Finding list showing severity ratings and the assigned remediation due dates · Policy repository / GRC workspace
First move
Automate the pull from your Vulnerability scanner / patch tooling. Scan schedule, findings and remediation age straight from the scanner; patch compliance from the patch console.
Common gaps auditors find
- Unauthenticated scans returning far fewer findings than the estate actually holds
- Coverage omitting container images, short lived hosts and appliances
- Monthly scans run but findings never assigned an owner or a due date
- Hosts discovered by the scanner that appear nowhere in the asset inventory
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 sheetOPS-21 Involvement of Cloud Customers in the Event of Incidents · OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening