Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set Account Lockout ASVS Levels 1-3 Aligned to NIST, PCI-DSS, CIS et al #2011

Closed
cmlh opened this issue Aug 11, 2024 · 1 comment
Closed
Labels
1) Discussion ongoing Issue is opened and assigned but no clear proposal yet V2 _5.0 - prep This needs to be addressed to prepare 5.0

Comments

@cmlh
Copy link
Contributor

cmlh commented Aug 11, 2024

ASVS Requirement 2.2.1 states "... More than 5 failed authentication attempts per hour for a single account should trigger some sort of reaction or alert. ..."

To expand on @TheDauntless comment within #906 (comment) I'd like the ASVS Levels to align within PCI-DSS and CIS.

NIST Special Publication 800-63B sets the limit to <100 as reproduced below:

image

PCI-DSS 4.0.1 sets the limit to 10 as reproduced below:

image

CIS sets the limit to 5 as reproduced below as provided by @TheDauntless:

image

Can we set the limits to <=100, 10, 5 for ASVS Level 1, 2, 3 respectively?

All other issues referencing "lockout"

@tghosth tghosth added 1) Discussion ongoing Issue is opened and assigned but no clear proposal yet _5.0 - prep This needs to be addressed to prepare 5.0 V2 labels Aug 11, 2024
@elarlang
Copy link
Collaborator

Here are two things mixed - the issue title asks to align "account lockout limits" but the content points to rate limiting and account lockout, and those are in conflict with each other (NIST vs PCI)

The direction should be do NOT use lockouts.

We have separate issues to handle those:

Closing this as duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1) Discussion ongoing Issue is opened and assigned but no clear proposal yet V2 _5.0 - prep This needs to be addressed to prepare 5.0
Projects
None yet
Development

No branches or pull requests

3 participants