AccidentalFinancial ServicesFinanceMisdeliverySupply Chain (3P Vendor)Customer Data InvolvedIdentity (basic)Financial accountLowContained

NISSAN NORTH AMERICA, INC.

bd_c258d420d6a38fc6 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jun 21, 2022

Filed

Feb 9, 2023

To disclose

33 weeks

Affected

20state residents only

Linked

2 filings

Confidence

67%

Full breach record for NISSAN NORTH AMERICA, INC. →5 incidents on file

Nissan North America, Inc. notified the NH AG of a data event involving its third-party software provider, LumenData, Inc. On June 21, 2022, Nissan learned that customer data provided for testing was inadvertently exposed in a public cloud repository. The incident affected 20 NH residents, exposing names, DOBs, and NMAC account numbers. No SSNs or credit cards were involved. Notifications were sent on Dec 19, 2022, offering 1 year of credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 33 weeks / 233 days

Jun 21, 2022

Discovered

Feb 9, 2023

Filed

vs. sector median

+24 wks slower

This filing is one of 2 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Maine State AGbd_59c63d969aa13dbd2023-02-03 · +6dCandidate

Name: NISSAN NORTH AMERICA, INC.
norm: nissan north america

Name: NISSAN NORTH AMERICA, INC.
norm: nissan north america
Industry: Financial Servicesllm

Discovered: Jun 21, 2022
Materiality determined: —
Notification sent: Dec 19, 2022
Affected individuals: 20state-resident count only
Data types: Identity (basic)Financial account
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1195 Supply Chain CompromiseT1074 Data Staged
Threat actor: External
Regulator citations: Notified New Hampshire Attorney General Consumer Protection Bureau
Third party: via LumenData, Inc.
Initial access: supply_chain

During the incident: Ensured that LumenData contained the threat by disabling all unauthorized access to the data
Commenced a prompt and thorough investigation
Worked with LumenData to assure that it took steps to prevent events like this in the future
Worked very closely with external cybersecurity professionals experienced in handling these types of complex security incidents
Changes made: Continue to evaluate and modify practices and procedures, including those required of third-party service providers, to enhance the security and privacy of personal information
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 33 weeks(233 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings · 2 states

View merged incident ↗

Maine State AGFeb 3 · first

New Hampshire State AG+6d · this page

Pattern: first filing Feb 3 (ME), last Feb 9 (NH) — a 6-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://mm.nh.gov/files/uploads/doj/remote-docs/nissan-north-america-lumendata-20230209.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 9, 2023
Raw hash: e4beca4b6bf9b7bd04e08542e154bdb94689180bc6a9013eeeb5aaa8ce0a9991

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityNISSAN NORTH AMERICA, INC.

Victim entityNISSAN NORTH AMERICA, INC.

Incidentdiscovered Jun 21, 2022

Stated responseEnsured that LumenData contained the threat by disabling all unauthorized access to the data

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov