Active

Key Revocation & Destruction

The organization shall revoke and destroy cryptographic keys when they are no longer needed or have been compromised. Revocation shall include deactivation of keys, notification of affected parties, and documentation of revocation. Destruction shall include secure destruction using approved methods and documentation of destruction.

Requirement ID
CRY-004-R007
Parent Control
CRY-004
Domain Code
CRY

Requirement Details & Guidance

CRY-004-R007 · CRY-004
Why This Requirement Exists

Ensures compromised, expired, or retired keys can no longer be used and are securely destroyed when retention requirements end.

Implementation Guidance

Define revocation and destruction triggers, authorization, evidence, dependency checks, and secure destruction procedures. Consider retained data and recovery requirements before destruction.

Practical Application & Audit Readiness

CRY-004-R007 · Field Guidance

Business Examples

    Common Audit Findings

      Common Mistakes

        Best Practices & Ownership

        CRY-004 · Recommended Approach

        Recommended Practices

          Typical Owner

          Cross-Mapped Regulatory Frameworks

          Harmonized Control Mappings
          FRAMEWORK CODE FRAMEWORK NAME & DETAILS FAMILY / CATEGORY VERSION ACTION
          IRDAI IRDAI Information & Cyber Security Guidelines IRDAI information and cyber-security requirements... Clause: §2.12-3.2 – Key Management
          India
          Guideline
          		 vLatest View →
          RBI-CSF RBI Cyber Security Framework / Master Directions RBI cyber-security requirements and directions set... Clause: 8) User Access Control / Management – 8.1 Secure access with protection of data at rest and in transit
          India
          Regulation
          		 vLatest View →
          SEBI-CSCRF SEBI Cyber Security & Cyber Resilience Framework SEBI’s Cybersecurity and Cyber Resilience Framewor... Clause: 3.3 PR.DS: Data Security
          India
          Regulation
          		 vLatest View →
          DORA Digital Operational Resilience Act The EU Digital Operational Resilience Act establis... Clause: Article 9(4)(d) – Strong authentication, cryptographic keys and encryption Article 9(2) – ICT security policies, procedures, protocols and tools for resilience and data security
          EU
          Regulation
          		 vCurrent View →
          ISO27002 ISO/IEC 27002 ISO/IEC 27002 is a guidance standard containing a... Clause: 8.24 – Use of cryptography
          ISO
          Standard
          		 v2022 View →
          NIS2 NIS2 Directive The NIS2 Directive establishes EU-wide cybersecuri... Clause: Article 21(2)(h) – Policies and procedures regarding cryptography and, where appropriate, encryption
          EU
          Directive
          		 vCurrent View →
          PCI-DSS PCI DSS PCI DSS is an industry security standard maintaine... Clause: 3.7.1 – Key-management policies and procedures are implemented to include generation of strong policies and procedures for keys used for; 3.7.2 – Key-management policies and procedures are; 3.7.3 – Key-management policies and procedures are; 3.7.4 – Key management policies and procedures are; 3.7.5 – Key management policies procedures are; 3.7.6 – Where manual cleartext cryptographic key-; 3.7.7 – Key management policies and procedures are; 3.7.8 – Key management policies and procedures are
          PCI
          Standard
          		 v4 View →
          NIST-CSF NIST Cybersecurity Framework (CSF) The NIST Cybersecurity Framework provides high-lev... Clause: PR.DS – Data Security | PR.DS-01 – The confidentiality, integrity, and availability of data-at-rest are protected
          NIST
          Framework
          		 v2 View →
          NIST80053 NIST SP 800-53 NIST SP 800-53 Rev. 5 presents control families, i... Clause: 3.18 – SYSTEM AND COMMUNICATIONS PROTECTION; SC-12 – CRYPTOGRAPHIC KEY ESTABLISHMENT AND MANAGEMENT
          NIST
          Control Catalog
          		 vRev. 5 View →
          NPCI-ISR NPCI Information Security Requirements NPCI information-security requirements define cont... Clause: Security Measures / Controls; Data Security
          India
          Standard
          		 vLatest View →
          SOC2 SOC 2 Trust Services Criteria SOC 2 is an independent examination and reporting... Clause: CC6.1 – Logical and Physical Access Controls – The entity implements logical access security software, infrastructure, and architectures over protected information assets to protect them from security events to meet the entity's objectives. CC6.5 – Logical and Physical Access Controls – The entity discontinues logical and physical protections over physical assets only after the ability to read or recover data and software from those assets has been diminished and is no longer required to meet the entity’s objectives.
          AICPA
          Audit Framework
          		 vLatest View →

          Parent Domain Context

          Governance Domain Baseline
          Domain Name:
          Cryptography & Key Management (CRY)
          Purpose:
          To manage the use of encryption and cryptographic keys to protect data.
          Scope:
          Enterprise
          View

          Parent Control Context

          Control Baseline
          Control Name:
          Cryptographic Key Management (CRY-004)
          Summary:
          Establishes comprehensive cryptographic key management including generation, distribution, secure storage, rotation, backup, recovery, revocation, and destruction throughout the key lifecycle.
          Business Description:
          Establish and maintain processes for generating, distributing, storing, protecting, rotating, archiving, recovering, revoking, and destroying cryptographic keys throughout their lifecycle.
          View