A vulnerability is a weak spot through which an attacker can get into a system. NIST defines it as a weakness in an information system, system security procedures, internal controls or implementation that could be exploited or triggered by a threat source. According to the review by Ukraine’s National Cybersecurity Coordination Center, exploiting vulnerabilities was one of the main ways into networks in 2025.
New vulnerabilities appear all the time, so a one-off check will not help. You need a process — vulnerability management. Below: how to set it up.
The vulnerability management cycle
- Inventory. You cannot protect what you do not know about: servers, workstations, network equipment, websites, cloud resources, printers and cameras.
- Scanning. Regular automated checks of all assets for known vulnerabilities — from outside and inside the network.
- Assessment and priorities. What to fix first and what can wait.
- Remediation. Updates, configuration changes or, if updating is not possible, compensating measures.
- Verification. A repeat scan: is the vulnerability really closed?
- Reporting. What was found, what was fixed, what remains and why.
NIST describes enterprise patch management as the process of identifying, prioritizing, acquiring, installing and verifying the installation of patches, updates and upgrades throughout an organization — and frames it as preventive maintenance and a cost of doing business.
How to decide what to fix first
A scanner often finds more vulnerabilities than can be fixed at once, so priorities matter:
- CVSS — a severity score for a vulnerability on a scale from 0 to 10.
- EPSS — FIRST’s estimate of how likely a vulnerability is to be exploited in the wild in the next 30 days.
- The KEV catalog from CISA — vulnerabilities already exploited in real attacks. CISA recommends using it as an input to prioritization.
- Your context: is the system reachable from the internet? Is it critical to the business? Are there compensating measures?
| Situation | Priority |
|---|---|
| The vulnerability is already exploited in attacks, the system faces the internet | Immediately |
| High severity and high likelihood of exploitation, or a critical system | First |
| High severity, but the system is isolated and compensating measures exist | As planned |
| Low severity, internal system | With regular updates |
Write down the deadlines for each level and stick to them.
Scanning or a penetration test
A scanner finds known vulnerabilities and misconfigurations — quickly and regularly. A penetration test shows which of them can really be exploited and what an attacker would gain. One does not replace the other: scanning between penetration tests, and a penetration test to check defences in practice. More in “Penetration testing: what it is, types and stages”.
What to do if you cannot update
Sometimes there is no update, the vendor has ended support, or the update breaks a business application. Then use compensating measures:
- isolate the system in a separate network segment and restrict access to it;
- close the vulnerable service off from the internet;
- protect a web application with a WAF;
- step up monitoring of that system;
- plan a replacement.
For insurers, credit unions, finance companies and pawnshops, NBU Resolution No. 143 requires a risk analysis and compensating measures for software no longer supported by its vendor, including regular security monitoring and audit to detect and remediate vulnerabilities (paragraph 34). More in “Windows Server 2016 end of support: what to do”.
Common mistakes
- Scanning without fixing. A report without owners and deadlines changes nothing.
- An incomplete asset list: forgotten servers, test environments, network equipment.
- Looking only at CVSS and missing less severe vulnerabilities that are already being exploited.
- No check after updating.
- A long report without priorities that the IT team struggles to work with.
Checklist
- There is an up-to-date asset list, including network equipment and cloud resources
- Scanning runs regularly — from outside and inside the network
- Priorities take CVSS, EPSS, the KEV catalog and internet exposure into account
- Remediation deadlines are written down for each severity level
- After updating, the vulnerability is checked again
- Systems that cannot be updated have compensating measures and a replacement plan
- Management receives a short report regularly
How Bereg-IT can help
We set up vulnerability management: finding and analysing vulnerabilities in IT infrastructure and key services, hardware included, ranking risks by severity, remediation recommendations and help with design and engineering work. A WAF protects web applications from mass exploitation of vulnerabilities, and a penetration test shows what of all this can really be exploited.
The first consultation is free. Send a request and an information security specialist will get in touch.
Sources
- NIST CSRC Glossary, vulnerability: https://csrc.nist.gov/glossary/term/vulnerability
- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology (April 2022): https://csrc.nist.gov/pubs/sp/800/40/r4/final
- FIRST, Common Vulnerability Scoring System (CVSS): https://www.first.org/cvss/; Exploit Prediction Scoring System (EPSS): https://www.first.org/epss/
- CISA, Known Exploited Vulnerabilities Catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- National Cybersecurity Coordination Center at the NSDC of Ukraine, Review of the National Cybersecurity System of Ukraine 2025 (in Ukrainian): https://www.rnbo.gov.ua/files/2026/NATIONAL_CYBER_SCC/kiber_2025.pdf
- Resolution of the Board of the National Bank of Ukraine of 09.12.2025 No. 143, paragraph 34 of the Regulation (in Ukrainian): https://bank.gov.ua/admin_uploads/law/09122025_143.pdf