[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M734P6DEDSS7ETMD4DPAFRVW":3,"skill-same:01M734P6DEDSS7ETMD4DPAFRVW":106},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M734P6DEDSS7ETMD4DPAFRVW","implementing-vulnerability-sla-breach-alerting",null,"Build automated alerting for vulnerability remediation SLA breaches with severity-based timelines, escalation workflows, and compliance reporting dashboards.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-vulnerability-sla-breach-alerting\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-vulnerability-sla-breach-alerting\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: implementing-vulnerability-sla-breach-alerting\ndescription: Build automated alerting for vulnerability remediation SLA breaches with\n  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\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\nnote: \"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.\"\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,"note":25,"tags":26,"author":34,"domain":35,"source":36,"license":15,"version":37,"nist_csf":38,"subdomain":32,"description":7,"mitre_attack":43,"source_commit":47},"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.",[27,28,29,30,31,32,33],"vulnerability-sla","remediation-tracking","alerting","compliance","sla-breach","vulnerability-management","escalation","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[39,40,41,42],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[44,45,46],"T1190","T1203","T1068","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fimplementing-vulnerability-sla-breach-alerting",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill implementing-vulnerability-sla-breach-alerting",{"tool":64,"command":65},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill implementing-vulnerability-sla-breach-alerting",{"tool":67,"command":68},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill implementing-vulnerability-sla-breach-alerting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-vulnerability-sla-breach-alerting\u002FSKILL.md",true,[72,78,82,88,92,96,102],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Ftemplate.md","ASSET","资产文件",3236,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-vulnerability-sla-breach-alerting\u002Fassets\u002Ftemplate.md",{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fapi-reference.md","REFERENCE","参考文档",5758,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-vulnerability-sla-breach-alerting\u002Freferences\u002Fapi-reference.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fstandards.md",2656,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-vulnerability-sla-breach-alerting\u002Freferences\u002Fstandards.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fworkflows.md",2532,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-vulnerability-sla-breach-alerting\u002Freferences\u002Fworkflows.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fagent.py","SCRIPT","脚本",9677,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-vulnerability-sla-breach-alerting\u002Fscripts\u002Fagent.py",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fprocess.py",11675,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-vulnerability-sla-breach-alerting\u002Fscripts\u002Fprocess.py",[107,115,122,130,138,146],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]