Quantum XChange says a US federal agency has deployed its Phio TX-EM product across 15 production sites in the United States and internationally, with five more planned. The customer is not identified because of its mission, so the announcement remains a vendor case study rather than an independently verified reference.

The company says the product runs as a container on existing routers, supports multiple algorithms and can change cryptographic methods without network downtime. It presents the deployment as a way to begin post-quantum protection without waiting for a full infrastructure refresh.

That approach addresses a practical migration problem. Large organisations cannot replace every application, router and protocol at once. A crypto-agile layer can create time and flexibility, but it also becomes a critical control point whose configuration, key handling and failure behaviour must be tested.

Buyers should confirm which data paths are covered, how endpoints authenticate, how algorithms are selected, what happens if the control layer fails and how FIPS validation applies to the deployed configuration. They should also maintain a cryptographic inventory; an overlay cannot protect an unknown connection or unsupported legacy system.


Execution Level Governance- What audit-ready agent governance actually looks like
David Girvin, founder and CEO of Assury argues that model-in-the-loop review, AI governing AI, is fundamentally unreliable for regulated environments: even the best-performing models miss a meaningful share of violations, the reviewing model is typically provided by the same vendor being reviewed, and prompt injection or context poisoning can compromise both the acting agent and its supposed overseer simultaneously. He makes the case for deterministic, architecturally enforced controls instead, walking through Assury’s approach of autonomy zones, session risk accumulation, and credential starvation, which lets a compromised agent be cut off from its tools instantly rather than relying on time-boxed access. The conversation touches on why David is sceptical of just-in-time credentialing as a solution for agent security more broadly, since agent sessions don’t run on predictable human timescales, along with the current gap between how identity and security vendors are pitching agent protection and what he sees happening at the execution layer in practice. He also discusses the compliance and audit implications of probabilistic decision-making, arguing that regulated industries will increasingly need tamper-evident, hash-chained audit trails that can withstand scrutiny from auditors and regulators who are only beginning to understand agentic risk, and reflects on a named frontier lab’s own published framework as an example of the gap between research and practitioner reality. Elsewhere, David reflects candidly on building a bootstrapped security company in an increasingly crowded market, why he turned down aggressive VC funding to stay in control of the product, and what a credible third-party assessment of his own gateway would need to look like given that Assury sits directly in the execution path for every customer’s agents.

Share this post
The link has been copied!