[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B5BSVKXV2P2FEEC6BF1ZWN":3,"skill-same:01M7B5BSVKXV2P2FEEC6BF1ZWN":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M7B5BSVKXV2P2FEEC6BF1ZWN","building-vulnerability-scanning-workflow",null,"Builds a structured vulnerability scanning workflow using tools like Nessus, Qualys, and OpenVAS to discover, prioritize, and track remediation of security vulnerabilities across infrastructure. Use when SOC teams need to establish recurring vulnerability assessment processes, integrate scan results with SIEM alerting, and build remediation tracking dashboards.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-vulnerability-scanning-workflow\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-vulnerability-scanning-workflow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: building-vulnerability-scanning-workflow\ndescription: 'Builds a structured vulnerability scanning workflow using tools like\n  Nessus, Qualys, and OpenVAS to discover, prioritize, and track remediation of security\n  vulnerabilities across infrastructure. Use when SOC teams need to establish recurring\n  vulnerability assessment processes, integrate scan results with SIEM alerting, and\n  build remediation tracking dashboards.\n\n  '\ndomain: cybersecurity\nsubdomain: soc-operations\ntags:\n- soc\n- vulnerability-scanning\n- nessus\n- qualys\n- openvas\n- cvss\n- remediation\n- patch-management\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- RS.MA-01\n- DE.AE-06\nmitre_attack:\n- T1595.002\n- T1190\n- T1046\n---\n# Building Vulnerability Scanning Workflow\n\n## When to Use\n\nUse this skill when:\n- SOC teams need to establish or improve recurring vulnerability scanning programs\n- Scan results require prioritization beyond raw CVSS scores using asset context and threat intelligence\n- Vulnerability data must be integrated into SIEM for correlation with exploitation attempts\n- Remediation tracking needs formalization with SLA-based dashboards and reporting\n\n**Do not use** for penetration testing or active exploitation — vulnerability scanning identifies weaknesses, penetration testing validates exploitability.\n\n## Prerequisites\n\n- Vulnerability scanner (Tenable Nessus Professional, Qualys VMDR, or OpenVAS\u002FGreenbone)\n- Asset inventory with criticality classifications (business-critical, standard, development)\n- Network access from scanner to all target segments (agent-based or network scan)\n- SIEM integration for scan result ingestion and correlation\n- Patch management system (WSUS, SCCM, Intune) for remediation tracking\n\n## Workflow\n\n### Step 1: Define Scan Scope and Scheduling\n\nCreate scan policies covering all asset types:\n\n**Nessus Scan Configuration (API):**\n```python\nimport requests\n\nnessus_url = \"https:\u002F\u002Fnessus.company.com:8834\"\nheaders = {\"X-ApiKeys\": f\"accessKey={access_key};secretKey={secret_key}\"}\n\n# Create scan policy\npolicy = {\n    \"uuid\": \"advanced\",\n    \"settings\": {\n        \"name\": \"SOC Weekly Infrastructure Scan\",\n        \"description\": \"Weekly credentialed scan of all server and workstation segments\",\n        \"scanner_id\": 1,\n        \"policy_id\": 0,\n        \"text_targets\": \"10.0.0.0\u002F16, 172.16.0.0\u002F12\",\n        \"launch\": \"WEEKLY\",\n        \"starttime\": \"20240315T020000\",\n        \"rrules\": \"FREQ=WEEKLY;INTERVAL=1;BYDAY=SA\",\n        \"enabled\": True\n    },\n    \"credentials\": {\n        \"add\": {\n            \"Host\": {\n                \"Windows\": [{\n                    \"domain\": \"company.local\",\n                    \"username\": \"nessus_svc\",\n                    \"password\": \"SCAN_SERVICE_PASSWORD\",\n                    \"auth_method\": \"Password\"\n                }],\n                \"SSH\": [{\n                    \"username\": \"nessus_svc\",\n                    \"private_key\": \"\u002Fpath\u002Fto\u002Fnessus_key\",\n                    \"auth_method\": \"public key\"\n                }]\n            }\n        }\n    }\n}\n\nresponse = requests.post(f\"{nessus_url}\u002Fscans\", headers=headers, json=policy,\n                         verify=not os.environ.get(\"SKIP_TLS_VERIFY\", \"\").lower() == \"true\")  # Set SKIP_TLS_VERIFY=true for self-signed certs in lab environments\nscan_id = response.json()[\"scan\"][\"id\"]\nprint(f\"Scan created: ID {scan_id}\")\n```\n\n**Qualys VMDR Scan via API:**\n```python\nimport qualysapi\n\nconn = qualysapi.connect(\n    hostname=\"qualysapi.qualys.com\",\n    username=\"api_user\",\n    password=\"API_PASSWORD\"\n)\n\n# Launch vulnerability scan\nparams = {\n    \"action\": \"launch\",\n    \"scan_title\": \"Weekly_Infrastructure_Scan\",\n    \"ip\": \"10.0.0.0\u002F16\",\n    \"option_id\": \"123456\",  # Scan profile ID\n    \"iscanner_name\": \"Internal_Scanner_01\",\n    \"priority\": \"0\"\n}\n\nresponse = conn.request(\"\u002Fapi\u002F2.0\u002Ffo\u002Fscan\u002F\", params)\nprint(f\"Scan launched: {response}\")\n```\n\n### Step 2: Process and Prioritize Scan Results\n\nDownload results and apply risk-based prioritization:\n\n```python\nimport requests\nimport csv\n\n# Export Nessus results\nresponse = requests.get(\n    f\"{nessus_url}\u002Fscans\u002F{scan_id}\u002Fexport\",\n    headers=headers,\n    params={\"format\": \"csv\"},\n    verify=not os.environ.get(\"SKIP_TLS_VERIFY\", \"\").lower() == \"true\",  # Set SKIP_TLS_VERIFY=true for self-signed certs in lab environments\n)\n\n# Parse and prioritize\nvulns = []\nreader = csv.DictReader(response.text.splitlines())\nfor row in reader:\n    cvss = float(row.get(\"CVSS v3.0 Base Score\", 0))\n    asset_criticality = get_asset_criticality(row[\"Host\"])  # From asset inventory\n\n    # Risk-based priority calculation\n    risk_score = cvss * asset_criticality_multiplier(asset_criticality)\n\n    # Boost score if actively exploited (check CISA KEV)\n    if row.get(\"CVE\") in cisa_kev_list:\n        risk_score *= 1.5\n\n    vulns.append({\n        \"host\": row[\"Host\"],\n        \"plugin_name\": row[\"Name\"],\n        \"severity\": row[\"Risk\"],\n        \"cvss\": cvss,\n        \"cve\": row.get(\"CVE\", \"N\u002FA\"),\n        \"risk_score\": round(risk_score, 1),\n        \"asset_criticality\": asset_criticality,\n        \"kev\": row.get(\"CVE\") in cisa_kev_list\n    })\n\n# Sort by risk score\nvulns.sort(key=lambda x: x[\"risk_score\"], reverse=True)\n```\n\n**CISA KEV (Known Exploited Vulnerabilities) Check:**\n```python\nimport requests\n\nkev_response = requests.get(\n    \"https:\u002F\u002Fwww.cisa.gov\u002Fsites\u002Fdefault\u002Ffiles\u002Ffeeds\u002Fknown_exploited_vulnerabilities.json\"\n)\nkev_data = kev_response.json()\ncisa_kev_list = {v[\"cveID\"] for v in kev_data[\"vulnerabilities\"]}\n\n# Check if vulnerability is actively exploited\ndef is_actively_exploited(cve_id):\n    return cve_id in cisa_kev_list\n```\n\n### Step 3: Define Remediation SLAs\n\nApply SLA-based remediation timelines:\n\n| Priority | CVSS Range | Asset Type | SLA | Examples |\n|----------|-----------|------------|-----|---------|\n| **P1 Critical** | 9.0-10.0 + KEV | All assets | 24 hours | Log4Shell, EternalBlue on prod servers |\n| **P2 High** | 7.0-8.9 or 9.0+ non-KEV | Business-critical | 7 days | RCE without known exploit |\n| **P3 Medium** | 4.0-6.9 | Business-critical | 30 days | Authenticated privilege escalation |\n| **P4 Low** | 0.1-3.9 | Standard | 90 days | Information disclosure, low-impact DoS |\n| **P5 Informational** | 0.0 | Development | Next cycle | Best practice findings, config hardening |\n\n### Step 4: Integrate with SIEM for Exploitation Detection\n\nCorrelate vulnerability scan data with SIEM alerts to detect active exploitation:\n\n```spl\nindex=vulnerability sourcetype=\"nessus:scan\"\n| eval vuln_key = Host.\":\".CVE\n| join vuln_key type=left [\n    search index=ids_ips sourcetype=\"snort\" OR sourcetype=\"suricata\"\n    | eval vuln_key = dest_ip.\":\".cve_id\n    | stats count AS exploit_attempts, latest(_time) AS last_exploit_attempt by vuln_key\n  ]\n| where isnotnull(exploit_attempts)\n| eval risk = \"CRITICAL — Vulnerability being actively exploited\"\n| sort - exploit_attempts\n| table Host, CVE, plugin_name, cvss_score, exploit_attempts, last_exploit_attempt, risk\n```\n\n**Alert when KEV vulnerabilities are detected on critical assets:**\n```spl\nindex=vulnerability sourcetype=\"nessus:scan\" severity=\"Critical\"\n| lookup cisa_kev_lookup.csv cve_id AS CVE OUTPUT kev_status, due_date\n| where kev_status=\"active\"\n| lookup asset_criticality_lookup.csv ip AS Host OUTPUT criticality\n| where criticality IN (\"business-critical\", \"mission-critical\")\n| table Host, CVE, plugin_name, cvss_score, kev_status, due_date, criticality\n```\n\n### Step 5: Build Remediation Tracking Dashboard\n\n**Splunk Dashboard for Vulnerability Metrics:**\n```spl\n-- Open vulnerabilities by severity\nindex=vulnerability sourcetype=\"nessus:scan\" status=\"open\"\n| stats count by severity\n| eval order = case(severity=\"Critical\", 1, severity=\"High\", 2, severity=\"Medium\", 3,\n                    severity=\"Low\", 4, 1=1, 5)\n| sort order\n\n-- SLA compliance tracking\nindex=vulnerability sourcetype=\"nessus:scan\" status=\"open\"\n| eval sla_days = case(\n    severity=\"Critical\", 1,\n    severity=\"High\", 7,\n    severity=\"Medium\", 30,\n    severity=\"Low\", 90\n  )\n| eval days_open = round((now() - first_detected) \u002F 86400)\n| eval sla_status = if(days_open > sla_days, \"OVERDUE\", \"Within SLA\")\n| stats count by severity, sla_status\n\n-- Remediation trend over 90 days\nindex=vulnerability sourcetype=\"nessus:scan\"\n| eval is_open = if(status=\"open\", 1, 0)\n| eval is_closed = if(status=\"fixed\", 1, 0)\n| timechart span=1w sum(is_open) AS opened, sum(is_closed) AS remediated\n```\n\n### Step 6: Automate Remediation Ticketing\n\nCreate tickets automatically for high-priority findings:\n\n```python\nimport requests\n\nservicenow_url = \"https:\u002F\u002Fcompany.service-now.com\u002Fapi\u002Fnow\u002Ftable\u002Fincident\"\nheaders = {\n    \"Content-Type\": \"application\u002Fjson\",\n    \"Authorization\": f\"Bearer {snow_token}\"\n}\n\nfor vuln in vulns:\n    if vuln[\"risk_score\"] >= 8.0:\n        ticket = {\n            \"short_description\": f\"[VULN] {vuln['cve']} — {vuln['plugin_name']} on {vuln['host']}\",\n            \"description\": (\n                f\"Vulnerability: {vuln['plugin_name']}\\n\"\n                f\"CVE: {vuln['cve']}\\n\"\n                f\"CVSS: {vuln['cvss']}\\n\"\n                f\"Host: {vuln['host']}\\n\"\n                f\"Asset Criticality: {vuln['asset_criticality']}\\n\"\n                f\"CISA KEV: {'YES' if vuln['kev'] else 'NO'}\\n\"\n                f\"Risk Score: {vuln['risk_score']}\\n\"\n                f\"Remediation SLA: {'24 hours' if vuln['kev'] else '7 days'}\"\n            ),\n            \"urgency\": \"1\" if vuln[\"kev\"] else \"2\",\n            \"impact\": \"1\" if vuln[\"asset_criticality\"] == \"business-critical\" else \"2\",\n            \"assignment_group\": \"IT Infrastructure\",\n            \"category\": \"Vulnerability\"\n        }\n        response = requests.post(servicenow_url, headers=headers, json=ticket)\n        print(f\"Ticket created: {response.json()['result']['number']}\")\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **CVSS** | Common Vulnerability Scoring System — standardized severity rating (0-10) for vulnerabilities |\n| **CISA KEV** | Known Exploited Vulnerabilities catalog — CISA-maintained list of vulnerabilities with confirmed active exploitation |\n| **Credentialed Scan** | Vulnerability scan using authenticated access for deeper detection than network-only scanning |\n| **Asset Criticality** | Business impact classification determining remediation priority (mission-critical, business-critical, standard) |\n| **Remediation SLA** | Service Level Agreement defining maximum time allowed to patch vulnerabilities by severity |\n| **EPSS** | Exploit Prediction Scoring System — ML-based probability score predicting likelihood of exploitation |\n\n## Tools & Systems\n\n- **Tenable Nessus \u002F Tenable.io**: Enterprise vulnerability scanner with 200,000+ plugin checks and compliance auditing\n- **Qualys VMDR**: Cloud-based vulnerability management with asset discovery, prioritization, and patching integration\n- **OpenVAS (Greenbone)**: Open-source vulnerability scanner with community-maintained vulnerability feed\n- **CISA KEV Catalog**: US government maintained list of actively exploited vulnerabilities requiring mandatory remediation\n- **Rapid7 InsightVM**: Vulnerability management platform with live dashboards and remediation project tracking\n\n## Common Scenarios\n\n- **Zero-Day Response**: New CVE published — run targeted scan for affected software, cross-reference with KEV and exploit databases\n- **Compliance Audit Prep**: Generate PCI DSS or HIPAA vulnerability report showing scan coverage and remediation status\n- **Post-Patch Verification**: Rescan patched systems to confirm vulnerability closure and update tracking dashboard\n- **Network Expansion**: New subnet added to infrastructure — onboard to scan scope with appropriate policy\n- **Third-Party Risk**: Scan externally-facing assets to validate vendor patch compliance before integration\n\n## Output Format\n\n```\nVULNERABILITY SCAN REPORT — Weekly Summary\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nScan Date:    2024-03-16 02:00 UTC\nScan Scope:   10.0.0.0\u002F16 (1,247 hosts scanned)\nDuration:     4h 23m\nCoverage:     98.7% (16 hosts unreachable)\n\nFindings:\n  Severity     Count    New    CISA KEV\n  Critical     23       5      3\n  High         187      34     12\n  Medium       892      78     0\n  Low          1,456    112    0\n  Info         3,891    201    0\n\nTop Priority (P1 — 24hr SLA):\n  CVE-2024-21762  FortiOS RCE           3 hosts   KEV: YES\n  CVE-2024-1709   ConnectWise RCE       1 host    KEV: YES\n  CVE-2024-3400   Palo Alto PAN-OS RCE  2 hosts   KEV: YES\n\nSLA Compliance:\n  Critical: 82% within SLA (4 overdue)\n  High:     91% within SLA (17 overdue)\n  Medium:   88% within SLA (107 overdue)\n\nTickets Created: 39 (ServiceNow)\n```\n","# Building Vulnerability Scanning Workflow\n\n## When to Use\n\nUse this skill when:\n- SOC teams need to establish or improve recurring vulnerability scanning programs\n- Scan results require prioritization beyond raw CVSS scores using asset context and threat intelligence\n- Vulnerability data must be integrated into SIEM for correlation with exploitation attempts\n- Remediation tracking needs formalization with SLA-based dashboards and reporting\n\n**Do not use** for penetration testing or active exploitation — vulnerability scanning identifies weaknesses, penetration testing validates exploitability.\n\n## Prerequisites\n\n- Vulnerability scanner (Tenable Nessus Professional, Qualys VMDR, or OpenVAS\u002FGreenbone)\n- Asset inventory with criticality classifications (business-critical, standard, development)\n- Network access from scanner to all target segments (agent-based or network scan)\n- SIEM integration for scan result ingestion and correlation\n- Patch management system (WSUS, SCCM, Intune) for remediation tracking\n\n## Workflow\n\n### Step 1: Define Scan Scope and Scheduling\n\nCreate scan policies covering all asset types:\n\n**Nessus Scan Configuration (API):**\n```python\nimport requests\n\nnessus_url = \"https:\u002F\u002Fnessus.company.com:8834\"\nheaders = {\"X-ApiKeys\": f\"accessKey={access_key};secretKey={secret_key}\"}\n\n# Create scan policy\npolicy = {\n    \"uuid\": \"advanced\",\n    \"settings\": {\n        \"name\": \"SOC Weekly Infrastructure Scan\",\n        \"description\": \"Weekly credentialed scan of all server and workstation segments\",\n        \"scanner_id\": 1,\n        \"policy_id\": 0,\n        \"text_targets\": \"10.0.0.0\u002F16, 172.16.0.0\u002F12\",\n        \"launch\": \"WEEKLY\",\n        \"starttime\": \"20240315T020000\",\n        \"rrules\": \"FREQ=WEEKLY;INTERVAL=1;BYDAY=SA\",\n        \"enabled\": True\n    },\n    \"credentials\": {\n        \"add\": {\n            \"Host\": {\n                \"Windows\": [{\n                    \"domain\": \"company.local\",\n                    \"username\": \"nessus_svc\",\n                    \"password\": \"SCAN_SERVICE_PASSWORD\",\n                    \"auth_method\": \"Password\"\n                }],\n                \"SSH\": [{\n                    \"username\": \"nessus_svc\",\n                    \"private_key\": \"\u002Fpath\u002Fto\u002Fnessus_key\",\n                    \"auth_method\": \"public key\"\n                }]\n            }\n        }\n    }\n}\n\nresponse = requests.post(f\"{nessus_url}\u002Fscans\", headers=headers, json=policy,\n                         verify=not os.environ.get(\"SKIP_TLS_VERIFY\", \"\").lower() == \"true\")  # Set SKIP_TLS_VERIFY=true for self-signed certs in lab environments\nscan_id = response.json()[\"scan\"][\"id\"]\nprint(f\"Scan created: ID {scan_id}\")\n```\n\n**Qualys VMDR Scan via API:**\n```python\nimport qualysapi\n\nconn = qualysapi.connect(\n    hostname=\"qualysapi.qualys.com\",\n    username=\"api_user\",\n    password=\"API_PASSWORD\"\n)\n\n# Launch vulnerability scan\nparams = {\n    \"action\": \"launch\",\n    \"scan_title\": \"Weekly_Infrastructure_Scan\",\n    \"ip\": \"10.0.0.0\u002F16\",\n    \"option_id\": \"123456\",  # Scan profile ID\n    \"iscanner_name\": \"Internal_Scanner_01\",\n    \"priority\": \"0\"\n}\n\nresponse = conn.request(\"\u002Fapi\u002F2.0\u002Ffo\u002Fscan\u002F\", params)\nprint(f\"Scan launched: {response}\")\n```\n\n### Step 2: Process and Prioritize Scan Results\n\nDownload results and apply risk-based prioritization:\n\n```python\nimport requests\nimport csv\n\n# Export Nessus results\nresponse = requests.get(\n    f\"{nessus_url}\u002Fscans\u002F{scan_id}\u002Fexport\",\n    headers=headers,\n    params={\"format\": \"csv\"},\n    verify=not os.environ.get(\"SKIP_TLS_VERIFY\", \"\").lower() == \"true\",  # Set SKIP_TLS_VERIFY=true for self-signed certs in lab environments\n)\n\n# Parse and prioritize\nvulns = []\nreader = csv.DictReader(response.text.splitlines())\nfor row in reader:\n    cvss = float(row.get(\"CVSS v3.0 Base Score\", 0))\n    asset_criticality = get_asset_criticality(row[\"Host\"])  # From asset inventory\n\n    # Risk-based priority calculation\n    risk_score = cvss * asset_criticality_multiplier(asset_criticality)\n\n    # Boost score if actively exploited (check CISA KEV)\n    if row.get(\"CVE\") in cisa_kev_list:\n        risk_score *= 1.5\n\n    vulns.append({\n        \"host\": row[\"Host\"],\n        \"plugin_name\": row[\"Name\"],\n        \"severity\": row[\"Risk\"],\n        \"cvss\": cvss,\n        \"cve\": row.get(\"CVE\", \"N\u002FA\"),\n        \"risk_score\": round(risk_score, 1),\n        \"asset_criticality\": asset_criticality,\n        \"kev\": row.get(\"CVE\") in cisa_kev_list\n    })\n\n# Sort by risk score\nvulns.sort(key=lambda x: x[\"risk_score\"], reverse=True)\n```\n\n**CISA KEV (Known Exploited Vulnerabilities) Check:**\n```python\nimport requests\n\nkev_response = requests.get(\n    \"https:\u002F\u002Fwww.cisa.gov\u002Fsites\u002Fdefault\u002Ffiles\u002Ffeeds\u002Fknown_exploited_vulnerabilities.json\"\n)\nkev_data = kev_response.json()\ncisa_kev_list = {v[\"cveID\"] for v in kev_data[\"vulnerabilities\"]}\n\n# Check if vulnerability is actively exploited\ndef is_actively_exploited(cve_id):\n    return cve_id in cisa_kev_list\n```\n\n### Step 3: Define Remediation SLAs\n\nApply SLA-based remediation timelines:\n\n| Priority | CVSS Range | Asset Type | SLA | Examples |\n|----------|-----------|------------|-----|---------|\n| **P1 Critical** | 9.0-10.0 + KEV | All assets | 24 hours | Log4Shell, EternalBlue on prod servers |\n| **P2 High** | 7.0-8.9 or 9.0+ non-KEV | Business-critical | 7 days | RCE without known exploit |\n| **P3 Medium** | 4.0-6.9 | Business-critical | 30 days | Authenticated privilege escalation |\n| **P4 Low** | 0.1-3.9 | Standard | 90 days | Information disclosure, low-impact DoS |\n| **P5 Informational** | 0.0 | Development | Next cycle | Best practice findings, config hardening |\n\n### Step 4: Integrate with SIEM for Exploitation Detection\n\nCorrelate vulnerability scan data with SIEM alerts to detect active exploitation:\n\n```spl\nindex=vulnerability sourcetype=\"nessus:scan\"\n| eval vuln_key = Host.\":\".CVE\n| join vuln_key type=left [\n    search index=ids_ips sourcetype=\"snort\" OR sourcetype=\"suricata\"\n    | eval vuln_key = dest_ip.\":\".cve_id\n    | stats count AS exploit_attempts, latest(_time) AS last_exploit_attempt by vuln_key\n  ]\n| where isnotnull(exploit_attempts)\n| eval risk = \"CRITICAL — Vulnerability being actively exploited\"\n| sort - exploit_attempts\n| table Host, CVE, plugin_name, cvss_score, exploit_attempts, last_exploit_attempt, risk\n```\n\n**Alert when KEV vulnerabilities are detected on critical assets:**\n```spl\nindex=vulnerability sourcetype=\"nessus:scan\" severity=\"Critical\"\n| lookup cisa_kev_lookup.csv cve_id AS CVE OUTPUT kev_status, due_date\n| where kev_status=\"active\"\n| lookup asset_criticality_lookup.csv ip AS Host OUTPUT criticality\n| where criticality IN (\"business-critical\", \"mission-critical\")\n| table Host, CVE, plugin_name, cvss_score, kev_status, due_date, criticality\n```\n\n### Step 5: Build Remediation Tracking Dashboard\n\n**Splunk Dashboard for Vulnerability Metrics:**\n```spl\n-- Open vulnerabilities by severity\nindex=vulnerability sourcetype=\"nessus:scan\" status=\"open\"\n| stats count by severity\n| eval order = case(severity=\"Critical\", 1, severity=\"High\", 2, severity=\"Medium\", 3,\n                    severity=\"Low\", 4, 1=1, 5)\n| sort order\n\n-- SLA compliance tracking\nindex=vulnerability sourcetype=\"nessus:scan\" status=\"open\"\n| eval sla_days = case(\n    severity=\"Critical\", 1,\n    severity=\"High\", 7,\n    severity=\"Medium\", 30,\n    severity=\"Low\", 90\n  )\n| eval days_open = round((now() - first_detected) \u002F 86400)\n| eval sla_status = if(days_open > sla_days, \"OVERDUE\", \"Within SLA\")\n| stats count by severity, sla_status\n\n-- Remediation trend over 90 days\nindex=vulnerability sourcetype=\"nessus:scan\"\n| eval is_open = if(status=\"open\", 1, 0)\n| eval is_closed = if(status=\"fixed\", 1, 0)\n| timechart span=1w sum(is_open) AS opened, sum(is_closed) AS remediated\n```\n\n### Step 6: Automate Remediation Ticketing\n\nCreate tickets automatically for high-priority findings:\n\n```python\nimport requests\n\nservicenow_url = \"https:\u002F\u002Fcompany.service-now.com\u002Fapi\u002Fnow\u002Ftable\u002Fincident\"\nheaders = {\n    \"Content-Type\": \"application\u002Fjson\",\n    \"Authorization\": f\"Bearer {snow_token}\"\n}\n\nfor vuln in vulns:\n    if vuln[\"risk_score\"] >= 8.0:\n        ticket = {\n            \"short_description\": f\"[VULN] {vuln['cve']} — {vuln['plugin_name']} on {vuln['host']}\",\n            \"description\": (\n                f\"Vulnerability: {vuln['plugin_name']}\\n\"\n                f\"CVE: {vuln['cve']}\\n\"\n                f\"CVSS: {vuln['cvss']}\\n\"\n                f\"Host: {vuln['host']}\\n\"\n                f\"Asset Criticality: {vuln['asset_criticality']}\\n\"\n                f\"CISA KEV: {'YES' if vuln['kev'] else 'NO'}\\n\"\n                f\"Risk Score: {vuln['risk_score']}\\n\"\n                f\"Remediation SLA: {'24 hours' if vuln['kev'] else '7 days'}\"\n            ),\n            \"urgency\": \"1\" if vuln[\"kev\"] else \"2\",\n            \"impact\": \"1\" if vuln[\"asset_criticality\"] == \"business-critical\" else \"2\",\n            \"assignment_group\": \"IT Infrastructure\",\n            \"category\": \"Vulnerability\"\n        }\n        response = requests.post(servicenow_url, headers=headers, json=ticket)\n        print(f\"Ticket created: {response.json()['result']['number']}\")\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **CVSS** | Common Vulnerability Scoring System — standardized severity rating (0-10) for vulnerabilities |\n| **CISA KEV** | Known Exploited Vulnerabilities catalog — CISA-maintained list of vulnerabilities with confirmed active exploitation |\n| **Credentialed Scan** | Vulnerability scan using authenticated access for deeper detection than network-only scanning |\n| **Asset Criticality** | Business impact classification determining remediation priority (mission-critical, business-critical, standard) |\n| **Remediation SLA** | Service Level Agreement defining maximum time allowed to patch vulnerabilities by severity |\n| **EPSS** | Exploit Prediction Scoring System — ML-based probability score predicting likelihood of exploitation |\n\n## Tools & Systems\n\n- **Tenable Nessus \u002F Tenable.io**: Enterprise vulnerability scanner with 200,000+ plugin checks and compliance auditing\n- **Qualys VMDR**: Cloud-based vulnerability management with asset discovery, prioritization, and patching integration\n- **OpenVAS (Greenbone)**: Open-source vulnerability scanner with community-maintained vulnerability feed\n- **CISA KEV Catalog**: US government maintained list of actively exploited vulnerabilities requiring mandatory remediation\n- **Rapid7 InsightVM**: Vulnerability management platform with live dashboards and remediation project tracking\n\n## Common Scenarios\n\n- **Zero-Day Response**: New CVE published — run targeted scan for affected software, cross-reference with KEV and exploit databases\n- **Compliance Audit Prep**: Generate PCI DSS or HIPAA vulnerability report showing scan coverage and remediation status\n- **Post-Patch Verification**: Rescan patched systems to confirm vulnerability closure and update tracking dashboard\n- **Network Expansion**: New subnet added to infrastructure — onboard to scan scope with appropriate policy\n- **Third-Party Risk**: Scan externally-facing assets to validate vendor patch compliance before integration\n\n## Output Format\n\n```\nVULNERABILITY SCAN REPORT — Weekly Summary\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nScan Date:    2024-03-16 02:00 UTC\nScan Scope:   10.0.0.0\u002F16 (1,247 hosts scanned)\nDuration:     4h 23m\nCoverage:     98.7% (16 hosts unreachable)\n\nFindings:\n  Severity     Count    New    CISA KEV\n  Critical     23       5      3\n  High         187      34     12\n  Medium       892      78     0\n  Low          1,456    112    0\n  Info         3,891    201    0\n\nTop Priority (P1 — 24hr SLA):\n  CVE-2024-21762  FortiOS RCE           3 hosts   KEV: YES\n  CVE-2024-1709   ConnectWise RCE       1 host    KEV: YES\n  CVE-2024-3400   Palo Alto PAN-OS RCE  2 hosts   KEV: YES\n\nSLA Compliance:\n  Critical: 82% within SLA (4 overdue)\n  High:     91% within SLA (17 overdue)\n  Medium:   88% within SLA (107 overdue)\n\nTickets Created: 39 (ServiceNow)\n```\n",{"name":5,"tags":24,"author":33,"domain":34,"license":14,"version":35,"nist_csf":36,"subdomain":41,"description":42,"mitre_attack":43},[25,26,27,28,29,30,31,32],"soc","vulnerability-scanning","nessus","qualys","openvas","cvss","remediation","patch-management","mahipal","cybersecurity","1.0",[37,38,39,40],"DE.CM-01","DE.AE-02","RS.MA-01","DE.AE-06","soc-operations","Builds a structured vulnerability scanning workflow using tools like Nessus, Qualys, and OpenVAS to discover, prioritize, and track remediation of security vulnerabilities across infrastructure. Use when SOC teams need to establish recurring vulnerability assessment processes, integrate scan results with SIEM alerting, and build remediation tracking dashboards.\n",[44,45,46],"T1595.002","T1190","T1046","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-vulnerability-scanning-workflow","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill building-vulnerability-scanning-workflow",{"tool":59,"command":60},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill building-vulnerability-scanning-workflow",{"tool":62,"command":63},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill building-vulnerability-scanning-workflow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-vulnerability-scanning-workflow\u002FSKILL.md",true,[67,71,77],{"path":68,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fapi-reference.md","REFERENCE","参考文档",1780,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-vulnerability-scanning-workflow\u002Freferences\u002Fapi-reference.md",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Fagent.py","SCRIPT","脚本",6296,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-vulnerability-scanning-workflow\u002Fscripts\u002Fagent.py",[84,92,99,106,113,120],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]