11.3.1 Internal vulnerability scans quarterly
Internal vulnerability scans are performed at least once every three months, with high-risk and critical vulnerabilities resolved per the entity's risk ranking, and re-scans confirm resolution.
5
artefacts
2
held by a system
1
at each review
moderate
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
- Remediation tickets with closure · Vulnerability scanner / patch tooling
- Re-scan reports confirming fix · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Quarterly scan reports for past 12 months · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Risk ranking documentation · Policy repository / GRC workspace
- Coverage matrix of scanned assets · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Coverage incomplete
- Critical findings open
- No re-scan
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 sheet11.2.2 Authorized wireless AP inventory · 11.3.1.1 Address non-high vulnerabilities per TRA