5.1.1: Cryptography management

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

Objective: When using cryptographic procedures, it is important to consider risks in the field of availability (lost key material) as well as risks due to incorrectly applied procedures in the fields of integrity and confidentiality (poor algorithms/protocols or insufficient key strengths).

Requirements (must): All cryptographic procedures used (e.g. encryption, signature, and hash algorithms, protocols) provide the security required by the respective application field according to the recognized industry standard,
- to the extent legally feasible.

Requirements (should): Preparation of technical rules containing requirements for encryption in order to protect information according to its classification.
A concept for the application of cryptography is defined and implemented. The following aspects are considered:
- Cryptographic procedures,
- Key strengths,
- Procedures for the complete lifecycle of cryptographic keys, including generation, storage, archiving, retrieval, distribution, deactivation, renewal, and deletion.
An emergency process for restoring key material is established.

This requirement is part of the framework:  
TISAX: Information security

Other requirements of the framework

28747
5.1.1: Cryptography management
Best practices
How to implement:
5.1.1: Cryptography management

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

Objective: When using cryptographic procedures, it is important to consider risks in the field of availability (lost key material) as well as risks due to incorrectly applied procedures in the fields of integrity and confidentiality (poor algorithms/protocols or insufficient key strengths).

Requirements (must): All cryptographic procedures used (e.g. encryption, signature, and hash algorithms, protocols) provide the security required by the respective application field according to the recognized industry standard,
- to the extent legally feasible.

Requirements (should): Preparation of technical rules containing requirements for encryption in order to protect information according to its classification.
A concept for the application of cryptography is defined and implemented. The following aspects are considered:
- Cryptographic procedures,
- Key strengths,
- Procedures for the complete lifecycle of cryptographic keys, including generation, storage, archiving, retrieval, distribution, deactivation, renewal, and deletion.
An emergency process for restoring key material is established.

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
5.1.1: Cryptography management
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
5.1.1: Cryptography management
of the framework  
TISAX: Information security
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Verifying achieved protection level from used cryptographic procedures
Critical
High
Normal
Low
2
requirements
Technical cyber security
Encryption

Verifying achieved protection level from used cryptographic procedures

This task helps you comply with the following requirements

Defining technical rules for encryption of information
Critical
High
Normal
Low
Ensuring sovereignty of encryption keys
Critical
High
Normal
Low
2
requirements
Technical cyber security
Encryption

Ensuring sovereignty of encryption keys

This task helps you comply with the following requirements

Revision of encryption methods and assessment of adequacy
Critical
High
Normal
Low

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.