Skip to content

Technical

HNDL for security engineers: handshakes, archives, and evidence

Engineers need specifics: which protocol artifacts are harvested, what hybrid TLS changes, and what evidence to attach after remediation.

TLS handshake HNDL flow diagram.
Why Your Encrypted Data Is Already Being Stolen Watch on YouTube

Key terms

ECDH, forward secrecy, key encapsulation, ML-KEM, STARTTLS — see tooltips on the HNDL hub.

Threat model for engineers

AssetHarvested artifactPost-Q-Day attack
TLS 1.2/1.3 (ECDHE)Full handshake + ciphertextSolve ECDLP → derive session keys
RSA-wrapped backupsEncrypted blob + envelopeFactor RSA / break ECIES
Email (S/MIME, PGP)Archived messagesBreak public-key layer
Code signingCertificate + signed artifactsForge signatures

Inventory scope beyond web TLS

Your external scan should include:

  • JWKS endpoints (OAuth/OIDC signing keys)
  • SSH host keys and certificate-based auth
  • SMTP STARTTLS for notification and claims systems
  • Uploaded PEM bundles and K8s TLS secrets

Hybrid TLS migration path

  1. Pilot X25519MLKEM768 or equivalent hybrid KEX on non-production
  2. Capture handshake proof appendix for auditor review
  3. Re-scan to verify PQC-ready classification
  4. Expand to production edge after rollback testing

See ML-KEM framework guide and hybrid TLS blog.

Evidence chain

Auditors want machine-readable inventory (CycloneDX CBOM), signed PDF with /verify link, and drift diffs between scans — not slide decks.

Run inventory · Read CBOM field guide

Continue on the Q-Day hub: Harvest now, decrypt later guide

References & further reading

Authoritative primary sources cited in this article. Summaries are our own — follow links for full context.

Last verified 2026-06-04

See your exposure with evidence

Run a live PQC inventory scan, export a CBOM, and verify signed reports independently.