Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Log all activities, results and relevant decisions for subsequent analysis. a) Establish a timeline of the organisation’s own and the threat actor’s activities. b) Update event data and situational awareness continuously in order to manage the incident in the best possible way. c) Secure electronic evidence for malware analysis and potential legal processes, see also principle 3.2 – Establish security monitoring.
Log all activities, results and relevant decisions for subsequent analysis. a) Establish a timeline of the organisation’s own and the threat actor’s activities. b) Update event data and situational awareness continuously in order to manage the incident in the best possible way. c) Secure electronic evidence for malware analysis and potential legal processes, see also principle 3.2 – Establish 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.
