A vulnerability management plan is developed and implemented.

The organization has defined a process for addressing identified technical vulnerabilities.

Some vulnerabilities can be fixed directly, but vulnerabilities that have a significant impact should also be documented as security incidents. Once a vulnerability with significant impacts has been identified:

• risks related to the vulnerability and the necessary actions are identified (e.g. patching the system or other management tasks)
• necessary actions are scheduled
• all actions taken are documented

The organization regularly conducts a vulnerability scan, which searches for vulnerabilities found on computers, workstations, mobile devices, networks or applications. It is important to scan even after significant changes.

It should be noted that vulnerable source code can be from operating system software, server applications, user applications, as well as from the firmware application as well as from drivers, BIOS and separate management interfaces (e.g. iLo , iDrac). In addition to software errors, vulnerabilities occur from configuration errors and old practices, such as the use of outdated encryption algorithms.

We have defined the rules for responding to identified vulnerabilities. The rules may include e.g. the following things:

• who are part of a quick-response team that is ready to respond to vulnerabilities
• the person locating the vulnerability immediately informs the entire team down the agreed channel
• the team determines the severity of the vulnerability (low, medium, high) based on predefined criteria
• the team decides whether to continue processing as a security breach (more urgently) or under general change management
• the necessary individuals are selected to continue addressing the vulnerability

Vulnerabilities related to high-risk data systems are always of high severity and are addressed first.

The technical vulnerability management process is regularly monitored and evaluated to ensure its effectiveness and efficiency.