Encrypting AI In Use

Today's encryption methods – from AES to TLS – were designed long before AI and high-speed, data-driven computation became central to business operations. They excel at protecting data at rest (stored on disk) and in motion (transmitted across networks), but they weren't built to safeguard data in use, which includes data actively processed by AI systems.

This distinction matters profoundly. To achieve truly secure or compliant AI, organizations need protection that extends beyond the traditional "before and after." They need technology that keeps data secure even while it's being computed on, akin to how Secure Sockets Layer (SSL) technology secured the early Internet. Without such an advancement, the potential for catastrophic data leakage is enormous.

The Fatal Flaw: The Memory Exposure Problem

In a typical AI workload, data usually remains in memory at all times. For performance reasons, this data is not encrypted. As a result, while the data is stored in the GPU's memory (VRAM)—which is essentially the entire time the AI system is running—it stays in plaintext and is therefore vulnerable.

This creates an opportunity for attackers to steal your AI model, prompts, related documents, and even the AI's responses.

The memory exposure problem runs deeper than many executives realize. During AI processing, plaintext data and model weights are loaded into the system's Random Access Memory (RAM) or Video Random Access Memory (VRAM) on a Graphics Processing Unit (GPU) for computation. Unlike traditional applications that may clear memory after use, most AI frameworks keep this data resident in memory long after inference completes to maximize performance and efficiency. This performance shortcut creates a severe exposure in two ways:

That performance shortcut comes with a heavy security cost. In most cloud or multi-tenant environments, system administrators, cloud operators, and third-party service engineers have access to bus traffic or driver-level hooks. A single compromised account at that level could capture model weights or input data in cleartext as it flows through the cluster.

In essence, traditional encryption only protects data before and after computation. During inference, when the data is actually being used, it remains dangerously exposed.

The New Standard: Cryptographic Guarantees for AI

To close this persistent vulnerability, protection must extend into the runtime environment so sensitive data and models never appear in plaintext at any stage. This requirement is driving the development and adoption of advanced cryptographic frameworks, known broadly as Confidential AI.

Confidential AI leverages technologies like Fully Homomorphic Encryption (FHE) and Trusted Execution Environments (TEEs) to achieve this "in-use" security:

By implementing these technologies, organizations achieve true "in-use" encryption:

Why This Matters for Business and Compliance

The demand for "in-use" security is driven by more than just technical best practice; it's a strategic necessity for compliance and preserving enterprise value.

"In use" encryption is not an optional extra; it is the logical next step in AI security. It is the only way to deploy AI in the cloud, across borders confidently, and in multi-tenant settings – knowing your secrets stay secret, always.