Requirement

RISK-2: Identify Cyber Risk

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

MIL1 requirements
a. Cyber risks are identified, at least in an ad hoc manner

MIL2 requirements
b. A defined method is used to identify cyber risks c. Stakeholders from appropriate operations and business areas participate in the identification of cyber risks
d. Identified cyber risks are consolidated into categories (for example, data breaches, insider mistakes, ransomware, OT control takeover) to facilitate management at the category level
e. Cyber risk categories and cyber risks are documented in a risk register or other artifact
f. Cyber risk categories and cyber risks are assigned to risk owners
g. Cyber risk identification activities are performed periodically and according to defined triggers, such as system changes and external events

MIL3 requirements
h. Cyber risk identification activities leverage asset inventory and prioritization information from the ASSET domain, such as IT and OT asset end of support, single points of failure, information asset risk of disclosure, tampering, or destruction
i. Vulnerability management information from THREAT domain activities is used to update cyber risks and identify new risks (such as risks arising from vulnerabilities that pose an ongoing risk to the organization or newly identified vulnerabilities)
j. Threat management information from THREAT domain activities is used to update cyber risks and identify new risks
k. Information from THIRD-PARTIES domain activities is used to update cyber risks and identify new risks
l. Information from ARCHITECTURE domain activities (such as unmitigated architectural conformance gaps) is used to update cyber risks and identify new risks m. Cyber risk identification considers risks that may arise from or impact critical infrastructure or other interdependent organizations

This requirement is part of the framework:  
C2M2: MIL1
Best practices
How to implement:
RISK-2: Identify Cyber Risk
This policy on
RISK-2: Identify Cyber Risk
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.

MIL1 requirements
a. Cyber risks are identified, at least in an ad hoc manner

MIL2 requirements
b. A defined method is used to identify cyber risks c. Stakeholders from appropriate operations and business areas participate in the identification of cyber risks
d. Identified cyber risks are consolidated into categories (for example, data breaches, insider mistakes, ransomware, OT control takeover) to facilitate management at the category level
e. Cyber risk categories and cyber risks are documented in a risk register or other artifact
f. Cyber risk categories and cyber risks are assigned to risk owners
g. Cyber risk identification activities are performed periodically and according to defined triggers, such as system changes and external events

MIL3 requirements
h. Cyber risk identification activities leverage asset inventory and prioritization information from the ASSET domain, such as IT and OT asset end of support, single points of failure, information asset risk of disclosure, tampering, or destruction
i. Vulnerability management information from THREAT domain activities is used to update cyber risks and identify new risks (such as risks arising from vulnerabilities that pose an ongoing risk to the organization or newly identified vulnerabilities)
j. Threat management information from THREAT domain activities is used to update cyber risks and identify new risks
k. Information from THIRD-PARTIES domain activities is used to update cyber risks and identify new risks
l. Information from ARCHITECTURE domain activities (such as unmitigated architectural conformance gaps) is used to update cyber risks and identify new risks m. Cyber risk identification considers risks that may arise from or impact critical infrastructure or other interdependent organizations

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
RISK-2: Identify Cyber Risk
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
RISK-2: Identify Cyber Risk
of the framework  
C2M2: MIL1
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Identification and documentation of cyber security risks
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.