Join our Newsletter — 33% off our NHI Course

AI security in production: can your controls prove trust in use?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Protecting data in use, not just data at rest or in transit, is now the weak point in enterprise AI security, according to Fortanix. AI workloads need attestation and tighter governance before sensitive inputs and models reach runtime.

Editorial analysis by NHI Mgmt Group, based on content published by Fortanix: “A Guide to Enterprise AI Security”.

By the numbers:

  • 93% of AI leaders know that traditional encryption does not protect data while it is processed in memory, according to Fortanix.

Key questions

Q: Why do traditional encryption controls fall short for enterprise AI?

A: Because encryption usually protects data at rest and in transit, while AI systems process data in memory.

Q: What happens when an AI agent is allowed to act without per-action approval and audit?

A: The session can move from low-risk work to irreversible change in seconds.

Q: What should teams do before moving AI workloads into production?

A: Teams should define separate access controls for model serving, GPU provisioning, and supporting infrastructure before production rollout.

Practitioner guidance

  • Protect sensitive AI workloads in trusted execution environments Run training and inference for sensitive data inside hardware-based trusted execution environments so prompts, weights, and data remain protected during processing.
  • Bind key release to attestation evidence Require successful attestation before releasing encryption keys, model weights, or datasets, and block unverified environments from starting sensitive workloads.
  • Treat AI agents as privileged identities Define what each agent may access, modify, and automate, then apply least privilege, separation of duties, and quorum approval for sensitive actions.

Bottom line: Enterprise AI security fails when organisations assume conventional encryption is enough to protect data that is being processed in memory.

Glossary terms: Data In Use, Attestation, Trusted Execution Environment, Agentic AI

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Enterprise AI security is becoming an identity and key governance problem, not just a model protection problem. The article is right to separate storage encryption from in-use protection, because AI workloads expose data in memory where normal safeguards no longer hold. That shifts the control question to who or what can gain access, under what proof, and with what audit trail. Practitioners should treat AI runtime authority as part of the identity model, not as a separate technical layer.

A few things that frame the scale:

A question worth separating out:

Q: Should organisations prioritise attestation or access control for AI systems?

A: They should treat them as linked controls, but attestation comes first when the goal is to protect sensitive in-use data. Access control decides who may request action, while attestation decides whether the environment is trustworthy enough to receive keys and datasets. Without proof of environment integrity, access control alone is incomplete.

👉 Read our full editorial: Enterprise AI security now depends on proving data protection in use


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.