ID.RA-1: Asset vulnerabilities are identified and documented.

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

Threats and vulnerabilities shall be identified.
Guidance
- A vulnerability refers to a weakness in the organization’s hardware, software, or procedures. It is a gap through which a bad actor can gain access to the organization’s assets. A vulnerability exposes an organization to threats.
- A threat is a malicious or negative event that takes advantage of a vulnerability.
- The risk is the potential for loss and damage when the threat does occur.

A process shall be established to monitor, identify, and document vulnerabilities of the organisation's business critical systems in a continuous manner.
Guidance
- Where safe and feasible, the use of vulnerability scanning should be considered.
- The organization should establish and maintain a testing program appropriate to its size, complexity, and maturity.

To ensure that organization's operations are not adversely impacted by the testing process, performance/load testing and penetration testing on the organization’s systems shall be conducted with care.
Guidance
Consider validating security measures after each penetration test.

Best practices
How to implement:
ID.RA-1: Asset vulnerabilities are identified and documented.
This policy on
ID.RA-1: Asset vulnerabilities are identified and documented.
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.

Threats and vulnerabilities shall be identified.
Guidance
- A vulnerability refers to a weakness in the organization’s hardware, software, or procedures. It is a gap through which a bad actor can gain access to the organization’s assets. A vulnerability exposes an organization to threats.
- A threat is a malicious or negative event that takes advantage of a vulnerability.
- The risk is the potential for loss and damage when the threat does occur.

A process shall be established to monitor, identify, and document vulnerabilities of the organisation's business critical systems in a continuous manner.
Guidance
- Where safe and feasible, the use of vulnerability scanning should be considered.
- The organization should establish and maintain a testing program appropriate to its size, complexity, and maturity.

To ensure that organization's operations are not adversely impacted by the testing process, performance/load testing and penetration testing on the organization’s systems shall be conducted with care.
Guidance
Consider validating security measures after each penetration test.

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-1: Asset vulnerabilities are identified and documented.
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-1: Asset vulnerabilities are identified and documented.
of the framework  
CyberFundamentals (Belgium)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Process for managing technical vulnerabilities
Critical
High
Normal
Low
41
requirements
Development and cloud
Technical vulnerability management

Process for managing technical vulnerabilities

This task helps you comply with the following requirements

Initial treatment of identified technical vulnerabilities
Critical
High
Normal
Low
20
requirements
Development and cloud
Technical vulnerability management

Initial treatment of identified technical vulnerabilities

This task helps you comply with the following requirements

Regular penetration testing
Critical
High
Normal
Low
Regular monitoring of the vulnerability management process
Critical
High
Normal
Low
18
requirements
Development and cloud
Technical vulnerability management

Regular monitoring of the vulnerability management process

This task helps you comply with the following requirements

Vulnerability monitoring in used third-party or open source libraries
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.