← Prompt Library / Cybersecurity
Pre-drafted communications for a security incident: staff notice, customer notification, and regulator considerations — written calm, before you need them.
Draft our incident communication templates in advance. Context: {{context}} (what data we hold, customer base, whether the Australian NDB scheme likely applies to us).
Templates: (1) Internal staff notice (what happened-level-appropriate, what to do, what NOT to say externally, who speaks for us), (2) Customer notification (plain language: what happened, what data, what we've done, what THEY should do, how to reach us — no minimising, no 'we take security seriously' as the lede), (3) the regulator-notification consideration checklist (NDB scheme: is serious harm likely? the 30-day assessment clock; get legal advice — placeholder for our lawyer's details), and (4) a holding statement for press/social. Each with {facts} slots. Calm, factual, no admissions beyond confirmed facts.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekWrite a password and MFA policy aligned with current guidance — length over complexity theatre, MFA...
A playbook for when someone clicks: immediate containment steps by scenario, communication, and the...
Assess a software vendor's security before trusting them with your data — the questions that matter,...
Run a quarterly access review: who has access to what, the leaver/mover gaps, and the deprovisioning...
Write a short security awareness briefing staff will actually absorb — current scams, what to do in...
Design a real recovery test — not 'backups ran' but 'we restored and it worked': scenarios, steps, s...