presidio-analyzer-fips

packaged by Chainguard

Chainguard Container for presidio-analyzer-fips

Minimal Presidio Analyzer image for PII detection over a REST API using spaCy NER and pattern/checksum recognizers, with FIPS support.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/presidio-analyzer-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Getting Started

The presidio-analyzer-fips image runs the Presidio Analyzer as a REST service (gunicorn + Flask) on port 3000, detecting PII entities in text using spaCy NER and pattern/checksum recognizers. It is the FIPS-enabled variant of presidio-analyzer.

Run the service

docker run -d -p 3000:3000 cgr.dev/ORGANIZATION/presidio-analyzer-fips:latest

It exposes /health, /analyze, /recognizers and /supportedentities. Check readiness and detect PII:

curl -s http://localhost:3000/health
# Presidio Analyzer service is up

curl -s -H "Content-Type: application/json" -X POST http://localhost:3000/analyze \
  -d '{"text":"My name is John Smith and my number is 212-555-1234","language":"en"}'

Behaviour is configured via environment variables: PORT (default 3000), WORKERS (gunicorn workers, default 1), and the ANALYZER_CONF_FILE / NLP_CONF_FILE / RECOGNIZER_REGISTRY_CONF_FILE config paths (relative to /app).

Using this image with Kubernetes

Presidio does not publish a first-party Helm chart, so deploy the analyzer as a standard Deployment + Service:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: presidio-analyzer
spec:
  replicas: 1
  selector:
    matchLabels:
      app: presidio-analyzer
  template:
    metadata:
      labels:
        app: presidio-analyzer
    spec:
      containers:
        - name: presidio-analyzer
          image: cgr.dev/ORGANIZATION/presidio-analyzer-fips:latest
          ports:
            - containerPort: 3000
          readinessProbe:
            httpGet:
              path: /health
              port: 3000
---
apiVersion: v1
kind: Service
metadata:
  name: presidio-analyzer
spec:
  selector:
    app: presidio-analyzer
  ports:
    - port: 80
      targetPort: 3000

FIPS support

This variant is built for FIPS 140-3 environments. Presidio Analyzer performs no cryptographic operations of its own, so its only crypto path is the Python standard library (ssl, hashlib), which uses the system OpenSSL. This image installs openssl-config-fipshardened, which activates the FIPS-validated OpenSSL provider as the system default, so:

• When the service terminates TLS itself (gunicorn --certfile/--keyfile), the handshake and ciphers run through the FIPS-validated module.
• Non-approved algorithms are rejected — e.g. hashlib.md5() raises unless called with usedforsecurity=False.

If TLS is terminated at an ingress/service mesh in front of the pod (the common deployment), the analyzer process itself performs no runtime crypto; the FIPS variant is most relevant when the service terminates TLS in-pod.

Compatibility Notes

Chainguard's presidio-analyzer-fips is a drop-in replacement for the upstream mcr.microsoft.com/presidio-analyzer image, with these differences:

• It runs as the non-root user 65532 (upstream uses UID 1001); files and volumes the service must read should be readable by that user.
• It is a minimal, shell-less image with few-to-zero CVEs and does not ship the Poetry/pip build tooling bundled in the upstream image.
• The en_core_web_lg spaCy model is baked in at build time (as upstream), so no model download happens at runtime.
• No Docker HEALTHCHECK is set (Chainguard convention); use a Kubernetes readiness probe on /health (shown above) or your orchestrator's health check instead.

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.