> 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/32/prisma-tm-cloud-compute-edition-release-information/release-notes-32-04.md).

# 32.04 (Build 32.04.113)

The following table outlines the release particulars:

| Build        | 32.04.113                                                        |
| ------------ | ---------------------------------------------------------------- |
| Code name    | O’Neal - Update 4, 32.04                                         |
| Release date | March 28th, 2024                                                 |
| Type         | Maintenance Release                                              |
| SHA-256      | 3c450d58a2a0ed52f7466b3116fa86ff097e1157afa31a457b49700925809d47 |

Review the [system requirements](https://docs.prismacloud.io/en/compute-edition/32/admin-guide/install/system-requirements) to learn about the supported operating systems, hypervisors, runtime, tools, and orchestrators.

## Upgrade from Previous Releases

### Upgrade Defender Versions

With the v32.xx release, the [supported (n, n-1, and n-2) Defender versions](https://docs.prismacloud.io/en/compute-edition/32/admin-guide/upgrade/support-lifecycle) are v32.xx, v31.xx, and v30.xx. Defender versions below v30.xx such as v22.12 cannot connect to the current version.

### Upcoming Defender Obsolescence

With the upcoming v33.00 release, release v30.xx defenders will be obsolete. To prepare for this upcoming update, plan to upgrade defenders to release v31.xx or later.

### Upgrade the Prisma Cloud Console

With the v32.xx release, the [supported (n, n-1, and n-2) Console versions](https://docs.prismacloud.io/en/compute-edition/32/admin-guide/upgrade/support-lifecycle) are v32.xx, v31.xx, and v30.xx. For example: for the current (n) major release v32.xx, the supported n-1 and n-2 versions are v31.xx and v30.xx respectively.

You can upgrade the Prisma Cloud Console from a major release to the next major release, but not to a major release that follows the next. So, to upgrade from the v30.xx release to the v32.xx release, you will have to first upgrade to v31.xx and then upgrade to the v32.xx release.

## Enhancements

| FEATURE                                                             | DESCRIPTION                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Blobstore Scanning Defender Upgrade for Tanzu Customers**         | Enhanced the existing `blobstore` scanning feature for Tanzu customers. As a part of this enhancement, existing `blobstore` scanning defenders will now appear disconnected and new defender instances will be automatically created to replace them. The disconnected `blobstore` will disappear after 24 hours as part of the retention process. This upgrade excludes Linux and Windows defenders (Full coverage defenders). If you have have configured `blobstore` scanning and assigned it to a specific `blobstore` defender after the release of 32.04, you are required to manually edit the configurations and change it to a newly created `blobstore` defender scanner. This release will also introduce a new tile support - jammy for TAS. |
| **Added Account ID information to the Defenders dashboard**         | Added **Account ID** to the manage Defenders dashboard under **Manage > Defenders**. The **Account ID** is also included in the downloadable CSV file.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| **Enhanced the vulnerability assessment process**                   | Prisma Cloud now has an enhanced vulnerability assessment process for applications installed through the OS. If Prisma Cloud can’t detect any vulnerabilities in the vendor feed, it automatically searches for third-party security data to ensure comprehensive security coverage. Go to **Monitor > Vulnerabilities > Vulnerability Explorer** for a comprehensive list of the detected vulnerabilities.                                                                                                                                                                                                                                                                                                                                              |
| **Added a new macro for webhook alerts**                            | Added the `incidentTime` macro for webhook alerts. The macro shows the time the incident occurred. For example, `Jan 21, 2018 UTC`. Go to [Alerts Webhook](https://docs.prismacloud.io/en/compute-edition/32/admin-guide/alerts/webhook) to learn more about the macro.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| **Exclude Go CVEs for Windows from the CVEs of Unix-based systems** | Prisma Cloud now excludes vulnerabilities found in Go packages that are specific to Windows from UNIX based operating systems in the **Vulnerability Explorer**. Go to **Monitor > Vulnerabilities > Vulnerability Explorer** for a comprehensive list of the detected vulnerabilities.                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |

## API Changes and New APIs

| **Report vulnerabilities using Package URL (purl) format** | <p>The following API responses include a new parameter, ‘purl’:</p><ul><li><a href="https://pan.dev/compute/api/get-images">Get Image Scan Results</a></li><li><a href="https://pan.dev/compute/api/get-registry/">Get Registry Scan Results</a></li><li><a href="https://pan.dev/compute/api/get-scans/">Get All CI Image Scan Results</a></li><li><a href="https://pan.dev/compute/api/get-hosts/">Get Host Scan Results</a></li><li><a href="https://pan.dev/compute/api/get-vms/">Get VM Image Scan Results</a></li><li><a href="https://pan.dev/compute/api/get-serverless/">Get All CI Image Scan Results</a></li></ul><p>The ‘purl’ field identifies the absolute path for the packages.</p> |
| ---------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **API for sending console logs to remote syslog**          | [Add Logging Settings](https://pan.dev/compute/api/post-settings-logging/) API includes a new parameter ‘cert’ under ‘Syslog’ to configure a TLS certificate.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |

## Addressed Issues

| **Console fails to load**                                      | The Prisma Cloud Compute Edition (PCCE) Console fails to load if it is accessed on a subdomain of a domain that serves other applications or pages that do not enforce host only cookies. This issue is fixed now. **Note:** Clear the browser cache after you upgrade.                                                                                                               |
| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Unable to download serverless defender bundle for C# Azure** | Fixed the error that blocked downloading of the serverless defender bundle for Azure C# functions.                                                                                                                                                                                                                                                                                    |
| **Twistcli Image Scanning**                                    | Resolved the issue where container images scanned with twistcli did not appear on the **Runtime Security > Inventory > Assets** and the **Cloud Security > Inventory > Compute Workloads** pages. **Note:** Use the `--build` and `--job` flags to include the build number and the job name to help identify the image as a build image that will be presented in the above screens. |
| **Suppressed vulnerabilities in Defender and Console images**  | Vulnerabilities identified as GHSA-xm99-6pv5-q363, also known as CVE-2022-29583, are now suppressed in Defender and Console images since they are disputed.                                                                                                                                                                                                                           |
| **Add "incidentTime" to support macros**                       | Added the `incidentTime` macro for webhook alerts. The macro shows the time the incident occurred. For example, `Jan 21, 2018 UTC`. Go to [Alerts Webhook](https://docs.prismacloud.io/en/classic/compute-admin-guide/alerts/webhook) to learn more about the macro.                                                                                                                  |

## Backward Compatibility for New Features

There is no backward compatibility for new features in this release.

## Change in Behavior

There are no changes in behavior for this release.

## End of Support Notifications

There are no End of Support notifications for this release.


---

# 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/32/prisma-tm-cloud-compute-edition-release-information/release-notes-32-04.md?ask=<question>&goal=<endgoal>
```

`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.
