performing-asset-criticality-scoring-for-vulns

Score asset criticality with weighted factors and adjust vulnerability remediation SLAs by tier.

4|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/braydos-h/BreachPilot --skill performing-asset-criticality-scoring-for-vulns-braydos-h
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: performing-asset-criticality-scoring-for-vulns
Source: https://github.com/braydos-h/BreachPilot/tree/main/skills/performing-asset-criticality-scoring-for-vulns
Command: npx skills add https://github.com/braydos-h/BreachPilot --skill performing-asset-criticality-scoring-for-vulns-braydos-h

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pandas, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Vulnerability teams often treat a CVSS 9.0 flaw on a test server the same as one on a payment database because raw severity scores ignore business context. This Skill builds a multi-factor asset criticality model so remediation effort is weighted by business impact, data sensitivity, and operational importance. ## Core Features & Use Cases - Multi-Factor Scoring Engine: Weights business function, data sensitivity, regulatory scope, network exposure, recoverability, and user population into a 1-5 criticality tier. - Risk-Adjusted Prioritization: Combines CVSS scores with tier multipliers and generates per-tier remediation SLA matrices (e.g., 24h for Crown Jewel criticals). - CMDB and Ticketing Integration: Consumes CSV asset inventories and outputs scored assets and SLA-adjusted vulnerability lists for Jira, ServiceNow, or SIEM enrichment. - Use Case: Load a CMDB export of 500 assets, score each into tiers, then apply the tiers to a scanner export so that critical findings on Crown Jewel systems get 24-hour SLAs while lab systems get 30 days. ## Quick Start Ask the AI to score the assets in your inventory CSV and produce a tiered report with adjusted vulnerability remediation SLAs.

Frequently Asked Questions about performing-asset-criticality-scoring-for-vulns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize vulnerabilities based on asset criticality?▼

Score each asset with weighted factors like data sensitivity, business function, and network exposure, then multiply the CVSS score by a tier multiplier (1.5 for Crown Jewels down to 0.5 for Minimal). The adjusted priority and per-tier SLA matrix drive remediation order.

What factors should an asset criticality scoring model include?▼

This model uses six weighted factors: business function (25%), data sensitivity (25%), regulatory scope (15%), network exposure (15%), recoverability (10%), and user population (10%). Each factor is scored 1-5 and combined into a weighted score mapped to five tiers.

What input format does the asset criticality scoring script require?▼

The scripts accept a CSV asset inventory with columns for hostname, data_classification, business_function, regulatory_scope, network_exposure, recoverability, and user_count. The process.py script additionally requires pandas and supports score and apply subcommands.

How are vulnerability remediation SLAs adjusted by asset tier?▼

Each tier carries an SLA modifier: Tier 1 Crown Jewels shorten base SLAs by 50%, Tier 2 by 25%, Tier 3 keeps baseline, and Tiers 4-5 extend SLAs by 25-50%. The agent script also emits a full SLA matrix, such as 24 hours for critical findings on Tier 1 assets.

What are common mistakes when implementing asset criticality scoring?▼

Common pitfalls include classifying all assets as critical, never updating scores when systems change roles, using only technical factors without business input, and applying uniform SLAs. Scores should be reviewed quarterly with business stakeholders and calibrated against real incident impact data.