Reporting Culture Guide for Security Incidents
Make it easy and safe to report mistakes.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Write a guide to encourage reporting of security mistakes and suspicious events at [ORGANISATION]. Current reporting channel and how often it is used: [CHANNEL_USAGE]. Reasons people have given for not reporting: [BARRIERS]. Produce: a one-page "what to report and how" that fits on a poster; a promise from leadership in 80 words that sets out how reports will be handled without punishment for honest mistakes; a triage process showing what happens within 1 hour, 1 day, and 1 week after a report; and a feedback loop that tells reporters what was done. Add a manager guide of eight sentences on how to respond when someone confesses a mistake, and a metrics list that celebrates early reporting. Include a short note on situations where the organisation may still have to act formally and how to be honest about that. Defensive guidance only, with no step-by-step attack methods. Mark anything that depends on my environment as [VERIFY] before I act on it.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.