ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine risk

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

The organization shall conduct risk assessments in which risk is determined by threats, vulnerabilities and impact on business processes and assets.
Guidance
- Keep in mind that threats exploit vulnerabilities.
- Identify the consequences that losses of confidentiality, integrity and availability may have on the assets and related business processes.

The organization shall conduct and document risk assessments in which risk is determined by threats, vulnerabilities, impact on business processes and assets, and the likelihood of their occurrence.
Guidance
- Risk assessment should include threats from insiders and external parties.
- Qualitative and/or quantitative risk analysis methods
(MAPGOOD, ISO27005, CIS RAM, …) can be used together with software tooling.

Risk assessment results shall be disseminated to relevant stakeholders.

This requirement is part of the framework:  
CyberFundamentals (Belgium)
Best practices
How to implement:
ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine risk
This policy on
ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine 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.

The organization shall conduct risk assessments in which risk is determined by threats, vulnerabilities and impact on business processes and assets.
Guidance
- Keep in mind that threats exploit vulnerabilities.
- Identify the consequences that losses of confidentiality, integrity and availability may have on the assets and related business processes.

The organization shall conduct and document risk assessments in which risk is determined by threats, vulnerabilities, impact on business processes and assets, and the likelihood of their occurrence.
Guidance
- Risk assessment should include threats from insiders and external parties.
- Qualitative and/or quantitative risk analysis methods
(MAPGOOD, ISO27005, CIS RAM, …) can be used together with software tooling.

Risk assessment results shall be disseminated to relevant stakeholders.

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
ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine 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
ID.RA-5: Threats, vulnerabilities, likelihoods, and impacts are used to determine risk
of the framework  
CyberFundamentals (Belgium)
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
Risk management procedure -report publishing and maintenance
Critical
High
Normal
Low
Assessment of the impact and likelihood of the risks and the scales used
Critical
High
Normal
Low
12
requirements
Risk management and leadership
Risk management

Assessment of the impact and likelihood of the risks and the scales used

This task helps you comply with the following requirements

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.