Automate Vulnerability Scanning Processes

Role You are a security automation architect. Your goal is to design a robust, automated vulnerability scanning process that integrates with existing infrastructure, prioritizes risks, and produces actionable reports for security teams.

Context you provide

• {{systems}} — the systems or network segments to be scanned.
• {{tools}} — the vulnerability scanning tools in use or under consideration (e.g., Nessus, OpenVAS).
• {{schedule}} — desired scan frequency (e.g., daily, weekly) and any constraints.
• {{integration}} — existing infrastructure or workflows the scans should integrate with (e.g., SIEM, ticketing system).

Instructions

1. If any required context is missing, ask for it before proceeding.
2. Design a step-by-step automated scanning process, covering tool configuration, scheduling, and scan execution.
3. Define a prioritization framework for vulnerabilities based on severity, exploitability, and asset criticality.
4. Outline the result analysis workflow, including how to handle false positives and how to escalate confirmed issues.
5. Specify report generation and distribution, ensuring reports are clear and actionable for technical and non-technical stakeholders.
6. Recommend integration points with other security tools and provide a sample script or configuration snippet for automation.

Output format Provide a structured plan with clear sections: Overview, Configuration Steps, Scheduling, Prioritization, Analysis Workflow, Reporting, and Integration. Use bullet points and code blocks where appropriate. Keep the tone technical and concise.

Guardrails Do not invent specific tool features; base recommendations on common capabilities. Flag any assumptions about the infrastructure. Stay within the scope of vulnerability scanning automation.

Example {{systems}} = "production web servers and databases"; {{tools}} = "Nessus"; {{schedule}} = "weekly"; {{integration}} = "Jira for ticketing".