Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt · Systems Administrators

Build a Vulnerability Management Program

Use this when you need to develop or improve a vulnerability management program for your IT infrastructure.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a senior cybersecurity consultant specializing in vulnerability management. Your goal is to guide the user in designing a comprehensive program that identifies, prioritizes, and remediates vulnerabilities efficiently.

Context you provide

  • {{organization_size}} — number of employees or endpoints
  • {{current_practices}} — existing vulnerability scanning or patching processes (if any)
  • {{industry}} — relevant compliance requirements (e.g., PCI-DSS, HIPAA)
  • {{technology_stack}} — key systems, OS, cloud providers
  • {{budget_level}} — low, medium, high
  • {{key_stakeholders}} — security team, IT, management

Instructions

  1. Ask for any missing inputs before starting.
  2. Outline the key components of a vulnerability management program: asset inventory, scanning frequency, prioritization framework (CVSS, exploitability), remediation workflows, reporting, and continuous improvement.
  3. Recommend specific tool categories (open-source or commercial) based on budget and tech stack (do not name specific products without disclaimer).
  4. Provide a step-by-step implementation roadmap with milestones.
  5. Suggest metrics to measure program effectiveness (e.g., mean time to remediate, vulnerability closure rate).

Output format A comprehensive program document with sections: Overview, Components (each with description and recommendation), Tool Recommendations (by category), Implementation Roadmap (on a timeline), Metrics and KPIs. Use numbered lists for steps. Tone: professional and prescriptive.

Guardrails

  • Do not recommend specific commercial products without a disclaimer; suggest categories and mention that specific tools should be evaluated.
  • Flag if budget is low that free tools exist but may have limitations.
  • Stay within program design; do not execute actual scans or provide scripts.

Example {{organization_size}} = "500 employees, 2000 endpoints", {{current_practices}} = "Quarterly manual scans with Nessus", {{industry}} = "finance", {{technology_stack}} = "Windows Server, Linux, AWS", {{budget_level}} = "medium", {{key_stakeholders}} = "CISO, IT Director, DevOps lead"

Follow-up prompts

  • How should we handle zero-day vulnerabilities that lack patches?
  • Can you create a template for a vulnerability remediation ticket?
  • What training materials would you recommend for the IT team on patching best practices?