11.3.1.1 Address non-high vulnerabilities per TRA
All other applicable vulnerabilities (not classified as high-risk or critical) are managed via the entity's targeted risk analysis.
5
artefacts
1
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Sample tickets for medium and low findings · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Annual TRA review · Document repository
governing documentDocuments that govern the control
- TRA defining handling of lower-severity vulnerabilities · Policy repository / GRC workspace
- Classification scheme document · Policy repository / GRC workspace
- Remediation SLA tracking · Vendor register / contract repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Ticketing / ITSM on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- No TRA
- Lower-severity findings ignored
- SLAs not tracked
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 Internal vulnerability scans quarterly · 11.3.1.2 Authenticated internal scans