[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71GJSJ0SE8EJ46PQ3479KAA":3,"skill-same:01M71GJSJ0SE8EJ46PQ3479KAA":109},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M71GJSJ0SE8EJ46PQ3479KAA","slaalerts-SKILL.md",null,">\n  Build automated alerting for vulnerability remediation SLA breaches with severity-based timelines, escalation workflows, and compliance reporting dashboards.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"slaalerts SKILL md","skill md","escalation","severity","sla","for","workflows","alerting","vulnerability","with","build","compliance","remediation","reporting","dashboards","2026-11-10 10:12:30",false,"---\nname: slaalerts-SKILL.md\ndescription: \">\\n  Build automated alerting for vulnerability remediation SLA breaches\\\n  \\ with severity-based timelines, escalation workflows, and compliance reporting\\\n  \\ dashboards.\"\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\n\n---\n\n## CyberSecSuite Integration\n\n```bash\n# Open a case before starting investigation\nmcp__cybersec__case_open --title \"slaalerts\" --type investigation\n\n# Persist findings to PostgreSQL\nmcp__cybersec__add_finding --title \"...\" --severity high --description \"...\"\n\n# Log IOCs\nmcp__cybersec__add_ioc --type domain --value \"...\" --confidence 0.9\n\n# Map to MITRE\nmcp__cybersec__suggest_mitre --description \"...\"\n```\n\n**Agent:** `@cybersec-agent` → delegates to appropriate specialist\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\n\n---\n\n## CyberSecSuite Integration\n\n```bash\n# Open a case before starting investigation\nmcp__cybersec__case_open --title \"slaalerts\" --type investigation\n\n# Persist findings to PostgreSQL\nmcp__cybersec__add_finding --title \"...\" --severity high --description \"...\"\n\n# Log IOCs\nmcp__cybersec__add_ioc --type domain --value \"...\" --confidence 0.9\n\n# Map to MITRE\nmcp__cybersec__suggest_mitre --description \"...\"\n```\n\n**Agent:** `@cybersec-agent` → delegates to appropriate specialist\n",{"name":5,"description":7},"main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill slaalerts-SKILL.md",{"tool":57,"command":58},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill slaalerts-SKILL.md",{"tool":60,"command":61},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill slaalerts-SKILL.md","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002FSKILL.md",true,[65,71,75,81,85,88,92,96,102,105],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"assets\u002Findex.json","ASSET","资产文件",84,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002Fassets\u002Findex.json",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"assets\u002Ftemplate.md",3236,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002Fassets\u002Ftemplate.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"index.json","REFERENCE","参考文档",1501,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002Findex.json",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fapi-reference.md",5758,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002Freferences\u002Fapi-reference.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":69,"sourceHtmlUrl":87},"references\u002Findex.json","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002Freferences\u002Findex.json",{"path":89,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fstandards.md",2656,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002Freferences\u002Fstandards.md",{"path":93,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fworkflows.md",2532,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002Freferences\u002Fworkflows.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fagent.py","SCRIPT","脚本",9677,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002Fscripts\u002Fagent.py",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":69,"sourceHtmlUrl":104},"scripts\u002Findex.json","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002Fscripts\u002Findex.json",{"path":106,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fprocess.py",11675,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fvulnerabilities\u002Fmanagement\u002Fslaalerts\u002Fscripts\u002Fprocess.py",[110,136,159,181,202,218],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":39},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135],"services","detect","services wmi persistence detect","wmi","persistence","de","cm","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","cybersecurity","process-forensics",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":39},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[143,117,144,120,145,146,147,134,148,149,150,151,152,153,122,154,155,156,157,158],"exploit","services wmi exec exploit","exec","remote","traffic","Bash","analysis","team","across","crackmapexec","native","command","lateral movement","read","lateral-movement","Impacket",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":39},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[166,167,168,169,170,171,134,148,172,149,173,174,122,156,175,176,177,178,179,180],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper","sonnet",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":39},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[118,188,189,190,191,192,26,123,193,134,135,194,195,196,197,198,199,200,201,122],"processes token impersonate detect","token","processes","attacks","windows","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":39},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[209,210,118,211,190,192,212,123,213,193,134,135,149,214,215,216,217,201,122,124],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":224,"publishedAt":39},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[225,118,190,226,212,123,227,228,134,135,229,230,231,232,233,33,122,124,234,235],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","mismatched","headers"]