Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Prevent manipulation of monitoring-data. a) Archive and sign logs digitally at regular intervals to ensure log integrity. b) Ensure sufficient access control for logs and implement functionality to detect attempted manipulation or deletion of logs. c) Ensure that all components are synchronised with a single time source. d) Gather and consolidate relevant monitoring-data and make available for analysis (see principle 3.3 – Analyse data from security monitoring).
Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Prevent manipulation of monitoring-data. a) Archive and sign logs digitally at regular intervals to ensure log integrity. b) Ensure sufficient access control for logs and implement functionality to detect attempted manipulation or deletion of logs. c) Ensure that all components are synchronised with a single time source. d) Gather and consolidate relevant monitoring-data and make available for analysis (see principle 3.3 – Analyse data from security monitoring).
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.
.svg)
.svg)
.svg)
Break down the framework into specific obligations that must be met.
.svg)
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.
