Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Launch recovery plan during or after the incident. Measures will depend on the type of incident, but could include:
• Reactivating redundant resources lost or damaged during the incident.
• Reinstalling hardware and software on affected components.
• Restoring configuration settings, to include any necessary adjustments.
• Restoring services halted during the incident.
The ICT systems should be rebuilt to a better state than they were in before the incident occurred (“build back better”).
Launch recovery plan during or after the incident. Measures will depend on the type of incident, but could include:
• Reactivating redundant resources lost or damaged during the incident.
• Reinstalling hardware and software on affected components.
• Restoring configuration settings, to include any necessary adjustments.
• Restoring services halted during the incident.
The ICT systems should be rebuilt to a better state than they were in before the incident occurred (“build back better”).
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.
