A.7 Physical controls

A.7.13 Equipment maintenance

Not mandatory by default – decided in your SoA

What it means in plain language

Maintain equipment correctly so it stays available and secure.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Equipment maintenance can weaken security when technicians gain unsupervised access, remote support tools remain active, or devices are repaired without first removing sensitive data. The Equipment Maintenance Procedure should define who authorizes service, how equipment is isolated, and what checks happen before and after maintenance. It should also distinguish routine preventive servicing from corrective repair so records show when data protection, access control, and asset status were considered together.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Maintenance visits are recorded only as vendor appointments, with no escort, identity verification, or boundary control for server rooms or equipment storage areas.
  • Devices are sent for repair without evidence of data removal, encryption status review, or decision on whether the media should remain in the unit.
  • Firmware updates or component swaps occur without post-maintenance verification, leaving configuration drift, disabled protections, or missing serial-number updates unnoticed.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define an end-to-end maintenance workflow owned by IT operations or facilities, depending on asset type. Include authorization, vendor identity checks, escort rules, work area restrictions, and a requirement to isolate or label the asset before service begins. High-risk or privileged devices should receive tighter supervision and documented handover.
  • Use maintenance tickets, service logs, and asset records to capture serial number, location, reason for service, and expected return. Before external repair, confirm whether data must be removed, whether spare units are needed, and whether media encryption or wipe steps are required to avoid unnecessary exposure.
  • After maintenance, perform a return-to-service checklist: verify boot state, patch or firmware version, physical seals, ports, and any changed settings. Where the repair introduces new risk, record compensating measures, such as temporary restricted use, heightened monitoring, or a follow-up configuration review.
  • Include vendor work, internal servicing, and emergency fixes in the same control process so bypasses remain visible. Escalate repeated failures such as missing tickets, unescorted access, or undocumented repairs through corrective action, and review them during management review for trend-based improvement.

What an auditor will ask to see

  • Approved maintenance ticket showing asset ID, vendor name, escort, start and finish time, and work performed.
  • Pre-maintenance checklist confirming isolation, backups or data removal decision, and device condition before service.
  • Post-maintenance verification sheet showing function test, configuration check, seal inspection, and return-to-use approval.
  • Vendor service report or invoice cross-referenced to the asset register and maintenance log.

Baseline documents in the kit

These free kit documents help you document or evidence A.7.13. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.7.8 — Equipment siting and protection and A.8.9 — Configuration management. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.