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.
Creators
Russ White and the discipline of containing network complexity
Russ White and the discipline of containing network complexity intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
IETF
Protocol Upgrades Need a Receipt for the Evidence They Retire
A protocol can become more private, efficient and interoperable while making an established detection or forensic question impossible to answer. That trade is governable only when the disappearing evidence, its replacement and the authority accepting the gap are recorded before…
IETF
A Valid OAuth Chain Cannot Prove Its Own Beginning
A signed route through OAuth brokers can show that nobody rearranged the route it contains. It cannot show that the first visible broker was truly the first entity. Revision 01 of a new individual Internet-Draft now states that limit plainly and leaves the decisive origin…
IETF
STAMP’s C Flag Does Not Name the Limit That Changed the Test
A reflector can lawfully replace a requested train of test packets with one marked response. The bit explains that the request was constrained; it does not preserve the local rule that constrained it or what the change did to the measurement.
IETF
One Bit Opens the IKEv2 Header, Not the Peer’s Memory Budget
An IKEv2 peer can say that it understands an extended payload header without promising how much memory, CPU time or concurrent work it will spend on the payload that follows. Revision 08 of an IPSECME candidate draft preserves that important gap: the proposed signal is a parsing…
Story
RIPE NCC Is Running Four Security Programmes at Once. Their Handoffs Need a Public Map
RIPE NCC’s quarterly plan puts audit work, risk management, application security and monitoring on four adjacent lines, all marked “In progress”. That is useful disclosure, but not yet a view of how evidence moves between them. A small public handoff map would let members…
North America Cloud Services Trends
Everbridge Bought More Signals; It Still Needs an Escalation Ledger
The attractive word in Everbridge’s acquisition of Open Measures is “earlier”. Open Measures follows public conversations across mainstream and alternative platforms; Everbridge coordinates risk events around people, places and assets. Joining the two could shorten the distance…
Global Cloud Services Trends
Newfold's certificate switch moves work to renewal time
A new certificate supplier does not finish a website's renewal. The commercial test is who handles the work between issuing a replacement and putting it into service.
IETF
A New security.txt Draft Splits the Inbox, Not the Product Boundary
A vulnerability report can reach the address a vendor prefers and still arrive at the wrong owner. A new individual Internet-Draft gives `security.txt` publishers a way to separate product reports from reports about their web infrastructure. What it does not supply is the missing…
IETF
SMTPUTF8 Draft Makes Invisible Unicode a Mailbox Admission Test
Two email addresses can occupy the same pixels and still contain different protocol input. Revision 05 of an IETF draft now makes that discrepancy part of the admission decision: a code point that renders as nothing does not disappear from the address a system is asked to accept.
Global Cloud Services Trends
Kiteworks buys Bonfy.AI; business context still needs upkeep
The acquisition brings contextual data classification into Kiteworks' integration plan. Its value depends on keeping the underlying relationships current, not simply putting two products under one owner.
IETF
An OAuth Remediation Challenge Is an Authority Proposal, Not a Retry Hint
A payment request fails, and the client receives an unusually helpful answer. The resource server does not merely say no. It supplies the structured authorization it says would make the operation acceptable. The client can carry that entity into a new OAuth flow and try again.…
Story
LACNIC's Election Recovery Defaults to ALL. One Email Search Reaches Vote, Nomination and Support Links
Convenience has a constitutional edge when the thing being recovered is not an account but a power. LACNIC’s newly published election code can use one email address to find three kinds of tokenised link. The missing record is not another log of clicks. It is a receipt showing why…
IETF
MPLS-IOAM Turns Unknown Load Balancing into a 19-Bit Constraint
A sequence counter is supposed to distinguish packets, but in an MPLS label stack its changing bits can also become accidental steering input. Revision 14 of an IETF MPLS-IOAM draft now says what to do when nobody can establish how a node balances traffic: keep a specific 19-bit…
History
Pål Spilling and the Cable That Made Norway Both Reachable and Vulnerable
Norway’s first Internet connection was a door to a global research community—and, for a time, a single physical point at which that door could be shut. Pål Spilling’s career shows why a network’s topology is also a map of authority: it decides who can connect, who absorbs…
IETF
DKIM2’s “Unaligned” Flag Can Produce a Pass Without Proving Alignment
A green result normally suggests that a test succeeded. Revision 01 of a new DKIM2 sender-policy proposal creates a more delicate possibility: an alignment result can say `pass` because alignment was expressly not required. The distinction is governable only if the reason travels…
IETF
A Valid Signature Does Not Prove What the Approver Saw
A revised proposal for high-risk action receipts has drawn a line that many approval systems blur: signed action bytes, a reconstructable screen, a trustworthy display and a valid mandate are four different things. Revision 01 now says so explicitly—and leaves the final…
IETF
The Parser Stopped. The Header Did Not Disappear: RFC 9740
A traffic report can register no use of a header because the header was absent, because an old field could not represent it, or because the exporter stopped looking. RFC 9740 gives those differences a more precise vocabulary. The consequential decision is whether a collector…
IETF
The old connection is the test
An accepted QUIC configuration and a healthy service can coexist without proving that the connection already carrying work adopted the change. Revision 08 of the QUIC YANG draft puts that missing proof inside the implementation: the operational question is what changed in the…
IETF
A Call-Home Datagram Is Not Device Authority
A managed router may need to reach an operator from behind an address translator or firewall. The newest NETCONF working-group draft adapts Call Home to QUIC by having the device send an empty UDP datagram and the management system connect back to its source. The mechanism is…