Why does the TLS handshake use both public key and symmetric key cryptography?

Why This Matters for Security Teams

TLS is often explained as a protocol detail, but for security teams it is really a pattern for balancing trust establishment with operational performance. public key cryptography solves the hard problem of proving who is on the other end and protecting the first exchange, while symmetric cryptography handles the steady-state traffic efficiently. That split matters because identity failures usually happen before encryption does, and once a session is established, speed and scale become the practical constraint.

The same lesson shows up in NHI governance. Authentication and credential exchange must be strong at the start, but long-lived or overexposed secrets become the real weakness over time. NHI Mgmt Group’s research on the Ultimate Guide to NHIs notes that 80% of identity breaches involved compromised non-human identities such as service accounts and API keys, which is a reminder that the setup phase is not where most organisations fail. In practice, many security teams discover that the handshake was sound only after the session, token, or secret has already been abused.

How It Works in Practice

During a tls handshake, public key cryptography establishes trust and negotiates a shared session secret. The server presents a certificate, the client validates it, and key exchange mechanisms such as ephemeral Diffie-Hellman create fresh keying material without sending the symmetric key in the clear. After that, both sides switch to symmetric encryption for the actual data stream because it is far more efficient for high-volume traffic.

That division of labour is exactly why TLS remains a useful mental model for modern identity design. Public key operations are computationally expensive but excellent for identity proof and key agreement. Symmetric algorithms are faster and better suited to continuous packet flow, which is why they protect the bulk of the session. Standards such as ISO/IEC 27001:2022 Information Security Management and PCI DSS v4.0 both reinforce the broader principle: strong authentication must be paired with secure ongoing protection, not treated as a one-time event.

For NHI-heavy environments, the practical parallel is workload identity plus short-lived secrets. A service, agent, or application should prove what it is with cryptographic identity, then receive ephemeral credentials scoped to a narrow task and automatically revoked when the task ends. That is the same design logic as TLS: authenticate first, then protect data efficiently with a shared session mechanism. The Schneider Electric credentials breach is a reminder that static or exposed credentials create failure conditions that no fast encryption layer can fully compensate for.

These controls tend to break down in legacy systems that cannot support modern certificate validation, short-lived tokens, or automated rotation because the security model depends on static secrets persisting far longer than the session itself.

Common Variations and Edge Cases

Tighter key management often increases operational overhead, requiring organisations to balance stronger cryptographic assurance against interoperability, latency, and certificate lifecycle complexity. That tradeoff is especially visible when older protocols, embedded devices, or partner integrations still depend on static keys or long-lived trust anchors.

There is also no universal standard for every handshake implementation detail. Some environments optimise for performance with session resumption, while others prioritise forward secrecy or mutual authentication. The core principle remains stable, but the exact cryptographic choices vary by risk appetite and deployment constraints. Best practice is evolving toward shorter-lived credentials, stronger certificate automation, and tighter revocation handling because static trust objects age poorly.

For NHI and agentic systems, the lesson is not simply “use more encryption.” It is to separate identity proof from bulk protection, then make both parts ephemeral where possible. That aligns with the same governance pressure seen across NHI programs: keep authentication strong, limit credential lifetime, and reduce exposure windows before attackers can reuse what was issued for convenience.

Related resources from NHI Mgmt Group

• Why do digital signature certificates depend on public key infrastructure for trusted document verification?
• What breaks when key distribution for symmetric cryptography is handled poorly?
• What is the difference between public TLS and private PKI for non-browser authentication use cases?
• How should security teams implement SSL certificates for public websites and customer portals?