4.1.1: Establish plans for incident management

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

Establish plans for incident management which meet the need for business continuity at times of preparedness and crisis. This should include a) a set of requirements for restoring ICT functions, ICT services and ICT systems based on an analysis of the consequences for the organisation (BIA – business impact analysis), b) a description of roles and responsibilities for relevant personnel, c) required training of relevant personnel, d) categorization regime for incidents and threshold values for activating the crisis management team, e) requirements for testing and exercising plans and personnel. f) Revise and update plans regularly, at least once a year and after an exercise, major incident or attack.

Best practices
How to implement:
4.1.1: Establish plans for incident management

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

Establish plans for incident management which meet the need for business continuity at times of preparedness and crisis. This should include a) a set of requirements for restoring ICT functions, ICT services and ICT systems based on an analysis of the consequences for the organisation (BIA – business impact analysis), b) a description of roles and responsibilities for relevant personnel, c) required training of relevant personnel, d) categorization regime for incidents and threshold values for activating the crisis management team, e) requirements for testing and exercising plans and personnel. f) Revise and update plans regularly, at least once a year and after an exercise, major incident or attack.

Read below what concrete actions you can take to improve this ->
Frameworks that include requirements for this topic:
No items found.

How to improve security around this topic

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.

Here's a list of tasks that help you improve your information and cyber security related to
4.1.1: Establish plans for incident management
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement
4.1.1: Establish plans for incident management
of the framework  
NSM ICT Security Principles (Norway)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Creating and maintaining incident response plans
Critical
High
Normal
Low

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.