Red Hat Enterprise Linux 5 Security Technical Implementation Guide
Pick two releases to diff their requirements.
Open a previous version of this STIG.
Digest of Updates ✎ 357
Comparison against the immediately-prior release (V1R7). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.
Content changes 357
- V-1011 Low check Inetd or xinetd logging/tracing must be enabled.
- V-1021 Medium check The X server must have the correct options enabled.
- V-1022 Medium check An X server must have none of the following options enabled: -ac, -core (except for debugging purposes), or -nolock.
- V-1023 Medium check The system must not run an Internet Network News (INN) server.
- V-1025 Medium check The /etc/access.conf file must be owned by root.
- V-1027 Medium check The /etc/smb.conf file must be owned by root.
- V-1028 Medium check The /etc/smb.conf file must have mode 0644 or less permissive.
- V-1029 Medium check The /etc/smbpasswd file must be owned by root.
- V-1032 Medium check Users must not be able to change passwords more than once every 24 hours.
- V-1047 Medium check The system must not permit root logins using remote access programs such as ssh.
- V-1048 Medium check Audio devices must have mode 0660 or less permissive.
- V-1049 Medium check Audio devices must be owned by root.
- V-1054 Medium check The /etc/access.conf file must have a privileged group owner.
- V-1055 Medium check The /etc/security/access.conf file must have mode 0640 or less permissive.
- V-1056 Medium check The /etc/smb.conf file must be group-owned by root, bin, sys, or system.
- V-1058 Medium check The smbpasswd file must be group-owned by root.
- V-1059 Medium check The smbpasswd file must have mode 0600 or less permissive.
- V-1061 Medium check Audio devices must be group-owned by root, sys, bin, or system.
- V-1062 Low check The root shell must be located in the / file system.
- V-11940 High check The operating system must be a supported release.
- V-11947 Medium check The system must require passwords contain a minimum of 14 characters.
- V-11948 Medium check The system must require passwords contain at least one uppercase alphabetic character.
- V-11972 Medium check The system must require passwords contain at least one numeric character.
- V-11973 Medium check The system must require passwords contain at least one special character.
- V-11975 Medium check The system must require passwords contain no more than three consecutive repeating characters.
- V-11976 Medium check User passwords must be changed at least every 60 days.
- V-11981 Medium check All global initialization files must have mode 0644 or less permissive.
- V-11982 Medium check All global initialization files must be owned by root.
- V-11983 Medium check All global initialization files must be group-owned by root, sys, bin, other, system, or the system default.
- V-11984 Medium check All skeleton files and directories (typically in /etc/skel) must be owned by root or bin.
- V-11985 Medium check All global initialization files' executable search paths must contain only absolute paths.
- V-11986 Medium check All local initialization files' executable search paths must contain only absolute paths.
- V-11988 High check There must be no .rhosts, .shosts, hosts.equiv, or shosts.equiv files on the system.
- V-11989 Medium check The .rhosts file must not be supported in PAM.
- V-11995 Medium check Default system accounts (with the exception of root) must not be listed in the cron.allow file or must be included in the cron.deny file, if cron.allow does not exist.
- V-11996 Low check Process core dumps must be disabled unless needed.
- V-11997 Low check The kernel core dump data directory must be owned by root.
- V-11999 Medium check The system must implement non-executable program stacks.
- V-12002 Medium check The system must not forward IPv4 source-routed packets.
- V-12003 Low check A separate file system must be used for user home directories (such as /home or an equivalent).
- V-12004 Medium check The system must log informational authentication data.
- V-12005 Medium check Inetd and xinetd must be disabled or removed if no network services utilizing them are enabled.
- V-12006 Medium check The SMTP service HELP command must not be enabled.
- V-12011 Medium check All FTP users must have a default umask of 077.
- V-12019 Medium check The snmpd.conf file must be owned by root.
- V-12023 Medium check IP forwarding for IPv4 must not be enabled, unless the system is a router.
- V-12030 Medium check The system's access control program must be configured to grant or deny system access to specific hosts.
- V-12039 Medium check The /etc/securetty file must be owned by root.
- V-12040 Medium check The /etc/securetty file must have mode 0600 or less permissive.
- V-12765 Medium checkfix The system must use and update a DoD-approved virus scan program.
- V-22290 Medium check The system clock must be synchronized continuously, or at least daily.
- V-22294 Medium check The time synchronization configuration file (such as /etc/ntp.conf) must be owned by root.
- V-22296 Medium check The time synchronization configuration file (such as /etc/ntp.conf) must have mode 0640 or less permissive.
- V-22298 Low check The system must limit users to 10 simultaneous system logins, or a site-defined number, in accordance with operational requirements.
- V-22302 Medium check The system must enforce compliance of the entire password during authentification.
- V-22303 Medium check The system must use a FIPS 140-2 approved cryptographic hashing algorithm for generating account password hashes.
- V-22304 Medium check The password hashes stored on the system must have been generated using a FIPS 140-2 approved cryptographic hashing algorithm.
- V-22305 Medium check The system must require passwords contain at least one lowercase alphabetic character.
- V-22306 Medium check The system must require at least four characters be changed between the old and new passwords during a password change.
- V-22307 Medium check The system must prevent the use of dictionary words for passwords.
- V-22308 Low check The system must restrict the ability to switch to the root user to members of a defined group.
- V-22310 Medium check The root account's library search path must be the system default and must contain only absolute paths.
- V-22311 Medium check The root account's list of preloaded libraries must be empty.
- V-22319 Medium check The /etc/resolv.conf file must be owned by root.
- V-22321 Medium check The /etc/resolv.conf file must have mode 0644 or less permissive.
- V-22323 Medium check The /etc/hosts file must be owned by root.
- V-22325 Medium check The /etc/hosts file must have mode 0644 or less permissive.
- V-22327 Medium check The /etc/nsswitch.conf file must be owned by root.
- V-22328 Medium check The /etc/nsswitch.conf file must be group-owned by root, bin, or sys.
- V-22329 Medium check The /etc/nsswitch.conf file must have mode 0644 or less permissive.
- V-22332 Medium check The /etc/passwd file must be owned by root.
- V-22333 Medium check The /etc/passwd file must be group-owned by root, bin, or sys.
- V-22335 Medium check The /etc/group file must be owned by root.
- V-22336 Medium check The /etc/group file must be group-owned by root, bin, or sys.
- V-22337 Medium check The /etc/group file must have mode 0644 or less permissive.
- V-22339 Medium check The /etc/shadow file (or equivalent) must be group-owned by root, bin, or sys.
- V-22341 Medium check The /etc/gshadow file must be owned by root.
- V-22342 Medium check The /etc/gshadow file must be group-owned by root.
- V-22343 Medium check The /etc/gshadow file must have mode 0400.
- V-22347 Medium check The /etc/passwd file must not contain password hashes.
- V-22348 Medium check The /etc/group file must not contain any group password hashes.
- V-22349 Medium check The /etc/gshadow file must not contain any group password hashes.
- V-22355 Medium check Run control scripts' lists of preloaded libraries must contain only absolute paths.
- V-22358 Medium check All skeleton files (typically in /etc/skel) must be group-owned by root, bin, sys, system, or other.
- V-22365 Medium check All shell files must be group-owned by root, bin, sys, or system.
- V-22370 Low check System audit tool executables must be owned by root.
- V-22371 Low check System audit tool executables must be group-owned by root, bin, sys, or system.
- V-22372 Low check System audit tool executables must have mode 0750 or less permissive.
- V-22374 Low check The audit system must alert the SA in the event of an audit processing failure.
- V-22375 Medium check The audit system must alert the SA when the audit storage volume approaches its capacity.
- V-22376 Low check The audit system must be configured to audit account creation.
- V-22377 Low check The audit system must be configured to audit account modification.
- V-22378 Low check The audit system must be configured to audit account disabling.
- V-22382 Low check The audit system must be configured to audit account termination.
- V-22383 Medium check The audit system must be configured to audit the loading and unloading of dynamic kernel modules.
- V-22385 Medium check Crontab files must be group-owned by root, cron, or the crontab creator's primary group.
- V-22391 Medium check The cron.allow file must be group-owned by root, bin, sys, or cron.
- V-22392 Medium check The at.deny file must have mode 0600 or less permissive.
- V-22394 Medium check The cron.deny file must be group-owned by root, bin, or sys.
- V-22396 Medium check The "at" directory must be group-owned by root, bin, sys, or cron.
- V-22397 Medium check The at.allow file must be group-owned by root, bin, sys, or cron.
- V-22398 Medium check The at.deny file must be group-owned by root, bin, sys, or cron.
- V-22404 Medium check Kernel core dumps must be disabled unless needed.
- V-22405 Low check The kernel core dump data directory must be group-owned by root, bin, sys, or system.
- V-22406 Low check The kernel core dump data directory must have mode 0700 or less permissive.
- V-22408 Medium check Network interfaces must not be configured to allow user control.
- V-22410 Medium check The system must not respond to Internet Control Message Protocol v4 (ICMPv4) echoes sent to a broadcast address.
- V-22411 Medium check The system must not respond to Internet Control Message Protocol (ICMP) timestamp requests sent to a broadcast address.
- V-22414 Medium check The system must not accept source-routed IPv4 packets.
- V-22415 Medium check Proxy Address Resolution Protocol (Proxy ARP) must not be enabled on the system.
- V-22416 Medium check The system must ignore IPv4 Internet Control Message Protocol (ICMP) redirect messages.
- V-22417 Medium check The system must not send IPv4 Internet Control Message Protocol (ICMP) redirects.
- V-22418 Low check The system must log martian packets.
- V-22419 Medium check The system must be configured to use TCP syncookies when experiencing a TCP SYN flood.
- V-22421 Medium check The system must not be configured for network bridging.
- V-22422 Low check All local file systems must employ journaling or another mechanism ensuring file system consistency.
- V-22423 Medium check The inetd.conf file, xinetd.conf file, and the xinetd.d directory must be group-owned by root, bin, sys, or system.
- V-22425 Medium check The xinetd.d directory must have mode 0755 or less permissive.
- V-22427 Medium check The services file must be group-owned by root, bin, sys, or system.
- V-22429 Medium check The portmap or rpcbind service must not be running unless needed.
- V-22430 Medium check The portmap or rpcbind service must not be installed unless needed.
- V-22431 Medium check The rshd service must not be installed.
- V-22432 Medium check The rlogind service must not be running.
- V-22433 Medium check The rlogind service must not be installed.
- V-22434 Medium check The rexecd service must not be installed.
- V-22435 Medium check The hosts.lpd (or equivalent) file must be group-owned by root, bin, sys, or system.
- V-22438 Medium check The aliases file must be group-owned by root, sys, bin, or system.
- V-22444 Medium check The ftpusers file must be group-owned by root, bin, sys, or system.
- V-22447 Medium check The SNMP service must use only SNMPv3 or its successors.
- V-22451 Medium check The snmpd.conf file must be group-owned by root, bin, sys, or system.
- V-22453 Medium check The /etc/syslog.conf file must have mode 0640 or less permissive.
- V-22455 Medium check The system must use a remote syslog server (loghost).
- V-22456 Medium check The SSH client must be configured to only use the SSHv2 protocol.
- V-22458 Medium checkfix The SSH daemon must be configured to only use FIPS 140-2 approved ciphers.
- V-22460 Medium check The SSH daemon must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.
- V-22461 Medium check The SSH client must be configured to only use FIPS 140-2 approved ciphers.
- V-22462 Medium check The SSH client must be configured to not use Cipher-Block Chaining (CBC)-based ciphers.
- V-22463 Medium check The SSH client must be configured to only use Message Authentication Codes (MACs) employing FIPS 140-2 approved cryptographic hash algorithms.
- V-22470 Medium check The SSH daemon must restrict login ability to specific users and/or groups.
- V-22471 Medium check The SSH public host key files must have mode 0644 or less permissive.
- V-22472 Medium check The SSH private host key files must have mode 0600 or less permissive.
- V-22473 Low check The SSH daemon must not permit GSSAPI authentication unless needed.
- V-22474 Low check The SSH client must not permit GSSAPI authentication unless needed.
- V-22475 Low check The SSH daemon must not permit Kerberos authentication unless needed.
- V-22485 Medium check The SSH daemon must perform strict mode checking of home directory configuration files.
- V-22486 Medium check The SSH daemon must use privilege separation.
- V-22487 Medium check The SSH daemon must not allow rhosts RSA authentication.
- V-22488 Medium check The SSH daemon must not allow compression or must only allow compression after successful authentication.
- V-22489 Medium check The SSH daemon must be configured with the Department of Defense (DoD) logon banner.
- V-22491 Medium check The system must not have IP forwarding for IPv6 enabled, unless the system is an IPv6 router.
- V-22492 Medium check The Network File System (NFS) export configuration file must be group-owned by root, bin, sys, or system.
- V-22496 Medium check All Network File System (NFS) exported system files and system directories must be group-owned by root, bin, sys, or system.
- V-22499 Medium check Samba must be configured to use an authentication mechanism other than "share."
- V-22500 Medium check Samba must be configured to use encrypted passwords.
- V-22501 Medium check Samba must be configured to not allow guest access to shares.
- V-22511 Medium check The Stream Control Transmission Protocol (SCTP) must be disabled unless required.
- V-22514 Medium check The Datagram Congestion Control Protocol (DCCP) must be disabled unless required.
- V-22524 Medium check The AppleTalk protocol must be disabled or not installed.
- V-22530 Medium check The Reliable Datagram Sockets (RDS) protocol must be disabled or not installed unless required.
- V-22533 Medium check The Transparent Inter-Process Communication (TIPC) protocol must be disabled or uninstalled.
- V-22539 Medium check The Bluetooth protocol handler must be disabled or not installed.
- V-22541 Medium check The IPv6 protocol handler must not be bound to the network stack unless needed.
- V-22542 Medium check The IPv6 protocol handler must be prevented from dynamic loading unless needed.
- V-22546 Medium check The system must not have Teredo enabled.
- V-22549 Medium check The DHCP client must not send dynamic DNS updates.
- V-22550 Medium check The system must ignore IPv6 ICMP redirect messages.
- V-22557 Medium check If the system is using LDAP for authentication or account information, the LDAP TLS connection must require the server provide a certificate with a valid trust path to a trusted CA.
- V-22558 Medium check If the system is using LDAP for authentication or account information, the system must verify the LDAP server's certificate has not been revoked.
- V-22559 Medium check If the system is using LDAP for authentication or account information the /etc/ldap.conf (or equivalent) file must have mode 0644 or less permissive.
- V-22560 Medium check If the system is using LDAP for authentication or account information, the /etc/ldap.conf (or equivalent) file must be owned by root.
- V-22561 Medium check If the system is using LDAP for authentication or account information, the /etc/ldap.conf (or equivalent) file must be group-owned by root, bin, sys, or system.
- V-22563 Medium check If the system is using LDAP for authentication or account information, the TLS certificate authority file and/or directory (as appropriate) must be owned by root.
- V-22564 Medium check If the system is using LDAP for authentication or account information, the TLS certificate authority file and/or directory (as appropriate) must be group-owned by root, bin, sys, or system.
- V-22565 Medium check If the system is using LDAP for authentication or account information, the TLS certificate authority file and/or directory (as appropriate) must have mode 0644 (0755 for directories) or less permissive.
- V-22567 Medium check For systems using NSS LDAP, the TLS certificate file must be owned by root.
- V-22568 Medium check If the system is using LDAP for authentication or account information, the LDAP TLS certificate file must be group-owned by root, bin, sys, or system.
- V-22569 Medium check If the system is using LDAP for authentication or account information, the LDAP TLS certificate file must have mode 0644 or less permissive.
- V-22571 Medium check If the system is using LDAP for authentication or account information, the LDAP TLS key file must be owned by root.
- V-22572 Medium check If the system is using LDAP for authentication or account information, the LDAP TLS key file must be group-owned by root, bin, or sys.
- V-22573 Medium check If the system is using LDAP for authentication or account information, the LDAP TLS key file must have mode 0600 or less permissive.
- V-22576 Low check The system must use available memory address randomization techniques.
- V-22577 Low check Automated file system mounting tools must not be enabled unless needed.
- V-22579 Low check The system must have USB Mass Storage disabled unless needed.
- V-22580 Low check The system must have IEEE 1394 (Firewire) disabled unless needed.
- V-22582 Medium check The system must employ a local firewall.
- V-22584 Low check The system must use a Linux Security Module configured to limit the privileges of system services.
- V-22586 Medium check The system's boot loader configuration files must be owned by root.
- V-22587 Medium check The system's boot loader configuration file(s) must be group-owned by root, bin, sys, or system.
- V-22598 Low check Auditing must be enabled at boot by setting a kernel parameter.
- V-22665 Medium check The system must not be running any routing protocol daemons, unless the system is a router.
- V-22702 Medium check System audit logs must be group-owned by root, bin, sys, or system.
- V-23736 Low check The system must use a separate file system for /var.
- V-23738 Low check The system must use a separate file system for the system audit data path.
- V-23739 Low check The system must use a separate file system for /tmp (or equivalent).
- V-23741 Medium check TCP backlog queue sizes must be set appropriately.
- V-23952 Medium check Mail relaying must be restricted.
- V-23953 Medium check The 'ldd' command must be disabled unless it protects against the execution of untrusted files.
- V-24357 Low check The system must be configured to send audit records to a remote audit server.
- V-24384 Medium check If the system is using LDAP for authentication or account information, the /etc/ldap.conf file (or equivalent) must not contain passwords.
- V-24624 Medium check The system boot loader must protect passwords using an MD5 or stronger cryptographic hash.
- V-27275 Medium check The system must not have the unnecessary "news" account.
- V-27276 Medium check The system must not have the unnecessary "gopher" account.
- V-27279 Medium check The system must not have the unnecessary "ftp" account.
- V-27283 Medium check The graphical desktop environment must set the idle timeout to no more than 15 minutes.
- V-27284 Medium check Graphical desktop environments provided by the system must have automatic lock enabled.
- V-29236 Medium check The audit system must be configured to audit failed attempts to access files and programs.
- V-29237 Medium check The audit system must be configured to audit failed attempts to access files and programs.
- V-29238 Medium check The audit system must be configured to audit failed attempts to access files and programs.
- V-29239 Medium check The audit system must be configured to audit failed attempts to access files and programs.
- V-29240 Medium check The audit system must be configured to audit file deletions.
- V-29241 Medium check The audit system must be configured to audit all administrative, privileged, and security actions.
- V-29242 Medium check The audit system must be configured to audit all administrative, privileged, and security actions.
- V-29243 Medium check The audit system must be configured to audit all administrative, privileged, and security actions.
- V-29244 Medium check The audit system must be configured to audit all administrative, privileged, and security actions.
- V-29245 Medium check The audit system must be configured to audit all administrative, privileged, and security actions.
- V-29246 Medium check The audit system must be configured to audit all administrative, privileged, and security actions.
- V-29247 Medium check The audit system must be configured to audit all administrative, privileged, and security actions.
- V-29248 Medium check The audit system must be configured to audit all administrative, privileged, and security actions.
- V-29249 Medium check The audit system must be configured to audit all administrative, privileged, and security actions.
- V-29250 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29251 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29252 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29253 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29255 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29257 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29259 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29261 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29272 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29274 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29275 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29279 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-29281 Medium check The audit system must be configured to audit the loading and unloading of dynamic kernel modules - delete_module.
- V-29284 Medium check The audit system must be configured to audit the loading and unloading of dynamic kernel modules - /sbin/insmod.
- V-29286 Medium check The audit system must be configured to audit the loading and unloading of dynamic kernel modules -/sbin/modprobe.
- V-29288 Medium check The audit system must be configured to audit the loading and unloading of dynamic kernel modules - /sbin/rmmod
- V-29289 Medium check Files in cron script directories must have mode 0700 or less permissive.
- V-4083 Medium check Graphical desktop environments provided by the system must automatically lock after 15 minutes of inactivity and the system must require users to re-authenticate to unlock the environment. Applications requiring continuous, real-time screen display (i.e., network management products) require the following and need to be documented with the IAO. -The logon session does not have administrator rights. -The display station (i.e., keyboard, monitor, etc.) is located in a controlled access area.
- V-4084 Medium check The system must prohibit the reuse of passwords within five iterations.
- V-4089 Medium check All system start-up files must be owned by root.
- V-4090 Medium check All system start-up files must be group-owned by root, sys, bin, other, or system.
- V-4248 High check For systems capable of using GRUB, the system must be configured with GRUB as the default boot loader unless another boot loader has been authorized, justified, and documented using site-defined procedures.
- V-4249 High check The system boot loader must require authentication.
- V-4250 Medium check The system's boot loader configuration file(s) must have mode 0600 or less permissive.
- V-4268 High check The system must not have special privilege accounts, such as shutdown and halt.
- V-4275 Medium check The /etc/news/readers.conf (or equivalent) must have mode 0600 or less permissive.
- V-4276 Medium check The /etc/news/passwd.nntp file (or equivalent) must have mode 0600 or less permissive.
- V-4278 Medium check The files in /etc/news must be group-owned by root or news.
- V-4295 High check The SSH daemon must be configured to only use the SSHv2 protocol.
- V-4321 Medium check The system must not run Samba unless needed.
- V-4334 Medium check The /etc/sysctl.conf file must be owned by root.
- V-4335 Medium check The /etc/sysctl.conf file must be group-owned by root.
- V-4336 Medium check The /etc/sysctl.conf file must have mode 0600 or less permissive.
- V-4342 High check The x86 CTRL-ALT-DELETE key sequence must be disabled.
- V-4358 Medium check The cron.deny file must have mode 0600 or less permissive.
- V-4361 Medium check The cron.allow file must be owned by root, bin, or sys.
- V-4364 Medium check The "at" directory must have mode 0755 or less permissive.
- V-4365 Medium check The at directory must be owned by root, bin, sys, daemon, or cron.
- V-4367 Medium check The at.allow file must be owned by root, bin, or sys.
- V-4368 Medium check The at.deny file must be owned by root, bin, or sys.
- V-4369 Medium check The traceroute command owner must be root.
- V-4370 Medium check The traceroute command must be group-owned by sys, bin, root, or system.
- V-4371 Medium check The traceroute file must have mode 0700 or less permissive.
- V-4384 Low check The SMTP service's SMTP greeting must not provide version information.
- V-4385 Medium checkfix The system must not use .forward files.
- V-4387 High check Anonymous FTP accounts must not have a functional shell.
- V-4393 Medium check The /etc/syslog.conf file must be owned by root.
- V-4394 Medium check The /etc/syslog.conf file must be group-owned by root, bin, sys, or system.
- V-4428 Medium check All .rhosts, .shosts, .netrc, or hosts.equiv files must be accessible by only root or the owner.
- V-4430 Medium check The cron.deny file must be owned by root, bin, or sys.
- V-4687 High check The rsh daemon must not be running.
- V-4688 High check The rexec daemon must not be running.
- V-4689 High check The SMTP service must be an up-to-date version.
- V-4692 Low check The SMTP service must not have the EXPN feature active.
- V-4693 Low check The SMTP service must not have the Verify (VRFY) feature active.
- V-4696 Medium check The system must not have the UUCP service active.
- V-756 Medium check The system must require authentication upon booting into single-user and maintenance modes.
- V-763 Medium check The Department of Defense (DoD) login banner must be displayed immediately prior to, or as part of, console login prompts.
- V-766 Medium check The system must disable accounts after three consecutive unsuccessful login attempts.
- V-770 High check The system must not have accounts configured with blank or null passwords.
- V-773 Medium check The root account must be the only account having a UID of 0.
- V-774 Low check The root user's home directory must not be the root directory (/).
- V-775 Medium check The root account's home directory (other than /) must have mode 0700.
- V-776 Medium check The root account's executable search path must be the vendor default and must contain only absolute paths.
- V-777 Medium check The root account must not have world-writable directories in its executable search path.
- V-778 Medium check The system must prevent the root account from directly logging in except from the system console.
- V-781 Low check All GIDs referenced in the /etc/passwd file must be defined in the /etc/group file.
- V-787 Medium check System log files must have mode 0640 or less permissive.
- V-788 Medium check All skeleton files (typically those in /etc/skel) must have mode 0644 or less permissive.
- V-789 Medium check NIS/NIS+/yp files must be owned by root, sys, or bin.
- V-791 Medium check The NIS/NIS+/yp command files must have mode 0755 or less permissive.
- V-793 Medium check Library files must have mode 0755 or less permissive.
- V-794 Medium check All system command files must have mode 0755 or less permissive.
- V-795 Medium check All system files, programs, and directories must be owned by a system account.
- V-796 Medium check System files, programs, and directories must be group-owned by a system group.
- V-797 Medium check The /etc/shadow (or equivalent) file must be owned by root.
- V-798 Medium check The /etc/passwd file must have mode 0644 or less permissive.
- V-800 Medium check The /etc/shadow (or equivalent) file must have mode 0400.
- V-808 Medium check The system and user default umask must be 077.
- V-811 Medium check Auditing must be implemented.
- V-812 Medium check System audit logs must be owned by root.
- V-813 Medium check System audit logs must have mode 0640 or less permissive.
- V-814 Medium check The audit system must be configured to audit failed attempts to access files and programs.
- V-815 Medium check The audit system must be configured to audit files and programs deleted by the user.
- V-818 Medium check The audit system must be configured to audit login, logout, and session initiation.
- V-819 Medium check The audit system must be configured to audit all discretionary access control permission modifications.
- V-821 Medium check The inetd.conf file, xinetd.conf file, and the xinetd.d directory must be owned by root or bin.
- V-822 Medium check The xinetd configuration files must have mode 0640 or less permissive.
- V-823 Medium check The services file must be owned by root or bin.
- V-824 Medium check The services file must have mode 0644 or less permissive.
- V-825 Low check Global initialization files must contain the "mesg -n" or "mesg n" commands.
- V-828 Medium check The hosts.lpd (or equivalent) file must be owned by root, bin, sys, or lp.
- V-829 Medium check The hosts.lpd (or equivalent) must have mode 0644 or less permissive.
- V-831 Medium check The alias file must be owned by root.
- V-832 Medium check The alias file must have mode 0644 or less permissive.
- V-834 Medium check Files executed through a mail aliases file must have mode 0755 or less permissive.
- V-835 Low check Sendmail logging must not be set to less than nine in the sendmail.cf file.
- V-836 Medium fix The system syslog service must log informational and more severe SMTP service messages.
- V-837 Medium check The SMTP service log file must be owned by root.
- V-838 Medium check The SMTP service log file must have mode 0644 or less permissive.
- V-840 Medium check The ftpusers file must exist.
- V-842 Medium check The ftpusers file must be owned by root.
- V-843 Medium check The ftpusers file must have mode 0640 or less permissive.
- V-847 High check The TFTP daemon must operate in "secure mode" which provides access only to a single directory on the host file system.
- V-848 High check The TFTP daemon must have mode 0755 or less permissive.
- V-867 Medium check The Network Information System (NIS) protocol must not be used.
- V-899 Low check All interactive users must be assigned a home directory in the /etc/passwd file.
- V-900 Low check All interactive user home directories defined in the /etc/passwd file must exist.
- V-901 Medium check All user home directories must have mode 0750 or less permissive.
- V-906 Medium check All run control scripts must have mode 0755 or less permissive.
- V-913 Medium check There must be no .netrc files on the system.
- V-916 Medium check The /etc/shells (or equivalent) file must exist.
- V-921 Medium check All shell files must be owned by root or bin.
- V-922 High check All shell files must have mode 0755 or less permissive.
- V-924 Medium check Device files and directories must only be writable by users with a system account or as configured by the vendor.
- V-928 Medium check The Network File System (NFS) export configuration file must be owned by root.
- V-929 Low check The Network File System (NFS) export configuration file must have mode 0644 or less permissive.
- V-931 Medium check All Network File System (NFS) exported system files and system directories must be owned by root.
- V-932 Medium check The Network File System (NFS) anonymous UID and GID must be configured to values without permissions.
- V-933 Medium check The Network File System (NFS) server must be configured to restrict file system access to local hosts.
- V-935 Medium check The Network File System (NFS) server must not allow remote root access.
- V-936 Medium check The "nosuid" option must be enabled on all Network File System (NFS) client mounts.
- V-940 Medium check The system must use an access control program.
- V-941 Medium check The system's access control program must log each system access attempt.
- V-974 Medium check Access to the cron utility must be controlled using the cron.allow and/or cron.deny file(s).
- V-975 Medium check The cron.allow file must have mode 0600 or less permissive.
- V-978 Medium check Crontab files must have mode 0600 or less permissive, and files in cron script directories must have mode 0700 or less permissive.
- V-979 Medium check Cron and crontab directories must have mode 0755 or less permissive.
- V-980 Medium check Cron and crontab directories must be owned by root or bin.
- V-981 Medium check Cron and crontab directories must be group-owned by root, sys, bin or cron.
- V-982 Medium check Cron logging must be implemented.
- V-983 Medium check The cronlog file must have mode 0600 or less permissive.
- V-984 Medium check Access to the "at" utility must be controlled via the at.allow and/or at.deny file(s).
- V-985 Medium check The at.deny file must not be empty if it exists.
- V-986 Medium check Default system accounts (with the exception of root) must not be listed in the at.allow file or must be included in the at.deny file if the at.allow file does not exist.
- V-987 Medium check The at.allow file must have mode 0600 or less permissive.
- V-994 Medium check The snmpd.conf file must have mode 0600 or less permissive.
- V-995 Medium check Management Information Base (MIB) files must have mode 0640 or less permissive.
- RMF Control
- AC-3
- Severity
- M
- CCI
- CCI-000213
- Version
- GEN000020
- Vuln IDs
-
- V-756
- Rule IDs
-
- SV-37350r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31285r1_fix
Edit /etc/inittab and set sulogin to run in single-user mode. Example line in /etc/inittab: ~:S:wait:/sbin/sulogin
- RMF Control
- IA-2
- Severity
- M
- CCI
- CCI-000770
- Version
- GEN000280
- Vuln IDs
-
- V-760
- Rule IDs
-
- SV-37419r2_rule
Checks: C-36102r2_chk
Use the last command to check for multiple accesses to an account from different workstations/IP addresses. # last -w If users log directly onto accounts, rather than using the switch user (su) command from their own named account to access them, this is a finding (such as logging directly on to oracle). Verify with the SA or the IAO on documentation for users/administrators to log into their own accounts first and then switch user (su) to the account to be shared has been maintained including requirements and procedures. If no such documentation exists, this is a finding.
Fix: F-31348r2_fix
Use the switch user (su) command from a named account login to access shared accounts. Document requirements and procedures for users/administrators to log into their own accounts first and then switch user (su) to the account to be shared.
- RMF Control
- IA-2
- Severity
- M
- CCI
- CCI-000764
- Version
- GEN000300
- Vuln IDs
-
- V-761
- Rule IDs
-
- SV-27063r1_rule
Checks: C-36103r1_chk
Check the system for duplicate account names. Example: # pwck -r If any duplicate account names are found, this is a finding.
Fix: F-31349r1_fix
Change user account names, or delete accounts, so each account has a unique name.
- RMF Control
- IA-2
- Severity
- M
- CCI
- CCI-000764
- Version
- GEN000320
- Vuln IDs
-
- V-762
- Rule IDs
-
- SV-27068r1_rule
Checks: C-36104r2_chk
Perform the following to ensure there are no duplicate UIDs: # cut -d: -f3 /etc/passwd | uniq -d If any duplicate UIDs are found, this is a finding.
Fix: F-31350r1_fix
Edit user accounts to provide unique UIDs for each account.
- RMF Control
- AC-8
- Severity
- M
- CCI
- CCI-000048
- Version
- GEN000400
- Vuln IDs
-
- V-763
- Rule IDs
-
- SV-37169r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31128r1_fix
Edit /etc/issue and add one of the DoD login banners (based on the character limitations imposed by the system). DoD Login Banners: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests- -not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. OR I've read & consent to terms in IS user agreem't.
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN000440
- Vuln IDs
-
- V-765
- Rule IDs
-
- SV-37178r1_rule
Checks: C-35882r1_chk
Determine if all logon attempts are being logged. Procedure: Verify successful logins are being logged: # last -R | more If the command does not return successful logins, this is a finding. Verify if unsuccessful logons are being logged: # lastb -R | more If the command does not return unsuccessful logins, this is a finding.
Fix: F-31137r1_fix
Make sure the collection files exist. Procedure: If there are no successful logins being returned from the "last" command, create /var/log/wtmp: # touch /var/log/wtmp If there are no unsuccessful logins being returned from the "lastb" command, create /var/log/btmp: # touch /var/log/btmp
- RMF Control
- AC-7
- Severity
- M
- CCI
- CCI-000044
- Version
- GEN000460
- Vuln IDs
-
- V-766
- Rule IDs
-
- SV-37203r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31153r1_fix
By default link /etc/pam.d/system-auth points to /etc/pam.d/system-auth-ac which is the file maintained by the authconfig utility. In order to add pam options other than those available via the utility create /etc/pam.d/system-auth-local with the options and including system-auth-ac. In order to set the account lockout to three failed attempts the content should be similar to: auth required pam_access.so auth required pam_tally2.so deny=3 auth include system-auth-ac account required pam_tally2.so account include system-auth-ac password include system-auth-ac session include system-auth-ac Once system-auth-local is written reset the /etc/pam.d/system-auth to point to system-auth-local. This is necessary because authconfig writes directly to system-auth-ac so any changes made by hand will be lost if authconfig is run.
- RMF Control
- AC-7
- Severity
- M
- CCI
- CCI-000043
- Version
- GEN000480
- Vuln IDs
-
- V-768
- Rule IDs
-
- SV-37213r1_rule
Checks: C-35903r2_chk
Check the value of the FAIL_DELAY variable and the ability to use it. Procedure: # grep FAIL_DELAY /etc/login.defs If the value does not exist, or is less than 4, this is a finding. Check for the use of pam_faildelay. # grep pam_faildelay /etc/pam.d/system-auth* If pam_faildelay.so module is not present, this is a finding. If pam_faildelay is present only in /etc/pam.d/system-auth-ac: ensure that /etc/pam.d/system-auth includes /etc/pam.d/system-auth-ac. #grep system-auth-ac /etc/pam.d/system-auth This should return: auth include system-auth-ac account include system-auth-ac password include system-auth-ac session include system-auth-ac /etc/pam.d/system-auth-ac should only be included by /etc/pam.d/system-auth. All other pam files should include /etc/pam.d/system-auth. If pam_faildelay is not defined in /etc/pam.d/system-auth either directly or through inclusion of system-auth-ac, this is a finding.
Fix: F-31161r1_fix
Add the pam_faildelay module and set the FAIL_DELAY variable. Procedure: Edit /etc/login.defs and set the value of the FAIL_DELAY variable to 4 or more. The default link /etc/pam.d/system-auth points to /etc/pam.d/system-auth-ac which is the file maintained by the authconfig utility. In order to add pam options other than those available via the utility create or modify /etc/pam.d/system-auth-local with the options and including system-auth-ac. For example: auth required pam_access.so auth optional pam_faildelay.so delay=4000000 auth include system-auth-ac account include system-auth-ac password include system-auth-ac session include system-auth-ac Once system-auth-local is written ensure the /etc/pam.d/system-auth points to system-auth-local. This is necessary because authconfig writes directly to system-auth-ac so any manual changes made will be lost if authconfig is run.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000520
- Vuln IDs
-
- V-769
- Rule IDs
-
- SV-37232r1_rule
Checks: C-35914r1_chk
If there is an application running on the system continuously in use (such as a network monitoring application), ask the SA what the name of the application is. Verify documentation exists for the requirement and justification of the application. If no documentation exists, this is a finding. Execute "ps -ef | more" to determine which user owns the process(es) associated with the application. If the owner is root, this is a finding.
Fix: F-31178r1_fix
Configure the system so the owner of a session requires a continuous screen display, such as a network management display, is not root. Ensure the display is also located in a secure, controlled access area. Document and justify this requirement and ensure the terminal and keyboard for the display (or workstation) are secure from all but authorized personnel by maintaining them in a secure area, in a locked cabinet where a swipe card, or other positive forms of identification, must be used to gain entry.
- RMF Control
- CM-6
- Severity
- H
- CCI
- CCI-000366
- Version
- GEN000560
- Vuln IDs
-
- V-770
- Rule IDs
-
- SV-37259r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31205r1_fix
Edit /etc/pam.d/system-auth and remove the "nullok" setting.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000880
- Vuln IDs
-
- V-773
- Rule IDs
-
- SV-37347r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31283r1_fix
Remove or change the UID of accounts other than root that have UID 0.
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN000900
- Vuln IDs
-
- V-774
- Rule IDs
-
- SV-37349r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31284r1_fix
The root home directory should be something other than / (such as /roothome). Procedure: # mkdir /rootdir # chown root /rootdir # chgrp root /rootdir # chmod 700 /rootdir # cp -r /.??* /rootdir/. Then, edit the passwd file and change the root home directory to /rootdir. The cp -r /.??* command copies all files and subdirectories of file names beginning with "." into the new root directory, which preserves the previous root environment. Ensure you are in the "/" directory when executing the "cp" command.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000920
- Vuln IDs
-
- V-775
- Rule IDs
-
- SV-37355r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31288r1_fix
The root home directory will have permissions of 0700. Do not change the protections of the / directory. Use the following command to change protections for the root home directory: # chmod 0700 /rootdir.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000940
- Vuln IDs
-
- V-776
- Rule IDs
-
- SV-37360r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31293r1_fix
Edit the root user's local initialization files ~/.profile,~/.bashrc (assuming root shell is bash). Change any found PATH variable settings to the vendor's default path for the root user. Remove any empty path entries or references to relative paths.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000960
- Vuln IDs
-
- V-777
- Rule IDs
-
- SV-37372r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31304r1_fix
For each world-writable path in root's executable search path, do one of the following: 1. Remove the world-writable permission on the directory. Procedure: # chmod o-w <path> 2. Remove the world-writable directory from the executable search path. Procedure: Identify and edit the initialization file referencing the world-writable directory and remove it from the PATH variable.
- RMF Control
- IA-2
- Severity
- M
- CCI
- CCI-000770
- Version
- GEN000980
- Vuln IDs
-
- V-778
- Rule IDs
-
- SV-37374r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31305r1_fix
Create if needed and set the contents of /etc/securetty to a "console" or "tty" device. # echo console > /etc/securetty or # echo tty1 > /etc/securetty
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000360
- Vuln IDs
-
- V-780
- Rule IDs
-
- SV-37157r1_rule
Checks: C-35866r1_chk
Confirm all accounts with a GID of 499 and below are used by a system account. Procedure: List all the users with a GID of 0-499. # cut -d: -f 1,4 /etc/passwd|egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$" If a GID reserved for system accounts (0 - 499) is used by a non-system account, this is a finding.
Fix: F-31121r1_fix
Change the primary group GID numbers for non-system accounts with reserved primary group GIDs (those less or equal to 499).
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN000380
- Vuln IDs
-
- V-781
- Rule IDs
-
- SV-27072r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-935r3_fix
Add a group to the system for each GID referenced without a corresponding group.
- RMF Control
- SI-4
- Severity
- M
- CCI
- CCI-001259
- Version
- GEN006480
- Vuln IDs
-
- V-782
- Rule IDs
-
- SV-37746r2_rule
Checks: C-36942r2_chk
Ask the SA or IAO if a host-based intrusion detection application is loaded on the system. The preferred intrusion detection system is McAfee HBSS available through Cybercom. If another host-based intrusion detection application, such as SELinux, is used on the system, this is not a finding. Procedure: Examine the system to see if the Host Intrusion Prevention System (HIPS) is installed #rpm -qa | grep MFEhiplsm If the MFEhiplsm package is installed, HBSS is being used on the system. If another host-based intrusion detection system is loaded on the system # find / -name <daemon name> Where <daemon name> is the name of the primary application daemon to determine if the application is loaded on the system. Determine if the application is active on the system. Procedure: # ps -ef | grep <daemon name> If no host-based intrusion detection system is installed on the system, this is a finding.
Fix: F-32207r1_fix
Install a host-based intrusion detection tool.
- RMF Control
- SI-2
- Severity
- M
- CCI
- CCI-001227
- Version
- GEN000120
- Vuln IDs
-
- V-783
- Rule IDs
-
- SV-27059r2_rule
Checks: C-27973r3_chk
Obtain the list of available package security updates from Red Hat. Check the available package security updates have been installed on the system. Use the "rpm" command to list the packages installed on the system. Example: # rpm -qa -last If updated packages are available and applicable to the system and have not been installed, this is a finding. One source for the list of Red Hat updates is available at https://access.redhat.com/security/updates/active/
Fix: F-31302r1_fix
Install the patches or updated packages available from the vendor.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001140
- Vuln IDs
-
- V-784
- Rule IDs
-
- SV-37159r1_rule
Checks: C-35867r1_chk
Check system directories for uneven file permissions. Procedure: # ls -lL /etc /bin /usr/bin /usr/lbin /usr/usb /sbin /usr/sbin Uneven file permissions exist if the file owner has less permissions than the group or other user classes. If any of the files in the above listed directories contain uneven file permissions, this is a finding.
Fix: F-31122r1_fix
Change the mode of files with uneven permissions so owners do not have less permission than group or world users.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001160
- Vuln IDs
-
- V-785
- Rule IDs
-
- SV-37161r1_rule
Checks: C-35868r1_chk
Check the system for files with no assigned owner. Procedure: # find / -nouser If any files have no assigned owner, this is a finding. Caution should be used when centralized authorization is used because valid files may appear as unowned due to communication issues.
Fix: F-31123r1_fix
All directories and files (executable and data) will have an identifiable owner and group name. Either trace files to an authorized user, change the file's owner to root, or delete them. Determine the legitimate owner of the files and use the chown command to set the owner and group to the correct value. If the legitimate owner cannot be determined, change the owner to root (but make sure none of the changed files remain executable because they could be Trojan horses or other malicious code). Examine the files to determine their origin and the reason for their lack of an owner/group.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001180
- Vuln IDs
-
- V-786
- Rule IDs
-
- SV-37194r1_rule
Checks: C-35891r1_chk
Check the mode of network services daemons. # find /usr/sbin -type f -perm +022 -exec stat -c %a:%n {} \; This will return the octal permissions and name of all files that are group or world writable. If any network services daemon listed is world or group writable (either or both of the 2 lowest order digits contain a 2, 3 or 6), this is a finding. Note: Network daemons not residing in these directories (such as httpd or sshd) must also be checked for the correct permissions.
Fix: F-31146r1_fix
Change the mode of the network services daemon. # chmod go-w <path>
- RMF Control
- SI-11
- Severity
- M
- CCI
- CCI-001314
- Version
- GEN001260
- Vuln IDs
-
- V-787
- Rule IDs
-
- SV-37228r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31175r1_fix
Change the mode of the system log file(s) to 0640 or less permissive. Procedure: # chmod 0640 /path/to/system-log-file Note: Do not confuse system log files with audit logs.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001800
- Vuln IDs
-
- V-788
- Rule IDs
-
- SV-37292r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31240r1_fix
Change the mode of skeleton files with incorrect mode: # chmod 0644 <skeleton file>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001320
- Vuln IDs
-
- V-789
- Rule IDs
-
- SV-37267r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31213r1_fix
Change the ownership of NIS/NIS+/yp files to root, sys or bin. Procedure (example): # chown root <filename>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001340
- Vuln IDs
-
- V-790
- Rule IDs
-
- SV-41577r2_rule
Checks: C-40079r2_chk
Perform the following to check NIS file group ownership: # ls -la /var/yp/* If the file group ownership is not root, sys, or bin, this is a finding.
Fix: F-35235r4_fix
Perform the following to change NIS file ownership. # chgrp root /var/yp/*
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001360
- Vuln IDs
-
- V-791
- Rule IDs
-
- SV-37272r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31220r1_fix
Change the mode of NIS/NIS+/yp command files to 0755 or less permissive. Procedure (example): # chmod 0755 <filename>
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN001280
- Vuln IDs
-
- V-792
- Rule IDs
-
- SV-37234r1_rule
Checks: C-35923r1_chk
Check the mode of the manual page files. Procedure: # ls -lL /usr/share/man /usr/share/info /usr/share/infopage If any of the manual page files have a mode more permissive than 0644, this is a finding.
Fix: F-31181r1_fix
Change the mode of manual page files to 0644 or less permissive. Procedure (example): # chmod 0644 /path/to/manpage
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-001499
- Version
- GEN001300
- Vuln IDs
-
- V-793
- Rule IDs
-
- SV-37241r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31188r1_fix
Change the mode of library files to 0755 or less permissive. Procedure (example): # chmod go-w </path/to/library-file> Note: Library files should have an extension of ".a" or a ".so" extension, possibly followed by a version number.
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-001499
- Version
- GEN001200
- Vuln IDs
-
- V-794
- Rule IDs
-
- SV-37205r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31155r1_fix
Change the mode for system command files to 0755 or less permissive taking into account necessary GIUD and SUID bits. Procedure: # chmod go-w <filename>
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-001499
- Version
- GEN001220
- Vuln IDs
-
- V-795
- Rule IDs
-
- SV-37216r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31164r1_fix
Change the owner of system files, programs, and directories to a system account. Procedure: # chown root /some/system/file (A different system user may be used in place of root.)
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-001499
- Version
- GEN001240
- Vuln IDs
-
- V-796
- Rule IDs
-
- SV-37220r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31167r1_fix
Change the group-owner of system files to a system group. Procedure: # chgrp root /path/to/system/file (System groups other than root may be used.)
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001400
- Vuln IDs
-
- V-797
- Rule IDs
-
- SV-37361r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31294r1_fix
Change the ownership of the /etc/shadow (or equivalent) file. # chown root /etc/shadow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001380
- Vuln IDs
-
- V-798
- Rule IDs
-
- SV-37344r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31280r1_fix
Change the mode of the passwd file to 0644. Procedure: # chmod 0644 /etc/passwd
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001420
- Vuln IDs
-
- V-800
- Rule IDs
-
- SV-37368r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31300r1_fix
Change the mode of the /etc/shadow (or equivalent) file. # chmod 0400 /etc/shadow
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000368
- Version
- GEN002380
- Vuln IDs
-
- V-801
- Rule IDs
-
- SV-37579r2_rule
Checks: C-36445r4_chk
If STIGID GEN000220 is satisfied, this is not a finding. List all setuid files on the system. Procedure: # find / -perm -4000 -exec ls -l {} \; | more Note: Executing these commands may result in large listings of files; the output may be redirected to a file for easier analysis. Ask the SA or IAO if files with the setuid bit set have been documented. Documentation must include the owner, group-owner, mode, ACL, and location of the files. If any undocumented file has its setuid bit set, this is a finding.
Fix: F-31615r1_fix
Document the files with the suid bit set or unset the suid bit on the executable.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000368
- Version
- GEN002440
- Vuln IDs
-
- V-802
- Rule IDs
-
- SV-37628r2_rule
Checks: C-36826r3_chk
If STIGID GEN000220 is satisfied, this is not a finding. List all setgid files on the system. Procedure: # find / -perm -2000 -exec ls -l {} \; | more Note: Executing these commands may result in large listings of files; the output may be redirected to a file for easier analysis. Ask the SA or IAO if files with the setgid bit set have been documented. Documentation must include owner, group-owner, mode, ACL, and location. If any undocumented file has its setgid bit set, this is a finding.
Fix: F-31664r1_fix
Document the files with the sgid bit set or unset the sgid bit on the executable.
- RMF Control
- CM-3
- Severity
- M
- CCI
- CCI-000318
- Version
- GEN002400
- Vuln IDs
-
- V-803
- Rule IDs
-
- SV-37592r2_rule
Checks: C-36666r3_chk
Ask the SA for the weekly automated or manual process used to generate a list of setuid files on the system and compare it with the prior list. If no such process is in place, this is a finding. Review the process. If the process does not identify and report changes in setuid files, this is a finding. NOTE: For MAC I systems, increase the frequency to daily.
Fix: F-31627r2_fix
Establish a weekly automated or manual process to generate a list of suid files on the system and compare it with the prior list. To create a list of suid files: # find / -perm -4000 > suid-file-list NOTE: For MAC I systems, increase the frequency to daily.
- RMF Control
- CM-3
- Severity
- M
- CCI
- CCI-000318
- Version
- GEN002460
- Vuln IDs
-
- V-804
- Rule IDs
-
- SV-37635r2_rule
Checks: C-36833r4_chk
Ask the SA if a weekly automated or manual process is used to generate a list of setgid files on the system and compare it with the prior list. If no such process is in place, this is a finding. NOTE: For MAC I systems, increase the frequency to daily.
Fix: F-31671r3_fix
Establish a weekly automated or manual process to generate a list of setgid files on the system and compare it with the prior list. To create a list of setgid files: # find / -perm -2000 > setgid-file-list NOTE: For MAC I systems, increase the frequency to daily.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002420
- Vuln IDs
-
- V-805
- Rule IDs
-
- SV-37607r1_rule
Checks: C-36773r2_chk
Check /etc/mtab and verify the "nosuid" mount option is used on file systems mounted from removable media, network shares, or any other file system not containing approved setuid or setgid files. If any of these files systems do not mount with the "nosuid" option, it is a finding.
Fix: F-31642r1_fix
Edit /etc/fstab and add the "nosuid" mount option to all file systems mounted from removable media or network shares, and any file system not containing approved setuid or setgid files.
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN002500
- Vuln IDs
-
- V-806
- Rule IDs
-
- SV-37647r1_rule
Checks: C-36843r1_chk
Check all world-writable directories have the sticky bit set. Procedure: # find / -type d -perm -002 ! -perm -1000 > wwlist If the sticky bit is not set on a world-writable directory, this is a finding.
Fix: F-31680r1_fix
Set the sticky bit on all public directories. Procedure: # chmod 1777 /tmp (Replace /tmp with the public directory missing the sticky bit, if necessary.)
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002520
- Vuln IDs
-
- V-807
- Rule IDs
-
- SV-37888r1_rule
Checks: C-37114r1_chk
Check the ownership of all public directories. Procedure: # find / -type d -perm -1002 -exec ls -ld {} \; If any public directory is not owned by root or an application user, this is a finding.
Fix: F-32382r1_fix
Change the owner of public directories to root or an application account. Procedure: # chown root /tmp (Replace root with an application user and/or /tmp with another public directory as necessary.)
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN002560
- Vuln IDs
-
- V-808
- Rule IDs
-
- SV-37898r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32392r1_fix
Edit local and global initialization files that contain "umask" and change them to use 077 instead of the current value.
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000178
- Version
- GEN002640
- Vuln IDs
-
- V-810
- Rule IDs
-
- SV-37903r1_rule
Checks: C-37129r2_chk
Determine if default system accounts (such as those for sys, bin, uucp, nuucp, daemon, smtp) have been disabled. # cat /etc/shadow If an account's password field (which is the second field in the /etc/shadow file) is "*", "*LK*", or is prefixed with a '!', the account is locked or disabled. If there are any unlocked default system accounts this is a finding.
Fix: F-32397r1_fix
Lock the default system account(s). # passwd -l <user>
- RMF Control
- AU-12
- Severity
- M
- CCI
- CCI-000169
- Version
- GEN002660
- Vuln IDs
-
- V-811
- Rule IDs
-
- SV-27270r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24516r1_fix
Start the auditd service and set it to start on boot. # service auditd start ; chkconfig auditd on
- RMF Control
- AU-9
- Severity
- M
- CCI
- CCI-000162
- Version
- GEN002680
- Vuln IDs
-
- V-812
- Rule IDs
-
- SV-37912r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-966r2_fix
Change the ownership of the audit log file(s). Procedure: # chown root <audit log file>
- RMF Control
- AU-9
- Severity
- M
- CCI
- CCI-000163
- Version
- GEN002700
- Vuln IDs
-
- V-813
- Rule IDs
-
- SV-37916r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-967r2_fix
Change the mode of the audit log directories/files. # chmod 0750 <audit directory> # chmod 0640 <audit file>
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002720
- Vuln IDs
-
- V-814
- Rule IDs
-
- SV-38645r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-33035r2_fix
Edit the audit.rules file and add the following line(s) to enable auditing of failed attempts to access files and programs: either: -a exit,always -F arch=<ARCH> -S creat -F success=0 or both: -a exit,always -F arch=<ARCH> -S creat -F exit=-EPERM -a exit,always -F arch=<ARCH> -S creat -F exit=-EACCES Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002740
- Vuln IDs
-
- V-815
- Rule IDs
-
- SV-42185r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24531r1_fix
Edit the audit.rules file and add the following line to enable auditing of deletions: -a exit,always -S unlink Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002800
- Vuln IDs
-
- V-818
- Rule IDs
-
- SV-37944r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32435r1_fix
Ensure logins Procedure: Modify /etc/audit/audit.rules to contain: -w /var/log/faillog -p wa -w /var/log/lastlog -p wa
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820
- Vuln IDs
-
- V-819
- Rule IDs
-
- SV-48488r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24555r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S chmod Restart the auditd service. # service auditd restart
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003720
- Vuln IDs
-
- V-821
- Rule IDs
-
- SV-37406r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31336r1_fix
Change the owner of the xinetd configuration files. # chown root /etc/xinetd.conf /etc/xinetd.d/*
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003740
- Vuln IDs
-
- V-822
- Rule IDs
-
- SV-37408r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31338r3_fix
Change the mode of the xinetd configuration files. # chmod 0640 /etc/xinetd.conf /etc/xinetd.d/*
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003760
- Vuln IDs
-
- V-823
- Rule IDs
-
- SV-37424r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31351r1_fix
Change the ownership of the services file to root or bin. Procedure: # chown root /etc/services
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003780
- Vuln IDs
-
- V-824
- Rule IDs
-
- SV-37426r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31353r1_fix
Change the mode of the services file to 0644 or less permissive. Procedure: # chmod 0644 /etc/services
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN001780
- Vuln IDs
-
- V-825
- Rule IDs
-
- SV-37289r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31237r1_fix
Edit /etc/profile or another global initialization script, and add the "mesg -n" command.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN003900
- Vuln IDs
-
- V-827
- Rule IDs
-
- SV-37447r1_rule
Checks: C-36119r2_chk
RHEL uses "cups" print service. Verify remote host access is limited. Procedure: # grep -i Listen /etc/cups/cupsd.conf The /etc/cups/cupsd.conf file must not contain a Listen *:<port> or equivalent line. If the network address of the "Listen" line is unrestricted, this is a finding. # grep -i "Allow From" /etc/cups/cupsd.conf The "Allow From" line within the "<Location />" element should limit access to the printers to @LOCAL and specific hosts. If the "Allow From" line contains "All" this is a finding
Fix: F-31365r1_fix
Configure cups to use only the localhost or specified remote hosts. Procedure: Modify the /etc/cups/cupsd.conf file to "Listen" only to the local machine or a known set of hosts (i.e., Listen localhost:631). Modify the /etc/cups/cupsd.conf file "<Location />" element to "Deny From All" and "Allow from 127.0.0.1" or allowed host addresses. Restart cups: # service cups restart
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003920
- Vuln IDs
-
- V-828
- Rule IDs
-
- SV-37448r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31366r3_fix
Change the owner of the /etc/cups/printers.conf to root. Procedure: # chown root /etc/cups/printers.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003940
- Vuln IDs
-
- V-829
- Rule IDs
-
- SV-37461r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31371r1_fix
Change the mode of the /etc/cups/printers.conf file to 0664 or less permissive. Procedure: # chmod 0664 /etc/cups/printers.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004360
- Vuln IDs
-
- V-831
- Rule IDs
-
- SV-37472r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31384r1_fix
Change the owner of the /etc/aliases file to root. Procedure: for sendmail: # chown root /etc/aliases # chown root /etc/aliases.db for postfix # chown root /etc/postfix/aliases # chown root /etc/postfix/aliases.db
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004380
- Vuln IDs
-
- V-832
- Rule IDs
-
- SV-37475r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31387r1_fix
Change the mode of the alias files as needed to function. No higher than 0644. Procedure: for sendmail: # chmod 0644 /etc/aliases /etc/aliases.db for postfix (assuming the default postfix directory): # chmod 0644 /etc/postfix/aliases /etc/postfix/aliases.db
- RMF Control
- AC-6
- Severity
- H
- CCI
- CCI-000225
- Version
- GEN004400
- Vuln IDs
-
- V-833
- Rule IDs
-
- SV-37491r1_rule
Checks: C-36149r1_chk
Verify the ownership of files referenced within the sendmail aliases file. Procedure: # more /etc/aliases Examine the aliases file for any utilized directories or paths. # ls -lL <directory or file path> Check the owner for any paths referenced. Check if the file or parent directory is owned by root. If not, this is a finding.
Fix: F-31398r1_fix
Edit the /etc/aliases file (alternatively, /usr/lib/sendmail.cf). Locate the entries executing a program. They will appear similar to the following line: Aliasname: : /usr/local/bin/ls (or some other program name) Ensure root owns the programs and the directory(ies) they reside in by using the chown command to change owner to root. Procedure: # chown root <file or directory name>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004420
- Vuln IDs
-
- V-834
- Rule IDs
-
- SV-37494r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31403r2_fix
Use the chmod command to change the access permissions for files executed from the alias file. For example: # chmod 0755 filename
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN004440
- Vuln IDs
-
- V-835
- Rule IDs
-
- SV-37497r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31405r2_fix
Edit the sendmail.cf file, locate the "O L" or "LogLevel" entry and change it to 9.
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN004460
- Vuln IDs
-
- V-836
- Rule IDs
-
- SV-37500r2_rule
Checks: C-36156r1_chk
Check the syslog configuration file for mail.crit logging configuration. Procedure: # grep "mail\." /etc/syslog.conf If syslog is not configured to log critical sendmail messages ("mail.crit" or "mail.*"), this is a finding.
Fix: F-31407r3_fix
Edit the syslog.conf file and add a configuration line specifying an appropriate destination for "mail.crit" or "mail.*" syslog messages.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004480
- Vuln IDs
-
- V-837
- Rule IDs
-
- SV-37501r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31408r1_fix
Change the ownership of the sendmail log file. Procedure: The fix procedure is the same for both sendmail and Postfix. # chown root <sendmail log file>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004500
- Vuln IDs
-
- V-838
- Rule IDs
-
- SV-37502r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31410r1_fix
Change the mode of the SMTP service log file. Procedure: The fix procedure is the same for both sendmail and Postfix. # chmod 0644 <sendmail log file>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004880
- Vuln IDs
-
- V-840
- Rule IDs
-
- SV-51983r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-45028r1_fix
Create an ftpusers file appropriate for the running FTP service. For gssftp: Create an /etc/ftpusers file containing a list of accounts not authorized for FTP. For vsftp: Create an /etc/vsftpd.ftpusers or /etc/vsftpd/ftpusers (as appropriate) file containing a list of accounts not authorized for FTP.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004900
- Vuln IDs
-
- V-841
- Rule IDs
-
- SV-52091r1_rule
Checks: C-36191r1_chk
Check the contents of the ftpusers file. For gssftp: # more /etc/ftpusers For vsftp: # more /etc/vsftpd.ftpusers /etc/vfsftpd/ftpusers If the system has accounts not allowed to use FTP and not listed in the ftpusers file, this is a finding.
Fix: F-45121r1_fix
For gssftp: Add accounts not allowed to use FTP to the /etc/ftpusers file. For vsftp: Add accounts not allowed to use FTP to the /etc/vsftpd.ftpusers or /etc/vsftpd/ftpusers file (as appropriate).
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004920
- Vuln IDs
-
- V-842
- Rule IDs
-
- SV-37537r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31452r1_fix
Change the owner of the ftpusers file to root. For gssftp: # chown root /etc/ftpusers For vsftp: # chown root /etc/vsftpd.ftpusers /etc/vsftpd/ftpusers
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004940
- Vuln IDs
-
- V-843
- Rule IDs
-
- SV-37542r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31457r1_fix
Change the mode of the ftpusers file to 0640. Procedure: For gssftp: # chmod 0640 /etc/ftpusers For vsftp: # chmod 0640 /etc/vsftpd.ftpusers /etc/vsftpd/ftpusers
- RMF Control
- AU-3
- Severity
- L
- CCI
- CCI-000130
- Version
- GEN004980
- Vuln IDs
-
- V-845
- Rule IDs
-
- SV-37547r1_rule
Checks: C-36202r2_chk
Find if logging is applied to the ftp daemon. The procedure depends on the implementation of ftpd used by the system. Procedures: For vsftpd: If vsftpd is started by xinetd: #grep vsftpd /etc/xinetd.d/* This will indicate the xinetd.d startup file #grep server_args <vsftpd xinetd.d startup file> This will indicate the vsftpd config file used when starting through xinetd. If the line is missing then "/etc/vsftpd/vsftpd.conf", the default config file, is used. #grep xferlog_enable <vsftpd config file> If "xferlog_enable" is missing or is not set to "yes", this is a finding. If vsftp is not started by xinetd: #grep xferlog_enable /etc/vsftpd/vsftpd.conf If "xferlog_enable" is missing or is not set to "yes", this is a finding. For gssftp: Find if the -l option will be applied when xinetd starts gssftp # grep server_args /etc/xinetd.d/gssftp If the line is missing or does not contain at least one -l, this is a finding.
Fix: F-31461r1_fix
Enable logging by changing ftpd startup or config files. Procedure: The procedure depends on the implementation of ftpd used by the system. For vsftpd: Ensure the server settings in "/etc/vsftpd.conf" (or other configuration file specified by the vaftpd xinetd.d startup file) contains: xferlog_enable = yes For gssftp: If the "disable" server setting is missing or set to "no" in "/etc/xinetd.d/gssftp" then ensure the server settings in "/etc/xinetd.d/gssftp" contains: server_args = -l The -l option may be added up to three times. Each -l will provide increasing verbosity on the log. Refer to the main page for ftpd for more information. For both if started using xinetd: If the "disable" server setting is missing or set to "no" in the /etc/xinetd.d startup file then ensure the server settings contains: log_on_success += DURATION USERID This will log the startup and shutdown of the daemon. log_on_failure += HOST USERID
- RMF Control
- AC-22
- Severity
- M
- CCI
- CCI-001475
- Version
- GEN004820
- Vuln IDs
-
- V-846
- Rule IDs
-
- SV-37526r1_rule
Checks: C-36185r1_chk
Attempt to log into this host with a user name of anonymous and a password of guest (also try the password of guest@mail.com). If the logon is successful and the use of anonymous ftp has not been documented and approved by the IAO, this is a finding. Procedure: # ftp localhost Name: anonymous 530 Guest login not allowed on this machine.
Fix: F-31440r1_fix
Configure the FTP service to not permit anonymous logins.
- RMF Control
- CM-6
- Severity
- H
- CCI
- CCI-000366
- Version
- GEN005080
- Vuln IDs
-
- V-847
- Rule IDs
-
- SV-37560r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31470r1_fix
Edit /etc/xinetd.d/tftp file and specify the "-s" parameter in server_args.
- RMF Control
- AC-6
- Severity
- H
- CCI
- CCI-000225
- Version
- GEN005100
- Vuln IDs
-
- V-848
- Rule IDs
-
- SV-37564r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31473r1_fix
Change the mode of the TFTP daemon. Procedure: # chmod 0755 <in.tftpd binary>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005120
- Vuln IDs
-
- V-849
- Rule IDs
-
- SV-37674r1_rule
Checks: C-36862r1_chk
Check the /etc/passwd file to determine if TFTP is configured properly. Procedure: Check if TFTP if used. # grep disable /etc/xinetd.d/tftp If the file does not exist or the returned line indicates "yes", then this is not a finding. Otherwise, if the returned line indicates "no" then TFTP is enabled and must use a dedicated "tftp" user. # grep user /etc/xinetd.d/tftp If the returned line indicates a user other than the dedicated "tftp" user, this is a finding. # grep tftp /etc/passwd If a "tftp" user account does not exist and TFTP is active, this is a finding. Check the user shell for the "tftp" user. If it is not /bin/false or equivalent, this is a finding. Check the home directory assigned to the "tftp" user. If no home directory is set, or the directory specified is not dedicated to the use of the TFTP service, this is a finding.
Fix: F-31798r1_fix
Configure TFTP to use a dedicated "tftp" user. Procedure: Create a dedicated "tftp" user account if none exists. Assign a non-login shell to the "tftp" user account, such as /bin/false. Assign a home directory to the "tftp" user account. Edit /etc/xinetd.d/tftp to have "tftp" as the value of the "user" parameter.
- RMF Control
- CM-2
- Severity
- M
- CCI
- CCI-000297
- Version
- GEN005160
- Vuln IDs
-
- V-850
- Rule IDs
-
- SV-37678r1_rule
Checks: C-36865r2_chk
Check for .Xauthority or .xauth files being utilized by looking for such files in the home directory of a user. Procedure: Verify Xwindows is used on the system. # egrep "^x:5.*X11" /etc/inittab If no line is returned the boot process does not start Xwindows. If Xwindows is not configured to run, this rule is not applicable. Look for xauthority files in user home directory. # cd ~someuser # ls -la|egrep "(\.Xauthority|\.xauth)" If the .Xauthority or .xauth (followed by apparently random characters) files do not exist, ask the SA if the user is using Xwindows. If the user is utilizing Xwindows and none of these files exist, this is a finding.
Fix: F-31811r1_fix
Ensure the X Windows host is configured to write .Xauthority files into user home directories. Edit the Xaccess file. Ensure the line writing the .Xauthority file is uncommented.
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001435
- Version
- GEN006400
- Vuln IDs
-
- V-867
- Rule IDs
-
- SV-37742r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32202r1_fix
Disable the use of NIS/NIS+. Use as a replacement Kerberos or LDAP.
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN001440
- Vuln IDs
-
- V-899
- Rule IDs
-
- SV-37375r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31306r1_fix
Assign a home directory to any user without one.
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN001460
- Vuln IDs
-
- V-900
- Rule IDs
-
- SV-37379r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31310r1_fix
If a user has no home directory, determine why. If possible, delete accounts without a home directory. If the account is valid, then create the home directory using the appropriate system administration utility or manually. For instance: mkdir directoryname; copy the skeleton files into the directory; chown accountname for the new directory and the skeleton files. Document all changes.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001480
- Vuln IDs
-
- V-901
- Rule IDs
-
- SV-37154r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32772r1_fix
Change the mode of user home directories to 0750 or less permissive. Procedure (example): # chmod 0750 <home directory> Note: Application directories are allowed and may need 0755 permissions (or greater) for correct operation.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001500
- Vuln IDs
-
- V-902
- Rule IDs
-
- SV-37163r1_rule
Checks: C-37526r1_chk
Check the ownership of each user home directory listed in the /etc/passwd file. Procedure: # cut -d : -f 6 /etc/passwd | xargs -n1 ls -ld If any user home directory is not owned by the assigned user, this is a finding.
Fix: F-1056r2_fix
Change the owner of a user's home directory to its assigned user. Procedure: # chown <user> <home directory>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001520
- Vuln IDs
-
- V-903
- Rule IDs
-
- SV-37168r1_rule
Checks: C-37527r2_chk
Check the group ownership for each user in the /etc/passwd file. Procedure: # cut -d : -f 6 /etc/passwd | xargs -n1 ls -ld If any user home directory is not group-owned by the assigned user's primary group, this is a finding. Home directories for application accounts requiring different group ownership must be documented using site-defined procedures.
Fix: F-32773r1_fix
Change the group-owner for user home directories to the primary group of the assigned user. Procedure: Find the primary group of the user (GID) which is the fourth field of the user entry in /etc/passwd. # chgrp <GID> <user home directory> Document all changes.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001860
- Vuln IDs
-
- V-904
- Rule IDs
-
- SV-37430r2_rule
Checks: C-35939r2_chk
NOTE: The following commands must be run in the BASH shell. Check the ownership of local initialization files. Procedure: # ls -al /<usershomedirectory>/.login # ls -al /<usershomedirectory>/.cshrc # ls -al /<usershomedirectory>/.logout # ls -al /<usershomedirectory>/.profile # ls -al /<usershomedirectory>/.bash_profile # ls -al /<usershomedirectory>/.bashrc # ls -al /<usershomedirectory>/.bash_logout # ls -al /<usershomedirectory>/.env # ls -al /<usershomedirectory>/.dtprofile # ls -al /<usershomedirectory>/.dispatch # ls -al /<usershomedirectory>/.emacs # ls -al /<usershomedirectory>/.exrc # find /<usershomedirectory>/.dt ! -fstype nfs ! -user <username> -exec ls -ld {} \; If local initialization files are not owned by the home directory's user, this is a finding.
Fix: F-31196r1_fix
Change the ownership of the startup and login files in the user's directory to the user or root, as appropriate. Examine each user's home directory and verify all filenames beginning with "." are owned by the owner of the directory or root. If they are not, use the chown command to change the owner to the user and research the reasons why the owners were not assigned as required. Procedure: # chown username .filename Document all changes.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001880
- Vuln IDs
-
- V-905
- Rule IDs
-
- SV-37431r1_rule
Checks: C-36108r1_chk
Check the modes of local initialization files. Procedure: # ls -al /<usershomedirectory>/.bashrc # ls -al /<usershomedirectory>/.bash_login # ls -al /<usershomedirectory>/.bash_logout # ls -al /<usershomedirectory>/.bash_profile # ls -al /<usershomedirectory>/.cshrc # ls -al /<usershomedirectory>/.kshrc # ls -al /<usershomedirectory>/.login # ls -al /<usershomedirectory>/.logout # ls -al /<usershomedirectory>/.profile # ls -al /<usershomedirectory>/.tcshrc # ls -al /<usershomedirectory>/.env # ls -al /<usershomedirectory>/.dtprofile (permissions should be 0755) # ls -al /<usershomedirectory>/.dispatch # ls -al /<usershomedirectory>/.emacs # ls -al /<usershomedirectory>/.exrc # find /<usershomedirectory>/.dt ! -fstype nfs \( -perm -0002 -o -perm -0020 \) -exec ls -ld {} \; (permissions not to be more permissive than 0755) If local initialization files are more permissive than 0740 or the .dt directory is more permissive than 0755 or the .dtprofile file is more permissive than 0755, this is a finding.
Fix: F-31202r1_fix
Ensure user startup files have permissions of 0740 or more restrictive. Examine each user's home directory and verify all file names beginning with "." have access permissions of 0740 or more restrictive. If they do not, use the chmod command to correct the vulnerability. Procedure: # chmod 0740 .filename Note: The period is part of the file name and is required.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001580
- Vuln IDs
-
- V-906
- Rule IDs
-
- SV-37192r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32777r1_fix
Ensure all system startup files have mode 0755 or less permissive. Examine the "rc" files, and all files in the rc1.d (rc2.d, and so on) directories, and in the /etc/init.d directory to ensure they are not world-writable. If they are world-writable, use the chmod command to correct the vulnerability and research why they are world-writable. Procedure: # chmod 755 <startup file>
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001600
- Vuln IDs
-
- V-907
- Rule IDs
-
- SV-37202r1_rule
Checks: C-37533r1_chk
Verify run control scripts' library search paths. # grep -r PATH /etc/rc* /etc/init.d This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon, or two consecutive colons, this is a finding. If an entry begins with a character other than a slash (/), this is a relative path, this is a finding.
Fix: F-32779r1_fix
Edit the run control script and remove the relative path entry from the executable search path variable.
- RMF Control
- AC-6
- Severity
- H
- CCI
- CCI-000225
- Version
- GEN001640
- Vuln IDs
-
- V-910
- Rule IDs
-
- SV-38154r2_rule
Checks: C-402r8_chk
Check the permissions on the files or scripts executed from system startup scripts to see if they are world-writable. Create a list of all potential run command level scripts. ls -l /etc/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d " " Create a list of world writeable files. # find / -perm -002 -type f >> worldWriteableFileList Determine if any of the world writeable files in worldWriteableFileList are called from the run command level scripts. Note: Depending upon the number of scripts vs world writeable files, it may be easier to inspect the scripts manually. # more `ls -l /etc/init.d/* | tr '\011' ' ' | tr -s ' ' | cut -f 9,9 -d "` If any system startup script executes any file or script that is world-writable, this is a finding.
Fix: F-1064r2_fix
Remove the world-writable permission from programs or scripts executed by run control scripts. Procedure: # chmod o-w <program or script executed from run control script>
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000196
- Version
- GEN002000
- Vuln IDs
-
- V-913
- Rule IDs
-
- SV-37436r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31295r1_fix
Remove the .netrc file(s). Procedure: # find / -name .netrc # rm <.netrc file>
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN001540
- Vuln IDs
-
- V-914
- Rule IDs
-
- SV-37175r1_rule
Checks: C-37528r1_chk
For each user in the /etc/passwd file, check for the presence of files and directories within the user's home directory not owned by the home directory owner. Procedure: # find /<usershomedirectory> ! -fstype nfs ! -user <username> ! \( -name .bashrc -o -name .bash_login -o -name .bash_logout -o -name .bash_profile -o -name .cshrc -o -name .kshrc -o -name .login -o -name .logout -o -name .profile -o -name .tcshrc -o -name .env -o -name .dtprofile -o -name .dispatch -o -name .emacs -o -name .exrc \) -exec ls -ld {} \; If user home directories contain files or directories not owned by the home directory owner, this is a finding.
Fix: F-32774r1_fix
Change the ownership of files and directories in user home directories to the owner of the home directory. Procedure: # chown accountowner filename
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN001560
- Vuln IDs
-
- V-915
- Rule IDs
-
- SV-37183r1_rule
Checks: C-37529r1_chk
For each user in the /etc/passwd file, check for files and directories with a mode more permissive than 0750. Procedure: # find /<usershomedirectory> ! -fstype nfs ! \( -name .bashrc -o -name .bash_login -o -name .bash_logout -o -name .bash_profile -o -name .cshrc -o -name .kshrc -o -name .login -o -name .logout -o -name .profile -o -name .tcshrc -o -name .env -o -name .dtprofile -o -name .dispatch -o -name .emacs -o -name .exrc \) \( -perm -0001 -o -perm -0002 -o -perm -0004 -o -perm -0020 -o -perm -2000 -o -perm -4000 \) -exec ls -ld {} \; If user home directories contain files or directories more permissive than 0750, this is a finding.
Fix: F-32775r1_fix
Change the mode of files and directories within user home directories to 0750. Procedure: # chmod 0750 filename Document all changes.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN002120
- Vuln IDs
-
- V-916
- Rule IDs
-
- SV-37390r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31321r1_fix
Create a /etc/shells file containing a list of valid system shells. Consult vendor documentation for an appropriate list of system shells. Procedure: # echo "/bin/bash" >> /etc/shells # echo "/bin/csh" >> /etc/shells (Repeat as necessary for other shells.)
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN002140
- Vuln IDs
-
- V-917
- Rule IDs
-
- SV-37393r1_rule
Checks: C-36080r2_chk
Confirm the login shells referenced in the /etc/passwd file are listed in the /etc/shells file. Procedure: # for USHELL in `cut -d: -f7 /etc/passwd`; do if [ $(grep -c "${USHELL}" /etc/shells) == 0 ]; then echo "${USHELL} not in /etc/shells"; fi; done The /usr/bin/false, /bin/false, /dev/null, /sbin/nologin, /bin/sync, /sbin/halt, /sbin/shutdown, (and equivalents), and sdshell will be considered valid shells for use in the /etc/passwd file, but will not be listed in the /etc/shells file. If a shell referenced in /etc/passwd is not listed in the shells file, excluding the above mentioned shells, this is a finding.
Fix: F-31324r2_fix
Use the "chsh" utility or edit the /etc/passwd file and correct the error by changing the default shell of the account in error to an acceptable shell name contained in the /etc/shells file. Example: # chsh -s /bin/bash testuser
- RMF Control
- AC-2
- Severity
- M
- CCI
- CCI-000017
- Version
- GEN000760
- Vuln IDs
-
- V-918
- Rule IDs
-
- SV-37314r2_rule
Checks: C-36007r4_chk
Indications of inactive accounts are those that have no entries in the "last" log. Check the date in the "last" log to verify it is within the last 35 days or the maximum numbers of days set by the site if more restrictive. If an inactive account is not disabled via an entry in the password field in the /etc/passwd or /etc/shadow (or equivalent), check the /etc/passwd file to check if the account has a valid shell. The passwd command can also be used to list a status for an account. For example, the following may be used to provide status information on each local account: NOTE: The following must be done in the BASH shell. # cut -d: -f1 /etc/passwd | xargs -n1 passwd -S If an inactive account is found not disabled, this is a finding.
Fix: F-31259r2_fix
All inactive accounts will have /sbin/nologin (or an equivalent), as the default shell in the /etc/passwd file and have the password disabled. Examine the user accounts using the "last" command. Note the date of last login for each account. If any (other than system and application accounts) exceed 35 days or the maximum number of days set by the site, not to exceed 35 days, then disable the accounts using system-config-users tool. Alternately place a shell field of /sbin/nologin /bin/false or /dev/null in the passwd file entry for the account.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002200
- Vuln IDs
-
- V-921
- Rule IDs
-
- SV-37396r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31328r1_fix
Change the ownership of the shell with incorrect ownership. # chown root <shell>
- RMF Control
- AC-6
- Severity
- H
- CCI
- CCI-000225
- Version
- GEN002220
- Vuln IDs
-
- V-922
- Rule IDs
-
- SV-37403r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31334r1_fix
Change the mode of the shell. # chmod 0755 <shell>
- RMF Control
- CM-3
- Severity
- L
- CCI
- CCI-000318
- Version
- GEN002260
- Vuln IDs
-
- V-923
- Rule IDs
-
- SV-37543r1_rule
Checks: C-36198r2_chk
Ask the SA for the automated or manual process used to check for extraneous device files. Review the process to determine if the system is checked for extraneous device files on a weekly basis. If no weekly automated or manual process is in place, this is a finding. If the process is not identifying extraneous device files, this is a finding.
Fix: F-31458r1_fix
Establish a weekly automated or manual process to create a list of device files on the system and determine if any files have been added, moved, or deleted since the last list was generated. A list of device files can be generated with this command: # find / -type b -o -type c > device-file-list
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002280
- Vuln IDs
-
- V-924
- Rule IDs
-
- SV-37553r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31464r1_fix
Remove the world-writable permission from the device file(s). Procedure: # chmod o-w <device file> Document all changes.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002300
- Vuln IDs
-
- V-925
- Rule IDs
-
- SV-37558r1_rule
Checks: C-36209r4_chk
Check the system for world-writable device files. Procedure: # find / -perm -2 -a \( -type b -o -type c \) -exec ls -ld {} \; Ask the SA to identify any device files used for backup purposes. If any device file(s) used for backup are writable by users other than root or the designated backup user, this is a finding.
Fix: F-31469r1_fix
Use the chmod command to remove the world-writable bit from the backup device files. Procedure: # chmod o-w <back device filename> Document all changes.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005740
- Vuln IDs
-
- V-928
- Rule IDs
-
- SV-37936r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32428r1_fix
Change the owner of the exports file to root. Example: # chown root /etc/exports
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN005760
- Vuln IDs
-
- V-929
- Rule IDs
-
- SV-37943r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32434r1_fix
# chmod 0644 /etc/exports
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005800
- Vuln IDs
-
- V-931
- Rule IDs
-
- SV-37849r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32313r1_fix
Change the ownership of exported file systems not owned by root. Procedure: # chown root <path>
- RMF Control
- AC-14
- Severity
- M
- CCI
- CCI-000062
- Version
- GEN005820
- Vuln IDs
-
- V-932
- Rule IDs
-
- SV-37854r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32316r1_fix
Edit "/etc/exports" and set the "anonuid=-1" and "anongid=-1" options for exports lacking it. Re-export the filesystems.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005840
- Vuln IDs
-
- V-933
- Rule IDs
-
- SV-37857r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32328r1_fix
Edit /etc/exports and add ro and/or rw options (as appropriate) specifying a list of hosts or networks which are permitted access. Re-export the file systems.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005880
- Vuln IDs
-
- V-935
- Rule IDs
-
- SV-37859r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32333r1_fix
Edit the "/etc/exports" file and add "root_squash" (or "all_squash") and remove "no_root_squash".
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005900
- Vuln IDs
-
- V-936
- Rule IDs
-
- SV-37860r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32336r1_fix
Edit "/etc/fstab" and add the "nosuid" option for all NFS file systems. Remount the NFS file systems to make the change take effect.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN006580
- Vuln IDs
-
- V-940
- Rule IDs
-
- SV-37756r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32218r1_fix
Install and configure the tcp_wrappers package.
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN006600
- Vuln IDs
-
- V-941
- Rule IDs
-
- SV-37757r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32219r1_fix
Configure the access restriction program to log every access attempt. Ensure the implementation instructions for tcp_wrappers are followed so system access attempts are recorded to the system log files. If an alternate application is used, it must support this function.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002960
- Vuln IDs
-
- V-974
- Rule IDs
-
- SV-27320r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24560r2_fix
Create /etc/cron.allow and/or /etc/cron.deny with appropriate content and reboot the system to ensure no lingering cron jobs are processed.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002980
- Vuln IDs
-
- V-975
- Rule IDs
-
- SV-27326r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24566r1_fix
Change the mode of the cron.allow file to 0600. Procedure: # chmod 0600 /etc/cron.allow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003000
- Vuln IDs
-
- V-976
- Rule IDs
-
- SV-37384r1_rule
Checks: C-36071r1_chk
List all cronjobs on the system. Procedure: # ls /var/spool/cron # ls /etc/cron.d /etc/crontab /etc/cron.daily /etc/cron.hourly /etc/cron.monthly /etc/cron.weekly or # ls /etc/cron*|grep -v deny If cron jobs exist under any of the above directories, use the following command to search for programs executed by cron: # more <cron job file> Perform a long listing of each program file found in the cron file to determine if the file is group-writable or world-writable. # ls -la <cron program file> If cron executes group-writable or world-writable files, this is a finding.
Fix: F-31315r1_fix
Remove the world-writable and group-writable permissions from the cron program file(s) identified. # chmod go-w <cron program file>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003020
- Vuln IDs
-
- V-977
- Rule IDs
-
- SV-37388r1_rule
Checks: C-36074r1_chk
List all cronjobs on the system. Procedure: # ls /var/spool/cron # ls /etc/cron.d /etc/crontab /etc/cron.daily /etc/cron.hourly /etc/cron.monthly /etc/cron.weekly or # ls /etc/cron*|grep -v deny If cron jobs exist under any of the above directories, use the following command to search for programs executed by at: # more <cron job file> Perform a long listing of each directory containing program files found in the cron file to determine if the directory is world-writable. # ls -ld <cron program directory> If cron executes programs in world-writable directories, this is a finding.
Fix: F-31318r1_fix
Remove the world-writable permission from the cron program directories identified. Procedure: # chmod o-w <cron program directory>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003080
- Vuln IDs
-
- V-978
- Rule IDs
-
- SV-37466r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31377r1_fix
Change the mode of the crontab files. # chmod 0600 /var/spool/cron/* /etc/cron.d/* /etc/crontab
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003100
- Vuln IDs
-
- V-979
- Rule IDs
-
- SV-37470r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31381r1_fix
Change the mode of the crontab directories. # chmod 0755 <crontab directory>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003120
- Vuln IDs
-
- V-980
- Rule IDs
-
- SV-37474r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31386r1_fix
Change the mode of the crontab directories. # chown root <crontab directory>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003140
- Vuln IDs
-
- V-981
- Rule IDs
-
- SV-37476r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31388r1_fix
Change the group owner of cron and crontab directories. # chgrp root <crontab directory>
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN003160
- Vuln IDs
-
- V-982
- Rule IDs
-
- SV-27352r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31389r1_fix
Edit /etc/syslog.conf and setup cron logging.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003180
- Vuln IDs
-
- V-983
- Rule IDs
-
- SV-27357r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24602r1_fix
Change the mode of the cron log file. # chmod 0600 /var/log/cron
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003280
- Vuln IDs
-
- V-984
- Rule IDs
-
- SV-37512r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31419r1_fix
Create at.allow and/or at.deny files containing appropriate lists of users to be allowed or denied access to the "at" daemon.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003300
- Vuln IDs
-
- V-985
- Rule IDs
-
- SV-37516r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31426r1_fix
Add appropriate users to the at.deny file, or remove the empty at.deny file if an at.allow file exists.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003320
- Vuln IDs
-
- V-986
- Rule IDs
-
- SV-37517r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31427r1_fix
Remove the default accounts (such as bin, sys, adm, and others, traditionally UID less than 500) from the at.allow file.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003340
- Vuln IDs
-
- V-987
- Rule IDs
-
- SV-37518r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31428r1_fix
Change the mode of the at.allow file. # chmod 0600 /etc/at.allow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003360
- Vuln IDs
-
- V-988
- Rule IDs
-
- SV-37519r1_rule
Checks: C-36179r1_chk
List the "at" jobs on the system. Procedure: # ls -la /var/spool/at For each "at" job file, determine which programs are executed. Procedure: # more <at job file> Check the each program executed by "at" for group- or world-writable permissions. Procedure: # ls -la <at program file> If "at" executes group or world-writable programs, this is a finding.
Fix: F-31429r1_fix
Remove group-write and world-write permissions from files executed by at jobs. Procedure: # chmod go-w <file>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003380
- Vuln IDs
-
- V-989
- Rule IDs
-
- SV-37520r1_rule
Checks: C-36180r1_chk
List any "at" jobs on the system. Procedure: # ls /var/spool/at For each "at" job, determine which programs are executed by "at." Procedure: # more <at job file> Check the directory containing each program executed by "at" for world-writable permissions. Procedure: # ls -la <at program file directory> If "at" executes programs in world-writable directories, this is a finding.
Fix: F-31432r1_fix
Remove the world-writable permission from directories containing programs executed by "at". Procedure: # chmod o-w <at program directory>
- RMF Control
- IA-5
- Severity
- H
- CCI
- CCI-000178
- Version
- GEN005300
- Vuln IDs
-
- V-993
- Rule IDs
-
- SV-37689r1_rule
Checks: C-36883r1_chk
Check the SNMP configuration for default passwords. Procedure: Examine the default install location /etc/snmp/snmpd.conf or: # find / -name snmpd.conf # more <snmpd.conf file> Identify any community names or user password configuration. If any community name or password is set to a default value such as "public", "private", "snmp-trap", or "password", or any value which does not meet DISA password requirements, this is a finding.
Fix: F-31908r1_fix
Change the default passwords. To change them, locate the file snmpd.conf. Edit the file. Locate the line system-group-read-community which has a default password of "public" and make the password something more secure and less guessable. Do the same for the lines reading system-group-write-community, read-community, write-community, trap and trap-community. Read the information in the file carefully. The trap is defining who to send traps to, for instance, by default. It is not a password, but the name of a host.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005320
- Vuln IDs
-
- V-994
- Rule IDs
-
- SV-37696r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31997r1_fix
Change the mode of the SNMP daemon configuration file to 0600. Procedure: # chmod 0600 <snmpd.conf>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005340
- Vuln IDs
-
- V-995
- Rule IDs
-
- SV-37698r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32000r1_fix
Change the mode of MIB files to 0640. Procedure: # chmod 0640 <mib file>
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN002480
- Vuln IDs
-
- V-1010
- Rule IDs
-
- SV-37645r1_rule
Checks: C-36841r1_chk
Check the system for world-writable files. Procedure: # find / -perm -2 -a \( -type d -o -type f \) -exec ls -ld {} \; If any world-writable files are located, except those required for system operation such as /tmp and /dev/null, this is a finding.
Fix: F-31679r1_fix
Remove or change the mode for any world-writable file on the system not required to be world-writable. Procedure: # chmod o-w <file> Document all changes
- RMF Control
- AU-3
- Severity
- L
- CCI
- CCI-000134
- Version
- GEN003800
- Vuln IDs
-
- V-1011
- Rule IDs
-
- SV-37439r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31357r1_fix
Edit each file in the /etc/xinetd.d directory and the /etc/xinetd.conf file to contain: log_type = SYSLOG authpriv log_on_success = HOST PID USERID EXIT log_on_failure = HOST USERID The /etc/xinetd.conf file contains default values that will hold true for all services unless individually modified in the service's xinetd.d file. To make the new settings effective, restart the xinetd service: # service xinetd restart
- RMF Control
- CM-6
- Severity
- H
- CCI
- CCI-000366
- Version
- GEN008600
- Vuln IDs
-
- V-1013
- Rule IDs
-
- SV-37986r1_rule
Checks: C-37289r1_chk
Determine if the system is configured to boot from devices other than the system startup media. If so, this is a finding.
Fix: F-32526r1_fix
Configure the system to only boot from system startup media. Procedure: On systems with a BIOS or system controller use the BIOS interface at startup to remove all but the proper boot device from the boot device list.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000000-LNX00360
- Vuln IDs
-
- V-1021
- Rule IDs
-
- SV-37207r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31154r1_fix
Enable the following options: -audit (at level 4), -auth and -s with 15 minutes as the timeout value. Procedure for gdm: Edit /etc/gdm/custom.conf and add the following: [server-Standard] name=Standard server command=/usr/bin/Xorg -br -audit 4 -s 15 chooser=false handled=true flexible=true priority=0 Procedure for xinit: Edit or create a .xserverrc file in the users home directory containing the startup script for xinit. This script must have an exec line with at least these options: exec /usr/bin/X -audit 4 -s 15 -auth <Xauth file> & The <Xauth file> is created using the "xauth" command and is customarily located in the users home directory with the name ".Xauthority".
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000000-LNX00380
- Vuln IDs
-
- V-1022
- Rule IDs
-
- SV-37217r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31162r1_fix
Disable the unwanted options: Procedure: For gdm: Remove the -ac, -core and -nolock options by creating a "command" entry in the /etc/gdm/custom.conf file with the options removed. For Xwindows started by xinit: Create or modify the .xserverrc script in the users home directory to remove the -ac, -core and -nolock options from the exec /usr/bin/X command.
- RMF Control
- CM-7
- Severity
- M
- CCI
- CCI-000381
- Version
- GEN006240
- Vuln IDs
-
- V-1023
- Rule IDs
-
- SV-37899r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32393r1_fix
Disable the INN server.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00400
- Vuln IDs
-
- V-1025
- Rule IDs
-
- SV-37224r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31171r1_fix
Follow the correct configuration parameters for access configuration file. Use the chown command to configure it properly. (for example: # chown root /etc/security/access.conf ).
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001436
- Version
- GEN006080
- Vuln IDs
-
- V-1026
- Rule IDs
-
- SV-37870r1_rule
Checks: C-37085r3_chk
SWAT is a tool for configuring Samba and should only be found on a system with a requirement for Samba. If SWAT is used, it must be utilized with SSL to ensure a secure connection between the client and the server. Procedure: # grep -H "bin/swat" /etc/xinetd.d/*|cut -d: -f1 |xargs grep "only_from" If the value of the "only_from" line in the "xinetd.d" file which starts "/usr/sbin/swat" is not "localhost" or the equivalent, this is a finding.
Fix: F-32357r2_fix
Disable SWAT or require SWAT is only accessed via SSH. Procedure: If SWAT is not needed for operation of the system remove the SWAT package: # rpm -qa|grep swat Remove "samba-swat" or "samba3x-swat" depending on which one is installed # rpm --erase samba-swat or # rpm --erase samba3x-swat If SWAT is required but not at all times disable it when it is not needed. Modify the /etc/xinetd.d file for "swat" to contain a "disable = yes" line. To access using SSH: Follow vendor configuration documentation to create an stunnel for SWAT.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006100
- Vuln IDs
-
- V-1027
- Rule IDs
-
- SV-37871r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32360r1_fix
Change the ownership of the smb.conf file. Procedure: # chown root smb.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006140
- Vuln IDs
-
- V-1028
- Rule IDs
-
- SV-37875r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32370r1_fix
Change the mode of the smb.conf file to 0644 or less permissive. Procedure: # chmod 0644 smb.conf.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006160
- Vuln IDs
-
- V-1029
- Rule IDs
-
- SV-37879r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32373r1_fix
Use the chown command to configure the files maintained by smbpasswd. For instance: # chown root /etc/samba/passdb.tdb /etc/samba/secrets.tdb
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006220
- Vuln IDs
-
- V-1030
- Rule IDs
-
- SV-37887r1_rule
Checks: C-37113r1_chk
Examine the "smb.conf" file. # more /etc/samba/smb.conf If the "hosts" option is not present to restrict access to a list of authorized hosts and networks, this is a finding.
Fix: F-32381r1_fix
Edit the "/etc/samba/smb.conf" file and set the "hosts" option to permit only authorized hosts to access Samba.
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000198
- Version
- GEN000540
- Vuln IDs
-
- V-1032
- Rule IDs
-
- SV-37239r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31186r1_fix
Change the minimum time period between password changes for each user account to 1 day. # passwd -n 1 <user name>
- RMF Control
- IA-5
- Severity
- H
- CCI
- CCI-000197
- Version
- GEN001100
- Vuln IDs
-
- V-1046
- Rule IDs
-
- SV-37150r1_rule
Checks: C-35865r1_chk
Determine if root has logged in over an unencrypted network connection. First determine if root has logged in over a network. Procedure: # last | grep "^root " | egrep -v "reboot|console" | more Next determine if the SSH daemon is running. Procedure: # ps -ef |grep sshd If root has logged in over the network and sshd is not running, this is a finding.
Fix: F-31120r1_fix
Enable SSH on the system and use it for all remote connections used to attain root access
- RMF Control
- IA-2
- Severity
- M
- CCI
- CCI-000770
- Version
- GEN001120
- Vuln IDs
-
- V-1047
- Rule IDs
-
- SV-37156r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31118r1_fix
Edit the sshd_config file and set the PermitRootLogin option to "no".
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002320
- Vuln IDs
-
- V-1048
- Rule IDs
-
- SV-37566r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31476r1_fix
Change the mode of audio devices. # chmod 0660 <audio device>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002340
- Vuln IDs
-
- V-1049
- Rule IDs
-
- SV-37575r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31611r1_fix
Change the owner of the audio device. # chown root <audio device>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00420
- Vuln IDs
-
- V-1054
- Rule IDs
-
- SV-37227r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31174r1_fix
Use the chgrp command to ensure the group owner is root, sys, or bin. (for example: # chgrp root /etc/security/access.conf ).
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00440
- Vuln IDs
-
- V-1055
- Rule IDs
-
- SV-37243r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31190r1_fix
Use the chmod command to set the permissions to 0640. (for example: # chmod 0640 /etc/security/access.conf ).
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006120
- Vuln IDs
-
- V-1056
- Rule IDs
-
- SV-37873r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32365r1_fix
Change the group owner of the smb.conf file. Procedure: # chgrp root smb.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006180
- Vuln IDs
-
- V-1058
- Rule IDs
-
- SV-41574r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-35231r1_fix
Use the chgrp command to ensure that the group owner of the smbpasswd file is root. For instance: # chgrp root /etc/samba/passdb.tdb /etc/samba/secrets.tdb
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006200
- Vuln IDs
-
- V-1059
- Rule IDs
-
- SV-41575r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-35233r1_fix
Change the mode of the files maintained through smbpasswd to 0600. Procedure: # chmod 0600 /etc/samba/passdb.tdb /etc/samba/secrets.tdb
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002360
- Vuln IDs
-
- V-1061
- Rule IDs
-
- SV-37577r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31613r1_fix
Change the group-owner of the audio device. Procedure: # chgrp root <audio device>
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN001080
- Vuln IDs
-
- V-1062
- Rule IDs
-
- SV-37380r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31311r1_fix
Change the root account's shell to one present on the / file system. Procedure: Edit /etc/passwd and change the shell for the root account to one present on the / file system (such as /bin/sh, assuming /bin is not on a separate file system). If the system does not store shell configuration in the /etc/passwd file, consult vendor documentation for the correct procedure for the system.
- RMF Control
- AC-11
- Severity
- M
- CCI
- CCI-000057
- Version
- GEN000500
- Vuln IDs
-
- V-4083
- Rule IDs
-
- SV-48455r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-26907r1_fix
For the Gnome screen saver, set the idle_activation_enabled flag. Procedure: # gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set /apps/gnome-screensaver/idle_activation_enabled true
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000200
- Version
- GEN000800
- Vuln IDs
-
- V-4084
- Rule IDs
-
- SV-37323r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31265r2_fix
Create the password history file. # touch /etc/security/opasswd # chown root:root /etc/security/opasswd # chmod 0600 /etc/security/opasswd Enable password history. If /etc/pam.d/system-auth references /etc/pam.d/system-auth-ac refer to the man page for system-auth-ac for a description of how to add options not configurable with authconfig. Edit /etc/pam.d/system-auth to include the remember option on any "password pam_unix" or "password pam_history" lines set to at least 5.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001940
- Vuln IDs
-
- V-4087
- Rule IDs
-
- SV-37433r1_rule
Checks: C-36012r3_chk
Check local initialization files for any executed world-writable programs or scripts and scripts executing from world writable directories. Procedure: For each home directory on the system make a list of files referenced within any local initialization script. Show the mode for each file and its parent directory. # FILES=".bashrc .bash_login .bash_logout .bash_profile .cshrc .kshrc .login .logout .profile .tcshrc .env .dtprofile .dispatch .emacs .exrc"; # for HOMEDIR in `cut -d: -f6 /etc/passwd|sort|uniq`;do for INIFILE in $FILES;do REFLIST=`egrep " [\"~]?/" ${HOMEDIR}/${INIFILE} 2>null|sed "s/.*\([~ \"]\/[\.0-9A-Za-z_\/\-]*\).*/\1/"`;for REFFILE in $REFLIST;do FULLREF=`echo $REFFILE|sed "s:\~:${HOMEDIR}:g"|sed "s:^\s*::g"`;dirname $FULLREF|xargs stat -c "dir:%a:%n";stat -c "file:%a:%n" $FULLREF;done;done;done|sort|uniq This command outputs a list of files and directories and their associated access modes. If any local initialization file executes a world-writable program or script or a script from a world-writable directory, this is a finding.
Fix: F-31263r1_fix
Remove the world-writable permission of files referenced by local initialization scripts, or remove the references to these files in the local initialization scripts.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001660
- Vuln IDs
-
- V-4089
- Rule IDs
-
- SV-37264r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31210r1_fix
Change the ownership of the run control script(s) with incorrect ownership. # find /etc -name "[SK][0-9]*"|xargs stat -L -c %U:%n|egrep -v "^root:"|cut -d: -f2|xargs chown root
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001680
- Vuln IDs
-
- V-4090
- Rule IDs
-
- SV-37269r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31216r1_fix
Change the group ownership of the run control script(s) with incorrect group ownership. Procedure: # chgrp root <run control script> # find /etc -name "[SK][0-9]*"|xargs stat -L -c %G:%n|egrep -v "^(root|sys|bin|other):"|cut -d: -f2|xargs chgrp root
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001700
- Vuln IDs
-
- V-4091
- Rule IDs
-
- SV-37270r1_rule
Checks: C-35962r1_chk
Determine the programs executed by system start-up files. Determine the ownership of the executed programs. # cat /etc/rc*/* /etc/init.d/* | more # ls -l <executed program> Alternatively: # for FILE in `egrep -r "/" /etc/rc.* /etc/init.d|awk '/^.*[^\/][0-9A-Za-z_\/]*/{print $2}'|egrep "^/"|sort|uniq`;do if [ -e $FILE ]; then stat -L -c '%U:%n' $FILE;fi;done This provides a list of files referenced by initialization scripts and their associated UIDs. If any file is run by an initialization file and is not owned by root, sys, bin, or in rare cases, an application account, this is a finding.
Fix: F-31218r1_fix
Change the ownership of the file executed from system startup scripts to root, bin, sys, or other. # chown root <executed file>
- RMF Control
- AC-3
- Severity
- M
- CCI
- CCI-000213
- Version
- GEN008620
- Vuln IDs
-
- V-4246
- Rule IDs
-
- SV-37925r1_rule
Checks: C-37163r1_chk
On systems with a BIOS or system controller, verify a supervisor or administrator password is set. If a password is not set, this is a finding. If the BIOS or system controller supports user-level access in addition to supervisor/administrator access, determine if this access is enabled. If so, this is a finding.
Fix: F-4157r2_fix
Access the system's BIOS or system controller. Set a supervisor/administrator password if one has not been set. Disable a user-level password if one has been set.
- RMF Control
- CM-6
- Severity
- H
- CCI
- CCI-000366
- Version
- GEN008640
- Vuln IDs
-
- V-4247
- Rule IDs
-
- SV-41534r1_rule
Checks: C-2057r2_chk
Ask the SA if the system uses removable media for the boot loader. If it does, this is a finding.
Fix: F-4158r2_fix
Configure the system to use a bootloader installed on fixed media.
- RMF Control
- CM-6
- Severity
- H
- CCI
- CCI-000366
- Version
- GEN008660
- Vuln IDs
-
- V-4248
- Rule IDs
-
- SV-42186r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-35823r1_fix
Configure the system to use the GRUB bootloader or document, justify, and authorize the alternate bootloader.
- RMF Control
- AC-3
- Severity
- H
- CCI
- CCI-000213
- Version
- GEN008700
- Vuln IDs
-
- V-4249
- Rule IDs
-
- SV-37933r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32425r1_fix
The GRUB console boot loader can be configured to use an MD5 encrypted password by adding password --md5 password-hash to the "/boot/grub/grub.conf" file. Use "/sbin/grub-md5-crypt" to generate MD5 passwords from the command line.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008720
- Vuln IDs
-
- V-4250
- Rule IDs
-
- SV-37942r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32433r1_fix
Change the mode of the grub.conf file to 0600. # chmod 0600 /boot/grub/grub.conf
- RMF Control
- SC-32
- Severity
- H
- CCI
- CCI-001208
- Version
- GEN008680
- Vuln IDs
-
- V-4255
- Rule IDs
-
- SV-4255r2_rule
Checks: C-2079r2_chk
Ask the SA if the system boots from removable media. If so, ask if the boot media is stored in a secure container when not in use. If it is not, this is a finding.
Fix: F-4166r2_fix
Store the system boot media in a secure container when not in use.
- RMF Control
- AC-6
- Severity
- H
- CCI
- CCI-000225
- Version
- GEN000000-LNX00320
- Vuln IDs
-
- V-4268
- Rule IDs
-
- SV-37181r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31139r1_fix
Remove any special privilege accounts, such as shutdown and halt, from the /etc/passwd and /etc/shadow files using the "userdel" or "system-config-users" commands.
- RMF Control
- AC-2
- Severity
- M
- CCI
- CCI-000012
- Version
- GEN000290
- Vuln IDs
-
- V-4269
- Rule IDs
-
- SV-38176r1_rule
Checks: C-37560r2_chk
Check the system for unnecessary user accounts. Procedure: # more /etc/passwd Obtain a list of authorized accounts from the IAO. If any unnecessary accounts are found on the system, this is a finding.
Fix: F-32804r1_fix
Remove all unnecessary accounts from the /etc/passwd file before connecting a system to the network. Other accounts that are associated with a service not in use should also be removed.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006260
- Vuln IDs
-
- V-4273
- Rule IDs
-
- SV-37901r1_rule
Checks: C-37127r1_chk
RHEL uses the InternetNewsDaemon (innd) news server. The file corresponding to "/etc/news/hosts.nntp" is "/etc/news/incoming.conf". Check the permissions for "/etc/news/incoming.conf". # ls -lL /etc/news/incoming.conf If "/etc/news/incoming.conf" has a mode more permissive than 0600, this is a finding.
Fix: F-32395r1_fix
Change the mode of the "/etc/news/incoming.conf" file to 0600. # chmod 0600 /etc/news/incoming.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006280
- Vuln IDs
-
- V-4274
- Rule IDs
-
- SV-37712r1_rule
Checks: C-36913r1_chk
RHEL uses the InternetNewsDaemon (innd) news server. The file that corresponds to "/etc/news/hosts.nntp.nolimit" is "/etc/news/infeed.conf". Check the permissions for "/etc/news/infeed.conf". # ls -lL /etc/news/infeed.conf If "/etc/news/infeed.conf" has a mode more permissive than 0600, this is a finding.
Fix: F-32122r1_fix
Change the mode of "/etc/news/infeed.conf" to 0600. # chmod 0600 /etc/news/infeed.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006300
- Vuln IDs
-
- V-4275
- Rule IDs
-
- SV-37714r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32155r1_fix
Change the mode of the /etc/news/readers.conf file to 0600. # chmod 0600 /etc/news/readers.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006320
- Vuln IDs
-
- V-4276
- Rule IDs
-
- SV-37731r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32193r1_fix
Change the mode of the "/etc/news/passwd.nntp" file. # chmod 0600 /etc/news/passwd.nntp
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006340
- Vuln IDs
-
- V-4277
- Rule IDs
-
- SV-37735r1_rule
Checks: C-36931r1_chk
Check the ownership of the files in "/etc/news". Procedure: # ls -al /etc/news If any files are not owned by root or news, this is a finding.
Fix: F-32195r1_fix
Change the ownership of the files in "/etc/news" to root or news. Procedure: # chown root /etc/news/*
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006360
- Vuln IDs
-
- V-4278
- Rule IDs
-
- SV-37737r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32198r1_fix
Change the group-owner of the files in "/etc/news" to root or news. Procedure: # chgrp root /etc/news/*
- RMF Control
- AC-17
- Severity
- H
- CCI
- CCI-001436
- Version
- GEN005500
- Vuln IDs
-
- V-4295
- Rule IDs
-
- SV-37818r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32288r2_fix
Edit the sshd_config file and set the "Protocol" setting to "2". If using the F-Secure SSH server, set the "Ssh1Compatibility" setting to "no". Restart the SSH daemon. # /sbin/service sshd restart
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-000070
- Version
- GEN001000
- Vuln IDs
-
- V-4298
- Rule IDs
-
- SV-37376r1_rule
Checks: C-36063r1_chk
Check /etc/securetty # more /etc/securetty If the file does not exist, or contains more than "console" or a single "tty" device this is a finding.
Fix: F-31307r1_fix
Create if needed and set the contents of /etc/securetty to a "console" or "tty" device. # echo console > /etc/securetty or # echo tty1 > /etc/securetty
- RMF Control
- AU-8
- Severity
- M
- CCI
- CCI-001492
- Version
- GEN000240
- Vuln IDs
-
- V-4301
- Rule IDs
-
- SV-37402r1_rule
Checks: C-36085r1_chk
Check if NTP running: # ps -ef | egrep "xntpd|ntpd" Check if "ntpd -qg" scheduled to run: # grep "ntpd -qg" /var/spool/cron/* # grep "ntpd -qg" /etc/cron.d/* # grep "ntpd -qg" /etc/cron.daily/* # grep "ntpd -qg" /etc/cron.hourly/* # grep "ntpd -qg" /etc/cron.monthly/* # grep "ntpd -qg" /etc/cron.weekly/* If NTP is running or "ntpd -qg" is found: # more /etc/ntp.conf Confirm the timeservers and peers or multicast client (as applicable) are local or authoritative U.S. DoD sources appropriate for the level of classification which the network operates. If a non-local/non-authoritative time-server is used, this is a finding.
Fix: F-31332r2_fix
Use an authoritative local time server or a time server operated by the U.S. government. Ensure all systems in the facility feed from one or more local time servers which feed from the authoritative U.S. government time server.
- RMF Control
- CP-10
- Severity
- M
- CCI
- CCI-000553
- Version
- GEN003640
- Vuln IDs
-
- V-4304
- Rule IDs
-
- SV-37398r1_rule
Checks: C-36083r1_chk
Logging should be enabled for those types of file systems not turning on logging by default. Procedure: # mount JFS, VXFS, HFS, XFS, reiserfs, EXT3 and EXT4 all turn logging on by default and will not be a finding. The ZFS file system uses other mechanisms to provide for file system consistency, and will not be a finding. For other file systems types, if the root file system does not support journaling this is a finding. If the 'nolog' option is set on the root file system that does support journaling, this is a finding.
Fix: F-31330r1_fix
Implement file system journaling for the root file system, or use a file system with other mechanisms to ensure file system consistency. If the root file system supports journaling, enable it. If the file system does not support journaling or another mechanism to ensure file system consistency, a migration to a different file system will be necessary.
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001436
- Version
- GEN006060
- Vuln IDs
-
- V-4321
- Rule IDs
-
- SV-37867r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32354r1_fix
If there is no functional need for Samba and the daemon is running, disable the daemon by killing the process ID as noted from the output of ps -ef |grep smbd. The samba package should also be removed or not installed if there is no functional requirement. Procedure: rpm -qa |grep samba This will show whether "samba" or "samba3x" is installed. To remove: rpm --erase samba or rpm --erase samba3x
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00480
- Vuln IDs
-
- V-4334
- Rule IDs
-
- SV-37253r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31200r1_fix
Use the chown command to change the owner of /etc/sysctl.conf to root: # chown root /etc/sysctl.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00500
- Vuln IDs
-
- V-4335
- Rule IDs
-
- SV-37257r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31203r1_fix
Use the chgrp command to change the group owner of /etc/sysctl.conf to root: # chgrp root /etc/sysctl.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00520
- Vuln IDs
-
- V-4336
- Rule IDs
-
- SV-37258r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31204r1_fix
Use the chmod command to change the mode of the /etc/sysctl.conf file. # chmod 0600 /etc/sysctl.conf
- RMF Control
- AC-6
- Severity
- H
- CCI
- CCI-000225
- Version
- GEN000000-LNX00560
- Vuln IDs
-
- V-4339
- Rule IDs
-
- SV-37316r1_rule
Checks: C-36008r1_chk
Determine if an NFS server is running on the system by: # ps -ef |grep nfsd If an NFS server is running, confirm it is not configured with the insecure_locks option by: # exportfs -v The example below would be a finding: /misc/export speedy.example.com(rw,insecure_locks)
Fix: F-4250r3_fix
Remove the "insecure_locks" option from all NFS exports on the system. Procedure: Edit /etc/exports and remove all instances of the insecure_locks option. Re-export the file systems to make the setting take effect. # exportfs -a
- RMF Control
- CM-6
- Severity
- H
- CCI
- CCI-000366
- Version
- GEN000000-LNX00580
- Vuln IDs
-
- V-4342
- Rule IDs
-
- SV-37327r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31276r1_fix
Ensure the CTRL-ALT-DELETE key sequence has been disabled and attempts to use the sequence are logged. In the /etc/inittab file replace: ca::ctrlaltdel:/sbin/shutdown -t3 -r now with ca:nil:ctrlaltdel:/usr/bin/logger -p security.info "Ctrl-Alt-Del was pressed"
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00600
- Vuln IDs
-
- V-4346
- Rule IDs
-
- SV-37339r1_rule
Checks: C-2225r2_chk
Ensure the pam_console.so module is not configured in any files in /etc/pam.d by: # cd /etc/pam.d # grep pam_console.so * Or # ls -la /etc/security/console.perms If either the pam_console.so entry or the file /etc/security/console.perms is found then this is a finding.
Fix: F-4257r3_fix
Configure PAM to not grant sole access of administrative privileges to the first user logged in at the console. Identify any instances of pam_console. # cd /etc/pam.d # grep pam_console.so * For any files containing an un-commented reference to pam_console.so, edit the file and remove or comment out the reference. Remove the console.perms file if it exists: # rm /etc/security/console.perms
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN002860
- Vuln IDs
-
- V-4357
- Rule IDs
-
- SV-37945r1_rule
Checks: C-37230r1_chk
Check for any crontab entries that rotate audit logs. Procedure: # crontab -l If such a cron job is found, this is not a finding. Otherwise, query the SA. If there is a process automatically rotating audit logs, this is not a finding. If the SA manually rotates audit logs, this is a finding, because if the SA is not there, it will not be accomplished. If the audit output is not archived daily, to tape or disk, this is a finding. This can be ascertained by looking at the audit log directory and, if more than one file is there, or if the file does not have today's date, this is a finding.
Fix: F-32436r1_fix
Configure a cron job or other automated process to rotate the audit logs on a daily basis.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003200
- Vuln IDs
-
- V-4358
- Rule IDs
-
- SV-27362r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24608r1_fix
Change the mode of the cron.deny file. # chmod 0600 /etc/cron.deny
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN003220
- Vuln IDs
-
- V-4360
- Rule IDs
-
- SV-37489r1_rule
Checks: C-36148r1_chk
Determine if there are any crontabs by viewing a long listing of the directory. If there are crontabs, examine them to determine what cron jobs exist. Check for any programs specifying an umask more permissive than 077: Procedure: # ls -lL /var/spool/cron # ls -lL /etc/cron.d /etc/cron.daily /etc/cron.hourly /etc/cron.monthly /etc/cron.weekly or # ls -lL /etc/cron.*|grep -v deny # cat <crontab file> # grep umask <cron program> If there are no cron jobs present, this vulnerability is not applicable. If any cron job contains an umask more permissive than 077, this is a finding.
Fix: F-31397r1_fix
Edit cron script files and modify the umask to 077.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003240
- Vuln IDs
-
- V-4361
- Rule IDs
-
- SV-27369r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24614r1_fix
# chown root /etc/cron.allow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003400
- Vuln IDs
-
- V-4364
- Rule IDs
-
- SV-37521r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31433r1_fix
Change the mode of the "at" directory to 0755. Procedure: # chmod 0755 <at directory>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003420
- Vuln IDs
-
- V-4365
- Rule IDs
-
- SV-37527r2_rule
Checks: C-36186r2_chk
Check the ownership of the "at" directory: Procedure: # ls -ld /var/spool/at If the directory is not owned by root, sys, bin, daemon, or cron, this is a finding.
Fix: F-31441r1_fix
Change the owner of the "at" directory to root, bin, sys, or system. Procedure: # chown <root or other system account> <"at" directory>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003440
- Vuln IDs
-
- V-4366
- Rule IDs
-
- SV-37531r1_rule
Checks: C-36190r1_chk
Determine what "at" jobs exist on the system. Procedure: # ls /var/spool/at If there are no "at" jobs present, this is not applicable. Determine if any of the "at" jobs or any scripts referenced execute the "umask" command. Check for any umask setting more permissive than 077. # grep umask <at job or referenced script> If any "at" job or referenced script sets umask to a value more permissive than 077, this is a finding.
Fix: F-31445r1_fix
Edit "at" jobs or referenced scripts to remove "umask" commands that set umask to a value less restrictive than 077.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003460
- Vuln IDs
-
- V-4367
- Rule IDs
-
- SV-37533r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31448r1_fix
Change the owner of the at.allow file. # chown root /etc/at.allow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003480
- Vuln IDs
-
- V-4368
- Rule IDs
-
- SV-37535r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31451r1_fix
Change the owner of the at.deny file. # chown root /etc/at.deny
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003960
- Vuln IDs
-
- V-4369
- Rule IDs
-
- SV-37463r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31373r1_fix
Change the owner of the traceroute command to root. Example: # chown root /bin/traceroute
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003980
- Vuln IDs
-
- V-4370
- Rule IDs
-
- SV-37464r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31375r1_fix
Change the group-owner of the traceroute command to root. Procedure: # chgrp root /bin/traceroute
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004000
- Vuln IDs
-
- V-4371
- Rule IDs
-
- SV-37465r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31376r1_fix
Change the mode of the traceroute command. # chmod 0700 /bin/traceroute
- RMF Control
- AC-6
- Severity
- H
- CCI
- CCI-000225
- Version
- GEN004220
- Vuln IDs
-
- V-4382
- Rule IDs
-
- SV-37469r1_rule
Checks: C-36135r3_chk
Look in the root account home directory for a .mozilla directory. If none exists, this is not a finding. If there is one, verify with the root users and the IAO the intent of the browsing. If the browsing is not limited to authorized local services administration, this is a finding.
Fix: F-31380r1_fix
Enforce policy requiring administrative accounts use web browsers only for local service administration.
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN004560
- Vuln IDs
-
- V-4384
- Rule IDs
-
- SV-37505r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31414r1_fix
Ensure sendmail or Postfix has been configured to mask the version information. Procedure for sendmail: Change the O SmtpGreetingMessage line in the /etc/mail/sendmail.cf file as noted below: O SmtpGreetingMessage=$j Sendmail $v/$Z; $b change it to: O SmtpGreetingMessage= Mail Server Ready ; $b for Postfix: Examine the "smtpd_banner" line of /etc/postfix/main.conf and remove any "$mail_version" entry on it or comment the entire "smtpd_banner" line to use the default value which does not display the version information.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN004580
- Vuln IDs
-
- V-4385
- Rule IDs
-
- SV-37506r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31416r2_fix
Disable forwarding for sendmail and remove .forward files from the system Procedure: Edit the /etc/mail/sendmail.mc file to change the ForwardPath entry to a null path by adding the line define(`confFORWARD_PATH',`') rebuild the sendmail.cf file. Remove all .forward files on the system # find / -name .forward -delete
- RMF Control
- AC-6
- Severity
- H
- CCI
- CCI-000225
- Version
- GEN005000
- Vuln IDs
-
- V-4387
- Rule IDs
-
- SV-37549r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31462r1_fix
Configure anonymous FTP accounts to use a non-functional shell. If necessary, edit the /etc/passwd file to remove any functioning shells associated with the ftp account and replace them with non-functioning shells, such as /dev/null.
- RMF Control
- SC-32
- Severity
- M
- CCI
- CCI-001208
- Version
- GEN005380
- Vuln IDs
-
- V-4392
- Rule IDs
-
- SV-37708r1_rule
Checks: C-36903r1_chk
Ask the SA if this is an NMS server. If it is an NMS server, then ask what other applications run on it. If there is anything other than network management software and DBMS software used only for the storage and inquiry of NMS data, this is a finding.
Fix: F-32073r1_fix
Ensure only authorized software is loaded on a designated NMS server. Authorized software is limited to the NMS software itself, a database management system for the NMS server if necessary, and network management software.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005400
- Vuln IDs
-
- V-4393
- Rule IDs
-
- SV-37707r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32061r1_fix
Use the chown command to set the owner to root. # chown root /etc/syslog.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005420
- Vuln IDs
-
- V-4394
- Rule IDs
-
- SV-37711r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32088r1_fix
Procedure: # chgrp root /etc/syslog.conf
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005460
- Vuln IDs
-
- V-4395
- Rule IDs
-
- SV-37812r1_rule
Checks: C-37014r1_chk
Examine the syslog.conf file for any references to remote log hosts. # grep -v "^#" /etc/syslog.conf | grep '@' Destination locations beginning with an '@' represent log hosts. If the log host name is a local alias such as "loghost", consult the /etc/hosts or other name databases as necessary to obtain the canonical name or address for the log host. Determine if the host referenced is a log host documented using site-defined procedures. If an undocumented log host is referenced, this is a finding.
Fix: F-32281r1_fix
Remove or document the referenced undocumented log host.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005560
- Vuln IDs
-
- V-4397
- Rule IDs
-
- SV-37918r1_rule
Checks: C-37145r1_chk
Check the system for an IPv4 default route. If the system is a VM host and acts as a router solely for the benefit of its client systems, then this rule is not applicable. Procedure: # netstat -r |grep default If a default route is not defined, this is a finding.
Fix: F-32410r1_fix
Set a default gateway for IPv4.
- RMF Control
- SC-32
- Severity
- M
- CCI
- CCI-001208
- Version
- GEN005580
- Vuln IDs
-
- V-4398
- Rule IDs
-
- SV-37924r1_rule
Checks: C-37160r1_chk
If the system is a VM host and acts as a router solely for the benefit of its client systems, then this rule is not applicable. Ask the SA if the system is a designated router. If it is not, this is not applicable. Check the system for non-routing network services. Procedure: # netstat -a | grep -i listen # ps -ef If non-routing services, including Web servers, file servers, DNS servers, or applications servers, but excluding management services such as SSH and SNMP, are running on the system, this is a finding.
Fix: F-32418r1_fix
Ensure only authorized software is loaded on a designated router. Authorized software will be limited to the most current version of routing protocols and SSH for system administration purposes.
- RMF Control
- AC-17
- Severity
- H
- CCI
- CCI-001436
- Version
- GEN006380
- Vuln IDs
-
- V-4399
- Rule IDs
-
- SV-37739r1_rule
Checks: C-36936r1_chk
If the system does not use NIS or NIS+, this is not applicable. Check if NIS or NIS+ is implemented using UDP. Procedure: # rpcinfo -p | grep yp | grep udp If NIS or NIS+ is implemented using UDP, this is a finding.
Fix: F-32201r1_fix
Configure the system to not use UDP for NIS and NIS+. Consult vendor documentation for the required procedure.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN002020
- Vuln IDs
-
- V-4427
- Rule IDs
-
- SV-37437r1_rule
Checks: C-36055r1_chk
Locate and examine all r-commands access control files. Procedure: # find / -name .rhosts # more /<directorylocation>/.rhosts # find / -name .shosts # more /<directorylocation>/.shosts # find / -name hosts.equiv # more /<directorylocation>/hosts.equiv # find / -name shosts.equiv # more /<directorylocation>/shosts.equiv If any .rhosts, .shosts, hosts.equiv, or shosts.equiv file contains other than host-user pairs, this is a finding.
Fix: F-31299r1_fix
If possible, remove the .rhosts, .shosts, hosts.equiv, and shosts.equiv files. If the files are required, remove any content from the files except for necessary host-user pairs.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002060
- Vuln IDs
-
- V-4428
- Rule IDs
-
- SV-37385r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31316r1_fix
Ensure the permission for these files is set to 600 or more restrictive and their owner is root or the same as the owner of the home directory in which they reside. Procedure: # chmod 600 /etc/hosts.equiv # chmod 600 /etc/ssh/shosts.equiv # chown root /etc/hosts.equiv # chown root /etc/ssh/shosts.equiv # find / -name .rhosts # chmod 600 /<home directory>/.rhosts # chown <home directory owner> <home directory>/.rhosts # find / -name .shosts # chmod 600 <directory location>/.shosts # chown <home directory owner> <home directory>/.shosts # find / -name .netrc # chmod 600 <directory location>/.netrc # chown <home directory owner> <home directory>/.netrc
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003260
- Vuln IDs
-
- V-4430
- Rule IDs
-
- SV-27374r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24620r1_fix
# chown root /etc/cron.deny
- RMF Control
- AC-17
- Severity
- H
- CCI
- CCI-000068
- Version
- GEN003820
- Vuln IDs
-
- V-4687
- Rule IDs
-
- SV-37441r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31359r1_fix
Edit /etc/xinetd.d/rsh and set "disable=yes".
- RMF Control
- AC-17
- Severity
- H
- CCI
- CCI-001435
- Version
- GEN003840
- Vuln IDs
-
- V-4688
- Rule IDs
-
- SV-37443r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31361r1_fix
Edit /etc/xinetd.d/rexec and set "disable=yes"
- RMF Control
- SI-2
- Severity
- H
- CCI
- CCI-001230
- Version
- GEN004600
- Vuln IDs
-
- V-4689
- Rule IDs
-
- SV-37507r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31417r1_fix
Obtain and install a newer version of the SMTP service software (sendmail or Postfix) from RedHat.
- RMF Control
- CM-6
- Severity
- H
- CCI
- CCI-000366
- Version
- GEN004620
- Vuln IDs
-
- V-4690
- Rule IDs
-
- SV-37508r1_rule
Checks: C-36167r2_chk
Check for an enabled "debug" command provided by the SMTP service. Procedure: # telnet localhost 25 debug If the command does not return a 500 error code of "command unrecognized" or a 550 error code of "access denied", this is a finding. The RHEL distribution ships with sendmail Version 8.13.8 which is not vulnerable. This should never be a finding.
Fix: F-31418r1_fix
Obtain and install a newer version of the SMTP service software (sendmail or Postfix) from RedHat.
- RMF Control
- SI-2
- Severity
- H
- CCI
- CCI-001230
- Version
- GEN004640
- Vuln IDs
-
- V-4691
- Rule IDs
-
- SV-37509r1_rule
Checks: C-36169r1_chk
Check the SMTP service for an active "decode" command. Procedure: # telnet localhost 25 decode If the command does not return a 500 error code of "command unrecognized", this is a finding.
Fix: F-31420r1_fix
Disable mail aliases for decode and uudecode. If the /etc/aliases or /usr/lib/aliases (mail alias) file contains entries for these programs, remove them or disable them by placing "#" at the beginning of the line, and then executing the new aliases command. For more information on mail aliases, refer to the man page for aliases. Disabled aliases would be similar to these examples: # decode: |/usr/bin/uudecode # uudecode: |/usr/bin/uuencode -d
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN004660
- Vuln IDs
-
- V-4692
- Rule IDs
-
- SV-37510r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31421r1_fix
Rebuild /etc/mail/sendmail.cf with the "noexpn" Privacy Flag set. Procedure: Edit /etc/mail/sendmail.mc resetting the Privacy Flags to the default: define('confPRIVACYFLAGS', 'authwarnings,novrfy,noexpn,restrictqrun')dnl Rebuild the sendmail.cf file with: # make -C /etc/mail Restart the sendmail service. # service sendmail restart
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN004680
- Vuln IDs
-
- V-4693
- Rule IDs
-
- SV-37511r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31422r1_fix
Add the "novrfy" flag to your sendmail in /etc/mail/sendmail.cf. Procedure: Edit the definition of "confPRIVACY_FLAGS" in /etc/mail/sendmail.mc to include "novrfy". Rebuild the sendmail.cf file with: # make -C /etc/mail Restart the sendmail service. # service sendmail restart
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN004700
- Vuln IDs
-
- V-4694
- Rule IDs
-
- SV-37513r1_rule
Checks: C-36172r3_chk
Log into the sendmail server with telnet and test the "wiz" command. Procedure: # telnet localhost 25 Trying 127.0.0.1... Connected to locahost.localdomain (127.0.0.1). Escape character ... Once the telnet greeting is complete type: wiz If you do not get a "Command unrecognized: " message, this is a finding.
Fix: F-31423r2_fix
If the WIZ command exists on sendmail then the version of sendmail is archaic and should be replaced with the latest version from RedHat. WIZ is not available on any sendmail distribution of RHEL. However, if the WIZ command is enabled on sendmail, it should be disabled by adding this line to the sendmail.cf configuration file (note that it must be typed in uppercase): OW* For the change to take effect, kill the sendmail process, refreeze the sendmail.cf file, and restart the sendmail process.
- RMF Control
- AC-6
- Severity
- H
- CCI
- CCI-000225
- Version
- GEN005140
- Vuln IDs
-
- V-4695
- Rule IDs
-
- SV-37676r1_rule
Checks: C-36864r2_chk
Determine if the TFTP daemon is active. # chkconfig --list | grep tftp If TFTP is found enabled ("on") and not documented using site-defined procedures, it is a finding.
Fix: F-31806r1_fix
Document or Disable the TFTP daemon. If the TFTP daemon is necessary on the system, document and justify its usage for approval from the IAO. If the TFTP daemon is not necessary on the system, turn it off. # chkconfig tftp off # service xinetd restart
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001436
- Version
- GEN005280
- Vuln IDs
-
- V-4696
- Rule IDs
-
- SV-37688r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31895r1_fix
# chkconfig uucp off # service uucp stop # service xinetd restart
- RMF Control
- AC-6
- Severity
- H
- CCI
- CCI-000225
- Version
- GEN005200
- Vuln IDs
-
- V-4697
- Rule IDs
-
- SV-37683r1_rule
Checks: C-36872r2_chk
If Xwindows is not used on the system, this is not applicable. Check the output of the "xhost" command from an X terminal. Procedure: # xhost If the output reports access control is enabled (and possibly lists the hosts able to receive X window logins), this is not a finding. If the xhost command returns a line indicating access control is disabled, this is a finding. Note: It may be necessary to define the display if the command reports it cannot open the display. Procedure: $ DISPLAY=MachineName:0.0; export DISPLAY MachineName may be replaced with an Internet Protocol Address. Repeat the check procedure after setting the display.
Fix: F-31847r1_fix
If using an xhost-type authentication the "xhost -" command can be used to remove current trusted hosts and then selectively allow only trusted hosts to connect with "xhost +" commands. A cryptographically secure authentication, such as provided by the xauth program, is always preferred. Refer to your X11 server's documentation for further security information.
- RMF Control
- AC-4
- Severity
- L
- CCI
- CCI-001551
- Version
- GEN003860
- Vuln IDs
-
- V-4701
- Rule IDs
-
- SV-37445r1_rule
Checks: C-36117r1_chk
# grep disable /etc/xinetd.d/finger If the finger service is not disabled, this is a finding.
Fix: F-31363r1_fix
Edit /etc/xinetd.d/finger and set "disable=yes"
- RMF Control
- IA-4
- Severity
- M
- CCI
- CCI-000787
- Version
- GEN004840
- Vuln IDs
-
- V-4702
- Rule IDs
-
- SV-37528r1_rule
Checks: C-36187r1_chk
Use the command "ftp" to connect the system's FTP service. Attempt to log into this host with a user name of anonymous and a password of guest (also try the password of guest@mail.com). If the logon is not successful, this check is Not Applicable. Ask the SA if the system is located on a DMZ network. If the system is not located on a DMZ network, this is a finding.
Fix: F-31442r1_fix
Remove anonymous ftp capability or move the system to a DMZ network.
- RMF Control
- SI-2
- Severity
- H
- CCI
- CCI-001230
- Version
- GEN000100
- Vuln IDs
-
- V-11940
- Rule IDs
-
- SV-27049r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-11211r2_fix
Upgrade to a supported version of the operating system.
- RMF Control
- RA-5
- Severity
- M
- CCI
- CCI-001069
- Version
- GEN000220
- Vuln IDs
-
- V-11945
- Rule IDs
-
- SV-38178r1_rule
Checks: C-37562r2_chk
Determine if there is an automated job, scheduled to run weekly or more frequently, to run the file integrity tool to check for unauthorized additions to system libraries. The check can be done using Advanced Intrusion Detection Environment (AIDE) which is part of the Red Hat Enterprise Linux (RHEL) distribution. Other file integrity software may be used but must be checked manually. Procedure: Check the root crontab (crontab -l) and the global crontabs in /etc/crontab, /etc/cron.d/* for the presence of an "aide" job to run at least weekly, which should have asterisks (*) in columns 3, 4, and 5. Check the weekly cron directory (/etc/cron.weekly) for any script running "aide --check" or "aide -C" or simply "aide". If there is not, this is a finding. NOTE: For MAC I systems, increase the frequency to daily.
Fix: F-32806r2_fix
Establish an automated job, scheduled to run weekly or more frequently, to run "aide --check" which is the file integrity tool to check for unauthorized system libraries or binaries. NOTE: For MAC I systems, increase the frequency to daily.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000340
- Vuln IDs
-
- V-11946
- Rule IDs
-
- SV-37155r1_rule
Checks: C-35863r2_chk
Check the UID assignments for all accounts. # cut -d: -f 1,3 /etc/passwd | egrep ":[1-4][0-9]{2}$|:[0-9]{1,2}$" Confirm all accounts with a UID of 499 and below are used by a system account. If a UID reserved for system accounts (0 - 499) is used by a non-system account, then this is a finding.
Fix: F-31119r1_fix
Change the UID numbers for non-system accounts with reserved UIDs (those less or equal to 499).
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000205
- Version
- GEN000580
- Vuln IDs
-
- V-11947
- Rule IDs
-
- SV-37260r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31206r1_fix
Edit "/etc/pam.d/system-auth" to include the line: password required pam_cracklib.so minlen=14 prior to the "password include system-auth-ac" line.
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000192
- Version
- GEN000600
- Vuln IDs
-
- V-11948
- Rule IDs
-
- SV-41826r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-35446r1_fix
Edit "/etc/pam.d/system-auth" to include the line: password required pam_cracklib.so ucredit=-1 prior to the "password include system-auth-ac" line.
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000194
- Version
- GEN000620
- Vuln IDs
-
- V-11972
- Rule IDs
-
- SV-37281r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31227r1_fix
Edit "/etc/pam.d/system-auth" to include the line: password required pam_cracklib.so dcredit=-1 prior to the "password include system-auth-ac" line.
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-001619
- Version
- GEN000640
- Vuln IDs
-
- V-11973
- Rule IDs
-
- SV-37287r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31235r1_fix
Edit "/etc/pam.d/system-auth" to include the line: password required pam_cracklib.so ocredit=-1 prior to the "password include system-auth-ac" line.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000680
- Vuln IDs
-
- V-11975
- Rule IDs
-
- SV-37294r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31243r1_fix
Edit "/etc/pam.d/system-auth" to include the line: password required pam_cracklib.so maxrepeat=3 prior to the "password include system-auth-ac" line.
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000180
- Version
- GEN000700
- Vuln IDs
-
- V-11976
- Rule IDs
-
- SV-37298r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31246r1_fix
Set the max days field to 60 for all user accounts. # passwd -x 60 <user>
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000199
- Version
- GEN000740
- Vuln IDs
-
- V-11977
- Rule IDs
-
- SV-37302r1_rule
Checks: C-35997r2_chk
Ask the SA if there are any automated processing accounts on the system. If there are automated processing accounts on the system, ask the SA if the passwords for those automated accounts are changed at least once a year or are locked. If SA indicates passwords for automated processing accounts are not changed once per year or are not locked, this is a finding.
Fix: F-31249r2_fix
Implement or establish procedures to change the passwords of automated processing accounts at least once per year or lock them.
- RMF Control
- IA-2
- Severity
- M
- CCI
- CCI-000770
- Version
- GEN001020
- Vuln IDs
-
- V-11979
- Rule IDs
-
- SV-37377r2_rule
Checks: C-36064r5_chk
Check if root is used for direct logins. Procedure: # last root | grep -v reboot Direct logins are indicated by the presence of a terminal or pseudo-terminal ID and/or X display name in the output of the last command. If any direct login records for root are listed, this is a finding.
Fix: F-31308r1_fix
Enforce policy requiring all root account access is attained by first logging into a user account and then becoming root preferably through the use of "sudo" which provides traceability to the command level. If that is not workable then using "su" to access the root account will provide traceability to the login user.
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN001060
- Vuln IDs
-
- V-11980
- Rule IDs
-
- SV-37378r1_rule
Checks: C-36065r1_chk
Check the log files to determine if access to the root account is being logged. Procedure: Examine /etc/syslog.conf to confirm the location to which "authpriv" messages will be directed. The default syslog.conf uses /var/log/messages and /var/log/secure but this needs to be confirmed. # grep @ /etc/syslog.conf If a line starting with "*.*" is returned then all syslog messages will be sent to system whose address appears after the "@". In this case syslog may or may not be configured to also log "authpriv" messages locally. # grep authpriv /etc/syslog.conf If any lines are returned which do not start with "#" the "authpriv" messages will be sent to the indicated files or remote systems. Try to "su -" and enter an incorrect password. If there are no records indicating the authentication failure, this is a finding.
Fix: F-31309r1_fix
Troubleshoot the system logging configuration to provide for logging of root account login attempts. Procedure: Edit /etc/syslog.conf to make sure "authpriv.*" messages are directed to a file or remote system. Examine /etc/audit/audit.rules to ensure user authentication messages have not been specifically excluded. There remove any entries that correspond to: -a exclude,never -Fmsgtype=USER_START -a exclude,never -Fmsgtype=USER_LOGIN -a exclude,never -Fmsgtype=USER_AUTH -a exclude,never -Fmsgtype=USER_END -a exclude,never -Fmsgtype=USER_ACCT
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001720
- Vuln IDs
-
- V-11981
- Rule IDs
-
- SV-37275r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31223r1_fix
Change the mode of the global initialization file(s) to 0644. # chmod 0644 <global initialization file>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001740
- Vuln IDs
-
- V-11982
- Rule IDs
-
- SV-37283r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31229r1_fix
Change the ownership of global initialization files with incorrect ownership. Procedure: # chown root <global initialization files> or: # ls etc/bashrc /etc/csh.cshrc /etc/csh.login /etc/csh.logout /etc/environment /etc/ksh.kshrc /etc/profile /etc/suid_profile /etc/profile.d/* 2>null|xargs stat -L -c %U:%n|egrep -v "^root"|cut -d: -f2|xargs chown root will set the owner of all files not currently owned by root to root.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001760
- Vuln IDs
-
- V-11983
- Rule IDs
-
- SV-37285r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31232r1_fix
Change the group ownership of the global initialization file(s) with incorrect group ownership. Procedure: # chgrp root <global initialization file> or: # ls -lL /etc/bashrc /etc/csh.cshrc /etc/csh.login /etc/csh.logout /etc/environment /etc/ksh.kshrc /etc/profile /etc/suid_profile /etc/profile.d/* 2>null|sed "s/^[^\/]*//"|xargs stat -L -c %G:%n|egrep -v "^(root|sys|bin|other):"|cut -d: -f2|xargs chgrp root will set the group of all files not currently owned by an approved group to root.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001820
- Vuln IDs
-
- V-11984
- Rule IDs
-
- SV-37300r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31248r1_fix
Change the ownership of skeleton files with incorrect mode: # chown root <skeleton file> or # ls -L /etc/skel|xargs stat -L -c %U:%n|egrep -v "^(root|bin):"|cut -d: -f2|chown root will change all files not owned by root or bin to root.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001840
- Vuln IDs
-
- V-11985
- Rule IDs
-
- SV-37420r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31187r1_fix
Edit the global initialization file(s) with PATH variables containing relative paths. Edit the file and remove the relative path from the PATH variable.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001900
- Vuln IDs
-
- V-11986
- Rule IDs
-
- SV-37432r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31242r2_fix
Edit the local initialization file and remove the relative path entry from the executable search path variable. If this is not feasible, justify and document the necessity of having the relative path for a specific application.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001980
- Vuln IDs
-
- V-11987
- Rule IDs
-
- SV-37435r1_rule
Checks: C-36048r1_chk
Check system configuration files for plus (+) entries. Procedure: # find / -name .rhosts # grep + /<directorylocation>/.rhosts # find / -name .shosts # grep + /<directorylocation>/.shosts # find / -name hosts.equiv # grep + /<directorylocation>/hosts.equiv # find / -name shosts.equiv # grep + /<directorylocation>/shosts.equiv # grep + /etc/passwd # grep + /etc/shadow # grep + /etc/group If the .rhosts, .shosts, hosts.equiv, shosts.equiv, /etc/passwd, /etc/shadow, and/or /etc/group files contain a plus (+) and do not define entries for NIS+ netgroups, this is a finding.
Fix: F-31292r1_fix
Edit the .rhosts, .shosts, hosts.equiv, shosts.equiv, /etc/passwd, /etc/shadow, and/or /etc/group files and remove entries containing a plus (+).
- RMF Control
- CM-6
- Severity
- H
- CCI
- CCI-000366
- Version
- GEN002040
- Vuln IDs
-
- V-11988
- Rule IDs
-
- SV-37370r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31301r1_fix
Remove all the r-commands access control files. Procedure: # find / -name .rhosts -exec rm {} \; # find / -name .shosts -exec rm {} \; # find / -name hosts.equiv -exec rm {} \; # find / -name shosts.equiv -exec rm {} \;
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN002100
- Vuln IDs
-
- V-11989
- Rule IDs
-
- SV-37389r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31319r1_fix
Edit the file(s) in /etc/pam.d referencing the rhosts_auth module, and remove the references to the rhosts_auth module.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002540
- Vuln IDs
-
- V-11990
- Rule IDs
-
- SV-37893r1_rule
Checks: C-37119r2_chk
Check the group-ownership of public directories. Procedure: # find / -type d -perm -1002 -exec ls -ld {} \; If any public directory is not group-owned by root, sys, bin, or an application group, this is a finding.
Fix: F-32387r1_fix
Change the group-ownership of the public directory. Procedure: # chgrp root /tmp (Replace root with a different system group and/or /tmp with a different public directory as necessary.)
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003040
- Vuln IDs
-
- V-11994
- Rule IDs
-
- SV-37392r1_rule
Checks: C-36076r1_chk
List all crontabs on the system. # ls -lL /var/spool/cron # ls -lL /etc/cron.d /etc/crontab /etc/cron.daily /etc/cron.hourly /etc/cron.monthly /etc/cron.weekly or # ls -lL /etc/cron*|grep -v deny If any crontab is not owned by root or the creating user, this is a finding.
Fix: F-31322r1_fix
Change the crontab owner to root or the crontab creator. # chown root <crontab file> or # chown <user> <crontab file>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003060
- Vuln IDs
-
- V-11995
- Rule IDs
-
- SV-27338r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31374r1_fix
Remove default system accounts (such as bin, sys, adm, or others, traditionally UID less than 500) from the cron.allow file if it exists, or add those accounts to the cron.deny file.
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN003500
- Vuln IDs
-
- V-11996
- Rule IDs
-
- SV-37546r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31460r1_fix
Edit /etc/security/limits.conf and set a hard limit for "core" to 0 for all users.
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN003520
- Vuln IDs
-
- V-11997
- Rule IDs
-
- SV-37570r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31608r1_fix
Change the owner of the kernel core dump data directory to root. # chown root /var/crash
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN003540
- Vuln IDs
-
- V-11999
- Rule IDs
-
- SV-27414r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24686r1_fix
Examine /etc/sysctl.conf for "kernel.exec-shield" and "kernel.randomize_va_space" entries and if found remove them. The system default of "1" enables these modules.
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN003600
- Vuln IDs
-
- V-12002
- Rule IDs
-
- SV-29795r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31612r1_fix
Configure the system to not accept source-routed IPv4 packets. Edit /etc/sysctl.conf and add a setting for "net.ipv4.conf.all.accept_source_route=0" and "net.ipv4.conf.default.accept_source_route=0". Reload the sysctls. Procedure: # sysctl -p
- RMF Control
- SC-32
- Severity
- L
- CCI
- CCI-001208
- Version
- GEN003620
- Vuln IDs
-
- V-12003
- Rule IDs
-
- SV-37640r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31675r1_fix
Migrate the /home (or equivalent) path onto a separate file system.
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN003660
- Vuln IDs
-
- V-12004
- Rule IDs
-
- SV-37404r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31333r1_fix
Edit /etc/syslog.conf and add local log destinations for "authpriv.*", "authpriv.debug" or "authpriv.info".
- RMF Control
- CM-2
- Severity
- M
- CCI
- CCI-000305
- Version
- GEN003700
- Vuln IDs
-
- V-12005
- Rule IDs
-
- SV-27424r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24696r1_fix
# service xinetd stop ; chkconfig xinetd off
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN004540
- Vuln IDs
-
- V-12006
- Rule IDs
-
- SV-37504r3_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31413r2_fix
To disable the SMTP HELP command, clear the Sendmail help file. # echo > /etc/mail/helpfile
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN004800
- Vuln IDs
-
- V-12010
- Rule IDs
-
- SV-37515r1_rule
Checks: C-36174r3_chk
Perform the following to determine if unencrypted FTP is enabled: # chkconfig --list gssftp # chkconfig --list vsftpd If any of these services are found, ask the SA if these services are encrypted. If they are not, this is a finding.
Fix: F-31425r2_fix
Disable the FTP daemons. Procedure: # chkconfig gssftp off # chkconfig vsftpd off
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005040
- Vuln IDs
-
- V-12011
- Rule IDs
-
- SV-37555r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31466r1_fix
Edit the initialization files for the ftp user and set the umask to 077. Procedure: For gssftp: Modify the /etc/xinetd.d/gssftp file adding "-u 077" to the server_args entry. For vsftp: Modify the "/etc/vsftpd/vsftpd.conf" setting "local_umask" and "anon_umask" to 077.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005180
- Vuln IDs
-
- V-12014
- Rule IDs
-
- SV-37679r1_rule
Checks: C-36866r1_chk
Check the file permissions for the .Xauthority files. Procedure: # ls -la |egrep "(\.Xauthority|\.xauth)" If the file mode is more permissive than 0600, this is finding.
Fix: F-31822r1_fix
Change the mode of the .Xauthority files. Procedure: # chmod 0600 .Xauthority
- RMF Control
- CM-2
- Severity
- M
- CCI
- CCI-000297
- Version
- GEN005220
- Vuln IDs
-
- V-12016
- Rule IDs
-
- SV-37684r1_rule
Checks: C-36875r1_chk
Determine if the X server is running. Procedure: # ps -ef |grep X Determine if xauth is being used. Procedure: # xauth xauth> list If the above command sequence does not show any host other than the localhost, then xauth is not being used. Search the system for an X*.hosts file, where "*" is a display number used to limit X window connections. If no files are found, X*.hosts files are not being used. If the X*.hosts files contain any unauthorized hosts, this is a finding. If both xauth and X*.hosts files are not being used, this is a finding.
Fix: F-31858r1_fix
Create an X*.hosts file, where "*" is a display number used to limit X window connections. Add the list of authorized X clients to the file.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005240
- Vuln IDs
-
- V-12017
- Rule IDs
-
- SV-37685r1_rule
Checks: C-36877r1_chk
Check the X window system access is limited to authorized clients. Procedure: # xauth xauth> list Ask the SA if the clients listed are authorized. If any are not, this is a finding.
Fix: F-31867r1_fix
Remove unauthorized clients from the xauth configuration. # xauth remove <display name>
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001436
- Version
- GEN005260
- Vuln IDs
-
- V-12018
- Rule IDs
-
- SV-37686r1_rule
Checks: C-36878r1_chk
Determine if the X window system is running. Procedure: # ps -ef |grep Xorg Ask the SA if the X window system is an operational requirement. If it is not, this is a finding.
Fix: F-31878r1_fix
Disable the X Windows server on the system.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005360
- Vuln IDs
-
- V-12019
- Rule IDs
-
- SV-37703r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32028r1_fix
Change the owner of the snmpd.conf file to root. Procedure: # chown root <snmpd.conf file>
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005440
- Vuln IDs
-
- V-12020
- Rule IDs
-
- SV-37810r1_rule
Checks: C-37010r1_chk
Ask the SA if the loghost server is collecting data for hosts outside the local enclave. If it is, this is a finding.
Fix: F-32274r1_fix
Configure the hosts outside of the local enclave to not log to this system.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005480
- Vuln IDs
-
- V-12021
- Rule IDs
-
- SV-37813r1_rule
Checks: C-37017r2_chk
Ask the SA if the system is an authorized syslog server. If the system is an authorized syslog server, this is not applicable. Determine if the system's syslog service is configured to accept remote messages. # ps -ef | grep syslogd If the '-r' option is present, the system is configured to accept remote syslog messages, and this is a finding.
Fix: F-32284r1_fix
Edit /etc/sysconfig/syslog to removing the '-r' in SYSLOGD_OPTIONS. Restart the syslogd service.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005540
- Vuln IDs
-
- V-12022
- Rule IDs
-
- SV-37913r1_rule
Checks: C-37139r1_chk
Check the TCP wrappers configuration files to determine if sshd is configured to use TCP wrappers. Procedure: # grep sshd /etc/hosts.deny # grep sshd /etc/hosts.allow If no entries are returned, the TCP wrappers are not configured for sshd, this is a finding.
Fix: F-32407r1_fix
Add appropriate IP restrictions for SSH to the /etc/hosts.deny and/or /etc/hosts.allow files.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005600
- Vuln IDs
-
- V-12023
- Rule IDs
-
- SV-37929r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32422r1_fix
Edit "/etc/sysctl.conf" and set net.ipv4.ip_forward to "0". Restart the system or run "sysctl -p" to make the change take effect.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN006000
- Vuln IDs
-
- V-12024
- Rule IDs
-
- SV-37862r1_rule
Checks: C-37073r1_chk
If an IM client is installed, ask the SA if it has access to any public domain IM servers. If it does have access to public servers, this is a finding.
Fix: F-32341r1_fix
Uninstall the IM client from the system, or configure the client to only connect to DoD-approved IM services.
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001436
- Version
- GEN006040
- Vuln IDs
-
- V-12025
- Rule IDs
-
- SV-37865r1_rule
Checks: C-37078r1_chk
Ask the SA if any peer-to-peer file-sharing applications are installed. Some examples of these applications include: - Napster - Kazaa - ARES - Limewire - IRC Chat Relay - BitTorrent If any of these applications are installed, this is a finding.
Fix: F-32351r1_fix
Uninstall the peer-to-peer file sharing application(s) from the system.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN006420
- Vuln IDs
-
- V-12026
- Rule IDs
-
- SV-37743r1_rule
Checks: C-36940r2_chk
Check the domain name for NIS maps. Procedure: # domainname If the name returned is simple to guess, such as the organization name, building or room name, etc., this is a finding. If the system does not use NIS, this is not applicable.
Fix: F-32205r1_fix
Change the NIS domainname to a value difficult to guess. Consult vendor documentation for the required procedure.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN006560
- Vuln IDs
-
- V-12028
- Rule IDs
-
- SV-37747r1_rule
Checks: C-36944r1_chk
For each security tool on the system, determine if the tool is configured to notify the IAO and SA of any detected security problem. If such notifications are not configured, this is a finding.
Fix: F-32209r1_fix
Configure the security tools on the system to notify the IAO and SA when any security issues are detected.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN006620
- Vuln IDs
-
- V-12030
- Rule IDs
-
- SV-37758r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32220r1_fix
Edit the "/etc/hosts.all" and "/etc/hosts.deny" files to configure access restrictions.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00620
- Vuln IDs
-
- V-12038
- Rule IDs
-
- SV-37340r1_rule
Checks: C-8001r2_chk
Check /etc/securetty group ownership: # ls -lL /etc/securetty If /etc/securetty is not group owned by root, sys, or bin, then this is a finding.
Fix: F-11295r2_fix
Change the group-owner of /etc/securetty to root, sys, or bin. Example: # chgrp root /etc/securetty
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00640
- Vuln IDs
-
- V-12039
- Rule IDs
-
- SV-37341r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-11296r2_fix
Change the owner of the /etc/securetty file to root. Procedure: # chown root /etc/securetty
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00660
- Vuln IDs
-
- V-12040
- Rule IDs
-
- SV-37342r3_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31277r3_fix
Change the mode of the /etc/securetty file to 0600. Procedure: # chmod 0600 /etc/securetty
- RMF Control
- CM-2
- Severity
- M
- CCI
- CCI-000305
- Version
- GEN003865
- Vuln IDs
-
- V-12049
- Rule IDs
-
- SV-37446r1_rule
Checks: C-36118r2_chk
Determine if any network analysis tools are installed. Procedure: # find / -name ethereal # find / -name wireshark # find / -name tshark # find / -name nc # find / -name tcpdump # find / -name snoop If any network analysis tools are found, this is a finding
Fix: F-31364r1_fix
Remove each network analysis tool binary from the system. Remove package items with a package manager, others remove the binary directly. Procedure: Find the binary file: # find / -name <Item to be removed> Find the package, if any, to which it belongs: # rpm -qf <binary file> Remove the package if it does not also include other software: # rpm -e <package name> or # yum remove <package name> If the item to be removed is not in a package, or the entire package cannot be removed because of other software it provides, remove the item's binary file. # rm <binary file>
- RMF Control
- SI-3
- Severity
- M
- CCI
- CCI-001668
- Version
- GEN006640
- Vuln IDs
-
- V-12765
- Rule IDs
-
- SV-37760r2_rule
Checks: C-36956r2_chk
Check for the existence of a cron job to execute a DoD-approved command-line scan tool daily. Other tools may be available but will have to be manually reviewed if they are installed. In addition, the definitions files should not be older than 7 days. Check if DoD-approved command-line scan tool is scheduled to run: # grep [scan tool] /var/spool/cron/* /etc/cron.d/* /etc/cron.daily/* /etc/cron.hourly/* /etc/cron.monthly/* /etc/cron.weekly/* If a virus scanner is not being run daily and an exception has not been documented with the IAO, this is a finding. Perform the following command to ensure the virus definition signature files are not older than 7 days. # cd <scan tool install directory> # ls -la *.dat If the virus definitions are older than 7 days, this is a finding.
Fix: F-32221r2_fix
Install a DoD-approved command-line virus scan tool, or an appropriate alternative. Ensure the virus signature definition files are no older than 7 days. Configure the system to run a virus scan on altered files dynamically or daily. If daily scans impede operations, justify, document, and obtain IAO approval for alternate scheduling.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000241
- Vuln IDs
-
- V-22290
- Rule IDs
-
- SV-26292r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23444r1_fix
Enable the NTP daemon for continuous synchronization. # service ntpd start ; chkconfig ntpd on OR Add a daily or more frequent cronjob to perform synchronization using ntpdate.
- RMF Control
- AU-8
- Severity
- M
- CCI
- CCI-000160
- Version
- GEN000242
- Vuln IDs
-
- V-22291
- Rule IDs
-
- SV-37412r1_rule
Checks: C-36095r1_chk
Check the root crontab (crontab -l) and the global crontabs in /etc/crontab, /etc/cron.d/*, or scripts in the /etc/cron.daily directory for the presence of an "ntpd -qg" job. If the "ntpd -qg" command is not invoked with at least two external NTP servers listed, this is a finding. Check the NTP daemon configuration for at least two external servers. # grep ^server /etc/ntp.conf | egrep -v '(127.127.1.0|127.127.1.1)' If less than two servers or external reference clocks (127.127.x.x other than 127.127.1.0 or 127.127.1.1) are listed, this is a finding.
Fix: F-31342r1_fix
If using "ntpd -qg", add additional NTP servers to the cron job running "ntpd -qg". If using the NTP daemon, add an additional "server" line to /etc/ntp.conf for each additional NTP server.
- RMF Control
- AU-8
- Severity
- L
- CCI
- CCI-000160
- Version
- GEN000244
- Vuln IDs
-
- V-22292
- Rule IDs
-
- SV-37413r2_rule
Checks: C-36096r1_chk
Check the root crontab (crontab -l) and the global crontabs in /etc/crontab, /etc/cron.d/*, or scripts in the /etc/cron.daily directory for the presence of an "ntpd -qg" job. If the "ntpd -qg" command is invoked with NTP servers outside of the enclave, this is a finding. Check the NTP daemon configuration for NTP servers. # grep ^server /etc/ntp.conf | grep -v 127.127.1.1 If an NTP server is listed outside of the enclave, this is a finding.
Fix: F-31343r1_fix
If using "ntpd -qg", remove NTP servers external to the enclave from the cron job running "ntpd -qg". If using the NTP daemon, remove the "server" line from /etc/ntp.conf for each NTP server external to the enclave.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000250
- Vuln IDs
-
- V-22294
- Rule IDs
-
- SV-37415r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31345r1_fix
Change the owner of the NTP configuration file. # chown root /etc/ntp.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000251
- Vuln IDs
-
- V-22295
- Rule IDs
-
- SV-37416r1_rule
Checks: C-36099r2_chk
Check the group ownership of the NTP configuration file. Procedure: # ls -lL /etc/ntp.conf If the group owner is not root, bin, or sys, this is a finding.
Fix: F-31346r1_fix
Change the group-owner of the NTP configuration file. Procedure: # chgrp root /etc/ntp.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000252
- Vuln IDs
-
- V-22296
- Rule IDs
-
- SV-37417r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31347r1_fix
Change the mode of the NTP configuration file to 0640 or more restrictive. # chmod 0640 /etc/ntp.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000253
- Vuln IDs
-
- V-22297
- Rule IDs
-
- SV-37418r1_rule
Checks: C-36101r1_chk
Check the NTP configuration file has no extended ACL. # ls -l /etc/ntp.conf If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-23451r1_fix
Remove the extended ACL from the NTP configuration file. # setfacl --remove-all /etc/ntp.conf
- RMF Control
- AC-10
- Severity
- L
- CCI
- CCI-000054
- Version
- GEN000450
- Vuln IDs
-
- V-22298
- Rule IDs
-
- SV-37182r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31140r1_fix
Add a "maxlogins" line such as "* hard maxlogins 10" to /etc/security/limits.conf or a file in /etc/security/limits.d. The enforced maximum should be defined by site requirements and policy.
- RMF Control
- AC-9
- Severity
- L
- CCI
- CCI-000052
- Version
- GEN000452
- Vuln IDs
-
- V-22299
- Rule IDs
-
- SV-37187r1_rule
Checks: C-35888r2_chk
Check that pam_lastlog is used and not silent, or that the SSH daemon is configured to display last login information. # grep pam_lastlog /etc/pam.d/sshd If pam_lastlog is present, and does not have the "silent" option, this is not a finding. # grep -i PrintLastLog /etc/ssh/sshd_config If PrintLastLog is not present in the configuration, this is not a finding. This is the default setting. If PrintLastLog is present in the configuration and set to "yes" (case insensitive), this is not a finding. Otherwise, this is a finding.
Fix: F-31144r1_fix
Implement pam_lastlog, or enable PrintLastLog in the SSH daemon. To enable pam_lastlog, add a line such as "session required pam_lastlog.so" to /etc/pam.d/sshd. To enable PrintLastLog in the SSH daemon, remove any lines disabling this option from /etc/ssh/sshd_config.
- RMF Control
- AC-14
- Severity
- L
- CCI
- CCI-000061
- Version
- GEN000510
- Vuln IDs
-
- V-22301
- Rule IDs
-
- SV-37222r1_rule
Checks: C-35911r1_chk
Determine if a publicly-viewable pattern is displayed during a session lock. Some screensaver themes available but not included in the RHEL distribution use a snapshot of the current screen as a graphic. This theme does not qualify as a publicly-viewable pattern. If the session lock pattern is not publicly-viewable this is a finding.
Fix: F-31169r1_fix
Configure the system to display a publicly-viewable pattern during a session lock. This is done graphically by selecting a screensaver theme using gnome-screensaver-preferences command. Any of the themes distributed with RHEL may be used including "Blank Screen".
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000205
- Version
- GEN000585
- Vuln IDs
-
- V-22302
- Rule IDs
-
- SV-37261r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31207r1_fix
Change the passwords for all accounts using non-compliant password hashes. (This requires GEN000590 is already met.)
- RMF Control
- IA-7
- Severity
- M
- CCI
- CCI-000803
- Version
- GEN000590
- Vuln IDs
-
- V-22303
- Rule IDs
-
- SV-26313r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31215r1_fix
Change the default password algorithm. # authconfig --passalgo=sha512 --update
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000196
- Version
- GEN000595
- Vuln IDs
-
- V-22304
- Rule IDs
-
- SV-26316r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31221r1_fix
Change the passwords for all accounts using non-compliant password hashes. (This requires GEN000590 is already met.)
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000193
- Version
- GEN000610
- Vuln IDs
-
- V-22305
- Rule IDs
-
- SV-26321r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31231r1_fix
Edit "/etc/pam.d/system-auth" to include the line: password required pam_cracklib.so lcredit=-1 prior to the "password include system-auth-ac" line.
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000195
- Version
- GEN000750
- Vuln IDs
-
- V-22306
- Rule IDs
-
- SV-37304r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31252r1_fix
If /etc/pam.d/system-auth references /etc/pam.d/system-auth-ac refer to the man page for system-auth-ac for a description of how to add options not configurable with authconfig. Edit /etc/pam.d/system-auth and add or edit a pam_cracklib entry with an difok parameter set equal to or greater than 4.
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000189
- Version
- GEN000790
- Vuln IDs
-
- V-22307
- Rule IDs
-
- SV-37318r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31262r1_fix
If /etc/pam.d/system-auth references /etc/pam.d/system-auth-ac refer to the man page for system-auth-ac for a description of how to add options not configurable with authconfig. Edit /etc/pam.d/system-auth and configure pam_cracklib by adding a line such as "password required pam_cracklib.so"
- RMF Control
- AC-2
- Severity
- L
- CCI
- CCI-000009
- Version
- GEN000850
- Vuln IDs
-
- V-22308
- Rule IDs
-
- SV-37345r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31282r1_fix
Edit /etc/pam.d/su and uncomment or add a line such as "auth required pam_wheel.so". If necessary, create a "wheel" group and add administrative users to the group.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000930
- Vuln IDs
-
- V-22309
- Rule IDs
-
- SV-37358r1_rule
Checks: C-36046r1_chk
Check the root account's home directory has no extended ACL. # grep "^root" /etc/passwd | awk -F":" '{print $6}' # ls -ld <root home directory> If the permissions include a '+' the directory has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31290r1_fix
Remove the extended ACL from the root account's home directory. # setfacl --remove-all <root home directory>
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000945
- Vuln IDs
-
- V-22310
- Rule IDs
-
- SV-37363r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31296r1_fix
Edit the root user initialization files and remove any definition of LD_LIBRARY_PATH.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000950
- Vuln IDs
-
- V-22311
- Rule IDs
-
- SV-37364r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31298r1_fix
Edit the root user initialization files and remove any definition of LD_PRELOAD.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001170
- Vuln IDs
-
- V-22312
- Rule IDs
-
- SV-37165r1_rule
Checks: C-35872r1_chk
Search the system for files without a valid group-owner. # find / -nogroup If any files are found, this is a finding.
Fix: F-31126r1_fix
Change the group-owner for each file without a valid group-owner. # chgrp avalidgroup /tmp/a-file-without-a-valid-group-owner
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001190
- Vuln IDs
-
- V-22313
- Rule IDs
-
- SV-37199r1_rule
Checks: C-35893r2_chk
Check network services daemon files have no extended ACLs. # ls -la /usr/sbin If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding. Note: Network daemons not residing in these directories must also be checked.
Fix: F-23542r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /usr/sbin/*
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-001499
- Version
- GEN001210
- Vuln IDs
-
- V-22314
- Rule IDs
-
- SV-37210r1_rule
Checks: C-35901r1_chk
Check all system command files have no extended ACLs. # ls -lL /etc /bin /usr/bin /usr/lbin /usr/usb /sbin /usr/sbin If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31159r1_fix
Remove the extended ACL from the file. # setfacl --remove-all [file with extended ACL]
- RMF Control
- SI-11
- Severity
- M
- CCI
- CCI-001314
- Version
- GEN001270
- Vuln IDs
-
- V-22315
- Rule IDs
-
- SV-37233r1_rule
Checks: C-35922r1_chk
Verify system log files have no extended ACLs. Procedure: # ls -lL /var/log If the permissions include a '+', the file has an extended ACL. If an extended ACL exists, verify with the SA if the ACL is required to support authorized software and provides the minimum necessary permissions. If an extended ACL exists providing access beyond the needs of authorized software, this is a finding.
Fix: F-31180r1_fix
Remove the extended ACL from the file. Procedure: # setfacl --remove-all [file with extended ACL]
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN001290
- Vuln IDs
-
- V-22316
- Rule IDs
-
- SV-37238r1_rule
Checks: C-35929r1_chk
Verify all manual page files have no extended ACLs. # ls -lL /usr/share/man /usr/share/info /usr/share/infopage If the permissions include a '+', the file has an extended ACL this is a finding.
Fix: F-31185r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /usr/share/man/* /usr/share/info/* /usr/share/infopage/*
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-001499
- Version
- GEN001310
- Vuln IDs
-
- V-22317
- Rule IDs
-
- SV-37250r1_rule
Checks: C-35940r2_chk
Verify system libraries have no extended ACLs. # ls -lL /usr/lib/* /lib/* | grep "+ " If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and has not been approved by the IAO, this is a finding.
Fix: F-31197r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /usr/lib/* /lib/*
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001361
- Vuln IDs
-
- V-22318
- Rule IDs
-
- SV-37277r1_rule
Checks: C-35968r1_chk
Verify NIS/NIS+/yp files have no extended ACLs. # ls -lL /var/yp/* If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-23574r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /var/yp/*
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001362
- Vuln IDs
-
- V-22319
- Rule IDs
-
- SV-37280r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31226r1_fix
Change the owner of the /etc/resolv.conf file to root. # chown root /etc/resolv.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001363
- Vuln IDs
-
- V-22320
- Rule IDs
-
- SV-37286r1_rule
Checks: C-35978r2_chk
Check the group ownership of the resolv.conf file. Procedure: # ls -lL /etc/resolv.conf If the file is not group-owned by root, bin, or sys, this is a finding.
Fix: F-31233r2_fix
Change the group-owner of the /etc/resolv.conf file to root, bin, or sys. Procedure: # chgrp root /etc/resolv.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001364
- Vuln IDs
-
- V-22321
- Rule IDs
-
- SV-37291r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31239r1_fix
Change the mode of the /etc/resolv.conf file to 0644. # chmod 0644 /etc/resolv.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001365
- Vuln IDs
-
- V-22322
- Rule IDs
-
- SV-37307r1_rule
Checks: C-36001r1_chk
Verify /etc/resolv.conf has no extended ACL. # ls -l /etc/resolv.conf If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-23589r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/resolv.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001366
- Vuln IDs
-
- V-22323
- Rule IDs
-
- SV-37309r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31256r1_fix
Change the owner of the /etc/hosts file to root. # chown root /etc/hosts
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001367
- Vuln IDs
-
- V-22324
- Rule IDs
-
- SV-37315r1_rule
Checks: C-36009r2_chk
Check the /etc/hosts file's group ownership. Procedure: # ls -lL /etc/hosts If the file is not group-owned by root, bin, or sys, this is a finding.
Fix: F-31260r2_fix
Change the group-owner of the /etc/hosts file to root, sys, or bin. Procedure: # chgrp root /etc/hosts
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001368
- Vuln IDs
-
- V-22325
- Rule IDs
-
- SV-37321r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31264r1_fix
Change the mode of the /etc/hosts file to 0644. # chmod 0644 /etc/hosts
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001369
- Vuln IDs
-
- V-22326
- Rule IDs
-
- SV-37324r1_rule
Checks: C-36016r1_chk
Verify /etc/hosts has no extended ACL. # ls -l /etc/hosts If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-23600r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/hosts
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001371
- Vuln IDs
-
- V-22327
- Rule IDs
-
- SV-37326r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31267r1_fix
Change the owner of the /etc/nsswitch.conf file to root. # chown root /etc/nsswitch.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001372
- Vuln IDs
-
- V-22328
- Rule IDs
-
- SV-37330r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31268r1_fix
Change the group-owner of the /etc/nsswitch.conf file to root, bin or sys. Procedure: # chgrp root /etc/nsswitch.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001373
- Vuln IDs
-
- V-22329
- Rule IDs
-
- SV-37332r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31270r1_fix
Change the mode of the /etc/nsswitch.conf file to 0644 or less permissive. # chmod 0644 /etc/nsswitch.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001374
- Vuln IDs
-
- V-22330
- Rule IDs
-
- SV-37334r1_rule
Checks: C-36025r1_chk
Verify /etc/nsswitch.conf has no extended ACL. # ls -l /etc/nsswitch.conf If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-23607r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/nsswitch.conf
- RMF Control
- SC-22
- Severity
- L
- CCI
- CCI-001182
- Version
- GEN001375
- Vuln IDs
-
- V-22331
- Rule IDs
-
- SV-37335r2_rule
Checks: C-36026r1_chk
Determine if DNS is enabled on the system. # grep dns /etc/nsswitch.conf If no line is returned, or any returned line is commented out, the system does not use DNS, and this is not applicable. Determine the name servers used by the system. # grep nameserver /etc/resolv.conf If less than two lines are returned that are not commented out, this is a finding.
Fix: F-31272r1_fix
Edit /etc/resolv.conf and add additional "nameserver" lines until at least two are present.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001378
- Vuln IDs
-
- V-22332
- Rule IDs
-
- SV-37336r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31273r1_fix
Change the owner of the /etc/passwd file to root. # chown root /etc/passwd
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001379
- Vuln IDs
-
- V-22333
- Rule IDs
-
- SV-37337r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31274r1_fix
Change the group-owner of the /etc/passwd file to root, bin or sys. Procedure: # chgrp root /etc/passwd
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001390
- Vuln IDs
-
- V-22334
- Rule IDs
-
- SV-37346r1_rule
Checks: C-36038r1_chk
Verify /etc/passwd has no extended ACL. # ls -l /etc/passwd If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-23614r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/passwd
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001391
- Vuln IDs
-
- V-22335
- Rule IDs
-
- SV-37351r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31286r1_fix
Change the owner of the /etc/group file to root. # chown root /etc/group
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001392
- Vuln IDs
-
- V-22336
- Rule IDs
-
- SV-37352r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31287r1_fix
Change the group-owner of the /etc/group file. Procedure: # chgrp root /etc/group
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001393
- Vuln IDs
-
- V-22337
- Rule IDs
-
- SV-37354r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31289r1_fix
Change the mode of the /etc/group file to 0644 or less permissive. # chmod 0644 /etc/group
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001394
- Vuln IDs
-
- V-22338
- Rule IDs
-
- SV-37357r1_rule
Checks: C-36047r1_chk
Verify /etc/group has no extended ACL. # ls -l /etc/group If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31291r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/group
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001410
- Vuln IDs
-
- V-22339
- Rule IDs
-
- SV-37365r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31297r1_fix
Change the group-owner of the /etc/shadow file. Procedure: # chgrp root /etc/shadow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001430
- Vuln IDs
-
- V-22340
- Rule IDs
-
- SV-37371r1_rule
Checks: C-36058r1_chk
Verify /etc/shadow has no extended ACL. # ls -l /etc/shadow If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31303r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/shadow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX001431
- Vuln IDs
-
- V-22341
- Rule IDs
-
- SV-37143r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31110r1_fix
Change the owner of the /etc/gshadow file to root. # chown root /etc/gshadow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX001432
- Vuln IDs
-
- V-22342
- Rule IDs
-
- SV-37164r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31125r1_fix
Change the group-owner of the /etc/gshadow file to root. # chgrp root /etc/gshadow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX001433
- Vuln IDs
-
- V-22343
- Rule IDs
-
- SV-37170r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31130r1_fix
Change the mode of the /etc/gshadow file to 0400 or less permissive. # chmod 0400 /etc/gshadow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX001434
- Vuln IDs
-
- V-22344
- Rule IDs
-
- SV-37176r1_rule
Checks: C-35880r1_chk
Check /etc/gshadow has no extended ACL. # ls -l /etc/gshadow If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31135r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/gshadow
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000201
- Version
- GEN001470
- Vuln IDs
-
- V-22347
- Rule IDs
-
- SV-37381r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31312r1_fix
Migrate /etc/passwd password hashes to /etc/shadow. # pwconv
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001475
- Vuln IDs
-
- V-22348
- Rule IDs
-
- SV-37383r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31314r1_fix
Edit /etc/group and change the password field to an exclamation point (!) to lock the group password.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN000000-LNX001476
- Vuln IDs
-
- V-22349
- Rule IDs
-
- SV-37386r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31317r1_fix
Edit /etc/gshadow and change the password field to an exclamation point (!) to lock the group password.
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN001490
- Vuln IDs
-
- V-22350
- Rule IDs
-
- SV-37162r1_rule
Checks: C-37525r1_chk
Verify user home directories have no extended ACLs. # cut -d : -f 6 /etc/passwd | xargs -n1 ls -ld If the permissions include a '+', the file has an extended ACL this is a finding.
Fix: F-23641r1_fix
Remove the extended ACL from the file. # setfacl --remove-all [user home directory with extended ACL]
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001550
- Vuln IDs
-
- V-22351
- Rule IDs
-
- SV-37180r1_rule
Checks: C-35883r2_chk
Check the contents of user home directories for files group-owned by a group of which the home directory's owner is not a member. 1. List the user accounts. # cut -d : -f 1 /etc/passwd 2. For each user account, get a list of GIDs for files in the user's home directory. # find ~username -printf %G\\n | sort | uniq 3. Obtain the list of GIDs where the user is a member. # id -G username 4. Check the GID lists. If there are GIDs in the file list not present in the user list, this is a finding.
Fix: F-31138r1_fix
Change the group of a file not group-owned by a group of which the home directory's owner is a member. # chgrp <group with user as member> <file with bad group ownership> Document all changes.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001570
- Vuln IDs
-
- V-22352
- Rule IDs
-
- SV-37188r1_rule
Checks: C-37530r1_chk
Check the contents of user home directories for files with extended ACLs. # cut -d : -f 6 /etc/passwd | xargs -n1 -IDIR ls -alLR DIR If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32776r1_fix
Remove the extended ACL from the file. # setfacl --remove-all <user file with extended ACL>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001590
- Vuln IDs
-
- V-22353
- Rule IDs
-
- SV-37196r1_rule
Checks: C-37532r1_chk
Verify run control scripts have no extended ACLs. # ls -lL /etc/rc* /etc/init.d If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32778r1_fix
Remove the extended ACL from the file. # setfacl --remove-all <run control script with extended ACL>
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001605
- Vuln IDs
-
- V-22354
- Rule IDs
-
- SV-37211r1_rule
Checks: C-37534r1_chk
Verify run control scripts' library search paths. # grep -r LD_LIBRARY_PATH /etc/rc* /etc/init.d This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon, or two consecutive colons, this is a finding. If an entry begins with a character other than a slash (/) this is a relative path, this is a finding.
Fix: F-32780r1_fix
Edit the run control script and remove the relative path entry from the library search path variable.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001610
- Vuln IDs
-
- V-22355
- Rule IDs
-
- SV-37215r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32781r1_fix
Edit the run control script and remove the relative path entry from the library preload variable.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001730
- Vuln IDs
-
- V-22356
- Rule IDs
-
- SV-37279r1_rule
Checks: C-35970r1_chk
Check global initialization files for extended ACLs: # ls -l /etc/bashrc /etc/csh.cshrc /etc/csh.login /etc/csh.logout /etc/environment /etc/ksh.kshrc /etc/profile /etc/suid_profile /etc/profile.d/* 2>null|grep "\+ " If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31225r1_fix
Remove the extended ACL from the file. # ls -l etc/bashrc /etc/csh.cshrc /etc/csh.login /etc/csh.logout /etc/environment /etc/ksh.kshrc /etc/profile /etc/suid_profile /etc/profile.d/* 2>null|grep "\+ "|sed "s/^.* \///g"|xargs setfacl --remove-all
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001810
- Vuln IDs
-
- V-22357
- Rule IDs
-
- SV-37297r1_rule
Checks: C-35991r2_chk
Check skeleton files for extended ACLs: # ls -alL /etc/skel If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31245r1_fix
Remove the extended ACL from the file. # setfacl --remove-all [skeleton file with extended ACL] or: # ls -lL /etc/skel|grep "\+ "|sed "s/^.* \//|xargs setfacl --remove-all will remove all ACLs from the files.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001830
- Vuln IDs
-
- V-22358
- Rule IDs
-
- SV-37237r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31184r1_fix
Change the group-owner of the skeleton file to root, bin, sys, system, or other. Procedure: # chgrp <group> /etc/skel/[skeleton file] or: # ls -L /etc/skel|xargs stat -L -c %G:%n|egrep -v "^(root|bin|sy|sytem|other):"|cut -d: -f2|chgrp root will change the group of all files not already one of the approved group to root.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001845
- Vuln IDs
-
- V-22359
- Rule IDs
-
- SV-37246r1_rule
Checks: C-35936r1_chk
Check the global initialization files' library search paths. Procedure: # grep LD_LIBRARY_PATH /etc/bashrc /etc/csh.cshrc /etc/csh.login /etc/csh.logout /etc/environment /etc/ksh.kshrc /etc/profile /etc/suid_profile /etc/profile.d/* This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon, or two consecutive colons, this is a finding. If an entry begins with a character other than a slash (/) this is a relative path, this is a finding.
Fix: F-31193r1_fix
Edit the global initialization file and remove the relative path entry from the library search path variable.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001850
- Vuln IDs
-
- V-22360
- Rule IDs
-
- SV-37248r1_rule
Checks: C-35938r1_chk
Check the global initialization files' library preload list. # grep -r LD_PRELOAD /etc/bashrc /etc/csh.cshrc /etc/csh.login /etc/csh.logout /etc/environment /etc/ksh.kshrc /etc/profile /etc/suid_profile /etc/profile.d/* This variable is formatted as a colon-separated list of paths. If there is an empty entry, such as a leading or trailing colon, or two consecutive colons, this is a finding. If an entry begins with a character other than a slash (/) this is a relative path, this is a finding.
Fix: F-31195r1_fix
Edit the global initialization file and remove the relative path entry from the library preload variable.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001870
- Vuln IDs
-
- V-22361
- Rule IDs
-
- SV-37252r1_rule
Checks: C-35943r1_chk
Check user home directories for local initialization files group-owned by a group other than the user's primary group or root. Procedure: # FILES=" .login .cshrc .logout .profile .bash_profile .bashrc .bash_logout .env .dtprofile .dispatch .emacs .exrc"; # for PWLINE in `cut -d: -f4,6 /etc/passwd`; do HOMEDIR=$(echo ${PWLINE}|cut -d: -f2);GROUP=$(echo ${PWLINE} | cut -d: -f1);for INIFILE in $FILES;do stat -c %g/%G:%n ${HOMEDIR}/${INIFILE} 2>null|egrep -v "${GROUP}";done;done If any file is not group-owned by root or the user's primary GID, this is a finding.
Fix: F-31199r1_fix
Change the group-owner of the local initialization file to the user's primary group, or root. # chgrp <user's primary GID> <user's local initialization file> Procedure: # FILES=".bashrc .bash_login .bash_logout .bash_profile .cshrc .kshrc .login .logout .profile .tcshrc .env .dtprofile .dispatch .emacs .exrc"; # for PWLINE in `cut -d: -f4,6 /etc/passwd`; do HOMEDIR=$(echo ${PWLINE}|cut -d: -f2);GROUP=$(echo ${PWLINE} | cut -d: -f1);for INIFILE in $FILES;do MATCH=$(stat -c %g/%G:%n ${HOMEDIR}/${INIFILE} 2>null|egrep -c -v "${GROUP}");if [ $MATCH != 0 ] ; then chgrp ${GROUP} ${HOMEDIR}/${INIFILE};fi;done;done
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN001890
- Vuln IDs
-
- V-22362
- Rule IDs
-
- SV-37271r1_rule
Checks: C-35963r1_chk
Check user home directories for local initialization files with extended ACLs. # cut -d : -f 6 /etc/passwd | xargs -n1 -IDIR ls -alL DIR/.bashrc DIR/.bash_login DIR/.bash_logout DIR/.bash_profile DIR/.cshrc DIR/.kshrc DIR/.login DIR/.logout DIR/.profile DIR/.env DIR/.dtprofile DIR/.dispatch DIR/.emacs DIR/.exrc If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31219r1_fix
Remove the extended ACL from the file. # setfacl --remove-all <local initialization file with extended ACL>
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001901
- Vuln IDs
-
- V-22363
- Rule IDs
-
- SV-37305r2_rule
Checks: C-36000r2_chk
Verify local initialization files have library search path containing only absolute paths. Procedure: NOTE: This must be done in the BASH shell. # cut -d: -f6 /etc/passwd |xargs -n1 -IDIR find DIR -name ".*" -type f -maxdepth 1 -exec grep -H LD_LIBRARY_PATH {} \; This variable is formatted as a colon-separated list of directories. If there is an empty entry, such as a leading or trailing colon, or two consecutive colons, this is a finding. If an entry begins with a character other than a slash (/) this is a relative path, this is a finding.
Fix: F-31253r1_fix
Edit the local initialization file and remove the relative path entry from the library search path variable.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN001902
- Vuln IDs
-
- V-22364
- Rule IDs
-
- SV-37312r2_rule
Checks: C-36005r2_chk
Verify local initialization files have library preload list containing only absolute paths. NOTE: The following must be done in the BASH shell. Procedure: # cut -d: -f6 /etc/passwd |xargs -n1 -IDIR find DIR -name ".*" -type f -maxdepth 1 -exec grep -H LD_PRELOAD {} \; This variable is formatted as a colon-separated list of paths. If there is an empty entry, such as a leading or trailing colon, or two consecutive colons, this is a finding. If an entry begins with a character other than a slash (/) this is a relative path, this is a finding.
Fix: F-31257r1_fix
Edit the local initialization file and remove the relative path entry from the library preload variable.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002210
- Vuln IDs
-
- V-22365
- Rule IDs
-
- SV-37399r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31329r1_fix
Change the group-owner of the shell to root, bin, sys, or system. Procedure: # chgrp root <shell>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002230
- Vuln IDs
-
- V-22366
- Rule IDs
-
- SV-37405r1_rule
Checks: C-36088r1_chk
If /etc/shells exists, check the permissions of each shell referenced. # cat /etc/shells | xargs -n1 ls -lL Otherwise, check any shells found on the system. # find / -name "*sh" | xargs -n1 ls -lL If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31335r1_fix
Remove the extended ACL from the file. # setfacl --remove-all [shell]
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002330
- Vuln IDs
-
- V-22367
- Rule IDs
-
- SV-37569r1_rule
Checks: C-36218r1_chk
Check the permissions of audio devices. # ls -lL /dev/audio* /dev/snd/* If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31478r1_fix
Remove the extended ACL from the file. # setfacl --remove-all [device file]
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN002430
- Vuln IDs
-
- V-22368
- Rule IDs
-
- SV-37623r1_rule
Checks: C-36822r2_chk
Check /etc/mtab and verify the "nodev" mount option is used on any filesystems mounted from removable media or network shares. If any filesystem mounted from removable media or network shares does not have this option, this is a finding.
Fix: F-31660r1_fix
Edit /etc/fstab and add the "nodev" option to any filesystems mounted from removable media or network shares.
- RMF Control
- AU-9
- Severity
- M
- CCI
- CCI-000163
- Version
- GEN002710
- Vuln IDs
-
- V-22369
- Rule IDs
-
- SV-37917r1_rule
Checks: C-37143r1_chk
Check the system audit log files for extended ACLs. Procedure: # grep "^log_file" /etc/audit/auditd.conf|sed s/^[^\/]*//|xargs ls -l If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-26222r1_fix
Remove the extended ACL from the system audit file(s).
- RMF Control
- AU-9
- Severity
- L
- CCI
- CCI-001493
- Version
- GEN002715
- Vuln IDs
-
- V-22370
- Rule IDs
-
- SV-26504r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23742r1_fix
Change the owner of the audit tool executable to root. # chown root [audit tool executable]
- RMF Control
- AU-9
- Severity
- L
- CCI
- CCI-001493
- Version
- GEN002716
- Vuln IDs
-
- V-22371
- Rule IDs
-
- SV-26507r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23743r1_fix
Change the group-owner of the audit tool executable to root, bin, sys, or system. Procedure: # chgrp root <audit tool executable>
- RMF Control
- AU-9
- Severity
- L
- CCI
- CCI-001493
- Version
- GEN002717
- Vuln IDs
-
- V-22372
- Rule IDs
-
- SV-26510r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23745r1_fix
Change the mode of the audit tool executable to 0750, or less permissive. # chmod 0750 [audit tool executable]
- RMF Control
- AU-9
- Severity
- L
- CCI
- CCI-001493
- Version
- GEN002718
- Vuln IDs
-
- V-22373
- Rule IDs
-
- SV-26513r1_rule
Checks: C-27567r1_chk
Check the permissions of audit tool executables. # ls -l /sbin/auditctl /sbin/auditd /sbin/ausearch /sbin/aureport /sbin/autrace /sbin/audispd If the permissions include a '+' the file has an extended ACL, this is a finding.
Fix: F-23749r1_fix
Remove the extended ACL from the file. # setfacl --remove-all [audit file]
- RMF Control
- AU-5
- Severity
- L
- CCI
- CCI-000139
- Version
- GEN002719
- Vuln IDs
-
- V-22374
- Rule IDs
-
- SV-68095r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32421r1_fix
Edit /etc/audit/auditd.conf and set the disk_full_action and/or disk_error_action parameters to a valid setting of "syslog", "exec", "single" or "halt", adding the parameters if necessary.
- RMF Control
- AU-5
- Severity
- M
- CCI
- CCI-000143
- Version
- GEN002730
- Vuln IDs
-
- V-22375
- Rule IDs
-
- SV-26518r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32424r1_fix
Edit /etc/audit/auditd.conf and set the space_left_action parameter to a valid setting other than "ignore". If the space_left_action parameter is set to "email" set the action_mail_acct parameter to an e-mail address for the system administrator.
- RMF Control
- AC-2
- Severity
- L
- CCI
- CCI-000018
- Version
- GEN002750
- Vuln IDs
-
- V-22376
- Rule IDs
-
- SV-26519r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23761r1_fix
Configure execute auditing of the useradd and groupadd executables. Add the following to audit.rules: -w /usr/sbin/useradd -p x -k useradd -w /usr/sbin/groupadd -p x -k groupadd Configure append auditing of the passwd, shadow, group, and gshadow files. Add the following to audit.rules: -w /etc/passwd -p a -k passwd -w /etc/shadow -p a -k shadow -w /etc/group -p a -k group -w /etc/gshadow -p a -k gshadow Restart the auditd service.
- RMF Control
- AC-2
- Severity
- L
- CCI
- CCI-001403
- Version
- GEN002751
- Vuln IDs
-
- V-22377
- Rule IDs
-
- SV-26520r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23762r1_fix
Configure execute auditing of the usermod and groupmod executables. Add the following to the audit.rules file: -w /usr/sbin/usermod -p x -k usermod -w /usr/sbin/groupmod -p x -k groupmod Configure append auditing of the passwd, shadow, group, and gshadow files. Add the following to the audit.rules file: -w /etc/passwd -p w -k passwd -w /etc/shadow -p w -k shadow -w /etc/group -p w -k group -w /etc/gshadow -p w -k gshadow Restart the auditd service.
- RMF Control
- AC-2
- Severity
- L
- CCI
- CCI-001404
- Version
- GEN002752
- Vuln IDs
-
- V-22378
- Rule IDs
-
- SV-26521r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23763r1_fix
Configure execute auditing of the passwd executable. Add the following to the audit.rules file: -w /usr/bin/passwd -p x -k passwd Restart the auditd service.
- RMF Control
- AC-2
- Severity
- L
- CCI
- CCI-001405
- Version
- GEN002753
- Vuln IDs
-
- V-22382
- Rule IDs
-
- SV-26522r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32432r1_fix
Configure execute auditing of the userdel and groupdel executables. Add the following to the audit.rules file: -w /usr/sbin/userdel -p x -w /usr/sbin/groupdel -p x Restart the auditd service.
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002825
- Vuln IDs
-
- V-22383
- Rule IDs
-
- SV-38652r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32807r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Configure auditing of the init_module syscalls. Add the following to the "etc/audit/audit.rules" or "etc/audit.rules" file: -a exit,always -S init_module Restart the auditd service. # service auditd restart
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN002990
- Vuln IDs
-
- V-22384
- Rule IDs
-
- SV-37382r1_rule
Checks: C-36069r1_chk
Check the permissions of the cron.allow file. # ls -l /etc/cron.allow If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31313r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/cron.allow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003050
- Vuln IDs
-
- V-22385
- Rule IDs
-
- SV-37400r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31323r1_fix
Change the group owner of the crontab file to root, cron, or the crontab's primary group. Procedure: # chgrp root [crontab file]
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003090
- Vuln IDs
-
- V-22386
- Rule IDs
-
- SV-37467r1_rule
Checks: C-36133r1_chk
Check the permissions of the crontab files. Procedure: # ls -lL /var/spool/cron # ls -lL /etc/cron.d /etc/crontab /etc/cron.daily /etc/cron.hourly /etc/cron.monthly /etc/cron.weekly or # ls -lL /etc/cron*|grep -v deny If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31378r1_fix
Remove the extended ACL from the file. # setfacl --remove-all [crontab file]
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003110
- Vuln IDs
-
- V-22387
- Rule IDs
-
- SV-37471r1_rule
Checks: C-36138r1_chk
Check the permissions of the crontab directories. Procedure: # ls -ld /var/spool/cron # ls -ld /etc/cron.d /etc/crontab /etc/cron.daily /etc/cron.hourly /etc/cron.monthly /etc/cron.weekly or # ls -ld /etc/cron*|grep -v deny If the permissions include a '+' the directory has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31383r1_fix
Remove the extended ACL from the directory. # setfacl --remove-all <crontab directory>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003190
- Vuln IDs
-
- V-22388
- Rule IDs
-
- SV-37477r1_rule
Checks: C-36144r1_chk
Check the permissions of the file. Procedure: Check the configured cron log file found in the cron entry in /etc/syslog (normally /var/log/cron). # grep cron /etc/syslog.conf # ls -lL /var/log/cron If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31390r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /var/log/cron
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003210
- Vuln IDs
-
- V-22389
- Rule IDs
-
- SV-37486r1_rule
Checks: C-36145r1_chk
Check the permissions of the file. # ls -lL /etc/cron.deny If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31394r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/cron.deny
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003245
- Vuln IDs
-
- V-22390
- Rule IDs
-
- SV-37495r1_rule
Checks: C-36151r1_chk
Check the permissions of the file. # ls -lL /etc/at.allow If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31402r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/at.allow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003250
- Vuln IDs
-
- V-22391
- Rule IDs
-
- SV-37499r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31406r1_fix
Change the group ownership of the file. Procedure: # chgrp root /etc/cron.allow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003252
- Vuln IDs
-
- V-22392
- Rule IDs
-
- SV-26555r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23799r1_fix
Change the mode of the file. # chmod 0600 /etc/at.deny
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003255
- Vuln IDs
-
- V-22393
- Rule IDs
-
- SV-26558r1_rule
Checks: C-36161r1_chk
Check the permissions of the file. # ls -lL /etc/at.deny If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31412r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/at.deny
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003270
- Vuln IDs
-
- V-22394
- Rule IDs
-
- SV-26562r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31415r1_fix
Change the group ownership of the file. # chgrp root /etc/cron.deny
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003410
- Vuln IDs
-
- V-22395
- Rule IDs
-
- SV-37523r1_rule
Checks: C-36184r1_chk
Check the permissions of the directory. # ls -lLd /var/spool/at If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31438r1_fix
Remove the extended ACL from the directory. # setfacl --remove-all /var/spool/at
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003430
- Vuln IDs
-
- V-22396
- Rule IDs
-
- SV-37529r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31443r1_fix
Change the group ownership of the file to root, bin, sys, daemon or cron. Procedure: # chgrp <root or other system group> <"at" directory>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003470
- Vuln IDs
-
- V-22397
- Rule IDs
-
- SV-26569r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31450r1_fix
Change the group ownership of the file. Procedure: # chgrp root /etc/at.allow
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003490
- Vuln IDs
-
- V-22398
- Rule IDs
-
- SV-26572r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31455r1_fix
Change the group ownership of the at.deny file to root, sys, bin, or cron. Procedure: # chgrp root /etc/at.deny
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN003510
- Vuln IDs
-
- V-22404
- Rule IDs
-
- SV-26604r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23849r1_fix
Disable kdump. # service kdump stop # chkconfig kdump off
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN003521
- Vuln IDs
-
- V-22405
- Rule IDs
-
- SV-26608r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31609r1_fix
Change the group-owner of the kernel core dump data directory. # chgrp root <kernel core dump data directory>
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN003522
- Vuln IDs
-
- V-22406
- Rule IDs
-
- SV-26612r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31610r1_fix
Change the group-owner of the kernel core dump data directory. # chmod 0700 <kernel core dump data directory>
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN003523
- Vuln IDs
-
- V-22407
- Rule IDs
-
- SV-26616r1_rule
Checks: C-36352r1_chk
Determine the kernel core dump data directory and check its permissions. Procedure: Examine /etc/kdump.conf. The "path" parameter, which defaults to /var/crash, determines the path relative to the crash dump device. The crash device is specified with a filesystem type and device, such as "ext3 /dev/sda2". Using this information, determine where this path is currently mounted on the system. # ls -l <kernel dump directory> If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-23859r1_fix
Remove the extended ACL from the file. # setfacl --remove-all <core file directory>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003581
- Vuln IDs
-
- V-22408
- Rule IDs
-
- SV-26620r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23863r1_fix
Edit the configuration for the user-controlled interface and remove the "USERCTL=yes" configuration line or set to "USERCTL=no".
- RMF Control
- AC-4
- Severity
- L
- CCI
- CCI-001551
- Version
- GEN003602
- Vuln IDs
-
- V-22409
- Rule IDs
-
- SV-37601r1_rule
Checks: C-36721r2_chk
Verify the system does not respond to ICMP TIMESTAMP_REQUESTs Procedure: # grep "timestamp" /etc/sysconfig/iptables This should return entries for "timestamp-reply" and "timestamp_request". Both should end with "-j DROP'. If either does not exist or does not "DROP" the message, this is a finding.
Fix: F-31637r1_fix
Configure the system to not respond to ICMP TIMESTAMP_REQUESTs. This is done by rejecting ICMP type 13 and 14 messages at the firewall. Procedure: Edit /etc/sysconfig/iptables to add: -A RH-Firewall-1-INPUT -p ICMP --icmp-type timestamp-request -j DROP -A RH-Firewall-1-INPUT -p ICMP --icmp-type timestamp-reply -j DROP Restart the firewall: # service iptables restart
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN003603
- Vuln IDs
-
- V-22410
- Rule IDs
-
- SV-37608r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31641r1_fix
Configure the system to not respond to ICMP ECHO_REQUESTs sent to broadcast addresses. Edit /etc/sysctl.conf and add a setting for "net.ipv4.icmp_echo_ignore_broadcasts=1" and reload the sysctls. Procedure: # echo "net.ipv4.icmp_echo_ignore_broadcasts=1" >> /etc/sysctl.conf # sysctl -p
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN003604
- Vuln IDs
-
- V-22411
- Rule IDs
-
- SV-29288r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31645r1_fix
Configure the system to not respond to ICMP TIMESTAMP_REQUESTs sent to broadcast addresses. Edit /etc/sysctl.conf and add a setting for "net.ipv4.icmp_echo_ignore_broadcasts=1" and reload the sysctls. Procedure: # echo "net.ipv4.icmp_echo_ignore_broadcasts=1" >> /etc/sysctl.conf # sysctl -p
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN003607
- Vuln IDs
-
- V-22414
- Rule IDs
-
- SV-37622r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31659r1_fix
Configure the system to not accept source-routed IPv4 packets. Edit /etc/sysctl.conf and add a setting for "net.ipv4.conf.all.accept_source_route=0" and "net.ipv4.conf.default.accept_source_route=0". Reload the sysctls. Procedure: # sysctl -p
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN003608
- Vuln IDs
-
- V-22415
- Rule IDs
-
- SV-37624r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31661r1_fix
Configure the system to not use proxy ARP. Edit /etc/sysctl.conf and add a setting for "net.ipv4.conf.all.proxy_arp=0" and "net.ipv4.conf.default.proxy_arp=0". # sysctl -p
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-001503
- Version
- GEN003609
- Vuln IDs
-
- V-22416
- Rule IDs
-
- SV-37626r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31663r1_fix
Configure the system to not accept IPv4 ICMP redirect messages. Edit /etc/sysctl.conf and add a setting for "net.ipv4.conf.all.accept_redirects=0" and "net.ipv4.conf.default.accept_redirects=0". # sysctl -p
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN003610
- Vuln IDs
-
- V-22417
- Rule IDs
-
- SV-37629r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31666r1_fix
Configure the system to not send IPv4 ICMP redirect messages. Edit /etc/sysctl.conf and add a setting for "net.ipv4.conf.all.send_redirects=0" and "net.ipv4.conf.default.send_redirects=0". # sysctl -p
- RMF Control
- AU-2
- Severity
- L
- CCI
- CCI-000126
- Version
- GEN003611
- Vuln IDs
-
- V-22418
- Rule IDs
-
- SV-37630r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31667r1_fix
Configure the system to log martian packets. Edit /etc/sysctl.conf and add a setting for "net.ipv4.conf.all.log_martians=1" and "net.ipv4.conf.default.log_martians=1". Reload the sysctls. Procedure: # sysctl -p
- RMF Control
- SC-5
- Severity
- M
- CCI
- CCI-001092
- Version
- GEN003612
- Vuln IDs
-
- V-22419
- Rule IDs
-
- SV-37633r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31670r1_fix
Configure the system to use TCP syncookies when experiencing a TCP SYN flood. Edit /etc/sysctl.conf and add a setting for "net.ipv4.tcp_syncookies=1". # sysctl -p
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN003619
- Vuln IDs
-
- V-22421
- Rule IDs
-
- SV-37639r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31674r1_fix
Configure the system to not use bridging. # rmmod bridge Edit /etc/modprobe.conf and add a line such as "install bridge /bin/false" to prevent the loading of the bridge module.
- RMF Control
- CP-10
- Severity
- L
- CCI
- CCI-000553
- Version
- GEN003650
- Vuln IDs
-
- V-22422
- Rule IDs
-
- SV-37401r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31331r1_fix
Convert local file systems to use journaling or another mechanism ensuring file system consistency.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003730
- Vuln IDs
-
- V-22423
- Rule IDs
-
- SV-37407r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31337r1_fix
Change the group-owner of the xinetd configuration files and directories. Procedure: # chgrp -R root /etc/xinetd.conf /etc/xinetd.d
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003745
- Vuln IDs
-
- V-22424
- Rule IDs
-
- SV-37409r1_rule
Checks: C-36092r1_chk
Check the permissions of the xinetd configuration files. Procedure: # ls -alL /etc/xinetd.conf If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31339r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/xinetd.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003750
- Vuln IDs
-
- V-22425
- Rule IDs
-
- SV-37410r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31340r1_fix
Change the mode of the directory. # chmod 0755 /etc/xinetd.d
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003755
- Vuln IDs
-
- V-22426
- Rule IDs
-
- SV-37411r1_rule
Checks: C-36094r1_chk
Check the permissions of the xinetd configuration files and directories. # ls -alL /etc/xinetd.conf /etc/xinetd.d If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31341r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/xinetd.d
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003770
- Vuln IDs
-
- V-22427
- Rule IDs
-
- SV-37425r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31352r1_fix
Change the group-owner of the services file. Procedure: # chgrp root /etc/services
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003790
- Vuln IDs
-
- V-22428
- Rule IDs
-
- SV-37438r1_rule
Checks: C-36109r1_chk
Check the permissions of the /etc/services file. # ls -lL /etc/services If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31356r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/services
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001436
- Version
- GEN003810
- Vuln IDs
-
- V-22429
- Rule IDs
-
- SV-26662r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23904r1_fix
Shutdown and disable the portmap service. # service portmap stop; chkconfig portmap off
- RMF Control
- CM-2
- Severity
- M
- CCI
- CCI-000305
- Version
- GEN003815
- Vuln IDs
-
- V-22430
- Rule IDs
-
- SV-26666r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23908r1_fix
Remove the portmap package. # rpm -e portmap or # yum remove portmap
- RMF Control
- CM-2
- Severity
- M
- CCI
- CCI-000305
- Version
- GEN003825
- Vuln IDs
-
- V-22431
- Rule IDs
-
- SV-26667r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23909r1_fix
Remove the rsh-server package. Procedure: # rpm -e rsh-server
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-000068
- Version
- GEN003830
- Vuln IDs
-
- V-22432
- Rule IDs
-
- SV-26671r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23912r1_fix
Remove or disable the rlogin configuration and restart xinetd. # rm /etc/xinetd.d/rlogin ; service xinetd restart
- RMF Control
- CM-2
- Severity
- M
- CCI
- CCI-000305
- Version
- GEN003835
- Vuln IDs
-
- V-22433
- Rule IDs
-
- SV-26669r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23909r1_fix
Remove the rsh-server package. Procedure: # rpm -e rsh-server
- RMF Control
- CM-2
- Severity
- M
- CCI
- CCI-000305
- Version
- GEN003845
- Vuln IDs
-
- V-22434
- Rule IDs
-
- SV-26673r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-23909r1_fix
Remove the rsh-server package. Procedure: # rpm -e rsh-server
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003930
- Vuln IDs
-
- V-22435
- Rule IDs
-
- SV-37449r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31367r1_fix
Change the group-owner of the printers.conf file. Procedure: # chgrp lp /etc/cups/printers.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003950
- Vuln IDs
-
- V-22436
- Rule IDs
-
- SV-37462r1_rule
Checks: C-36128r2_chk
Check the permissions of the /etc/cups/printers.conf file. # ls -lL /etc/cups/printers.conf If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31372r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/cups/printers.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004010
- Vuln IDs
-
- V-22437
- Rule IDs
-
- SV-37468r1_rule
Checks: C-36134r1_chk
Check the permissions of the /bin/traceroute file. # ls -lL /bin/traceroute If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31379r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /bin/traceroute
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004370
- Vuln IDs
-
- V-22438
- Rule IDs
-
- SV-37473r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31385r1_fix
Change the group-owner of the /etc/aliases file. Procedure: for sendmail: # chgrp root /etc/aliases # chgrp smmsp /etc/aliases.db The aliases.db file must be owned by the same system group as sendmail, which is smmsp by default. for postfix # chgrp root /etc/postfix/aliases # chgrp root /etc/postfix/aliases.db
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004390
- Vuln IDs
-
- V-22439
- Rule IDs
-
- SV-37488r2_rule
Checks: C-36146r2_chk
If the "sendmail" and "postfix" packages are not installed, this is not applicable. Check the permissions of the alias file. Procedure: for sendmail: # ls -lL /etc/aliases /etc/aliases.db If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding. for postfix: Verify the location of the alias file. # postconf alias maps This will return the location of the "aliases" file, by default "/etc/postfix/aliases" # ls -lL <postfix aliases file> <postfix aliases.db file> If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31396r1_fix
Remove the extended permissions from the alias files. Procedure: for sendmail: # setfacl --remove-all /etc/aliases /etc/aliases.db for postfix (assuming the default postfix directory): # setfacl --remove-all /etc/postfix/aliases /etc/postfix/aliases.db
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004410
- Vuln IDs
-
- V-22440
- Rule IDs
-
- SV-37493r1_rule
Checks: C-36150r1_chk
Examine the contents of the /etc/aliases file. Procedure: # more /etc/aliases Examine the aliases file for any utilized directories or paths. # ls -lL <file referenced from aliases> Check the permissions for any paths referenced. If the group owner of any file is not root, bin, sys, or system, this is a finding.
Fix: F-31401r1_fix
Change the group ownership of the file referenced from /etc/aliases. Procedure: # chgrp root <file referenced from aliases>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004430
- Vuln IDs
-
- V-22441
- Rule IDs
-
- SV-37496r1_rule
Checks: C-36153r1_chk
Examine the contents of the /etc/aliases file. Procedure: # more /etc/aliases Examine the aliases file for any utilized directories or paths. # ls -lL <file referenced from aliases> Check the permissions for any paths referenced. If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31404r1_fix
Remove the extended ACL from the file. # setfacl --remove-all <file referenced from aliases>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004510
- Vuln IDs
-
- V-22442
- Rule IDs
-
- SV-37503r1_rule
Checks: C-36160r1_chk
Examine /etc/syslog.conf and determine the log file(s) receiving logs for "mail.crit", "mail.debug", mail.*, or "*.crit". Procedure: This check is applicable to both Postfix or sendmail servers. Check the permissions on these log files.Identify any log files configured for "*.crit" and the "mail" service (excluding mail.none) and at any severity level. # egrep "(\*.crit|mail\.[^n][^/]*)" /etc/syslog.conf|sed 's/^[^/]*//'|xargs ls -lL If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31411r1_fix
This fix is applicable to both Postfix and sendmail servers. Remove the extended ACL from the file. # setfacl --remove-all <log file>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004930
- Vuln IDs
-
- V-22444
- Rule IDs
-
- SV-37538r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31454r1_fix
Change the group owner of the ftpusers file. Procedure: # chgrp root /etc/ftpusers /etc/vsftpd.ftpusers /etc/vsftpd/ftpusers
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN004950
- Vuln IDs
-
- V-22445
- Rule IDs
-
- SV-37544r1_rule
Checks: C-36200r1_chk
Check the permissions of the /etc/ftpusers file. # ls -lL /etc/ftpusers /etc/vsftpd.ftpusers /etc/vsftpd/ftpusers If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31459r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/ftpusers /etc/vsftpd.ftpusers /etc/vsftpd/ftpusers
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005190
- Vuln IDs
-
- V-22446
- Rule IDs
-
- SV-37682r1_rule
Checks: C-36869r2_chk
Check the file permissions for the .Xauthority files. These files will be located in user home directories. Procedure: # ls -la ~username |egrep "(\.Xauthority|\.xauth)" If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-31834r1_fix
Remove the extended ACL from the file. # setfacl --remove-all .Xauthority
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001435
- Version
- GEN005305
- Vuln IDs
-
- V-22447
- Rule IDs
-
- SV-37692r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31966r1_fix
Edit /etc/snmpd.conf and remove references to the "v1", "v2c", "community", or "com2sec". Restart the SNMP service. # service snmpd restart
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001453
- Version
- GEN005306
- Vuln IDs
-
- V-22448
- Rule IDs
-
- SV-37693r1_rule
Checks: C-36890r1_chk
Verify the SNMP daemon uses SHA for SNMPv3 users. Procedure: Examine the default install location /etc/snmp/snmpd.conf or: # find / -name snmpd.conf # grep -v '^#' <snmpd.conf file> | grep -i createuser | grep -vi SHA If any line is present this is a finding.
Fix: F-31971r1_fix
Edit /etc/snmp/snmpd.conf and add the SHA keyword for any create user statement without one. Restart the SNMP service. # service snmpd restart
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-000068
- Version
- GEN005307
- Vuln IDs
-
- V-22449
- Rule IDs
-
- SV-37695r1_rule
Checks: C-36891r1_chk
Verify the SNMP daemon uses AES for SNMPv3 users. Procedure: Examine the default install location /etc/snmp/snmpd.conf or: # find / -name snmpd.conf # grep -v '^#' <snmpd.conf file> | grep -i createuser | grep -vi AES If any line is present this is a finding.
Fix: F-31986r1_fix
Edit /etc/snmp/snmpd.conf and add the AES keyword for any create user statement without one. Restart the SNMP service. # service snmpd restart
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005350
- Vuln IDs
-
- V-22450
- Rule IDs
-
- SV-37700r1_rule
Checks: C-36895r1_chk
Check the file permissions for the MIB files. # find / -name *.mib # ls -lL <mib file> If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32014r1_fix
Remove the extended ACL from the file. # setfacl --remove-all <mib file>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005365
- Vuln IDs
-
- V-22451
- Rule IDs
-
- SV-37704r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32038r1_fix
Change the group ownership of the SNMP configuration file. Procedure: # chgrp root <snmpd.conf>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005375
- Vuln IDs
-
- V-22452
- Rule IDs
-
- SV-37706r1_rule
Checks: C-36900r1_chk
Check the permissions of the SNMP configuration file. Procedure: Examine the default install location /etc/snmp/snmpd.conf or: # find / -name snmpd.conf # ls -lL <snmpd.conf> If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32047r1_fix
Remove the extended ACL from the file. # setfacl --remove-all <snmpd.conf file>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005390
- Vuln IDs
-
- V-22453
- Rule IDs
-
- SV-37709r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32082r1_fix
Change the permissions of the syslog configuration file. # chmod 0640 /etc/syslog.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005395
- Vuln IDs
-
- V-22454
- Rule IDs
-
- SV-37710r1_rule
Checks: C-36909r1_chk
Check the permissions of the syslog configuration file. # ls -lL /etc/syslog.conf If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32087r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/syslog.conf
- RMF Control
- AU-3
- Severity
- M
- CCI
- CCI-000136
- Version
- GEN005450
- Vuln IDs
-
- V-22455
- Rule IDs
-
- SV-37811r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32277r1_fix
Edit the syslog configuration file and add an appropriate remote syslog server.
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001436
- Version
- GEN005501
- Vuln IDs
-
- V-22456
- Rule IDs
-
- SV-37820r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32289r1_fix
Edit the /etc/ssh/ssh_config file and add or edit a "Protocol" configuration line not allowing versions less than 2.
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-000069
- Version
- GEN005504
- Vuln IDs
-
- V-22457
- Rule IDs
-
- SV-37823r2_rule
Checks: C-37024r2_chk
Ask the SA to identify which interfaces on the system are designated for management traffic. If all interfaces on the system are authorized for management traffic, this is not applicable. Check the SSH daemon configuration for listening network addresses. # grep -i Listen /etc/ssh/sshd_config | grep -v '^#' If no configuration is returned, or if a returned 'Listen' configuration contains addresses not designated for management traffic, this is a finding.
Fix: F-32292r2_fix
Edit the SSH daemon configuration to specify listening network addresses designated for management traffic. Restart the SSH daemon. # /sbin/service sshd restart
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-000068
- Version
- GEN005505
- Vuln IDs
-
- V-22458
- Rule IDs
-
- SV-37824r3_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32293r4_fix
Edit the SSH daemon configuration and remove any ciphers not starting with "3des" or "aes" and remove any ciphers ending with "cbc". If necessary, add a "Ciphers" line. Ciphers aes256-ctr,aes192-ctr,aes128-ctr Restart the SSH daemon. # /sbin/service sshd restart
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005506
- Vuln IDs
-
- V-22459
- Rule IDs
-
- SV-26752r2_rule
Checks: C-27761r1_chk
Check the SSH daemon configuration for allowed ciphers. # grep -i ciphers /etc/ssh/sshd_config | grep -v '^#' If no lines are returned, or the returned ciphers list contains any cipher ending with cbc, this is a finding.
Fix: F-24001r2_fix
Edit /etc/ssh/sshd_config and add or edit the "Ciphers" line. Only include ciphers that start with "3des" or "aes" and do not contain "cbc". For the list of available ciphers for the particular version of your software, consult the sshd_config manpage. Restart the SSH daemon.
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001453
- Version
- GEN005507
- Vuln IDs
-
- V-22460
- Rule IDs
-
- SV-37826r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32294r2_fix
Edit the SSH daemon configuration and remove any MACs other than "hmac-sha1". If necessary, add a "MACs" line. Restart the SSH daemon. # /sbin/service sshd restart
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-000068
- Version
- GEN005510
- Vuln IDs
-
- V-22461
- Rule IDs
-
- SV-37828r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32297r2_fix
Edit the SSH client configuration and remove any ciphers not starting with "3des" or "aes" and remove any ciphers ending with "cbc". If necessary, add a "Ciphers" line.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005511
- Vuln IDs
-
- V-22462
- Rule IDs
-
- SV-37830r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32298r2_fix
Edit the SSH client configuration and remove any ciphers not starting with "3des" or "aes" and remove any ciphers ending with "cbc". If necessary, add a "Ciphers" line.
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001453
- Version
- GEN005512
- Vuln IDs
-
- V-22463
- Rule IDs
-
- SV-37836r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32301r1_fix
Edit the SSH client configuration and remove any MACs other than "hmac-sha1". If necessary, add a "MACs" line.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005521
- Vuln IDs
-
- V-22470
- Rule IDs
-
- SV-37843r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32309r2_fix
Edit the SSH daemon configuration and add an "AllowGroups" or "AllowUsers" directive specifying the groups and users allowed to have access. Restart the SSH daemon. # /sbin/service sshd restart Alternatively, modify the /etc/pam.d/sshd file to include the line account required pam_access.so accessfile=<path to access.conf for sshd> If the "accessfile" option is not specified the default "access.conf" file will be used. The "access.conf" file must contain the user restriction definitions.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005522
- Vuln IDs
-
- V-22471
- Rule IDs
-
- SV-37844r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32310r1_fix
Change the permissions for the SSH public host key files. # chmod 0644 /etc/ssh/*key.pub
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005523
- Vuln IDs
-
- V-22472
- Rule IDs
-
- SV-37863r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32347r1_fix
Change the permissions for the SSH private host key files. # chmod 0600 /etc/ssh/*key
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN005524
- Vuln IDs
-
- V-22473
- Rule IDs
-
- SV-37866r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32342r2_fix
Edit the SSH daemon configuration and set (add if necessary) a "GSSAPIAuthentication" directive set to "no". Restart the SSH daemon. # /sbin/service sshd restart
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN005525
- Vuln IDs
-
- V-22474
- Rule IDs
-
- SV-37868r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32356r1_fix
Edit the SSH client configuration and set the GSSAPIAuthentication" directive set to "no".
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN005526
- Vuln IDs
-
- V-22475
- Rule IDs
-
- SV-37872r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32363r2_fix
Edit the SSH daemon configuration and set (add if necessary) the "KerberosAuthentication" directive set to "no". Restart the SSH daemon. # /sbin/service sshd restart
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005536
- Vuln IDs
-
- V-22485
- Rule IDs
-
- SV-37900r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32394r2_fix
Edit the SSH daemon configuration and add or edit the "StrictModes" setting value to "yes". Restart the SSH daemon. # /sbin/service sshd restart
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005537
- Vuln IDs
-
- V-22486
- Rule IDs
-
- SV-37904r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32398r2_fix
Edit the SSH daemon configuration and add or edit the "UsePrivilegeSeparation" setting value to "yes". Restart the SSH daemon. # /sbin/service sshd restart
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005538
- Vuln IDs
-
- V-22487
- Rule IDs
-
- SV-37905r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32399r2_fix
Edit the SSH daemon configuration and add or edit the "RhostsRSAAuthentication" setting value to "no". Restart the SSH daemon. # /sbin/service sshd restart
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005539
- Vuln IDs
-
- V-22488
- Rule IDs
-
- SV-37908r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32403r2_fix
Edit the SSH daemon configuration and add or edit the "Compression" setting value to "no" or "delayed". Restart the SSH daemon. # /sbin/service sshd restart
- RMF Control
- AC-8
- Severity
- M
- CCI
- CCI-000048
- Version
- GEN005550
- Vuln IDs
-
- V-22489
- Rule IDs
-
- SV-37915r3_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32408r3_fix
Edit /etc/issue and the DoD login banner. DoD Login Banners: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests- -not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. OR I've read & consent to terms in IS user agreem't. Find the location of the banner file for sshd and examine the content: # grep -i banner /etc/ssh/sshd_config | grep -v '^#' # cat Edit the SSH daemon configuration and add or edit a "Banner" setting referencing a file containing a logon warning banner. Restart the SSH daemon. # /sbin/service sshd restart
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005570
- Vuln IDs
-
- V-22490
- Rule IDs
-
- SV-37921r1_rule
Checks: C-37153r1_chk
Check for a default route for IPv6. If the system is a VM host and acts as a router solely for the benefit of its client systems, then this rule is not applicable. # ip -6 route list | grep default If the system uses IPv6, and no results are returned, this is a finding.
Fix: F-24048r1_fix
Add a default route for IPv6. Edit /etc/sysconfig/network-scripts/ifcfg-eth0 (substitute interface as appropriate). Add an IPV6_DEFAULTGW=<gateway> configuration setting. Restart the interface. # ifdown eth0; ifup eth0
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005610
- Vuln IDs
-
- V-22491
- Rule IDs
-
- SV-37930r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32423r1_fix
Disable IPv6 forwarding. Edit /etc/sysctl.conf and add a setting for "net.ipv6.conf.all.forwarding=0" and "net.ipv6.conf.default.forwarding=0". Reload the sysctls. Procedure: # sysctl -p
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005750
- Vuln IDs
-
- V-22492
- Rule IDs
-
- SV-37940r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32431r1_fix
Change the group ownership of the NFS export configuration file. Procedure: # chgrp root /etc/exports
- RMF Control
- AC-6
- Severity
- L
- CCI
- CCI-000225
- Version
- GEN005770
- Vuln IDs
-
- V-22493
- Rule IDs
-
- SV-37947r1_rule
Checks: C-37232r1_chk
Check the permissions of the NFS export configuration file. # ls -lL /etc/exports If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32439r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/exports
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN005810
- Vuln IDs
-
- V-22496
- Rule IDs
-
- SV-37851r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32314r1_fix
Change the group owner of the export directory. # chgrp root <export>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006150
- Vuln IDs
-
- V-22497
- Rule IDs
-
- SV-37877r1_rule
Checks: C-37098r1_chk
Check the permissions of the Samba configuration file. # ls -lL /etc/samba/smb.conf If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32372r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/samba/smb.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006210
- Vuln IDs
-
- V-22498
- Rule IDs
-
- SV-37884r1_rule
Checks: C-37109r1_chk
Check the permissions of the Samba password files. Procedure: # ls -lL /etc/samba/passdb.tdb /etc/samba/secrets.tdb If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32377r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/samba/passdb.tdb /etc/samba/secrets.tdb
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN006225
- Vuln IDs
-
- V-22499
- Rule IDs
-
- SV-37891r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32385r1_fix
Edit the "/etc/samba/smb.conf" file and change the "security" setting to "user" or another valid setting other than "share".
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN006230
- Vuln IDs
-
- V-22500
- Rule IDs
-
- SV-37894r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32388r1_fix
Edit the "/etc/samba/smb.conf" file and change the "encrypt passwords" setting to "yes".
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN006235
- Vuln IDs
-
- V-22501
- Rule IDs
-
- SV-37896r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32390r1_fix
Edit the "/etc/samba/smb.conf" file and change the "guest ok" setting to "no".
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006270
- Vuln IDs
-
- V-22502
- Rule IDs
-
- SV-37902r2_rule
Checks: C-37128r2_chk
Check the permissions of the file. # ls -lL /etc/news/incoming.conf If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32396r2_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/news/incoming.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006290
- Vuln IDs
-
- V-22503
- Rule IDs
-
- SV-37713r1_rule
Checks: C-36914r1_chk
Check the permissions for "/etc/news/hosts.nntp.nolimit". # ls -lL /etc/news/hosts.nntp.nolimit If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32132r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/news/hosts.nntp.nolimit
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006310
- Vuln IDs
-
- V-22504
- Rule IDs
-
- SV-37730r1_rule
Checks: C-36926r1_chk
Check the permissions of the file. # ls -lL /etc/news/nnrp.access If the permissions include a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32191r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/news/nnrp.access
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN006330
- Vuln IDs
-
- V-22505
- Rule IDs
-
- SV-37733r1_rule
Checks: C-36929r1_chk
Check the permissions of the file. # ls -lL /etc/news/passwd.nntp If the mode includes a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32194r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/news/passwd.nntp
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN006565
- Vuln IDs
-
- V-22506
- Rule IDs
-
- SV-37751r2_rule
Checks: C-36948r3_chk
Check the root crontab (crontab -l) and the global crontabs in "/etc/crontab", "/etc/cron.*" for the presence of an rpm verification command such as: rpm -qVa | awk '$2!="c" {print $0}' If no such cron job is found, this is a finding. If the result of the cron job indicates packages which do not pass verification exist, this is a finding unless the changes were made due to another STIG entry.
Fix: F-32212r1_fix
Add a cron job to run an rpm verification command such as: rpm -qVa | awk '$2!="c" {print $0}' For packages which failed verification: If the package is not necessary for operations, remove it from the system. If the package is necessary for operations, re-install the package.
- RMF Control
- SI-7
- Severity
- L
- CCI
- CCI-001297
- Version
- GEN006570
- Vuln IDs
-
- V-22507
- Rule IDs
-
- SV-37752r1_rule
Checks: C-36950r1_chk
If using an Advanced Intrusion Detection Environment (AIDE), verify that the configuration contains the "ACL" option for all monitored files and directories. Procedure: Check for the default location /etc/aide/aide.conf or: # find / -name aide.conf # egrep "[+]?acl" <aide.conf file> If the option is not present. This is a finding. If using a different file integrity tool, check the configuration per tool documentation.
Fix: F-32214r1_fix
If using AIDE, edit the configuration and add the "ACL" option for all monitored files and directories. If using a different file integrity tool, configure ACL checking per the tool's documentation.
- RMF Control
- SI-7
- Severity
- L
- CCI
- CCI-001297
- Version
- GEN006571
- Vuln IDs
-
- V-22508
- Rule IDs
-
- SV-37753r1_rule
Checks: C-36951r1_chk
If using an Advanced Intrusion Detection Environment (AIDE), verify the configuration contains the "xattrs" option for all monitored files and directories. Procedure: Check for the default location /etc/aide/aide.conf or: # find / -name aide.conf # egrep "[+]?xattrs" <aide.conf file> If the option is not present. This is a finding. If using a different file integrity tool, check the configuration per tool documentation.
Fix: F-32215r1_fix
If using AIDE, edit the configuration and add the "xattrs" option for all monitored files and directories. If using a different file integrity tool, configure extended attributes checking per the tool's documentation.
- RMF Control
- SI-7
- Severity
- L
- CCI
- CCI-001297
- Version
- GEN006575
- Vuln IDs
-
- V-22509
- Rule IDs
-
- SV-37754r1_rule
Checks: C-36952r1_chk
If using an Advanced Intrusion Detection Environment (AIDE), verify the configuration contains the "sha256" or "sha512" options for all monitored files and directories. Procedure: Check for the default location /etc/aide/aide.conf or: # find / -name aide.conf # egrep "[+]?(sha256|sha512)" <aide.conf file> If the option is not present. This is a finding. If one of these options is not present. This is a finding. If using a different file integrity tool, check the configuration per tool documentation.
Fix: F-32217r1_fix
If using AIDE, edit the configuration and add the "sha512" option for all monitored files and directories. If using a different file integrity tool, configure FIPS 140-2 approved cryptographic hashes per the tool's documentation.
- RMF Control
- CM-7
- Severity
- M
- CCI
- CCI-000382
- Version
- GEN007020
- Vuln IDs
-
- V-22511
- Rule IDs
-
- SV-37761r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32222r1_fix
Prevent the SCTP protocol handler for dynamic loading. # echo "install sctp /bin/true" >> /etc/modprobe.conf
- RMF Control
- CM-7
- Severity
- M
- CCI
- CCI-000382
- Version
- GEN007080
- Vuln IDs
-
- V-22514
- Rule IDs
-
- SV-37763r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32223r1_fix
Prevent the DCCP protocol handler for dynamic loading. # echo "install dccp /bin/true" >> /etc/modprobe.conf # echo "install dccp_ipv4 /bin/true" >> /etc/modprobe.conf # echo "install dccp_ipv6 /bin/true" >> /etc/modprobe.conf
- RMF Control
- CM-7
- Severity
- M
- CCI
- CCI-000382
- Version
- GEN007260
- Vuln IDs
-
- V-22524
- Rule IDs
-
- SV-26887r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24130r1_fix
Prevent the AppleTalk protocol handler for dynamic loading. # echo "install appletalk /bin/true" >> /etc/modprobe.conf
- RMF Control
- CM-7
- Severity
- M
- CCI
- CCI-000382
- Version
- GEN007480
- Vuln IDs
-
- V-22530
- Rule IDs
-
- SV-37603r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31638r1_fix
Prevent the RDS protocol handler for dynamic loading. # echo "install rds /bin/true" >> /etc/modprobe.conf
- RMF Control
- CM-7
- Severity
- M
- CCI
- CCI-000382
- Version
- GEN007540
- Vuln IDs
-
- V-22533
- Rule IDs
-
- SV-37604r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31639r1_fix
Prevent the TIPC protocol handler for dynamic loading. # echo "install tipc /bin/true" >> /etc/modprobe.conf
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN007660
- Vuln IDs
-
- V-22539
- Rule IDs
-
- SV-37605r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31640r1_fix
Prevent the Bluetooth protocol handler for dynamic loading. # echo "install bluetooth /bin/true" >> /etc/modprobe.conf
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN007700
- Vuln IDs
-
- V-22541
- Rule IDs
-
- SV-37606r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31643r1_fix
Remove the capability to use IPv6 protocol handler. Procedure: Edit /etc/sysconfig/network and change NETWORKING_IPV6=yes to NETWORKING_IPV6=no Edit /etc/modprobe.conf and add these lines (if they are not in it): alias net-pf-10 off alias ipv6 off Stop the ipv6tables service by typing: service ip6tables stop Disable the ipv6tables service by typing: chkconfig ip6tables off Remove the ipv6 kernel module # rmmod ipv6 Reboot
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN007720
- Vuln IDs
-
- V-22542
- Rule IDs
-
- SV-37609r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31644r1_fix
Prevent the IPv6 protocol handler for dynamic loading. # echo "install ipv6 /bin/true" >> /etc/modprobe.conf
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN007780
- Vuln IDs
-
- V-22545
- Rule IDs
-
- SV-37610r1_rule
Checks: C-36796r1_chk
Check the system for any active 6to4 tunnels without specific remote addresses. # ip tun list | grep "remote any" | grep "ipv6/ip" If any results are returned the "tunnel" is the first field. If any results are returned, this is a finding.
Fix: F-31646r1_fix
Disable the active 6to4 tunnel. # ip link set <tunnel> down Add this command to a startup script, or remove the configuration creating the tunnel.
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN007800
- Vuln IDs
-
- V-22546
- Rule IDs
-
- SV-37611r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31647r1_fix
Edit startup scripts to prevent the service from running on startup.
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN007820
- Vuln IDs
-
- V-22547
- Rule IDs
-
- SV-37613r1_rule
Checks: C-36809r1_chk
Check for any IP tunnels. # ip tun list # ip -6 tun list If any tunnels are listed, this is a finding.
Fix: F-31648r1_fix
Remove the tunnels. # ip tun del <tunnel> Edit system startup scripts to prevent tunnel creation on startup.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN007840
- Vuln IDs
-
- V-22548
- Rule IDs
-
- SV-37615r1_rule
Checks: C-36811r1_chk
Verify no interface is configured to use DHCP. # grep -i bootproto=dhcp /etc/sysconfig/network-scripts/ifcfg-* If any configuration is found, this is a finding.
Fix: F-24173r1_fix
Edit the "/etc/sysconfig/network-scripts/ifcfg-*" file(s) and change the "bootproto" setting to "static".
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN007850
- Vuln IDs
-
- V-22549
- Rule IDs
-
- SV-26933r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24178r1_fix
Edit or add the "/etc/dhclient.conf" file and add or edit the "do-forward-updates" setting to false. Procedure: # echo "do-forward-updates false;" >> /etc/dhclient.conf
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN007860
- Vuln IDs
-
- V-22550
- Rule IDs
-
- SV-37616r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31651r1_fix
Configure the system to ignore IPv6 ICMP redirect messages. Edit "/etc/sysctl.conf" and add a settings for "net.ipv6.conf.default.accept_redirects=0" and "net.ipv6.conf.all.accept_redirects=0". Restart the system for the setting to take effect.
- RMF Control
- AC-4
- Severity
- M
- CCI
- CCI-001551
- Version
- GEN007920
- Vuln IDs
-
- V-22553
- Rule IDs
-
- SV-37618r1_rule
Checks: C-36815r1_chk
Determine if the system is configured to forward IPv6 source-routed packets. Procedure: # egrep "net.ipv6.conf.*forwarding" /etc/sysctl.conf If there are no entries found or the value of the entries is not = "0", this is a finding.
Fix: F-31656r1_fix
Configure the system to not forward IPv6 source-routed packets. Procedure: Edit the /etc/sysctl.conf file to include: net.ipv6.conf.all.forwarding = 0 net.ipv6.conf.default.forwarding = 0 Reload the kernel parameters: # sysctl -p
- RMF Control
- AC-17
- Severity
- M
- CCI
- CCI-001453
- Version
- GEN007980
- Vuln IDs
-
- V-22555
- Rule IDs
-
- SV-37627r1_rule
Checks: C-36827r2_chk
Check if the system is using NSS LDAP. # grep -v '^#' /etc/nsswitch.conf | grep ldap If no lines are returned, this vulnerability is not applicable. Check if NSS LDAP is using TLS. # grep '^ssl start_tls' /etc/ldap.conf If no lines are returned, this is a finding. Check if NSS LDAP TLS is using only FIPS 140-2 approved cryptographic algorithms. # grep '^tls_ciphers' /etc/ldap.conf If the line is not present, or contains ciphers not approved by FIPS 140-2, this is a finding. FIPS approved ciphers include 3DES and AES. FIPS approved hashes include the SHA hash family.
Fix: F-31665r1_fix
Edit "/etc/ldap.conf" and add a "ssl start_tls" and "tls_ciphers" options with only FIPS 140-2 approved ciphers.
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000185
- Version
- GEN008000
- Vuln IDs
-
- V-22556
- Rule IDs
-
- SV-37631r1_rule
Checks: C-36829r1_chk
Verify the source of the LDAP certificates Check if the system is using NSS LDAP. # grep -v '^#' /etc/nsswitch.conf | grep ldap If no lines are returned, this vulnerability is not applicable. Verify with the SA that the system is connected to the GIG. If the system part of a stand alone network which is not connected to the GIG this vulnerability is not applicable. Verify a certificate is used for client authentication to the server. # grep -i '^tls_cert' /etc/ldap.conf If no line is found, this is a finding. List the certificate issuer. # openssl x509 -text -in <cert> If the certificate is not issued by DoD PKI or a DoD-approved external PKI, this is a finding.
Fix: F-31668r1_fix
Edit "/etc/ldap.conf" and add or edit the 'tls_cert' setting to reference a file containing a client certificate issued by DoD PKI or a DoD-approved external PKI.
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000185
- Version
- GEN008020
- Vuln IDs
-
- V-22557
- Rule IDs
-
- SV-37632r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31669r1_fix
Edit "/etc/ldap.conf" and add or set the "tls_checkpeer" setting to "yes".
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000185
- Version
- GEN008040
- Vuln IDs
-
- V-22558
- Rule IDs
-
- SV-37634r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31672r1_fix
Edit "/etc/ldap.conf" and add or set the "tls_crlcheck" setting to "all".
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008060
- Vuln IDs
-
- V-22559
- Rule IDs
-
- SV-37951r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32441r1_fix
Change the permissions of the file. # chmod 0644 /etc/ldap.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008080
- Vuln IDs
-
- V-22560
- Rule IDs
-
- SV-37953r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32442r1_fix
Change the owner of the file. # chown root /etc/ldap.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008100
- Vuln IDs
-
- V-22561
- Rule IDs
-
- SV-37955r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32444r1_fix
Change the group owner of the file to root, bin, sys, or system. Procedure: # chgrp root /etc/ldap.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008120
- Vuln IDs
-
- V-22562
- Rule IDs
-
- SV-37956r1_rule
Checks: C-37245r1_chk
Check the permissions of the file. # ls -lL /etc/ldap.conf If the mode includes a '+', the file has an extended ACL. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32445r1_fix
Remove the extended ACL from the "/etc/ldap.conf" file. # setfacl --remove-all /etc/ldap.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008140
- Vuln IDs
-
- V-22563
- Rule IDs
-
- SV-37959r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32446r1_fix
Change the ownership of the file or directory. # chown root <certpath>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008160
- Vuln IDs
-
- V-22564
- Rule IDs
-
- SV-37961r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32447r1_fix
Change the group ownership of the file or directory. # chgrp root <certpath>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008180
- Vuln IDs
-
- V-22565
- Rule IDs
-
- SV-37962r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32448r1_fix
Change the mode of the file or directory. File Procedure: # chmod 0644 <certpath> Directory Procedure: # chmod 0755 <certpath>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008200
- Vuln IDs
-
- V-22566
- Rule IDs
-
- SV-37964r1_rule
Checks: C-37262r1_chk
Determine the certificate authority file and/or directory. # grep -i '^tls_cacert' /etc/ldap.conf For each file or directory returned, check the permissions. # ls -lLd <certpath> If the mode of the file or directory contains a '+', an extended ACL is present. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32461r1_fix
Remove the extended ACL from the certificate file. Procedure: For each certificate file found remove all extended permissions # setfacl --remove-all <certpath>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008220
- Vuln IDs
-
- V-22567
- Rule IDs
-
- SV-37965r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32470r1_fix
Change the ownership of the file. # chown root <certpath>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008240
- Vuln IDs
-
- V-22568
- Rule IDs
-
- SV-37967r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32501r1_fix
Change the group ownership of the file. Procedure: # chgrp root <certpath>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008260
- Vuln IDs
-
- V-22569
- Rule IDs
-
- SV-37966r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32487r1_fix
Change the mode of the file. # chmod 0644 <certpath>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008280
- Vuln IDs
-
- V-22570
- Rule IDs
-
- SV-37968r1_rule
Checks: C-37266r1_chk
Determine the certificate file. # grep -i '^tls_cert' /etc/ldap.conf Check the permissions. # ls -lL <certpath> If the mode of the file contains a '+', an extended ACL is present. This is a finding.
Fix: F-32502r1_fix
Remove the extended ACL from the certificate file. Procedure: For each certificate file found remove all extended permissions. # setfacl --remove-all <certpath>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008300
- Vuln IDs
-
- V-22571
- Rule IDs
-
- SV-37969r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32503r1_fix
Change the ownership of the file. # chown root <keypath>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008320
- Vuln IDs
-
- V-22572
- Rule IDs
-
- SV-37971r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32505r1_fix
Change the group ownership of the file. # chgrp root <keypath>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008340
- Vuln IDs
-
- V-22573
- Rule IDs
-
- SV-37973r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32506r1_fix
Change the mode of the file. # chmod 0600 <keypath>
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008360
- Vuln IDs
-
- V-22574
- Rule IDs
-
- SV-37977r1_rule
Checks: C-37272r3_chk
Determine the key file. # grep -i '^tls_key' /etc/ldap.conf Check the permissions. # ls -lL <keypath> If the permissions of the file contains a '+', an extended ACL is present. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-32509r1_fix
Remove the extended ACL from the key file. Procedure: For each key file found remove all extended permissions. # setfacl --remove-all <keypath>
- RMF Control
- SC-28
- Severity
- M
- CCI
- CCI-001199
- Version
- GEN008380
- Vuln IDs
-
- V-22575
- Rule IDs
-
- SV-37978r1_rule
Checks: C-37274r1_chk
Ask the SA if a root kit check tool is run on the system weekly. If this is not performed, this is a finding.
Fix: F-32511r1_fix
Create an automated job or establish a site-defined procedure to check the system weekly with a root kit check tool.
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN008420
- Vuln IDs
-
- V-22576
- Rule IDs
-
- SV-37979r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32513r1_fix
Edit the kernel boot parameters, or "/etc/sysctl.conf", and set exec-shield to "1". Reboot the system.
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN008440
- Vuln IDs
-
- V-22577
- Rule IDs
-
- SV-37980r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32515r1_fix
Stop and disable the autofs service. # service autofs stop # chkconfig autofs off
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN008460
- Vuln IDs
-
- V-22578
- Rule IDs
-
- SV-37981r1_rule
Checks: C-37280r1_chk
If the system needs USB, this vulnerability is not applicable. Check if the directory "/proc/bus/usb" exists. If so, this is a finding.
Fix: F-32517r1_fix
Edit the grub bootloader file "/boot/grub/grub.conf" or "/boot/grub/menu.lst" by appending the "nousb" parameter to the kernel boot line.
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN008480
- Vuln IDs
-
- V-22579
- Rule IDs
-
- SV-37982r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32519r1_fix
Prevent the usb-storage module from loading. # echo 'install usb-storage /bin/true' >> /etc/modprobe.conf
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN008500
- Vuln IDs
-
- V-22580
- Rule IDs
-
- SV-37983r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32520r1_fix
Prevent the system from loading the firewire module. # echo 'install ieee1394 /bin/true' >> /etc/modprobe.conf
- RMF Control
- SC-7
- Severity
- M
- CCI
- CCI-001118
- Version
- GEN008520
- Vuln IDs
-
- V-22582
- Rule IDs
-
- SV-37984r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32522r1_fix
Enable the system's local firewall. # chkconfig iptables on # service iptables start
- RMF Control
- SC-7
- Severity
- M
- CCI
- CCI-001109
- Version
- GEN008540
- Vuln IDs
-
- V-22583
- Rule IDs
-
- SV-37985r1_rule
Checks: C-37287r3_chk
Check the firewall rules for a default deny rule. # iptables --list Example of a rule meeting this criteria: REJECT all -- anywhere anywhere reject-with icmp-host-prohibited A rule using DROP is also acceptable. The default rule should be the last rule of a table and match all traffic. If there is no default deny rule, this is a finding.
Fix: F-32525r2_fix
Edit "/etc/sysconfig/iptables" and add a default deny rule. An example of a default deny rule: -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited Restart the iptable service. # service iptables restart
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN000000-LNX00800
- Vuln IDs
-
- V-22584
- Rule IDs
-
- SV-26978r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31279r2_fix
Enable one of the SELinux policies. Edit /etc/sysconfig/selinux and set the value of the SELINUX option to "enforcing" and SELINUXTYPE to "targeted" or "strict". Restart the system.
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008740
- Vuln IDs
-
- V-22585
- Rule IDs
-
- SV-26984r1_rule
Checks: C-37229r3_chk
Check the permissions of the file. # ls -lL /boot/grub/grub.conf If the permissions of the file or directory contains a '+', an extended ACL is present. This is a finding.
Fix: F-24248r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/grub.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008760
- Vuln IDs
-
- V-22586
- Rule IDs
-
- SV-26986r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32438r1_fix
Change the ownership of the file. # chown root /boot/grub/grub.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN008780
- Vuln IDs
-
- V-22587
- Rule IDs
-
- SV-26988r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32443r1_fix
Change the group ownership of the file. # chgrp root /boot/grub/grub.conf
- RMF Control
- CM-5
- Severity
- L
- CCI
- CCI-000351
- Version
- GEN008800
- Vuln IDs
-
- V-22588
- Rule IDs
-
- SV-26990r1_rule
Checks: C-27933r2_chk
Verify RPM signature validation is not disabled. # grep nosignature /etc/rpmrc /usr/lib/rpm/rpmrc /usr/lib/rpm/redhat/rpmrc ~root/.rpmrc If any configuration is found, this is a finding. Verify YUM signature validation is not disabled. # grep gpgcheck /etc/yum.conf /etc/yum.repos.d/* If any "gpgcheck" setting is returned that is not equal to "1", this is a finding.
Fix: F-24256r1_fix
Edit the RPM configuration file containing the "nosignature" option and remove the option. Edit the YUM configuration containing "gpgcheck=0" and set the value to "1".
- RMF Control
- SI-2
- Severity
- L
- CCI
- CCI-001233
- Version
- GEN008820
- Vuln IDs
-
- V-22589
- Rule IDs
-
- SV-26992r1_rule
Checks: C-27935r1_chk
Verify the YUM service is enabled. # service yum-updatesd status If the service is enabled, this is a finding.
Fix: F-24258r1_fix
Disable the yum service. # chkconfig yum-updatesd off ; service yum-updatesd stop
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00450
- Vuln IDs
-
- V-22595
- Rule IDs
-
- SV-26998r1_rule
Checks: C-35941r3_chk
Check the permissions of the file. # ls -lL /etc/security/access.conf If the permissions of the file or directory contain a '+', an extended ACL is present. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-24264r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/security/access.conf
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN000000-LNX00530
- Vuln IDs
-
- V-22596
- Rule IDs
-
- SV-26999r1_rule
Checks: C-35992r3_chk
Check the permissions of the file. # ls -lL /etc/sysctl.conf If the permissions of the file or directory contain a '+', an extended ACL is present. If the file has an extended ACL and it has not been documented with the IAO, this is a finding.
Fix: F-24265r1_fix
Remove the extended ACL from the file. # setfacl --remove-all /etc/sysctl.conf
- RMF Control
- CM-6
- Severity
- L
- CCI
- CCI-000366
- Version
- GEN000000-LNX00720
- Vuln IDs
-
- V-22598
- Rule IDs
-
- SV-27001r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31278r1_fix
Edit the grub bootloader file /boot/grub/grub.conf or /boot/grub/menu.lst by appending the "audit=1" parameter to the kernel boot line. Reboot the system for the change to take effect.
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN005590
- Vuln IDs
-
- V-22665
- Rule IDs
-
- SV-37926r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32420r1_fix
Disable any routing protocol daemons.
- RMF Control
- AU-9
- Severity
- M
- CCI
- CCI-000162
- Version
- GEN002690
- Vuln IDs
-
- V-22702
- Rule IDs
-
- SV-37914r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-24520r1_fix
Change the group ownership of the audit log file(s). Procedure: # chgrp root <audit log file>
- RMF Control
- AC-8
- Severity
- M
- CCI
- CCI-000048
- Version
- GEN000410
- Vuln IDs
-
- V-23732
- Rule IDs
-
- SV-28606r1_rule
Checks: C-35878r1_chk
FTP to the system. # ftp localhost Check for either of the following login banners based on the character limitations imposed by the system. An exact match is required. If one of these banners is not displayed, this is a finding. If the system does not run the FTP service, this is not applicable. DoD Login Banners: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. OR I've read & consent to terms in IS user agreem't.
Fix: F-25878r2_fix
Provide the proper text for the DoD banner to be presented by the FTP server to the user. For vsftp: Examine the /etc/vsftp.conf file for the "banner_file" entry. (i.e. banner_file = /etc/banner/vsftp) For gssftp: Examine the /etc/xinetd.d/gssftp file for the "banner" entry. (i.e. banner = /etc/banner/gssftp) For both: Add the banner entry if one is not found. Modify or create the referenced banner file to contain one of the following DoD login banners (based on the character limitations imposed by the system). DoD Login Banners: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. OR I've read & consent to terms in IS user agreem't.
- RMF Control
- SC-32
- Severity
- L
- CCI
- CCI-001208
- Version
- GEN003621
- Vuln IDs
-
- V-23736
- Rule IDs
-
- SV-37641r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31676r1_fix
Migrate the /var path onto a separate file system.
- RMF Control
- SC-32
- Severity
- L
- CCI
- CCI-001208
- Version
- GEN003623
- Vuln IDs
-
- V-23738
- Rule IDs
-
- SV-37642r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31677r1_fix
Migrate the /var/log/audit path onto a separate filesystem.
- RMF Control
- SC-32
- Severity
- L
- CCI
- CCI-001208
- Version
- GEN003624
- Vuln IDs
-
- V-23739
- Rule IDs
-
- SV-37395r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31325r1_fix
Migrate the /tmp path onto a separate file system.
- RMF Control
- Severity
- M
- CCI
- Version
- GEN003601
- Vuln IDs
-
- V-23741
- Rule IDs
-
- SV-37594r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31631r1_fix
Edit /etc/sysctl.conf and add a setting for "net.ipv4.tcp_max_syn_backlog=1280". Procedure: # sysctl -p
- RMF Control
- SI-8
- Severity
- M
- CCI
- CCI-001305
- Version
- GEN004710
- Vuln IDs
-
- V-23952
- Rule IDs
-
- SV-37514r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31424r2_fix
If the system uses sendmail, edit the sendmail.mc file and remove the "promiscuous_relay" configuration. Rebuild the sendmail.cf file from the modified sendmail.mc and restart the service. If the system does not need to receive mail from external hosts, add one or more DaemonPortOptions lines referencing system loopback addresses (such as "O DaemonPortOptions=Addr=127.0.0.1,Port=smtp,Name=MTA") and remove lines containing non-loopback addresses. Restart the service. If the system uses Postfix, edit the main.cf file and add or edit the "smtpd_client_restrictions" line to have contents "permit_mynetworks, reject" or a similarly restrictive rule. If the system does not need to receive mail from external hosts, add or edit the "inet_interfaces" line to have contents "loopback-only" or a set of loopback addresses for the system. Restart the service. If the system is using other SMTP software, consult the software's documentation for procedures to restrict mail relaying.
- RMF Control
- CM-2
- Severity
- M
- CCI
- CCI-000305
- Version
- GEN007960
- Vuln IDs
-
- V-23953
- Rule IDs
-
- SV-37621r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31658r1_fix
Remove the execute permissions from the 'ldd' executable. Procedure: # chmod a-x /usr/bin/ldd
- RMF Control
- CM-6
- Severity
- M
- CCI
- CCI-000366
- Version
- GEN007950
- Vuln IDs
-
- V-23972
- Rule IDs
-
- SV-29788r1_rule
Checks: C-30069r1_chk
Check for an iptables rule that drops inbound IPv6 ICMP ECHO_REQUESTs sent to the all-hosts multicast address. Procedure: # less /etc/sysconfig/ip6tables Check for a rule in, or referenced by, the INPUT chain such as: -A INPUT -p icmpv6 -d ff02::1 --icmpv6-type 128 -j DROP If such a rule does not exist, this is a finding.
Fix: F-26899r1_fix
Add an iptables rule that drops inbound IPv6 ICMP ECHO_REQUESTs sent to the all-hosts multicast address. Edit /etc/sysconfig/ip6tables and add a rule in, or referenced by, the INPUT chain such as: -A INPUT -p icmpv6 -d ff02::1 --icmpv6-type 128 -j DROP Reload the iptables rules. Procedure: # service ip6tables restart
- RMF Control
- AC-8
- Severity
- M
- CCI
- CCI-000048
- Version
- GEN000402
- Vuln IDs
-
- V-24331
- Rule IDs
-
- SV-37171r1_rule
Checks: C-35876r1_chk
Access the graphical desktop environment(s) provided by the system and attempt to log in. Check for either of the following login banners based on the character limitations imposed by the system. An exact match is required. If one of these banners is not displayed, this is a finding. You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests- -not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. OR I've read & consent to terms in IS user agreem't.
Fix: F-31131r1_fix
Configure the system to display one of the DoD login banners prior to, or as part of, the graphical desktop environment login process. Procedure: Modify /usr/share/gdm/themes/RHEL/RHEL.xml by adding the following xml after the first two "pixmap" entries. <item type="rect" id="custom-dod-banner"> <pos anchor="nw" x="20%" y="10" width="80%" height="100%"/> <box> <item type="label"> <normal font="Sans Bold 9" color="#ffffff"/> <text> Insert the "approved text" here based on the character limitations imposed by the system. </text> </item> </box> </item> Approved text: DoD Login Banners: You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only. By using this IS (which includes any device attached to this IS), you consent to the following conditions: -The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations. -At any time, the USG may inspect and seize data stored on this IS. -Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose. -This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy. -Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details. OR I've read & consent to terms in IS user agreem't.
- RMF Control
- IA-2
- Severity
- M
- CCI
- CCI-000768
- Version
- GEN009120
- Vuln IDs
-
- V-24347
- Rule IDs
-
- SV-30004r1_rule
Checks: C-30833r1_chk
Consult vendor documentation to determine if the system is capable of CAC authentication. If it is not, this is not applicable. Interview the SA to determine if all accounts not exempted by policy are using CAC authentication. If non-exempt accounts are not using CAC authentication, this is a finding.
Fix: F-27447r1_fix
Consult vendor documentation to determine the procedures necessary for configuring CAC authentication. Configure all accounts required by policy to use CAC authentication.
- RMF Control
- AU-3
- Severity
- L
- CCI
- CCI-000136
- Version
- GEN002870
- Vuln IDs
-
- V-24357
- Rule IDs
-
- SV-37948r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32440r1_fix
Configure the system to send audit records to a remote server. Procedure: These instructions assume a known remote audit server is available to this system. Modify /etc/syslog.conf to contain a line sending all audit records to a remote audit server. The server is specified by placing an "@" before the DNS name or IP address in the line. *.* @<remote audit server> Edit the "active" line in /etc/audisp/plugins.d/syslog.conf so it shows "active = yes". Restart audit and syslog: # service auditd restart # service syslog restart
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000196
- Version
- GEN008050
- Vuln IDs
-
- V-24384
- Rule IDs
-
- SV-37643r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31678r1_fix
Edit the "/etc/ldap.conf" file to use anonymous binding by removing the "bindpw" option.
- RMF Control
- IA-5
- Severity
- H
- CCI
- CCI-000197
- Version
- GEN003850
- Vuln IDs
-
- V-24386
- Rule IDs
-
- SV-37444r1_rule
Checks: C-36116r2_chk
The telnet service included in the RHEL distribution is part of krb5-workstation. There are two versions of telnetd server provided. The xinetd.d file ekrb5-telnet allows only connections authenticated through kerberos. The xinetd.d krb5-telnet allows normal telnet connections as well as kerberized connections. Both are set to "disable = yes" by default. Ensure that neither is running. Procedure: Check if telnetd is running: # ps -ef |grep telnetd If the telnet daemon is running, this is a finding. Check if telnetd is enabled on startup: # chkconfig --list|grep telnet If an entry with "on" is found, this is a finding.
Fix: F-31362r2_fix
Identify the telnet service running and disable it. Procedure: Disable the telnet server. # chkconfig telnet off Verify the telnet daemon is no longer running. # ps -ef |grep telnet
- RMF Control
- AC-3
- Severity
- M
- CCI
- CCI-000213
- Version
- GEN008710
- Vuln IDs
-
- V-24624
- Rule IDs
-
- SV-37938r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-27516r1_fix
Consult vendor documentation for procedures concerning the system's boot loader. Configure the boot loader to hash boot loader passwords using MD5 or a stronger hash.
- RMF Control
- CM-2
- Severity
- M
- CCI
- CCI-000293
- Version
- GEN000140-2
- Vuln IDs
-
- V-27250
- Rule IDs
-
- SV-34549r2_rule
Checks: C-37553r4_chk
Verify a system integrity baseline exists. The Advanced Intrusion Detection Environment (AIDE) is included in the distribution of RHEL. Other host intrusion detection system (HIDS) software is available but must be checked manually. Procedure: # grep DBDIR /etc/aide.conf If /etc/aide.conf does not exist AIDE has not been installed. Unless another HIDS is used on the system, this is a finding. Examine the response for "database" this indicates the location of the system integrity baseline database used as input to a comparison. # ls -la <DBDIR> If no "database" file as defined in /etc/aide.conf exists a system integrity baseline has not been created, this is a finding. Examine /etc/aide.conf to ensure some form of cryptographic hash (i.e. md5,rmd160,sha256) is used for files. In the default /etc/aide.conf the "NORMAL" or "LSPP" rules which are used for virtually all files DO include some form of cryptographic hash. If the site has defined rules to replace the functionality provided by the default "NORMAL" and "LSPP" rules but DOES NOT include cryptographic hashes, this is a finding. Otherwise, if any element used to define the "NORMAL" and "LSPP" rules has been modified resulting in cryptographic hashes not being used, this is a finding. If any other modification to the default /etc/aide.conf file have been made resulting in rules which do not include cryptographic hashes on appropriate files, this is a finding.
Fix: F-32799r4_fix
Use AIDE to create a file integrity baseline, including cryptographic hashes, for the system. Configure the /etc/aide.conf file to ensure some form of cryptographic hash (e.g., md5,rmd160,sha256) is used for files. In the default /etc/aide.conf the "NORMAL" or "LSPP" rules which are used for virtually all files DO include some form of cryptographic hash.
- RMF Control
- CM-2
- Severity
- M
- CCI
- CCI-000293
- Version
- GEN000140-3
- Vuln IDs
-
- V-27251
- Rule IDs
-
- SV-34550r1_rule
Checks: C-37565r1_chk
Verify a system integrity baseline is maintained. The baseline has been updated to be consistent with the latest approved system configuration changes. The Advanced Intrusion Detection Environment (AIDE) is included in the distribution of RHEL-5. Other host intrusion detection system (HIDS) software is available but must be checked manually. Procedure: # grep DBDIR /etc/aide.conf If /etc/aide.conf does not exist AIDE has not been installed. Unless another HIDS is used on the system, this is a finding. Examine the response for "database" indicates the location of the system integrity baseline database used as input to a comparison. # ls -la <DBDIR> If the no "database" file as defined in /etc/aide.conf a system integrity baseline has not been created, this is a finding. Ask the SA when the last approved system configuration changes occurred. If the modification date of the AIDE database is prior to the last approved configuration change, this is a finding.
Fix: F-32808r1_fix
Regularly rebuild the integrity baseline, including cryptographic hashes, for the system to be consistent with the latest approved system configuration. Procedure: After an approved modification to the system configuration has been made perform: # aide -u This will update the database.
- RMF Control
- AC-2
- Severity
- M
- CCI
- CCI-000012
- Version
- GEN000290-2
- Vuln IDs
-
- V-27275
- Rule IDs
-
- SV-34574r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-33038r1_fix
Remove the "news" account from the /etc/passwd file before connecting a system to the network.
- RMF Control
- AC-2
- Severity
- M
- CCI
- CCI-000012
- Version
- GEN000290-3
- Vuln IDs
-
- V-27276
- Rule IDs
-
- SV-34575r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-33039r1_fix
Remove the "gopher" account from the /etc/passwd file before connecting a system to the network.
- RMF Control
- AC-2
- Severity
- M
- CCI
- CCI-000012
- Version
- GEN000290-4
- Vuln IDs
-
- V-27279
- Rule IDs
-
- SV-34578r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-33040r1_fix
Remove the "ftp" account from the /etc/passwd file before connecting a system to the network.
- RMF Control
- AC-11
- Severity
- M
- CCI
- CCI-000057
- Version
- GEN000500-2
- Vuln IDs
-
- V-27283
- Rule IDs
-
- SV-48550r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-33041r1_fix
For the Gnome screen saver, set idle_delay to 15. Procedure: # gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type int --set /apps/gnome-screensaver/idle_delay 15
- RMF Control
- AC-11
- Severity
- M
- CCI
- CCI-000057
- Version
- GEN000500-3
- Vuln IDs
-
- V-27284
- Rule IDs
-
- SV-48551r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-33042r1_fix
For the Gnome screen saver, set the lock_enabled flag. Procedure: # gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set /apps/gnome-screensaver/lock_enabled true
- RMF Control
- IA-5
- Severity
- M
- CCI
- CCI-000192
- Version
- GEN000600-2
- Vuln IDs
-
- V-27285
- Rule IDs
-
- SV-34584r1_rule
Checks: C-37566r3_chk
Verify the system-auth settings are being applied. Procedure: Verify the additional pam.d requirements are in use. The file "/etc/pam.d/system-auth-ac" is auto generated by "authconfig". Any manual changes made to it will be lost next time "authconfig" is run. Check to see if the systems default of the symlink "/etc/pam.d/system-auth" pointing to "/etc/pam.d/system-auth-ac" has been changed. # ls -l /etc/pam.d/system-auth If the symlink points to "/etc/pam.d/system-auth-ac", manual changes cannot be protected. This is a finding. # grep system-auth-ac /etc/pam.d/system-auth The local system-auth file pointed to by "/etc/pam.d/system-auth" must contain "/etc/pam.d/system-auth-ac" for the auth, account, password, and session lines. If it does not then the parameters maintained by "authconfig" will not be applied, this is a finding.
Fix: F-32809r2_fix
In the default distribution of RHEL "/etc/pam.d/system-auth" is a symlink "/etc/pam.d/system-auth-ac" which is an autogenerated file. When a site adds password requirements a new system-auth-local file must be created with only the additional requirements and includes for auth, account, passwd and session pointing to "/etc/pam.d/system-auth-ac". Then the symlink "/etc/system-auth" is modified to point to "/etc/pam.d/system-auth-local". This way any changes made do not get lost when "/etc/pam.d/system-auth-ac" is regenerated and each program's pam.d definition file need only have "include system-auth" for auth, account, passwd and session, as needed, in order to assure the password requirements will be applied to it.
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002720-2
- Vuln IDs
-
- V-29236
- Rule IDs
-
- SV-37612r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31649r1_fix
Edit the audit.rules file and add the following line(s) to enable auditing of failed attempts to access files and programs: either: -a exit,always -F arch=<ARCH> -S open -F success=0 or both: -a exit,always -F arch=<ARCH> -S open -F exit=-EPERM -a exit,always -F arch=<ARCH> -S open -F exit=-EACCES Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002720-3
- Vuln IDs
-
- V-29237
- Rule IDs
-
- SV-37614r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31650r1_fix
Edit the audit.rules file and add the following line(s) to enable auditing of failed attempts to access files and programs: either: -a exit,always -F arch=<ARCH> -S openat -F success=0 or both: -a exit,always -F arch=<ARCH> -S openat -F exit=-EPERM -a exit,always -F arch=<ARCH> -S openat -F exit=-EACCES Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002720-4
- Vuln IDs
-
- V-29238
- Rule IDs
-
- SV-37654r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31681r1_fix
Edit the audit.rules file and add the following line(s) to enable auditing of failed attempts to access files and programs: either: -a exit,always -F arch=<ARCH> -S truncate -F success=0 or both: -a exit,always -F arch=<ARCH> -S truncate -F exit=-EPERM -a exit,always -F arch=<ARCH> -S truncate -F exit=-EACCES Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002720-5
- Vuln IDs
-
- V-29239
- Rule IDs
-
- SV-37655r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31682r1_fix
Edit the audit.rules file and add the following line(s) to enable auditing of failed attempts to access files and programs: either: -a exit,always -F arch=<ARCH> -S ftruncate -F success=0 or both: -a exit,always -F arch=<ARCH> -S ftruncate -F exit=-EPERM -a exit,always -F arch=<ARCH> -S ftruncate -F exit=-EACCES Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002740-2
- Vuln IDs
-
- V-29240
- Rule IDs
-
- SV-37656r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31683r1_fix
Edit the audit.rules file and add the following line to enable auditing of deletions: -a exit,always -S rmdir Restart the auditd service. # service auditd restart
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-000347
- Version
- GEN002760-2
- Vuln IDs
-
- V-29241
- Rule IDs
-
- SV-48474r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-41610r1_fix
The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Add the following lines to the audit.rules file to enable auditing of administrative, privileged, and security actions: -w /etc/audit/audit.rules Restart the auditd service. # service auditd restart
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-000347
- Version
- GEN002760-3
- Vuln IDs
-
- V-29242
- Rule IDs
-
- SV-37658r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31685r4_fix
The "-F arch=<ARCH>"restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>"restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Add the following lines to the audit.rules file to enable auditing of administrative, privileged, and security actions: -a exit,always -F arch=<ARCH> -S adjtimex Restart the auditd service. # service auditd restart
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-000347
- Version
- GEN002760-4
- Vuln IDs
-
- V-29243
- Rule IDs
-
- SV-37659r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31686r1_fix
The "-F arch=<ARCH>"restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>"restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Add the following lines to the audit.rules file to enable auditing of administrative, privileged, and security actions: -a exit,always -F arch=<ARCH> -S settimeofday Restart the auditd service. # service auditd restart
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-000347
- Version
- GEN002760-5
- Vuln IDs
-
- V-29244
- Rule IDs
-
- SV-37660r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32213r2_fix
The "-F arch=<ARCH>"restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>"restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Add the following lines to the audit.rules file to enable auditing of administrative, privileged, and security actions: -a exit,always -F arch=<ARCH> -S stime -a exit,always -F arch=<ARCH> -S settimeofday (only needed on systems using a b64 architecture) Restart the auditd service. # service auditd restart
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-000347
- Version
- GEN002760-6
- Vuln IDs
-
- V-29245
- Rule IDs
-
- SV-37661r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31687r1_fix
The "-F arch=<ARCH>"restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>"restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Add the following lines to the audit.rules file to enable auditing of administrative, privileged, and security actions: -a exit,always -F arch=<ARCH> -S clock_settime Restart the auditd service. # service auditd restart
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-000347
- Version
- GEN002760-7
- Vuln IDs
-
- V-29246
- Rule IDs
-
- SV-37662r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31688r1_fix
The "-F arch=<ARCH>"restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>"restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Add the following lines to the audit.rules file to enable auditing of administrative, privileged, and security actions: -a exit,always -F arch=<ARCH> -S sethostname Restart the auditd service. # service auditd restart
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-000347
- Version
- GEN002760-8
- Vuln IDs
-
- V-29247
- Rule IDs
-
- SV-37663r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31689r1_fix
The "-F arch=<ARCH>"restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>"restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Add the following lines to the audit.rules file to enable auditing of administrative, privileged, and security actions: -a exit,always -F arch=<ARCH> -S setdomainname Restart the auditd service. # service auditd restart
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-000347
- Version
- GEN002760-9
- Vuln IDs
-
- V-29248
- Rule IDs
-
- SV-37664r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31690r1_fix
The "-F arch=<ARCH>"restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>"restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: A Real Time Operating System (RTOS) provides specialized system scheduling which causes an inordinate number of messages to be produced when the sched_setparam and set_setscheduler are audited. This not only may degrade the system speed to an unusable level but obscures any forensic information which may otherwise have been useful. Unless the operating system is a Red Hat 5 based RTOS (including MRG and AS5300) the following should also be present in /etc/audit/audit.rules -a exit,always -F arch=<ARCH> -S sched_setparam Restart the auditd service. # service auditd restart
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-000347
- Version
- GEN002760-10
- Vuln IDs
-
- V-29249
- Rule IDs
-
- SV-37665r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31691r1_fix
The "-F arch=<ARCH>"restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>"restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: A Real Time Operating System (RTOS) provides specialized system scheduling which causes an inordinate number of messages to be produced when the sched_setparam and set_setscheduler are audited. This not only may degrade the system speed to an unusable level but obscures any forensic information which may otherwise have been useful. Unless the operating system is a Red Hat 5 based RTOS (including MRG and AS5300) the following should also be present in /etc/audit/audit.rules -a exit,always -F arch=<ARCH> -S sched_setscheduler Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820-2
- Vuln IDs
-
- V-29250
- Rule IDs
-
- SV-37666r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31692r2_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S fchmod Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820-3
- Vuln IDs
-
- V-29251
- Rule IDs
-
- SV-37667r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31695r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S fchmodat Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820-4
- Vuln IDs
-
- V-29252
- Rule IDs
-
- SV-37668r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31710r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S chown Additionally, the following rule is required in systems supporting the 32-bit syscall table (such as i686 and x86_64): -a exit,always -F arch=<ARCH> -S chown32 Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820-5
- Vuln IDs
-
- V-29253
- Rule IDs
-
- SV-37669r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31729r2_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S fchown Additionally, the following rule is required in systems supporting the 32-bit syscall table (such as i686 and x86_64): -a exit,always -F arch=<ARCH> -S fchown32 Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820-6
- Vuln IDs
-
- V-29255
- Rule IDs
-
- SV-37671r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31781r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S fchownat Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820-7
- Vuln IDs
-
- V-29257
- Rule IDs
-
- SV-37673r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31805r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S lchown Additionally, the following rule is required in systems supporting the 32-bit syscall table (such as i686 and x86_64): -a exit,always -F arch=<ARCH> -S lchown32 Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820-8
- Vuln IDs
-
- V-29259
- Rule IDs
-
- SV-37677r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31825r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S setxattr Restart the auditd service. # service auditd restart
- RMF Control
- Severity
- M
- CCI
- Version
- GEN002820-9
- Vuln IDs
-
- V-29261
- Rule IDs
-
- SV-37681r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-31843r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S lsetxattr Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820-10
- Vuln IDs
-
- V-29272
- Rule IDs
-
- SV-37716r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32185r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S fsetxattr Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820-11
- Vuln IDs
-
- V-29274
- Rule IDs
-
- SV-37718r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32186r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S removexattr Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820-12
- Vuln IDs
-
- V-29275
- Rule IDs
-
- SV-37719r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32187r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S lremovexattr Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002820-13
- Vuln IDs
-
- V-29279
- Rule IDs
-
- SV-37726r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32188r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Edit the audit.rules file and add the following lines to enable auditing of discretionary access control permissions modifications. -a exit,always -F arch=<ARCH> -S fremovexattr Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002825-2
- Vuln IDs
-
- V-29281
- Rule IDs
-
- SV-37728r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32192r1_fix
The "-F arch=<ARCH>" restriction is required on dual-architecture systems (such as x86_64). On dual-architecture systems, two separate rules must exist - one for each architecture supported. Use the generic architectures "b32" and "b64" for specifying these rules. On single architecture systems, the "-F arch=<ARCH>" restriction may be omitted, but if present must match either the architecture of the system or its corresponding generic architecture. The architecture of the system may be determined by running "uname -m". See the auditctl(8) manpage for additional details. Any restrictions (such as with "-F") beyond those provided in the example rules are not in strict compliance with this requirement, and are a finding unless justified and documented appropriately. The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Configure auditing of the delete_module syscalls. Add the following to the "etc/audit/audit.rules" or "etc/audit.rules" file: -a exit,always -S delete_module Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002825-3
- Vuln IDs
-
- V-29284
- Rule IDs
-
- SV-37734r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32197r2_fix
The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Configure auditing of the /sbin/insmod, files. Add the following to the "etc/audit/audit.rules" or "etc/audit.rules" file: -w /sbin/insmod -p x Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002825-4
- Vuln IDs
-
- V-29286
- Rule IDs
-
- SV-37738r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32199r2_fix
The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: -w /sbin/modprobe -p x Restart the auditd service. # service auditd restart
- RMF Control
- AU-2
- Severity
- M
- CCI
- CCI-000126
- Version
- GEN002825-5
- Vuln IDs
-
- V-29288
- Rule IDs
-
- SV-37741r2_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32203r2_fix
The use of audit keys consistent with the provided example is encouraged to provide for uniform audit logs, however omitting the audit key or using an alternate audit key is not a finding. Procedure: Configure auditing of the /sbin/rmmod file. Add the following to the "etc/audit/audit.rules" or "etc/audit.rules" file: -w /sbin/rmmod -p x Restart the auditd service. # service auditd restart
- RMF Control
- AC-6
- Severity
- M
- CCI
- CCI-000225
- Version
- GEN003080-2
- Vuln IDs
-
- V-29289
- Rule IDs
-
- SV-37745r1_rule
Checks: http://oval.mitre.org/XMLSchema/oval-definitions-5
Fix: F-32208r1_fix
Change the mode of the cron scripts. # chmod 0700 /etc/cron.daily/* /etc/cron.hourly/* /etc/cron.monthly/* /etc/cron.weekly/*
- RMF Control
- AC-2
- Severity
- M
- CCI
- CCI-000012
- Version
- GEN000290-1
- Vuln IDs
-
- V-29376
- Rule IDs
-
- SV-38177r1_rule
Checks: C-37561r1_chk
Check the system for the unnecessary "games" accounts. Procedure: # grep ^games /etc/passwd If this account exists, it is a finding.
Fix: F-32805r2_fix
Remove the "games" account. Procedure: # userdel games
- RMF Control
- AC-2
- Severity
- L
- CCI
- CCI-000017
- Version
- GEN006660
- Vuln IDs
-
- V-38692
- Rule IDs
-
- SV-50927r1_rule
Checks: C-46254r2_chk
To verify the "INACTIVE" setting, run the following command: grep "INACTIVE" /etc/default/useradd The output should indicate the "INACTIVE" configuration option is set to an appropriate integer as shown in the example below: # grep "INACTIVE" /etc/default/useradd INACTIVE=35 If it does not, this is a finding.
Fix: F-43641r2_fix
To specify the number of days after a password expires (which signifies inactivity) until an account is permanently disabled, add or correct the following lines in "/etc/default/useradd", substituting "[NUM_DAYS]" appropriately: INACTIVE=[NUM_DAYS] A value of 35 is recommended. If a password is currently on the verge of expiration, then 35 days remain until the account is automatically disabled. However, if the password will not expire for another 60 days, then 95 days could elapse until the account would be automatically disabled. See the "useradd" man page for more information. Determining the inactivity timeout must be done with careful consideration of the length of a "normal" period of inactivity for users in the particular environment. Setting the timeout too low incurs support costs and also has the potential to impact availability of the system to legitimate users.