Defined notes and rules for BSI APP.4.4.A17

[benruland]

Description:
Notes / Rules for BSI APP4.4.A17

Rationale:
As we have multiple customers asking for a BSI profile to be included in the compliance-operator, we are contributing a profile. To provide a better review process, the individual controle are implemented as separate PRs.

This is a follow-up of #11659. It was breaken up for better reviewability.

[openshift-ci]

Hi @benruland. 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-sigs/prow repository.

[github-actions]

Start a new ephemeral environment with changes proposed in this pull request:

Fedora Environment

Oracle Linux 8 Environment

[github-actions]

🤖 A k8s content image for this PR is available at:
ghcr.io/complianceascode/k8scontent:12153
This image was built from commit: 241636c

Click here to see how to deploy it

If you alread have Compliance Operator deployed:
utils/build_ds_container.py -i ghcr.io/complianceascode/k8scontent:12153

Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and:
CONTENT_IMAGE=ghcr.io/complianceascode/k8scontent:12153 make deploy-local

[codeclimate]

Code Climate has analyzed commit 241636c and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 59.4% (0.0% change).

View more on Code Climate.

[sluetze]

you should number the sections here.

  (1) Nodes SHOULD send a cryptographically secured (and, if possible, TPM-verified) status
  message to the control plane. (2) The control plane SHOULD ONLY accept nodes into a cluster
  that have successfully proven their integrity.

[yuumasato]

@sluetze Would you like to handle this on a subsequent PR?

Also, the addition of bsi: references in the rules is not needed anymore.

[BhargaviGudi]

Verification passed
Verified the content of the PR and rules listed according to the section.
/lgtm