Subscribe to the Non-Human & AI Identity Journal

Notifications
Clear all

AI governance gaps are widening as policy outpaces controls


(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 3218
Topic starter  

TL;DR: The White House’s AI Action Plan pushes faster AI adoption, infrastructure build-out, and secure-by-design expectations, but the article argues that governance will increasingly fall to industry as federal guardrails loosen and questions about training data, bias, and sensitive-data use remain unresolved, according to Cyera. The practical issue is not ambition but whether organisations can prove their AI data, model, and agent controls are trustworthy enough to absorb the policy shift.

NHIMG editorial — based on content published by Cyera: It’s Up to Industry to Regulate AI: The White House’s AI Action Plan is long on ambition, but short on guardrails

By the numbers:

  • The Plan cuts federal science funding by 34 percent, including math and physics at $289 million, engineering at $127 million, computer science at $85 million, and technology at $18 million.

Questions worth separating out

Q: How should organisations govern AI systems that can access sensitive training data?

A: Organisations should treat sensitive training data as a governed input, not a loose repository.

Q: Why do AI applications and agents create new access risks for IAM teams?

A: AI applications and agents can request data, call tools, and move information across systems faster than traditional review cycles were designed to track.

Q: What do security teams get wrong about secure-by-design AI governance?

A: They often treat secure-by-design as a policy label instead of an enforceable operating model.

Practitioner guidance

  • Inventory AI-connected identities and data paths Map every AI application, agent, service account, and API key that can touch training, retrieval, or output workflows.
  • Gate sensitive data before model ingestion Require classification and policy checks at the point where training data, fine-tuning data, or retrieval content enters the AI pipeline.
  • Apply least privilege to AI tool use Limit every AI-connected identity to the smallest set of tools, prompts, datasets, and export paths needed for its task.

What's in the full article

Cyera's full analysis covers the operational detail this post intentionally leaves for the source:

  • The article’s specific commentary on the White House AI Action Plan and the policy trade-offs it introduces for enterprises.
  • Cyera's description of how its AI-native platform discovers and classifies sensitive data in AI training sets and AI applications.
  • The article’s examples of bias, training-data curation, and the governance challenge of defining objective truth in practice.
  • The source article’s closing guidance on how organisations should think about secure AI adoption at scale.

👉 Read Cyera’s analysis of the White House AI Action Plan and AI governance →

AI governance gaps are widening as policy outpaces controls?

Explore further

View Full Forum →  |  NHI Foundation Course →



   
Quote
(@mr-nhi)
Member Moderator
Joined: 4 weeks ago
Posts: 1804
 

AI governance is becoming an identity problem, not just a policy problem. Once AI systems are allowed to train on sensitive material and act across enterprise tools, the key question is no longer whether the model is clever. It is which identities can reach which data, under what policy, and with what proof of restraint. That shifts the centre of gravity from model quality to access governance, classification, and runtime enforcement.

A few things that frame the scale:

  • The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
  • Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap.

A question worth separating out:

Q: How do AI data controls differ from traditional access control?

A: Traditional access control focuses on who can open a system or file. AI data control must also govern what gets ingested, what gets retained in model behaviour, and what can be reproduced in outputs. That makes the control surface broader, because risk can appear both before training and after deployment.

👉 Read our full editorial: AI governance gaps widen as policy outpaces guardrails



   
ReplyQuote
Share: