[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMVHQC8EGC8BAKXFSSJRT9":3,"skill-same:01M7EMVHQC8EGC8BAKXFSSJRT9":80},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M7EMVHQC8EGC8BAKXFSSJRT9","implementing-vulnerability-sla-breach-alerting",null,"Build an automated SLA breach alerting system for vulnerability remediation, including a database schema for SLA tracking, breach detection logic, notification dispatch, a scheduled check runner, and a KPI\u002Fcompliance metrics dashboard. Use when implementing severity-based SLA timelines (critical\u002Fhigh\u002Fmedium\u002Flow), detecting and escalating SLA breaches, or building vulnerability remediation compliance reporting.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-vulnerability-sla-breach-alerting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-vulnerability-sla-breach-alerting\ndescription: Build an automated SLA breach alerting system for vulnerability remediation,\n  including a database schema for SLA tracking, breach detection logic, notification\n  dispatch, a scheduled check runner, and a KPI\u002Fcompliance metrics dashboard. Use\n  when implementing severity-based SLA timelines (critical\u002Fhigh\u002Fmedium\u002Flow), detecting\n  and escalating SLA breaches, or building vulnerability remediation compliance reporting.\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\n---\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":24,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":30,"description":7,"mitre_attack":40},[25,26,27,28,29,30,31],"vulnerability-sla","remediation-tracking","alerting","compliance","sla-breach","vulnerability-management","escalation","mahipal","cybersecurity","1.0",[36,37,38,39],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[41,42,43],"T1190","T1203","T1068","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fimplementing-vulnerability-sla-breach-alerting",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-vulnerability-sla-breach-alerting",{"tool":58,"command":59},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-vulnerability-sla-breach-alerting",{"tool":61,"command":62},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill implementing-vulnerability-sla-breach-alerting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-vulnerability-sla-breach-alerting\u002FSKILL.md",true,[66,72,76],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fapi-reference.md","REFERENCE","参考文档",5758,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-vulnerability-sla-breach-alerting\u002Freferences\u002Fapi-reference.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fstandards.md",2656,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-vulnerability-sla-breach-alerting\u002Freferences\u002Fstandards.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fworkflows.md",2532,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fimplementing-vulnerability-sla-breach-alerting\u002Freferences\u002Fworkflows.md",[81,90,95,102,109,116],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":91,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":89},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":89},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":89},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":89},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":89},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]