32.02 (Build 32.02.127)

The following table outlines the release particulars:

Build	32.02.127
Code name	O’Neal - Update 2, 32.02
Release date	January 28th, 2024
Type	Maintenance Release
SHA-256	a4790f3e94509fb1d80b0ff5a3567ac57295fd52b976b7f67d34ab268f9636ee

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.

Enhancements

FEATURE	DESCRIPTION
Agentless Scanning	Enabled the scan of non-running hosts by default. Agentless scanning now scans non-running hosts by default for all newly added accounts. This change does not affect existing accounts.
Registry Scanning	The following new fields are now displayed for registry scans: Scan status—if the scan completed successfully or failed. Last scan time—the time at which defender started scanning the registry. A new unified scan progress indicator shows the status (percentage and number) of scanning and pending registries.
Vulnerability Management	Improved the detection of vulnerabilities on supported Windows OS workloads to fix false negative and false positive alerts related to Windows feeds.

API Changes

API to list cloud accounts that are imported from the Prisma Cloud platform

You can onboard accounts and cloud credentials only through the Prisma Cloud platform Accounts page now. To support this change, the following new query parameters have been added to the Get All Credentials endpoint. These parameters allow you to list cloud accounts that are imported from the Prisma Cloud platform: external: Set to true to retrieve credentials imported from the Prisma Cloud platform Accounts page. autoImported: Set to true to retrieve credentials that were automatically imported from the Prisma Cloud platform Accounts page.

New request body field in the Download Serverless Layer Bundle endpoint

The Download Serverless Layer Bundle endpoint includes a new request body field: nodeJSModuleType, which accepts one of these values: commonjs ecmascript The nodeJSModuleType field is optional and the default value is commonjs.

End of Support Notifications

Code Security Module for Scanning

The Code Repository Scanning feature is sunset in Prisma Cloud Compute Edition. It is replaced by Prisma Cloud Application Security in the Enterprise Edition, which offers more comprehensive and advanced Software Composition Analysis (SCA). For information, see Prisma Cloud Application Security.

Code Security Module for Scanning APIs are Sunset

The Code Repository Scanning feature in Prisma Cloud Compute is no longer available as Prisma Cloud Enterprise Edition (Cloud Application Security) offers a more comprehensive and advanced Software Composition Analysis (SCA) feature. Also, the following Prisma Cloud Compute code scan endpoints have been sunset (removed): /api/<vVersion>/coderepos - GET /api/<vVersion>/coderepos/scan - POST /api/<vVersion>/coderepos/stop - POST /api/<vVersion>/coderepos/download- GET /api/<vVersion>/coderepos/progress - GET /api/<vVersion>/coderepos/discover - GET /api/<vVersion>/coderepos-ci - POST /api/<vVersion>/coderepos-ci - GET /api/<vVersion>/coderepos-ci/download - GET /api/<vVersion>/policies/vulnerability/coderepos - GET /api/<vVersion>/policies/vulnerability/coderepos/impacted - GET /api/<vVersion>/policies/vulnerability/ci/coderepos - GET /api/<vVersion>/policies/compliance/coderepos - GET /api/<vVersion>/policies/compliance/coderepos/impacted - GET /api/<vVersion>/policies/compliance/ci/coderepos- GET /api/<vVersion>/policies/vulnerability/coderepos - PUT /api/<vVersion>/policies/vulnerability/ci/coderepos - PUT /api/<vVersion>/policies/compliance/coderepos - PUT /api/<vVersion>/policies/compliance/ci/coderepos- PUT /api/<vVersion>/settings/coderepos - PUT /api/<vVersion>/settings/coderepos - GET /api/<vVersion>/coderepos/webhook/{" + id + "}" - POST

Addressed Issues

FIXED VERSION	DESCRIPTION
Fixed in 32.02	Agentless scanning now supports scanning of Podman container images deployed to hosts with the default storage driver.
Fixed in 32.02	Fixed an issue where scanning scripts that contain binary data caused memory consumption issues.
Fixed in 32.02	Improved the detection of vulnerabilities on supported Windows OS workloads to fix false negative and false positive alerts related to Windows feeds.
Fixed in 32.02	Fixed an issue causing some TAS blobstore controllers not to be listed.
Fixed in 32.02	Fixed an issue found during configuration of the Tanzu blobstore scanner. The configuration didn’t filter the scanners from the selected cloud controller correctly. Now, when you provide a cloud controller in the Tanzu blobstore scan configuration, only the suitable scanners are available in the scanner dropdown.
Fixed in 32.02	Added support for installing serverless defender on AWS with NodeJS runtime, using layer based deployment type and ES modules type.
Fixed in 32.02	Fixed an issue where users could not see credentials stored in the Runtime Security credential store, when creating a new System Admin role while specifying cloud accounts only onboarded under Runtime Security.