CIS RedHat OpenShift Container Platform 4 v1.5.0 L2

Audit Details

Name: CIS RedHat OpenShift Container Platform 4 v1.5.0 L2

Updated: 1/29/2024

Authority: CIS

Plugin: OpenShift

Revision: 1.0

Estimated Item Count: 35

File Details

Filename: CIS_RedHat_OpenShift_Container_Platform_4_v1.5.0_L2.audit

Size: 71.7 kB

MD5: ab5df871baf60a8a3c21c923cbd50df3
SHA256: ea66d6081405811dd8c4045d0d855a9b858e103207ffe7095457112a900f7602

Audit Items

DescriptionCategories
2.7 Ensure that a unique Certificate Authority is used for etcd

IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

3.1.1 Client certificate authentication should not be used for users - Authentications

CONFIGURATION MANAGEMENT, SYSTEM AND SERVICES ACQUISITION

3.1.1 Client certificate authentication should not be used for users - ClusterRoleBindings

CONFIGURATION MANAGEMENT, SYSTEM AND SERVICES ACQUISITION

3.1.1 Client certificate authentication should not be used for users - Identities

CONFIGURATION MANAGEMENT, SYSTEM AND SERVICES ACQUISITION

3.1.1 Client certificate authentication should not be used for users - Secrets

CONFIGURATION MANAGEMENT, SYSTEM AND SERVICES ACQUISITION

3.2.2 Ensure that the audit policy covers key security concerns - openshift-apiserver

AUDIT AND ACCOUNTABILITY

3.2.2 Ensure that the audit policy covers key security concerns - openshift-kube-apiserver

AUDIT AND ACCOUNTABILITY

4.2.8 Ensure that the kubeAPIQPS [--event-qps] argument is set to 0 or a level which ensures appropriate event capture

AUDIT AND ACCOUNTABILITY

4.2.10 Ensure that the --rotate-certificates argument is not set to false

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

4.2.11 Verify that the RotateKubeletServerCertificate argument is set to true

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

5.2.6 Minimize the admission of root containers

ACCESS CONTROL, SYSTEM AND INFORMATION INTEGRITY

5.2.9 Minimize the admission of containers with capabilities assigned

CONFIGURATION MANAGEMENT

5.2.10 Minimize access to privileged Security Context Constraints

ACCESS CONTROL, AUDIT AND ACCOUNTABILITY

5.3.2 Ensure that all Namespaces have Network Policies defined - Namespaces

SECURITY ASSESSMENT AND AUTHORIZATION, SYSTEM AND COMMUNICATIONS PROTECTION

5.3.2 Ensure that all Namespaces have Network Policies defined - NetworkPolicies

SECURITY ASSESSMENT AND AUTHORIZATION, SYSTEM AND COMMUNICATIONS PROTECTION

5.4.1 Prefer using secrets as files over secrets as environment variables

ACCESS CONTROL, IDENTIFICATION AND AUTHENTICATION, SYSTEM AND COMMUNICATIONS PROTECTION

5.4.2 Consider external secret storage

SYSTEM AND COMMUNICATIONS PROTECTION

5.5.1 Configure Image Provenance using image controller configuration parameters

CONFIGURATION MANAGEMENT, SYSTEM AND SERVICES ACQUISITION

5.7.2 Ensure that the seccomp profile is set to docker/default in your pod definitions

CONFIGURATION MANAGEMENT, SYSTEM AND SERVICES ACQUISITION

5.7.3 Apply Security Context to Your Pods and Containers

RISK ASSESSMENT, SYSTEM AND INFORMATION INTEGRITY

5.7.4 The default namespace should not be used - BuildConfigs

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - Builds

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - CronJobs

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - DaemonSets

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - DeploymentConfigs

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - Deployments

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - HorizontalPodAutoScalers

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - ImageStreams

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - Jobs

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - Pods

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - ReplicaSets

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - ReplicationControllers

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - Routes

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - Services

SYSTEM AND COMMUNICATIONS PROTECTION

5.7.4 The default namespace should not be used - StatefulSets

SYSTEM AND COMMUNICATIONS PROTECTION