Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Response Templates

Internal Security Alert

SUBJECT: SECURITY INCIDENT - [Type: Deepfake/Prompt Injection]

SEVERITY: [Critical/High/Medium/Low]
DISCOVERED: [Timestamp - ISO 8601]
IMPACT: [Description of affected systems/users]
ACTIONS: [What's being done immediately]
CONTACT: [Response team contact info]

---

INCIDENT DETAILS:
- Type: [Deepfake video/Audio deepfake/Prompt injection/etc]
- Platform: [Where discovered]
- Scope: [Number of users/systems affected]
- Evidence: [Links to evidence, preserved for forensics]

IMMEDIATE ACTIONS (0-2 hours):
1. Incident confirmed and documented
2. Affected systems isolated/monitored
3. Evidence preserved for forensic analysis
4. Stakeholders notified

NEXT STEPS (2-24 hours):
1. Forensic analysis underway
2. Platform takedown requests submitted
3. External communications being prepared
4. Recovery procedures initiated

CONTACT FOR QUESTIONS:
- Security Team: security@company.com
- Incident Commander: [Name/Contact]
- Legal: [Name/Contact]

External Public Statement

[Organization] is aware of [incident type] affecting [scope].

WHAT HAPPENED:
[Brief, factual description of the incident]

WHAT WE'RE DOING:
- Immediate containment and investigation
- Cooperation with platform providers for removal
- Enhanced security monitoring
- Support for affected individuals

WHAT YOU SHOULD DO:
- Do not share or amplify the content
- Report suspicious content to [platform/email]
- Monitor your accounts for unauthorized activity
- Contact us with questions: security@company.com

TIMELINE:
- [Time]: Incident discovered
- [Time]: Investigation began
- [Time]: Platforms notified
- [Time]: Public statement issued

We take this seriously and are committed to protecting our community.

Contact: security@company.com

Deepfake Incident Response (0-24 hours)

Hour 0-2: Contain

  1. Document everything (screenshots, URLs, timestamps)
  2. Alert security team immediately
  3. Preserve evidence (do not delete or modify)
  4. Identify affected individuals
  5. Assess platform (social media, email, etc.)

Hour 2-6: Assess

  1. Identify deepfake type (video, audio, image)
  2. Determine creation method if possible
  3. Assess damage and reach
  4. Identify all platforms where content appears
  5. Check for related incidents

Hour 6-24: Respond

  1. Submit takedown requests to platforms
  2. Contact platform trust & safety teams
  3. Issue internal and external statements
  4. Provide support to affected individuals
  5. Begin forensic analysis
  6. Notify law enforcement if applicable

Prompt Injection Incident Response

Immediate (0-1 hour)

  1. Isolate affected systems from network
  2. Review access logs and audit trails
  3. Identify scope of compromise
  4. Preserve evidence for forensics
  5. Alert security team

Short-term (1-24 hours)

  1. Patch identified vulnerabilities
  2. Reset compromised credentials
  3. Notify affected users
  4. Review system prompts for exposure
  5. Implement additional monitoring

Medium-term (1-7 days)

  1. Complete forensic analysis
  2. Implement preventive controls
  3. Conduct security training
  4. Update incident response procedures
  5. Document lessons learned

Crisis Communication Template

PHASE 1: INITIAL RESPONSE (First 2 hours)
- Acknowledge the incident
- Confirm investigation is underway
- Provide initial guidance to users
- Avoid speculation

PHASE 2: ONGOING UPDATES (2-24 hours)
- Share investigation progress
- Provide specific guidance
- Address public concerns
- Maintain transparency

PHASE 3: RESOLUTION (24+ hours)
- Explain what happened
- Detail preventive measures
- Provide support resources
- Commit to improvements

KEY MESSAGES:
1. We take security seriously
2. We're investigating thoroughly
3. We're protecting affected individuals
4. We're implementing improvements
5. We're committed to transparency

Recovery Checklist

  • ✅ All evidence collected and preserved
  • ✅ Forensic analysis completed
  • ✅ Root cause identified
  • ✅ Vulnerabilities patched
  • ✅ Systems restored to clean state
  • ✅ Credentials reset
  • ✅ Monitoring enhanced
  • ✅ Staff trained on incident
  • ✅ Procedures updated
  • ✅ Post-incident review completed
  • ✅ Stakeholders notified of resolution
  • ✅ Public statement issued (if applicable)