Bug 2175882

Summary:	scap results should be clear about what values are acceptable for "pam faillock deny" and "pam faillock interval".
Product:	Red Hat Enterprise Linux 8	Reporter:	Lark Gordon <lagordon>
Component:	scap-security-guide	Assignee:	Vojtech Polasek <vpolasek>
Status:	CLOSED ERRATA	QA Contact:	Milan Lysonek <mlysonek>
Severity:	medium	Docs Contact:	Petr Hybl <phybl>
Priority:	unspecified
Version:	8.6	CC:	ggasparb, jcerny, jjaburek, maburgha, matyc, mhaicman, mjahoda, mlysonek, peter.vreman, suwu, vpolasek, wsato
Target Milestone:	rc	Keywords:	AutoVerified, Triaged, ZStream
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Linux
Whiteboard:
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`	Story Points:	---
Clone Of:
Clones:	2228441 2228442 (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:	2228441, 2228442

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