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

# 32.06 (Build 32.06.113)

The following table outlines the release particulars:

| Build        | 32.06.113                                                        |
| ------------ | ---------------------------------------------------------------- |
| Code name    | O’Neal - Update 6, 32.06                                         |
| Release date | June 10th, 2024                                                  |
| Type         | Maintenance Release                                              |
| SHA-256      | 540772e5de63f9d70d428152254a1d7de5417325e435d18a2b157295eefd6897 |

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.

## Announcement

| **Feature**                      | **Description**                                                                                       |
| -------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Base Image updated to RHEL 9** | The base image used by the Console and Defenders is now updated to Red Hat Enterprise Linux (RHEL) 9. |

## Enhancements

| **Feature**                                                                    | **Description**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Go Symbol Extraction in Prisma Cloud**                                       | <p>When scanning Golang binaries, Prisma Cloud extracts Go symbols, which allows for evaluating vulnerabilities accurately with specific package names and symbols. The feature flag for extracting Go symbols is enabled by default. Prisma Cloud also allows you to selectively disable symbol extraction when they are not needed, to optimize the scan.</p><p>To disable this feature, follow these steps:</p><ul><li>Self-hosted edition: Add the environment variable SYMBOL\_EXTRACTION\_ENABLED=False in the twistlock.cfg file.</li><li>SaaS edition: Add the environment variable core-symbol-extraction-enabled=False in the Launch Darkly mode.</li><li>Using twistcli: Add the --disable-symbol-extraction flag to the image scan command.</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| **Exporting Software Bill of Materials (SBOM) files in CycloneDX version 1.4** | <p>Prisma Cloud now supports <a href="https://docs.prismacloud.io/en/compute-edition/32/admin-guide/vulnerability-management/exporting-sboms">exporting Software Bill of Materials (SBOM) files</a> in CycloneDX version 1.4 for functions, images, and hosts scans. SBOM files can be generated in JSON or XML format.</p><p><strong>SBOM Attributes</strong></p><p>The SBOM files contain the following attributes:</p><ul><li>Name: Name of the package</li><li>BOM-REF: Package URL (PURL) if it exists; otherwise, UUID (for applications)</li><li>Package Version: Version number for the package</li><li>Package Author: Applicable only for specific package types such as rpm, jem, apk, and deb</li><li>PURL Identifier: Package URL (PURL) identifier</li><li>License: Package license details</li><li>Timestamp (metadata): Time of printing</li><li>Type (metadata): Type of asset. In all the stages, images are categorized as containers, serverless functions as services, hosts and VMs as frameworks.</li><li>Name (metadata): Asset ID of images, hosts, and functions</li></ul><p>SBOM files can be downloaded either through API calls or twistcli.</p><p>For information about the SBOM API calls, see the <a href="#rest-api-changes">REST API Changes</a> section.</p><p><strong>twistcli Configuration</strong></p><ul><li>Export SBOMs using the new flag: --SBOM \[file\_format]</li><li>File Format Values: cyclonedx\_json or cyclonedx\_xml</li><li>SBOM output is concatenated to the scan results output. Use the --output flag to print scan results and SBOM output to a specified file.</li></ul> |
| **Resolving method for cluster name**                                          | <p>When deploying Defender to your Kubernetes cluster, Prisma Cloud now provides you the option to use the API server address from the kube config file to resolve cluster names.</p><p>This option ensures that each cluster has a unique cluster name in Prisma Cloud.</p><p>A new field, Cluster name resolving method, has been added to the Manage → Defenders → “Manual Deploy” → Orchestrator → “Orchestrator type = Kubernetes" → Advanced Settings page.</p><p>The <strong>Cluster name resolving method</strong> field has the following options:</p><ul><li><strong>Default</strong>: Allows Prisma Cloud to automatically generate the name based on available information such as kube config, resource group information, and cloud provider metadata endpoints.</li><li><strong>Manual</strong>: Enables you to set the cluster name manually. When you select this option, the "Specify a cluster name" box appears, allowing you to enter the desired name.</li><li><strong>API Server</strong>: Uses the API server address from the kube config file to generate a unique cluster name in Prisma Cloud.</li></ul><p>This enhancement ensures that vulnerability information is accurately reported for each cluster and makes sure that the clean clusters are not misrepresented as vulnerable due to naming conflicts.</p>                                                                                                                                                                                                                                                                                       |

## API Changes and New APIs

| **Feature**                                                                   | **Description**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Download the Software Bill of Materials (SBOM)**                            | <p>The following new API endpoints enable you to download the Software Bill of Materials (SBOM) details:</p><ul><li><a href="https://pan.dev/compute/api/get-sbom-download-images/">Download SBOM Images</a></li><li><a href="https://pan.dev/compute/api/get-sbom-download-hosts/">Download SBOM Hosts</a></li><li><a href="https://pan.dev/compute/api/get-sbom-download-vms/">Download SBOM VMs</a></li><li><a href="https://pan.dev/compute/api/get-sbom-download-serverless/">Download SBOM Serverless</a></li><li><a href="https://pan.dev/compute/api/get-sbom-download-registry/">Download SBOM Registry</a></li><li><a href="https://pan.dev/compute/api/get-sbom-download-cli-serverless/">Download SBOM CLI Serverless</a></li><li><a href="https://pan.dev/compute/api/get-sbom-download-cli-images/">Download SBOM CLI Images</a></li></ul><p>For more details on the SBOM feature, refer to the <a href="#enhancements">Enhancement</a> section.</p> |
| **Remove hostname from registry progress response**                           | <p>The response of the <a href="https://pan.dev/compute/api/get-registry-progress/">View Registry Scan Progress</a> API has the following changes:</p><ul><li>A new “specScanStartTime” field is added</li><li><p>The existing “discovery” and “imageScan” properties have been modified to:</p><ul><li>Include a new “type” field</li><li>Remove the “hostname” and “scanTime” fields\`</li></ul></li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| **Documentation update for Add Registry Settings**                            | <p>A new registry type - “Harbor” is added to the “version” field for the <a href="https://pan.dev/compute/api/post-settings-registry/">Add Registry Settings</a> API.</p><p>This option enables you to configure a Harbor registry for scanning.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| **Component documentation for API address resolving method for cluster name** | <p>A new optional field clusterNameResolvingMethod is added to the following APIs:</p><ul><li><a href="https://pan.dev/compute/api/post-defenders-daemonset-yaml/">Generate Daemonset Deployment YAML File</a></li><li><a href="https://pan.dev/compute/api/post-defenders-helm-twistlock-defender-helm-tar-gz/">Generate a Helm Deployment Chart for Defender</a></li></ul><p>The permissible values for this field are default, manual, and api-server.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |

## Addressed Issues

There are no Addressed Issues for this release.

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

## Deprecation Notices

There are no Deprecation Notices 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-06.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.