Building Vulnerability Scanning Workflow
Overview
Cybersecurity skill for building vulnerability scanning workflow. Follows industry best practices and security standards.
When to Use
Trigger phrases:
- "building vulnerability scanning workflow"
- "SOC teams need to establish or improve recurring vulnerability scanning programs"
- "Scan results require prioritization beyond raw CVSS scores using asset context a"
- "Vulnerability data must be integrated into SIEM for correlation with exploitatio"
Use this skill when:
- SOC teams need to establish or improve recurring vulnerability scanning programs
- Scan results require prioritization beyond raw CVSS scores using asset context and threat intelligence
- Vulnerability data must be integrated into SIEM for correlation with exploitation attempts
- Remediation tracking needs formalization with SLA-based dashboards and reporting
Do not use for penetration testing or active exploitation — vulnerability scanning identifies weaknesses, penetration testing validates exploitability.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Vulnerability scanner (Tenable Nessus Professional, Qualys VMDR, or OpenVAS/Greenbone)
- Asset inventory with criticality classifications (business-critical, standard, development)
- Network access from scanner to all target segments (agent-based or network scan)
- SIEM integration for scan result ingestion and correlation
- Patch management system (WSUS, SCCM, Intune) for remediation tracking
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Assess Requirements — Evaluate current environment and define vulnerability scanning workflow implementation requirements.
- Design Architecture — Plan the vulnerability scanning workflow architecture, including components, integrations, and data flows.
- Configure Components — Set up and configure each vulnerability scanning workflow component according to best practices.
- Test Integration — Validate that all components work together. Run functional and security tests.
- Deploy to Production — Roll out the implementation with monitoring and rollback capabilities.
- Validate and Document — Verify the implementation meets requirements. Document configuration and runbooks.
Tools
- Configuration Management — Infrastructure as code and automation
- Monitoring Stack — Observability and alerting
- Documentation Platform — Runbooks and architecture docs
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: building-vulnerability-scanning-workflow3description: 'Use when builds a structured vulnerability scanning workflow using tools4 like Nessus, Qualys, and OpenVAS to discover, prioritize, and track remediation5 of security vulnerabilities across infrastructure. Use when SOC teams need to establish6 recurring vulnerability assessment processes, integrate scan results with SIEM alerting,7 and build remediation tracking dashboards.89 '10domain: cybersecurity11tags:12- soc13- vulnerability-scanning14- nessus15- qualys16- openvas17- cvss18- remediation19- patch-management20subdomain: soc-operations21version: '1.0'22author: oyi7723license: Apache-2.024nist_csf:25- DE.CM-0126- DE.AE-0227- RS.MA-0128- DE.AE-0629category: cybersecurity30metadata:31 source: https://skillmd.com/skills/oyi77/building-vulnerability-scanning-workflow32---3334# Building Vulnerability Scanning Workflow3536## Overview3738Cybersecurity skill for building vulnerability scanning workflow. Follows industry best practices and security standards.3940## When to Use4142**Trigger phrases:**43- "building vulnerability scanning workflow"44- "SOC teams need to establish or improve recurring vulnerability scanning programs"45- "Scan results require prioritization beyond raw CVSS scores using asset context a"46- "Vulnerability data must be integrated into SIEM for correlation with exploitatio"474849Use this skill when:50- SOC teams need to establish or improve recurring vulnerability scanning programs51- Scan results require prioritization beyond raw CVSS scores using asset context and threat intelligence52- Vulnerability data must be integrated into SIEM for correlation with exploitation attempts53- Remediation tracking needs formalization with SLA-based dashboards and reporting5455**Do not use** for penetration testing or active exploitation — vulnerability scanning identifies weaknesses, penetration testing validates exploitability.565758## When NOT to Use5960- When you lack proper authorization for testing61- For production systems without change management62- When the task requires legal or compliance expertise beyond technical scope636465## Prerequisites6667- Vulnerability scanner (Tenable Nessus Professional, Qualys VMDR, or OpenVAS/Greenbone)68- Asset inventory with criticality classifications (business-critical, standard, development)69- Network access from scanner to all target segments (agent-based or network scan)70- SIEM integration for scan result ingestion and correlation71- Patch management system (WSUS, SCCM, Intune) for remediation tracking7273## Workflow7475```python76# Example: IOC detection77import re7879IOC_PATTERNS = {80 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",81 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",82 "hash_md5": r"\b[a-f0-9]{32}\b",83 "hash_sha256": r"\b[a-f0-9]{64}\b",84}8586def extract_iocs(text: str) -> dict:87 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}88```89901. **Assess Requirements** — Evaluate current environment and define vulnerability scanning workflow implementation requirements.912. **Design Architecture** — Plan the vulnerability scanning workflow architecture, including components, integrations, and data flows.923. **Configure Components** — Set up and configure each vulnerability scanning workflow component according to best practices.934. **Test Integration** — Validate that all components work together. Run functional and security tests.945. **Deploy to Production** — Roll out the implementation with monitoring and rollback capabilities.956. **Validate and Document** — Verify the implementation meets requirements. Document configuration and runbooks.9697## Tools9899- **Configuration Management** — Infrastructure as code and automation100- **Monitoring Stack** — Observability and alerting101- **Documentation Platform** — Runbooks and architecture docs102103104## Process1051061. **Reconnaissance** — Gather target information, identify attack surface, enumerate services1071. **Analysis/Exploitation** — Execute the technique, analyze results, document findings1081. **Reporting** — Document IOCs, write findings, provide remediation recommendations109110## Verification111112- [ ] All vulnerability scanning workflow procedures executed completely and documented113- [ ] Findings validated against multiple data sources114- [ ] False positives identified and filtered115- [ ] Results documented with evidence and timestamps116- [ ] Recommendations provided with risk-based prioritization117118## Anti-Rationalization Table119120| Rationalization | Reality |121|---|---|122| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |123| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |124| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |