Skip to content
Skillpedia
Misc35k · #6023

performing-asset-criticality-scoring-for-vulns

Allows your agent to create an asset criticality scoring model to prioritize vulnerabilities.

What it does

This tool helps rank the importance of your computer systems. It assigns a score from 1 to 5 to each system, considering how sensitive the data it holds is, how crucial it is for business operations, and other factors. This helps decide which systems need more attention when security issues arise.

When to use it

  • ✓When deciding which security vulnerabilities to fix first.
  • ✓When organizing which systems need faster updates.
  • ✓When understanding the risk each system poses to the company.

Example of what to ask your AI

“Classify the importance of our systems, considering the payment system is the most critical and test servers are the least important.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/main/skills/performing-asset-criticality-scoring-for-vulns/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/main/skills/performing-asset-criticality-scoring-for-vulns/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool analyzes various aspects of each system, such as the type of information it stores and its importance for daily business. Based on this, it calculates an overall score and defines a criticality tier (from 1 to 5), which helps set deadlines for fixing security problems.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-asset-criticality-scoring-for-vulns

Or download just the file:

curl -L https://raw.githubusercontent.com/mukul975/Anthropic-Cybersecurity-Skills/main/skills/performing-asset-criticality-scoring-for-vulns/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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."""

…
FAQ

Why is it important to classify system criticality?

It helps focus security efforts on the most important systems, ensuring the most severe issues are addressed first and protecting the company's most sensitive data.

What information is used to classify criticality?

Information such as data sensitivity (e.g., personal, financial data), business function dependency, network exposure, and recoverability are used.

What does 'SLA Modifier' mean?

It's an adjustment to the deadline (SLA - Service Level Agreement) for fixing security issues. More critical systems will have shorter deadlines for fixes, while less critical systems may have longer ones.

Details

Original description by the author

Build a multi-factor asset criticality scoring model—incorporating data sensitivity, business function dependency, regulatory scope, network exposure, and recoverability—to produce a 1-5 criticality tier that weights vulnerability prioritization and remediation SLAs. Use when prioritizing vulnerability remediation by business impact or aligning CMDB asset data with risk-based patching timelines.

repo: mukul975/Anthropic-Cybersecurity-Skills

Popularity

GitHub stars
35k
Ranking position
#6023
License
Apache-2.0
Updated
8/31/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills