Restricted data accessed outside approved boundaries
Data under a residency, contract or government commitment was read, copied or processed outside its approved boundary. Read the commitment and record when its notification deadline started. Preserve the evidence of where the data went before deleting any stray copy.
- Read the commitment: which data, what it allows, and its notification terms. Record the time the deadline started.Legal advisor
- Identify who or what accessed or received the data, and where the access came from or the copy went.Intelligence/Investigations
- Check exception, ticket and break-glass records before treating the access as unapproved.Liaison
- Close the access path if it is still open: suspend the account, correct the policy, stop the replication or revoke the export.Operations
- Preserve evidence as in Evidence collection before deleting any copy outside the boundary.Intelligence/Investigations
Then work the page: First questions, Scope, Contain, Report, Fix the cause.
Some data may be stored, processed or read only inside set boundaries: a country or region, a named set of systems, a cleared group of people, or a partner's environment under a legal agreement. Data residency commitments, export controls, government contracts and privacy law all create such boundaries. An incident here is any access, copy or processing outside the boundary, whether by an attacker, an insider or a pipeline configured wrong.
Many of these incidents involve no attacker. A support engineer in an unapproved country opens a record, a replication job copies a table to the wrong region, or an analytics export lands in a shared bucket. The duty to report can apply anyway, so the Legal advisor rates the incident before anyone calls it minor.
This scenario is an addition to the book. It builds on the phase playbooks for scope, contain, eradicate and recover, and on the insider and cloud scenarios.
What is different
| Fact about the boundary | Effect on the response |
|---|---|
| A contract, regulation or government agreement sets it | The agreement may define the incident, the deadline and who gets notified. Read it before scoping. |
| An approved exception may cover the access | Check exception and break-glass records before treating the access as unapproved |
| The data is encrypted with keys kept inside the boundary | Key usage logs can show whether anyone outside the boundary could read it |
| Where the data did not go matters as much as where it went | Scope needs logs that cover the whole boundary, including egress and replication |
| An independent monitor or auditor oversees the boundary | Their notice terms go into the plan, and they may ask for the evidence |
First questions
| # | Item | Owner |
|---|---|---|
| 1 | Identify the data, the commitment that covers it, and what the commitment allows | Legal advisor |
| 2 | Identify who or what accessed or received the data: a person, a service account, a pipeline or a partner | Intelligence/Investigations |
| 3 | Find where the access came from or the copy went: country, region, network or tenant | Intelligence/Investigations |
| 4 | Check whether an approved exception, ticket or break-glass record covers it | Liaison |
| 5 | Check whether it is still happening | Operations |
| 6 | Record the commitment's notification terms and deadline, and the time the deadline started | Legal advisor |
Scope
| # | Item | Owner |
|---|---|---|
| 1 | Pull data access logs from every store that contains the data, with the identity, source address and location of each read | Intelligence/Investigations |
| 2 | Pull key management logs for the keys protecting the data: every decrypt, by whom and from where | Intelligence/Investigations |
| 3 | Compare replication, backup and export settings with the approved design, and list every copy outside the boundary | Operations |
| 4 | Check egress and flow logs for transfers to destinations outside the boundary | Intelligence/Investigations |
| 5 | Pull identity records for each person involved: role, location and approval to access the data | Liaison |
| 6 | Find downstream copies: caches, analytics tables, logs, tickets and chat messages that picked up the data | Operations |
| 7 | Set the window from the first possible access to containment, and confirm log retention covers the whole window | Planning |
Contain
| # | Item | Owner |
|---|---|---|
| 1 | Close the access path: suspend the account, correct the policy, stop the replication or revoke the export | Operations |
| 2 | Preserve evidence, as in Evidence collection, before deleting any copy outside the boundary | Intelligence/Investigations |
| 3 | Delete the copies outside the boundary, and record and verify each deletion | Operations |
| 4 | If key material or decrypt rights were exposed, rotate the keys | Operations |
| 5 | Add an alert for the same path, so a repeat pages someone | Intelligence/Investigations |
| 6 | Record the decision in T3 Containment decision record | Planning |
Report
Deadlines in common regimes are in notification deadlines. The commitment itself may set a shorter one.
| # | Item | Owner |
|---|---|---|
| 1 | After the Legal advisor's review, send notice to every party the commitment names by its deadline, with one T17 per regime | Legal advisor |
| 2 | Keep facts apart from assessments in each report, and state what is still unknown | Planning |
| 3 | Keep every version sent in the incident record with its recipients | Planning |
| 4 | When privacy law or the commitment requires it, notify affected individuals with T16 | Legal advisor |
| 5 | Give the monitor or auditor the evidence they ask for | Liaison |
Fix the cause
| # | Item | Owner |
|---|---|---|
| 1 | Find the cause: a missing control, a wrong configuration, an unclear approval process or deliberate misuse | Intelligence/Investigations |
| 2 | Add a preventive control where a detective one failed, such as a policy that blocks replication outside approved regions | Operations |
| 3 | Review standing access to the data, person by person | Liaison |
| 4 | Brief the staff who handle the data on the boundary and the exception process | Liaison |
- Deleting the stray copy first destroys the evidence of what was copied and when. Preserve, then delete.
- An incident with no attacker can still be reportable. The commitment decides, and the Legal advisor reads it.
- A quiet alert queue proves nothing. Show where the data went from logs that cover the whole boundary, and state any gap in coverage.