K8s IOMs
This local console is not CrowdStrike production. IOMs you see stay on this clone. They do not come from a Falcon tenant and they do not call Falcon cloud. This is not CrowdStrike Kubernetes Protection.
Sign in first. Follow Signing in to the console with
[email protected], then use the left rail.
K8s IOMs
Choose K8s IOMs in the rail. The table lists the seed indicators of misconfiguration for this CID (detection id, name, cluster, namespace, resource, type, severity, detection type, prevented, and cloud service):
| detection_id | detection_name | cluster_name | namespace | resource_name | resource_type | severity | detection_type | prevented | cloud_service |
|---|---|---|---|---|---|---|---|---|---|
| iom-lab-1 | Privileged container | lab-eks-1 | default | api | Pod | High | Misconfiguration | false | eks |
| iom-lab-2 | HostPath volume | lab-aks-1 | kube-system | worker | Pod | Medium | Misconfiguration | true | aks |
Filter with FQL cluster_name:'lab-eks-1' to match Privileged container.
Leave the filter empty to see both rows.
Leave the filter empty, then Run search. The table still shows Privileged container and HostPath volume.
Open Privileged container. Detail shows detection id, name, cluster, namespace, resource, type, severity, detection type, prevented, cloud service, and CID.
K8s IOMs is not Custom IOA, not Kubernetes clusters, not K8s cloud clusters, not K8s combined clusters, not K8s deployments, and not container vulns. Custom IOA stays on Custom IOA. Kubernetes stays on Kubernetes. K8s cloud clusters stays on K8s cloud clusters. K8s combined clusters stays on K8s combined clusters. K8s deployments stays on K8s deployments. Container vulnerabilities stay on Container vulnerabilities.