OCP4 CIS 5.2.5 (SCC privilege escalation)

[nkinder]

Description:

• This adds a rule to check if SCC privilege escalation is disabled for at least one SCC.

Rationale:

• This is required to satisfy CIS 5.2.5.

[openshift-ci-robot]

Hi @nkinder. Thanks for your PR.

I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jhrozek]

/ok-to-test

[jhrozek]

The rule and the check look good. The default OCP4 installation is not compliant at the moment so I put a note to the draft CIS document that we need to follow up and see why even the restricted SCC doesn't prevent privilege escalation.