Cortex Cloud: Issues are not being generated from Cloud Workload Misconfiguration Policies for Kubernetes Clusters

Misconfiguration scan results appear in findings, but do not appear in Issues table, despite having a policy set to do so.

• Cortex Cloud
• Cloud Workload Policies for Kubernetes

The policy scope being set to a static asset group with a particular cluster selected - Not currently supported.

The policy scope being set to a dynamic asset group filtered by "Name contains <Cluster Name>" - Not currently supported.

To get a Cloud Workload Policy to generate misconfiguration issues from a Kubernetes resource, the asset group that the policy is scoped to must be set a certain way and the policy cannot be scoped to 'all'. 

1. 1. Navigate to Inventory > Assets > Groups, right-click the asset group that is already scoped to the Cloud Workload Policy.
2. Select "View Selected", uncheck anything that is already selected and remove all filters in the group.
3. Select "Show Filters" underneath the group name on the top left, type in "Kubernetes Resource Cluster", and select it.
4. Verify the filter states "Kubernetes Resource Cluster Contains <Your Cluster Name> and select "Save Dynamic Group" on the bottom right.
5. Navigate to Posture Management > Kubernetes Security > Kubernetes Clusters, right-click your cluster, and select "Request Scan".
6. Select both check boxes and execute the scan. Allow 30 minutes to confirm misconfiguration issues are now properly generating.