Maryland breach notification lookup
Use this Maryland breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for Maryland: 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 | Md. Code, Com. Law § 14-3504 | Link the decision record to the official citation |
| Deadline | Owner/licensee resident notice as soon as reasonably practicable and no later than 45 days after discovery or notification of the breach when notice is required; a service provider that maintains data it does not own or license must notify the owner/licensee as soon as practicable and no later than 10 days. | Sort multi-state response work by the shortest stated clock |
| Residents | Maryland residents whose personal information was, or is reasonably believed to have been, acquired by an unauthorized person after a good-faith investigation determines likely misuse, unless a documented no-notice determination applies. | Identify whether affected residents receive notice |
| Regulator | Notify the Maryland Office of the Attorney General before giving resident notice; include the number of affected Maryland residents, when and how the breach occurred, response steps, and the sample notice or form of notice to residents. | Record AG or regulator portal review |
| Consumer-reporting agencies | Maryland resident notices must include toll-free numbers and addresses for the major consumer reporting agencies; the reviewed statute does not add a separate statewide consumer-reporting-agency filing threshold beyond those resident-notice content requirements. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | Maryland requires a business to notify the Office of the Attorney General before sending required notices to affected Maryland residents, including resident count, breach description, response steps, and the form or sample of resident notice. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
Maryland fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
Md. Code, Com. Law § 14-3504 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
Maryland requires a business to notify the Office of the Attorney General before sending required notices to affected Maryland residents, including resident count, breach description, response steps, and the form or sample of resident 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 Maryland 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 Maryland, 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 Maryland 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 Maryland 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 Maryland?
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.