openstack/ansible-hardening
Code Issues Proposed changes
ansible-hardening/doc/metadata/rhel6/V-38519.rst
Major Hayden e57593dfd4 Automate the STIG documentation 
With the upcoming changes to rebase onto the RHEL 7 STIG controls,
there needs to be a new solution for documentation that is easier
to manage and filter. This patch automates the generation of the STIG
control documentation in the following way:

* A Sphinx extension runs early in the doc build process that writes
  all of the individual STIG control docs as well as ToC pages.
* ToC pages are now sorted by severity, tag, and implementation status.
* A giant listing of controls is easier to navigate now.
* Docs are generated from metadata in the /doc/metadata directory. New
  documentation only needs to be added there. (Will explain this in
  the developer notes in a subsequent patch.)

Implements: blueprint security-rhel7-stig
Change-Id: I455af1121049f52193e98e2c9cb1ba5d4c292386
2016-09-09 14:43:30 +00:00

405 B
Raw Blame History

---id: V-38519 status: exception tag: misc ---

Exception

Different systems may have different log files populated depending on the type of data that rsyslogd receives. By default, log files are created with the user and group ownership set to root.

Deployers should review the files generated by the rsyslogd daemon to verify that they have the most restrictive ownership and permissions.