Security Teams Swim in Other People's PII
The tooling a modern SOC runs on — SIEM, EDR, NDR, email security, ticketing — exists to collect evidence, and evidence is soaked in personal data. Proxy logs carry usernames and the sites employees visit. Email security gateways quarantine messages containing medical claims and payroll figures. EDR telemetry records file paths like C:\Users\jsmith\Documents\divorce_settlement.docx. Packet captures and alert payloads embed whatever content happened to be in flight. Security teams rarely think of themselves as data controllers, yet the SIEM is often the single largest concentration of personal data in the company — and the least governed one.
That creates two distinct problems. Day to day, PII and secrets accumulate in detection pipelines where analysts, MSSP contractors, and third-party tools can see them, quietly expanding regulatory scope and insider risk. And on the worst day, when data has actually been stolen, the incident commander faces a deadline-driven question that manual review cannot answer at scale: exactly which records in the affected data contained personal information, of what kinds, for roughly how many people?
Our PII Detection API gives security engineering a programmatic answer to both. Send any text — a log batch, an alert payload, a paste-site dump, a recovered file — and get back every detected entity with its type, character offsets, and confidence score, plus an optionally masked copy. It is a single JSON endpoint you can call from a SOAR playbook, a log shipper, or a one-off triage script during an active incident.