II - Mission Support Sensitive
Rules and Groups employed by this XCCDF Profile
-
SRG-OS-000077-GPOS-00045
Group -
SLEM 5 must not allow passwords to be reused for a minimum of five generations.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user...Rule Medium Severity -
SRG-OS-000073-GPOS-00041
Group -
SLEM 5 must configure the Linux Pluggable Authentication Modules (PAM) to only store encrypted representations of passwords.
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily c...Rule Medium Severity -
SRG-OS-000480-GPOS-00227
Group -
SLEM 5 must not be configured to allow blank or null passwords.
Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily c...Rule High Severity -
SRG-OS-000480-GPOS-00227
Group -
SLEM 5 must not have accounts configured with blank or null passwords.
If an account has an empty password, anyone could log on and run commands with the privileges of that account. Accounts with empty passwords should never be used in operational environments.Rule High Severity -
SRG-OS-000075-GPOS-00043
Group -
SLEM 5 must employ user passwords with a minimum lifetime of 24 hours (one day).
Enforcing a minimum password lifetime helps prevent repeated password changes to defeat the password reuse or history enforcement requirement. If users are allowed to immediately and continually ch...Rule Medium Severity -
SRG-OS-000076-GPOS-00044
Group -
SLEM 5 must employ user passwords with a maximum lifetime of 60 days.
Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed periodically. If SLEM 5 does not limit the lifetime of passwords and force users to change th...Rule Medium Severity -
SRG-OS-000077-GPOS-00045
Group -
SLEM 5 must employ a password history file.
Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. If the information system or application allows the user...Rule Medium Severity -
SRG-OS-000073-GPOS-00041
Group -
SLEM 5 must employ FIPS 140-2/140-3-approved cryptographic hashing algorithms for system authentication.
The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required level of entropy. Passwords need to be protec...Rule High Severity -
SRG-OS-000073-GPOS-00041
Group -
SLEM 5 shadow password suite must be configured to use a sufficient number of hashing rounds.
The system must use a strong hashing algorithm to store the password. The system must use a sufficient number of hashing rounds to ensure the required level of entropy. Passwords need to be protec...Rule High Severity -
SRG-OS-000120-GPOS-00061
Group -
SLEM 5 must employ FIPS 140-2/140-3 approved cryptographic hashing algorithm for system authentication (login.defs).
Unapproved mechanisms that are used for authentication to the cryptographic module are not verified and therefore cannot be relied on to provide confidentiality or integrity, and DOD data may be co...Rule Medium Severity
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.