Asset Criticality and Business Context
What you'll learn: How to weight vulnerability severity based on what the asset actually does for your business, not just the technical CVSS score.
Why Technical Scores Aren't Enough
You've learned CVSS, EPSS, SSVC, and threat intelligence integration—but a critical vulnerability in a honeypot server is not the same as one in your payment gateway. Asset criticality means understanding which systems matter most to your organization's mission, revenue, compliance, and operations.
A CVSS 9.8 vulnerability sounds terrifying, but if it's on an isolated test server with no sensitive data, it's far less urgent than a CVSS 6.5 flaw on your customer database that's internet-facing and processes credit cards.
Core Components of Business Context
Asset Value
What does this system do? Revenue generation, customer trust, regulatory compliance, operational continuity—these define value beyond uptime.
Business Function
Is this asset part of your primary service delivery? Supporting infrastructure? Development environment? Production always trumps staging.
Data Sensitivity
What data lives here or flows through it? PII, payment card data, trade secrets, or just publicly available information? Data classification drives risk.
Exposure Level
Internet-facing assets accessible to anyone carry higher risk than internal systems behind multiple network segments and access controls.
Practical Weighting Example
Consider two vulnerabilities:
- Server A: CVSS 8.5, internal file server, general business documents
- Server B: CVSS 7.0, customer portal, processes transactions, internet-facing, stores PII
Server B's vulnerability should be remediated first despite the lower technical score—it combines high exposure, sensitive data, and critical business function.
Key Takeaway: Vulnerability management without asset criticality is just playing whack-a-mole with numbers. Context transforms raw scores into actionable business risk decisions.