Vulnerability Severity and Risk Rating
What you'll learn: How to quantify and communicate the seriousness of discovered vulnerabilities using standardized scoring systems and business context.
The Challenge of Measuring Risk
After finding vulnerabilities during penetration testing, you face a critical question: how bad is this, really? Not all flaws are created equal—a cross-site scripting bug in a demo site differs vastly from remote code execution on a payment server. Your job is to translate technical findings into actionable risk assessments that both technical teams and business leaders understand.
Understanding CVSS
The Common Vulnerability Scoring System (CVSS) provides a standardized framework for rating vulnerabilities from 0.0 to 10.0. It evaluates three metric groups:
- Base metrics: Exploitability (attack vector, complexity, privileges required) and impact (confidentiality, integrity, availability)
- Temporal metrics: Exploit maturity, remediation availability, report confidence
- Environmental metrics: How the vulnerability affects your specific environment
A vulnerability might score 9.8 in a vacuum, but if it requires physical access to an air-gapped system with no sensitive data, the actual risk is low.
Beyond the Score
CVSS is a starting point, not the final word. Consider:
- Exploitability: Is there public exploit code? Have you verified it works?
- Business impact: What happens if this is exploited? Revenue loss? Regulatory penalties? Reputation damage?
- Asset criticality: Database servers matter more than staging environments
- Compensating controls: Does a firewall or WAF reduce realistic exploitability?
Think of CVSS like a car's crash test rating—important, but you also need to know if the driver wears a seatbelt (controls) and where they're driving (context).
Key Takeaway: Effective vulnerability rating combines standardized CVSS scoring with business impact analysis and real-world exploitability to communicate risk accurately and drive prioritized remediation decisions.