AccidentalTechnologyInformationMisconfigurationDelayed DiscoveryCustomer Data InvolvedPIIIdentity (basic)EmploymentLowResolved

Front Rush, LLC

bd_68f8b1274e1cf10a · schema v1 · pii pii-v1

Severity

Low

Discovered

Jan 5, 2020

Filed

Jul 28, 2020

To disclose

29 weeks

Affected

163state residents only

Linked

6 filings

Confidence

65%

Full breach record for Front Rush, LLC →

Front Rush, LLC notified affected individuals of a data breach involving a publicly accessible AWS S3 bucket. The bucket was accessible from January 18, 2016, to January 8, 2020. The data included names and personal information of student-athletes and their families. Front Rush secured the bucket, engaged forensic investigators, and offered credit monitoring services.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 1448 days

discovery → filing · 29 weeks / 205 days

Jan 18, 2016

Begins

Jan 5, 2020

Discovered

Jul 28, 2020

Filed

vs. sector median

+11 wks slower

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

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

California State AGbd_09111982c3df17bb2020-07-28Verified
Oregon State AGbd_2e6b95638e8361dc2020-07-28Candidate
Washington State AGbd_54b5fe5337da06f22020-07-28Verified
Massachusetts State AGbd_77262271d4644e262020-07-28Verified

Show 1 more filing ↓up to 1d gap

Indiana State AGbd_2b3fd85825d4af232020-07-27 · +1dVerified

Name: Front Rush, LLC
norm: front rush

Name: Front Rush, LLC
norm: front rush
Industry: Technologyllm

Discovered: Jan 5, 2020
Breach occurred: Jan 18, 2016 – Jan 8, 2020
Undetected for: 1,448 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jun 15, 2020
Affected individuals: 163state-resident count only
Data types: PIIIdentity (basic)Employment
Attack vector: Misconfiguration
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Threat actor: External
Regulator citations: Notifying state regulatory authorities, where required

During the incident: Immediately commenced an investigation, working with third-party forensic investigators
Reconfigured and secured the S3 bucket to ensure it was no longer publicly accessible
Launched an in-depth investigation to determine the nature and scope of the incident
Notified its customer institutions
Reviewed its existing policies and procedures to ensure the security of information in its systems
Offering complimentary access to identity monitoring, fraud consultation and identity theft restoration services through TransUnion
Changes made: Reviewed its existing policies and procedures to ensure the security of information in its systems
Continuing to work to further secure the information in its systems going forward
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 29 weeks(205 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 ↗

Indiana State AGJul 27 · first

California State AG+1d

Oregon State AG+1d

Washington State AG+1d

Massachusetts State AG+1d

Montana State AG+1d · 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/Front-Rush-Consumer-ltr.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 28, 2020
Raw hash: 729b7f2626281f12b81b404db94cec22d7a2c519328e614db1787af95ab3ae01

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityFront Rush, LLC

Victim entityFront Rush, LLC

Incidentdiscovered Jan 5, 2020

Stated responseImmediately commenced an investigation, working with third-party forensic investigators

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov