Chainguard Container for trillian-fips

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/trillian-fips:latest

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

Trillian FIPS Images

Trillian is Google's open-source implementation of a transparent, scalable data store using Merkle trees. It serves as the foundation for transparency logs including Certificate Transparency and the Sigstore Rekor transparency log. Trillian provides cryptographic proofs of inclusion and consistency for all data added to the log, ensuring tamper-evident storage.

These FIPS-validated versions provide the same functionality with additional cryptographic compliance for regulated environments.

Chainguard offers two core Trillian FIPS components:

trillian-logserver-fips

The Trillian log server is the main gRPC service that handles API requests for transparency log operations:

• Data Retrieval: Processes get/set requests for Merkle tree data
• Proof Generation: Serves inclusion and consistency proofs to verify entries
• Tree Management: Manages multiple independent Merkle trees within a single service
• Client Interface: Provides the primary API endpoint for transparency log clients

trillian-logsigner-fips

The Trillian log signer operates as a background service that maintains the cryptographic integrity of the transparency log:

• Entry Processing: Periodically processes pending log entries from the queue
• Tree Updates: Adds verified entries to the Merkle tree structure
• Signing: Updates and signs the tree head to ensure cryptographic consistency
• Sequencing: Assigns sequence numbers to entries in normal log mode

Compatibility Notes

The Chainguard trillian-logserver-fips and trillian-logsigner-fips images are designed to be drop-in replacements for the standard Trillian components with added FIPS compliance.

FIPS Support

These Chainguard Images ship with a validated redistribution of OpenSSL's FIPS provider module. For more on FIPS support in Chainguard Images, consult the guide on FIPS-enabled Chainguard Images on Chainguard Academy.

Trillian is currently in maintenance mode. For new transparency log implementations, consider using Trillian Tessera.

Getting Started

Deploy the Trillian components individually in Kubernetes.

Note that both components require a MySQL database for storage. Along with the name of your organization in the container's image field, you will need to update the --mysql_uri argument in both examples to reflect your own configuration.

Log Server Deployment

Create a deployment for the log server:

cat > trillian-logserver-deployment.yaml <<EOF
apiVersion: apps/v1
kind: Deployment
metadata:
  name: trillian-logserver
spec:
  replicas: 1
  selector:
    matchLabels:
      app: trillian-logserver
  template:
    metadata:
      labels:
        app: trillian-logserver
    spec:
      containers:
      - name: logserver
        image: cgr.dev/ORGANIZATION/trillian-logserver-fips:latest
        ports:
        - containerPort: 8090
        - containerPort: 8091
        args:
        - --storage_system=mysql
        - --mysql_uri=user:password@tcp(mysql:3306)/trillian
        - --rpc_endpoint=0.0.0.0:8090
        - --http_endpoint=0.0.0.0:8091
---
apiVersion: v1
kind: Service
metadata:
  name: trillian-logserver
spec:
  selector:
    app: trillian-logserver
  ports:
  - name: grpc
    port: 8090
    targetPort: 8090
  - name: http
    port: 8091
    targetPort: 8091
EOF

Log Signer Deployment

Create a deployment for the log signer:

cat > trillian-logsigner-deployment.yaml <<EOF
apiVersion: apps/v1
kind: Deployment
metadata:
  name: trillian-logsigner
spec:
  replicas: 1
  selector:
    matchLabels:
      app: trillian-logsigner
  template:
    metadata:
      labels:
        app: trillian-logsigner
    spec:
      containers:
      - name: logsigner
        image: cgr.dev/ORGANIZATION/trillian-logsigner-fips:latest
        args:
        - --storage_system=mysql
        - --mysql_uri=user:password@tcp(mysql:3306)/trillian
        - --sequencer_interval=1s
        - --batch_size=50
EOF

Apply the deployments:

kubectl apply -f trillian-logserver-deployment.yaml
kubectl apply -f trillian-logsigner-deployment.yaml

Documentation and Resources

• Trillian GitHub Repository
• Certificate Transparency Documentation
• Sigstore Documentation

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.