-
Notifications
You must be signed in to change notification settings - Fork 1
Security Policy Draft
Ihar Suvorau edited this page Sep 19, 2023
·
2 revisions
- All users must create unique email-based logins which are authenticated via secure protocols.
- Passwords should contain a mix of uppercase, lowercase, numeric and special characters and be a minimum length.
- Email verification should be used to confirm the user's email address.
- Password reset functionality should be implemented.
- Passwords should be stored using a secure hashing algorithm such as bcrypt.
- Passwords should be encrypted at rest.
- User data must be encrypted during transmission.
- Account lockout policy will be implemented after a limited number of failed logins.
- Multifactor authentication is encouraged and should be implemented where necessary.
-
Archive (ignore this, for history reasons only)
- Jonas' Notes
- Developer Notes
- System Design
-
Developer Notes
-
System Design
-
Policies