docs: Security refrence rework

[nhennigan]

Description

We need to update our docs to include the latest info on DISA STIG and FIPS. This is the first PR where I will tackle the reference pages.

Solution

• I have moved the CIS manual audit to reference
• I have moved the DISA STIG manual audit to reference. This is taken from @louiseschmidtgen PR docs: disa-stig hardening guide #1882 disa-stig-assessment.md
• I have updated the links in the security reference page (There are TODOs but I will fill those in once I have all PRs up)

Issue

N/A

Backport

1.34 only

Checklist

• PR title formatted as type: title
• Covered by unit tests
• Covered by integration tests
• Documentation updated
• CLA signed
• Backport label added if necessary

If any item on the checklist is not complete, please provide justification why.

[louiseschmidtgen]

I think the auditing should stay in the how-to section. While there are many rules to reference we're still making users apply some of these commands. In that sense it is more of a how to in my opinion. Wdyt?

[louiseschmidtgen]

Changed the base branch to the feature branch KU-4397/fips-stig-docs-release-branch where we will collect all PRs for the docs release.

[louiseschmidtgen]

I think the auditing should stay in the how-to section. While there are many rules to reference we're still making users apply some of these commands. In that sense it is more of a how to in my opinion. Wdyt?

We discussed this async. TAs think this should be more of a reference page. We can work in the future on bringing some of the actionable steps into the how-tos.

[louiseschmidtgen]

It looks like I missed one update missing for this argument:
extra-node-kube-scheduler-args: --bind-address: 127.0.0.1 and feature-gates. I will make a commit. (I will do this in the feature branch)

[cdkbot]

Successfully created backport PR for release-1.34:

• docs: Security refrence rework [Backport release-1.34] #1910