[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HMEXEF7DHPMG7WBAMM7NJG":3,"skill-same:01M6HMEXEF7DHPMG7WBAMM7NJG":120},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":6,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6HMEXEF7DHPMG7WBAMM7NJG","implementing-vulnerability-sla-breach-alerting",null,"Build automated alerting for vulnerability remediation SLA breaches with severity-based timelines, escalation workflows, and compliance reporting dashboards.","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-vulnerability-sla-breach-alerting\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"breach","alerting","implementing","sla","vulnerability","implementing vulnerability sla breach alerting","vulnerability-sla","for","with","id","build","tracking","cybersecurity","remediation","vulnerability-management","severity","escalation","compliance","reporting","workflows","2026-11-10 10:12:30",false,"---\nname: implementing-vulnerability-sla-breach-alerting\ndescription: Build automated alerting for vulnerability remediation SLA breaches with severity-based timelines, escalation workflows, and compliance reporting dashboards.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- vulnerability-sla\n- remediation-tracking\n- alerting\n- compliance\n- sla-breach\n- vulnerability-management\n- escalation\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- ID.RA-02\n- ID.IM-02\n- ID.RA-06\nmitre_attack:\n- T1190\n- T1203\n- T1068\ncategory: implementing-vulnerability-sla-breach-alerting\n---\n# Implementing Vulnerability SLA Breach Alerting\n\n## Overview\n\nVulnerability remediation SLAs define maximum timeframes for addressing security findings based on severity. This skill covers building an automated alerting system that tracks remediation timelines, detects SLA breaches, sends escalation notifications, and generates compliance reports. Industry-standard SLA targets are: Critical (24-48 hours), High (15-30 days), Medium (60 days), Low (90 days).\n\n\n## When to Use\n\n- When deploying or configuring implementing vulnerability sla breach alerting 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\n- Python 3.9+ with `requests`, `pandas`, `jinja2`, `smtplib` libraries\n- Vulnerability management platform with API access (DefectDojo, Qualys, Tenable)\n- SMTP server or webhook endpoint (Slack, Microsoft Teams, PagerDuty)\n- Database for SLA tracking (PostgreSQL or SQLite)\n\n## SLA Policy Definition\n\n### Standard SLA Tiers\n\n| Severity | Remediation SLA | Grace Period | Escalation Level |\n|----------|----------------|--------------|-----------------|\n| Critical (CVSS 9.0-10.0) | 48 hours | 12 hours | VP Engineering + CISO |\n| High (CVSS 7.0-8.9) | 15 days | 5 days | Director of Engineering |\n| Medium (CVSS 4.0-6.9) | 60 days | 14 days | Team Lead |\n| Low (CVSS 0.1-3.9) | 90 days | 30 days | Asset Owner |\n\n### SLA Configuration File\n\n```yaml\n# sla_policy.yaml\nsla_tiers:\n  critical:\n    cvss_min: 9.0\n    cvss_max: 10.0\n    remediation_days: 2\n    grace_period_days: 0.5\n    escalation_contacts:\n      - ciso@company.com\n      - vp-engineering@company.com\n    pagerduty_severity: critical\n  high:\n    cvss_min: 7.0\n    cvss_max: 8.9\n    remediation_days: 15\n    grace_period_days: 5\n    escalation_contacts:\n      - security-director@company.com\n    pagerduty_severity: high\n  medium:\n    cvss_min: 4.0\n    cvss_max: 6.9\n    remediation_days: 60\n    grace_period_days: 14\n    escalation_contacts:\n      - team-lead@company.com\n    pagerduty_severity: warning\n  low:\n    cvss_min: 0.1\n    cvss_max: 3.9\n    remediation_days: 90\n    grace_period_days: 30\n    escalation_contacts:\n      - asset-owner@company.com\n    pagerduty_severity: info\n\nnotification_channels:\n  slack:\n    webhook_url: \"${SLACK_WEBHOOK_URL}\"\n    channel: \"#vulnerability-alerts\"\n  email:\n    smtp_host: smtp.company.com\n    smtp_port: 587\n    from_address: vuln-alerts@company.com\n  pagerduty:\n    api_key: \"${PAGERDUTY_API_KEY}\"\n    service_id: \"${PAGERDUTY_SERVICE_ID}\"\n\nalert_schedules:\n  approaching_breach:\n    percentage_elapsed: 80\n    frequency_hours: 24\n  at_breach:\n    notification: immediate\n    escalation: true\n  post_breach:\n    frequency_hours: 12\n    escalation_increase: true\n```\n\n## Workflow\n\n### Step 1: Database Schema for SLA Tracking\n\n```sql\nCREATE TABLE vulnerability_sla (\n    id SERIAL PRIMARY KEY,\n    cve_id VARCHAR(20) NOT NULL,\n    finding_id VARCHAR(100) NOT NULL,\n    asset_hostname VARCHAR(255),\n    severity VARCHAR(20) NOT NULL,\n    cvss_score DECIMAL(3,1),\n    discovered_at TIMESTAMP NOT NULL,\n    sla_deadline TIMESTAMP NOT NULL,\n    remediated_at TIMESTAMP,\n    status VARCHAR(20) DEFAULT 'open',\n    owner_email VARCHAR(255),\n    escalation_level INTEGER DEFAULT 0,\n    last_alert_sent TIMESTAMP,\n    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP\n);\n\nCREATE INDEX idx_sla_status ON vulnerability_sla(status);\nCREATE INDEX idx_sla_deadline ON vulnerability_sla(sla_deadline);\nCREATE INDEX idx_sla_severity ON vulnerability_sla(severity);\n```\n\n### Step 2: SLA Breach Detection Logic\n\n```python\nfrom datetime import datetime, timedelta, timezone\nimport yaml\n\ndef load_sla_policy(policy_path=\"sla_policy.yaml\"):\n    with open(policy_path, \"r\") as f:\n        return yaml.safe_load(f)\n\ndef get_sla_tier(cvss_score, policy):\n    for tier_name, tier in policy[\"sla_tiers\"].items():\n        if tier[\"cvss_min\"] \u003C= cvss_score \u003C= tier[\"cvss_max\"]:\n            return tier_name, tier\n    return \"low\", policy[\"sla_tiers\"][\"low\"]\n\ndef calculate_sla_deadline(discovered_at, cvss_score, policy):\n    tier_name, tier = get_sla_tier(cvss_score, policy)\n    deadline = discovered_at + timedelta(days=tier[\"remediation_days\"])\n    return deadline, tier_name\n\ndef check_sla_status(discovered_at, sla_deadline, remediated_at=None):\n    now = datetime.now(timezone.utc)\n    if remediated_at:\n        if remediated_at \u003C= sla_deadline:\n            return \"remediated_within_sla\"\n        return \"remediated_breach\"\n    if now > sla_deadline:\n        overdue_days = (now - sla_deadline).days\n        return f\"breached_{overdue_days}d_overdue\"\n    remaining = sla_deadline - now\n    total_sla = sla_deadline - discovered_at\n    pct_elapsed = ((total_sla - remaining) \u002F total_sla) * 100\n    if pct_elapsed >= 80:\n        return \"approaching_breach\"\n    return \"within_sla\"\n```\n\n### Step 3: Notification Dispatch\n\n```python\nimport requests\nimport json\nimport smtplib\nfrom email.mime.text import MIMEText\nfrom email.mime.multipart import MIMEMultipart\n\ndef send_slack_alert(webhook_url, vuln_data, sla_status):\n    color = {\"breached\": \"#FF0000\", \"approaching_breach\": \"#FFA500\", \"within_sla\": \"#36A64F\"}\n    status_color = color.get(\"breached\" if \"breached\" in sla_status else sla_status, \"#808080\")\n    payload = {\n        \"attachments\": [{\n            \"color\": status_color,\n            \"title\": f\"Vulnerability SLA Alert: {vuln_data['cve_id']}\",\n            \"fields\": [\n                {\"title\": \"Severity\", \"value\": vuln_data[\"severity\"], \"short\": True},\n                {\"title\": \"CVSS\", \"value\": str(vuln_data[\"cvss_score\"]), \"short\": True},\n                {\"title\": \"Asset\", \"value\": vuln_data[\"asset_hostname\"], \"short\": True},\n                {\"title\": \"SLA Status\", \"value\": sla_status, \"short\": True},\n                {\"title\": \"Deadline\", \"value\": vuln_data[\"sla_deadline\"].strftime(\"%Y-%m-%d %H:%M UTC\"), \"short\": True},\n                {\"title\": \"Owner\", \"value\": vuln_data.get(\"owner_email\", \"Unassigned\"), \"short\": True},\n            ],\n        }]\n    }\n    requests.post(webhook_url, json=payload, timeout=10)\n\ndef send_pagerduty_alert(api_key, service_id, vuln_data, severity):\n    payload = {\n        \"routing_key\": api_key,\n        \"event_action\": \"trigger\",\n        \"payload\": {\n            \"summary\": f\"SLA Breach: {vuln_data['cve_id']} on {vuln_data['asset_hostname']}\",\n            \"severity\": severity,\n            \"source\": vuln_data[\"asset_hostname\"],\n            \"custom_details\": {\n                \"cve_id\": vuln_data[\"cve_id\"],\n                \"cvss_score\": vuln_data[\"cvss_score\"],\n                \"sla_deadline\": vuln_data[\"sla_deadline\"].isoformat(),\n            }\n        }\n    }\n    requests.post(\n        \"https:\u002F\u002Fevents.pagerduty.com\u002Fv2\u002Fenqueue\",\n        json=payload, timeout=10\n    )\n\ndef send_email_alert(smtp_config, to_addresses, vuln_data, sla_status):\n    msg = MIMEMultipart(\"alternative\")\n    msg[\"Subject\"] = f\"[SLA {sla_status.upper()}] {vuln_data['cve_id']} - {vuln_data['severity']}\"\n    msg[\"From\"] = smtp_config[\"from_address\"]\n    msg[\"To\"] = \", \".join(to_addresses)\n    body = f\"\"\"\n    Vulnerability SLA Alert\n\n    CVE: {vuln_data['cve_id']}\n    Severity: {vuln_data['severity']} (CVSS {vuln_data['cvss_score']})\n    Asset: {vuln_data['asset_hostname']}\n    SLA Deadline: {vuln_data['sla_deadline'].strftime('%Y-%m-%d %H:%M UTC')}\n    Status: {sla_status}\n    Owner: {vuln_data.get('owner_email', 'Unassigned')}\n\n    Please take immediate action to remediate this vulnerability.\n    \"\"\"\n    msg.attach(MIMEText(body, \"plain\"))\n    with smtplib.SMTP(smtp_config[\"smtp_host\"], smtp_config[\"smtp_port\"]) as server:\n        server.starttls()\n        server.send_message(msg)\n```\n\n### Step 4: Scheduled SLA Check Runner\n\n```bash\n# Run SLA breach check every hour via cron\necho \"0 * * * * cd \u002Fopt\u002Fvuln-sla && python3 scripts\u002Fprocess.py --check-sla\" | crontab -\n\n# Manual check\npython3 scripts\u002Fprocess.py --check-sla --policy sla_policy.yaml\n\n# Generate SLA compliance report\npython3 scripts\u002Fprocess.py --report --period monthly --output sla_report.html\n```\n\n## SLA Metrics Dashboard\n\n### Key Performance Indicators\n\n```python\ndef calculate_sla_metrics(db_connection, period_start, period_end):\n    metrics = {\n        \"total_findings\": 0,\n        \"remediated_within_sla\": 0,\n        \"sla_breach_count\": 0,\n        \"mean_time_to_remediate\": {},\n        \"sla_compliance_rate\": 0.0,\n        \"current_overdue\": 0,\n    }\n    # Query findings in period grouped by severity\n    query = \"\"\"\n        SELECT severity, COUNT(*) as total,\n               SUM(CASE WHEN remediated_at \u003C= sla_deadline THEN 1 ELSE 0 END) as within_sla,\n               AVG(EXTRACT(EPOCH FROM (COALESCE(remediated_at, NOW()) - discovered_at))\u002F86400) as avg_days\n        FROM vulnerability_sla\n        WHERE discovered_at BETWEEN %s AND %s\n        GROUP BY severity\n    \"\"\"\n    return metrics\n```\n\n## References\n\n- [Vulnerability Management SLAs Guide](https:\u002F\u002Fhostedscan.com\u002Fblog\u002Fvulnerability-management-slas-guide)\n- [NIST SP 800-40 Rev 4 - Patch Management](https:\u002F\u002Fcsrc.nist.gov\u002Fpublications\u002Fdetail\u002Fsp\u002F800-40\u002Frev-4\u002Ffinal)\n- [PagerDuty Events API v2](https:\u002F\u002Fdeveloper.pagerduty.com\u002Fapi-reference\u002Fa7d81b0e9200f-send-an-event-to-pager-duty)\n- [Slack Incoming Webhooks](https:\u002F\u002Fapi.slack.com\u002Fmessaging\u002Fwebhooks)\n","# Implementing Vulnerability SLA Breach Alerting\n\n## Overview\n\nVulnerability remediation SLAs define maximum timeframes for addressing security findings based on severity. This skill covers building an automated alerting system that tracks remediation timelines, detects SLA breaches, sends escalation notifications, and generates compliance reports. Industry-standard SLA targets are: Critical (24-48 hours), High (15-30 days), Medium (60 days), Low (90 days).\n\n\n## When to Use\n\n- When deploying or configuring implementing vulnerability sla breach alerting 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\n- Python 3.9+ with `requests`, `pandas`, `jinja2`, `smtplib` libraries\n- Vulnerability management platform with API access (DefectDojo, Qualys, Tenable)\n- SMTP server or webhook endpoint (Slack, Microsoft Teams, PagerDuty)\n- Database for SLA tracking (PostgreSQL or SQLite)\n\n## SLA Policy Definition\n\n### Standard SLA Tiers\n\n| Severity | Remediation SLA | Grace Period | Escalation Level |\n|----------|----------------|--------------|-----------------|\n| Critical (CVSS 9.0-10.0) | 48 hours | 12 hours | VP Engineering + CISO |\n| High (CVSS 7.0-8.9) | 15 days | 5 days | Director of Engineering |\n| Medium (CVSS 4.0-6.9) | 60 days | 14 days | Team Lead |\n| Low (CVSS 0.1-3.9) | 90 days | 30 days | Asset Owner |\n\n### SLA Configuration File\n\n```yaml\n# sla_policy.yaml\nsla_tiers:\n  critical:\n    cvss_min: 9.0\n    cvss_max: 10.0\n    remediation_days: 2\n    grace_period_days: 0.5\n    escalation_contacts:\n      - ciso@company.com\n      - vp-engineering@company.com\n    pagerduty_severity: critical\n  high:\n    cvss_min: 7.0\n    cvss_max: 8.9\n    remediation_days: 15\n    grace_period_days: 5\n    escalation_contacts:\n      - security-director@company.com\n    pagerduty_severity: high\n  medium:\n    cvss_min: 4.0\n    cvss_max: 6.9\n    remediation_days: 60\n    grace_period_days: 14\n    escalation_contacts:\n      - team-lead@company.com\n    pagerduty_severity: warning\n  low:\n    cvss_min: 0.1\n    cvss_max: 3.9\n    remediation_days: 90\n    grace_period_days: 30\n    escalation_contacts:\n      - asset-owner@company.com\n    pagerduty_severity: info\n\nnotification_channels:\n  slack:\n    webhook_url: \"${SLACK_WEBHOOK_URL}\"\n    channel: \"#vulnerability-alerts\"\n  email:\n    smtp_host: smtp.company.com\n    smtp_port: 587\n    from_address: vuln-alerts@company.com\n  pagerduty:\n    api_key: \"${PAGERDUTY_API_KEY}\"\n    service_id: \"${PAGERDUTY_SERVICE_ID}\"\n\nalert_schedules:\n  approaching_breach:\n    percentage_elapsed: 80\n    frequency_hours: 24\n  at_breach:\n    notification: immediate\n    escalation: true\n  post_breach:\n    frequency_hours: 12\n    escalation_increase: true\n```\n\n## Workflow\n\n### Step 1: Database Schema for SLA Tracking\n\n```sql\nCREATE TABLE vulnerability_sla (\n    id SERIAL PRIMARY KEY,\n    cve_id VARCHAR(20) NOT NULL,\n    finding_id VARCHAR(100) NOT NULL,\n    asset_hostname VARCHAR(255),\n    severity VARCHAR(20) NOT NULL,\n    cvss_score DECIMAL(3,1),\n    discovered_at TIMESTAMP NOT NULL,\n    sla_deadline TIMESTAMP NOT NULL,\n    remediated_at TIMESTAMP,\n    status VARCHAR(20) DEFAULT 'open',\n    owner_email VARCHAR(255),\n    escalation_level INTEGER DEFAULT 0,\n    last_alert_sent TIMESTAMP,\n    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP\n);\n\nCREATE INDEX idx_sla_status ON vulnerability_sla(status);\nCREATE INDEX idx_sla_deadline ON vulnerability_sla(sla_deadline);\nCREATE INDEX idx_sla_severity ON vulnerability_sla(severity);\n```\n\n### Step 2: SLA Breach Detection Logic\n\n```python\nfrom datetime import datetime, timedelta, timezone\nimport yaml\n\ndef load_sla_policy(policy_path=\"sla_policy.yaml\"):\n    with open(policy_path, \"r\") as f:\n        return yaml.safe_load(f)\n\ndef get_sla_tier(cvss_score, policy):\n    for tier_name, tier in policy[\"sla_tiers\"].items():\n        if tier[\"cvss_min\"] \u003C= cvss_score \u003C= tier[\"cvss_max\"]:\n            return tier_name, tier\n    return \"low\", policy[\"sla_tiers\"][\"low\"]\n\ndef calculate_sla_deadline(discovered_at, cvss_score, policy):\n    tier_name, tier = get_sla_tier(cvss_score, policy)\n    deadline = discovered_at + timedelta(days=tier[\"remediation_days\"])\n    return deadline, tier_name\n\ndef check_sla_status(discovered_at, sla_deadline, remediated_at=None):\n    now = datetime.now(timezone.utc)\n    if remediated_at:\n        if remediated_at \u003C= sla_deadline:\n            return \"remediated_within_sla\"\n        return \"remediated_breach\"\n    if now > sla_deadline:\n        overdue_days = (now - sla_deadline).days\n        return f\"breached_{overdue_days}d_overdue\"\n    remaining = sla_deadline - now\n    total_sla = sla_deadline - discovered_at\n    pct_elapsed = ((total_sla - remaining) \u002F total_sla) * 100\n    if pct_elapsed >= 80:\n        return \"approaching_breach\"\n    return \"within_sla\"\n```\n\n### Step 3: Notification Dispatch\n\n```python\nimport requests\nimport json\nimport smtplib\nfrom email.mime.text import MIMEText\nfrom email.mime.multipart import MIMEMultipart\n\ndef send_slack_alert(webhook_url, vuln_data, sla_status):\n    color = {\"breached\": \"#FF0000\", \"approaching_breach\": \"#FFA500\", \"within_sla\": \"#36A64F\"}\n    status_color = color.get(\"breached\" if \"breached\" in sla_status else sla_status, \"#808080\")\n    payload = {\n        \"attachments\": [{\n            \"color\": status_color,\n            \"title\": f\"Vulnerability SLA Alert: {vuln_data['cve_id']}\",\n            \"fields\": [\n                {\"title\": \"Severity\", \"value\": vuln_data[\"severity\"], \"short\": True},\n                {\"title\": \"CVSS\", \"value\": str(vuln_data[\"cvss_score\"]), \"short\": True},\n                {\"title\": \"Asset\", \"value\": vuln_data[\"asset_hostname\"], \"short\": True},\n                {\"title\": \"SLA Status\", \"value\": sla_status, \"short\": True},\n                {\"title\": \"Deadline\", \"value\": vuln_data[\"sla_deadline\"].strftime(\"%Y-%m-%d %H:%M UTC\"), \"short\": True},\n                {\"title\": \"Owner\", \"value\": vuln_data.get(\"owner_email\", \"Unassigned\"), \"short\": True},\n            ],\n        }]\n    }\n    requests.post(webhook_url, json=payload, timeout=10)\n\ndef send_pagerduty_alert(api_key, service_id, vuln_data, severity):\n    payload = {\n        \"routing_key\": api_key,\n        \"event_action\": \"trigger\",\n        \"payload\": {\n            \"summary\": f\"SLA Breach: {vuln_data['cve_id']} on {vuln_data['asset_hostname']}\",\n            \"severity\": severity,\n            \"source\": vuln_data[\"asset_hostname\"],\n            \"custom_details\": {\n                \"cve_id\": vuln_data[\"cve_id\"],\n                \"cvss_score\": vuln_data[\"cvss_score\"],\n                \"sla_deadline\": vuln_data[\"sla_deadline\"].isoformat(),\n            }\n        }\n    }\n    requests.post(\n        \"https:\u002F\u002Fevents.pagerduty.com\u002Fv2\u002Fenqueue\",\n        json=payload, timeout=10\n    )\n\ndef send_email_alert(smtp_config, to_addresses, vuln_data, sla_status):\n    msg = MIMEMultipart(\"alternative\")\n    msg[\"Subject\"] = f\"[SLA {sla_status.upper()}] {vuln_data['cve_id']} - {vuln_data['severity']}\"\n    msg[\"From\"] = smtp_config[\"from_address\"]\n    msg[\"To\"] = \", \".join(to_addresses)\n    body = f\"\"\"\n    Vulnerability SLA Alert\n\n    CVE: {vuln_data['cve_id']}\n    Severity: {vuln_data['severity']} (CVSS {vuln_data['cvss_score']})\n    Asset: {vuln_data['asset_hostname']}\n    SLA Deadline: {vuln_data['sla_deadline'].strftime('%Y-%m-%d %H:%M UTC')}\n    Status: {sla_status}\n    Owner: {vuln_data.get('owner_email', 'Unassigned')}\n\n    Please take immediate action to remediate this vulnerability.\n    \"\"\"\n    msg.attach(MIMEText(body, \"plain\"))\n    with smtplib.SMTP(smtp_config[\"smtp_host\"], smtp_config[\"smtp_port\"]) as server:\n        server.starttls()\n        server.send_message(msg)\n```\n\n### Step 4: Scheduled SLA Check Runner\n\n```bash\n# Run SLA breach check every hour via cron\necho \"0 * * * * cd \u002Fopt\u002Fvuln-sla && python3 scripts\u002Fprocess.py --check-sla\" | crontab -\n\n# Manual check\npython3 scripts\u002Fprocess.py --check-sla --policy sla_policy.yaml\n\n# Generate SLA compliance report\npython3 scripts\u002Fprocess.py --report --period monthly --output sla_report.html\n```\n\n## SLA Metrics Dashboard\n\n### Key Performance Indicators\n\n```python\ndef calculate_sla_metrics(db_connection, period_start, period_end):\n    metrics = {\n        \"total_findings\": 0,\n        \"remediated_within_sla\": 0,\n        \"sla_breach_count\": 0,\n        \"mean_time_to_remediate\": {},\n        \"sla_compliance_rate\": 0.0,\n        \"current_overdue\": 0,\n    }\n    # Query findings in period grouped by severity\n    query = \"\"\"\n        SELECT severity, COUNT(*) as total,\n               SUM(CASE WHEN remediated_at \u003C= sla_deadline THEN 1 ELSE 0 END) as within_sla,\n               AVG(EXTRACT(EPOCH FROM (COALESCE(remediated_at, NOW()) - discovered_at))\u002F86400) as avg_days\n        FROM vulnerability_sla\n        WHERE discovered_at BETWEEN %s AND %s\n        GROUP BY severity\n    \"\"\"\n    return metrics\n```\n\n## References\n\n- [Vulnerability Management SLAs Guide](https:\u002F\u002Fhostedscan.com\u002Fblog\u002Fvulnerability-management-slas-guide)\n- [NIST SP 800-40 Rev 4 - Patch Management](https:\u002F\u002Fcsrc.nist.gov\u002Fpublications\u002Fdetail\u002Fsp\u002F800-40\u002Frev-4\u002Ffinal)\n- [PagerDuty Events API v2](https:\u002F\u002Fdeveloper.pagerduty.com\u002Fapi-reference\u002Fa7d81b0e9200f-send-an-event-to-pager-duty)\n- [Slack Incoming Webhooks](https:\u002F\u002Fapi.slack.com\u002Fmessaging\u002Fwebhooks)\n",{"name":5,"tags":49,"author":52,"domain":36,"license":15,"version":53,"category":5,"nist_csf":54,"subdomain":38,"description":7,"mitre_attack":59},[30,50,25,41,51,38,40],"remediation-tracking","sla-breach","mahipal","1.0",[55,56,57,58],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[60,61,62],"T1190","T1203","T1068","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fimplementing-vulnerability-sla-breach-alerting",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill implementing-vulnerability-sla-breach-alerting",{"tool":77,"command":78},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill implementing-vulnerability-sla-breach-alerting",{"tool":80,"command":81},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill implementing-vulnerability-sla-breach-alerting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-vulnerability-sla-breach-alerting\u002FSKILL.md",true,[85,91,96,102,106,110,116],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Ftemplate.md","ASSET","资产文件",3236,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-vulnerability-sla-breach-alerting\u002Fassets\u002Ftemplate.md",{"path":92,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-vulnerability-sla-breach-alerting\u002FLICENSE",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fapi-reference.md","REFERENCE","参考文档",5758,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-vulnerability-sla-breach-alerting\u002Freferences\u002Fapi-reference.md",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fstandards.md",2656,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-vulnerability-sla-breach-alerting\u002Freferences\u002Fstandards.md",{"path":107,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fworkflows.md",2532,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-vulnerability-sla-breach-alerting\u002Freferences\u002Fworkflows.md",{"path":111,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":114,"sourceHtmlUrl":115},"scripts\u002Fagent.py","SCRIPT","脚本",9677,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-vulnerability-sla-breach-alerting\u002Fscripts\u002Fagent.py",{"path":117,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":118,"sourceHtmlUrl":119},"scripts\u002Fprocess.py",11675,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fimplementing-vulnerability-sla-breach-alerting\u002Fscripts\u002Fprocess.py",[121,151,173,196,211,232],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":132,"publishedAt":44},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[133,134,135,136,31,137,36,138,139,140,141,142,143,144,145,146,147,148,149,150],"integrity","backup","recovery","validating backup integrity for recovery","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":44},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[158,159,160,161,32,36,162,163,38,164,165,37,28,166,167,168,169,170,171,172],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","risk-management","cvss","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":44},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[180,181,148,36,182,183,184,144,145,185,186,187,188,189,190,191,192,193,194,195],"security","triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":44},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[180,203,204,181,148,32,36,205,183,141,206,39,144,145,207,186,168,208,209,210],"playbook","triaging security incident with ir playbook","teams","IR-playbook","classification","classify","incidents","initiate",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":217,"publishedAt":44},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[180,218,219,220,221,222,36,223,224,225,183,226,144,227,228,229,189,230,148,231],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review","cm","de",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":236,"categories":237,"keywords":238,"publishedAt":44},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[239,240,35,241,36,242,243,244,245,246,247,227,248,249,230,250,231,251,252,253],"infrastructure","tracking threat actor infrastructure","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]