HackingRetail & ConsumerRetailStolen CredentialsCapture Stored DataTargetedData ExfiltratedPCIFinancial accountIdentity (basic)LowResolved

Brooks Brothers Group, Inc.

bd_bbf08a8f8865dd5a · schema v1 · pii pii-v1

Severity

Low

Discovered

Apr 24, 2017

Filed

May 12, 2017

To disclose

18 days

Affected

Not disclosed

Linked

4 filings

Confidence

70%

Full breach record for Brooks Brothers Group, Inc. →

Brooks Brothers reported a cybersecurity incident involving skimmers installed on point-of-sale systems at select US and Puerto Rico locations between April 2016 and March 2017. The breach compromised payment card data (account numbers, expiration dates, CVVs) for an unknown number of customers. The incident was discovered in April 2017, law enforcement was notified, and forensic experts were engaged. The matter is resolved.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 385 days

discovery → filing · 18 days

Apr 4, 2016

Begins

Apr 24, 2017

Discovered

May 12, 2017

Filed

vs. sector median

6 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

California State AGbd_008ccb98190916df2017-05-12Verified
New Hampshire State AGbd_dfe8272f79490f612017-05-11 · +1dVerified
South Carolina State AGbd_586bd05269b039fd2017-05-17 · +5dVerified

Name: Brooks Brothers Group, Inc.
norm: brooks brothers

Name: Brooks Brothers Group, Inc.
norm: brooks brothers
Industry: Retail & Consumerllm

Discovered: Apr 24, 2017
Breach occurred: Apr 4, 2016 – Mar 1, 2017
Undetected for: 385 daysoccurrence → discovery
Materiality determined: —
Notification sent: May 12, 2017
Affected individuals: Not disclosed
Data types: PCIFinancial accountIdentity (basic)
Data elements: Financial account numberName
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 300-399dexposure 300-399d
WA-stated discovery: Found after the fact
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1056 Input CaptureT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Notified Washington Office of the Attorney General
Initial access: exploit_public_facing

During the incident: Engaged outside data forensic experts to assist in investigating and remediating the situation
Contacted law enforcement and will continue to cooperate in their investigation
Changes made: Initiated an internal review
Engaged independent forensic experts to assist in the investigation and remediation of our systems
Continuing to review and enhance our security measures moving forward
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 18 days(18 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 ↗

New Hampshire State AGMay 11 · first

California State AG+1d

Washington State AG+1d · this page

South Carolina State AG+6d

Pattern: first filing May 11 (NH), last May 17 (SC) — 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://agportal-s3bucket.s3.amazonaws.com/databreach/BreachM9700.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 12, 2017
Raw hash: ab3506053b274f7de5e174045458ae0370209aa1879e48b91b09a70a8d09ee1a

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityBrooks Brothers Group, Inc.

Victim entityBrooks Brothers Group, Inc.

Incidentdiscovered Apr 24, 2017

Stated responseEngaged outside data forensic experts to assist in investigating and remediating the situation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com