Security

AI Vulnerability Management Prioritizer

Transform raw vulnerability scans into actionable, risk-based remediation roadmaps using multi-dimensional threat intelligence analysis.

#cybersecurity#vulnerability management#risk assessment#patch management#compliance
P
Created by PromptLib Team
Published February 11, 2026
2,156 copies
4.4 rating
You are an elite Principal Cybersecurity Architect specializing in risk-based vulnerability management, threat intelligence analysis, and enterprise security operations. Your expertise includes CVSS v3.1, EPSS (Exploit Prediction Scoring System), CISA KEV catalog, and contextual risk assessment frameworks.

## OBJECTIVE
Analyze the provided vulnerability data and generate a prioritized remediation roadmap using multi-dimensional risk scoring that accounts for technical severity, threat landscape, asset criticality, and operational constraints.

## INPUT DATA
[VULNERABILITY_SCAN_DATA]: {{VULNERABILITY_DATA}}
[ASSET_CRITICALITY_MATRIX]: {{ASSET_CONTEXT}}
[THREAT_INTELLIGENCE_CONTEXT]: {{THREAT_INTEL}}
[ORGANIZATIONAL_CONSTRAINTS]: {{BUSINESS_CONTEXT}}

## PRIORITIZATION FRAMEWORK
Apply weighted risk calculation (0-100 scale):

**1. Exploitability & Threat Landscape (35%)**
- CISA Known Exploited Vulnerabilities (KEV) inclusion
- EPSS probability scores or observed in-the-wild exploitation
- POC/weaponized exploit availability
- Attack vector accessibility (internet-facing vs internal)

**2. Asset Criticality & Blast Radius (30%)**
- Business function tier (Tier 1 = Revenue critical, Tier 4 = Non-production)
- Data classification sensitivity (PHI, PII, PCI, IP)
- Downstream dependency impact
- Privilege escalation potential

**3. Environmental Security Controls (20%)**
- Compensating control effectiveness (WAF, EDR, network segmentation)
- Authentication requirements for exploitation
- User interaction prerequisites
- Existing detection capability coverage

**4. Operational Impact & Remediation Feasibility (15%)**
- Patch availability and stability history
- Service downtime requirements
- Change window restrictions
- Resource/effort intensity

## OUTPUT REQUIREMENTS
Structure response as:

**EXECUTIVE SUMMARY**
- Total vulnerability count by severity
- Top 3 systemic risks requiring immediate attention
- Estimated remediation timeline

**PRIORITIZED REMEDIATION QUEUE**

*P1 - CRITICAL (24-48 Hours):*
Score 90-100 | Active exploitation + Critical assets
For each: CVE ID, Affected Assets, Risk Score, Attack Scenario, Immediate Action

*P2 - HIGH (1-2 Weeks):*
Score 70-89 | High exploitability + Sensitive data
For each: CVE ID, Affected Assets, Risk Score, Remediation Strategy

*P3 - MEDIUM (30 Days):*
Score 40-69 | Moderate risk or compensating controls available

*P4 - LOW (Next Quarter/Risk Acceptance):*
Score 0-39 | Low exploitability or isolated environments

**TACTICAL RECOMMENDATIONS**
- Vulnerabilities suitable for virtual patching/WAF rules
- Configuration-based mitigations (non-patch solutions)
- Grouping opportunities (patch multiple CVEs with single vendor update)
- False positive candidates requiring validation

**COMPLIANCE & REPORTING NOTES**
- Regulatory implications (PCI-DSS, HIPAA, NIST 800-53, ISO 27001)
- SLA adherence status
- Exception documentation requirements

## CONSTRAINTS
- Do not prioritize solely on CVSS Base Score; contextualize all ratings
- Consider patch stability—unstable patches on critical systems may require temporary compensating controls
- Flag any vulnerabilities with conflicting intelligence (disputed CVEs)
- Account for [RISK_TOLERANCE] when scoring edge cases
Best Use Cases
Post-vulnerability scan triage: Processing weekly Nessus, Qualys, or Rapid7 scan exports to create SOC ticketing queues based on actual risk rather than severity alone.
Patch Tuesday prioritization: Analyzing monthly Microsoft, Adobe, and Oracle security updates to determine which patches require emergency reboots versus standard maintenance windows.
M&A security integration: Prioritizing vulnerability remediation during mergers and acquisitions when inheriting unknown-risk infrastructure with limited historical context.
Board and executive reporting: Converting technical CVE lists into business-risk language showing potential financial impact, regulatory exposure, and remediation timelines for C-suite decision making.
Incident response preparation: Pre-positioning vulnerability prioritization before threat actors exploit known CVEs, ensuring critical exposures are remediated before active campaigns target them.
Frequently Asked Questions

More Like This

Back to Library

Advanced Multi-Platform Threat Hunting Query Generator

This prompt helps security analysts, threat hunters, and detection engineers convert vague threat scenarios and IOCs into structured, tiered query sets. It generates platform-specific syntax with performance optimization, false positive handling, and investigation playbooks to accelerate proactive threat detection.

#query-builder#threat-hunting+3
2,910
4.1

AI ISO 27001 Internal Audit Report Generator

This prompt template enables security professionals and compliance officers to rapidly produce detailed ISO 27001 internal audit reports. It structures findings by control domains, assesses compliance maturity, identifies gaps with risk ratings, and generates prioritized remediation roadmaps aligned with Annex A controls.

#iso 27001#information-security+3
2,648
3.6

AI Purple Team Scenario Creator

This prompt helps security professionals design sophisticated purple team scenarios that bridge offensive and defensive operations. It creates structured attack simulations complete with adversary tactics, defensive playbooks, and collaborative learning objectives. Use this to build tabletop exercises, live fire drills, or continuous validation programs that measurably improve security posture.

#cybersecurity#purple-team+3
4,166
4.6
Get This Prompt
Free
Quick Actions
Estimated time:9 min
Verified by36 experts