HackingRetail & ConsumerRetailStolen CredentialsCustomer Data InvolvedIdentity (basic)LowContained

Asbury Automotive Group, Inc.

bd_1f650bcc4c18cb84 · schema v1 · pii pii-v1

Severity

Low

Discovered

Dec 25, 2023

Filed

Apr 24, 2024

To disclose

17 weeks

Affected

7state residents only

Linked

7 filings

Confidence

64%

Full breach record for Asbury Automotive Group, Inc. →2 incidents on file

Asbury Automotive Group notified affected individuals of unauthorized access to file servers on December 25, 2023. The incident involved access to files containing names and other personal data. The company engaged a cybersecurity firm, notified law enforcement, and offered complimentary identity monitoring services.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 17 weeks / 121 days

Dec 25, 2023

Begins

Dec 25, 2023

Discovered

Apr 24, 2024

Filed

vs. sector median

+10 wks slower

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitecactusbd_61315dea1c4d6b6d2024-01-12 · +102dVerified by operator

Regulatory filings (5) · sorted by filing gap

Maine State AGbd_128bda9c925acce52024-04-24Candidate
New Hampshire State AGbd_2f4692a880bce6542024-04-24Verified
Vermont State AGbd_4ddce7a31b86d2c52024-04-24Verified
Indiana State AGbd_92252072357742dd2024-04-24Verified

Show 1 more filing ↓

Massachusetts State AGbd_ea73e323df49c9f52024-04-24Verified

Name: Asbury Automotive Group, Inc.
norm: asbury automotive
Domain: asburyauto.com

Name: Asbury Automotive Group, Inc.
norm: asbury automotive
Domain: asburyauto.com
Industry: Retail & Consumerllm

Discovered: Dec 25, 2023
Breach occurred: Dec 25, 2023
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 25, 2024
Affected individuals: 7state-resident count only
Data types: Identity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: External
Initial access: valid_credentials

During the incident: Implemented our incident response plan
Took steps to contain the activity
Launched an investigation
Engaged a cybersecurity firm
Notified law enforcement
Changes made: Enhanced our existing security measures
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 6 states

View merged incident ↗

Maine State AGApr 24 · first

New Hampshire State AGApr 24 · first

Vermont State AGApr 24 · first

Indiana State AGApr 24 · first

Massachusetts State AGApr 24 · first

Montana State AGApr 24 · first · this page

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-1305.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 24, 2024
Raw hash: f6f808adfd487fe2bb7b6c4cf84cfab4676c33a28b27c26dfad3801357b294a8

Linked disclosures

Ransomware claims (1)

Regulatory filings (5) · sorted by filing gap

Reporting entityAsbury Automotive Group, Inc.

Victim entityAsbury Automotive Group, Inc.

Incidentdiscovered Dec 25, 2023

Stated responseImplemented our incident response plan

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov