#
Maryland lacks a dedicated payments-sector operational-resilience statute equivalent to DORA; resilience obligations for payments/financial entities instead flow from the state's general data-breach notification law (PIPA), sector-specific insurance-carrier cybersecurity-event reporting rules, and an OFR-issued Emergency Preparedness Guide for state-chartered depository institutions.
Kept on Dataprotection.gi, not restated here: data and cloud switching obligations on service providers, including notice periods and charges. Open its jurisdiction pages on Dataprotection.gi →
Outlook
This module's trajectory is stable rather than escalating: absent a dedicated payments-resilience statute, Maryland's posture will continue to be read as an assembly of general breach law, sector-specific insurance rules, and the federal CIRCIA backstop, a structural gap relative to EU/UK peers that this monitor will keep tracking.
no periodic updates on record for this sub-brief
Sources and findings (5 unique sources · R-3/R-4)
- [W3-E1] T1 Derived: Confirmed in_forcehttps://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gcl§ion=14-3504&enactments=False&archived=False re-verified
A business that owns, licenses, or maintains computerized personal information of a Maryland resident must conduct a good-faith investigation upon a breach and, unless misuse is unlikely, notify affected individuals as soon as reasonably practicable but not later than 45 days after discovery.
A carrier must notify the Maryland Insurance Commissioner as promptly as possible but no later than 3 business days from determining a cybersecurity event involving nonpublic information has occurred, where Maryland is the state of domicile or the event has a reasonable likelihood of consumer harm.
OFR's Depository Supervision Unit, responsible for regulation, supervision, and examination of all Maryland-chartered banks, credit unions, and trust companies, maintains an Emergency Preparedness Guide (revised August 16, 2023) as part of its operational-resilience expectations.
- [W3-E4] T3 Derived: Probable in_forcehttps://www.mwe.com/insights/maryland-joins-growing-ranks-and-passes-its-own-consumer-data-privacy-law/ re-verified
MODPA requires controllers to conduct data protection assessments for processing activities presenting heightened risk of harm, including profiling that could result in unfair, abusive, or deceptive treatment, with data protection assessment requirements applying to processing on or after October 1, 2025.
- [W3-E5] T3 Derived: Probable in_forcehttps://pivitstrategy.com/maryland-cybersecurity-laws-you-should-know-2026/ re-verified
Under CIRCIA, critical infrastructure entities in Maryland must report substantial cyber incidents to the federal Cybersecurity and Infrastructure Security Agency (CISA) within 72 hours, layering a federal resilience backstop atop Maryland's state breach-notification regime.