K8s IOM entities
This local console is not CrowdStrike production. IOM entities 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 IOM entities
Choose K8s IOM entities 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 by ids iom-lab-1 to match Privileged container.
Leave the filter empty to see both rows.
Open Privileged container. Detail shows detection id, name, cluster, namespace, resource, type, severity, detection type, prevented, cloud service, and CID.
K8s IOM entities is not K8s IOMs (the combined FQL list), not K8s IOM count, and not K8s IOM dates. K8s IOMs stays on K8s IOMs. K8s IOM count stays on K8s IOM count. K8s IOM dates stays on K8s IOM dates.