Built for scale
Designed for terabytes of unstructured storage. Parallel workers, streaming I/O, and bounded memory so a discovery job never takes down the host it's running on.
Sensitive data discovery scanner
Phinder
Phinder is a high-speed discovery scanner that crawls files, object storage, and document repositories to map where sensitive information actually lives across your environment. It's the step that comes before redaction. You can't protect what you can't find.
Why Phinder
Storage-aware
Native crawlers for Amazon S3, Google Cloud Storage, Azure Blob, and local filesystems. Same policy, same output format, regardless of where the documents live.
Shared policies with Philter
Define a policy once. Phinder uses it to discover; Philter uses it to redact. The entity types you found are the entity types you redact, with no drift between detection and action.
Audit-ready reports
JSON, CSV, or human-readable summaries. Inventory the entity types per file, per bucket, per pipeline: exactly the artifacts auditors ask for.
Search-result redaction
Search Redact brings the same Phileas detection to OpenSearch and Elasticsearch, redacting sensitive information from search results before they leave the cluster. Same engine, different surface.
Compounds with the rest of the toolkit
Discovery without redaction is just inventory. Pair Phinder with Philter (to remediate what was found) and Phield (to keep watching what was missed) for a complete PII lifecycle.
Frequently asked questions
If something here isn’t covered, get in touch and we’ll answer.
What is Phinder?
Phinder is a high-speed discovery scanner. Point it at a bucket, a file share, or a document repository and it crawls the content, detects PII and PHI, and reports which entity types live in which files. It is read-only: the job is to map where sensitive data is, not to change it. Think of it as the inventory step that comes before redaction. You can't protect what you can't find.
How is Phinder different from Philter?
Phinder finds and inventories sensitive data; Philter redacts it. Phinder answers "where is the PII, and what kinds," while Philter acts on it. Because both read the same policy, the entity types Phinder discovers are exactly the entity types Philter will redact, with no drift between detection and remediation.
What storage and file types can Phinder scan?
Phinder ships native crawlers for Amazon S3, Google Cloud Storage, Azure Blob, and local filesystems, and it reads many document formats. The same policy and the same output format apply regardless of where the documents live, so a scan of a local directory and a scan of an S3 bucket produce comparable reports.
Does Phinder modify or move my data?
No. Phinder is read-only discovery. It reports the entity types it found per file, per bucket, and per pipeline, and it never redacts, rewrites, or copies your source data anywhere. Remediation is Philter's job; Phinder's job is to tell you what is there and where.
Is Phinder open source?
Yes. Phinder is open source under the permissive Apache License, version 2, and the code is on GitHub. Run it wherever your data lives, with no per-seat fees and no vendor lock-in.
Ready to use Phinder?
Grab the open source and run it yourself, or work with our team directly. Pick the path that fits.