MA-2 Controlled maintenance
Requires maintenance, repair and replacement to be scheduled, documented and reviewed against vendor and organizational requirements, all maintenance approved and monitored whether local or remote, removal of components
5
artefacts
0
held by a system
4
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
- Approval records for off site removal of systems or components · Document repository
- Sanitisation records for equipment removed for maintenance or repair · Document repository
- Verification records confirming controls were checked before return to service · Document repository
- Defined maintenance record fields and evidence they are captured · Document repository
governing documentDocuments that govern the control
- Maintenance schedule and completed maintenance records per component · 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
- Failed drives returned to the vendor under warranty without sanitisation or destruction
- Vendor performed maintenance not recorded because it was arranged directly by operations
- No verification that security controls still function after maintenance
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 sheetMA-1 Policy and procedures for maintenance · MA-3 Maintenance tools