HackingTechnologyManufacturingInformationTargetedPIIIdentity (basic)LowContained

Elbit Systems of America, LLC

bd_81bbd31d9b03ac6c · schema v1 · pii pii-v1

Severity

Low

Discovered

Jun 8, 2022

Filed

Mar 29, 2023

To disclose

42 weeks

Affected

1state residents only

Linked

5 filings

Confidence

65%

Full breach record for Elbit Systems of America, LLC →2 incidents on file

Elbit Systems of America, LLC notified Montana residents of a June 8, 2022 cyber incident where an unknown actor gained unauthorized access to the network. Personal information may have been impacted. The company shut down its network, engaged forensic investigators, notified law enforcement, and offered credit monitoring services.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 42 weeks / 294 days

Jun 8, 2022

Begins

Jun 8, 2022

Discovered

Mar 29, 2023

Filed

vs. sector median

+23 wks slower

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteblack_bastabd_f937459b0a5f62212022-06-26 · +276dVerified by operator

Regulatory filings (3) · sorted by filing gap

Massachusetts State AGbd_833edd4bf302e7b72023-04-03 · +5dVerified by operator
Indiana State AGbd_e8241aea71ae62a42023-04-03 · +5dVerified by operator
Maine State AGbd_d5f9ac72010bea502022-09-25 · +185dVerified

Name: Elbit Systems of America, LLC
norm: elbit systems of america

Name: Elbit Systems of America, LLC
norm: elbit systems of america
Industry: TechnologyllmManufacturingllm

Discovered: Jun 8, 2022
Breach occurred: Jun 8, 2022
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 16, 2023
Affected individuals: 1state-resident count only
Data types: PIIIdentity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1078 Valid Accounts
Threat actor: External
Regulator citations: Notified law enforcement
Initial access: exploit_public_facing

During the incident: Shut down network
Engaged a leading cybersecurity firm to assist with safely restoring operations and to investigate the incident
Notified law enforcement and is cooperating with the resulting investigation
Offering complimentary credit and identity monitoring and recovery services for 12 or 24 months through IDX
Changes made: Taking steps to protect against a similar incident from occurring in the future
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Maine State AGSep 25 · first

Montana State AG+185d · this page

Massachusetts State AG+190d

Indiana State AG+190d

Pattern: first filing Sep 25 (ME), last Apr 3 (IN) — a 190-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://dojmt.gov/wp-content/uploads/OCP/Consumer-notification-letter-147.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 29, 2023
Raw hash: cc62c3abd3566cf76db39648029988e391cd79e597cb8ae038db6f75425330b9

Linked disclosures

Ransomware claims (1)

Regulatory filings (3) · sorted by filing gap

Reporting entityElbit Systems of America, LLC

Victim entityElbit Systems of America, LLC

Incidentdiscovered Jun 8, 2022

Stated responseShut down network

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov