Add documentation about CIS hardening and compliance verification

[olljanat]

Based on #957 it looks that at least some point target have been made Talos CIS compliance but I was not able find if those tests still run and that where results would be stored.

What I have found so far is that https://github.com/aquasecurity/kube-bench/blob/main/job.yaml need to be modified on way that these mounts are disabled (maybe it would make sense to include those as empty folders? ):

• /etc/systemd
• /lib/systemd/
• /srv/kubernetes/

After that scan can be run and this was result on v0.11.5:
kube-bench_v0.11.5_result.log

Many of those tests fails because files are on different place (e.g. files on /etc/kubernetes/manifests/ contains "talos-" prefix).
However not everyone is ready for all CIS requirements (e.g. disabling root containers) so probably best option would be add option to enable CIS hardening (like RKE2 does) and probably that should be done on way that it is first added as option is which is disabled by default and then on some future version change it other way around (as many might miss that setting unless it is enabled by default).

Also some of those failing tests can be handled by just explaining them on documentation about how Talos does things differently.

[smira]

So after some discussion internally, our first step would be:

1. Go over existing CIS benchmarks, and make sure Talos has either integration or unit-test verifying it (if applies to Talos).
2. If there's something that can be improved in Talos to comply with CIS, fix it.

Running existing CIS benchmarks on Talos makes little sense, as they are kubeadm based, and don't quite work for Talos.

[smira]

https://github.com/aquasecurity/kube-bench/tree/main/cfg/cis-1.24

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.