CyberKit

Salting

Also called Salt.

Adding unique random data to each password before hashing it.

What it is

The practice of prepending or appending a unique, random value to each password before hashing, so identical passwords produce different stored hashes. The salt is stored alongside the hash and need not be secret.

Why it matters

Salting defeats precomputed rainbow tables and stops an attacker from cracking many accounts at once, since each hash must be attacked individually. Finding unsalted password hashes in a breach is a serious red flag.

In practice

Two users with the password 'summer2025' having entirely different stored hashes because each got a random salt.

What to look for

  • Identical password hashes for different users, a sign of no salt.
  • One salt shared by every user.
  • Salts stored separately as if they were secret.

Common mistake

Treating the salt as a secret. It only needs to be unique; slowness comes from the hashing function.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • hashcat Open source

    A password recovery tool used to test how fast a hash type falls.

  • HashiCorp Vault Source available

    Generates and rotates credentials so people do not reuse passwords.

  • Microsoft Entra ID Protection Commercial

    Flags leaked credentials and risky sign-ins against Microsoft accounts.

Read next

Sources