Last changed
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
Cerbos is the open core, language-agnostic, scalable authorization solution that makes user permissions and authorization simple to implement and manage by writing context-aware access control policies for your application resources.
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard Registry.
The Chainguard cerbos-fips
image is a drop-in replacement for the upstream cerbos/cerbos container image. It is fully compatibile with the official cerbos Helm charts and supports all core functionality of the cerbos
application. This image is designed to be a minimal, secure alternative that runs as a non-root user. Switching to this image should not require any changes to your existing deployment configuration.
You can deploy this image using the official cerbos Helm charts. Be sure to override the image to use the cerbos-fips
Chainguard Image by setting the following values in a values.yaml
file:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard registry.
Then, deploy the cerbos
Helm chart, as shown in the following shell example.
You can verify that the Cerbos Helm chart deployed successfully with kubectl
, as shown in the following command. This will show you the Cerbos pod running from the chart's deployment.
To deploy Cerbos using Docker, you can do so using the docker run
command. By default, Cerbos listens on port 3592 for HTTP requests, and port 3593 for gRPC requests, requiring that these ports be exposed. Execute the following command in your terminal to deploy Cerbos with its default configuration. Please note that the -d
flag is included to run the container in a detached state, as otherwise Cerbos logs would occupy the terminal.
When you are finished with this container, you can remove it with the docker rm
command, as follows:
To apply custom policies and configurations to Cerbos, the /policies
and /config
directories are mounted volumes at runtime. To demonstrate this, begin by using the following commands to create these directories and navigate to them.
Then, copy the following YAML data into a new file, policies/derived_roles_common.yaml
:
Repeat this process for the configuration of policies/resource_album.yaml
:
To apply a custom Cerbos configuration, we repeat the process once more for the config/conf.yaml
file. Note that this configuration establishes a username linky
and password LinkyAdmin
, which is utilized for demonstrative purposes only, and should be changed in production use.
With all configurations and policies in place, we are ready to deploy our container using the following docker run
command:
The Cerbos container will now be running with our custom configuration settings. We can test this deployment by sending a simple request to the Cerbos server, using cURL
as follows.
You should receive the following in response, reflecting the successful application of the configured Cerbos policies:
We can also verify that the Admin API service was configured correctly with the use of the cerbosctl-fips
Chainguard Image. First, pull this image from the Chainguard registry using the following command.
With the image pulled locally, execute the following command in your terminal to use cerbosctl
to query the cerbos
Chainguard Image's Admin API for its resource_policies
.
The response from the Admin API should be similar to the following output.
The same can be repeated for a query for Cerbos' derived_roles
:
The expected output for this request is shown in the following snippet.
To clean up your system after completing this demonstration, be sure to run the following commands.
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:
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.
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.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
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.
Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:
Apache-2.0
GCC-exception-3.1
GPL-3.0-or-later
LGPL-2.1-or-later
MIT
MPL-2.0
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementThis is a FIPS validated image for FedRAMP compliance.
This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.
Learn more about STIGsGet started with STIGs