STIG rules for RHEL6 addressed with restrictions
The following section details the STIG rules for Red Hat Enterprise Linux (RHEL) 6 that have been addressed in BMC Discovery, but have restrictions. The table provides links to STIG rule descriptions and details on the STIGviewer website. STIGviewer provides an online, searchable index of Public Domain STIG content, though is not related to DISA. The STIGviewer content may not be up to date.
Rule number | Description |
|---|---|
RHEL-06-000003 V-38463 | The system must use a separate file system for /var/log. |
RHEL-06-000004 V-38467 | The system must use a separate file system for the system audit data path. |
RHEL-06-000349 V-38595 | The system must be configured to require the use of a CAC, PIV compliant hardware token, or Alternate Logon Token (ALT) for authentication. |
| RHEL-06-000516 V-38454 | Files and directories must not have different ownership from what is expected in the RPM database. Note — Discovery intentionally changes/usr/tideway/bin and /usr/tideway/lib. Other files and directories may change during application of STIG rules, or by the OSU for security or functionality reasons. |
| RHEL-06-000517 V-38453 | Files and directories must not have different group-ownership from what is expected in the RPM database. Note — Discovery intentionally changes/usr/tideway/bin and /usr/tideway/lib. Other files and directories may change during application of STIG rules, or by the OSU for security or functionality reasons. |
RHEL-06-000518 V-38452 | Permissions of files should match the permissions expected in the RPM database. |
| RHEL-06-000519 V-38447 | Non-configuration files must not have file hashes different from what is expected in the RPM database. Note — Some files may be updated during an upgrade. If for example, tw-python is updated, some python modules may be recompiled, changing the files on disk if the source for that module is shipped. |
Comments
Log in or register to comment.