DECONFLICT: This talk is NOT about the PaperCut NG/MF exploit chain (CVE-2026-81578 + CVE-2026-82078, CISA KEV, August 2026). No printers were harmed. Different kind of paper cut. Patch anyway.
▶ Case Disposition – King County District Court
Case No.
25CIV60102KCX
Trial Date
March 16, 2026
Result
JUDGMENT FOR PLAINTIFF
Judge
Michael J. Finkle
Defendant
Pension Benefit Information, LLC
Award
$350.00 – PAID, FINAL
▶ Talk Overview

In 2023, Pension Benefit Information, LLC – a Minneapolis data broker – lost the presenter's name, Social Security Number, and date of birth in the MOVEit/Cl0p ransomware breach. Notification arrived 42 days after PBI's own discovery (per the judgment) – past Washington State's 30-day statutory requirement. The presenter spent time on expert remediation, invoiced PBI $1,050, and was refused. He filed small claims in King County District Court.

PBI responded with corporate counsel and a jurisdictional dismissal motion. On March 16, 2026, Judge Michael J. Finkle denied that motion and issued judgment for the plaintiff, explicitly finding that a cybersecurity professional's time assessing a breach is compensable at professional rates. Routine tasks any victim could perform are not. PBI paid.

"Don't piss off a geek … They don't have a life and can EASILY make you the focus of THEIR life." – Ken Hollis

This talk distills the experience into a complete, replicable playbook for any breach victim with documentation, a $50 filing fee, and a few hours of preparation. Class actions pay lawyers. Small claims pays you.

▶ Key Findings (Judge Finkle, Addendum to Judgment)
▶ Supporting Documents

All documents are either public court record or the presenter's own work.

▶ The Template – Fourteen Steps
  1. Save everything. Scan the breach notification the day it arrives. Bookmark relevant web pages. "Just the facts, ma'am" – you do NOT need 10,000 pages of documentation. Keep only the pages that prove your points, and leave out articles that make claims without solid references.
  2. Wayback their web presence. Archive the sender's web presence on the Wayback Machine the same day. Blogs disappear during litigation. Screenshots too – belt and suspenders.
  3. Find the real legal entity. Use the state Secretary of State registry plus the AG breach notification registry. The name on the letter is not necessarily the entity you sue – here, "PBI Research Services" versus "Pension Benefit Information, LLC." The WA AG breach registry is searchable from any state, but only lists breaches affecting 500+ Washington residents.
  4. Log your time from day one. Timestamps and specific activities. Include hardcopy review AND online research time. Separate expert-skill tasks from routine tasks – the judge WILL draw this line. You can ask a nominal rate (e.g. $25/hr) for routine work; the judge may or may not allow it.
  5. Document your rate basis. Specifics and market data. You are asking for a conservative, defensible floor – not your ceiling.
  6. Invoice before filing in small claims. Set a payment deadline. Keep the refusal letter. "They wouldn't pay" is the whole story in two seconds.
  7. File your small claim. Washington example: WA AG – Small Claims Court. Not all states are as well documented as Washington – read everything on your court's website, and if it isn't clear, call the clerk and ask.
    • Know your state's limits – the claim cap AND the appeal rules.
    • Washington: claim under $1,000 and YOU can't appeal – but THEY still can on any claim of $250 or more.
    • File for yourself only. A spouse files as a co-plaintiff and must appear. (My first filing was dismissed because I tried to claim for my wife; I had to refile for myself.)
    • Minor child: file as yourself, individually and/or "as guardian ad litem for J.H., a minor." Use initials, NOT their name.
  8. Serve THEIR registered agent – never yourself. Use a professional process server in THEIR city – they know what they are doing. Not the PR address, not your cousin in that town. In Washington, service must be completed at least 10 days before the pretrial hearing, and the Declaration of Service MUST be filed. Miss this and your case is dismissed. Add the process server fee to your claim – I forgot to, and it cost me about $80.
  9. Attach yourself to the case portal. After filing, ask the clerk explicitly how to attach your account to the case. You are the plaintiff. This is not automatic. Nobody volunteers this.
  10. Mediation is mandatory, free, and confidential. You MUST attend. It does not become part of the court record and does not affect your right to trial if it fails. Do not settle below your documented claim just to avoid the hearing – walk out and go to trial. If their lawyer asks for a "just want to chat" call before mediation, be very careful – it is not a friendly call. They are fishing.
  11. Beat the jurisdiction motion with data. How many residents of your state were affected, and where can those individuals practically sue? The answer is: here. They will tell you to join the class action or file in their state – nope, nope, nope.
  12. Exchange evidence 14 days before trial (Washington). Not optional – failure risks continuance or exclusion. Do it in writing, keep proof of delivery. Bring two printed copies of everything to the courtroom. The clerk makes nothing.
  13. Show up prepared. Five elements. Documented evidence. No drama. See the trial argument outline.
  14. Take the check. Then file a Satisfaction of Judgment with the clerk to close the record. Your court packet includes this form. File it.
▶ Home Game – Running This in Oregon

These are Oregon's rules as I read them – I have NOT been through Oregon small claims. Read them yourself. YMMV.

▶ What You Leave With

The barrier was never lawyers. The barrier is documentation discipline – a skill this community already has. (And you KNOW you started investigating the breach the minute you got the letter.) You already keep logs, versions, and evidence, and you write postmortems. Those ARE the skills. The lawyers will try to bluff you out of pursuing the case.

NOTE: This is a legal strategy framework built from documented experience, not legal advice. I am not a lawyer. Small claims sets no binding precedent – the method replicates, the ruling does not. Procedures, limits, and statutes vary by jurisdiction. Verify your state's small claims rules before filing. IANAL.
▶ Speaker

Ken Hollis spent 40 years in technology – starting with punch cards, before the Internet – across aerospace (Kennedy Space Center), enterprise networking, SCADA/ICS, and 18 years at Microsoft with 11 in security engineering, including the Cyber Defense Operations Center and critical infrastructure security for data centers and industrial control systems. He is retired and lives near Redmond, Washington. He is not a lawyer. He won anyway.

GandalfDDI – BlueSky · Mastodon (ioc.exchange) · gandalfddi.github.io