Prisma Cloud Microsegmentation Known Issues

Review the list of known and addressed issues and deprecation notice for the Identity-Based Microsegmentation module on Prisma Cloud.
The following table lists the known issues on the Cloud Network Security—Identity-Based Microsegmentation module on Prisma Cloud.
The release deployment is a scheduled roll out that occurs over a week, and the release date below marks the deployment to the first stack.
Issue ID
Description
CNS-5129
Tag prefixes with ‘*’ character cannot be deleted.
CNS-5199
Fixed in the 22.7.2 release
Default networks for Managed TCP networks are not created when a new Enforcer profile is created.
CNS-5221
Fixed in the 22.7.1 release
The debug data for Tech support collection uses too much memory.
CNS-5281
Fixed in the 22.7.2 release
Enforcer cgroup tampered alarm skips the reporting the process ID when the process cannot be found.
CNS-5230
Fixed in the 22.7.1 release
Stopping or deleting Docker containers with Enforcers has issues. Network Diagnostics option provides incorrect results.
CNS-5234
Fixed in the 22.7.1 release
Client (PU) to Server (No PU) traffic within target networks through a next generation firewall do not produce a connection exception.
CNS-5240
Fixed in the 22.7.1 release
Auto completion in rulesets does not display the accurate list when the Source and Destination processing units are on different namespaces.
CNS-5300
Fixed in the 22.7.1 release
OCP 4.10 duplicate processing units shows up on the backend after deleting the enforcer pods.
CNS-5577
A few troubleshooting options are not working for ECS.
CNS-5689
Fixed in the 22.7.2 release
Incorrect exposed port format causes apoctl to fail.
CNS-5787
Installing an RPM enforcer overwrites existing config file (works as expected with DEB packages).
Deprecation Notice—Namespace Editor Role
If you have any API authorizations using the Namespace Editor role, migrate them to the Namespace Administrator role.
The Namespace Editor role will be removed in a future release.
Deprecation Notice—Non-Standard Tag Names
With the 22.1.2 release, a standardized tag format is being introduced. See Features Introduced in January 2022
All your existing tags will continue to be supported until further notice.
We recommend that you modify all your existing rulesets to use the new standardized tag format, to allow or deny communication and access to resources. This will enable you to be ready for the specific release where the new tag format will be enforced.

Recommended For You