Requirement

8.2.2: Business impact analysis

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

To establish business continuity requirements, the organization must conduct a formal business impact analysis. This analysis shall identify critical activities and evaluate the escalating consequences of their disruption over time against defined criteria. The process must determine the point at which impacts become unacceptable, thereby setting recovery time objectives for resuming operations at a minimum capacity. Furthermore, all necessary resources and dependencies, including those involving partners, must be identified for these priority activities.

See how Cyberday guides you to fulfill this requirement:
This requirement is part of the framework:  
ISO 22301:2019

Other requirements of the framework

51403
8.2.2: Business impact analysis
Best practices
How to implement:
8.2.2: Business impact analysis
This policy on
8.2.2: Business impact analysis
provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

To establish business continuity requirements, the organization must conduct a formal business impact analysis. This analysis shall identify critical activities and evaluate the escalating consequences of their disruption over time against defined criteria. The process must determine the point at which impacts become unacceptable, thereby setting recovery time objectives for resuming operations at a minimum capacity. Furthermore, all necessary resources and dependencies, including those involving partners, must be identified for these priority activities.

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
8.2.2: Business impact analysis
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
8.2.2: Business impact analysis
of the framework  
ISO 22301:2019
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Formal business impact analysis for prioritized activities
Critical
High
Normal
Low
2
requirements
Risk management and leadership
Continuity management

Formal business impact analysis for prioritized activities

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Conducting business impact analysis
Critical
High
Normal
Low
5
requirements
Risk management and leadership
Cyber security management

Conducting business impact analysis

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Definition of recovery objectives and resource dependencies
Critical
High
Normal
Low
2
requirements
Risk management and leadership
Continuity management

Definition of recovery objectives and resource dependencies

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

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.