Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Incident response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) shall be established, maintained, approved, and tested to determine the effectiveness of the plans, and the readiness to execute the plans.
Guidance
- The incident response plan is the documentation of a predetermined set of instructions or
procedures to detect, respond to, and limit consequences of a malicious cyber-attack.
- Plans should incorporate recovery objectives, restoration priorities, metrics, contingency roles,
personnel assignments and contact information.
- Maintaining essential functions despite system disruption, and the eventual restoration of the
organization’s systems, should be addressed.
- Consider defining incident types, resources and management support needed to effectively maintain
and mature the incident response and contingency capabilities.
The organization shall coordinate the development and the testing of incident response
plans and recovery plans with stakeholders responsible for related plans.
Guidance
Related plans include, for example, Business Continuity Plans, Disaster Recovery Plans, Continuity of
Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber incident response
plans, and Occupant Emergency Plans.
Incident response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) shall be established, maintained, approved, and tested to determine the effectiveness of the plans, and the readiness to execute the plans.
Guidance
- The incident response plan is the documentation of a predetermined set of instructions or
procedures to detect, respond to, and limit consequences of a malicious cyber-attack.
- Plans should incorporate recovery objectives, restoration priorities, metrics, contingency roles,
personnel assignments and contact information.
- Maintaining essential functions despite system disruption, and the eventual restoration of the
organization’s systems, should be addressed.
- Consider defining incident types, resources and management support needed to effectively maintain
and mature the incident response and contingency capabilities.
The organization shall coordinate the development and the testing of incident response
plans and recovery plans with stakeholders responsible for related plans.
Guidance
Related plans include, for example, Business Continuity Plans, Disaster Recovery Plans, Continuity of
Operations Plans, Crisis Communications Plans, Critical Infrastructure Plans, Cyber incident response
plans, and Occupant Emergency Plans.
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.