> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/ce-release-notes/33/prisma-tm-cloud-compute-edition-release-information/release-notes-33-01.md). # 33.01 (Build 33.01.137) The following table outlines the release particulars: | Build | 33.01.137 | | ------------ | ---------------------------------------------------------------- | | Code name | Pascal Update 1 | | Release date | October 06, 2024 | | Type | Minor release | | SHA-256 | e7f9fd298a4d84ec9247509e584db0ad55b34dd669953e017e01b9a4e79450ec | Review the [system requirements](https://docs.prismacloud.io/en/compute-edition/33/admin-guide/install/system-requirements) to learn about the supported operating systems, hypervisors, runtimes, tools, and orchestrators. ## Lifecycle Support Update Prisma Cloud officially guarantees backward compatibility with up to two previous major versions (n-2). Although the support lifecycle remains unchanged, starting from version 33.xx, Prisma Cloud will not restrict the usage of Defender versions or REST API calls from up to three major releases before the current version (upto n-3 major releases). For example, with the current version at 33.xx, API calls and Defenders from version 30.xx will be allowed. However, support and complete backward compatibility is guaranteed for the 32.xx and 31.xx releases. ## Upgrade from Previous Releases ### Upgrade Defenders Starting with the `v33.00` release, the [Defender versions supported (n, n-1, and n-2)](https://docs.prismacloud.io/en/compute-edition/33/admin-guide/upgrade/support-lifecycle) are `v33.00`, `v32.00`, and `v31.00` respectively. In addition, starting from release 33.00, Prisma Cloud will not restrict the usage of Defender versions or REST API calls from the n-3 version. So the current release will allow Defenders and REST API calls from release 30.xx also. Failure to upgrade Defenders below version `v30.00`, such as `v22.12`, will result in disconnection of the Defenders from the Console. However, to maintain full support, you must upgrade your Defenders to `v31.xx` or a higher release. To summarize, the level of support for the different versions of Defenders is as follows: * Defender versions 33.xx, 32.xx, and 31.xx have full support * Defender versions 30.xx are functional (will be able to connect to version 33.xx Console) but support is not available for such Defenders * Defender versions previous to 30.xx, such as 22.12, are neither supported nor functional (cannot connect to version 33.xx Console) ### Upgrade the Prisma Cloud Console Starting with the `v33.00` release, the [supported Console versions (n, n-1, and n-2)](https://docs.prismacloud.io/en/compute-edition/33/admin-guide/upgrade/support-lifecycle) are `v33.00`, `v32.00`, and `v31.00` respectively. Defenders from the n-3 release will remain functional as described above. You can upgrade the Prisma Cloud console directly from any n-1 version to n. For example, with `v33.00` as n and `v32.00` as n-1, you can upgrade directly from `v32.05.124` to `v33.01.137`. You have to upgrade any version of `v31.00` to `v32.00` before upgrading to `v33.00`. For example, you must upgrade from `v31.02.137` to `v32.07.123` before you upgrade to `v33.01.137`. ## Enhancements ### Multiple Intelligence Stream (IS) Builders for Compatibility across Console and Defender Versions Starting from this release, Prisma Cloud will introduce versioning for the Intelligence Stream (IS) to ensure compatibility across different Console and Defender versions. **Purpose of Intelligence Stream (IS) Versioning** * **Maintain functionality for older Consoles and Defenders:** IS versioning ensures that older Consoles and Defenders continue to operate properly, even if they are unable to support the latest Intelligence feeds (for example, due to changes in external data feed formats). * **Reduce disruptions:** Versioning helps minimize disruptions caused by updates, such as changes in downloaded JSON file fields that could impact CVE accuracy or result in duplicate CVEs. **Impact on Prisma Cloud Customers** * **Enterprise Edition (SaaS) customers:** These customers always have the latest Console version, so they will not be affected by this change. * **Compute Edition (self-hosted) customers:** IS versions will be aligned with specific Console versions. For example, older 31.xx and 32.xx Consoles will be supported by the IS version released for Console 33.00. When customers upgrade to the latest Console version, they will receive the most recent IS updates. **Vulnerability Reporting Consistency** * **New Intelligence Stream (IS) logic updates:** These updates will only apply to the latest IS versions. * **Vulnerability data:** All IS versions will continue to provide up-to-date vulnerability information, and changes in IS logic or algorithms will not affect the vulnerability metrics and reporting in the Console. ### Support for Deploying Defenders on Podman Containers Previously, Prisma Cloud supported scanning Podman images in the CI pipeline using *twistcli*. With this release, Prisma Cloud now supports deploying Defenders on Podman containers, providing comprehensive visibility and protection for workloads running in Podman environments. This enhancement enables full protection for Podman containers, including continuous vulnerability scanning, compliance policy enforcement, and active runtime security monitoring. To deploy a Linux Container Defender on Podman, navigate to **Manage** > **Defenders** > **Manual Deploy** > **Single Defender**. Select **Container Defender - Linux** as Defender Type. In the **Container Runtime Type** field, select **Podman** (the default is Docker). If you select Podman, the installation script automatically includes the `--install-podman` argument. If your Podman environment uses a custom runtime socket path, you can specify it using the `--podman-socket` argument. For example, to use Podman with a custom runtime socket path, the installation command would be: `curl -sSL --header "###" -X POST /api/v1/scripts/defender.sh \| sudo bash -s — -c "stage-consoles-cwp.cloud.twistlock.com" -v --install-podman --podman-socket ""` ### SHA-256 Checksum for Defender Image Downloads Prisma Cloud now enables users to validate the integrity of Defender images downloaded from the Console using a SHA-256 checksum, ensuring the downloaded image matches the server version. To access the feature, do the following: 1. In the Console, go to **Manage > System > Utilities**. The SHA-256 checksum is available next to the downloadable Defender image. 2. Click **Show Checksum** to view the checksum to verify the downloaded image. This feature ensures that Defender images are secure and protected from tampering. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.prismacloud.io/ce-release-notes/33/prisma-tm-cloud-compute-edition-release-information/release-notes-33-01.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.