New Mexico breach notification lookup
Use this New Mexico breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for New Mexico: 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 | N.M. Stat. §§ 57-12C-6 and 57-12C-10 | Link the decision record to the official citation |
| Deadline | Resident and owner/licensee notice in the most expedient time possible and no later than 45 calendar days after discovery, subject to law-enforcement delay, scope/restoration needs, and the no-significant-risk exception; AG and consumer-reporting-agency notices for more than 1,000 residents are due within the same 45-day window. | Sort multi-state response work by the shortest stated clock |
| Residents | New Mexico residents whose personal identifying information is reasonably believed to have been subject to a security breach, unless an appropriate investigation determines the breach does not create significant risk of identity theft or fraud. | Identify whether affected residents receive notice |
| Regulator | Notify the New Mexico Attorney General when notification is required for more than 1,000 New Mexico residents from a single security breach, in the most expedient time possible and no later than 45 calendar days; include the number of New Mexico residents notified and a copy of the resident notice. Substitute notice also includes written notice to the Attorney General. | Record AG or regulator portal review |
| Consumer-reporting agencies | Notify major nationwide consumer reporting agencies when notification is required for more than 1,000 New Mexico residents from a single breach, in the most expedient time possible and no later than 45 calendar days. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | New Mexico requires Attorney General and nationwide consumer reporting agency notice when a single breach requires notice to more than 1,000 New Mexico residents; substitute notice also includes written notice to the Attorney General and major New Mexico media. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
New Mexico fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
N.M. Stat. §§ 57-12C-6 and 57-12C-10 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
New Mexico requires Attorney General and nationwide consumer reporting agency notice when a single breach requires notice to more than 1,000 New Mexico residents; substitute notice also includes written notice to the Attorney General and major New Mexico media. 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 New Mexico 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 New Mexico, 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 New Mexico 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 New Mexico 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 New Mexico?
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.