Topic
Security Automation
Within the Topic facet, Security Automation topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
CASE FILE
The Name Selected a TLS Context. It Did Not Authorize the Request: SNI and the Authority of a Routing Hint
The gateway received `tenant-a.example` in a ClientHello, selected Tenant A's certificate, and attached Tenant A's policy context. It then let the connection reach a privileged route without a tenant credential. Every TLS selection step had worked. The error was believing that a…
CASE FILE
The Certificate Signature Passed. The Handshake Was Not Finished: TLS 1.3 `Finished` and Transcript Authority
The dashboard declared a secure session when the server's CertificateVerify signature passed. One record later, the client rejected a corrupt `Finished` message and closed the connection. The certificate key had proved one thing accurately. Operations had promoted it into proof…
History
The Token That Proved a Reply Had a Path Back: DNS Cookies Without Identity
A small EDNS option changed what a DNS server could reasonably infer from a UDP source address. It did not identify the sender. It showed, more narrowly and more usefully, that someone at that apparent address had received an earlier reply and returned a server-made token.
History
The Test That Succeeded by Saying Nothing: What Discard Could Actually Prove
An engineer sends a known stream to port 9 and waits for confirmation. None arrives. That is not an omitted feature: RFC 863 requires the Discard service to throw the data away and send no response. The test can still be useful, but only if its operator names which layer produced…
CASE FILE
The Edge Negotiated HTTP/2. The Origin Still Spoke HTTP/1.1: TLS ALPN and the Authority of One Connection
The browser offered `h2` and `http/1.1`. The edge selected `h2`, completed TLS and exchanged valid HTTP/2 frames. A fleet dashboard then labelled the origin “HTTP/2 native.” It was not. The edge terminated that connection and opened a different one upstream, where it sent…
CASE FILE
The CA Was on the List. The Identity Was Not Approved: TLS `certificate_authorities` and the Authority of a Selection Hint
The client chose a certificate whose issuer appeared in the server's CA list. The server built and validated the chain. Then the application rejected the subject because that identity had never been admitted to the tenant. Every cryptographic step could be correct while access…
CASE FILE
The Staple Was Signed. The Status Could Still Be Stale: TLS OCSP and the Authority of a Cached Answer
The certificate was revoked at 10:07. At 10:11, the server still stapled a correctly signed `good` OCSP response whose `nextUpdate` was hours away. Nothing had been forged. The answer was authentic, within its declared interval and already behind reality. The incident began when…
History
The One-for-One Replies That Never Stopped: How Echo and Chargen Formed a Network Loop
The sender can vanish after the first datagram. One machine receives a packet and generates characters for the address named as its source. A second receives those characters and echoes them back. From then on, each reply is the other service's request. Nothing in either…
CASE FILE
The Socket Closed. The Transaction Did Not: TLS close_notify and the Authority of an Ending
The payment service wrote a success response, initiated an orderly TLS shutdown and recorded the request as complete. Its database commit failed milliseconds later. The client had received an authentic ending, but not the fact it needed. `close_notify` said the server would send…
CASE FILE
The Ticket Survived. The Session Did Not: TLS 1.3 Resumption and the Authority of Carried State
The failover node accepted a TLS 1.3 session ticket issued before the user’s access was revoked. Cryptographically, the shortcut worked: the client knew the resumption PSK and its binder covered the new handshake. Operationally, the old decision had crossed into a new connection…
CASE FILE
The Record Was Longer. The Message Was Not: TLS 1.3 Padding and the Authority of Observable Length
The incident report treated a larger encrypted record as a larger application message. Its arithmetic was precise and its conclusion was false. The sender had rounded TLS 1.3 records to a block boundary and sometimes emitted padding-only Application Data. The capture established…
CASE FILE
The First Hello Was Rejected. It Was Not Erased: TLS HelloRetryRequest and the Authority of the Transcript
The capture began with a second ClientHello. It offered one key share, the server accepted it, and the handshake completed. Read in isolation, the trace appeared to prove that the client had chosen that group from the start. It proved nothing of the kind. The missing first flight…
History
The Retraction That Had to Travel as News: How Usenet Made Cancellation a Local Decision
One cancel article reaches three news servers. The first already holds the named post and withdraws it. The second rejects the request under local policy. The third has not yet seen the post, so it remembers the Message-ID and refuses the late arrival. Nothing in that sequence…
CASE FILE
The Client Expected a Certificate. The Library Accepted a Key: TLS Raw Public Keys and the Authority of Negotiation
The key was mathematically usable. That was precisely the problem. In June 2026, wolfSSL disclosed that an RPK-enabled build could accept an unnegotiated Raw Public Key where the peer expected X.509, bypassing certificate-chain validation. The repair did more than reject a format…
CASE FILE
The Proof Arrived After the Connection Began. It Did Not Rewrite the Past: TLS Exported Authenticators and Application Authority
At 14:03, a valid certificate proof arrived on a connection that had already carried hundreds of operations. The service upgraded every stream and relabelled five earlier minutes as authenticated by the new identity. The signature was sound. The history was not. TLS Exported…
History
The Bytes That Had to Wait for Permission: How IMAP Literals Traded a Round Trip for a Resource Boundary
An IMAP client could finish a line with `{11}`, announce exactly how much data came next—and then stop. The eleven octets were not late, lost or flow-controlled by TCP. They were waiting for a one-character reply from the server: `+`. That pause turned a count into a permission…
CASE FILE
The Certificate Had Not Been Verified. Its Memory Claim Already Had to Be Judged: TLS Compression and the Pre-Trust Boundary
A two-kilobyte handshake message says it will become twelve megabytes after decompression. Before the receiver can inspect a name, a signature or a chain, it must decide whether that unauthenticated claim deserves memory and CPU. RFC 8879 makes certificates smaller on the wire…
CASE FILE
The Edge Received a Key. It Did Not Receive the Certificate: TLS Delegated Credentials and the Boundary of Short-Lived Authority
A front end can finish a TLS 1.3 handshake for the certificate owner without holding the certificate’s long-term private key. What crosses that boundary is powerful but deliberately small: a signed public key, a role, an algorithm and an expiry—not the certificate, the CA…
History
The Empty Query That Listed Everyone: How Finger Made Human Presence a Network Reply
Send no name, no password and no command word—only a carriage return and line feed—to a remote service on port 79. In the original Finger protocol, that empty line asked the host to list everyone currently using it. The exchange was tiny. The disclosure could include a room…
CASE FILE
The Peer Requested New Keys. It Did Not Own the Epoch: TLS 1.3 KeyUpdate and the Authority to Rotate a Live Connection
One encrypted record leaves under the old key. Every later record from that sender must use the next one. The peer can authenticate the transition and ask for a reciprocal change, but it cannot see whether yesterday’s secret left memory, choose the other endpoint’s work queue, or…