Handle a law-enforcement or subpoena request
An inbound legal demand is a preservation and routing problem before it is a disclosure problem.
The organisation's job is to stop the relevant evidence degrading, verify who is asking, and hand
the question to counsel — not to decide scope on the spot.
Procedure
- Log the request on arrival with the receiving channel, the requester, and the exact identifier
of what was asked for. This timestamp starts every later clock.
printf '%s,%s,%s,%s\n' "$(date -u +%FT%TZ)" "$REQUESTER" "$CASE_REF" "$SCOPE" \
>> legal-requests.log
Preserve immediately and broadly, then narrow later. Snapshot the accounts, transaction
records, and any linked identifiers named, and record what was preserved:
aws s3api put-object --bucket compliance-archive --key "hold/$CASE_REF/manifest.json" \
--body hold-manifest.json --metadata legal-hold=true
Preservation is cheap and reversible; deletion is not. Never let a routine retention job expire
data under a hold.
Verify the legal instrument before producing anything: who issued it, under what authority, in
which jurisdiction, whether it is an order or a voluntary request, and whether it is valid on
its face. A screenshot of a document in an email is a request to be verified, not an order.
Route to counsel and, where required, to the designated law-enforcement response team.
Technical staff should not assess scope alone.
Apply the tipping-off rule: do not notify the customer, a colleague without a need to know, or
a third-party service that a request exists unless counsel directs otherwise.
Produce only what counsel approves, in the format they specify, with a transmittal that records
exactly what was disclosed and to whom.
Close the request with a record: instrument verified, counsel advice reference, what was
preserved, what was produced, and the date each step happened.
Pitfalls
- Deleting or letting retention expire data after receiving a request, which converts a
disclosure request into a spoliation problem.
- Producing records to whoever asks first, including a plausible-looking emailed demand or a
private party's civil subpoena with no legal basis for the data sought.
- Over-disclosing: answering a request for one account with a bundle that covers hundreds,
including data outside the instrument's scope.
- Letting an engineer answer a request directly to be helpful, bypassing counsel and the log.
- Failing to preserve metadata: a transfer list without timestamps, IPs and counterparties is not
the record that was asked for.
Verification
tail -n 3 legal-requests.log
aws s3api head-object --bucket compliance-archive --key "hold/$CASE_REF/manifest.json" \
| jq -r '.Metadata."legal-hold"'
A pass shows the request logged with a timestamp and a hold object present with the hold metadata
set, before any production.
Report the requester, the instrument and its verification status, the scope preserved, and what
counsel directed. Validating an instrument and deciding what may lawfully be disclosed is a legal
determination that only qualified counsel can make.
1---2name: handle-law-enforcement-and-subpoena-requests3description: Use when law enforcement, a regulator or a private party demands records covering customer data or an account, and you must preserve and route the request without over-disclosing.4metadata:5 source: https://skillmd.com/skills/jiayaoqijia/handle-law-enforcement-and-subpoena-requests6---78# Handle a law-enforcement or subpoena request910An inbound legal demand is a preservation and routing problem before it is a disclosure problem.11The organisation's job is to stop the relevant evidence degrading, verify who is asking, and hand12the question to counsel — not to decide scope on the spot.1314## Procedure15161. Log the request on arrival with the receiving channel, the requester, and the exact identifier17 of what was asked for. This timestamp starts every later clock.1819```20 printf '%s,%s,%s,%s\n' "$(date -u +%FT%TZ)" "$REQUESTER" "$CASE_REF" "$SCOPE" \21 >> legal-requests.log22```23242. Preserve immediately and broadly, then narrow later. Snapshot the accounts, transaction25 records, and any linked identifiers named, and record what was preserved:2627 aws s3api put-object --bucket compliance-archive --key "hold/$CASE_REF/manifest.json" \28 --body hold-manifest.json --metadata legal-hold=true2930 Preservation is cheap and reversible; deletion is not. Never let a routine retention job expire31 data under a hold.32333. Verify the legal instrument before producing anything: who issued it, under what authority, in34 which jurisdiction, whether it is an order or a voluntary request, and whether it is valid on35 its face. A screenshot of a document in an email is a request to be verified, not an order.36374. Route to counsel and, where required, to the designated law-enforcement response team.38 Technical staff should not assess scope alone.39405. Apply the tipping-off rule: do not notify the customer, a colleague without a need to know, or41 a third-party service that a request exists unless counsel directs otherwise.42436. Produce only what counsel approves, in the format they specify, with a transmittal that records44 exactly what was disclosed and to whom.45467. Close the request with a record: instrument verified, counsel advice reference, what was47 preserved, what was produced, and the date each step happened.4849## Pitfalls5051- Deleting or letting retention expire data after receiving a request, which converts a52 disclosure request into a spoliation problem.53- Producing records to whoever asks first, including a plausible-looking emailed demand or a54 private party's civil subpoena with no legal basis for the data sought.55- Over-disclosing: answering a request for one account with a bundle that covers hundreds,56 including data outside the instrument's scope.57- Letting an engineer answer a request directly to be helpful, bypassing counsel and the log.58- Failing to preserve metadata: a transfer list without timestamps, IPs and counterparties is not59 the record that was asked for.6061## Verification6263 tail -n 3 legal-requests.log64 aws s3api head-object --bucket compliance-archive --key "hold/$CASE_REF/manifest.json" \65 | jq -r '.Metadata."legal-hold"'6667A pass shows the request logged with a timestamp and a hold object present with the hold metadata68set, before any production.6970Report the requester, the instrument and its verification status, the scope preserved, and what71counsel directed. Validating an instrument and deciding what may lawfully be disclosed is a legal72determination that only qualified counsel can make.