VISA · Vulnerability Impact Scoring Automation
Intake
Incoming — suspected vulnerabilities
ALL ITEMS ↓
Filter 1 DON’T FIX IF NOT A VUL
Is it a vulnerability?
- Vulnerability — applies to code → continues
- Protection Weakness — applies to system → don’t fix as vulnerability
- Mitigation Exposure — applies to security control → don’t fix as vulnerability
CODE VULS ONLY ↓
Filter 2 DON’T FIX IF LOW / MEDIUM
Behavior base — is the impact Critical?
- Compute — install / CE, tamper, read configs → Critical
- Data — CRUD on PII → Critical · system / service → High
- Service — down → Critical · random → High · load → Medium
CRITICAL IMPACT ↓
Filter 3 MAY REDUCE
Exploit level
- CE — full code execution demonstrated → no reduction
- PoC — behavior change proven, not full CE → no reduction
- Theoretical — condition exists, no behavior shown → reduce one level
PROVEN EXPLOITS ↓
Filter 4 AUTHENTICATED = LOWER
Auth context
- Unauthenticated — remote, over the web (RCE) → keeps severity
- Authenticated — low / medium / high privileges → lower in scoring
- Logged in as root → not a vulnerability
RISK FLOORS ↓
Veto Gate MAY RESTORE CRITICAL
Risk floors — vendor system definition
- Service is mission critical
- Data is confidential — PII, secrets, or by system definition
- Compute is publicly accessible — CE on data / control plane
VENDOR SCORE ↓
Output · SE decides and signs off
Vendor score → fix decision
SEV 1FIX now — top priority · potential Crisis Response
SEV 2FIX soon · potential Emergency Response
SEV 3FIX later · potential Incident Response
