Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Decide which data is security-relevant and should be collected. With regard to the parts of the system described in 3.2.3, one should collect the following as a minimum: a) Data relating to access control (successful and unsuccessful log-in attempts), and b) Administration and security logs from devices and services in the ICT systems. With regard to clients, one should record the following as a minimum: c) attempts to run unknown software (cf. 2.3.2), and d) attempts to seek privilege escalation.
Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Decide which data is security-relevant and should be collected. With regard to the parts of the system described in 3.2.3, one should collect the following as a minimum: a) Data relating to access control (successful and unsuccessful log-in attempts), and b) Administration and security logs from devices and services in the ICT systems. With regard to clients, one should record the following as a minimum: c) attempts to run unknown software (cf. 2.3.2), and d) attempts to seek privilege escalation.
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.
