The IBM Aspera Faspex private/secret cryptographic keys file must be group-owned by faspex to prevent unauthorized read access.
An XCCDF Rule
Description
<VulnDiscussion>Private key data is used to prove that the entity presenting a public key certificate is the certificate's rightful owner. Compromise of private key data allows an adversary to impersonate the key holder.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-252593r831507_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
Configure the /opt/aspera/faspex/config/secret.yml file to be group-owned by faspex with the following command:
$ sudo chgrp faspex /opt/aspera/faspex/config/secret.yml