Ticket #4821: Coverage renewal
Policyholder NAME (EMAIL) asked about renewing the plan on the account ending ACCOUNT.
Redact PII from search results
Search Redact is an open source plugin for OpenSearch and Elasticsearch that redacts PII and PHI from search results at query time, before they reach the user. It runs inside your cluster and applies a Phileas policy, the same policy format Philter uses, passed with each search request.
A user runs an ordinary search. Search Redact applies your Phileas policy to the matching documents inside the cluster, so the hits come back with sensitive fields redacted before they reach the user. The stored documents are untouched.
Policyholder NAME (EMAIL) asked about renewing the plan on the account ending ACCOUNT.
Caller NAME at PHONE requested a card change; SSN SSN on file.
Redaction happens in the response path, per query, using the policy you pass. Nothing in the index is rewritten.
Sensitive fields are redacted as results are returned, so PII and PHI do not have to leave the cluster in the clear. The stored documents are untouched; redaction is applied to the response.
Detection is the open source Phileas engine: pattern matching for structured identifiers and dictionaries for names and places. Policies use the same Phileas format as Philter. PhEye AI models are not yet supported in the plugin.
Apache-2.0 licensed and runs entirely inside your own cluster. No data leaves your environment for redaction, which keeps your compliance boundary intact.
The same plugin, built for each platform. Both are Apache-2.0 licensed and built on Phileas.
Install the plugin in your OpenSearch cluster to redact sensitive fields from search results. See the OpenSearch walkthrough.
The Elasticsearch build of the same plugin, with the same query-time redaction. See the Elasticsearch walkthrough.
If something here isn’t covered, get in touch and we’ll answer.
ext.search-redact block. Different applications can apply different policies to the same index without reindexing. Redaction applies only when a request includes the block, so the plugin is not an access control: a client that omits it gets the stored data, and enforcing redaction needs a gateway or role restriction in front of the cluster.Install the plugin for OpenSearch or Elasticsearch to redact PII and PHI from your search results, or talk to us about your search privacy requirements.