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

V-275566

CAT I (High)

Ubuntu OS must require authentication upon booting into single-user and maintenance modes.

Rule ID

SV-275566r1147748_rule

STIG

Riverbed NetIM OS Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000213

Discussion

To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.

Check Content

Verify Ubuntu OS requires a password for authentication upon booting into single-user and maintenance modes by using the following command:  
  
     $ sudo grep -i password /boot/grub/grub.cfg  
  
     password_pbkdf2 root grub.pbkdf2.sha512.10000.03255F190F0E2F7B4F0D1C3216012309162F022A7A636771 
  
If the root password entry does not begin with "password_pbkdf2", this is a finding.

Fix Text

Configure Ubuntu OS to require a password for authentication upon booting into single-user and maintenance modes.  

Note: GRUB password will need to be disabled prior to upgrade of the NETIM System if done unattended.
  
Generate an encrypted (grub) password for root by using the following command:  
  
     $ grub-mkpasswd-pbkdf2  
     Enter Password:  
     Reenter Password: 
     PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.03255F190F0E2F7B4F0D1C3216012309162F022A7A636771 
  
Using the hash from the output, modify the "/etc/grub.d/40_custom" file by using the following command to add a boot password:  
  
     $ sudo sed -i '$i set superusers=\"root\"\npassword_pbkdf2 root <hash>' /etc/grub.d/40_custom  
  
where <hash> is the hash generated by grub-mkpasswd-pbkdf2 command.  
  
Generate an updated "grub.conf" file with the new password by using the following command:  
  
     $ sudo update-grub