OpenShift must use FIPS-validated cryptographic mechanisms to protect the integrity of log information.
An XCCDF Rule
Description
<VulnDiscussion>To fully investigate an incident and to have trust in the audit data that is generated, it is important to put in place data protections. Without integrity protections, unauthorized changes may be made to the audit files and reliable forensic analysis and discovery of the source of malicious system activity may be degraded. Although digital signatures are one example of protecting integrity, this control is not intended to cause a new cryptographic hash to be generated every time a record is added to a log file. Integrity protections can also be implemented by using cryptographic techniques for security function isolation and file system protections to protect against unauthorized changes.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-257536r960951_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
Edit the Cluster Log Forwarder configuration to configure TLS on the transport by executing the following:
oc edit clusterlogforwarder <name> -n openshift-logging
For any output->url value that is not using a secure transport, edit the url to use a secure (https:// or tls://) transport.