TRUST ATLAS WORKSHEET
Incident assessment
Mexico LFPDPPP · Step 4 · Secure data and notify significant incidents- Who prepares it
- Security + responsible party
- When to prepare it
- Ongoing and upon qualifying incidents
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Incident ID
- INC-041
- Awareness and facts
- 2026-11-13 09:20 UTC. Export link exposed to an unauthorized account.
- Scope and uncertainty
- One confirmed access. Log review for further recipients in progress.
- Decision and reason
- Privacy lead to assess reporting threshold with counsel by 10:30 UTC.
- Actions and status
- Access revoked, logs preserved, next review at 12:00 UTC.
Gather first
- Alert or breach report
- Investigation facts and relevant thresholds
- Escalation contacts and official reporting clocks
How to prepare it
- Start a case with UTC timestamps for detection, awareness, assessment and containment. Keep known facts separate from estimates and update both as evidence changes.
- Identify affected systems, people, data and likely harms. Link your classification, notice decision and the rule that starts each clock.
- Record containment, preservation, escalation and notification actions. Capture who approved the decision and set a time to confirm outstanding facts.
Review
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Handoff
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.