Lesson4Lec DataSecurityAwareness
Lesson4Lec DataSecurityAwareness
Lecture
PASSWORDS &
AUTHENTICATION
1. User-Generated Credentials
2. Down Brute-Force Attacks
3. Recycled Passwords
4. Large-Scale Breaches
Take a look at this chart with some best practices for ensuring
password security. When your team implements criteria such as these into the
back-end of password requirements, it can reduce the number of insecure
credentials that get through.
As a result, users are forced to create stronger passwords and avoid those
that can be easily guessed. However, it’s important that your team stays up-to-
date with all the latest password protection protocols, as best practices are
constantly evolving alongside authentication technology.
Simply put, a brute-force attack occurs when a computer program runs through every
password combination until they find a match. The system will run through all one-digit
combinations, two-digit combinations, and so forth until it cracks your password. Some
programs specifically focus on combing through the most commonly used dictionary words,
while others target popular passwords against a list of possible usernames.
As technology evolves, so do the tools hackers use to crack people’s credentials. Aside
from merely guessing your password, a brute-force attack is the most common technique
hackers use.
To make matters worse, these systems are able to run through thousands of combinations
in less than a second, which means that shorter passwords can be cracked in a very short time
frame.
In addition to making these changes, it’s also important that you encourage users to create longer and
stronger passwords, as recommended in the previous section. This is because the longer a user’s password is,
the longer it will take for a computer to gain access. And hopefully, your system will be able to lock the
hacker out before that even happens!
Because it’s wholly unrealistic to expect users to manage 90-something unique passwords, one effective
solution is to encourage users to connect multiple accounts with a single, ultra-secure password.
For example, we already mentioned that email clients tend to have stronger password security
regulations. It makes sense to use that as a tool to authenticate further online accounts as well.
However, social media platforms such as Facebook and Twitter have also become popular resources for
streamlining the registration and login processes.
A hacker might attempt to crack an individual’s credentials using a brute force attack. However, the
real goal is often to gain access to the website’s user database. Once hackers have cracked the master
code, they’ll have a list of all your users’ credentials, and as a result, no level of password security will
be able to protect your users.
Password breaches are becoming a real concern for businesses and organizations of all sizes.
Storing all of your users’ credentials puts you at risk, and simply encrypting the information is often not
enough. Instead, developers need to understand that weak internal passwords and improper storage of
credentials could make a hacker’s job easier.
Additionally, the password breaches of other websites could affect your website’s security. Think
about it: if you’re using a service from a company that recently had a password breach, your own
employees’ accounts could be compromised, which means your end users are also at risk. Once a big
company gets hacked, the consequences can start to trickle down fairly quickly.
If your organization continues to use passwords as a user authentication method, it’s important that you
store your passwords with more than just encryption. In fact, you can boost your website’s overall security
by:
Hashing your passwords. Hashing your passwords translates them into a random set of characters.
Once the data has been hashed, it’s extremely difficult to decode the information without the key. This
is especially useful for passwords because they don’t need to be read back. When users log in, the
same hashing will be applied and then compared to the information on file.
Salting your passwords. This technique adds an extra value at the end of your passwords so that it’s
harder to determine what the actual credential is. For instance, the password “admin” would change to
“admin+salt” when salt is added. For an additional security precaution, the salt added to each
password should be random and unique.
However, it’s important to recognize that as our password- based technology improves,
cybercriminals’ tools are often trailing not far behind. In fact, some hackers have figured out how to run
brute-force attacks on passwords even after they’ve been salted and hashed!
As you can see, password authentication has many weaknesses that can put you and your users’
sensitive information at risk. Hopefully, this article has made you more aware of password weaknesses
and ways you can improve your website’s vulnerabilities. Don’t wait to make changes until it’s too late!