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 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Riverbed NetIM OS Security Technical Implementation Guide

V-275627

CAT I (High)

Ubuntu OS must use strong authenticators in establishing nonlocal maintenance and diagnostic sessions.

Rule ID

SV-275627r1147931_rule

STIG

Riverbed NetIM OS Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000877

Discussion

Nonlocal maintenance and diagnostic activities are those activities conducted by individuals communicating through a network, either an external network (e.g., the internet) or an internal network. Local maintenance and diagnostic activities are those activities carried out by individuals physically present at the information system or information system component and not communicating across a network connection. Typically, strong authentication requires authenticators that are resistant to replay attacks and employ multifactor authentication. Strong authenticators include, for example, PKI where certificates are stored on a token protected by a password, passphrase, or biometric.

Check Content

Verify Ubuntu OS is configured to use strong authenticators in the establishment of nonlocal maintenance and diagnostic maintenance by using the following command: 
 
     $ sudo /usr/sbin/sshd -dd 2>&1 | awk '/filename/ {print $4}' | tr -d '\r' | tr '\n' ' ' | xargs sudo grep -iH 'usepam' 
     /etc/ssh/sshd_config:UsePAM yes 
 
If "UsePAM" is not set to "yes", is commented out, is missing, or conflicting results are returned, this is a finding.

Fix Text

Configure Ubuntu OS to use strong authentication when establishing nonlocal maintenance and diagnostic sessions.   
  
Add or modify the following line to /etc/ssh/sshd_config:  
  
UsePAM yes 
 
Restart the SSH server for changes to take effect: 
 
     $ sudo systemctl restart sshd.service