Vulnerability assessment

Business basics2min read

A vulnerability assessment is a structured review that identifies security weaknesses in systems, networks or applications and ranks them by risk so an organization can decide what to fix first.

The term also appears in physical security and disaster planning.

How it works

Start by defining the systems and data in scope. Use scanning tools and manual checks to find weaknesses, then validate results to remove false positives. Prioritize confirmed findings by severity, exposure and business impact. Assign fixes and retest them.

A vulnerability assessment finds and ranks weaknesses. A penetration test goes further by attempting to exploit selected weaknesses and demonstrate their consequences. Neither guarantees security.

Fixing nine findings still leaves three open

A fictional startup assesses its customer-facing application before an enterprise security review. Its scan produces 18 alerts, but manual review removes six duplicates or false positives.

ResultCount
Initial alerts18
Duplicates or false positives6
Confirmed weaknesses: 18 − 612
Fixed and verified through retesting9
Still open: 12 − 93

The startup should report three unresolved findings, their risks and planned fixes, rather than simply say it "passed a scan." One exposed administrator account could matter more than several low-impact findings.

What the report should contain

NIST's Technical Guide to Information Security Testing and Assessment covers planning, conducting tests, analyzing findings and developing mitigation strategies. Ask for affected assets, supporting evidence, recommended fixes and retest results. A raw scanner export is not evidence that remediation worked.

Questions people ask

What is CVE vs CVSS?

CVE provides identifiers for specific vulnerabilities. CVSS is a method for scoring vulnerability severity from 0 to 10. Not every assessment finding has a CVE identifier, and a CVSS score does not capture your full business risk.

What are the four types of vulnerability?

There is no universal four-part classification. Assessments are often grouped by what they examine, such as networks, individual hosts, applications or cloud configurations. Those categories overlap; define the actual scope rather than rely on a label.

Sources

  1. NIST, SP 800-115: Technical Guide to Information Security Testing and Assessment, September 2008.
  2. FIRST, Common Vulnerability Scoring System v4.0: Specification Document.
  3. CVE Program, Frequently Asked Questions.