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

Expand user enumeration section for Clearance and Devise #26

Merged
merged 1 commit into from
Jun 12, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,10 @@ One aim for this document is to turn it into a community resource much like the
- [ ] Require user confirms account (see Devise's confirmable module)
- [ ] Lock account after X failed password attempts (see Devise's lockable module)
- [ ] Timeout logins (see Devise's timeoutable module)
- [ ] Favor mitigating user enumeration (see paranoid mode in Devise and https://www.owasp.org/index.php/Testing_for_user_enumeration_(OWASP-AT-002))
- [ ] Favor mitigating user enumeration [(source)](https://www.owasp.org/index.php/Testing_for_user_enumeration_(OWASP-AT-002))
- Clearance mitigates user enumeration by default (except on registration) [(source)](https://github.com/eliotsykes/rails-security-checklist/issues/21#issuecomment-294912368)
- Devise needs to be configured to mitigate user enumeration by configuring `paranoid` mode (except on registration) [(source)](https://github.com/eliotsykes/rails-security-checklist/issues/21#issue-222185446)
- Both Clearance & Devise do not mitigate user enumeration for registration, as apps often want to report if an email address is already registered.


### Passwords
Expand Down