ID.RA-08 Processes for receiving, analyzing, and responding to vulnerability disclosures are established
Processes for receiving, analyzing, and responding to vulnerability disclosures are established.
5
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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
- Risk response effectiveness review minutes · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Control effectiveness testing reports · Document repository
- Key risk indicator trending with thresholds · Document repository
- Independent validation of high risk responses · Document repository
- Closure tracking when responses fail · Document repository
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
- Control testing infrequent
- KRIs flat with no investigation
- Effectiveness reviews narrative only
- Independent validation absent
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 sheetID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked · ID.RA-09 The authenticity and integrity of hardware and software are assessed prior to acquisition and use