9.2: Cryptographic measures, protocols, and key management requirements

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

The policy and procedures referred to in point 9.1 shall establish:

  1. in accordance with the relevant entities’ classification of assets, the type, strength and quality of the cryptographic measures required to protect the relevant entities’ assets, including data at rest and data in transit;
  2. based on point (a), the protocols or families of protocols to be adopted, as well as cryptographic algorithms, cipher strength, cryptographic solutions and usage practices to be approved and required for use in the relevant entities, following, where appropriate, a cryptographic agility approach;
  3. the relevant entities’ approach to key management, including, where appropriate, methods for the following:
    • generating different keys for cryptographic systems and applications;
    • issuing and obtaining public key certificates;
    • distributing keys to intended entities, including how to activate keys when received;
    • storing keys, including how authorised users obtain access to keys;
    • changing or updating keys, including rules on when and how to change keys;
    • dealing with compromised keys;
    • revoking keys including how to withdraw or deactivate keys;
    • recovering lost or corrupted keys;
    • backing up or archiving keys;
    • destroying keys;
    • logging and auditing of key management-related activities;
    • setting activation and deactivation dates for keys ensuring that the keys can only be used for the specified period of time according to the organization's rules on key management.

    This requirement is part of the framework:  
    NIS2 Implementing Regulation

    Other requirements of the framework

    No items found.
    50519
    9.2: Cryptographic measures, protocols, and key management requirements
    Best practices
    How to implement:
    9.2: Cryptographic measures, protocols, and key management requirements
    This policy on
    9.2: Cryptographic measures, protocols, and key management requirements
    provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

    The policy and procedures referred to in point 9.1 shall establish:

    1. in accordance with the relevant entities’ classification of assets, the type, strength and quality of the cryptographic measures required to protect the relevant entities’ assets, including data at rest and data in transit;
    2. based on point (a), the protocols or families of protocols to be adopted, as well as cryptographic algorithms, cipher strength, cryptographic solutions and usage practices to be approved and required for use in the relevant entities, following, where appropriate, a cryptographic agility approach;
    3. the relevant entities’ approach to key management, including, where appropriate, methods for the following:
      • generating different keys for cryptographic systems and applications;
      • issuing and obtaining public key certificates;
      • distributing keys to intended entities, including how to activate keys when received;
      • storing keys, including how authorised users obtain access to keys;
      • changing or updating keys, including rules on when and how to change keys;
      • dealing with compromised keys;
      • revoking keys including how to withdraw or deactivate keys;
      • recovering lost or corrupted keys;
      • backing up or archiving keys;
      • destroying keys;
      • logging and auditing of key management-related activities;
      • setting activation and deactivation dates for keys ensuring that the keys can only be used for the specified period of time according to the organization's rules on key management.

      Read below what concrete actions you can take to improve this ->
      Frameworks that include requirements for this topic:
      No items found.

      How to improve security around this topic

      In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

      Here's a list of tasks that help you improve your information and cyber security related to
      9.2: Cryptographic measures, protocols, and key management requirements
      Task name
      Priority
      Task completes
      Complete these tasks to increase your compliance in this policy.
      Critical
      No other tasks found.

      How to comply with this requirement

      In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

      Here's a list of tasks that help you comply with the requirement
      9.2: Cryptographic measures, protocols, and key management requirements
      of the framework  
      NIS2 Implementing Regulation
      Task name
      Priority
      Task completes
      Complete these tasks to increase your compliance in this policy.
      Critical
      Encryption key inventory and management system
      Critical
      High
      Normal
      Low
      Regularly auditing encryption and encryption key management systems
      Critical
      High
      Normal
      Low
      5
      requirements
      Technical cyber security
      Encryption

      Regularly auditing encryption and encryption key management systems

      This task helps you comply with the following requirements

      Revoking encryption keys
      Critical
      High
      Normal
      Low
      3
      requirements
      Technical cyber security
      Encryption

      Revoking encryption keys

      This task helps you comply with the following requirements

      Destruction of encryption keys
      Critical
      High
      Normal
      Low
      3
      requirements
      Technical cyber security
      Encryption

      Destruction of encryption keys

      This task helps you comply with the following requirements

      Encryption key archival
      Critical
      High
      Normal
      Low
      3
      requirements
      Technical cyber security
      Encryption

      Encryption key archival

      This task helps you comply with the following requirements

      Encryption key recovery
      Critical
      High
      Normal
      Low
      Considering encryption and cryptographic key management in risk management procedures
      Critical
      High
      Normal
      Low
      4
      requirements
      Technical cyber security
      Encryption

      Considering encryption and cryptographic key management in risk management procedures

      This task helps you comply with the following requirements

      The ISMS component hierachy

      When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

      Framework

      Sets the overall compliance standard or regulation your organization needs to follow.

      Requirements

      Break down the framework into specific obligations that must be met.

      Tasks

      Concrete actions and activities your team carries out to satisfy each requirement.

      Policies

      Documented rules and practices that are created and maintained as a result of completing tasks.

      Never duplicate effort. Do it once - improve compliance across frameworks.

      Reach multi-framework compliance in the simplest possible way
      Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
      Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
      Do it once - we automatically apply it to all current and future frameworks.