Merge pull request #10289 from jhrozek/STIG-SC-24

OCP4 STIG: Two SRGs that relate to SC-24 are inherently met

controls/srg_ctr/SRG-APP-000225-CTR-000570.yml

@@ -5,3 +5,9 @@ controls:
   title: {{{ full_name }}} runtime must fail to a secure state if system initialization
     fails, shutdown fails, or aborts fail.
   status: inherently met
+  artifact_description: |-
+    Supporting evidence is in the following documentation
+    https://docs.openshift.com/container-platform/latest/support/gathering-cluster-data.html
+  status_justification: |-
+    In the event that there is a failure or disruption to the OpenShift platform, information necessary to identifying the cause would be preserved. The cluster state (resource definitions) is preserved by etcd, audit and system logs are preserved via journald service at the node levels. The following guide provide steps on how to gather cluster data in order to investigate issue with the cluster.
+    https://docs.openshift.com/container-platform/latest/support/gathering-cluster-data.html

controls/srg_ctr/SRG-APP-000226-CTR-000575.yml

@@ -5,3 +5,9 @@ controls:
   title: {{{ full_name }}} must preserve any information necessary to determine
     the cause of the disruption or failure.
   status: inherently met
+  artifact_description: |-
+    Supporting evidence is in the following documentation
+    https://docs.openshift.com/container-platform/latest/support/gathering-cluster-data.html
+  status_justification: |-
+    In the event that there is a failure or disruption to the OpenShift platform, information necessary to identifying the cause would be preserved. The cluster state (resource definitions) is preserved by etcd, audit and system logs are preserved via journald service at the node levels. The following guide provide steps on how to gather cluster data in order to investigate issue with the cluster.
+    https://docs.openshift.com/container-platform/latest/support/gathering-cluster-data.html