Check ID:
Provider: Kubernetes
Service:
Severity: HIGH
Categories:
Resource type:
core_seccomp_profile_docker_defaultProvider: Kubernetes
Service:
coreSeverity: HIGH
Categories:
container-securityResource type:
PodWhat this check verifies
Kubernetes Pods and their containers specify the runtime default seccomp profile usingseccompProfile.type: RuntimeDefault in the security context.
The evaluation looks for this setting at the Pod level or per container.
Risk
Without seccomp RuntimeDefault, containers may run unconfined and invoke risky syscalls, expanding the kernel attack surface.- Container escape, privilege escalation (integrity)
- Data access or exfiltration (confidentiality)
- Node or workload disruption (availability)
Recommendation
Enforce least privilege for syscalls:- Set
seccompProfile.type: RuntimeDefaulton Pods/containers - Use tailored profiles for sensitive workloads
- Avoid privileged or unconfined containers; drop unused capabilities
- Combine with AppArmor/SELinux and policy guardrails to enforce and audit
Remediation
- CLI
- Terraform
- Dashboard steps
References
- https://kubernetes.io/docs/tutorials/clusters/seccomp/
- https://docs.docker.com/engine/security/seccomp/
Where this check fires
This check runs on every scheduled scan against your Kubernetes account. Findings appear at Cloud Security → Findings filterable byCheck ID = core_seccomp_profile_docker_default. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to Kubernetes checks