[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GX2GC86YV7PRKZ2SP2D69F":3,"skill-same:01M6GX2GC86YV7PRKZ2SP2D69F":107},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6GX2GC86YV7PRKZ2SP2D69F","building-vulnerability-aging-and-sla-tracking",null,"Implement a vulnerability aging dashboard and SLA tracking system to measure remediation performance against severity-based timelines and drive accountability.","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-vulnerability-aging-and-sla-tracking\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"aging","sla tracking","tracking","vulnerability","sla","building vulnerability aging and sla tracking","remediation-metrics","system","risk","risk-management","aging-report","performance","sla-tracking","vulnerability-management","kpi","severity","compliance","dashboard","implement","cybersecurity","2026-11-10 10:12:30",false,"---\nname: building-vulnerability-aging-and-sla-tracking\ndescription: Implement a vulnerability aging dashboard and SLA tracking system to measure remediation performance against severity-based timelines and drive accountability.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags: [vulnerability-management, sla-tracking, remediation-metrics, aging-report, kpi, compliance, risk-management]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\n---\n# Building Vulnerability Aging and SLA Tracking\n\n## Overview\nWith over 30,000 new vulnerabilities identified in 2024 (a 17% increase from the prior year), organizations must track how long vulnerabilities remain unpatched and whether remediation occurs within defined Service Level Agreements (SLAs). Vulnerability aging measures the time between discovery and remediation, while SLA tracking enforces severity-based deadlines. Industry benchmarks indicate standard SLAs of 14 days for critical, 30 days for high, 60 days for medium, and 90 days for low vulnerabilities, though more aggressive timelines (24-48 hours for actively exploited critical CVEs) are increasingly common. This skill covers designing SLA policies, building aging dashboards, implementing automated escalations, and generating compliance metrics.\n\n\n## When to Use\n\n- When deploying or configuring building vulnerability aging and sla tracking capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Vulnerability management platform with historical scan data\n- Asset inventory with criticality ratings\n- ITSM\u002Fticketing system for remediation tracking\n- Reporting platform (Splunk, Elastic, Power BI, Grafana)\n- Stakeholder agreement on SLA timelines and escalation procedures\n\n## Core Concepts\n\n### Standard Vulnerability SLA Framework\n\n| Severity | CVSS Range | Standard SLA | Aggressive SLA | CISA KEV SLA |\n|----------|-----------|-------------|----------------|-------------|\n| Critical | 9.0-10.0 | 14 days | 48 hours | BOD 22-01 due date |\n| High | 7.0-8.9 | 30 days | 7 days | 14 days |\n| Medium | 4.0-6.9 | 60 days | 30 days | N\u002FA |\n| Low | 0.1-3.9 | 90 days | 60 days | N\u002FA |\n| Informational | 0.0 | Best effort | Best effort | N\u002FA |\n\n### Adaptive SLA Modifiers\n\n| Factor | Modifier | Rationale |\n|--------|----------|-----------|\n| Internet-facing asset | -50% SLA | Higher exposure risk |\n| CISA KEV listed | Override to 48h | Active exploitation confirmed |\n| EPSS > 0.7 | -50% SLA | High exploitation probability |\n| Tier 1 (crown jewel) asset | -25% SLA | Maximum business impact |\n| Compensating control in place | +25% SLA | Risk partially mitigated |\n| Vendor patch unavailable | Exception with review date | Cannot remediate yet |\n\n### Key Performance Indicators (KPIs)\n\n| KPI | Formula | Target |\n|-----|---------|--------|\n| Mean Time to Remediate (MTTR) | Avg(remediation_date - discovery_date) | \u003C 30 days overall |\n| SLA Compliance Rate | (Vulns remediated within SLA \u002F Total vulns) * 100 | >= 90% |\n| Overdue Vulnerability Count | Count where age > SLA | Trending downward |\n| Vulnerability Aging Distribution | Count by age bucket (0-14d, 15-30d, 31-60d, 60+d) | Majority in 0-30d |\n| Remediation Velocity | Vulns closed per week | Trending upward |\n| Exception Rate | (Exceptions \u002F Total vulns) * 100 | \u003C 5% |\n\n## Workflow\n\n### Step 1: Define SLA Policy Document\n\n```\nVulnerability Remediation SLA Policy v1.0\n\n1. Scope: All information systems and applications\n2. Severity Classification: Based on CVSS v4.0\u002Fv3.1 base score\n3. SLA Timelines: See Standard SLA Framework table\n4. Adaptive Modifiers: Applied based on asset context\n5. Exception Process:\n   - Must be documented with business justification\n   - Requires compensating control description\n   - Maximum extension: 90 days (one renewal)\n   - CISO approval required for Critical\u002FHigh exceptions\n6. Escalation Path:\n   - 50% SLA elapsed: Automated reminder to asset owner\n   - 75% SLA elapsed: Escalation to manager\n   - 100% SLA elapsed (overdue): CISO notification\n   - 120% SLA elapsed: VP\u002FCTO escalation\n7. Metrics Reporting: Monthly to security committee\n```\n\n### Step 2: Build the Aging Calculation Engine\n\n```python\nimport pandas as pd\nfrom datetime import datetime, timedelta\n\nclass VulnerabilityAgingTracker:\n    \"\"\"Track vulnerability aging and SLA compliance.\"\"\"\n\n    SLA_DAYS = {\n        \"Critical\": 14,\n        \"High\": 30,\n        \"Medium\": 60,\n        \"Low\": 90,\n    }\n\n    def __init__(self, sla_overrides=None):\n        if sla_overrides:\n            self.SLA_DAYS.update(sla_overrides)\n\n    def calculate_aging(self, vulns_df):\n        \"\"\"Calculate aging metrics for each vulnerability.\"\"\"\n        today = datetime.now()\n\n        vulns_df[\"discovery_date\"] = pd.to_datetime(vulns_df[\"discovery_date\"])\n        vulns_df[\"remediation_date\"] = pd.to_datetime(\n            vulns_df[\"remediation_date\"], errors=\"coerce\"\n        )\n\n        vulns_df[\"age_days\"] = vulns_df.apply(\n            lambda row: (row[\"remediation_date\"] - row[\"discovery_date\"]).days\n            if pd.notna(row[\"remediation_date\"])\n            else (today - row[\"discovery_date\"]).days,\n            axis=1\n        )\n\n        vulns_df[\"sla_days\"] = vulns_df[\"severity\"].map(self.SLA_DAYS)\n        vulns_df[\"sla_deadline\"] = vulns_df[\"discovery_date\"] + \\\n            pd.to_timedelta(vulns_df[\"sla_days\"], unit=\"D\")\n\n        vulns_df[\"is_overdue\"] = vulns_df.apply(\n            lambda row: row[\"age_days\"] > row[\"sla_days\"]\n            if pd.isna(row[\"remediation_date\"]) else False,\n            axis=1\n        )\n\n        vulns_df[\"sla_compliance\"] = vulns_df.apply(\n            lambda row: row[\"age_days\"] \u003C= row[\"sla_days\"]\n            if pd.notna(row[\"remediation_date\"]) else None,\n            axis=1\n        )\n\n        vulns_df[\"days_overdue\"] = vulns_df.apply(\n            lambda row: max(0, row[\"age_days\"] - row[\"sla_days\"])\n            if row[\"is_overdue\"] else 0,\n            axis=1\n        )\n\n        vulns_df[\"sla_pct_elapsed\"] = (\n            vulns_df[\"age_days\"] \u002F vulns_df[\"sla_days\"] * 100\n        ).round(1)\n\n        return vulns_df\n\n    def generate_kpis(self, vulns_df):\n        \"\"\"Generate KPI summary from aging data.\"\"\"\n        open_vulns = vulns_df[vulns_df[\"remediation_date\"].isna()]\n        closed_vulns = vulns_df[vulns_df[\"remediation_date\"].notna()]\n\n        kpis = {\n            \"total_vulnerabilities\": len(vulns_df),\n            \"open_vulnerabilities\": len(open_vulns),\n            \"closed_vulnerabilities\": len(closed_vulns),\n            \"overdue_count\": open_vulns[\"is_overdue\"].sum(),\n            \"mttr_days\": closed_vulns[\"age_days\"].mean() if len(closed_vulns) > 0 else 0,\n            \"sla_compliance_rate\": (\n                closed_vulns[\"sla_compliance\"].mean() * 100\n                if len(closed_vulns) > 0 else 0\n            ),\n        }\n\n        kpis[\"overdue_by_severity\"] = (\n            open_vulns[open_vulns[\"is_overdue\"]]\n            .groupby(\"severity\")\n            .size()\n            .to_dict()\n        )\n\n        return kpis\n\n    def get_escalation_list(self, vulns_df):\n        \"\"\"Get vulnerabilities requiring escalation.\"\"\"\n        open_vulns = vulns_df[vulns_df[\"remediation_date\"].isna()].copy()\n\n        escalations = []\n        for _, vuln in open_vulns.iterrows():\n            pct = vuln[\"sla_pct_elapsed\"]\n            if pct >= 120:\n                level = \"VP\u002FCTO Escalation\"\n            elif pct >= 100:\n                level = \"CISO Notification\"\n            elif pct >= 75:\n                level = \"Manager Escalation\"\n            elif pct >= 50:\n                level = \"Owner Reminder\"\n            else:\n                continue\n\n            escalations.append({\n                \"cve_id\": vuln.get(\"cve_id\", \"\"),\n                \"severity\": vuln[\"severity\"],\n                \"age_days\": vuln[\"age_days\"],\n                \"sla_days\": vuln[\"sla_days\"],\n                \"days_overdue\": vuln[\"days_overdue\"],\n                \"sla_pct\": pct,\n                \"escalation_level\": level,\n                \"asset\": vuln.get(\"asset\", \"\"),\n                \"owner\": vuln.get(\"owner\", \"\"),\n            })\n\n        return pd.DataFrame(escalations)\n```\n\n### Step 3: Dashboard Visualization\n\n```python\n# Grafana\u002FKibana query examples for vulnerability aging\n\n# Age distribution histogram (Elasticsearch)\nage_distribution_query = {\n    \"aggs\": {\n        \"age_buckets\": {\n            \"range\": {\n                \"field\": \"age_days\",\n                \"ranges\": [\n                    {\"key\": \"0-7 days\", \"to\": 8},\n                    {\"key\": \"8-14 days\", \"from\": 8, \"to\": 15},\n                    {\"key\": \"15-30 days\", \"from\": 15, \"to\": 31},\n                    {\"key\": \"31-60 days\", \"from\": 31, \"to\": 61},\n                    {\"key\": \"61-90 days\", \"from\": 61, \"to\": 91},\n                    {\"key\": \"90+ days\", \"from\": 91},\n                ]\n            }\n        }\n    }\n}\n\n# SLA compliance trend (monthly)\nsla_trend_query = {\n    \"aggs\": {\n        \"monthly\": {\n            \"date_histogram\": {\"field\": \"remediation_date\", \"interval\": \"month\"},\n            \"aggs\": {\n                \"within_sla\": {\n                    \"filter\": {\"script\": {\n                        \"source\": \"doc['age_days'].value \u003C= doc['sla_days'].value\"\n                    }}\n                }\n            }\n        }\n    }\n}\n```\n\n## Best Practices\n1. Start with achievable SLA targets and tighten them as processes mature\n2. Adapt SLAs based on asset criticality and threat context, not just CVSS scores\n3. Automate escalation notifications to reduce manual tracking overhead\n4. Track MTTR trends month-over-month to demonstrate improvement\n5. Build exception workflows that require documented compensating controls\n6. Report SLA compliance to executive leadership monthly for accountability\n7. Include aging metrics in security committee and board-level reporting\n8. Integrate SLA tracking with ITSM ticketing for end-to-end remediation visibility\n\n## Common Pitfalls\n- Setting unrealistic SLA targets that teams cannot meet, causing SLA fatigue\n- Not adapting SLAs for asset criticality, treating all systems equally\n- Lacking exception processes, forcing teams to either ignore SLAs or request blanket waivers\n- Measuring only open vulnerability count without considering age and SLA compliance\n- Not tracking the SLA clock from discovery date (using report date instead)\n- Failing to re-baseline SLAs as team maturity improves\n\n## Related Skills\n- implementing-vulnerability-remediation-sla\n- building-executive-vulnerability-risk-report\n- implementing-security-metrics-and-kpis\n- performing-remediation-validation-scanning\n","# Building Vulnerability Aging and SLA Tracking\n\n## Overview\nWith over 30,000 new vulnerabilities identified in 2024 (a 17% increase from the prior year), organizations must track how long vulnerabilities remain unpatched and whether remediation occurs within defined Service Level Agreements (SLAs). Vulnerability aging measures the time between discovery and remediation, while SLA tracking enforces severity-based deadlines. Industry benchmarks indicate standard SLAs of 14 days for critical, 30 days for high, 60 days for medium, and 90 days for low vulnerabilities, though more aggressive timelines (24-48 hours for actively exploited critical CVEs) are increasingly common. This skill covers designing SLA policies, building aging dashboards, implementing automated escalations, and generating compliance metrics.\n\n\n## When to Use\n\n- When deploying or configuring building vulnerability aging and sla tracking capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Vulnerability management platform with historical scan data\n- Asset inventory with criticality ratings\n- ITSM\u002Fticketing system for remediation tracking\n- Reporting platform (Splunk, Elastic, Power BI, Grafana)\n- Stakeholder agreement on SLA timelines and escalation procedures\n\n## Core Concepts\n\n### Standard Vulnerability SLA Framework\n\n| Severity | CVSS Range | Standard SLA | Aggressive SLA | CISA KEV SLA |\n|----------|-----------|-------------|----------------|-------------|\n| Critical | 9.0-10.0 | 14 days | 48 hours | BOD 22-01 due date |\n| High | 7.0-8.9 | 30 days | 7 days | 14 days |\n| Medium | 4.0-6.9 | 60 days | 30 days | N\u002FA |\n| Low | 0.1-3.9 | 90 days | 60 days | N\u002FA |\n| Informational | 0.0 | Best effort | Best effort | N\u002FA |\n\n### Adaptive SLA Modifiers\n\n| Factor | Modifier | Rationale |\n|--------|----------|-----------|\n| Internet-facing asset | -50% SLA | Higher exposure risk |\n| CISA KEV listed | Override to 48h | Active exploitation confirmed |\n| EPSS > 0.7 | -50% SLA | High exploitation probability |\n| Tier 1 (crown jewel) asset | -25% SLA | Maximum business impact |\n| Compensating control in place | +25% SLA | Risk partially mitigated |\n| Vendor patch unavailable | Exception with review date | Cannot remediate yet |\n\n### Key Performance Indicators (KPIs)\n\n| KPI | Formula | Target |\n|-----|---------|--------|\n| Mean Time to Remediate (MTTR) | Avg(remediation_date - discovery_date) | \u003C 30 days overall |\n| SLA Compliance Rate | (Vulns remediated within SLA \u002F Total vulns) * 100 | >= 90% |\n| Overdue Vulnerability Count | Count where age > SLA | Trending downward |\n| Vulnerability Aging Distribution | Count by age bucket (0-14d, 15-30d, 31-60d, 60+d) | Majority in 0-30d |\n| Remediation Velocity | Vulns closed per week | Trending upward |\n| Exception Rate | (Exceptions \u002F Total vulns) * 100 | \u003C 5% |\n\n## Workflow\n\n### Step 1: Define SLA Policy Document\n\n```\nVulnerability Remediation SLA Policy v1.0\n\n1. Scope: All information systems and applications\n2. Severity Classification: Based on CVSS v4.0\u002Fv3.1 base score\n3. SLA Timelines: See Standard SLA Framework table\n4. Adaptive Modifiers: Applied based on asset context\n5. Exception Process:\n   - Must be documented with business justification\n   - Requires compensating control description\n   - Maximum extension: 90 days (one renewal)\n   - CISO approval required for Critical\u002FHigh exceptions\n6. Escalation Path:\n   - 50% SLA elapsed: Automated reminder to asset owner\n   - 75% SLA elapsed: Escalation to manager\n   - 100% SLA elapsed (overdue): CISO notification\n   - 120% SLA elapsed: VP\u002FCTO escalation\n7. Metrics Reporting: Monthly to security committee\n```\n\n### Step 2: Build the Aging Calculation Engine\n\n```python\nimport pandas as pd\nfrom datetime import datetime, timedelta\n\nclass VulnerabilityAgingTracker:\n    \"\"\"Track vulnerability aging and SLA compliance.\"\"\"\n\n    SLA_DAYS = {\n        \"Critical\": 14,\n        \"High\": 30,\n        \"Medium\": 60,\n        \"Low\": 90,\n    }\n\n    def __init__(self, sla_overrides=None):\n        if sla_overrides:\n            self.SLA_DAYS.update(sla_overrides)\n\n    def calculate_aging(self, vulns_df):\n        \"\"\"Calculate aging metrics for each vulnerability.\"\"\"\n        today = datetime.now()\n\n        vulns_df[\"discovery_date\"] = pd.to_datetime(vulns_df[\"discovery_date\"])\n        vulns_df[\"remediation_date\"] = pd.to_datetime(\n            vulns_df[\"remediation_date\"], errors=\"coerce\"\n        )\n\n        vulns_df[\"age_days\"] = vulns_df.apply(\n            lambda row: (row[\"remediation_date\"] - row[\"discovery_date\"]).days\n            if pd.notna(row[\"remediation_date\"])\n            else (today - row[\"discovery_date\"]).days,\n            axis=1\n        )\n\n        vulns_df[\"sla_days\"] = vulns_df[\"severity\"].map(self.SLA_DAYS)\n        vulns_df[\"sla_deadline\"] = vulns_df[\"discovery_date\"] + \\\n            pd.to_timedelta(vulns_df[\"sla_days\"], unit=\"D\")\n\n        vulns_df[\"is_overdue\"] = vulns_df.apply(\n            lambda row: row[\"age_days\"] > row[\"sla_days\"]\n            if pd.isna(row[\"remediation_date\"]) else False,\n            axis=1\n        )\n\n        vulns_df[\"sla_compliance\"] = vulns_df.apply(\n            lambda row: row[\"age_days\"] \u003C= row[\"sla_days\"]\n            if pd.notna(row[\"remediation_date\"]) else None,\n            axis=1\n        )\n\n        vulns_df[\"days_overdue\"] = vulns_df.apply(\n            lambda row: max(0, row[\"age_days\"] - row[\"sla_days\"])\n            if row[\"is_overdue\"] else 0,\n            axis=1\n        )\n\n        vulns_df[\"sla_pct_elapsed\"] = (\n            vulns_df[\"age_days\"] \u002F vulns_df[\"sla_days\"] * 100\n        ).round(1)\n\n        return vulns_df\n\n    def generate_kpis(self, vulns_df):\n        \"\"\"Generate KPI summary from aging data.\"\"\"\n        open_vulns = vulns_df[vulns_df[\"remediation_date\"].isna()]\n        closed_vulns = vulns_df[vulns_df[\"remediation_date\"].notna()]\n\n        kpis = {\n            \"total_vulnerabilities\": len(vulns_df),\n            \"open_vulnerabilities\": len(open_vulns),\n            \"closed_vulnerabilities\": len(closed_vulns),\n            \"overdue_count\": open_vulns[\"is_overdue\"].sum(),\n            \"mttr_days\": closed_vulns[\"age_days\"].mean() if len(closed_vulns) > 0 else 0,\n            \"sla_compliance_rate\": (\n                closed_vulns[\"sla_compliance\"].mean() * 100\n                if len(closed_vulns) > 0 else 0\n            ),\n        }\n\n        kpis[\"overdue_by_severity\"] = (\n            open_vulns[open_vulns[\"is_overdue\"]]\n            .groupby(\"severity\")\n            .size()\n            .to_dict()\n        )\n\n        return kpis\n\n    def get_escalation_list(self, vulns_df):\n        \"\"\"Get vulnerabilities requiring escalation.\"\"\"\n        open_vulns = vulns_df[vulns_df[\"remediation_date\"].isna()].copy()\n\n        escalations = []\n        for _, vuln in open_vulns.iterrows():\n            pct = vuln[\"sla_pct_elapsed\"]\n            if pct >= 120:\n                level = \"VP\u002FCTO Escalation\"\n            elif pct >= 100:\n                level = \"CISO Notification\"\n            elif pct >= 75:\n                level = \"Manager Escalation\"\n            elif pct >= 50:\n                level = \"Owner Reminder\"\n            else:\n                continue\n\n            escalations.append({\n                \"cve_id\": vuln.get(\"cve_id\", \"\"),\n                \"severity\": vuln[\"severity\"],\n                \"age_days\": vuln[\"age_days\"],\n                \"sla_days\": vuln[\"sla_days\"],\n                \"days_overdue\": vuln[\"days_overdue\"],\n                \"sla_pct\": pct,\n                \"escalation_level\": level,\n                \"asset\": vuln.get(\"asset\", \"\"),\n                \"owner\": vuln.get(\"owner\", \"\"),\n            })\n\n        return pd.DataFrame(escalations)\n```\n\n### Step 3: Dashboard Visualization\n\n```python\n# Grafana\u002FKibana query examples for vulnerability aging\n\n# Age distribution histogram (Elasticsearch)\nage_distribution_query = {\n    \"aggs\": {\n        \"age_buckets\": {\n            \"range\": {\n                \"field\": \"age_days\",\n                \"ranges\": [\n                    {\"key\": \"0-7 days\", \"to\": 8},\n                    {\"key\": \"8-14 days\", \"from\": 8, \"to\": 15},\n                    {\"key\": \"15-30 days\", \"from\": 15, \"to\": 31},\n                    {\"key\": \"31-60 days\", \"from\": 31, \"to\": 61},\n                    {\"key\": \"61-90 days\", \"from\": 61, \"to\": 91},\n                    {\"key\": \"90+ days\", \"from\": 91},\n                ]\n            }\n        }\n    }\n}\n\n# SLA compliance trend (monthly)\nsla_trend_query = {\n    \"aggs\": {\n        \"monthly\": {\n            \"date_histogram\": {\"field\": \"remediation_date\", \"interval\": \"month\"},\n            \"aggs\": {\n                \"within_sla\": {\n                    \"filter\": {\"script\": {\n                        \"source\": \"doc['age_days'].value \u003C= doc['sla_days'].value\"\n                    }}\n                }\n            }\n        }\n    }\n}\n```\n\n## Best Practices\n1. Start with achievable SLA targets and tighten them as processes mature\n2. Adapt SLAs based on asset criticality and threat context, not just CVSS scores\n3. Automate escalation notifications to reduce manual tracking overhead\n4. Track MTTR trends month-over-month to demonstrate improvement\n5. Build exception workflows that require documented compensating controls\n6. Report SLA compliance to executive leadership monthly for accountability\n7. Include aging metrics in security committee and board-level reporting\n8. Integrate SLA tracking with ITSM ticketing for end-to-end remediation visibility\n\n## Common Pitfalls\n- Setting unrealistic SLA targets that teams cannot meet, causing SLA fatigue\n- Not adapting SLAs for asset criticality, treating all systems equally\n- Lacking exception processes, forcing teams to either ignore SLAs or request blanket waivers\n- Measuring only open vulnerability count without considering age and SLA compliance\n- Not tracking the SLA clock from discovery date (using report date instead)\n- Failing to re-baseline SLAs as team maturity improves\n\n## Related Skills\n- implementing-vulnerability-remediation-sla\n- building-executive-vulnerability-risk-report\n- implementing-security-metrics-and-kpis\n- performing-remediation-validation-scanning\n",{"name":5,"tags":48,"author":49,"domain":42,"license":14,"version":50,"subdomain":36,"description":7},[36,35,29,33,37,39,32],"mahipal","1.0","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-vulnerability-aging-and-sla-tracking",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add micsapp\u002Fmicstec-skills --skill building-vulnerability-aging-and-sla-tracking",{"tool":64,"command":65},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill building-vulnerability-aging-and-sla-tracking",{"tool":67,"command":68},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill building-vulnerability-aging-and-sla-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-vulnerability-aging-and-sla-tracking\u002FSKILL.md",true,[72,78,83,89,93,97,103],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Ftemplate.md","ASSET","资产文件",1158,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-vulnerability-aging-and-sla-tracking\u002Fassets\u002Ftemplate.md",{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-vulnerability-aging-and-sla-tracking\u002FLICENSE",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fapi-reference.md","REFERENCE","参考文档",1400,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-vulnerability-aging-and-sla-tracking\u002Freferences\u002Fapi-reference.md",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fstandards.md",1379,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-vulnerability-aging-and-sla-tracking\u002Freferences\u002Fstandards.md",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fworkflows.md",1821,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-vulnerability-aging-and-sla-tracking\u002Freferences\u002Fworkflows.md",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Fagent.py","SCRIPT","脚本",7133,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-vulnerability-aging-and-sla-tracking\u002Fscripts\u002Fagent.py",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fprocess.py",5810,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002F_universal\u002Fcybersecurity-skills\u002Fskills\u002Fbuilding-vulnerability-aging-and-sla-tracking\u002Fscripts\u002Fprocess.py",[108,144,174,195,215,240],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":123,"publishedAt":43},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[115,118],{"categoryNo":116,"categoryName":117,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":158,"publishedAt":43},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[150,151,154,157],{"categoryNo":116,"categoryName":117,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":152,"categoryName":153,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":155,"categoryName":156,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},[159,160,161,162,125,163,164,165,166,167,168,169,133,134,140,170,171,141,172,173],"deployment","apiops deployment","workflows","azure devops","infrastructure","code","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":181,"publishedAt":43},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[180],{"categoryNo":116,"categoryName":117,"taxonomyType":20,"taxonomyTypeDesc":21},[182,183,184,185,125,128,133,134,186,187,188,189,190,191,192,141,193,194,173,143],"policy","authoring","apim policy authoring","security","access","use","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":203,"publishedAt":43},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[201,202],{"categoryNo":116,"categoryName":117,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},[204,185,205,133,189,206,125,159,207,208,209,210,134,211,141,212,213,214,142,143],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"publishedAt":43},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[222,223,224,161,225,226,227,228,133,229,230,231,232,233,234,235,236,237,238,239],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":241,"name":242,"nameZh":6,"description":243,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":112,"licenseFileUrl":6,"sourceHtmlUrl":244,"categories":245,"keywords":246,"publishedAt":43},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[242,247,248,249,250,251,252,187,253,254],"npm","js","calculate","node","math","user","compute","errors"]