HackingTechnologyInformationCustomer Data InvolvedHigh

Brightly Software, Inc.

bd_e09583e9f0cc1903 · schema v1 · pii pii-v1

Severity

High

Discovered

Apr 28, 2023

Filed

May 11, 2023

To disclose

13 days

Affected · nationwide

2,964,29211,486 in this filing

Linked

5 filings

Confidence

50%

Full breach record for Brightly Software, Inc. →2 incidents on file

Brightly Software, Inc. reported an external system breach that occurred on April 20, 2023, and was discovered on April 28, 2023. The breach impacted 11,486 residents of Maine. The company began notifying affected individuals electronically on May 11, 2023. No identity theft protection services were offered.

J jump to incidentP pin to compareR raw source

Maine clockDiscovered Apr 28, 2023 → Filed with AG May 11, 202313d ✓ ME AG ≤30d13 days discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 8 days

discovery → filing · 13 days

Apr 20, 2023

Begins

Apr 28, 2023

Discovered

May 11, 2023

Filed

vs. sector median

17 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Washington State AGbd_3c2dcee5e907b8382023-05-11Verified
California State AGbd_56e0a48129bd1e6c2023-05-11Candidate
Delaware State AGbd_818f02162898a1642023-05-11Verified
Oregon State AGbd_eb246d4714ee3ae42023-05-11Verified

Name: Brightly Software, Inc.
norm: brightly software

Name: Brightly Software, Inc.
norm: brightly software
Industry: Technologyllm

Discovered: Apr 28, 2023
Breach occurred: Apr 20, 2023
Undetected for: 8 daysoccurrence → discovery
Materiality determined: —
Notification sent: May 11, 2023
Affected individuals: 2,964,292state + nationwide
Data types: —
Attack vector: Unauthorized Access

During the incident: Notified affected customers and users.
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 13 days(13 days from discovery to filing)
Compliance flags: ME AG ≤30d · 13dME CRA notice due
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.
Clock breakdown: Statute Window Elapsed Threshold Status
Maine
Discovered: Apr 28, 2023
→ Filed with AG: May 11, 2023
13d 30 days ME AG ≤30d

Statute	Window	Elapsed	Threshold	Status
Maine	Discovered: Apr 28, 2023 → Filed with AG: May 11, 2023	13d	30 days	ME AG ≤30d

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Washington State AGMay 11 · first

California State AGMay 11 · first

Delaware State AGMay 11 · first

Oregon State AGMay 11 · first

Maine State AGMay 11 · 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/5da35692-18a7-4cdf-acbe-5fe1a955e406.shtml
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 11, 2023
Raw hash: 98f6177508ad2987f48f0eb4b054aa4e8ac7ad17c9bba0bfdc015c1398f03288

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityBrightly Software, Inc.

Victim entityBrightly Software, Inc.

Incidentdiscovered Apr 28, 2023

Stated responseNotified affected customers and users.

ComplianceME AG ≤30d

Extraction provenanceno artifact recorded

Source provenancewww.maine.gov