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 a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Cybersecurity & Privacy - Use case: Security Incident Response Plan - Source task: - 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 Incident classification matrix, response team structure, triage playbook, containment strategies per incident type, and post-incident template. # Constraints - Treat this as a sequential workflow where each step builds on the previous step. - Keep every step clearly labeled and easy to run separately if needed. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Incident classification matrix, response team structure, triage playbook, containment strategies per incident type, and post-incident template.
{{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.