PIVTR-D
RScenario

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.

First moves
  1. Read the commitment: which data, what it allows, and its notification terms. Record the time the deadline started.Legal advisor
  2. Identify who or what accessed or received the data, and where the access came from or the copy went.Intelligence/Investigations
  3. Check exception, ticket and break-glass records before treating the access as unapproved.Liaison
  4. Close the access path if it is still open: suspend the account, correct the policy, stop the replication or revoke the export.Operations
  5. 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 boundaryEffect on the response
A contract, regulation or government agreement sets itThe agreement may define the incident, the deadline and who gets notified. Read it before scoping.
An approved exception may cover the accessCheck exception and break-glass records before treating the access as unapproved
The data is encrypted with keys kept inside the boundaryKey usage logs can show whether anyone outside the boundary could read it
Where the data did not go matters as much as where it wentScope needs logs that cover the whole boundary, including egress and replication
An independent monitor or auditor oversees the boundaryTheir notice terms go into the plan, and they may ask for the evidence

First questions

#ItemOwner
1Identify the data, the commitment that covers it, and what the commitment allowsLegal advisor
2Identify who or what accessed or received the data: a person, a service account, a pipeline or a partnerIntelligence/Investigations
3Find where the access came from or the copy went: country, region, network or tenantIntelligence/Investigations
4Check whether an approved exception, ticket or break-glass record covers itLiaison
5Check whether it is still happeningOperations
6Record the commitment's notification terms and deadline, and the time the deadline startedLegal advisor

Scope

#ItemOwner
1Pull data access logs from every store that contains the data, with the identity, source address and location of each readIntelligence/Investigations
2Pull key management logs for the keys protecting the data: every decrypt, by whom and from whereIntelligence/Investigations
3Compare replication, backup and export settings with the approved design, and list every copy outside the boundaryOperations
4Check egress and flow logs for transfers to destinations outside the boundaryIntelligence/Investigations
5Pull identity records for each person involved: role, location and approval to access the dataLiaison
6Find downstream copies: caches, analytics tables, logs, tickets and chat messages that picked up the dataOperations
7Set the window from the first possible access to containment, and confirm log retention covers the whole windowPlanning

Contain

#ItemOwner
1Close the access path: suspend the account, correct the policy, stop the replication or revoke the exportOperations
2Preserve evidence, as in Evidence collection, before deleting any copy outside the boundaryIntelligence/Investigations
3Delete the copies outside the boundary, and record and verify each deletionOperations
4If key material or decrypt rights were exposed, rotate the keysOperations
5Add an alert for the same path, so a repeat pages someoneIntelligence/Investigations
6Record the decision in T3 Containment decision recordPlanning

Report

Deadlines in common regimes are in notification deadlines. The commitment itself may set a shorter one.

#ItemOwner
1After the Legal advisor's review, send notice to every party the commitment names by its deadline, with one T17 per regimeLegal advisor
2Keep facts apart from assessments in each report, and state what is still unknownPlanning
3Keep every version sent in the incident record with its recipientsPlanning
4When privacy law or the commitment requires it, notify affected individuals with T16Legal advisor
5Give the monitor or auditor the evidence they ask forLiaison

Fix the cause

#ItemOwner
1Find the cause: a missing control, a wrong configuration, an unclear approval process or deliberate misuseIntelligence/Investigations
2Add a preventive control where a detective one failed, such as a policy that blocks replication outside approved regionsOperations
3Review standing access to the data, person by personLiaison
4Brief the staff who handle the data on the boundary and the exception processLiaison
Watch out
  • 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.
Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.