building-vulnerability-scanning-workflow

Builds a vulnerability scanning workflow using Nessus, Qualys, or OpenVAS with SIEM correlation and remediation tracking.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill building-vulnerability-scanning-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building-vulnerability-scanning-workflow
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/soc-operations/building-vulnerability-scanning-workflow
Command: npx skills add https://github.com/xalgord/xalgorix --skill building-vulnerability-scanning-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, qualysapi.

What problem does it solve?

SOC teams often run vulnerability scans that produce unprioritized findings, miss active exploitation, and lack formal remediation tracking. This Skill establishes a complete recurring vulnerability assessment program covering scan configuration, risk-based prioritization, SIEM correlation, SLA enforcement, and automated ticketing.

Core Features & Use Cases

  • Scan Configuration: Create credentialed Nessus and Qualys scan policies via API with scheduled weekly execution across network segments.
  • Risk-Based Prioritization: Combine CVSS scores with asset criticality and CISA KEV data to compute risk scores that surface actively exploited vulnerabilities first.
  • SIEM Integration: Correlate scan results with IDS/IPS alerts in Splunk to detect vulnerabilities under active exploitation and alert on KEV findings on critical assets.
  • Remediation Tracking: Build SLA compliance dashboards and auto-create ServiceNow tickets for high-risk findings.
  • Use Case: A SOC team needs to respond to a newly published zero-day — run a targeted scan, cross-reference results against the CISA KEV catalog, and generate prioritized tickets with 24-hour SLAs for affected production hosts.

Quick Start

Build a weekly credentialed Nessus scanning workflow for our 10.0.0.0/16 network with KEV-based prioritization, Splunk exploitation correlation, and ServiceNow ticketing for critical findings.

Frequently Asked Questions about building-vulnerability-scanning-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a recurring Nessus vulnerability scan via API?

Create a scan policy through the Nessus REST API by posting to /scans with a schedule (e.g., FREQ=WEEKLY;BYDAY=SA), target CIDR ranges, and Windows/SSH credentials. Credentialed scans are essential since uncredentialed scans miss most findings and falsely report hosts as clean.

How to prioritize vulnerabilities beyond CVSS scores?

Multiply the CVSS base score by an asset criticality factor from your inventory, then boost the score by 1.5x if the CVE appears in the CISA Known Exploited Vulnerabilities catalog. Sort findings by this combined risk score to focus remediation on actively exploited issues first.

Nessus vs Qualys vs OpenVAS for vulnerability scanning?

Nessus offers 200,000+ plugin checks with compliance auditing, Qualys VMDR provides cloud-based asset discovery and patching integration, and OpenVAS (Greenbone) is the open-source option with a community feed. All three support API-driven scan automation.

Why does my SIEM vulnerability correlation join return no results?

The join fails when Nessus emits hostnames while IDS logs IP addresses, or when multi-CVE plugins store CVEs in multivalue fields. Normalize hosts to IPs, use mvexpand on the CVE field, and test the join against a known exploitation event.

Can vulnerability scanning replace penetration testing?

No. Vulnerability scanning identifies potential weaknesses across infrastructure, while penetration testing validates actual exploitability. This workflow explicitly excludes active exploitation and should be paired with periodic penetration tests for validation.