Colour theme
Book a consultation

Six steps for handling known vulnerabilities

Inventory affected systems, validate findings, prioritize exposure and verify remediation through a repeatable vulnerability-management process.

A brass padlock on a laptop keyboard, lit in red and green.

Vulnerability management is the ongoing work of finding known weaknesses, deciding what needs attention and checking that the chosen fix took effect.

A scanner can provide useful findings. It still needs an inventory, permission to assess the systems and people who can resolve the results.

1. Define the inventory and assessment scope

List devices, applications, firmware, hosted services and their owners. Record support status and exposure, including systems reachable from outside the organization.

Agree in writing what will be scanned, how and when. Older or specialist equipment, such as phone systems, medical devices or building controls, can misbehave when scanned, so involve the supplier first.

Include laptops that work from home and your cloud services, which a scan of the office network won’t reach.

2. Validate the findings

Compare detected versions and configurations with vendor advisories. Investigate uncertain results and document what the assessment couldn’t see.

A scanner may flag a version that the supplier has already patched without changing the version number, so confirm before acting. A scan can come back empty and still miss weaknesses.

A vulnerability scan looks for known weaknesses. A penetration test has a person try to get in. A clean scan doesn’t show that an attack would fail.

3. Prioritize exposure and business impact

Consider active exploitation, internet exposure, available access paths and the importance of the affected system. A severity score is one input.

CISA’s Known Exploited Vulnerabilities catalogue identifies vulnerabilities with evidence of exploitation and can inform prioritization. Its deadlines are set for US federal agencies, so set your own.

Give each finding an owner and a target date based on its risk and any contract or insurance requirements.

4. Remediate through controlled change

Apply the vendor’s fix or recommended workaround. Test it first where you can, know how you’d roll it back and plan for restarts and anything else the change affects.

Where no fix exists, you can remove the system’s internet access, isolate it on its own network segment, limit who uses it or replace it. Record any temporary measure and when you’ll review it.

The Cyber Centre’s foundational guidance includes maintaining software and addressing security weaknesses.

5. Verify closure

Confirm the installed version or configuration and repeat the relevant assessment. Test the business function after the change.

Record the advisory, affected assets, action and evidence of completion. A closed support ticket doesn’t count if the update failed on some devices.

Keep risks you’ve decided to accept on a separate list from findings you’ve fixed.

6. Repeat and respond to new information

Scan on a regular schedule, and also check urgent vendor advisories and any change that exposes a system to the internet. Update the inventory when systems are added or removed.

Track unresolved findings and repeated failures with their owners. Use the security action-plan guide to keep business decisions and technical remediation connected.


Featured Image Credit