Control implementations for CIS 1.10 implementation

[slashben]

This pull request introduces new security controls and updates to implement CIS 1.10 compliance framework. The changes include adding new JSON files for various security controls, as well as corresponding Rego rules and metadata files to enforce these controls.

This closes #651 and #647

New Security Controls:

1. Ensure Strong Cryptographic Ciphers for API Server:

   • Added a new control to ensure that the API server only uses strong cryptographic ciphers. This includes a detailed description, remediation steps, and a manual test procedure.
   • Introduced Rego rules to check and enforce the use of strong cryptographic ciphers in the API server configuration. [1] [2]
   • Added metadata for the new rule to describe its purpose and remediation.

2. Minimize Access to Create Persistent Volumes:

   • Added a new control to restrict access to creating persistent volumes, which can help prevent privilege escalation through hostPath volumes.

3. Minimize Access to Node Proxy Sub-Resource:

   • Introduced a control to limit access to the proxy sub-resource of node objects to prevent unauthorized use of the Kubelet API.

4. Minimize Access to Certificate Signing Requests:

   • Added a control to restrict access to the approval sub-resource of certificate signing requests to prevent unauthorized creation of high-privileged user accounts.

5. Minimize Access to Webhook Configuration Objects:

   • Introduced a control to minimize access to creating, modifying, or deleting webhook configuration objects to prevent privilege escalation or cluster disruption.

6. Minimize Access to Service Account Token Creation:

   • Added a control to restrict access to creating service account tokens to prevent long-lived privileged credentials and potential privilege escalation.

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success