District of Columbia breach notification lookup
Use this District of Columbia breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for District of Columbia: statute citation, stated notification deadline, residents or regulators who may need notice, consumer-reporting-agency threshold, consumer-notice trigger, official source links, and the last verified date.
Last verified 2026-08-13. Not legal advice.
| Field | Verified value | Use in the incident file |
|---|---|---|
| Statute | D.C. Code §§ 28-3851 through 28-3853, including § 28-3852 | Link the decision record to the official citation |
| Deadline | Resident notice in the most expedient time possible and without unreasonable delay, subject to law-enforcement delay and scope/restoration needs; DC Attorney General notice for 50+ District residents no later than resident notice; consumer-reporting-agency notice without unreasonable delay for more than 1,000 persons. | Sort multi-state response work by the shortest stated clock |
| Residents | District residents whose personal information was included in the breach of the security system, subject to the statutory secure-data and no-likely-harm exceptions. | Identify whether affected residents receive notice |
| Regulator | Provide written notice to the DC Attorney General if the breach affects 50 or more District residents, in the most expedient manner possible, without unreasonable delay, and no later than when District resident notice is provided; include the statutory incident details and a sample resident notice. | Record AG or regulator portal review |
| Consumer-reporting agencies | Notify all nationwide consumer reporting agencies without unreasonable delay when more than 1,000 persons must be notified of a breach, unless the entity is already required to notify consumer reporting agencies under GLBA Title V. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | DC requires written notice to the Office of the Attorney General when a breach affects 50 or more District residents, no later than when resident notice is provided; if more than 1,000 persons are notified, nationwide consumer reporting agencies must also receive timing, distribution, and content notice. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
District of Columbia fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
D.C. Code §§ 28-3851 through 28-3853, including § 28-3852 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
DC requires written notice to the Office of the Attorney General when a breach affects 50 or more District residents, no later than when resident notice is provided; if more than 1,000 persons are notified, nationwide consumer reporting agencies must also receive timing, distribution, and content notice. The consumer trigger matters because the clock usually starts only after a legally meaningful incident analysis, not merely because an IT alert appeared.
The last verified date for this District of Columbia lookup is 2026-08-13. Use that date as a prompt to refresh counsel review before making a live notification decision.
How to use it during an incident
Start with containment and evidence preservation, then identify affected resident states and compare the shortest stated deadline first.
A practical incident file should record discovery time, encryption status, systems involved, affected consumer count, vendor involvement, and the person responsible for counsel review.
For District of Columbia, the WISP should say where the notification decision log lives, who contacts counsel, who checks the regulator portal, and who approves any consumer notice before it is sent.
This lookup pairs with the Incident Response Plan because the plan owns the workflow: intake, escalation, containment, preservation, notice analysis, communications, and final review.
How it fits the WISP
A WISP should not guess at state-law outcomes; it should make the breach-review path fast, documented, and source-linked.
Pair this lookup with the District of Columbia WISP requirements page so the firm's written program names the state-aware incident path before an event happens.
Policywright keeps the breach clock separate from the policy packet: the lookup tells you what to review, while the generated packet assigns owners, evidence records, remediation steps, and review cadence.
Not legal advice. A qualified lawyer should confirm whether the incident facts meet a statutory definition, whether substitute notice or regulator notice applies, and whether another state or federal rule changes the timeline.
FAQ
Is this District of Columbia lookup legal advice?
No. It is a source-linked lookup for incident planning and should be reviewed with qualified counsel before relying on it in a live notification decision.
What if affected residents live outside District of Columbia?
Use the multi-state lookup page and include every state where affected residents may live. The comparison table sorts selected states by the shortest stated deadline first.
Does this replace the FTC Safeguards Rule notice analysis?
No. State notice review is separate from the federal Safeguards Rule and 16 CFR 314.4(j) analysis. A serious incident file should preserve both review tracks.