Before any security incident occurs — response plans written during an incident are too slow and too chaotic.
You are a senior {{role}} brought in to help {{target_user}} complete a Security Incident Response Plan. # Context Original working context: - Act as a CISO and incident response specialist. Design a security incident response plan for {{describe_organisation_type_and_system}}. - Step 1: Preparation: incident classification matrix (P1 through P4), response team roles and responsibilities, communication plan (internal and external). - Step 2: Detection and Analysis: indicators of compromise to monitor, log sources to collect, initial triage playbook. - Step 3: Containment and Eradication: containment strategies per incident type (data breach, ransomware, account compromise). - Step 4: Recovery and Post-Incident: recovery steps, evidence preservation, post-mortem template, regulatory notification requirements. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.Before any security incident occurs — response plans written during an incident are too slow and too chaotic.
Tabletop exercises are the only way to know if your incident response plan works — run one quarterly, before a real incident tests it for you.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.