> 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-01.md).

# 32.01 (Build 32.01.128)

The following table outlines the release particulars:

| Build        | 32.01.128                                                        |
| ------------ | ---------------------------------------------------------------- |
| Code name    | O’Neal - Update 1, 32.01                                         |
| Release date | January 7th, 2024                                                |
| Type         | Maintenance Release                                              |
| SHA-256      | c7540e43ccd43c625a0a379570915198decaeaa48e61b145508c792adf084fc2 |

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, runtimes, tools, and orchestrators.

## Upgrade from Previous Releases

### Upgrade Defender Versions 22.12 and Earlier

With the `v32.00` release, [Defender versions supported (n, n-1, and n-2)](https://docs.prismacloud.io/en/compute-edition/32/admin-guide/upgrade/support-lifecycle) are `v32.00`, `v31.00`, and `v30.00`.

To prepare for this update, you must upgrade your Defenders from version `v22.12` (Lagrange) or earlier to a later version. Failure to upgrade Defenders will result in disconnection of any Defender version below `v30.00` such as `v22.12`.

### Upgrade the Prisma Cloud Console

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

You can upgrade the Prisma Cloud console directly from any version for n-1 to n. With `v30.00` as n-1 and `v31.00` as n, you can for example go directly from `v30.01.153` to `v31.00.129`.

You have to upgrade any version of `v22.00` to `v30.00` before upgrading to `v31.00`. For example, you can upgrade from `v22.12.693` to `v30.02.123` and then upgrade to `v32.00.159`.

## API Changes and New APIs

* Collections that were added using the [Add a New Collection](https://pan.dev/prisma-cloud/api/cwpp/post-collections/) did not display as expected in the Console. This issue has been resolved by making all request body fields, except `name`, optional. Any field that is not provided will default to the wildcard value '\*'.

## Enhancements

| FEATURE                      | DESCRIPTION                                                                                                                                                                                                                                                                                   |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Agentless Scanning**       | Added agentless scanning support of encrypted volumes in Azure for the hub account mode.                                                                                                                                                                                                      |
| **Agentless Scanning**       | Added agentless scanning hub account mode for Azure.                                                                                                                                                                                                                                          |
| **Vulnerability Management** | Added support for Debian Bullseye and Bookworm Security fixes.                                                                                                                                                                                                                                |
| **Operating System Support** | Added support for OpenShift 4.14.                                                                                                                                                                                                                                                             |
| **Vulnerability Management** | From 32.01, support is added to detect the Java version number when IBM Java is used during vulnerability management. This enhancement covers IBM Java version 1.8 and earlier. For IBM Java version 1.9 and later, support is partial and depends on the presence of the `jdk/release` file. |

## End of Support Notifications

| **Alerts** | <p>Deprecated the <code>AccountID</code> and <code>Cluster</code> macros used in alerts. This removes the <code>AccountID</code> and <code>Cluster</code> fields in the following alerts using the macros.</p><ul><li>Webhook</li><li>AWS SQS</li><li>Prisma Cortex Alert</li><li>Splunk</li></ul> |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

## Addressed Issues

| **FIXED VERSION**                                            | **DESCRIPTION**                                                                                                                                                                                                                                                                                                                    |
| ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <mark style="background-color:orange;">Fixed in 32.01</mark> | Collections that were added using the [Add a New Collection](https://pan.dev/prisma-cloud/api/cwpp/post-collections/) did not display as expected in the Console. This issue has been resolved by making all request body fields, except `name`, optional. Any field that is not provided will default to the wildcard value '\*'. |
| <mark style="background-color:orange;">Fixed in 32.01</mark> | **Container Support:** Bump `github.com/containers/storage` to v1.42.0 (or later).                                                                                                                                                                                                                                                 |
| <mark style="background-color:orange;">Fixed in 32.01</mark> | **Documentation:** Updated the inconsistent icons in the documentation of the trusted images compliance under **Monitor > Compliance > Trusted images**.                                                                                                                                                                           |
| <mark style="background-color:orange;">Fixed in 32.01</mark> | **Serverless:** Fixed confusion around the serverless function defended status.                                                                                                                                                                                                                                                    |
| <mark style="background-color:orange;">Fixed in 32.01</mark> | **Operating System Support:** Fixed false positives caused by CVE-2016-9063 in hosts running RHEL.                                                                                                                                                                                                                                 |
| <mark style="background-color:orange;">Fixed in 32.01</mark> | **Operating System Support:** Improve parsing of Debian feed for CVEs with status open to include only the vulnerable versions.                                                                                                                                                                                                    |
| <mark style="background-color:orange;">Fixed in 32.01</mark> | **Cloud Service Providers - Azure:** Fixed an issue where the cluster name of Azure AKS clusters was incorrectly resolved by Defenders as vanilla Kubernetes cluster instead of AKS cluster, if the resource group name of the cluster contained the suffix `_group`.                                                              |
| <mark style="background-color:orange;">Fixed in 32.01</mark> | **Image Scanning:** Fixed an issue where system administrators could see all the clusters in the Image Vulnerability scan reports.                                                                                                                                                                                                 |
| <mark style="background-color:orange;">Fixed in 32.01</mark> | **User Interface:** Fixed an issue where adding a collection via API with missing `labels:["*"]` caused the operation to go through but caused the UI to freeze.                                                                                                                                                                   |
| <mark style="background-color:orange;">Fixed in 32.01</mark> | **Logging:** Fixed an issue causing errors in logs after upgrading from v30.00.140 to v31.00.129.                                                                                                                                                                                                                                  |
| <mark style="background-color:orange;">Fixed in 32.01</mark> | **Registry Scanning:** Fixed an issue that caused a scanning failure for Google artifactory registry using credentials imported from the Prisma Cloud platform.                                                                                                                                                                    |


---

# 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-01.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.