What is Phield?
Phield is a PII drift and trend monitor. It receives counts of PII entity types over time, stores them as a time series, builds a baseline, and alerts when a new count rises significantly above the established trend. A sudden spike in credit card numbers raises an alert. Phield alerts on increases only; a count that falls below its baseline does not alert.
What data does Phield need? Does it see the actual PII?
No. Phield only ingests counts: a timestamped map of entity types to numbers, tagged with a source and context. It never receives the underlying documents or the sensitive values themselves. You get monitoring and alerting on your redaction pipeline without centralizing any of the PII the pipeline is meant to protect.
How does Phield decide that a count is anomalous?
Phield builds a baseline from the history of counts it has received for each source, context, and entity type, then compares every new sample against that established trend. When a sample rises above it by more than the configured threshold (a percentage increase over the average, or a z-score), Phield raises an alert with the source, entity type, observed count, baseline, and size of the increase. Counts that fall below the baseline do not alert.
How do I get counts into Phield?
Two ways, with the same payload shape: POST them to Phield's HTTP API, or publish them to a Kafka topic. Each source, organization, context, and entity type is tracked as its own series with its own baseline, so counts reported from different points in a pipeline, such as before and after redaction, are monitored separately.
Where does Phield store data, and how does it alert?
Phield stores samples in a MongoDB time-series collection for durable, queryable history, and falls back to in-memory storage when MongoDB isn't available so you can run it with no external dependencies. When a count rises above its trend, it sends alerts to PagerDuty, Slack, or both.
Is Phield open source?
Yes. Phield is open source under the permissive Apache License, version 2, and the code is on
GitHub. It is self-hosted: it runs entirely inside your perimeter with no SaaS dashboard and no external data shipping.