Bug 2209073
Summary: | Please explain if "accounts_passwords_pam_faillock_interval" should apply to RHEL8.2+ or not | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Renaud Métrich <rmetrich> | |
Component: | scap-security-guide | Assignee: | Vojtech Polasek <vpolasek> | |
Status: | CLOSED ERRATA | QA Contact: | Milan Lysonek <mlysonek> | |
Severity: | medium | Docs Contact: | Petr Hybl <phybl> | |
Priority: | medium | |||
Version: | 8.7 | CC: | ggasparb, jcerny, jjaburek, matyc, mhaicman, mjahoda, mlysonek, vpolasek, wsato | |
Target Milestone: | rc | Keywords: | Triaged, ZStream | |
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | scap-security-guide-0.1.69-1.el8 | Doc Type: | Bug Fix | |
Doc Text: |
.The SCAP rule `accounts_passwords_pam_faillock_interval` now covers new STIG IDs
Previously, the SCAP Security Guide rule `accounts_passwords_pam_faillock_interval` did not cover RHEL-08-020012 and RHEL-08-020013. Consequently, the rule `accounts_passwords_pam_faillock_interval` checked for `faillock` configuration in all of these three files: `/etc/pam.d/password-auth`, `/etc/pam.d/system-auth`, and `/etc/security/faillock.conf`. With this update, the rule now covers STIG IDs RHEL-08-020012 and RHEL-08-020013.
|
Story Points: | --- | |
Clone Of: | ||||
: | 2228465 2228466 (view as bug list) | Environment: | ||
Last Closed: | 2023-11-14 15:36:38 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: | 2228465, 2228466 |
Description
Renaud Métrich
2023-05-22 13:47:20 UTC
Hello Renaud, this rule is a bit special - it actually covers also this STIG item: https://stigaview.com/products/rhel8/v1r9/RHEL-08-020013/ It decides what to do based on presence of Authselect, so it works for all RHEL 8 systems. I think we should include the STIGID I have posted above into the rule reference so that it does not confuse people. Would this solve the issue? Best regards, Vojta Hello, thanks for the information, you may indeed add the stigid, I think it's more the STIG text in the rule that is confusing. Fixed upstream: https://github.com/ComplianceAsCode/content/pull/10846 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 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:7056 |