Ensure PAM Enforces Password Requirements - Minimum Uppercase Characters
Forces pam_pwquality to require at least one uppercase letter in every new password by setting ucredit = -1.
Checked against the content of a persistent configuration file, the source of truth that survives reboots.
A mapping is a cross-reference to where each standard places this requirement, anchored and cross-validated, not a claim of equivalence. A passing check is evidence toward these references, how to read it.
Why this rule matters
A complex password increases the time and resources needed to compromise it. The ucredit parameter governs how uppercase letters count toward password strength: a value of -1 makes at least one uppercase character mandatory. Mixing case enlarges the character search space, slowing brute-force and dictionary attacks. Without this requirement, users can pick single-case passwords drawn from a much smaller alphabet that are far quicker to crack.
What Pavois checks
Pavois reads the effective ucredit value by scanning /etc/security/pwquality.conf and every drop-in under /etc/security/pwquality.conf.d/, keeping the last definition that wins at runtime. A file-based scanner reading only the main config would miss a value set or overridden by a drop-in. The control passes only when the resolved value is <= -1.
describe command('v=$(grep -rh \'^[[:space:]]*ucredit[[:space:]]*=\' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/ 2>/dev/null | tail -1 | grep -oE \'[-]?[0-9]+\'); { [ -n "$v" ] && [ "$v" -le -1 ] && echo ok; } || echo ko') do
its('stdout.strip') { should eq 'ok' }
endHow to verify it is applied
Run grep -rh '^[[:space:]]*ucredit' /etc/security/pwquality.conf /etc/security/pwquality.conf.d/ | tail -1. The effective line must read ucredit = -1 (or any value <= -1).
Inspect & investigate
Rejected password changes are logged via PAM in /var/log/auth.log (Debian/Ubuntu) or /var/log/secure (RHEL family) with pam_pwquality messages about insufficient character classes. Inspect the live setting with grep -r ucredit /etc/security/pwquality.conf.d/.
Remediation
pavois harden apply writes ucredit = -1 to the drop-in /etc/security/pwquality.conf.d/99-Pavois.conf via the idempotent keyval resource. The 99- prefix ensures it overrides any earlier value. No service restart is needed; it applies at the next password change.
Pavois applies this with its own harden engine, the plan below, not a shell script:
| file | /etc/security/pwquality.conf.d/99-pavois.conf |
|---|---|
| key | ucredit |
| resource | keyval |
| value | -1 |
pavois harden plan localwhere the target is local, a user@host SSH alias, or a container , Docs
Impact & precautions
Existing passwords stay valid; only new passwords must contain an uppercase letter. Users setting all-lowercase passwords will be rejected at change time. Lockout risk is low, but verify that automated provisioning and password-rotation tooling generate passwords with at least one uppercase letter before applying, to avoid failed account setups.
Standards mapping
| Standard | Reference | Type | Version | Confidence |
|---|---|---|---|---|
| ANSSI BP-028 | R31 | direct | 2.0 | high |
| CIS | 5.3.3.2.3 | direct | per OS, see the benchmark table | high |
| NIST | CM-6(a), IA-5(1)(a), IA-5(4), IA-5(c) | supporting | 800-53 Rev 5 · 800-171 Rev 2 (pinned) | medium |
| PCI DSS | 8.3.6 | supporting | 4.0.1 | medium |
| DISA STIG | UBTU-22-611010, UBTU-24-400260 | direct | per OS STIG release | high |
Each reference is a cross-reference anchored in the upstream benchmark and cross-validated against the SCAP Security Guide and ansible-lockdown, not a claim of equivalence. Direct = a prescriptive, line-level requirement; supporting = an abstract control family (NIST) the check provides evidence toward. How to read a mapping.