The Hash
A hash is a one-way scramble. Put the same password in and the same long string of characters comes out every time, but there is no way to run it backwards. When a customer signs up, the system hashes the password and stores only the result. When they log in, it hashes what they typed and compares the two results. If they match, the password was right. The real password never has to be written down anywhere.
The Salt
Hashing alone has a weakness. Many people use the same common passwords, and the same password always makes the same hash, so an attacker who steals the stored hashes can look them up against huge prebuilt lists of common passwords and their hashes.
The salt fixes that. Before hashing, the system adds a random value that is different for every account and stores it next to the hash. Two people with the same password now end up with completely different stored values, the prebuilt lists are useless, and an attacker has to attack each account one at a time.
Why They Belong Together
A hash without a salt can be looked up. A salt without a hash is just a random string. Together they are the accepted standard, and modern password hashing methods are also built to be slow on purpose, which makes guessing millions of passwords against one stolen record take far too long to be worth it.
How To Tell When It Is Missing
A company that hashes and salts passwords cannot tell you your password. It does not have it. So if a company ever emails you your password, shows it to you on a screen, or a support person reads it back over the phone, the password is stored in plain text or in a form that can be unscrambled. The right answer to a forgotten password is always a link to set a new one.
The Foundation Connection
Hash and salt belongs to Active Security in the Digital Foundation. Every BizPinPro system with a login, from the client portal to the CRM, stores passwords this way. It is invisible when it is done right, and the day it matters is the day someone else's database gets broken into.