OSCP Report Writing: Risk Assessment Methodology
1. Understanding Risk vs. Vulnerability
The Fundamental Distinction
One of the most important concepts in security reporting is understanding the difference between a vulnerability and a risk:
| Concept | Definition | Example |
|---|---|---|
| Vulnerability | A weakness in a system that could be exploited | An unpatched Apache Struts server |
| Threat | A potential cause of an unwanted incident | An attacker with internet access |
| Risk | The potential for harm when a threat exploits a vulnerability | The likelihood and impact of an attacker exploiting the unpatched server |
The Risk Formula
Risk = Likelihood × Impact
- Likelihood: How probable is it that the vulnerability will be exploited?
- Impact: How severe would the consequences be if it is exploited?
- Risk: The combination of likelihood and impact determines the overall risk level.
Why This Matters
- A critical vulnerability in an isolated, air-gapped system may have low risk (low likelihood).
- A medium vulnerability in an internet-facing production system may have high risk (high likelihood and high impact).
- Context matters. The same vulnerability has different risk in different environments.
2. Risk Matrix
The Risk Matrix Framework
The risk matrix is a visual tool that combines likelihood and impact to determine the overall risk level.
Risk Matrix Table
| Likelihood \ Impact | Negligible | Minor | Moderate | Major | Catastrophic |
|---|---|---|---|---|---|
| Almost Certain | Medium | High | High | Extreme | Extreme |
| Likely | Low | Medium | High | High | Extreme |
| Possible | Low | Medium | Medium | High | High |
| Unlikely | Negligible | Low | Medium | Medium | High |
| Rare | Negligible | Low | Low | Medium | Medium |
Visual Risk Matrix
IMPACT
Negl Minor Mod Major Catast
┌──────┬──────┬──────┬──────┬────────┐
│ │ │ │ │ │
Almost Certain │ M │ H │ H │ Ex │ Ex │
│ │ │ │ │ │
Likely │ L │ Me │ H │ H │ Ex │
LIKELIHOOD │ │ │ │ │ │
Possible │ L │ Me │ Me │ H │ H │
│ │ │ │ │ │
Unlikely │ Ne │ L │ Me │ Me │ H │
│ │ │ │ │ │
Rare │ Ne │ L │ L │ Me │ Me │
└──────┴──────┴──────┴──────┴────────┘
Legend: Ex=Extreme, H=High, Me=Medium, L=Low, Ne=Negligible
Risk Level Definitions
| Risk Level | Description | Action Required |
|---|---|---|
| Extreme | Unacceptable risk, immediate action required | Stop operations if necessary, immediate remediation |
| High | Significant risk, urgent action required | Remediate within 1 week, management awareness |
| Medium | Moderate risk, action required | Remediate within 1 month, track and monitor |
| Low | Minor risk, manageable | Remediate within 3 months, accept with monitoring |
| Negligible | Minimal risk, no action required | Accept, no immediate action needed |
3. Likelihood Assessment
Likelihood Scale
| Rating | Description | Characteristics |
|---|---|---|
| Almost Certain | Expected to occur in most circumstances | Public exploit, internet-facing, no authentication required |
| Likely | Will probably occur in most circumstances | Known vulnerability, easy to exploit, some authentication |
| Possible | May occur at some time | Vulnerability exists, requires specific conditions |
| Unlikely | Might occur in some circumstances | Vulnerability exists, difficult to exploit |
| Rare | May occur in exceptional circumstances | Theoretical vulnerability, complex exploitation |
Likelihood Factors
| Factor | Description | Effect on Likelihood |
|---|---|---|
| Exploit Availability | Public exploit code exists | Increases likelihood |
| Attack Complexity | Simple to exploit | Increases likelihood |
| Authentication Required | No authentication needed | Increases likelihood |
| Target Exposure | Internet-facing system | Increases likelihood |
| Skill Level Required | Basic skills sufficient | Increases likelihood |
| Detection Difficulty | Hard to detect | Increases likelihood |
| Vulnerability Age | Known for a long time | Increases likelihood |
| Patch Availability | No patch available | Increases likelihood |
| Security Controls | No compensating controls | Increases likelihood |
| Threat Actor Motivation | High-value target | Increases likelihood |
Likelihood Assessment Example
Scenario: SQL injection on internet-facing login page
| Factor | Assessment | Effect |
|---|---|---|
| Exploit Availability | Public tools (sqlmap) available | Increases |
| Attack Complexity | Low (automated tools work) | Increases |
| Authentication Required | None (unauthenticated) | Increases |
| Target Exposure | Internet-facing | Increases |
| Skill Level Required | Basic (automated tools) | Increases |
| Detection Difficulty | Moderate (logs may show) | Neutral |
Overall Likelihood: Almost Certain
4. Impact Assessment
Impact Scale
| Rating | Description | Characteristics |
|---|---|---|
| Catastrophic | Causes irreversible damage or complete business failure | Complete data breach, total system compromise, regulatory shutdown |
| Major | Causes significant damage or major business disruption | Large data breach, extended downtime, significant financial loss |
| Moderate | Causes noticeable damage or business disruption | Limited data exposure, partial downtime, moderate financial impact |
| Minor | Causes minor damage or inconvenience | Small data exposure, brief downtime, minimal financial impact |
| Negligible | Causes no significant damage | Informational finding, no direct impact |
Impact Factors
| Factor | Description | Effect on Impact |
|---|---|---|
| Data Sensitivity | PII, financial, health data | Increases impact |
| System Criticality | Production vs. development | Increases impact |
| Regulatory Requirements | PCI-DSS, HIPAA, GDPR | Increases impact |
| Business Disruption | Service downtime cost | Increases impact |
| Reputational Damage | Customer trust impact | Increases impact |
| Lateral Movement | Path to other systems | Increases impact |
| Data Volume | Number of affected records | Increases impact |
| Recovery Difficulty | Time and cost to recover | Increases impact |
Impact Assessment Example
Scenario: SQL injection on customer database server
| Factor | Assessment | Effect |
|---|---|---|
| Data Sensitivity | Customer PII and payment data | Increases |
| System Criticality | Production database | Increases |
| Regulatory Requirements | PCI-DSS applicable | Increases |
| Business Disruption | Potential service outage | Increases |
| Reputational Damage | Customer data breach | Increases |
| Lateral Movement | Database server has network access | Increases |
| Data Volume | 50,000 customer records | Increases |
Overall Impact: Catastrophic
5. Risk Assessment Process
Step-by-Step Process
Step 1: Identify Asset
↓
Step 2: Identify Threat
↓
Step 3: Identify Vulnerability
↓
Step 4: Assess Likelihood
↓
Step 5: Assess Impact
↓
Step 6: Calculate Risk (Likelihood × Impact)
↓
Step 7: Determine if Risk is Acceptable
↓
Step 8: If Not Acceptable → Prioritize Remediation
↓
Step 9: Implement Controls
↓
Step 10: Re-assess Risk
Detailed Steps
Step 1: Identify Asset
What is being protected? Examples:
- Customer database server
- Web application
- Domain controller
- Employee workstation
Step 2: Identify Threat
What could go wrong? Examples:
- External attacker exploiting vulnerability
- Insider threat abusing access
- Ransomware infection
- Data breach
Step 3: Identify Vulnerability
What weakness exists? Examples:
- Unpatched software
- Weak passwords
- Misconfigured firewall
- Lack of encryption
Step 4: Assess Likelihood
How likely is exploitation? Use the likelihood factors table.
Step 5: Assess Impact
How severe would the consequences be? Use the impact factors table.
Step 6: Calculate Risk
Use the risk matrix to determine the overall risk level.
Step 7: Determine if Risk is Acceptable
Compare the risk level against the organization’s risk appetite.
Step 8: Prioritize Remediation
If the risk is not acceptable, prioritize remediation based on risk level.
Step 9: Implement Controls
Apply security controls to reduce the risk.
Step 10: Re-assess Risk
After remediation, re-assess the risk to verify reduction.
6. Risk Treatment Options
The Four T’s of Risk Treatment
| Option | Description | When to Use |
|---|---|---|
| Treat (Mitigate) | Apply controls to reduce risk | High and Extreme risks |
| Tolerate (Accept) | Accept the risk as-is | Low and Negligible risks |
| Transfer (Share) | Shift risk to a third party (insurance) | Medium risks with financial impact |
| Terminate (Avoid) | Eliminate the risk by stopping the activity | Extreme risks that cannot be mitigated |
Risk Treatment Example
| Finding | Risk Level | Treatment | Action |
|---|---|---|---|
| SQL Injection on customer portal | Extreme | Treat | Immediate patching and WAF deployment |
| Missing security headers | Low | Tolerate | Schedule for next maintenance window |
| Third-party API vulnerability | Medium | Transfer | Cyber insurance coverage |
| Unnecessary service running | High | Terminate | Disable the service |
7. Risk Assessment in OSCP Reports
How to Include Risk Assessment in Your Report
For the OSCP exam, you should include risk assessment in the following sections:
- Executive Summary: Overall risk rating and findings distribution
- Each Finding: Individual risk assessment (severity + CVSS score)
- Risk Summary: Aggregate risk matrix and distribution
- Recommendations: Prioritized remediation based on risk
Risk Summary Template
RISK SUMMARY
The following table summarizes the risk assessment for all findings
identified during this engagement:
| Finding ID | Vulnerability | Likelihood | Impact | Risk Level |
|---|---|---|---|---|
| VULN-001 | SQL Injection | Almost Certain | Catastrophic | Extreme |
| VULN-002 | Privilege Escalation | Likely | Major | High |
| VULN-003 | Information Disclosure | Possible | Moderate | Medium |
| VULN-004 | Missing Headers | Unlikely | Minor | Low |
Overall Risk Assessment: HIGH
The presence of Extreme and High risk findings indicates that
immediate remediation is required to reduce the organization's
attack surface and protect critical assets.
8. Key Takeaways
- Risk = Likelihood × Impact. This formula is the foundation of risk assessment.
- Context matters. The same vulnerability has different risk in different environments.
- Use the risk matrix. It provides a visual and consistent way to assess risk.
- Consider all factors. Both likelihood and impact have multiple contributing factors.
- Prioritize by risk. Remediation should be prioritized based on risk level, not just severity.
- Re-assess after remediation. Verify that controls effectively reduce risk.
- For OSCP: Include risk assessment in the executive summary, each finding, and the risk summary section.
9. Further Reading
- NIST SP 800-30 Risk Management Guide
- ISO 31000 Risk Management Standards
- OCTAVE Risk Assessment Methodology
- FAIR (Factor Analysis of Information Risk) Framework