AccidentalTechnologyFinancial ServicesInformationMisconfigurationCustomer Data InvolvedIdentity (basic)Government IDFinancial accountMediumContained

Vertafore

bd_0b6fb2d524526bb7 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Nov 30, 2020

Filed

Jun 16, 2021

To disclose

28 weeks

Affected

607state residents only

Linked

5 filings

Confidence

67%

Full breach record for Vertafore →

Vertafore discovered a configuration error in its QQCatalyst product on November 30, 2020, leading to unauthorized public access to reports, forms, and potentially insurance applications. Impacted data included names, addresses, birthdates, driver's license numbers, and potentially SSNs and financial account info. Vertafore fixed the error, engaged forensic investigators, notified federal law enforcement, and offered one year of free identity monitoring via Kroll.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 28 weeks / 198 days

Nov 30, 2020

Discovered

Jun 16, 2021

Filed

vs. sector median

+10 wks slower

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

South Carolina State AGbd_8c3393904c1de7c72021-07-08 · +22dVerified
New Hampshire State AGbd_e05b9e1eb99587362021-07-09 · +23dVerified
Montana State AGbd_46b0579fff296ea12021-08-09 · +54dVerified
New Hampshire State AGbd_b417a50418164b432021-09-23 · +99dVerified

Name: Vertafore
norm: vertafore

Name: Vertafore
norm: vertafore
Industry: TechnologyllmFinancial Servicesllm

Discovered: Nov 30, 2020
Materiality determined: —
Notification sent: —
Affected individuals: 607state-resident count only
Data types: Identity (basic)Government IDFinancial account
Attack vector: Misconfiguration
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Regulator citations: Reported the matter to U.S. federal law enforcement

During the incident: Fixed the configuration error and secured the potentially affected files
Engaged a leading security firm to search for evidence indicating potential misuse of the information
Reported the matter to U.S. federal law enforcement
Offering free identity monitoring services
Changes made: Working to further enhance security tools, policies and procedures, as well as security governance and staffing
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 3 states

View merged incident ↗

Montana State AGJun 16 · first · this page

South Carolina State AG+22d

New Hampshire State AG+23d

Montana State AG+54d

New Hampshire State AG+99d

Pattern: first filing Jun 16 (MT), last Sep 23 (NH) — a 99-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://dojmt.gov/wp-content/uploads/pattSamp.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 16, 2021
Raw hash: f2aa4e3d6a813a2d7ac866f96b9bf8da904932a112cccb4a7ec1c80570000f9d

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityVertafore

Victim entityVertafore

Incidentdiscovered Nov 30, 2020

Stated responseFixed the configuration error and secured the potentially affected files

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov