diff --git a/bitnami/sealed-secrets-controller/0/debian-12/Dockerfile b/bitnami/sealed-secrets-controller/0/debian-12/Dockerfile
index 5a1c78d95dec..f64260fa3851 100644
--- a/bitnami/sealed-secrets-controller/0/debian-12/Dockerfile
+++ b/bitnami/sealed-secrets-controller/0/debian-12/Dockerfile
@@ -17,7 +17,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
     DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
     mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
     COMPONENTS=( \
-      "sealed-secrets-0.36.1-0-linux-${OS_ARCH}-debian-12" \
+      "sealed-secrets-0.36.1-1-linux-${OS_ARCH}-debian-12" \
     ) ; \
     for COMPONENT in "${COMPONENTS[@]}"; do \
       if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -40,7 +40,7 @@ ARG TARGETARCH
 ENV OS_ARCH="${TARGETARCH:-amd64}"
 
 LABEL org.opencontainers.image.base.name="scratch" \
-      org.opencontainers.image.created="2026-03-13T09:17:09Z" \
+      org.opencontainers.image.created="2026-04-08T08:36:17Z" \
       org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
       org.opencontainers.image.title="sealed-secrets-controller" \
       org.opencontainers.image.vendor="Broadcom, Inc." \
@@ -53,7 +53,7 @@ COPY --from=builder /opt/bitnami/sealed-secrets/licenses /opt/bitnami/sealed-sec
 
 ENV APP_VERSION="0.36.1" \
     BITNAMI_APP_NAME="sealed-secrets-controller" \
-    IMAGE_REVISION="0" \
+    IMAGE_REVISION="1" \
     PATH="/opt/bitnami/sealed-secrets/bin:$PATH"
 
 USER 1001
diff --git a/bitnami/sealed-secrets-controller/README.md b/bitnami/sealed-secrets-controller/README.md
index bf68f9e4e861..7470794de917 100644
--- a/bitnami/sealed-secrets-controller/README.md
+++ b/bitnami/sealed-secrets-controller/README.md
@@ -34,25 +34,7 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
 
 ## Get this image
 
-The recommended way to get the Bitnami sealed-secrets Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/sealed-secrets).
-
-```console
-docker pull bitnami/sealed-secrets:latest
-```
-
-To use a specific version, you can pull a versioned tag. You can view the [list of available versions](https://hub.docker.com/r/bitnami/sealed-secrets/tags/) in the Docker Hub Registry.
-
-```console
-docker pull bitnami/sealed-secrets:[TAG]
-```
-
-If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the `docker build` command. Remember to replace the `APP`, `VERSION` and `OPERATING-SYSTEM` path placeholders in the example command below with the correct values.
-
-```console
-git clone https://github.com/bitnami/containers.git
-cd bitnami/APP/VERSION/OPERATING-SYSTEM
-docker build -t bitnami/APP:latest .
-```
+The Bitnami Sealed Secrets Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
 
 ## Configuration
 
@@ -72,6 +54,12 @@ docker run --rm --name sealed-secrets bitnami/sealed-secrets:latest -- kubeseal
 
 - The `docker-compose.yaml` file has been removed, as it was solely intended for internal testing purposes.
 
+### FIPS configuration in Bitnami Secure Images
+
+The Bitnami Sealed Secrets Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:
+
+- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.
+
 ## License
 
 Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.