Skip to content
ATO Pathways
Log In
Overview
Search
Catalogs
SCAP
OSCAL
Catalogs
Profiles
Documents
References
Knowledge Base
Platform Documentation
Compliance Dictionary
Platform Changelog
About
Catalogs
XCCDF
Guide to the Secure Configuration of Red Hat Enterprise Linux 9
Introduction
How to Use This Guide
How to Use This Guide
An XCCDF Group - A logical subset of the XCCDF Benchmark
Details
Profiles
Prose
How to Use This Guide
Readers should heed the following points when using the guide.
Formatting Conventions
Commands intended for shell execution, as well as configuration file text, are featured in a
monospace font
.
Italics
are used to indicate instances where the system administrator must substitute the appropriate information into a command or configuration file.
Read Sections Completely and in Order
Each section may build on information and recommendations discussed in prior sections. Each section should be read and understood completely; instructions should never be blindly applied. Relevant discussion may occur after instructions for an action.
Reboot Required
A system reboot is implicitly required after some actions in order to complete the reconfiguration of the system. In many cases, the changes will not take effect until a reboot is performed. In order to ensure that changes are applied properly and to test functionality, always reboot the system after applying a set of recommendations from this guide.
Root Shell Environment Assumed
Most of the actions listed in this document are written with the assumption that they will be executed by the root user running the
/bin/bash
shell. Commands preceded with a hash mark (#) assume that the administrator will execute the commands as root, i.e. apply the command via
sudo
whenever possible, or use
su
to gain root privileges if
sudo
cannot be used. Commands which can be executed as a non-root user are are preceded by a dollar sign ($) prompt.
Test in Non-Production Environment
This guidance should always be tested in a non-production environment before deployment. This test environment should simulate the setup in which the system will be deployed as closely as possible.