ISO/IEC 27001
The international standard for an information security management system, applied to your cloud.
Updated
ISO/IEC 27001 certifies a management system rather than a snapshot of settings. You define the scope, assess risks, select controls from Annex A, record the selection in a Statement of Applicability, and show an accredited certification body that the system runs: internal audits, management reviews, and surveillance audits every year between recertifications.
The 2022 edition reorganised Annex A into 93 controls across four themes: organisational, people, physical and technological. Several technological controls speak directly to cloud infrastructure, and one organisational control, A.5.23, is specifically about the secure use of cloud services.
Official text: ISO/IEC 27001:2022 at ISO.
Who needs it
Companies selling internationally or into regulated sectors, where ISO 27001 is the attestation procurement teams recognise. It is frequently a contractual requirement in Europe, and in finance, healthcare and the public sector.
From Annex A to your accounts
A certification auditor checks that each applicable control is implemented and effective. For the technological controls that means configuration evidence: which identities have privileged access, how authentication is enforced, whether logging and monitoring cover the estate, how networks are segregated and how cryptography is applied. Translating the control text into concrete settings in AWS, Google Cloud or Azure is where most audit preparation time goes.
Keeping the certificate
Certification is not a one-off. Surveillance audits look for evidence that controls kept operating and that nonconformities were handled. Scheduled reviews with a record of findings and fixes give you that evidence without a separate exercise.
What ISO 27001 asks of your cloud
The control areas that map onto infrastructure configuration in AWS, Google Cloud and Azure.
A.5.15 – A.5.18 · Access control and identities
Access rights follow a policy, are provisioned and revoked deliberately, and authentication information such as keys and secrets is managed over its lifecycle.
A.5.23 · Cloud services
Information security requirements for acquiring, using and leaving cloud services, including who is responsible for which controls.
A.8.2 – A.8.5 · Privileged access and authentication
Privileged rights are restricted and reviewed, information access is limited, and strong authentication such as MFA is enforced.
A.8.9 · Configuration management
New in the 2022 edition: configurations of hardware, software, services and networks are established, documented, monitored and reviewed.
A.8.15 – A.8.16 · Logging and monitoring
Events are logged, protected and analysed; networks, systems and applications are monitored for anomalous behaviour.
A.8.20 – A.8.24 · Networks and cryptography
Networks are secured and segregated, network services are controlled, and cryptography is used according to a policy, including encryption at rest and in transit.
How AKRIBOS checks ISO 27001
Mapped to your resources
Every ISO 27001 control is evaluated against the actual accounts, roles, networks and storage in your estate, with the setting behind each result.
Findings come with the fix
A failing control is shown with the exact change as CLI commands or Terraform. You review and approve; nothing is applied on its own.
Evidence over time
Scheduled reviews and a full audit trail give you a dated record of each control for the whole audit period, not just the day of the audit.
Common issues under ISO 27001
Misconfigurations that fail ISO 27001 controls, with the control reference for each.
Storage bucket open to the internet
CriticalObject storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.A.5.15 Access control, A.8.3 Information access restriction, A.5.23 Cloud services.
Read moreRoot or owner account without MFA
CriticalThe most privileged identity in the account protected by a password alone.A.8.2 Privileged access rights, A.8.5 Secure authentication.
Read moreDatabase reachable from the internet
CriticalA managed database with a public address and a firewall that lets the world in.A.8.3 Information access restriction, A.8.20 Networks security.
Read moreSnapshots or machine images shared publicly
CriticalDisk snapshots, database snapshots or machine images that anyone with a cloud account can copy.A.8.3 Information access restriction, A.5.14 Information transfer.
Read moreOver-permissive IAM policies
HighIdentities, often service accounts, that can do anything in the account because a wildcard or a basic role was easier than a scoped policy.A.5.15 Access control, A.5.18 Access rights, A.8.2 Privileged access rights.
Read moreSSH or RDP open to 0.0.0.0/0
HighManagement ports reachable from any address on the internet.A.8.20 Networks security, A.8.21 Security of network services.
Read moreAudit logging incomplete
HighGaps in the record of who did what: missing regions, missing data-access events, or logs that can be altered.A.8.15 Logging, A.8.16 Monitoring activities.
Read moreLong-lived or unused credentials
HighAccess keys, service account keys and client secrets that never rotate and are no longer needed.A.5.17 Authentication information, A.5.18 Access rights.
Read moreInstance metadata without session tokens
HighCompute instances that answer metadata requests, including their temporary credentials, to any process that can reach the local metadata address.A.8.9 Configuration management, A.8.8 Management of technical vulnerabilities.
Read moreTrust policies open to any account
HighRoles or bindings that let identities outside your organisation assume access, often for a vendor integration that was set up too generously.A.5.15 Access control, A.5.19 Information security in supplier relationships, A.8.2 Privileged access rights.
Read moreData at rest without the encryption you intended
MediumVolumes, snapshots or databases created without encryption, or without the customer-managed keys your policy requires.A.8.24 Use of cryptography.
Read moreTransport encryption not enforced
MediumEndpoints that still accept plaintext or outdated TLS, even though an encrypted path exists.A.8.24 Use of cryptography, A.8.21 Security of network services.
Read moreNetwork flow logs off
MediumNo record of which addresses talked to which, so traffic to and from a compromised host cannot be reconstructed.A.8.15 Logging, A.8.16 Monitoring activities.
Read moreDefault network with permissive rules
MediumWorkloads running in the cloud-created default network, which ships with rules nobody would write deliberately.A.8.20 Networks security, A.8.22 Segregation of networks.
Read moreISO 27001 questions
Is ISO 27001 about technology or process?
Both. The management system in clauses 4 to 10 is process; Annex A supplies the controls, a third of which are technological. Auditors expect configuration evidence for those.
What changed in the 2022 edition?
Annex A went from 114 controls in 14 domains to 93 controls in 4 themes, with 11 new controls. The ones that matter most for cloud are A.5.23 on cloud services, A.8.9 on configuration management and A.8.16 on monitoring. Existing certificates had to transition by 31 October 2025.
Can AKRIBOS produce our Statement of Applicability?
No. The SoA is a management decision about which controls apply to your scope. What AKRIBOS gives you is the evidence for the technological controls you include, mapped control by control to your cloud accounts.
Do we need ISO 27001 if we already have SOC 2?
They overlap heavily on the technical side, and the same cloud evidence supports both. ISO 27001 adds a certified management system and is better recognised outside the United States, which is why many companies hold both.
Other frameworks
CIS Benchmarks
The baseline configuration standard for AWS, Google Cloud and Azure.
Read moreSOC 2
Evidence that your cloud controls work, not just that they exist.
Read moreDORA
The EU Digital Operational Resilience Act, applied to the cloud behind your financial services.
Read moreNIS2
EU-wide cyber risk-management obligations for essential and important entities.
Read morePCI DSS v4
Requirements for every environment that stores, processes or transmits cardholder data.
Read moreNIST CSF 2.0
The US framework of outcomes: Govern, Identify, Protect, Detect, Respond, Recover.
Read moreBSI C5
Germany's cloud computing compliance criteria catalogue.
Read moreDNB Good Practice Information Security
What De Nederlandsche Bank expects of the financial institutions it supervises.
Read moreAttackers don't wait for your next audit. Neither does AKRIBOS.
Connect AWS, Google Cloud or Azure and get your first review today.
