Requirement

RESPONSE-4: Address Cybersecurity in Continuity of Operations

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

MIL1 requirements
a. Continuity plans are developed to sustain and restore operation of the function if a cybersecurity event or incident occurs, at least in an ad hoc manner
b. Data backups are available and tested, at least in an ad hoc manner
c. IT and OT assets requiring spares are identified, at least in an ad hoc manner

MIL2 requirements
d. Continuity plans address potential impacts from cybersecurity incidents
e. The assets and activities necessary to sustain minimum operations of the function are identified and documented in continuity plans
f. Continuity plans address IT, OT, and information assets that are important to the delivery of the function, including the availability of backup data and replacement, redundant, and spare IT and OT assets
g. Recovery time objectives (RTOs) and recovery point objectives (RPOs) for assets that are important to the delivery of the function are incorporated into continuity plans
h. Cybersecurity incident criteria that trigger the execution of continuity plans are established and communicated to incident response and continuity management personnel
i. Continuity plans are tested through evaluations and exercises periodically and according to defined triggers, such as system changes and external events
j. Cybersecurity controls protecting backup data are equivalent to or more rigorous than controls protecting source data
k. Data backups are logically or physically separated from source data
l. Spares for selected IT and OT assets are available

MIL3 requirements
m. Continuity plans are aligned with identified risks and the organization’s threat profile (THREAT-2e) to ensure coverage of identified risk categories and threats
n. Continuity plan exercises address higher priority risks
o. The results of continuity plan testing or activation are compared to recovery objectives, and plans are improved accordingly
p. Continuity plans are periodically reviewed and updated

This requirement is part of the framework:  
C2M2: MIL1
Best practices
How to implement:
RESPONSE-4: Address Cybersecurity in Continuity of Operations

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

MIL1 requirements
a. Continuity plans are developed to sustain and restore operation of the function if a cybersecurity event or incident occurs, at least in an ad hoc manner
b. Data backups are available and tested, at least in an ad hoc manner
c. IT and OT assets requiring spares are identified, at least in an ad hoc manner

MIL2 requirements
d. Continuity plans address potential impacts from cybersecurity incidents
e. The assets and activities necessary to sustain minimum operations of the function are identified and documented in continuity plans
f. Continuity plans address IT, OT, and information assets that are important to the delivery of the function, including the availability of backup data and replacement, redundant, and spare IT and OT assets
g. Recovery time objectives (RTOs) and recovery point objectives (RPOs) for assets that are important to the delivery of the function are incorporated into continuity plans
h. Cybersecurity incident criteria that trigger the execution of continuity plans are established and communicated to incident response and continuity management personnel
i. Continuity plans are tested through evaluations and exercises periodically and according to defined triggers, such as system changes and external events
j. Cybersecurity controls protecting backup data are equivalent to or more rigorous than controls protecting source data
k. Data backups are logically or physically separated from source data
l. Spares for selected IT and OT assets are available

MIL3 requirements
m. Continuity plans are aligned with identified risks and the organization’s threat profile (THREAT-2e) to ensure coverage of identified risk categories and threats
n. Continuity plan exercises address higher priority risks
o. The results of continuity plan testing or activation are compared to recovery objectives, and plans are improved accordingly
p. Continuity plans are periodically reviewed and updated

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
RESPONSE-4: Address Cybersecurity in Continuity of Operations
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
RESPONSE-4: Address Cybersecurity in Continuity of Operations
of the framework  
C2M2: MIL1
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical

The ISMS component hierachy

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.