Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Objective: To check the authorization for both physical access and electronic access, means of identification such as keys, visual IDs, other physical access devices as well as cryptographic tokens are often used. The security features are only reliable if the use of such identification means is handled adequately.
Requirements (must): The requirements for the handling of identification means over the entire lifecycle are determined and fulfilled. The following aspects are considered:
- Creation, handover, return and destruction,
- Validity periods,
- Traceability,
- Handling of loss.
Requirements (should): Identification means can be produced under controlled conditions only.
Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Objective: To check the authorization for both physical access and electronic access, means of identification such as keys, visual IDs, other physical access devices as well as cryptographic tokens are often used. The security features are only reliable if the use of such identification means is handled adequately.
Requirements (must): The requirements for the handling of identification means over the entire lifecycle are determined and fulfilled. The following aspects are considered:
- Creation, handover, return and destruction,
- Validity periods,
- Traceability,
- Handling of loss.
Requirements (should): Identification means can be produced under controlled conditions only.
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.
In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.
When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.
Sets the overall compliance standard or regulation your organization needs to follow.
Break down the framework into specific obligations that must be met.
Concrete actions and activities your team carries out to satisfy each requirement.
Documented rules and practices that are created and maintained as a result of completing tasks.