6.9.6 Technical vulnerability management
Technical vulnerability management and restriction on software installation apply as the base guidance requires, read as protecting the personal data that an unpatched vulnerability would expose.
3
artefacts
0
held by a system
2
at each review
hard
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
none for this control
periodic reviewEvidence produced at each review
- Evidence of coverage over systems holding personal data · Vulnerability scanner / patch tooling
- Remediation records and exception approvals · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Vulnerability management process with timescales · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Remediation prioritised on technical severity with no weighting for personal data exposure
- Coverage gaps on systems that the asset inventory misses
- Exceptions granted indefinitely without review
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 sheet6.9.5 Control of operational software · 6.9.7 Information systems audit considerations