MalwareProfessional ServicesProfessional ServicesRansomwareRansom DemandedData EncryptedIdentity (basic)Government IDMediumContained

Oostra Rouw & Associates, Inc. (ORA, Inc.)

bd_fb463aebcaf31b15 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Dec 26, 2019

Filed

Jan 31, 2020

To disclose

5 weeks

Affected

1state residents only

Linked

3 filings

Confidence

64%

Full breach record for Oostra Rouw & Associates, Inc. (ORA, Inc.) →

Oostra Rouw & Associates, Inc., a tax preparation firm, notified clients of a ransomware attack on December 26, 2019. While no data theft was confirmed, sensitive PII (names, SSNs, addresses) was present on affected systems. The company engaged third-party forensic experts, notified law enforcement and the IRS, and is strengthening system security.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 5 weeks / 36 days

Dec 26, 2019

Begins

Dec 26, 2019

Discovered

Jan 31, 2020

Filed

vs. sector median

14 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

Indiana State AGbd_5af082b7a4cb8bb62020-01-24 · +7dVerified
Washington State AGbd_f5b9de6c383f0b592020-01-24 · +7dCandidate

Name: Oostra Rouw & Associates, Inc. (ORA, Inc.)
norm: oostra rouw associates inc ora

Name: Oostra Rouw & Associates, Inc. (ORA, Inc.)
norm: oostra rouw associates inc ora
Industry: Professional Servicesllm

Discovered: Dec 26, 2019
Breach occurred: Dec 26, 2019
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jan 24, 2020
Affected individuals: 1state-resident count only
Data types: Identity (basic)Government ID
Data elements: Social Security number
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for Impact
Threat actor: ExternalFinancial
Regulator citations: Notified law enforcementNotified the IRS

During the incident: Engaged a third-party security expert to conduct an independent assessment of the incident
Notified law enforcement and the IRS of the incident
Providing all relevant regulatory notices
Changes made: Taking steps to confirm and further strengthen the security of our systems moving forward
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 5 weeks(36 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 ↗

Indiana State AGJan 24 · first

Washington State AGJan 24 · first

Montana State AG+7d · this page

Pattern: first filing Jan 24 (IN), last Jan 31 (MT) — a 7-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/OCP/Breach-NotificationDetails-110.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jan 31, 2020
Raw hash: 24ab30c0bd9144d400d94c3539b6b0932822f809eeffd19bc39a2efe3f73e241

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityOostra Rouw & Associates, Inc. (ORA, Inc.)

Victim entityOostra Rouw & Associates, Inc. (ORA, Inc.)

Incidentdiscovered Dec 26, 2019

Stated responseEngaged a third-party security expert to conduct an independent assessment of the incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov