Restrict access to cross datavolumes cloning

보통레벨 1수동 검토openshift-virt

설명

Datavolume cross-namespace cloning allows cloning a datavolume from one namespace to another, breaking the namespace isolation. The benchmark marks this recommendation Manual; TMAegis reports it as a manual review item with the audit steps.

점검 방법

감사 방식: 수동 검토

이 권장 사항은 자동으로 점검할 수 없습니다. --include-manual 옵션을 전달하면 스캔 결과에 이 지침과 함께 표시됩니다.

To check which role bindings have the ability to clone across namespaces, use the following command where to list all the rolebinding and verify which one has a ClusterRole which enables it to operate on data volumes and have bound a service account in another namespace . Ensure that the destination namespace is a desired one. $ oc get rolebinding - n <source - namespace> <allow - clone - to - user> - oyaml Output will be in the following format: apiVersion: rbac.authorization.k8s.io/v1 kind: RoleBinding metadata: name: <role - binding - name> namespace: <source namespace> subjects: - kind: ServiceAccount name: default namespace: <destination namespace> roleRef: kind: ClusterRole name: ...

조치 방법

조치 방식: 가이드 또는 인프라 패치

Remove any rolebinding resources that grant unintended access across namespaces. Please refer to the latest OpenShift documentation for details on this process.

속성

운영 체제: 모두
태그: openshift-virtmanual-review
참고 자료: CIS Red Hat OpenShift Virtual Machine Extension Benchmark v1.0.0 - 3.1 Restrict access to cross datavolumes cloning