Hashing solutions

Unilateral data obfuscation and authentication

Data masking - overview
Anonymize
User-defined
Coding
Encrypt
Hash
Pseudonymize
Randomize
Blackening
Scrambling
Twiddle
Move
Tokenize

Hashing is a one-way data masking technique that converts a variable-length „message“ (e.g., someone's password) into a scrambled, fixed-length alphanumeric string. The message digest, or „hash value,“ can be an indexed lookup for the message. Sometimes there is more than one message per index (a „collision“).

Because hashing is not as strong as encryption or as reliably reversible, it is sometimes only suitable for masking. More commonly, however, hashing is used in encryption. IRI provides MD5, SHA1, and SHA2 hashing algorithms as well as various Encryption features.

Hash functions are also used to generate checksums or Message Authentication Codes (MACs). These are created and sent along with messages such as emails, EFTs, or passwords. When the message is received, its content is put through the same hash function to create a new MAC. If the original and new MACs match, the message is authentic; if they do not, it is likely that the message has been altered and therefore compromised.

Use field-level hashing functions in IRI FieldShield in the IRI Data Privacy Suite, IRI CoSort in the IRI Data Management Suite or the IRI Voracity–Platform to mask PII. Or create a MAC for one or more column values in each row. Add the MACs as an additional field or provide them in a separate file. Use the MAC to ensure data in the record was undisturbed.

For more information and further use of hash values: See here.

Frequently Asked Questions (FAQ)

Hashing is a one-way data masking technique that converts any input (e.g., a password) into a fixed-length alphanumeric string, known as the hash value or message digest. It is difficult to reverse and is used to protect or verify sensitive data.
Hashing is irreversible and is used for verification, while encryption is reversible and protects data that needs to be recovered later. Encrypted data can be decrypted with the appropriate key, whereas hash values cannot be reliably reversed.
Hashing is used to obscure passwords, verify data integrity, generate Message Authentication Codes (MACs), and generate checksums for validating files or data. This ensures that data has not been altered during storage or transmission.
Yes. Hashing can be used to irreversibly mask PII values such as email addresses or user IDs when reversibility is not needed—such as for indexing, auditing, or privacy-compliant reporting.
Hashing functions can generate a MAC (Message Authentication Code), which is transmitted along with the original message. If the receiving system calculates the same MAC, this confirms that the message has not been tampered with.
IRI supports MD5, SHA1, and SHA2, allowing you to choose the appropriate algorithm depending on your security and compatibility requirements.
Yes. IRI FieldShield, DarkShield, CellShield, CoSort, and Voracity can generate MACs for one or more column values per row. The MAC can be stored along with the data or in a separate file to verify data integrity later.
Hashing is well suited for one-way obfuscation and integrity checking. For sensitive data that needs to be recovered later, encryption is recommended. Hashing is most effective in combination with additional security measures.
Yes. Hashing can be combined with encryption, pseudonymization, redaction, and other masking functions of the IRI tools to build multi-layered protection.
A hash collision occurs when two different inputs produce the same hash value. With strong algorithms like SHA2, this is rare, but it can undermine integrity checking—which is why choosing reliable hashing standards is important.