--kubeconfig=${KUBECONFIG} get serviceaccounts -A -o json | jq -r '.items[] | select(.metadata.name=="default") | select((.automountServiceAccountToken == null) or (.automountServiceAccountToken == default_binding="$(kubectl get rolebindings,clusterrolebindings -A -o json | jq -r '.items[] | select(.subjects[].kind=="ServiceAccount" and .subjects[].name=="default" and .metadata.name=="default") false. Audit: kubectl --kubeconfig=/root/.kube/config get psp -o json | jq .items[] | jq -r 'select((.spec.hostPID == null) or CIS Benchmark Rancher Self-Assessment Guide - v2.4 50 (.spec.hostPID

--kubeconfig=${KUBECONFIG} get serviceaccounts -A -o json | jq -r '.items[] | select(.metadata.name=="default") | select((.automountServiceAccountToken == null) or (.automountServiceAccountToken == default_binding="$(kubectl get rolebindings,clusterrolebindings -A -o json | jq -r '.items[] | select(.subjects[].kind=="ServiceAccount" and .subjects[].name=="default" and .metadata.name=="default") Rancher v2.5 50 kubectl --kubeconfig=/root/.kube/config get psp -o json | jq .items[] | jq -r 'select((.spec.hostPID == null) or (.spec.hostPID == false))' | jq .metadata.name | wc -l | xargs -I

organization's change management process for user accounts. Audit In the Rancher UI, select Global Select Security Select Authentication Ensure the authentication provider for your environment is active prevent users from using Rancher resources to provision the nodes. Audit In the Rancher UI select Global Select Node Drivers Review the list of node drivers that are in an Active state. Remediation If

count_sa=$(kubectl get serviceaccounts --all-namespaces -o json | jq -r '.items[] | select(.metadata.name=="default") | select((.automountServiceAccountToken == null) or CIS 1.6 Benchmark - Self-Assessment for result in $(kubectl get clusterrolebinding,rolebinding -n $ns -o json | jq -r '.items[ ] | select((.subjects[].kind=="ServiceAccount" and .subjects[].name=="default") or (.subjects[].kind=="Group" echo $result) resource_count=$(kubectl get $kind $name -n $ns -o json | jq -r '.rules[] | select(.resources[] != "podsecuritypolicies")' | wc -l) if [[ ${resource_count} -gt 0 ]]; then

cluster 3. In the Cluster type, click Existing nodes. 4. Provide a name for the cluster and select the required Kubernetes version and click Next. The new cluster is registered and is displayed 5. Click on the newly created cluster name. 6. Click Get Registration Command. 7. Select the required node role and copy the command. Installation of the SUSE Rancher Kubernetes cluster Kubernetes cluster protection policy: • Crash Consistent: Select this type for point-in-time backup of namespaces. • Exclusion: Select this type if there are assets within the protection policy to

https://support.juniper.net/support/downloads/?p=contrail-networking site. Select the Contrail Analytics package from the same release page that you select the Contrail Networking manifests. Contrail Analytics is compatible

repositories to the Developer Catalog via the CLI. Through the Developer UI, OpenShift users can also select a git repo to access their code and base image with the programming language needed to deploy a

Once the service is successfully created, navigate with the Rancher UI to the Kubernetes menu, select “Infrastructure stacks” and look for the section labeled “kubernetes- loadbalancers”. You will notice