HackingOtherCustomer Data InvolvedDelayed DiscoveryMedium

American Symphony Orchestra League

bd_1cf2ac69ba17738b · schema v1 · pii pii-v1

Severity

Medium

Discovered

Aug 1, 2020

Filed

Oct 5, 2020

To disclose

9 weeks

Affected · nationwide

49,063186 in this filing

Linked

2 filings

Confidence

65%

Full breach record for American Symphony Orchestra League →5 incidents on file

American Symphony Orchestra League, a non-profit organization, reported a data breach affecting 49,063 individuals. The breach, described as an external system breach (hacking), occurred on May 1, 2020, and was discovered on August 1, 2020. Affected individuals were notified electronically on October 5, 2020.

J jump to incidentP pin to compareR raw source

Maine clockDiscovered Aug 1, 2020 → Filed with AG Oct 5, 202065d ⏱ ME AG >30d9 weeks discovery → filing

⚠ unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.

Incident timeline

undetected · 92 days

discovery → filing · 9 weeks / 65 days

May 1, 2020

Begins

Aug 1, 2020

Discovered

Oct 5, 2020

Filed

vs. sector median

+3 wks slower

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

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Oregon State AGbd_788f208c543bd7c82020-10-05Candidate

Name: American Symphony Orchestra League
norm: american symphony orchestra league
Domain: americanorchestras.org

Name: American Symphony Orchestra League
norm: american symphony orchestra league
Domain: americanorchestras.org
Industry: Otherllm

Discovered: Aug 1, 2020
Breach occurred: May 1, 2020
Undetected for: 92 daysoccurrence → discovery
Materiality determined: —
Notification sent: Oct 5, 2020
Affected individuals: 49,063state + nationwide
Data types: —
Attack vector: Unauthorized Access
Threat actor: External

During the incident: Sent electronic notification to affected individuals
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 9 weeks(65 days from discovery to filing)
Compliance flags: ME AG >30d · 65d
Discovery-date grounding: unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.
Clock breakdown: Statute Window Elapsed Threshold Status
Maine
Discovered: Aug 1, 2020
→ Filed with AG: Oct 5, 2020
65d 30 days (soft) ME AG >30d

Statute	Window	Elapsed	Threshold	Status
Maine	Discovered: Aug 1, 2020 → Filed with AG: Oct 5, 2020	65d	30 days (soft)	ME AG >30d

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings · 2 states

View merged incident ↗

Oregon State AGOct 5 · first

Maine State AGOct 5 · 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://www.maine.gov/agviewer/content/ag/985235c7-cb95-4be2-8792-a1252b4f8318/e8eda50c-b696-4a67-bbce-6d23976191aa.shtml
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Oct 5, 2020
Raw hash: aa91629f12c722185fedbe5219ae6e1a1826ad99c1740a67e8314793b69edd33

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityAmerican Symphony Orchestra League

Victim entityAmerican Symphony Orchestra League

Incidentdiscovered Aug 1, 2020

Stated responseSent electronic notification to affected individuals

ComplianceME AG >30d

Extraction provenanceno artifact recorded

Source provenancewww.maine.gov