STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated just now
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to IBM Aspera Platform 4.2 Security Technical Implementation Guide

V-252622

CAT II (Medium)

The IBM Aspera High-Speed Transfer Endpoint must not store node content-protection secrets in plain text.

Rule ID

SV-252622r831522_rule

STIG

IBM Aspera Platform 4.2 Security Technical Implementation Guide

Version

V1R3

CCIs

CCI-002475CCI-002476

Discussion

Configuring the network element to implement organization-wide security implementation guides and security checklists ensures compliance with federal standards and establishes a common security baseline across DoD that reflects the most restrictive security posture consistent with operational requirements. Configuration settings are the set of parameters that can be changed that affect the security posture and/or functionality of the network element. Security-related parameters are those parameters impacting the security state of the network element, including the parameters required to satisfy other security control requirements. For the network element, security-related parameters include settings for network traffic management configurations. Aspera recommends that you do not store content-protection secrets in aspera.conf.

Check Content

Verify the IBM High-Speed Transfer Endpoint does not store node content-protection secrets in plain text with the following command:

$ sudo /opt/aspera/bin/asuserdata -a | grep secret | grep transfer

transfer_encryption_content_protection_secret: "AS_NULL"

If the "transfer_encryption_content_protection_secret" is not "AS_NULL", this is a finding.

Fix Text

Configure the IBM High-Speed Transfer Endpoint to not store node content-protection secrets in plain text.

Remove any secrets from the /opt/aspera/aspera.conf file with the following command:

$ sudo /opt/aspera/bin/asconfigurator -x "set_node_data; transfer_encryption_content_protection_secret,AS_NULL"

Restart the IBM Aspera Node service to activate the changes.

$ sudo systemctl restart asperanoded.service