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:	MODIFIED ---	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	ggasparb, jcerny, jjaburek, maburgha, matyc, mhaicman, mlysonek, peter.vreman, suwu, wsato
Target Milestone:	rc	Keywords:	AutoVerified, Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	scap-security-guide-0.1.69-1.el8	Doc Type:	Bug Fix
Doc Text:	.Rules related to the PAM faillock option have clarified description Rules related to PAM faillock rules have contained description that was misaligned with some profile values.These rules have been modified so that XCCDF variable which is used in their checks and remediations is displayed in the description. Therefore, the descriptions are no longer misleading. This change is affecting 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:		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