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.
Bug 2175882 - scap results should be clear about what values are acceptable for "pam faillock deny" and "pam faillock interval".
Summary: scap results should be clear about what values are acceptable for "pam faillo...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: scap-security-guide
Version: 8.6
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Vojtech Polasek
QA Contact: Milan Lysonek
Petr Hybl
URL:
Whiteboard:
Depends On:
Blocks: 2228441 2228442
TreeView+ depends on / blocked
 
Reported: 2023-03-06 17:08 UTC by Lark Gordon
Modified: 2023-11-14 17:07 UTC (History)
12 users (show)

Fixed In Version: scap-security-guide-0.1.69-1.el8
Doc Type: Bug Fix
Doc Text:
.SCAP rules related to `pam_faillock` have correct descriptions Previously, the SCAP Security Guide rules related to the `pam_faillock` contained descriptions that were misaligned with some profile values. Consequently, the descriptions were not correct. With this update, the rules descriptions are now using XCCDF variables. This change affects the following rules: * `accounts_passwords_pam_faillock_deny` * `accounts_passwords_pam_faillock_interval` * `accounts_passwords_pam_faillock_dir` * `accounts_passwords_pam_faillock_unlock_time`
Clone Of:
: 2228441 2228442 (view as bug list)
Environment:
Last Closed: 2023-11-14 15:36:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-150855 0 None None None 2023-03-06 17:24:52 UTC
Red Hat Product Errata RHBA-2023:7056 0 None None None 2023-11-14 15:37:30 UTC

Description Lark Gordon 2023-03-06 17:08:58 UTC 
Description of problem:
The following checks in the xccdf_org.ssgproject.content_profile_stig profile for ssg-rhel8-xccdf.xml do not have clear guidelines for meeting the check requirements.

xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_interval xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_deny

The following values lead to all 3 checks Success:

deny = 3
fail_interval = 900
unlock_time = 900

A deny of 2 fails, a deny of 4 fails

Setting fail_interval to 300 fails
Setting fail_interval to 1200 Success

Setting unlock_time to 1200 is Success
Setting unlock_time to 300 is still Success, which is strange as it weaker than the 900 seconds.

Version-Release number of selected component (if applicable):

scap-security-guide-0.1.66-2.el8_7.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Run scap scan for xccdf_org.ssgproject.content_profile_stig profile
2. Scan results do not state the exact requirement for the fallock interval or faillock deny settings.

Actual results:
Scan results do not state the exact requirement for the fallock interval or faillock deny settings. If the system fails the check, there is no clear recommendation for what the settings must be. 

Expected results:
The scap results should be clear about what settings are required for compliance.

Additional info:
Comment 4 Marcus Burghardt 2023-07-12 14:15:14 UTC 
Fix is already merged in Upstream: https://github.com/ComplianceAsCode/content/pull/10824
Comment 22 errata-xmlrpc 2023-11-14 15:36:38 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.