10.4.2.1 Frequency defined by TRA
The frequency of periodic reviews for all other system components is defined in the entity's targeted risk analysis.
5
artefacts
0
held by a system
2
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
- Annual TRA review records · Document repository
- Sample reviews aligned to cadence · Document repository
governing documentDocuments that govern the control
- TRA document with risk inputs and chosen cadence · Document repository
- Approval by senior leadership · Document repository
- Mapping of cadence to system criticality · 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
- No TRA
- Cadence chosen without analysis
- TRA not updated
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 sheet10.4.2 Periodic review of other system component logs · 10.4.3 Exceptions and anomalies addressed