Bug 2115343
Summary: | file_permissions_sshd_private_key is not aligned with DISA STIG benchmark | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Milan Lysonek <mlysonek> | |
Component: | scap-security-guide | Assignee: | Vojtech Polasek <vpolasek> | |
Status: | CLOSED ERRATA | QA Contact: | Jiri Jaburek <jjaburek> | |
Severity: | unspecified | Docs Contact: | Jan Fiala <jafiala> | |
Priority: | unspecified | |||
Version: | 8.7 | CC: | ggasparb, jafiala, jjaburek, matyc, mhaicman, mlysonek, smahanga, vpolasek, wsato | |
Target Milestone: | rc | Keywords: | AutoVerified, Triaged, ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | scap-security-guide-0.1.66-1.el8 | Doc Type: | Bug Fix | |
Doc Text: |
.SCAP Security Guide rule `file_permissions_sshd_private_key` is aligned with STIG configuration RHEL-08-010490
Previously, the implementation of rule `file_permissions_sshd_private_key` allowed private SSH keys to be readable by the `ssh_keys` group with mode `0644`, while DISA STIG version RHEL-08-010490 required private SSH keys to have mode `0600`. As a consequence, evaluation with DISA’s automated STIG benchmark failed for configuration RHEL-08-010490.
For this update, we worked with DISA to align the expected permissions for private SSH keys, and now private keys are expected to have mode `0644` or less permissive. As a result, the rule `file_permissions_sshd_private_key` and configuration RHEL-08-010490 are now aligned.
|
Story Points: | --- | |
Clone Of: | ||||
: | 2123284 2168057 2168058 2168059 (view as bug list) | Environment: | ||
Last Closed: | 2023-05-16 08:39:27 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 2123284, 2168057, 2168058, 2168059 |
Description
Milan Lysonek
2022-08-04 13:06:42 UTC
See also: https://github.com/ComplianceAsCode/content/issues/9251 and https://github.com/ComplianceAsCode/content/issues/7833 for the context. DISA has updated their automated content and now the rules are aligned. The update to DISA's automated content V1R8 aligns them: https://github.com/ComplianceAsCode/content/pull/10078 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (scap-security-guide bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:2869 |