updates to rec for Token is Not Invalidated After Login#458
Open
updates to rec for Token is Not Invalidated After Login#458
Conversation
norsec0de
suggested changes
May 15, 2024
| Passwords should be stored and transmitted securely | ||
| Once a user’s password has been reset, they should be prompted to login in again through the usual login portal and not automatically signed in | ||
| - A secure password policy should be in place for the user to create a strong new password | ||
| - Password reset tokens should be long to protect against brute force guessinging attacks, linked to an individual, invalidated after use, and have a short expiry time |
Contributor
Author
There was a problem hiding this comment.
Guessing that I didn't have enough coffee that day
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
2 participants
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.
No description provided.