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 1 hour ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to IBM Aspera Platform 4.2 Security Technical Implementation Guide

V-252613

CAT I (High)

The IBM Aspera High-Speed Transfer Endpoint must be configured to comply with the required TLS settings in NIST SP 800-52.

Rule ID

SV-252613r818009_rule

STIG

IBM Aspera Platform 4.2 Security Technical Implementation Guide

Version

V1R3

CCIs

CCI-000068

Discussion

SP 800-52 provides guidance on using the most secure version and configuration of the TLS/SSL protocol. Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and unknown attacks that exploit vulnerabilities in this protocol. This requirement applies to TLS gateways (also known as SSL gateways) and is not applicable to VPN devices. Application protocols such as HTTPS and DNSSEC use TLS as the underlying security protocol thus are in scope for this requirement. NIST SP 800-52 specifies the preferred configurations for government systems.

Check Content

Verify IBM Aspera High-Speed Transfer Endpoint only uses TLS 1.2 or greater with the following command:

$ sudo /opt/aspera/bin/asuserdata -a | grep ssl_protocol
 ssl_protocol: "tlsv1.2" 
 ssl_protocol: "tlsv1.2" 

If both entries do not return "tlsv1.2" or greater , this is a finding.

Fix Text

Configure the IBM Aspera High-Speed Endpoint SSL security protocol to TLS version 1.2 or higher:

$ sudo /opt/aspera/bin/asconfigurator -x "set_server_data;ssl_protocol,tlsv1.2"

$ sudo /opt/aspera/bin/asconfigurator -x "set_client_data;ssl_protocol,tlsv1.2"

Restart the IBM Aspera Node service to activate the changes.

$ sudo systemctl restart asperanoded.service