Colour theme
Book a consultation

Matching vulnerability advisories to your systems

Read vulnerability identifiers, affected versions and vendor instructions against your inventory before deciding which systems need action.

A hooded figure against a background of green computer code

A vulnerability advisory is useful when you can connect it to a system your business runs. A familiar vendor name or an alarming headline doesn’t tell you whether your installed version is affected.

Older weaknesses can still matter on neglected systems. The date of a news story also doesn’t make its product list a current assessment of your network.

Start with the identifier and original advisory

A CVE identifier names a particular reported vulnerability. Use it to find the vendor’s advisory and confirm that the product, component and technical description match.

Read the affected versions and any required conditions. A desktop application, a server component and a browser engine can share a brand while needing different actions.

Don’t infer the mechanism from a brief summary. Remote code execution, authentication bypass and denial of service describe different effects.

Match the installed component

Check the installed version, edition, firmware and configuration against the advisory. Include software embedded in another application and equipment managed by a supplier.

Ask the owner of a hosted service what applies and what they will address. Your business may still be responsible for a local client or connector.

If the inventory is incomplete, note the gap and look into it. Don’t mark a product as absent until someone has checked.

Understand evidence of exploitation

CISA’s Known Exploited Vulnerabilities catalogue records vulnerabilities with evidence of exploitation. It can inform priorities alongside vendor advisories and the Cyber Centre’s alerts and advisories.

CISA explains in its catalogue alert guidance that the associated directive applies to US federal civilian executive branch agencies. Its listed due dates aren’t automatically Canadian business deadlines.

A vulnerability that isn’t in the catalogue can still be exploited, so don’t treat a missing entry as a reason to wait.

Separate the fix from temporary measures

Read the vendor’s supported resolution, including prerequisites, restarts and verification instructions. Confirm that the advisory hasn’t been revised.

A workaround may reduce one attack path while leaving the underlying flaw present. Record its limits and who will revisit it.

For unsupported software, an old patch may not provide a supported destination. Assess replacement with the application’s owner. Don’t remove operating-system components indiscriminately because a browser name appears in an advisory.

Hand off a clear finding

Give the technical owner the identifier, affected asset, installed version, source link and required decision. Include the business function and any evidence of suspicious activity.

Use the six-step vulnerability workflow to track assessment, action and verification after the finding is understood.

Our managed IT service can connect findings with supported update and replacement work. Confirm the installed result and test the business function before treating the finding as resolved.


Featured Image Credit