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 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) 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) 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 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	Deprecated the AccountID and Cluster macros used in alerts. This removes the AccountID and Cluster fields in the following alerts using the macros. Webhook AWS SQS Prisma Cortex Alert Splunk

Addressed Issues

FIXED VERSION	DESCRIPTION
Fixed in 32.01	Collections that were added using the Add a New Collection 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 '*'.
Fixed in 32.01	Container Support: Bump github.com/containers/storage to v1.42.0 (or later).
Fixed in 32.01	Documentation: Updated the inconsistent icons in the documentation of the trusted images compliance under Monitor > Compliance > Trusted images.
Fixed in 32.01	Serverless: Fixed confusion around the serverless function defended status.
Fixed in 32.01	Operating System Support: Fixed false positives caused by CVE-2016-9063 in hosts running RHEL.
Fixed in 32.01	Operating System Support: Improve parsing of Debian feed for CVEs with status open to include only the vulnerable versions.
Fixed in 32.01	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.
Fixed in 32.01	Image Scanning: Fixed an issue where system administrators could see all the clusters in the Image Vulnerability scan reports.
Fixed in 32.01	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.
Fixed in 32.01	Logging: Fixed an issue causing errors in logs after upgrading from v30.00.140 to v31.00.129.
Fixed in 32.01	Registry Scanning: Fixed an issue that caused a scanning failure for Google artifactory registry using credentials imported from the Prisma Cloud platform.