> 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-03.md). # 33.03 (Build 33.03.138) The following table outlines the release particulars: | Build | 33.03.138 | | ------------ | ---------------------------------------------------------------- | | Code name | Pascal Update 3 | | Release date | January 05, 2024 | | Type | Minor release | | SHA-256 | a071ad84ace670a9f4ee37fc3e2f44f270527d4671ebc8e3dc448a6d50282d3d | 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. You can download the release image from the Palo Alto Networks Customer Support Portal, or use a program or script (such as curl, wget) to download the release image directly from our CDN: \ ## 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 | **Feature** | **Description** | | -------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Enhancements to Vulnerability Reporting for Red Hat Enterprise Linux (RHEL) Versions 8 and 9 |

To ensure accurate vulnerability reporting, Intelligence Stream will include RPM module and stream information for RHEL in the reports. This approach improves detection of vulnerabilities and ensures that all associated RPM packages installed by a module are examined during the scan.

What are RPM Modules and Streams?

In Red Hat Enterprise Linux (RHEL), an RPM module is a collection of related RPM packages that represent a software component, such as an application, its dependencies, and helper utilities. Starting with RHEL 6 and 7, modules replaced the Software Collections mechanism.

Modules are structured in the following way:

For example, the notation python39:3.9/python39 indicates the module python39, the stream 3.9, and the source package python39.

Enhancements to Vulnerability Reporting

Benefits of Module-Aware Vulnerability Reporting

NOTE:

| | Enhanced Vulnerability Reporting for NuGet Packages |

Previously, the scanning process included NuGet packages listed in the .deps.json files, which were essential for the runtime environment but not related to the application itself. These unrelated packages result in false positives in vulnerability reporting.

With this enhancement, the scanning process excludes runtime-specific dependencies that are not directly related to the application. This provides a more accurate view of vulnerabilities directly associated with the application, and reduces false positive alerts.

NOTE:

| | Enhancement to Prevent Action with `fsmon_v2` |

To enhance the handling of file system events for the Prevent Action in the Runtime Policy, a new version, fsmon\_v2, has been developed. This version improves stability by managing timeouts more promptly and in a robust manner, thereby reducing bottlenecks and enhancing overall stability.

While fsmon\_v2 brings significant improvements, it is still under active development, and further enhancements are planned. Currently, fsmon\_v2 is being rolled out gradually.

This feature is disabled by default. Customers who want to activate this feature should submit a ticket requesting engineering to enable it.

| | "last-connected" Field Added to Defender Stats Logs | A new field, last-connected, has been added to each Defender stats log. This field records the last confirmed connection time between the Defender and the Console, even when the Connected flag is set to false. The timestamp is represented in epoch seconds (UTC), providing customers with a reliable way to track connection history. | --- # 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-03.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.