A.8 Technological controls

A.8.24 Use of cryptography

Not mandatory by default – decided in your SoA

What it means in plain language

Define and apply rules for using cryptography, including key management.

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

Cryptography can protect information only while the algorithms, implementations and keys remain suitable for the intended purpose. Encrypting a database does little against a user who also has unrestricted access to its decryption keys. A practical cryptographic policy therefore connects information protection needs to key custody, lifecycle management, recovery and the operational responsibilities of both internal teams and service providers.

Common auditor findings to check for

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

  • Encrypted information and the keys needed to decrypt it are accessible to the same broad group, undermining the intended separation of responsibilities.
  • Certificates or keys expire unexpectedly because no owner maintains an inventory, renewal process or tested response for loss and compromise.
  • A policy names approved encryption methods but omits backups, application secrets or supplier-managed keys, leaving significant information flows outside its operational scope.

How you can implement it

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

  • Identify where cryptography is needed for confidentiality, integrity or authenticity across storage, transfer and authentication. Record applicable obligations and system constraints, and choose approved approaches using current specialist guidance rather than copying fixed algorithm settings into a policy indefinitely.
  • Define key and certificate ownership, access and lifecycle activities. Cover creation, distribution, storage, use, renewal, revocation and destruction, with appropriate separation of duties. Prefer managed key custody where suitable, but verify the provider’s responsibilities and the organisation’s remaining configuration obligations.
  • Plan for loss, compromise and service disruption. Test authorised recovery of required information without making keys broadly accessible, and document how compromised credentials or certificates are replaced. Ensure backup and recovery arrangements preserve the ability to decrypt information for its legitimate retention period.
  • Review implementations and inventories after technology or risk changes. Check expiry alerts, excessive key permissions, deprecated protocols and untracked exceptions. Retain evidence linking policy decisions to deployed settings, and assign remediation owners when observed configurations no longer meet the approved protection requirements.

What an auditor will ask to see

  • A cryptography policy and system inventory explaining protection purposes, approved approaches, accountable owners and any exceptions or supplier responsibilities affecting key custody.
  • Key-management permissions, certificate-renewal records and configuration samples demonstrating that approved lifecycle controls are implemented rather than merely described in an encryption policy.
  • Controlled recovery or compromise-response tests showing that authorised teams can restore required access or revoke affected material while preserving confidentiality, traceability and appropriate separation of duties.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.5.14 — Information transfer and A.8.5 — Secure authentication. Keep the ownership and evidence consistent across these activities.

NIS2 and ISO/IEC 27001: reuse controls and check legal gaps 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.