TLS
Transport Layer Security (TLS) is a cryptographic protocol that protects network communications through confidentiality, integrity, and authentication of communicating endpoints.
Real-World Cryptography
TLS is the Transport Layer Security protocol for securing network communications through authentication, confidentiality, and integrity.
- How it is used
- Secures communications between browsers, servers, mobile applications, devices, and other networked applications.
- How deep it goes
- Explains TLS phases, TLS 1.3 negotiation, certificate chains, encrypted records, replay risks, and deployment warnings without implementation-level detail.
- Examples
- Uses Go client and server listings, browser certificate chains, OpenSSL certificate output, and TLS 1.3 handshake diagrams.
- What you can do after
- Operate/configure TLS clients and servers, choose supported versions, understand handshakes, and recognize certificate and 0-RTT failure risks.
Software Security for Developers
TLS is a cryptographic protocol standard that provides confidentiality, integrity, and authenticated communication over networks.
- How it is used
- Secures browser, server, API, and service-to-service communication across untrusted networks.
- How deep it goes
- Explains threats, handshake roles, certificates, mTLS, deployment, and pitfalls while stopping short of cryptographic mathematics.
- Examples
- Uses browser connections, hostile Wi-Fi, man-in-the-middle attacks, certificate warnings, local private CAs, and microservice communication.
- What you can do after
- Configure TLS safely, distinguish TLS from mTLS, validate certificates, and diagnose common connection and deployment mistakes.
ASP.NET Core in Action, 3e
Transport Layer Security is a cryptographic protocol that provides authenticated and encrypted communication over a network.
- How it is used
- Protects users and applications by encrypting web traffic and preventing network attackers from reading or changing it.
- How deep it goes
- Explains HTTPS risks, deployment choices, and enforcement techniques but defers protocol details and certificate mechanics.
- Examples
- Uses browser traffic, public Wi-Fi interception, web APIs, Razor Pages applications, and reverse-proxy passthrough or offloading.
- What you can do after
- Operate/configure HTTPS in ASP.NET Core applications using direct TLS, reverse-proxy handling, request rejection, and HSTS.
Logs and Telemetry
Transport Layer Security is a cryptographic protocol that authenticates endpoints and protects network communications against interception and tampering.
- How it is used
- Secures network-centric log and event traffic handled by Fluent Bit plugins.
- How deep it goes
- Explains TLS through flags, certificate files, CA verification, and HTTP and forwarding configurations.
- Examples
- Uses an HTTPS listener with certificate paths and a Fluent Bit-to-Fluentd forwarding scenario.
- What you can do after
- Operate/configure protected Fluent Bit HTTP inputs and forwarding connections with certificate-validation choices.
Google Anthos in Action
Transport Layer Security is a cryptographic protocol that protects network communications with confidentiality, integrity, and endpoint authentication.
- How it is used
- Secures service-mesh traffic and cloud-management connections through encryption, authentication, and integrity protection.
- How deep it goes
- Explains encryption, signatures, integrity checks, certificates, mutual authentication, and automated rotation.
- Examples
- Uses Istio workload certificates and a Connect Agent’s persistent outbound TLS 1.2 tunnel as deployment examples.
- What you can do after
- Operate/configure encrypted service and cloud-management channels while selecting certificate-authority and network-exposure arrangements.
Kafka for Architects
TLS is a cryptographic protocol that authenticates endpoints and protects data in transit through encryption and integrity checks.
- How it is used
- Protects Kafka data in transit and supports endpoint authentication within an enterprise security architecture.
- How deep it goes
- Explains certificate materials, setup sequence, mTLS, and broker/client properties, while deferring detailed troubleshooting and component-specific configuration.
- Examples
- Uses certificate-generation diagrams plus broker and client configuration listings as concrete implementation artifacts.
- What you can do after
- Operate/configure Kafka TLS by generating certificates, preparing keystores and truststores, and applying broker and client properties.
gRPC Microservices in Go
SSL/TLS is a family of cryptographic communication protocols that authenticates peers and encrypts data exchanged over a network.
- How it is used
- Protects gRPC communication between microservices and at a Kubernetes Ingress boundary.
- How deep it goes
- Works through Go client and server credential configuration and Ingress setup, while deferring production certificate management and omitting certificate-password encryption.
- Examples
- Uses Go transport-credential listings for both peers and a Kubernetes Ingress manifest for a locally signed certificate.
- What you can do after
- Operate/configure TLS credentials for Go gRPC peers and TLS settings for a Kubernetes Ingress.
Authorization in Action
Transport Layer Security is a cryptographic protocol that provides secure communication over a network, including encryption and peer authentication.
- How it is used
- Protects web communication and authenticates servers so browsers can preserve trusted relationships with websites and applications.
- How deep it goes
- Explains encrypted channels, certificate-based authentication, visible metadata, and common weaknesses without detailing cryptographic internals.
- Examples
- Uses an anonymous health consultation, an eavesdropper, browser locks, deceptive domains, and certificate failure scenarios.
- What you can do after
- Evaluate secure web connections by distinguishing encrypted content from exposed metadata and checking what certificates actually authenticate.
Hacking Cryptography
TLS is a cryptographic protocol for securing communications over computer networks.
- How it is used
- Replaces custom message-encryption protocols with established TLS versions and algorithms.
- How deep it goes
- Positions TLS as an engineering recommendation but stops short of handshake, implementation, attack, or configuration detail.
- Examples
- Uses replacing a self-written message-encryption protocol with TLS as the concrete engineering example.
- What you can do after
- Apply TLS through recommended versions and algorithms instead of writing a custom cryptographic protocol.
MongoDB 8.0 in Action, Third Edition
TLS is a cryptographic network protocol that provides encrypted communication and server or client authentication over a network connection.
- How it is used
- Secures application-to-Atlas and inter-node communication against disclosure and modification during transmission.
- How deep it goes
- Explains encrypted channels, TLS version selection, certificates, ephemeral keys, and operational key handling.
- Examples
- Uses customer data sent to Atlas and traffic exchanged between Atlas cluster nodes as protected communication examples.
- What you can do after
- Operate Atlas TLS protection and select a supported TLS version while understanding its key-management safeguards.
Read how MongoDB 8.0 in Action, Third Edition explains TLS →
Learn Docker in a Month of Lunches, Second Edition
TLS is a cryptographic protocol that provides encrypted and authenticated communication over a network.
- How it is used
- Deploys HTTPS at a reverse proxy while keeping TLS configuration and certificate management outside application containers.
- How deep it goes
- Shows certificate generation and Nginx configuration, but defers detailed protocol and cipher selection.
- Examples
- Uses a self-signed certificate, image-gallery.local, Docker-mounted certificate files, and an Nginx HTTPS server block.
- What you can do after
- Operate/configure HTTPS by generating certificates, enabling Nginx TLS, redirecting HTTP traffic, and reloading the proxy.
Read how Learn Docker in a Month of Lunches, Second Edition explains TLS →
Data-Driven Cybersecurity
TLS is a cryptographic protocol that provides secure communication over a network by protecting data confidentiality and integrity and authenticating endpoints.
- How it is used
- Protects data in transit across internet communications, especially exchanges between user devices and servers.
- How deep it goes
- Explains TLS’s security role, threats, HTTPS use, endpoint authentication, and version requirements without detailing protocol internals.
- Examples
- Uses HTTPS between a user device and server and contrasts TLS with VPN protection for transmitted data.
- What you can do after
- Evaluate TLS choices by checking protocol versions and identifying protections against eavesdropping, tampering, and endpoint risks.
Kubernetes for Developers
TLS is a cryptographic protocol that encrypts network communication and can authenticate endpoints using certificates.
- How it is used
- Secures Kubernetes web traffic while shifting TLS processing from application servers to an Ingress load balancer.
- How deep it goes
- Explains termination, re-encryption, certificates, Secrets, and traffic passthrough, but does not detail certificate-authority procedures.
- Examples
- Uses OpenSSL commands, a kubectl TLS Secret, an Ingress manifest, and browser access to an HTTPS endpoint.
- What you can do after
- Operate/configure TLS with OpenSSL, kubectl, Kubernetes Secrets, and Ingress manifests.
Grokking Web Application Security
TLS is a cryptographic protocol that provides confidentiality, integrity, and authentication for network communications.
- How it is used
- Secures web-server traffic in transit against interception, impersonation, and undetected modification.
- How deep it goes
- Explains certificates, handshakes, and cipher-suite roles, then stops short of implementation internals.
- Examples
- Uses browser padlocks, self-signed certificate warnings, AWS Certificate Manager, HSTS, and certificate-transparency monitoring.
- What you can do after
- Operate/configure HTTPS by obtaining certificates, enforcing secure transport, and revoking compromised or expired credentials.
Apache Kafka in Action
Transport Layer Security (TLS) is a cryptographic protocol that provides authenticated, encrypted communication and protects network traffic from eavesdropping and tampering.
- How it is used
- Secures Kafka client, broker, and ZooKeeper communication during deployment and migration.
- How deep it goes
- Explains keys, certificate authorities, keystores, truststores, listeners, and performance trade-offs, but defers detailed keytool commands.
- Examples
- Uses dual PLAINTEXT and SSL listeners, PKCS12 broker stores, CA truststores, and sequential cluster migration as concrete examples.
- What you can do after
- Operate/configure encrypted Kafka communication and plan a gradual migration while checking configuration and performance risks.
Related concepts
- HTTPSused by · HTTPS is HTTP carried over TLS, which provides encryption and endpoint authentication for network communication.
- public key cryptographyuses · Public-key cryptography is asymmetric cryptography that uses mathematically related public and private keys for encryption, decryption, signing, and verification.
- cipher suiteuses · A cipher suite is a defined or negotiated combination of cryptographic algorithms and parameters used to secure a communication session.
- heartbeat extensionhas part · The TLS heartbeat extension is a protocol extension that lets a peer request an arbitrary payload to be echoed for connection liveness checking.
- TCPuses · TCP is a connection-oriented transport-layer protocol that provides reliable, ordered delivery of byte streams between network endpoints.
- symmetric key encryptionuses · Symmetric-key encryption is cryptography that uses the same shared secret key, or equivalent derived key material, to encrypt and decrypt data.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.