Join our Newsletter — 33% off our NHI Course

Could 93% concern over AI data exposure still leave 61% using public cloud?

 

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

TL;DR: AI leaders in regulated industries remain split between concern and proof, with Fortanix finding 93% worry about exposing prompts, models or intellectual property while only 50% can fully verify protection during processing. Inference-time exposure means policy alone leaves sensitive data unproved inside public cloud AI services.

Editorial analysis by NHI Mgmt Group, based on content published by Fortanix: “The Enterprise AI Trust Fall: Why Regulated Companies Send Sensitive Data to Infrastructure They Don't Trust”.

By the numbers:

  • 93% of AI leaders are concerned about exposing proprietary prompts, models or intellectual property to AI infrastructure providers.
  • 61% of organisations send sensitive data to public cloud AI services anyway.
  • Only 50% of AI leaders can fully verify that sensitive data stays protected while a model is processing it.

Key questions

Q: Why is encryption not enough for AI systems processing sensitive data?

A: Encryption protects data at rest and in transit, but AI must decrypt and process data to generate outputs.

Q: What are the signs that AI security controls are failing in production?

A: Common warning signs include unapproved model behavior, unexpected data access, prompt leakage, suspicious outbound calls, and runtime actions that do not match the workload’s intended function.

Q: How should organisations govern access to data used by AI systems?

A: Treat AI data access as an identity governance problem, not just a data storage problem.

Practitioner guidance

  • Define inference-time trust as a gating control Require proof that the AI runtime is trustworthy before sensitive data, prompts or model weights are allowed into production inference paths.
  • Bind key release to environment attestation Do not release decryption keys unless the workload, firmware and software stack all match the approved trusted state for that AI deployment.
  • Limit sensitive inputs before model processing Classify and reduce customer data, financial data and proprietary prompts before they reach the AI service so the runtime sees less exposed information.

Bottom line: Regulated enterprise AI is creating a trust gap because organisations can use public cloud AI services without being able to prove that sensitive data remains protected during processing.

Glossary terms: Inference-time exposure, Composite Attestation, Trusted Execution Environment, Key release gating

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
 

Trust in enterprise AI has become a verification problem, not an awareness problem. The article shows that most leaders already understand the risk of exposing sensitive data during AI processing, but many still cannot prove that controls work at inference time. That creates a governance gap between policy intent and runtime assurance, especially in regulated sectors. Practitioners should treat proof of protection as a required control outcome, not an aspirational target.

A few things that frame the scale:

  • 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to the State of Secrets in AppSec.
  • Enterprise AI use rose from 55% of organisations in 2023 to 88% in 2025, according to McKinsey’s Global Surveys on the State of AI.

A question worth separating out:

Q: Should organisations use public cloud AI services for sensitive workloads?

A: Yes, but only when they can prove the processing environment is trustworthy and the data scope is tightly controlled. For sensitive workloads, the decision should depend on whether the organisation can enforce attestation, key-release gating and input minimisation. If not, the safer choice is to limit the workload or keep it out of that service.

👉 Read our full editorial: Regulated enterprise AI still runs ahead of trust controls


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.