Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Vulnerability management is the ongoing activity of finding holes, ranking them, and fixing them. A vulnerability is a flaw in software or settings that an attack could use. The work is not done after one fix: you run it round and round.
How does vulnerability management work?
It resembles a periodic inspection of a house. You list the window locks, the aging roof, and the broken fence, fix first the places where rain is most likely to get in, check that they are fixed, and set the date of the next inspection.
The flow is a repeat of these steps: know the equipment and software you use, detect vulnerabilities, rank them by how dangerous they are, fix them by updates and similar means, and confirm the fix. NIST SP 800-40 Rev. 4 explains patch management as a process that includes identifying, prioritizing, obtaining, applying, and verifying the application of updates.
One input for ranking is CVSS, which turns the degree of danger into a score. CISA in the US publishes a catalog of vulnerabilities whose exploitation has actually been confirmed, the Known Exploited Vulnerabilities Catalog. Whether a hole is being exploited is also a clue for judging it.
The free URL check reads only public information from the outside, so it is not a full inventory of what you run. The whole picture of preparing for attacks is on the hacking measures page.
Why does vulnerability management matter?
Vulnerabilities that have been made public become known to many people. The later a fix, the longer the period in which you can be targeted. On the other hand, fixing every hole found at once is not realistic, so setting priorities is the heart of the work.
A vulnerability assessment is the work of finding holes. Vulnerability management means the activity that keeps going through to fixing and confirming after they are found. If you only receive an assessment and the report stays on a shelf, the holes stay as they are. The daily work of updating is called patch management and is part of vulnerability management.
Related terms
- Vulnerability: a flaw in software or settings that an attack could use
- CVSS: a common yardstick that expresses the severity of a vulnerability as a score
- Patch management: the activity of applying update programs in a planned way
- Vulnerability assessment: an investigation that searches for holes and lists them
Next step
First make a list of the software, services, and equipment you use. Without a list, you cannot judge which vulnerabilities concern you. The free URL check shows only what is visible from outside. If you are unsure how to proceed, contact us, and see the web application assessment page for the kinds of assessment.
Frequently asked questions
How is vulnerability management different from a vulnerability assessment?
An assessment is an investigation to find holes. Vulnerability management is the activity of ranking the holes found, fixing them, and confirming the fix, repeated again and again. The assessment is the step in it that finds the holes.
Which vulnerability should I fix first?
Decide by combining the score for severity with whether actual exploitation has been confirmed, whether the hole is reachable from the internet, and whether the information handled is important. Fix first the ones for which exploitation has been confirmed.
Frequently asked questions
How is vulnerability management different from a vulnerability assessment?
An assessment is an investigation to find holes. Vulnerability management is the activity of ranking the holes found, fixing them, and confirming the fix, repeated again and again. The assessment is the step in it that finds the holes.
Which vulnerability should I fix first?
Decide by combining the score for severity with whether actual exploitation has been confirmed, whether the hole is reachable from the internet, and whether the information handled is important. Fix first the ones for which exploitation has been confirmed.