Internationalstandard

ISO/IEC 27001:2022

ISO 27001 certification is increasingly a procurement prerequisite. Without it, organisations face exclusion from enterprise supply chain shortlists and heightened scrutiny from insurers and regulators.

Mapped to Microsoft controls
Effective DateOctober 2022 (revised)
Enforcement BodyAccredited certification bodies (UKAS in the UK)
Penalty FrameworkISO 27001 is a voluntary standard, there are no direct regulatory fines for non-compliance. However, the consequences of failing to achieve or maintain certification include exclusion from procurement processes (particularly UK Government G-Cloud and NHS DSPT), contractual breach with clients who mandate certification, increased insurance premiums, and reputational damage following a breach where the absence of certification is cited as evidence of negligence. Certification bodies conduct surveillance audits annually and full re-certification every three years. Non-conformities must be remediated within defined timescales or certification is suspended.

ISO/IEC 27001:2022 is the globally recognised standard for establishing and maintaining a formal Information Security Management System (ISMS). The 2022 revision consolidated requirements into 93 controls across four critical themes: Organisational, People, Physical, and Technological.

For enterprises pursuing certification, the standard demands more than "paper compliance"—it requires provable, deterministic operational controls. This is where legacy implementations fail: firms generate documentation but lack the cryptographic or telemetry-based evidence that controls are continuously enforced in the cloud.

We build and operate the technical enforcement layer required to achieve and maintain ISO 27001 certification. Instead of merely writing policies, we translate Annex A requirements directly into Microsoft-native configurations—ensuring your tenant generates the exact cryptographic and telemetry evidence auditors demand.

Why This Matters Now

ISO 27001:2022 certification is no longer optional for enterprise procurement. Without it, your firm is automatically excluded from Tier-1 supply chain shortlists in financial services, healthcare, defence, and government. The standard forces rigorous risk-based discipline—organisations that implement it under our architecture experience significantly fewer security incidents and demonstrate immediate recovery. For M365-dependent enterprises, the 2022 revision's advanced controls on cloud services (A.5.23), threat intelligence (A.5.7), and data masking (A.8.11) demand complex, deterministic technical enforcement that require specialist configuration and operational oversight.

Scope & Applicability

ISO 27001 applies to any organisation, regardless of size, sector, or geography, that wishes to demonstrate a systematic approach to information security. The standard is scope-defined, the organisation determines which business units, systems, and data are within scope. However, auditors scrutinise scope exclusions carefully. For M365 environments, the scope typically encompasses the Entra ID tenant, all M365 workloads (Exchange, SharePoint, Teams, OneDrive), Azure subscriptions, Intune-managed devices, and the people and processes that manage them. Organisations processing data for regulated clients are increasingly expected to include their entire cloud infrastructure within scope.

Core Obligations

01
Annex A.5.15–5.18

Access Control

Implement identity verification, role-based access, privileged access management, and access review procedures. Access must be granted on a need-to-know basis and reviewed at defined intervals.

02
Annex A.8.24

Cryptography

Define and implement a policy on the use of cryptographic controls, including key management procedures. Encryption must protect data at rest and in transit.

03
Annex A.8.1–8.12

Operations Security

Maintain documented operating procedures, implement change management, ensure capacity management, and separate development from production environments.

04
Annex A.5.24–5.28

Incident Management

Establish incident response procedures, define reporting responsibilities, collect forensic evidence, and conduct post-incident reviews.

05
Annex A.5.19–5.23

Supplier Relationships

Assess and monitor information security risks in the supply chain. Maintain security requirements in supplier agreements and audit compliance.

06
Annex A.8.15–8.16

Logging and Monitoring

Produce, retain, and protect audit logs. Monitor systems for anomalous activity and ensure logs are available for forensic investigation.

Microsoft 365 Control Mapping

How each obligation maps to enforceable Microsoft 365 controls and the evidence they produce.

Obligation

A.5.15 - Access Control

M365 Control

Entra ID Conditional Access policies enforcing MFA, device compliance, and sign-in risk evaluation. Named locations restrict access by geography.

Evidence

Conditional Access policy exports, sign-in logs filtered by policy evaluation, monthly access review completion reports.

Obligation

A.5.18 - Privileged Access Rights

M365 Control

Entra ID Privileged Identity Management (PIM) with time-bound role activation, justification requirements, and peer approval for critical roles.

Evidence

PIM activation logs, role assignment reports, standing privilege audit (target: zero permanent Global Admins).

Obligation

A.8.24 - Use of Cryptography

M365 Control

BitLocker device encryption enforced via Intune compliance policy. TLS 1.2+ enforced on all M365 endpoints. Purview Message Encryption for sensitive email.

Evidence

Intune encryption compliance report, BitLocker recovery key rotation logs, TLS configuration audit.

Obligation

A.5.24 - Incident Management

M365 Control

Microsoft Sentinel SIEM with rigorous incident classification from Defender XDR alerts. Playbooks for common scenarios (compromised account, data exfiltration).

Evidence

Forensic incident timeline exports, detailed response logs, thorough post-incident review documentation.

Obligation

A.8.15 - Logging

M365 Control

Unified Audit Log retention at 10 years (E5). Activity logs shipped to Sentinel workspace. Log integrity protected by immutable storage.

Evidence

Audit log retention configuration export, Sentinel workspace retention policy, log query results for sample periods.

Obligation

A.8.12 - Data Classification

M365 Control

Purview Sensitivity Labels (Confidential, Restricted, Internal, Public) with automatic labelling policies based on content inspection.

Evidence

Label usage analytics, auto-labelling policy match reports, DLP incident summary.

Implementation Timeline

October 2005
Original ISO 27001:2005 published
September 2013
ISO 27001:2013 revision published
October 2022
ISO 27001:2022 published with restructured Annex A (93 controls in 4 themes)
October 2025
Transition deadline - all certifications must reference the 2022 revision
Ongoing
Annual surveillance audits and triennial re-certification cycles

Related Frameworks

Ready to get ISO 27001-ready?

Start with a fixed-scope sprint. We assess your Microsoft 365 controls against ISO 27001 requirements, close gaps, and produce audit-ready evidence.