Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
.SSG now supports the `/etc/security/faillock.conf` file
This enhancement adds support for the `/etc/security/faillock.conf` file in SCAP Security Guide (SSG). With this update, SSG can assess and remediate the `/etc/security/faillock.conf` file for definition of `pam_faillock` settings. The `authselect` tool is also used to enable the `pam_faillock` module while ensuring the integrity of `pam` files. As a result, the assessment and remediation of the `pam_faillock` module is aligned with the latest versions and best practices.
Description of problem:
The SCAP check for faillock checks for 'silent' and deny' in the pam file
------
/etc/pam.d/system-auth [\n][\s]*auth[\s]+required[\s]+pam_faillock\.so[\s]+preauth[\s]+[^\n]*silent[\s]+[^\n]*deny=([0-9]+)[\s]*(?s).*[\n][\s]*auth[^\n]+pam_unix\.so[^\n]*[\n]
------
This is against the recommendation in the man page of pam_faillock:
------
NOTES
Configuring options on the module command line is not recommend. The /etc/security/faillock.conf should be used instead.
------
Version-Release number of selected component (if applicable):
Header of the HTML output of the scap report:
------
Evaluation target li-lc-2624
Benchmark URL /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml
Benchmark ID xccdf_org.ssgproject.content_benchmark_RHEL-8
Benchmark version 0.1.50
Profile ID xccdf_org.ssgproject.content_profile_ospp
Started at 2021-04-12T16:57:29+00:00
Finished at 2021-04-12T16:57:30+00:00
Performed by vrempet-admin
Test system cpe:/a:redhat:openscap:1.3.3
------
Additional info ( Customer Comments )
If there is a good reason to divert from the recommendation on the pam_faillock developers to use faillock.conf then this has to be written in the SCAP rationale
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-2022:1900
Description of problem: The SCAP check for faillock checks for 'silent' and deny' in the pam file ------ /etc/pam.d/system-auth [\n][\s]*auth[\s]+required[\s]+pam_faillock\.so[\s]+preauth[\s]+[^\n]*silent[\s]+[^\n]*deny=([0-9]+)[\s]*(?s).*[\n][\s]*auth[^\n]+pam_unix\.so[^\n]*[\n] ------ This is against the recommendation in the man page of pam_faillock: ------ NOTES Configuring options on the module command line is not recommend. The /etc/security/faillock.conf should be used instead. ------ Version-Release number of selected component (if applicable): Header of the HTML output of the scap report: ------ Evaluation target li-lc-2624 Benchmark URL /usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml Benchmark ID xccdf_org.ssgproject.content_benchmark_RHEL-8 Benchmark version 0.1.50 Profile ID xccdf_org.ssgproject.content_profile_ospp Started at 2021-04-12T16:57:29+00:00 Finished at 2021-04-12T16:57:30+00:00 Performed by vrempet-admin Test system cpe:/a:redhat:openscap:1.3.3 ------ Additional info ( Customer Comments ) If there is a good reason to divert from the recommendation on the pam_faillock developers to use faillock.conf then this has to be written in the SCAP rationale