Further Reading: Applied Cryptography

Curated, annotated resources to deepen this chapter. Each entry notes which learning path it serves most (🛡️ SOC, 🏗️ Engineer, 📋 GRC, 📜 Cert) and its citation tier. Start with the suggested order; you do not need everything before Part II. All standards below are Tier 1 (verifiable primary sources).

Suggested order

1. Read the introduction and handshake overview of RFC 8446 (TLS 1.3) — even skimming the message flow makes Figure 5.1 click.
2. Skim NIST SP 800-52 Rev. 2 for the authoritative "how to configure TLS for an organization."
3. Use Mozilla's Server Side TLS guide as the practical, copy-from configuration reference.
4. Dip into Ristić, Bulletproof TLS and PKI for the deep, readable treatment of everything here.
5. Keep NIST SP 800-57 nearby as the reference for key-management lifecycle questions.

Standards & primary documents (Tier 1)

• IETF, RFC 8446 — The Transport Layer Security (TLS) Protocol Version 1.3 (2018). 🏗️📜 The authoritative definition of TLS 1.3. Read the introduction and §2 (Protocol Overview) for the handshake; the rest is a reference. This is the source for §5.2.
• NIST SP 800-52 Rev. 2, Guidelines for the Selection, Configuration, and Use of TLS Implementations. 🏗️📋📜 NIST's practical guidance on which TLS versions and ciphers to allow in a federal/enterprise context — effectively a hardening standard you can cite in policy.
• NIST SP 800-57 Part 1, Recommendation for Key Management. 🏗️📋 The canonical treatment of the key lifecycle — generation, distribution, storage, rotation, destruction — that §5.6 introduced. The reference for any key-management decision.
• NIST SP 800-77 Rev. 1, Guide to IPsec VPNs. 🏗️ The authoritative guide to IPsec design and configuration; pair with §5.4 when you actually build a site-to-site tunnel.
• NIST SP 800-111, Guide to Storage Encryption Technologies for End User Devices. 🏗️📋 The reference for full-disk encryption decisions (§5.5) — exactly the territory of Case Study 2.
• PCI Security Standards Council, PCI-DSS v4.0 (Requirements 3 and 4: protect stored cardholder data; protect data in transit). 📋📜 The mandate behind Meridian's at-rest and in-transit obligations, tokenization scope reduction, and key-management requirements. We map it fully later in the book.
• IETF, RFC 6960 — Online Certificate Status Protocol (OCSP) and RFC 5280 (X.509 / CRLs). 🏗️ The primary sources for revocation mechanics behind §5.6; read for why revocation is the weak link.
• IETF, RFC 6962 — Certificate Transparency. 🏗️📋 Defines the public append-only logs that detect mis-issuance and double as your endpoint inventory (Case Study 1).

Books (Tier 1)

• Ristić, I., Bulletproof TLS and PKI (2nd ed.). 🏗️📜 The single best practical book on everything in this chapter — TLS protocol internals, cipher suites, certificate and PKI operation, and how to configure and test it all. If you read one thing beyond the RFC, read this.
• Aumasson, J.-P., Serious Cryptography. 🏗️📜 A modern, accessible bridge from Chapter 4's primitives to their application — authenticated encryption (AEAD), key exchange, and the real-world pitfalls. Read it alongside Chapters 4 and 5.
• Anderson, R., Security Engineering (3rd ed.), chapters on protocols and cryptography. 🏗️ The systems view of why cryptographic protocols fail in deployment — almost always at the edges and the key management, exactly this chapter's theme.
• Barker & Barker (eds.), NIST cryptographic-standards corpus (as referenced above). 📋 Not a read-through; the GRC reference shelf for citing approved algorithms and key sizes in a standard.

Free online & tools (Tier 1 / Tier 2)

• Mozilla Server Side TLS (wiki.mozilla.org/Security/Server_Side_TLS). 🏗️ The most-used practical reference for "what cipher configuration should I deploy?" with Modern/Intermediate/Old profiles and a config generator. Tier 1 (vendor security documentation).
• Qualys SSL Labs — SSL Server Test (ssllabs.com). 🏗️🛡️ Free online grader for public endpoints; the model for §5.7's grading. Use it on your own public sites; the grading rubric itself is instructive.
• testssl.sh (testssl.sh) and sslscan / nmap ssl-enum-ciphers. 🏗️🛡️ Open-source, read-only TLS scanners for your own estate (§5.7). The defensive toolkit Case Study 1 uses. Authorized assets only.
• WireGuard whitepaper and documentation (wireguard.com). 🏗️ The protocol's own concise, readable design rationale — a short illustration of "no negotiation = no downgrade." (Tier 2 for the whitepaper's specific claims; the documentation itself is primary.)
• The SSL/TLS attack catalogue (POODLE, BEAST, FREAK, Logjam, Sweet32, ROBOT, Lucky 13). 🛡️📜 Read a reputable retrospective on two or three; understanding how a downgrade or padding-oracle attack worked cements why the red-flag ciphers in §5.3 are retired. (Tier 2: read well-sourced accounts; details vary by retelling.)

Tools to explore (in your own lab only)

• A local TLS test bench. 🏗️ Stand up a web server in your own VM, deliberately misconfigure it (enable TLS 1.0 and a weak cipher), scan it with testssl.sh, then harden it and re-scan — the §5.7 loop, hands on, against a target you own.
• BitLocker / LUKS on a spare machine or VM. 🏗️ Encrypt a test volume, then deliberately trigger and practice recovery (the Case Study 2 lesson) — recovery is the path you will actually use.

⚖️ Authorization & Ethics reminder: The scanners above are read-only, but they still probe systems. Run them only against assets you own or are explicitly authorized to assess. SSL Labs and similar tools are for your public endpoints, not arbitrary third parties.