11.3.1.2 Authenticated internal scans
Internal vulnerability scans are performed via authenticated scanning, with credentials, where supported.
5
artefacts
2
held by a system
0
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
- Scanner credential vault configuration · Vulnerability scanner / patch tooling
- Authenticated scan reports and credential validation · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Coverage list of authenticated vs unauthenticated assets · Policy repository / GRC workspace
- Procedure for credential rotation · Policy repository / GRC workspace
- Exception list with compensating controls · 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
- Unauthenticated scans only
- Credentials hardcoded in scanner
- Coverage gaps
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.3.1.1 Address non-high vulnerabilities per TRA · 11.3.1.3 Internal scans after significant changes