TL;DR: Data in use is the pressure point for regulated AI, secrets, and multi-party workloads, Anjuna reports. Trusted execution environments and attestation make runtime trust explicit when memory exposure would otherwise be hard to govern.
Editorial analysis by NHI Mgmt Group, based on content published by Anjuna: “Confidential Computing: The Critical Enabler for AI-First CIOs in 2026”.
Key questions
Q: Why does data-in-use risk matter even when data is encrypted at rest?
A: Encryption at rest protects stored data, but it does not stop privileged infrastructure from seeing the data while it is being processed.
Q: What are the signs that a workload should move into a confidential computing model?
A: Look for workloads where administrators, cloud operators, or insiders could observe sensitive data during execution, where compliance requires stronger evidence of runtime integrity, or where AI and secrets handling make ordinary cloud trust assumptions too broad.
Q: How should organisations decide which workloads need confidential computing first?
A: Start with workloads that process regulated data, partner data, or high-value secrets where exposure in memory would create material risk.
Practitioner guidance
- Define enclave-worthy workloads Prioritise AI, secrets-bearing, and regulated-data workloads that cannot tolerate exposure during processing.
- Bind key release to attestation Require cryptographic attestation before secrets or keys are released into the workload environment.
- Inventory workload identity paths Map which service accounts, automation jobs, and workload identities can reach sensitive data flows.
Bottom line: Confidential computing addresses a real gap in conventional encryption by protecting data while it is being processed, not only when stored or transmitted.
Glossary terms: Data In Use, Trusted Execution Environment, Cryptographic Attestation, Workload Identity
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Confidential computing is becoming a runtime trust control, not just a data protection control. Traditional encryption stops at rest and in transit, but modern AI and regulated workloads create a third exposure point during computation. That means the relevant governance question is no longer whether data is encrypted, but whether the execution environment itself is trustworthy enough to receive sensitive inputs. For identity programmes, this shifts control emphasis toward attested workload identity and constrained runtime access.
A question worth separating out:
Q: What should teams do when confidential computing is needed but application rewrites are unrealistic?
A: Choose deployment patterns that allow existing containerised workloads to run inside trusted execution environments without redesigning the application stack. The practical aim is to reduce runtime exposure and strengthen trust evidence without forcing a broad rebuild of the service architecture.
👉 Read our full editorial: Confidential computing closes the data-in-use gap for AI workloads