AccidentalTechnologyInformationMisconfigurationCustomer Data InvolvedEmployee Data InvolvedIdentity (basic)Government IDEmploymentMediumResolved

AVALARA, INC.

bd_5377a486edec37a5 · schema v1 · pii pii-v1

Severity

Medium

Discovered

May 22, 2019

Filed

Jun 7, 2019

To disclose

16 days

Affected

Not disclosed

Linked

3 filings

Confidence

65%

Full breach record for AVALARA, INC. →2 incidents on file

Avalara, Inc. disclosed a data breach involving the eCompli software application, acquired from Compli, Inc. On May 22, 2019, a former Compli employee notified Avalara of a vulnerability that allowed unauthorized access to personal information of certain individuals at Avalara's customers. The exposed data included names, SSNs, driver's license numbers, dates of birth, and employment history. The third party deleted the accessed data and certified it was not shared. Avalara removed the vulnerability, investigated the scope, and offered credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 16 days

May 22, 2019

Begins

May 22, 2019

Discovered

Jun 7, 2019

Filed

vs. sector median

16 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Montana State AGbd_9f77ce9ab4c656e02019-06-02 · +5dCandidate
New Hampshire State AGbd_48ed1e38290146102019-06-13 · +6dVerified

Name: AVALARA, INC.
norm: avalara

Name: AVALARA, INC.
norm: avalara
Industry: Technologyllm

Discovered: May 22, 2019
Breach occurred: May 22, 2019
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)Government IDEmployment
Attack vector: Misconfiguration
Threat actor: External
Third party: via Compli, Inc. employee
Initial access: exploit_public_facing

During the incident: Promptly conducted an investigation to determine the scope of the incident
Confirmed that the vulnerability was removed on May 22, 2019
Took all reasonable and appropriate actions to ensure that the security and integrity of our platform has been restored
Reviewed our security protocols and taken steps to address the security of the platform
Closely monitoring our platform to help protect against future unauthorized access
Offering a period of credit monitoring services at no cost
Changes made: Removed the vulnerability on May 22, 2019
Reviewed security protocols
Taken steps to address the security of the platform
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Montana State AGJun 2 · first

California State AG+5d · this page

New Hampshire State AG+11d

Pattern: first filing Jun 2 (MT), last Jun 13 (NH) — a 11-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://oag.ca.gov/ecrime/databreach/reports/sb24-147956
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 7, 2019
Raw hash: 06c12f975af1a2b23d33696ea5a052070ef37fc6bfa6a23c56589bc7ea602695

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityAVALARA, INC.

Victim entityAVALARA, INC.

Incidentdiscovered May 22, 2019

Stated responsePromptly conducted an investigation to determine the scope of the incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov