1. Threat Intelligence Report Writer
Copy-paste prompt
You are a senior threat intelligence analyst. Using the raw indicators and context below, write a structured threat intelligence report with the following sections: 1. Executive Summary (3–4 sentences: who, what, and why it matters) 2. Threat Actor Profile (attribution confidence, known aliases, motivation, historic TTPs) 3. Attack Vector Analysis (initial access method, lateral movement, persistence mechanisms, tools used) 4. Indicators of Compromise (formatted table: Type | Value | Confidence | First Seen | Notes) 5. Recommended Mitigations (prioritised by feasibility and impact — include detection rules where relevant) Raw data to use: IOCs: [paste IP addresses, domains, file hashes, email addresses] TTPs: [paste MITRE ATT&CK technique IDs or descriptions] Context: [affected sector, geography, incident date range, any attribution hints] Tone: Technical but readable by a security leadership audience. Cite confidence levels (High / Medium / Low) for attribution claims.
Why it works: Raw IOCs and TTPs are only useful when contextualised. This prompt structures everything into a report leadership can act on — without you spending two hours formatting tables.
2. Security Incident Brief Writer
Copy-paste prompt
You are a cybersecurity analyst writing a stakeholder incident brief. Using the timeline and details below, write a concise incident brief that covers: 1. What happened (plain-language summary of the incident — no jargon) 2. How it was detected (tool, alert, or person that identified the issue) 3. What was affected (systems, data, users, business functions impacted) 4. Immediate response actions taken (containment, isolation, credential resets, etc.) 5. Current status (resolved / ongoing / under monitoring — with timestamp) Incident timeline: [paste your bulleted timeline] Severity: [Critical / High / Medium / Low] Audience: [C-suite / IT leadership / board / all-staff] Tone: Clear, factual, and reassuring. Avoid blame language. Max 400 words.
Why it works: During an incident, leadership needs fast clarity, not a technical deep-dive. This prompt produces a brief that answers the five questions every stakeholder asks — in the tone that keeps them calm.
3. Vulnerability Assessment Summary Writer
Copy-paste prompt
You are a cybersecurity analyst writing a vulnerability assessment summary report. Using the scan findings below, produce a clean report with these sections: 1. Findings Breakdown (table: Severity | Count | % of Total — Critical / High / Medium / Low / Informational) 2. Business Impact Narrative (2–3 paragraphs explaining what the vulnerabilities mean for the organisation in non-technical terms) 3. Prioritised Remediation Roadmap (numbered list: immediate actions within 24–72 hours, short-term fixes within 30 days, longer-term hardening within 90 days) 4. Executive Recommendation (1 paragraph summary: overall risk posture, urgency, and recommended next step) Scan findings: [paste CVE IDs, CVSS scores, affected systems, and descriptions] Business context: [industry, compliance requirements, critical systems] Audience: [CISO / IT director / board]
Why it works: Scan tools output noise. This prompt turns a raw CVE list into a prioritised, business-language report that gets remediation budgets approved faster.
Nexus Vault
Need more than the free prompts?
Get 200 business prompts, instant download, and no subscription.
4. Security Advisory Writer
Copy-paste prompt
You are a cybersecurity communications specialist writing an internal security advisory for a non-technical employee audience. Using the details below, draft an advisory that covers: 1. What it is (plain-language description of the vulnerability or threat — no acronyms without explanation) 2. Why it matters (real-world impact: what could happen if exploited, without causing panic) 3. What employees should do (specific, numbered actions — e.g. update software, change password, avoid clicking X) 4. When to escalate (clear trigger conditions — e.g. "If you receive an email matching this description, forward it to security@company.com immediately") Vulnerability / threat details: [paste CVE, threat description, or incident summary] Affected systems or user groups: [who this advisory applies to] Tone: Clear, direct, non-alarmist. Written at an 8th-grade reading level. Max 300 words.
Why it works: Security advisories fail when employees don’t understand them. This prompt forces plain-language output with clear actions — so staff actually do what you need them to do.
5. Penetration Test Executive Summary Writer
Copy-paste prompt
You are a senior penetration tester writing the executive summary section of a pentest report. Using the findings below, write a polished executive summary that includes: 1. Scope & Methodology (what was tested, what was out of scope, testing approach used) 2. Key Findings by Severity (brief narrative covering Critical, High, Medium, and Low findings — not a raw list, but a readable summary of what was found and where) 3. Risk Rating Narrative (overall risk posture: Critical / High / Medium / Low — with 2–3 sentences explaining the rating in business terms) 4. Top 3 Recommended Actions (the three highest-impact remediations, each with a one-sentence rationale) Pentest findings: [paste your list of findings with severity ratings and affected systems] Client: [organisation name and industry] Audience: [board / C-suite / IT leadership] Tone: Professional, direct, and constructive. Avoid sensationalising findings. Max 500 words.
Why it works: The executive summary is the section that drives remediation budgets — yet it’s often the last thing written and the most rushed. This prompt produces a board-ready narrative that translates technical risk into business consequence.