Enhancements

Added support for cgroupv2:
Scans
:
Full support for cgroup v1 and cgroup v2.
Hybrid mode not supported: this will not fail the scan, but the scan will run without the process limitation protection.
WAAS
:
In-Line firewall:
Full support for cgroup v1 and cgroup v2.
Hybrid mode: partially supported. It is supported if the memory and CPU controllers are both under the legacy hierarchy (v1). Otherwise, the firewall will fail.
Out-Of-Band firewall:
Only cgroup v1 is fully supported.
Cgroup v2: not supported. The firewall will run but the memory limit of the defender’s cgroup will not be increased.
Hybrid mode: partially supported. Same as WAAS In-Line.
Console deployment
:
Not supported in cgroup v2. The console can run on cgroup v2, but the stat periodic process will fail to run and will log an error to the console log.
cgroup v2 is not supported for Talos and other Operating Systems, as both don’t have Systemd.

Added support for Oracle Enterprise Linux (OEL) 8 and 9. You can now run Defenders on OEL 8 and 9 hosts. Prisma Cloud now also protects OEL containers and images.

Added support for Red Hat Enterprise Linux 9 on X86 architecture. You can now run Defenders on RHEL 9 hosts. Prisma Cloud now also protects RHEL 9 containers and images.

Added support for Rocky Linux 8 and 9. You can now run Defenders on hosts running Rocky Linux 8 and 9. Prisma Cloud now also protects Rocky Linux containers and images.

Added support for Windows Server 2022.
Container Defenders support the following features for Windows Server 2022.
Windows compliance scans
Vulnerability scans
Registry scans
Runtime scans
CNNS
Windows metadata scans in Alibaba, AWS, Azure, and GCP
Host Defenders support the following features for Windows Server 2022.
Windows compliance scans
Vulnerability scans
WAAS scans
Windows metadata scans in Alibaba, AWS, Azure, and GCP

Registry scan logs (
Manage > Logs > Console
) now include information about registry scans that failed if there is no Defender available to scan the registry.

Added WAAS support for whitespace in JSON (body) Firewall exception.

Add log when package manager files are missing in the scan

Added support for custom tagging agentless scanners and resources created within your accounts. You can specify up to ten tags as a part of the advanced agentless configuration. These tags are added to any previously existing resource tags.

Updated the agentless scanning onboarding instructions for AWS and GCP to include setting up agentless using hub and target accounts.

Introduced a new column
Last changed
to API Discovery with the date of the latest change to the API. The discovered API
Change history
log is shown in the details pane.

Addressed Issues

Fixed crypto miner check issue that adversely impacted the performance of the host runtime protection and of the host. Enable this check to get alerts when crypto miners are created or executed in your deployment. You can prevent their execution by setting the

Effect

to

Prevent

in your runtime rules.

Fixed an issue in grouping the columns under
Monitor > Events
. The events grouped by any field now display relevant results.

Fixed security group is malformed error causing the VM image scans to fail in AWS EC2 environments.

Fixed an issue where adding or updating collections in large deployments took a significant amount of time to show in Prisma Cloud.

Fixed an issue where the
Refresh
action on the Vulnerability Explorer page/API failed in cases where some images in the environment had a large number of containers running (~10-20K containers per image).

Fixed an issue for App-Embedded WAAS events. To add an exception directly from an event, you can now use the
Add as exception
button.

Fixed an issue where the Prisma Cloud console displayed an expired certificate warning for Defenders even if the certificate was not in use. Now there is no incorrect warning displayed.

Fixed an issue wherein the registry scan stops when there is no running Defender found in one of the registry’s pre-defined scopes. The scan will continue, and the skipped registry will be re-scanned once a running defender is found for the registry’s scope.

Fixed a Definition Scan API error that happened when trying to display non-printable characters in the code editor.

Fixed an issue on Tanzu Application Services Windows apps where scanner containers were not removed if there was an error during download or upload of the app’s droplet.

End of Support Notifications