Bug 817102 - Update to the "A Guide to Securing Red Hat Enterprise Linux Edition 2" Hardening Guide for RHEL 6
Update to the "A Guide to Securing Red Hat Enterprise Linux Edition 2" Harde...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Security_Guide (Show other bugs)
6.3
Unspecified Linux
medium Severity medium
: rc
: ---
Assigned To: Martin Prpič
ecs-bugs
: Documentation
Depends On:
Blocks: 741765
  Show dependency treegraph
 
Reported: 2012-04-27 13:43 EDT by William Gomeringer
Modified: 2012-11-09 07:57 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-11-09 07:57:05 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description William Gomeringer 2012-04-27 13:43:02 EDT
Description of problem:
In the current RHEL 6 Security Guide Documentation, Section 4.1 "Tips, Guides, and Tools" a Note states:

"References to Red Hat Enterprise Linux 5 hardening guides are provided in this document until hardening guides for Red Hat Enterprise Linux 6 can be made available. In the meantime, please note that the hardening guides for Red Hat Enterprise Linux 5 may not apply completely to Red Hat Enterprise Linux 6."

Is there a time line for updating the documentation to be more specific to RHEL 6?

Version-Release number of selected component (if applicable):
6
Comment 1 Martin Prpič 2012-11-09 07:57:05 EST
NSA has not come up with the RHEL6 version of their Hardening Guide yet. The work is in progress and is tracked in the scap-security-guide project [1].

As far as providing some hardening advice goes, bug 842936 tracks this and provides a patch with a few hardening tips.

Closing this for now. Please re-open if you have a specific request.

Thanks for reporting!
Martin

[1] https://fedorahosted.org/scap-security-guide/wiki/usageguide

Note You need to log in before you can comment on or make changes to this bug.