What's New and Changed in Release 23.5.10
The following new feature was added in Illumio Core 23.5.10.
Rule Hit Count Report
You can add a Rule Hit Count Report through the PCE UI or through the Illumio REST API.
Requirements
PCE Version:
SaaS: 24.2.0 or later
On-prem 23.5.10 or later
VEN Version: 23.2.30 or later
Benefits
The Rule Hit Count Report provides the following:
Policy Compliance: Generate a Rule Hit Count Report to provide evidence that security controls are in place and working effectively, demonstrating compliance to auditors.
Redundancy Removal: Identify unused or less-used rules so you can remove or modify them to reduce redundancy and clutter in your implementation.
Troubleshooting: When network issues arise, identify the rules that were in effect during the relevant traffic flow, allowing you to resolve problems faster and more efficiently.
The PCE and VENs require enablement through the Illumio REST API.
CLAS Architecture in Illumio Core for Kubernetes and OpenShift
Illumio Core for Kubernetes 5.1.0 adds support for a new Cluster Local Actor Store (CLAS) mode, in which Kubelink becomes a full intermediary between PCE and C-VENs. With the CLAS architecture, Kubelink provides greater scalability, faster responsiveness, and streamlined policy convergence with several advantages:
Reclassifies a container workload to more closely align to the Kubernetes concept of a workload (now called in PCE a Kubernetes Workload, to distinguish from a non-CLAS legacy Container Workload)
Improved visibility to all containers/Kubernetes objects and changes
Enforces traffic to/from containers, and responds dynamically to changes
Improved performance as PCE does not have to keep track of every C-VEN change, which is now handled by CLAS
Traffic flow data is now retained even after deleting the corresponding pods