MA-3 Maintenance tools
Requires the maintenance tools used on the system to be approved, controlled and monitored in use, and requires previously approved tools to be reviewed at an organization-defined frequency so the approved set stays curr
4
artefacts
1
held by a system
2
at each review
moderate
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Monitoring records of tool use during maintenance activity · SIEM / log platform
periodic reviewEvidence produced at each review
- Control evidence such as restricted issue, checkout records or managed installation · Document repository
- Review record for previously approved tools at the defined frequency · Document repository
governing documentDocuments that govern the control
- Register of approved maintenance tools including diagnostic and remote support software · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (SIEM / log platform); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Engineers bring personal utilities and portable media that were never approved
- Approved list created once and never reviewed as tooling changed
- Tool use unmonitored, so a maintenance tool becomes an unlogged administrative channel
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 sheet