EvidenceSheet

7.13 Equipment maintenance

Requires equipment to be maintained correctly, so that information stays available, intact and confidential.

5
artefacts
1
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

  • Evidence of checks after maintenance, confirming security configuration was not altered · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • Maintenance records for the period, showing what was done, by whom and when · Document repository
  • Evidence of protection where equipment is sent off site for repair, including removal or sanitisation of storage media · Data governance / DLP tooling

governing documentDocuments that govern the control

  • The maintenance schedule per equipment type, aligned to supplier recommendation and to criticality · Vendor register / contract repository
  • Controls over maintenance personnel, including authorisation, supervision and escorting where they access secure areas · Document repository

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management 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

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

7.12 Cabling security · 7.14 Secure disposal or re-use of equipment