MA.L2-3.7.1 Perform Maintenance
Carry out maintenance on organizational systems, so the scheduled and corrective upkeep those systems require is actually performed and recorded.
3
artefacts
1
held by a system
1
at each review
moderate
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
- Completed maintenance records showing work performed and by whom · Document repository
periodic reviewEvidence produced at each review
- Evidence maintenance covers both routine and corrective work · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Maintenance schedule covering in scope systems · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Maintenance performed but never recorded
- Only corrective repair occurs with no scheduled maintenance
- Systems in scope for CUI omitted from the maintenance regime
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 sheetIR.L2-3.6.3 Incident Response Testing · MA.L2-3.7.2 System Maintenance Control