Features Introduced in February 2024
There were two releases in February 2024.
Features Introduced in February 2024 (32.03)
Learn about the new Compute capabilities on Prisma™ Cloud Enterprise Edition (SaaS) in February 2024.
The host, container, and serverless capabilities on the Compute tab are being upgraded starting on February 25, 2024. When upgraded, the version will be 32.03.
Defender Upgrade
Plan to Upgrade Defender Versions 22.12 and Earlier
With the v32.00 (O’Neal) 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.
Upcoming Defender Obsolescence
With the upcoming v33.00 release, release v30.xx defenders will be obsolete. To prepare for this coming update, plan for upgrading to release v31.xx or later at the earliest.
Enhancements
FEATURE
DESCRIPTION
Support Amazon Linux 2023
Prisma Cloud now supports Amazon Linux 2023 OS scans and security feed integration for Amazon Linux 2023.
Enhanced CSV Organization
Segregating vulnerability and compliance findings based on Download Context.
Enhanced Compliance Report
Added a new Result column to the compliance report CSV file. To get the report, go to Monitor > Compliance > Compliance Explorer and select Containers, Images, or Hosts. The new column shows either pass or fail for each resource and the corresponding compliance check ID.
New incident policies based on traffic observation
This update adds two new policies that alert you to traffic that includes:
Sensitive data sent through an API endpoint that is exposed to the internet without authentication.
Sensitive data sent through an API endpoint that is exposed to the internet without encryption.
Detect Go Stdlib Vulnerabilities at the Package Level
In O’Neal Update 3, Prisma Cloud has enhanced its capability to detect vulnerabilities in Go libraries. Previously, a broad approach was used for Go stdlib libraries, categorizing CVEs as "Go" vulnerabilities rather than associating them with specific vulnerable standard libraries. This update offers a more precise classification, allowing for the identification of specific vulnerable symbols within libraries. Moreover, the latest agents can now detect both stdlib with symbols they utilize and the installed Go runtime. This comprehensive approach enables Prisma Cloud to conduct more accurate vulnerability assessments, leading to a significant reduction in false positives. If you have utilized the Go detection capabilities previously, you are likely to experience a noticeable reduction in the number of reported vulnerabilities due to this improvement.
API Changes
Split Vulnerability and Compliance CSV
The following APIs include a new parameter, issueType:
The issueType parameter can be set to vulnerabilities or compliance for downloading vulnerability or compliance issues respectively. If either value is not provided, both vulnerability and compliance issues are downloaded.
Features Introduced in February 2024 (32.02)
Learn about the new Compute capabilities on Prisma™ Cloud Enterprise Edition (SaaS) in February 2024.
The host, container, and serverless capabilities on the Compute tab are being upgraded starting on January 28, 2024. When upgraded, the version will be 32.02.
Defender Upgrade
Plan to Upgrade Defender Versions 22.12 and Earlier
With the v32.00 (O’Neal) 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.
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 totrueto retrieve credentials imported from the Prisma Cloud platform Accounts page.autoImported: Set totrueto 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:
commonjsecmascript
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
Last updated
Was this helpful?