Red Hat lists certified container images for Red Hat products and partner offerings from the Container Images section of the Red Hat Ecosystem Catalog. From that catalog, you can see details of each image, including CVE, software packages listings, and health scores.

Red Hat uses a health index to reflect the security risk for each container provided through the Red Hat Ecosystem Catalog. Because containers consume software provided by Red Hat and the errata process, old, stale containers are insecure whereas new, fresh containers are more secure.

The SELinux context of the container The container user ID The use of host namespaces and networking The allocation of an FSGroup that owns the pod volumes The configuration of allowable supplemental groups Whether a container requires write access to its root file system The usage of volume types The configuration of allowable seccomp profiles

Master Kubernetes security hardening with pod security standards, network policies, RBAC, OPA Gatekeeper, Falco runtime protection, and admission controllers.

Running of privileged containers. Capabilities a container can request to be added. Use of host directories as volumes. The SELinux context of the container. The user ID. The use of host namespaces and networking. Allocating an FSGroup that owns the pod’s volumes Configuring allowable supplemental groups Requiring the use of a read only root file system Controlling the usage of volume types ...

Learn Kubernetes SecurityContext for container security. Configure runAsUser, capabilities, readOnlyRootFilesystem, and secure container execution.

This hands-on tutorial is for developers and cluster administrators who are interested in learning how to deploy workloads on a Red Hat OpenShift cluster that need access to protected Linux functions.

Kubernetes security best practices for production clusters: RBAC, Pod Security Standards, network policies, supply-chain signing, and CIS Benchmark coverage.

Kubernetes security is complex, with attack surfaces spanning container images, cluster configurations, network policies, secrets management, and runtime behavior. A single misconfiguration can expose your entire infrastructure to threats. This comprehensive guide covers proven security practices based on our experience securing Kubernetes clusters for healthcare, financial services, and ...

Why Container Security Matters in 2026 The statistics are unambiguous and getting worse. Key Statistics and Incident Data 59% of organizations have experienced security incidents in Kubernetes or container environments (Infosecurity Magazine / Red Hat survey, 2025). 90% of organizations experienced at least one Kubernetes security incident in the past year (Red Hat, 2025). Roughly 75% of ...