ISO 27001 A.8.24: encryption, explained for startups
What A.8.24 asks of a small company, and what an auditor samples.

Use encryption and related techniques to protect data, backed by proper key management. Apply the right level of cryptography for the sensitivity involved.
Why it exists: to protect data with encryption when it is stored and when it moves.
A.8.24 Use of cryptography
Data is encrypted when stored and when it moves, and keys are managed safely. What proves it: encryption on stored data and connections, and keys kept in a key management service.
A certification auditor samples encryption settings and key management. A file that usually does the job: database and storage encryption settings, a scan of your domain's encrypted connections, and key rotation settings.
How to put it in place
Each step leaves a record, and the record is what the auditor samples rather than the step itself. Inside Polara, the control card for A.8.24 walks you through it in this order.
- Turn on encryption for every database, storage bucket and disk.
- Allow only encrypted connections.
- Keep keys in a managed key service with rotation on.
The free ISO 27001 readiness assessment asks 3 questions that evidence it:
- Is data encrypted at rest?
- Is data encrypted in transit?
- Do you have a key management practice?
Policies, connectors and the SOC 2 overlap
In the ISO 27001 policy pack, the Cryptography and Key Management Policy covers A.8.24. An auditor reads the policy for the rule, then samples the records to see the rule was followed.
Connected systems that pull evidence for it:
- Amazon Web Services, S3 bucket encryption: server-side encryption at rest settings on each S3 bucket.
- Amazon Web Services, RDS instance encryption: storage encryption at rest for each RDS database.
- Amazon Web Services, KMS keys: customer-managed encryption keys per region.
- Google Cloud, Storage buckets: cloud Storage buckets with their default encryption at rest.
- Microsoft Entra ID, Intune managed devices: devices managed in Intune, with their encryption and compliance state.
The same evidence counts toward SOC 2. The Trust Services criteria that cover this ground: CC6.1, logical access and CC6.7, data in transit.
Technological controls
A.8.24 is one of the 34 technological controls in Annex A. The controls built into your systems: access, devices, malware, vulnerabilities, backups, logging, networks, encryption and secure development. Exports and settings screenshots prove most of them.
Nearby controls in the same theme:
- A.8.21, network services
- A.8.22, network segregation
- A.8.23, web filtering
- A.8.25, secure development
- A.8.26, application security needs
- A.8.27, secure architecture
Before it: A.8.23, web filtering. After it: A.8.25, secure development. Every control, by theme, is on the Annex A controls page.
Questions
What does ISO 27001 A.8.24 require?
What evidence does an auditor want for A.8.24?
Get ready for ISO 27001 certification.
The readiness assessment is free, with no payment and no card. ISO 27001 is part of Constellation, at $10,800 a year: everything in Orbit plus the management system, the policies, the evidence and the management review for ISO 27001, and your SOC 2 Type 2 audit is included in every contract year. You contract the certification body directly.
The internal audit is priced separately: Polara arranges it with an independent internal auditor from our partner network who works in the platform, and quotes it for your company.
Take the free assessmentPolara Labs is not a certification body. Certification audits are performed by independent accredited certification bodies.