ISO/IEC 27001:2022·Annex A A.8.10·high·Component: Technological controls

What this control requires

Information stored in information systems, devices or in any other storage media shall be deleted when no longer required.
— ISO/IEC 27001:2022, Annex A A.8.10

In plain English

Information stored in information systems, devices or in any other storage media shall be deleted when no longer required. In practice, this means you can prove you information information-level controls on a defined cadence.

Why it matters

ISO 27001 certification depends on showing each Annex A control is either implemented or explicitly justified for exclusion in the Statement of Applicability (SoA). Certification bodies sample controls during surveillance audits, and a missing SoA entry — or implementation that doesn't match the SoA wording — is a finding.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

An ISO 27001 lead auditor looks for: (1) an SoA entry covering the control with justification, (2) a documented procedure or policy implementing it, (3) records that prove the procedure runs (logs, tickets, training records) and (4) management-review evidence that effectiveness is monitored.

Within Technological controls, the assessor will trace your implementation back to the catalogue reference (Annex A A.8.10) and look for objective evidence on the latest two assessment cycles.

How to implement

Endpoint Protection

MDM. Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token.

EDR. Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h.

Operational checklist

  • Information. Document the trigger, the owner and the cadence.
  • Protection. Document the trigger, the owner and the cadence.
  • Security. Document the trigger, the owner and the cadence.
  • Storage. Document the trigger, the owner and the cadence.
  • Scope: information, media, security, deletion.

Evidence to collect

  • Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.
  • User Device Scan. MDM compliance state per user device (Intune / Jamf / Workspace ONE).

Storage lifecycle policies and endpoint wipe telemetry show data is deleted from servers and user devices when retired.

Common pitfalls

  • Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

Related controls in ISO/IEC 27001:2022

References

Topics: endpoint securityendpoint protection