WA Data Breach Notifications - Security Intelligence avatar

WA Data Breach Notifications - Security Intelligence

Pricing

$2.00 / 1,000 wa data breach notification records

Go to Apify Store
WA Data Breach Notifications - Security Intelligence

WA Data Breach Notifications - Security Intelligence

Washington data-breach notifications (1,653, WA AG, 2017-present): breached organization, industry, cause (cyberattack / unauthorized access), attack type (ransomware / phishing), Washingtonians affected. Filter by industry, attack type, date or minimum affected; screen vendors and suppliers.

Pricing

$2.00 / 1,000 wa data breach notification records

Rating

0.0

(0)

Developer

Wenhao Yang

Wenhao Yang

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Categories

Share

WA Data Breach Notifications (wa-data-breach)

Pull Washington data-breach notifications - 1,653 breaches filed with the WA Attorney General (2015-present, free public open data). Every time a business, healthcare organization or government body discovers a breach affecting 500+ Washington residents, state law requires them to file one of these.

This is a security-intelligence feed: who got breached in WA, in what industry, by what kind of attack, and how many Washingtonians were exposed.

Built for security researchers, auditors, vendor-screening and supply-chain teams, insurance underwriters, journalists and market-intelligence users - the question "has this organization / this industry / this vendor ever had a WA data breach?" answered in one query.

What this data is

Each record is one breach notification:

FieldMeaning
nameThe breached organization
industryTypeBusiness / Health / Finance / Education / Government / Non-Profit/Charity
businessTypeFiner business category (e.g. Software, Medical)
breachCauseCyberattack / Unauthorized Access / Theft or Mistake
cyberAttackTypeRansomware / Malware / Phishing / Skimmers...
washingtoniansAffectedWA residents exposed (source also carries a range)
year / dateSubmittedWhen the notification was filed
daysToContainDays from discovery to containment (where known)

Note on scope: notifications are required at ~500+ WA residents affected, so this is the reportable tail of breaches, not every incident. It still shows the industry and attack-vector mix clearly (ransomware dominates; Health is the top non-Business industry).

Typical questions it answers

  • Ransomware victims in WA - filter cyberAttackType=Ransomware, sort by Washingtonians affected.
  • Healthcare breaches - filter industryType=Health (+ a yearFrom). 326 Health notifications on file.
  • Has this company ever reported a breach here? - filter name=... (e.g. "Premera", "Delta").
  • Large-impact incidents - minAffected=10000.
  • Newest activity - leave everything blank; you get the latest notifications first.

Inputs (all optional)

InputWhat it does
nameBreached organization (substring)
keywordsMatch across org name / industry / business type
industryTypeIndustry (Business / Health / Finance / Education / Government)
breachCauseCyberattack / Unauthorized Access / Theft or Mistake
cyberAttackTypeAttack type (substring: Ransomware, Phishing, ...)
minAffectedAt least N Washingtonians affected
yearFrom / yearToNotification-year range
maxResultsCap records (default 200)

Low cost & full coverage

$0.002 per record returned, with a per-run charge cap so no surprise bills.

Every breach notification on file is in the dataset - the full 1,653 reportable breaches (2015-present). Runs scan the whole set and return exactly what matches your filters. One source quirk handled for you: the dataset's own year field is the state fiscal year of reporting, which runs ahead of the real filing date (a breach filed in Aug 2026 can be stamped 2027), so all date filtering here runs off the actual submission date rather than the label that would silently mislead a naive pull.

Data source & freshness