STIGhubSTIGhub
STIGsSearchCompare

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
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to VMware vRealize Operations Manager 6.x SLES Security Technical Implementation Guide

V-239505

CAT II (Medium)

Bootloader authentication must be enabled to prevent users without privilege to gain access restricted file system resources.

Rule ID

SV-239505r661966_rule

STIG

VMware vRealize Operations Manager 6.x SLES Security Technical Implementation Guide

Version

V2R2

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

To verify a boot password exists. In "/boot/grub/menu.lst" run the following command:

# grep password /boot/grub/menu.lst

The output should show the following: 

password --encrypted $1$[rest-of-the-password-hash]

If it does not, this is a finding.

Fix Text

Run the following command: 

# /usr/sbin/grub-md5-crypt 

An MD5 password is generated. After the password is supplied, the command supplies the md5 hash output.

Append the password to the menu.lst file by running the following command:

echo 'password --md5 <hash from grub-md5-crypt>' >> /boot/grub/menu.lst

Or use "yast2" to set the bootloader password:

Open the Boot Loader Installation tab.
Click Boot Loader Options.
Activate the Protect Boot Loader with Password option with a click and type in your Password twice.

Click "OK" twice to save the changes.