Skip to content

Latest commit

 

History

History
322 lines (271 loc) · 30.6 KB

cs_benchmarks_131.md

File metadata and controls

322 lines (271 loc) · 30.6 KB
Raw
copyright lastupdated keywords subcollection
years
2024, 2024
2024-11-11
kubernetes, containers, benchmarks, 1.31, CIS benchmarks
containers

{{site.data.keyword.attribute-definition-list}}

Kubernetes version 1.31 CIS Kubernetes Benchmark

{: #cis-benchmark-131}

The Center for Internet Security (CIS) publishes the CIS Kubernetes Benchmark{: external} as a framework of specific steps to configure Kubernetes more securely and with standards that are commensurate to various industry regulations. This document contains the results of the version 1.5 CIS Kubernetes benchmark for clusters that run Kubernetes version 1.31. For more information or help understanding the benchmark, see Using the benchmark. {: shortdesc}

1 Master node security configuration

{: #cis-section-1-131}

Review the Master node security configuration results of the version 1.5 CIS Kubernetes benchmark. {: shortdesc}

1.1 Master node configuration files

{: #cis-benchmark-11-131}

Section Recommendation Scored? Level Result Responsibility
1.1.1 Ensure that the API server pod specification file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.2 Ensure that the API server pod specification file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.3 Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.5 Ensure that the scheduler pod specification file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.7 Ensure that the etcd pod specification file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.8 Ensure that the etcd pod specification file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.9 Ensure that the Container Network Interface file permissions are set to 644 or more restrictive. Not Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.10 Ensure that the Container Network Interface file ownership is set to root:root. Not Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.11 Ensure that the etcd data directory permissions are set to 700 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.12 Ensure that the etcd data directory ownership is set to etcd:etcd. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.13 Ensure that the admin.conf file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.14 Ensure that the admin.conf file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.15 Ensure that the scheduler.conf file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.16 Ensure that the scheduler.conf file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.17 Ensure that the controller-manager.conf file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.18 Ensure that the controller-manager.conf file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.19 Ensure that the Kubernetes PKI directory and file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.20 Ensure that the Kubernetes PKI certificate file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.1.21 Ensure that the Kubernetes PKI key file permissions are set to 600. Scored 1 Pass {{site.data.keyword.IBM_notm}}
{: caption="Section 1.1 Master node benchmark results" caption-side="bottom"}

1.2 API server

{: #cis-benchmark-12-131}

Section Recommendation Scored? Level Result Responsibility
1.2.1 Ensure that the --anonymous-auth argument is set to false. Not Scored 1 Fail {{site.data.keyword.IBM_notm}}
1.2.2 Ensure that the --basic-auth-file argument is not set. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.3 Ensure that the --token-auth-file parameter is not set. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.4 Ensure that the --kubelet-https argument is set to true. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.5 Ensure that the --kubelet-client-certificate and --kubelet-client-key arguments are set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.6 Ensure that the --kubelet-certificate-authority argument is set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.7 Ensure that the --authorization-mode argument is not set to AlwaysAllow. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.8 Ensure that the --authorization-mode argument includes Node. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.9 Ensure that the --authorization-mode argument includes RBAC. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.10 Ensure that the admission control plugin EventRateLimit is set. Not Scored 1 Fail {{site.data.keyword.IBM_notm}}
1.2.11 Ensure that the admission control plugin AlwaysAdmit is not set. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.12 Ensure that the admission control plugin AlwaysPullImages is set. Not Scored 1 Fail {{site.data.keyword.IBM_notm}}
1.2.13 Ensure that the admission control plugin SecurityContextDeny is set if PodSecurityPolicy is not used. Not Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.14 Ensure that the admission control plugin ServiceAccount is set. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.15 Ensure that the admission control plugin NamespaceLifecycle is set. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.16 Ensure that the admission control plugin PodSecurityPolicy is set. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.17 Ensure that the admission control plugin NodeRestriction is set. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.18 Ensure that the --insecure-bind-address argument is not set. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.19 Ensure that the --insecure-port argument is set to 0. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.20 Ensure that the --secure-port argument is not set to 0. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.21 Ensure that the --profiling argument is set to false. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.22 Ensure that the --audit-log-path argument is set. Scored 1 Fail Shared
1.2.23 Ensure that the --audit-log-maxage argument is set to 30 or as appropriate. Scored 1 Fail Shared
1.2.24 Ensure that the --audit-log-maxbackup argument is set to 10 or as appropriate. Scored 1 Fail Shared
1.2.25 Ensure that the --audit-log-maxsize argument is set to 100 or as appropriate. Scored 1 Fail Shared
1.2.26 Ensure that the --request-timeout argument is set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.27 Ensure that the --service-account-lookup argument is set to true. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.28 Ensure that the --service-account-key-file argument is set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.29 Ensure that the --etcd-certfile and --etcd-keyfile arguments are set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.30 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.31 Ensure that the --client-ca-file argument is set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.32 Ensure that the --etcd-cafile argument is set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.2.33 Ensure that the --encryption-provider-config argument is set as appropriate. Scored 1 Fail Shared
1.2.34 Ensure that encryption providers are appropriately configured. Scored 1 Fail Shared
1.2.35 Ensure that the API Server only makes use of Strong Cryptographic Ciphers. Not Scored 1 Pass {{site.data.keyword.IBM_notm}}
{: caption="Section 1.2 API server benchmark results" caption-side="bottom"}

1.3 Controller manager

{: #cis-benchmark-13-131}

Section Recommendation Scored? Level Result Responsibility
1.3.1 Ensure that the --terminated-pod-gc-threshold argument is set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.3.2 Ensure that the --profiling argument is set to false. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.3.3 Ensure that the --use-service-account-credentials argument is set to true. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.3.4 Ensure that the --service-account-private-key-file argument is set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.3.5 Ensure that the --root-ca-file argument is set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.3.6 Ensure that the RotateKubeletServerCertificate argument is set to true. Scored 2 Fail {{site.data.keyword.IBM_notm}}
1.3.7 Ensure that the --bind-address argument is set to 127.0.0.1. Scored 1 Pass {{site.data.keyword.IBM_notm}}
{: caption="Section 1.3 Controller manager benchmark results" caption-side="bottom"}

1.4 Scheduler

{: #cis-benchmark-14-131}

Section Recommendation Scored? Level Result Responsibility
1.4.1 Ensure that the --profiling argument is set to false. Scored 1 Pass {{site.data.keyword.IBM_notm}}
1.4.2 Ensure that the --bind-address argument is set to 127.0.0.1. Scored 1 Pass {{site.data.keyword.IBM_notm}}
{: caption="Section 1.4 Scheduler benchmark results" caption-side="bottom"}

2 Etcd node configuration

{: #cis-section-2-131}

Review the Etcd Node Configuration results of the version 1.5 CIS Kubernetes benchmark. {: shortdesc}

Section Recommendation Scored? Level Result Responsibility
2.1 Ensure that the --cert-file and --key-file arguments are set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
2.2 Ensure that the --client-cert-auth argument is set to true. Scored 1 Pass {{site.data.keyword.IBM_notm}}
2.3 Ensure that the --auto-tls argument is not set to true. Scored 1 Pass {{site.data.keyword.IBM_notm}}
2.4 Ensure that the --peer-cert-file and --peer-key-file arguments are set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
2.5 Ensure that the --peer-client-cert-auth argument is set to true. Scored 1 Pass {{site.data.keyword.IBM_notm}}
2.6 Ensure that the --peer-auto-tls argument is not set to true. Scored 1 Pass {{site.data.keyword.IBM_notm}}
2.7 Ensure that a unique Certificate Authority is used for etcd. Not Scored 2 Pass {{site.data.keyword.IBM_notm}}
{: caption="Section 2 Etcd node configuration benchmark results" caption-side="bottom"}

3 Control plane configuration

{: #cis-section-3-131}

Review the Control Plane Configuration results of the version 1.5 CIS Kubernetes benchmark. {: shortdesc}

3.1 Authentication and authorization

{: #cis-benchmark-31-131}

Section Recommendation Scored? Level Result Responsibility
3.1.1 Client certificate authentication should not be used for users. Not Scored 2 Pass Shared
{: caption="Section 3.1 Authentication and authorization benchmark results" caption-side="bottom"}

3.2 Logging

{: #cis-benchmark-32-131}

Section Recommendation Scored? Level Result Responsibility
3.2.1 Ensure that a minimal audit policy is created. Scored 1 Fail Shared
3.2.2 Ensure that the audit policy covers key security concerns. Not Scored 2 Fail Shared
{: caption="Section 3.2 Logging benchmark results" caption-side="bottom"}

4 Worker node security configuration

{: #cis-section-4-131}

Review the Worker Node Security Configuration results of the version 1.5 CIS Kubernetes benchmark. {: shortdesc}

4.1 Worker node configuration files

{: #cis-benchmark-41-131}

Section Recommendation Scored? Level Result Responsibility
4.1.1 Ensure that the kubelet service file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.1.2 Ensure that the kubelet service file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.1.3 Ensure that the proxy kubeconfig file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.1.4 Ensure that the proxy kubeconfig file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.1.5 Ensure that the kubelet.conf file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.1.6 Ensure that the kubelet.conf file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.1.7 Ensure that the certificate authorities file permissions are set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.1.8 Ensure that the client certificate authorities file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.1.9 Ensure that the kubelet configuration file has permissions set to 644 or more restrictive. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.1.10 Ensure that the kubelet configuration file ownership is set to root:root. Scored 1 Pass {{site.data.keyword.IBM_notm}}
{: caption="Section 4.1 Worker node configuration files benchmark results" caption-side="bottom"}

4.2 Kubelet

{: #cis-benchmark-42-131}

Section Recommendation Scored? Level Result Responsibility
4.2.1 Ensure that the --anonymous-auth argument is set to false. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.2.2 Ensure that the --authorization-mode argument is not set to AlwaysAllow. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.2.3 Ensure that the --client-ca-file argument is set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.2.4 Ensure that the --read-only-port argument is set to 0. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.2.5 Ensure that the --streaming-connection-idle-timeout argument is not set to 0. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.2.6 Ensure that the --protect-kernel-defaults argument is set to true. Scored 1 Fail {{site.data.keyword.IBM_notm}}
4.2.7 Ensure that the --make-iptables-util-chains argument is set to true. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.2.8 Ensure that the --hostname-override argument is not set. Not Scored 1 Fail {{site.data.keyword.IBM_notm}}
4.2.9 Ensure that the --event-qps argument is set to 0 or a level which ensures appropriate event capture. Not Scored 2 Pass {{site.data.keyword.IBM_notm}}
4.2.10 Ensure that the --tls-cert-file and --tls-private-key-file arguments are set as appropriate. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.2.11 Ensure that the --rotate-certificates argument is not set to false. Scored 1 Pass {{site.data.keyword.IBM_notm}}
4.2.12 Ensure that the RotateKubeletServerCertificate argument is set to true. Scored 1 Fail {{site.data.keyword.IBM_notm}}
4.2.13 Ensure that the Kubelet only makes use of Strong Cryptographic Ciphers. Not Scored 1 Pass {{site.data.keyword.IBM_notm}}
{: caption="Section 4.2 Kubelet benchmark results" caption-side="bottom"}

5 Kubernetes policies

{: #cis-section-5-131}

Review the Kubernetes Policies results of the version 1.5 CIS Kubernetes benchmark. {: shortdesc}

5.1 RBAC and service accounts

{: #cis-benchmark-51-131}

Section Recommendation Scored? Level Result Responsibility
5.1.1 Ensure that the cluster-admin role is only used where required. Not Scored 1 Pass Shared
5.1.2 Minimize access to secrets. Not Scored 1 Fail Shared
5.1.3 Minimize wildcard use in Roles and ClusterRoles. Not Scored 1 Fail Shared
5.1.4 Minimize access to create pods. Not Scored 1 Pass Shared
5.1.5 Ensure that default service accounts are not actively used. Scored 1 Fail Shared
5.1.6 Ensure that Service Account Tokens are only mounted where necessary. Not Scored 1 Fail Shared
{: caption="Section 5.1 RBAC and service accounts benchmark results" caption-side="bottom"}

5.2 Pod security policies

{: #cis-benchmark-52-131}

Section Recommendation Scored? Level Result Responsibility
5.2.1 Minimize the admission of privileged containers. Not Scored 1 Pass Shared
5.2.2 Minimize the admission of containers wishing to share the host process ID namespace. Scored 1 Pass Shared
5.2.3 Minimize the admission of containers wishing to share the host IPC namespace. Scored 1 Pass Shared
5.2.4 Minimize the admission of containers wishing to share the host network namespace. Scored 1 Pass Shared
5.2.5 Minimize the admission of containers with allowPrivilegeEscalation. Scored 1 Pass Shared
5.2.6 Minimize the admission of root containers. Not Scored 2 Pass Shared
5.2.7 Minimize the admission of containers with the NET_RAW capability. Not Scored 1 Pass Shared
5.2.8 Minimize the admission of containers with added capabilities. Not Scored 1 Pass Shared
5.2.9 Minimize the admission of containers with capabilities assigned. Not Scored 2 Pass Shared
{: caption="Section 5.2 Pod security policies benchmark results" caption-side="bottom"}

5.3 Network policies and CNI

{: #cis-benchmark-53-131}

Section Recommendation Scored? Level Result Responsibility
5.3.1 Ensure that the CNI in use supports Network Policies. Not Scored 1 Pass {{site.data.keyword.IBM_notm}}
5.3.2 Ensure that all Namespaces have Network Policies defined. Scored 2 Fail Shared
{: caption="Section 5.3 Network policies and CNI benchmark results" caption-side="bottom"}

5.4 Secrets management

{: #cis-benchmark-54-131}

Section Recommendation Scored? Level Result Responsibility
5.4.1 Prefer using secrets as files over secrets as environment variables. Not Scored 1 Pass Shared
5.4.2 Consider external secret storage. Not Scored 2 Fail Shared
{: caption="Section 5.4 Secrets management benchmark results" caption-side="bottom"}

5.5 Extensible admission control

{: #cis-benchmark-55-131}

Section Recommendation Scored? Level Result Responsibility
5.5.1 Configure Image Provenance using ImagePolicyWebhook admission controller. Not Scored 2 Fail Shared
{: caption="Section 5.5 Extensible admission control benchmark results" caption-side="bottom"}

5.7 General policies

{: #cis-benchmark-56-131}

Section Recommendation Scored? Level Result Responsibility
5.7.1 Create administrative boundaries between resources using namespaces. Not Scored 1 Pass Shared
5.7.2 Ensure that the seccomp profile is set to docker/default in your pod definitions. Not Scored 2 Fail Shared
5.7.3 Apply Security Context to Your Pods and Containers. Not Scored 2 Fail Shared
5.7.4 The default namespace should not be used. Scored 2 Fail Shared
{: caption="Section 5.7 General policies benchmark results" caption-side="bottom"}

{{site.data.keyword.IBM_notm}} remediations and explanations

{: #cis-benchmark-remediations-131}

Review information from {{site.data.keyword.IBM_notm}} on the CIS Benchmark results. {: shortdesc}

Section Remediation and explanation
1.2.1 {{site.data.keyword.containerlong_notm}} utilizes RBAC for cluster protection, but allows anonymous discovery, which is considered reasonable per CIS Kubernetes Benchmark{: external}.
1.2.10 {{site.data.keyword.containerlong_notm}} does not enable the EventRateLimit{: external} admission controller since it is a Kubernetes alpha feature.
1.2.12 {{site.data.keyword.containerlong_notm}} does not enable the AlwaysPullImages{: external} admission controller since it overrides a container's imagePullPolicy and may impact performance.
1.2.13 {{site.data.keyword.containerlong_notm}} can optionally configure pod security admission, which is similar to the unsupported Kubernetes pod security policies{: external}.
1.2.16 {{site.data.keyword.containerlong_notm}} can optionally configure pod security admission, which is similar to the unsupported Kubernetes pod security policies{: external}.
1.2.22 {{site.data.keyword.containerlong_notm}} can optionally enable Kubernetes API server auditing.
1.2.23 {{site.data.keyword.containerlong_notm}} can optionally enable Kubernetes API server auditing.
1.2.24 {{site.data.keyword.containerlong_notm}} can optionally enable Kubernetes API server auditing.
1.2.25 {{site.data.keyword.containerlong_notm}} can optionally enable Kubernetes API server auditing.
1.2.33 {{site.data.keyword.containerlong_notm}} can optionally enable a Kubernetes Key Management Service (KMS) provider.
1.2.34 {{site.data.keyword.containerlong_notm}} can optionally enable a Kubernetes Key Management Service (KMS) provider.
1.3.6 {{site.data.keyword.containerlong_notm}} rotates certificates on every worker node reload or update.
3.2.1 {{site.data.keyword.containerlong_notm}} can optionally enable Kubernetes API server auditing.
3.2.2 {{site.data.keyword.containerlong_notm}} can optionally enable Kubernetes API server auditing.
4.2.6 {{site.data.keyword.containerlong_notm}} does not protect kernel defaults to allow customers to tune kernel parameters.
4.2.8 {{site.data.keyword.containerlong_notm}} ensures that the hostname matches the name issued by the infrastructure.
4.2.11 {{site.data.keyword.containerlong_notm}} rotates certificates on every worker node reload or update.
4.2.12 {{site.data.keyword.containerlong_notm}} rotates certificates on every worker node reload or update.
5.1.2 {{site.data.keyword.containerlong_notm}} deploys some system components that could have their Kubernetes secret access further restricted.
5.1.3 {{site.data.keyword.containerlong_notm}} deploys some system components that could have their Kubernetes resource access further restricted.
5.1.5 {{site.data.keyword.containerlong_notm}} does not set automountServiceAccountToken: false{: external} for each default service account.
5.1.6 {{site.data.keyword.containerlong_notm}} deploys some system components that could set automountServiceAccountToken: false{: external}.
5.2.1 {{site.data.keyword.containerlong_notm}} can optionally configure pod security admission, which is similar to the unsupported Kubernetes pod security policies{: external}.
5.2.2 {{site.data.keyword.containerlong_notm}} can optionally configure pod security admission, which is similar to the unsupported Kubernetes pod security policies{: external}.
5.2.3 {{site.data.keyword.containerlong_notm}} can optionally configure pod security admission, which is similar to the unsupported Kubernetes pod security policies{: external}.
5.2.4 {{site.data.keyword.containerlong_notm}} can optionally configure pod security admission, which is similar to the unsupported Kubernetes pod security policies{: external}.
5.2.5 {{site.data.keyword.containerlong_notm}} can optionally configure pod security admission, which is similar to the unsupported Kubernetes pod security policies{: external}.
5.2.6 {{site.data.keyword.containerlong_notm}} can optionally configure pod security admission, which is similar to the unsupported Kubernetes pod security policies{: external}.
5.2.7 {{site.data.keyword.containerlong_notm}} can optionally configure pod security admission, which is similar to the unsupported Kubernetes pod security policies{: external}.
5.2.8 {{site.data.keyword.containerlong_notm}} can optionally configure pod security admission, which is similar to the unsupported Kubernetes pod security policies{: external}.
5.2.9 {{site.data.keyword.containerlong_notm}} can optionally configure pod security admission, which is similar to the unsupported Kubernetes pod security policies{: external}.
5.3.2 {{site.data.keyword.containerlong_notm}} has a set of default Calico and Kubernetes network policies defined and additional network policies can optionally be added.
5.4.2 {{site.data.keyword.containerlong_notm}} can optionally enable Secrets Manager service.
5.5.1 {{site.data.keyword.containerlong_notm}} can optionally enable image security enforcement.
5.7.2 {{site.data.keyword.containerlong_notm}} does not annotate all pods with seccomp profiles{: external}.
5.7.3 {{site.data.keyword.containerlong_notm}} deploys some system components that do not set a pod or container securityContext{: external}.
5.7.4 {{site.data.keyword.containerlong_notm}} deploys some Kubernetes resources to the default names.
{: caption="Explanation and remediation" caption-side="bottom"}