🔒Cybersecurity

Incident Response Messages

Security incident communication templates for various severity levels.

9 snippets included|Free to download|Works with TypeFire for macOS
Download TypeFire for macOS
zcir1

Updated Request

Hi {{cursor}},

Following up on our recent conversation about updated request.

Here are the key details:

- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]

Please review the above and let me know if you have any questions or need additional information.

I look forward to hearing from you. Feel free to reply to this message or schedule a call.

Best regards
zcir2

Revised Summary

Revised Summary

Date: {{date}}
Prepared by: {{cursor}}

Summary:
[Brief overview of revised summary]

Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]

Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]

Next Steps:
[Description of what happens next]

Notes:
[Additional context or considerations]
zcir3

Initial Alert

Hi {{cursor}},

Quick update on initial alert:

[Key information]

Let me know if you have any questions.

Best
zcir4

Follow-Up Note

Follow-Up Note

Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}

Description:
[Detailed description of follow-up note]

Key Points:
- [Point 1]
- [Point 2]
- [Point 3]

Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]

Notes:
[Additional information]
zcir5

Standard Memo

Hi {{cursor}},

I wanted to follow up with you about standard memo.

Here are the key details:

- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]

Please review the above and let me know if you have any questions or need additional information.

I look forward to hearing from you. Feel free to reply to this message or schedule a call.

Best regards
zcir6

Formal Version

Formal Version

Date: {{date}}
Prepared by: {{cursor}}

Summary:
[Brief overview of formal version]

Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]

Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]

Next Steps:
[Description of what happens next]

Notes:
[Additional context or considerations]
zcir7

Friendly Response

Hi {{cursor}},

Quick update on friendly response:

[Key information]

Let me know if you have any questions.

Best
zcir8

Brief Update

Brief Update

Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}

Description:
[Detailed description of brief update]

Key Points:
- [Point 1]
- [Point 2]
- [Point 3]

Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]

Notes:
[Additional information]
zcir9

Detailed Template

Hi {{cursor}},

Thank you for reaching out regarding detailed template.

Here are the key details:

- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]

Please review the above and let me know if you have any questions or need additional information.

Please let me know if you have any questions or if there is anything else I can help with.

Best regards

When to use this template

Customize for your workflow

Common questions

When do I notify regulators or customers about a breach?

Per applicable regulations (GDPR is 72 hours; varies elsewhere). Get legal involved early; the notification timeline is often the most important compliance question.

Public statement before or after notifying affected users?

Affected users first when possible. They shouldn't learn from press. Coordinate timing with legal and comms — sometimes simultaneous is the only option.

Related reading

More Cybersecurity Templates

Use these snippets in TypeFire

Download the template pack, drop the .md files into your TypeFire snippets folder, and start expanding with abbreviations instantly.

Get TypeFire Free