← Back to IBM Aspera Platform 4.2 Security Technical Implementation Guide

V-252576

CAT II (Medium)

The IBM Aspera Faspex private/secret cryptographic keys file must have a mode of 0600 or less permissive to prevent unauthorized read access.

Rule ID

SV-252576r831500_rule

STIG

IBM Aspera Platform 4.2 Security Technical Implementation Guide

Version

V1R3

CCIs

CCI-002165

Discussion

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.

Check Content

If the IBM Aspera Faspex feature of the Aspera Platform is not installed, this is Not Applicable.

Verify the /opt/aspera/faspex/config/secret.yml file has a mode of "0600" or less permissive with the following command:

$ sudo stat -c "%a %n" /opt/aspera/faspex/config/secret.yml

600 /opt/aspera/faspex/config/secret.yml

If the resulting mode is more permissive than "0600", this is a finding.

Fix Text

Configure the /opt/aspera/faspex/config/secret.yml file to have a mode of "0600" or less permissive with the following command:

$ sudo chmod 0600 /opt/aspera/faspex/config/secret.yml