DLPX-86530 CIS: delphix user lockout after failed login attempts#564
Draft
rupalimatkar wants to merge 1 commit into
Draft
DLPX-86530 CIS: delphix user lockout after failed login attempts#564rupalimatkar wants to merge 1 commit into
rupalimatkar wants to merge 1 commit into
Conversation
5802549 to
2f15fa7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
CIS hardening — DLPX-86530. The appliance must lock out users after repeated
failed login attempts (`pam_faillock` in `common-auth` / `common-account`)
and reject password reuse (`pam_pwhistory` in `common-password`).
Solution
Three pam-auth-update profiles under `/usr/share/pam-configs/` shipped by the
`delphix-platform` package, plus a single `pam-auth-update --package` ansible
task to compose them in after the CRA enable:
Faillock parameters: `deny=5 unlock_time=900 onerr=fail audit silent`.
Pwhistory: `remember=5`.
All three profiles set `Default: yes` so they auto-enable on install.
pam-auth-update recalculates the `success=N` jumps and composes faillock
around whichever Primary auth module is active (`unix` on internal,
`challenge-response` on external), so the same change works for all variants.
The `account required pam_faillock.so` line handles counter reset on
successful auth — no separate `authsucc` is needed.
Testing Done
internal variant
external variant
password
pwhistory
pam_faillock.so`
external variant (faillock lines present, ordering correct)