DOMAIN 3 · Security Architecture and Engineering
Cryptography and key management
Distinguish encryption, hashing, message authentication, and signatures, and follow keys through their lifecycle.
Choose a security service
Section titled “Choose a security service”Start with the required property. Confidentiality prevents unauthorized reading; integrity helps detect unauthorized change; origin authentication connects data to a source under stated assumptions. Cryptographic mechanisms provide different combinations of services. NIST SP 800-57 explains these services together with the key types and protections needed to deliver them.1
An algorithm name alone does not describe a secure system. Protocol design, key generation, access controls, implementation, and recovery procedures also determine the result.
Compare the mechanisms
Section titled “Compare the mechanisms”| Mechanism | Primary purpose | What it does not establish alone |
|---|---|---|
| Symmetric encryption | Confidentiality using a shared secret key | Integrity or the identity of a particular sender |
| Hash | A digest for comparison | Authenticity when an attacker can replace data and digest |
| Message authentication code | Integrity and authentication using a shared key | Which of several key holders created the message |
| Digital signature | Integrity and origin authentication using a private/public key pair | Confidentiality of the signed content |
A signature’s evidentiary value depends on identity binding, private-key control, validation, and relevant procedures. Avoid treating nonrepudiation as an unconditional technical promise.1
Understand AES accurately
Section titled “Understand AES accurately”FIPS 197 specifies AES-128, AES-192, and AES-256. All use 128-bit blocks; the suffix identifies key length. The 2023 update made editorial improvements without changing the algorithm.2
AES is a building block, not a complete storage or communication protocol. A mode of operation and its requirements determine how messages are handled. When confidentiality and integrity are required, choose an approved construction that supplies both and follow its nonce or initialization-value rules. Increasing key length does not repair misuse of the construction.
Distinguish key purposes
Section titled “Distinguish key purposes”Symmetric cryptography uses a shared secret; asymmetric cryptography uses related public and private keys. An asymmetric scheme may provide signatures or key establishment depending on the algorithm. Do not assume every public-key algorithm can encrypt arbitrary application data.
In an illustrative hybrid design, public-key mechanisms establish or protect a symmetric data key, and a symmetric mechanism protects the bulk data. Separating a data-encryption key from the key that protects it can simplify controlled rotation, but introduces dependencies that must be tracked.
Manage the full key lifecycle
Section titled “Manage the full key lifecycle”Plan generation, distribution, storage, authorized use, rotation, recovery where appropriate, and destruction. NIST distinguishes key types and their required protection, and discusses cryptoperiods and compromised keys.1 A cryptoperiod is not necessarily the same for every purpose or every environment.
Keys needed to read retained records may outlive the period in which new information is encrypted with them. Deleting such keys without a retention decision can destroy availability. Conversely, keeping unnecessary copies indefinitely expands exposure. Recovery arrangements should reflect key purpose; indiscriminately backing up every private signing key can create additional impersonation risk.
Example: protecting payroll exports
Section titled “Example: protecting payroll exports”Suppose payroll files are encrypted before transfer. An attacker who steals the files should lack the decryption key. If the key sits beside each export with the same access permissions, the design loses that separation. Protect key access independently, log sensitive operations, and test authorized recovery.
The recipient must also detect altered content and verify the intended source. Encryption alone does not resolve mistaken recipients, compromised endpoints, or excessive application permissions.
Avoid common misconceptions
Section titled “Avoid common misconceptions”Encoding is not encryption. A plain hash is not a digital signature. Public keys may be public, but the association between a key and an identity still needs validation. Strong cryptography cannot protect plaintext after an authorized endpoint releases it. Study the service, assumptions, and key lifecycle together rather than memorizing algorithm names alone.
Continue learning
Section titled “Continue learning”Read TLS for a protocol combining these mechanisms and media sanitization for key destruction dependencies.
Footnotes
Section titled “Footnotes”-
NIST, SP 800-57 Part 1 Rev. 5, sections 3–5 and 7–8. ↩ ↩2 ↩3
-
NIST, FIPS 197: Advanced Encryption Standard, 2023 update, announcement and algorithm specification. ↩
Independent, unofficial study notes. Not endorsed or reviewed by ISC2. CISSP is a registered trademark of ISC2.
Editorial policy & attribution