Understanding the relationship between attack surface, vulnerabilities, and threats
Click each concept to learn more about its role in the security landscape.
What can be targeted
Weakness that exists
Actor with capability
Technique to abuse
| Aspect | Attack Surface | Vulnerability |
|---|---|---|
| Definition | Sum of all potential entry points | Specific weakness or flaw |
| Scope | Broad - entire exposure | Narrow - specific issue |
| Management | Reduce/minimize | Patch/remediate |
| Examples | Open ports, APIs, users | CVE-2021-44228, misconfig |
From discovery to remediation
Click each stage to learn about the process.
| Phase | Description | Risk Level |
|---|---|---|
| Zero-Day | Unknown to vendor, no patch exists | Critical |
| Disclosed | Publicly known, patch may be available | High |
| Patch Available | Fix released, but not yet applied | High |
| Patched | Fix applied to affected systems | Low |
How vulnerability intelligence feeds into security operations
SOC analysts use vulnerability context to prioritize alerts. An alert on a system with known critical vulnerabilities gets escalated faster.
When new vulnerabilities are disclosed (like Log4Shell), SOC proactively hunts for exploitation attempts before automated detection is tuned.
Combining vulnerability data with threat intelligence helps assess which vulnerabilities are actively being exploited in the wild.
During IR, understanding which vulnerabilities exist on compromised systems helps determine attack vector and scope.
| Source | Data Provided | SOC Use |
|---|---|---|
| Vulnerability Scanner | Asset vulnerabilities | Enrich alerts with context |
| CMDB/Asset Inventory | System criticality | Prioritize response |
| Threat Intel Feeds | Actively exploited vulns | Hunt for exploitation |
| Patch Management | Remediation status | Track exposure window |
Test your understanding of attack surface and vulnerability concepts