Performing Asset Criticality Scoring for Vulns
Overview
Asset criticality scoring assigns a business impact rating to each IT asset so that vulnerability remediation efforts focus on systems with the greatest organizational risk. Without criticality context, a CVSS 9.0 vulnerability on a test server receives the same urgency as the same vulnerability on a payment processing database. This skill covers building a multi-factor scoring model incorporating data sensitivity, business function dependency, regulatory scope, network exposure, and recoverability to create a 1-5 criticality tier that directly modifies vulnerability remediation SLAs.
When to Use
- When conducting security assessments that involve performing asset criticality scoring for vulns
- When following incident response procedures for related security events
- When performing scheduled security testing or auditing activities
- When validating security controls through hands-on testing
Prerequisites
- Configuration Management Database (CMDB) or asset inventory
- Business Impact Analysis (BIA) data
- Data classification policy
- Network architecture documentation
- Stakeholder input from business unit owners
Core Concepts
Asset Criticality Scoring Model
| Factor |
Weight |
Score Range |
Description |
| Business Function Impact |
25% |
1-5 |
How critical is the supported business process |
| Data Sensitivity |
25% |
1-5 |
Type and sensitivity of data processed/stored |
| Regulatory Scope |
15% |
1-5 |
Regulatory requirements (PCI, HIPAA, SOX) |
| Network Exposure |
15% |
1-5 |
Internet-facing vs internal-only |
| Recoverability |
10% |
1-5 |
RTO/RPO requirements, DR capability |
| User Population |
10% |
1-5 |
Number of users/customers affected |
Criticality Tier Definitions
| Tier |
Score Range |
Label |
SLA Modifier |
Examples |
| 1 |
4.5-5.0 |
Crown Jewels |
-50% SLA |
Domain controllers, payment systems, ERP |
| 2 |
3.5-4.4 |
High Value |
-25% SLA |
Email servers, HR systems, CI/CD |
| 3 |
2.5-3.4 |
Standard |
Baseline SLA |
Internal apps, file servers |
| 4 |
1.5-2.4 |
Low Impact |
+25% SLA |
Test environments, printers |
| 5 |
1.0-1.4 |
Minimal |
+50% SLA |
Decommissioning, isolated labs |
Data Sensitivity Scoring
| Score |
Classification |
Examples |
| 5 |
Restricted/Secret |
PII, PHI, payment card data, trade secrets |
| 4 |
Confidential |
Financial reports, HR records, source code |
| 3 |
Internal |
Internal documents, policies, project files |
| 2 |
Semi-public |
Marketing materials, press releases (draft) |
| 1 |
Public |
Published content, public APIs |
Workflow
Step 1: Define Scoring Criteria
class AssetCriticalityScorer:
"""Multi-factor asset criticality scoring engine."""
WEIGHTS = {
"business_function": 0.25,
"data_sensitivity": 0.25,
"regulatory_scope": 0.15,
"network_exposure": 0.15,
"recoverability": 0.10,
"user_population": 0.10,
}
TIER_THRESHOLDS = [
(4.5, 1, "Crown Jewels", -0.50),
(3.5, 2, "High Value", -0.25),
(2.5, 3, "Standard", 0.00),
(1.5, 4, "Low Impact", 0.25),
(1.0, 5, "Minimal", 0.50),
]
def score_asset(self, asset):
"""Calculate criticality score for an asset."""
weighted_score = sum(
asset.get(factor, 3) * weight
for factor, weight in self.WEIGHTS.items()
)
score = round(weighted_score, 2)
for threshold, tier, label, sla_mod in self.TIER_THRESHOLDS:
if score >= threshold:
return {
"score": score,
"tier": tier,
"label": label,
"sla_modifier": sla_mod,
}
return {"score": score, "tier": 5, "label": "Minimal", "sla_modifier": 0.50}
def adjust_vuln_sla(self, base_sla_days, asset_tier_data):
"""Adjust vulnerability SLA based on asset criticality."""
modifier = asset_tier_data["sla_modifier"]
adjusted = int(base_sla_days * (1 + modifier))
return max(1, adjusted) # Minimum 1 day SLA
Step 2: Integrate with Vulnerability Prioritization
def apply_criticality_to_vulns(vulns_df, asset_scores):
"""Enrich vulnerability data with asset criticality context."""
for idx, vuln in vulns_df.iterrows():
asset_id = vuln.get("asset_id", "")
asset_data = asset_scores.get(asset_id, {"tier": 3, "sla_modifier": 0})
vulns_df.at[idx, "asset_tier"] = asset_data["tier"]
vulns_df.at[idx, "asset_label"] = asset_data.get("label", "Standard")
base_sla = get_base_sla(vuln["severity"])
adjusted_sla = int(base_sla * (1 + asset_data["sla_modifier"]))
vulns_df.at[idx, "adjusted_sla_days"] = max(1, adjusted_sla)
return vulns_df
Best Practices
- Involve business stakeholders in criticality scoring; IT alone cannot assess business impact
- Review and update criticality scores at least quarterly or when systems change roles
- Automate scoring where possible using CMDB tags and data classification labels
- Apply criticality tiers to vulnerability SLAs for risk-proportional remediation
- Validate scoring against actual incident impact data to calibrate the model
- Start with a simple 3-tier model before expanding to 5 tiers
Common Pitfalls
- Classifying all assets as "critical" which defeats the purpose of tiering
- Not updating criticality scores when systems are repurposed or decommissioned
- Using only technical factors without business context
- Applying uniform SLAs regardless of asset importance
- Not documenting the scoring methodology for audit and consistency
Related Skills
- performing-cve-prioritization-with-kev-catalog
- building-vulnerability-aging-and-sla-tracking
- performing-business-impact-analysis
- implementing-asset-management-program
1---2name: performing-asset-criticality-scoring-for-vulns-23description: Build a multi-factor asset criticality scoring model—incorporating data4 sensitivity, business function dependency, regulatory scope, network exposure, and5 recoverability—to produce a 1-5 criticality tier that weights vulnerability prioritization6 and remediation SLAs. Use when prioritizing vulnerability remediation by business7 impact or aligning CMDB asset data with risk-based patching timelines.8domain: cybersecurity9subdomain: vulnerability-management10tags:11- asset-criticality12- vulnerability-prioritization13- risk-management14- cmdb15- business-impact16- crown-jewels17- asset-classification18version: '1.0'19author: mahipal20license: Apache-2.021nist_csf:22- ID.RA-0123- ID.RA-0224- ID.IM-0225- ID.RA-0626mitre_attack:27- T119028- T120329- T106830metadata:31 source: https://skillmd.com/skills/26zl/performing-asset-criticality-scoring-for-vulns-232---3334# Performing Asset Criticality Scoring for Vulns3536## Overview37Asset criticality scoring assigns a business impact rating to each IT asset so that vulnerability remediation efforts focus on systems with the greatest organizational risk. Without criticality context, a CVSS 9.0 vulnerability on a test server receives the same urgency as the same vulnerability on a payment processing database. This skill covers building a multi-factor scoring model incorporating data sensitivity, business function dependency, regulatory scope, network exposure, and recoverability to create a 1-5 criticality tier that directly modifies vulnerability remediation SLAs.383940## When to Use4142- When conducting security assessments that involve performing asset criticality scoring for vulns43- When following incident response procedures for related security events44- When performing scheduled security testing or auditing activities45- When validating security controls through hands-on testing4647## Prerequisites48- Configuration Management Database (CMDB) or asset inventory49- Business Impact Analysis (BIA) data50- Data classification policy51- Network architecture documentation52- Stakeholder input from business unit owners5354## Core Concepts5556### Asset Criticality Scoring Model5758| Factor | Weight | Score Range | Description |59|--------|--------|-------------|-------------|60| Business Function Impact | 25% | 1-5 | How critical is the supported business process |61| Data Sensitivity | 25% | 1-5 | Type and sensitivity of data processed/stored |62| Regulatory Scope | 15% | 1-5 | Regulatory requirements (PCI, HIPAA, SOX) |63| Network Exposure | 15% | 1-5 | Internet-facing vs internal-only |64| Recoverability | 10% | 1-5 | RTO/RPO requirements, DR capability |65| User Population | 10% | 1-5 | Number of users/customers affected |6667### Criticality Tier Definitions6869| Tier | Score Range | Label | SLA Modifier | Examples |70|------|------------|-------|-------------|---------|71| 1 | 4.5-5.0 | Crown Jewels | -50% SLA | Domain controllers, payment systems, ERP |72| 2 | 3.5-4.4 | High Value | -25% SLA | Email servers, HR systems, CI/CD |73| 3 | 2.5-3.4 | Standard | Baseline SLA | Internal apps, file servers |74| 4 | 1.5-2.4 | Low Impact | +25% SLA | Test environments, printers |75| 5 | 1.0-1.4 | Minimal | +50% SLA | Decommissioning, isolated labs |7677### Data Sensitivity Scoring7879| Score | Classification | Examples |80|-------|---------------|---------|81| 5 | Restricted/Secret | PII, PHI, payment card data, trade secrets |82| 4 | Confidential | Financial reports, HR records, source code |83| 3 | Internal | Internal documents, policies, project files |84| 2 | Semi-public | Marketing materials, press releases (draft) |85| 1 | Public | Published content, public APIs |8687## Workflow8889### Step 1: Define Scoring Criteria9091```python92class AssetCriticalityScorer:93 """Multi-factor asset criticality scoring engine."""9495 WEIGHTS = {96 "business_function": 0.25,97 "data_sensitivity": 0.25,98 "regulatory_scope": 0.15,99 "network_exposure": 0.15,100 "recoverability": 0.10,101 "user_population": 0.10,102 }103104 TIER_THRESHOLDS = [105 (4.5, 1, "Crown Jewels", -0.50),106 (3.5, 2, "High Value", -0.25),107 (2.5, 3, "Standard", 0.00),108 (1.5, 4, "Low Impact", 0.25),109 (1.0, 5, "Minimal", 0.50),110 ]111112 def score_asset(self, asset):113 """Calculate criticality score for an asset."""114 weighted_score = sum(115 asset.get(factor, 3) * weight116 for factor, weight in self.WEIGHTS.items()117 )118 score = round(weighted_score, 2)119120 for threshold, tier, label, sla_mod in self.TIER_THRESHOLDS:121 if score >= threshold:122 return {123 "score": score,124 "tier": tier,125 "label": label,126 "sla_modifier": sla_mod,127 }128 return {"score": score, "tier": 5, "label": "Minimal", "sla_modifier": 0.50}129130 def adjust_vuln_sla(self, base_sla_days, asset_tier_data):131 """Adjust vulnerability SLA based on asset criticality."""132 modifier = asset_tier_data["sla_modifier"]133 adjusted = int(base_sla_days * (1 + modifier))134 return max(1, adjusted) # Minimum 1 day SLA135```136137### Step 2: Integrate with Vulnerability Prioritization138139```python140def apply_criticality_to_vulns(vulns_df, asset_scores):141 """Enrich vulnerability data with asset criticality context."""142 for idx, vuln in vulns_df.iterrows():143 asset_id = vuln.get("asset_id", "")144 asset_data = asset_scores.get(asset_id, {"tier": 3, "sla_modifier": 0})145146 vulns_df.at[idx, "asset_tier"] = asset_data["tier"]147 vulns_df.at[idx, "asset_label"] = asset_data.get("label", "Standard")148149 base_sla = get_base_sla(vuln["severity"])150 adjusted_sla = int(base_sla * (1 + asset_data["sla_modifier"]))151 vulns_df.at[idx, "adjusted_sla_days"] = max(1, adjusted_sla)152153 return vulns_df154```155156## Best Practices1571. Involve business stakeholders in criticality scoring; IT alone cannot assess business impact1582. Review and update criticality scores at least quarterly or when systems change roles1593. Automate scoring where possible using CMDB tags and data classification labels1604. Apply criticality tiers to vulnerability SLAs for risk-proportional remediation1615. Validate scoring against actual incident impact data to calibrate the model1626. Start with a simple 3-tier model before expanding to 5 tiers163164## Common Pitfalls165- Classifying all assets as "critical" which defeats the purpose of tiering166- Not updating criticality scores when systems are repurposed or decommissioned167- Using only technical factors without business context168- Applying uniform SLAs regardless of asset importance169- Not documenting the scoring methodology for audit and consistency170171## Related Skills172- performing-cve-prioritization-with-kev-catalog173- building-vulnerability-aging-and-sla-tracking174- performing-business-impact-analysis175- implementing-asset-management-program