IonQ has entered a definitive agreement to acquire Zero Trust microsegmentation company Elisity in an all-stock transaction valued at up to $1.3 billion, including a performance-based earnout. The deal has not yet closed and remains subject to customary conditions.

Elisity builds policy around the identity and context of devices, users and workloads rather than relying only on network location. IonQ says the acquisition will help connect its post-quantum cryptography and quantum key distribution ambitions with a broader security architecture for discovering assets and enforcing access policies.

The strategic logic is more important than the “quantum” label. A post-quantum migration does not end with replacing cryptographic algorithms. Enterprises also need to know where vulnerable cryptography is used, which systems communicate, which identities are trusted and how access can be reduced while changes are made.

For financial institutions, the announcement is a prompt to join cryptographic inventory, identity governance and microsegmentation programmes. It also requires vendor scrutiny: customers should distinguish products available now from roadmap claims, and assess integration, lock-in and execution risk after the acquisition. The practical goal is crypto-agility backed by enforceable, least-privilege connectivity.


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!