Authenticated Encryption
Pronunciation: aw-THEHN-tuh-kay-tuhd ehn-KRIHP-shun
Definition
Authenticated Encryption is a security mechanism or control discipline that protects data confidentiality while also detecting unauthorized modification, typically by producing ciphertext and an authentication tag. Authenticated encryption combines encryption with integrity and authenticity checks in one cryptographic construction. The recipient can verify that protected ciphertext and optional associated data were not modified before accepting and decrypting the message.
Overview
Meaning and scope
Authenticated Encryption is a security mechanism or control discipline that protects data confidentiality while also detecting unauthorized modification, typically by producing ciphertext and an authentication tag. Authenticated encryption combines encryption with integrity and authenticity checks in one cryptographic construction. The recipient can verify that protected ciphertext and optional associated data were not modified before accepting and decrypting the message.
Mechanism and operation
Keys should be purpose-specific, rotated appropriately, and protected securely throughout their lifecycle, while error handling must not reveal sensitive verification details. For Authenticated Encryption, unmatched records need owners and deadlines because apparent technical success can coexist with unresolved financial or compliance impact. For Authenticated Encryption, end-to-end validation must therefore include both mechanism and business meaning. Authenticated encryption provides confidentiality and tamper detection together, but only when nonce, key, tag, and verification rules are followed correctly. A production treatment of Authenticated Encryption should test protection of data confidentiality while also detecting unauthorized modification, typically by producing ciphertext and an authentication tag within the relevant asset, decision, or service state.
Practical payment example
A service encrypts sensitive configuration with integrity protection, so tampering causes decryption to fail instead of silently changing data.
Operational checks
The Authenticated Encryption context record for data confidentiality while also detecting unauthorized should preserve source data, configuration or policy version, responsible actor, exception, and outcome. Review of Authenticated Encryption should determine whether safeguards addressing data confidentiality while also detecting unauthorized changed exposure in practice, not merely whether a document or setting existed.
Distinctions and limits
Security depends on correct key use, nonce requirements, tag length, associated-data handling, and strict rejection when verification fails. Developers should rely on reviewed libraries and high-level interfaces rather than combining encryption and message authentication manually.
Related reading
Related definitions: encryption, authentication.
Example
A service encrypts sensitive configuration with integrity protection, so tampering causes decryption to fail instead of silently changing data.
Comparison
The recipient can verify that protected ciphertext and optional associated data were not modified before accepting and decrypting the message. Security depends on correct key use, nonce requirements, tag length, associated-data handling, and strict rejection when verification fails.
Key Takeaway
Authenticated encryption provides confidentiality and tamper detection together, but only when nonce, key, tag, and verification rules are followed correctly.
Sources
- Ethereum Foundation Documentation: Accounts — Ethereum Foundation (2026-07-30)
- NIST Documentation: Cryptographic Standards And Guidelines — NIST (2026-07-30)