add controls C-0275, C-0276 for cis-1.10

Signed-off-by: YiscahLevySilas1 <[email protected]>

Author: YiscahLevySilas1

controls/C-0275-minimizetheadmissionofcontainerswishingtosharethehostprocessidnamespace.json

@@ -0,0 +1,28 @@
+{
+    "controlID": "C-0275",
+    "name": "Minimize the admission of containers wishing to share the host process ID namespace",
+    "description": "Do not generally permit containers to be run with the hostPID flag set to true.",
+    "long_description": "A container running in the host's PID namespace can inspect processes running outside the container. If the container also has access to ptrace capabilities this can be used to escalate privileges outside of the container.\n\n There should be at least one admission control policy defined which does not permit containers to share the host PID namespace.\n\n If you need to run containers which require hostPID, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+    "remediation": "Configure the Admission Controller to restrict the admission of `hostPID` containers.",
+    "manual_test": "Fetch hostPID from each pod with\n\n \n```\nget pods -A -o=jsonpath=$'{range .items[*]}{@.metadata.name}: {@.spec.hostPID}\n{end}'\n```",
+    "references": [
+        "https://workbench.cisecurity.org/sections/2633390/recommendations/4261968"
+    ],
+    "attributes": {
+    },
+    "rulesNames": [
+        "host-pid-privileges"
+    ],
+    "baseScore": 5,
+    "impact_statement": "Pods defined with `spec.hostPID: true` will not be permitted unless they are run under a specific policy.",
+    "default_value": "By default, there are no restrictions on the creation of `hostPID` containers.",
+    "category": {
+        "name" : "Workload"
+   },
+    "scanningScope": {
+        "matches": [
+            "cluster",
+            "file"
+        ]
+    }
+}

controls/C-0276-minimizetheadmissionofcontainerswishingtosharethehostipcnamespace.json

@@ -0,0 +1,28 @@
+{
+    "controlID": "C-0276",
+    "name": "Minimize the admission of containers wishing to share the host IPC namespace",
+    "description": "Do not generally permit containers to be run with the hostIPC flag set to true.",
+    "long_description": "A container running in the host's IPC namespace can use IPC to interact with processes outside the container.\n\n There should be at least one admission control policy defined which does not permit containers to share the host IPC namespace.\n\n If you need to run containers which require hostIPC, this should be definited in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.",
+    "remediation": "Add policies to each namespace in the cluster which has user workloads to restrict the admission of `hostIPC` containers.",
+    "manual_test": "To fetch hostIPC from each pod.\n\n```\nget pods -A -o=jsonpath=$'{range .items[*]}{@.metadata.name}: {@.spec.hostIPC}\n{end}'\n```",
+    "references": [
+        "https://workbench.cisecurity.org/sections/2633390/recommendations/4261969"
+    ],
+    "attributes": {
+    },
+    "rulesNames": [
+        "host-ipc-privileges"
+    ],
+    "baseScore": 5,
+    "impact_statement": "Pods defined with `spec.hostIPC: true` will not be permitted unless they are run under a specific policy.",
+    "default_value": "By default, there are no restrictions on the creation of `hostIPC` containers.",
+    "category": {
+        "name" : "Workload"
+   },
+    "scanningScope": {
+        "matches": [
+            "cluster",
+            "file"
+        ]
+    }
+}