e57593dfd4
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
17 lines
538 B
ReStructuredText
17 lines
538 B
ReStructuredText
---
|
|
id: V-38492
|
|
status: exception
|
|
tag: misc
|
|
---
|
|
|
|
**Exception**
|
|
|
|
Virtual consoles are helpful during an emergency and they can only be reached
|
|
by physical or other out-of-band access (such as DRAC, iLO, or iKVM). This
|
|
change can be confusing for system administrators and it is left up to the
|
|
deployer to complete.
|
|
|
|
As an alternative, deployers could take action to restrict physical access to
|
|
server terminals. Out-of-band access mechanisms should be segmented onto their
|
|
own restricted network and should use centralized authentication.
|