10.4.2 Periodic review of other system component logs
Logs of all other system components (those not specified in 10.4.1) are reviewed periodically.
5
artefacts
1
held by a system
3
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
- Findings remediation tickets · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Review schedule for non-critical systems · Document repository
- Sample of completed reviews · Document repository
- Sign-off records by reviewer · Document repository
governing documentDocuments that govern the control
- Inventory of systems in scope · Policy repository / GRC workspace
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
- Reviews not performed
- Scope unclear
- No remediation
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.1.1 Automated mechanisms for log review · 10.4.2.1 Frequency defined by TRA