TL;DR: The real issue is not visibility alone but whether AI risk management can be embedded into operating models fast enough to keep pace with deployment, as Cranium and ISTARI say their partnership combines AI security tooling with advisory execution to help enterprises operationalise governance across internal and third-party AI systems.
NHIMG editorial — what this means for NHI practitioners
Questions worth separating out
Q: How should security teams operationalise AI governance across internal and third-party systems?
A: Security teams should connect discovery, testing, approval, and monitoring to the workflows that already govern change and risk.
Q: Why do AI governance programmes fail when security and advisory ownership is split?
A: They fail because no single team owns the full decision chain from risk identification to remediation and evidence retention.
Q: How can organisations govern third-party AI systems without losing accountability?
A: They need explicit ownership, control evidence, and review cadence for every external AI dependency.
Practitioner guidance
- Define a single owner for AI governance decisions Assign one accountable function for approvals, exceptions, and evidence retention across internal and third-party AI systems so the control model does not fragment across security, risk, and delivery teams.
- Tie AI discovery to operational workflows Feed discovery, testing, and compliance findings directly into change management, procurement, and deployment gates so controls are enforced where AI systems actually move into use.
- Map third-party AI dependencies before production Record which external systems, advisory partners, and integrated platforms participate in AI delivery, then assign control evidence and review cadence to each dependency.
What's in the full announcement
Cranium's full article covers the operational detail this post intentionally leaves for the source:
- The partnership framing and product positioning behind Cranium's AI security and governance platform integration
- Named capabilities for automated discovery, security testing, and real-time compliance monitoring across internal and third-party AI systems
- The vendor's own explanation of how ISTARI's advisory-led execution is intended to fit into enterprise operating models
- The full press-release wording around regulatory alignment and enterprise integration that this post has condensed into practitioner implications
👉 Read Cranium's announcement on its AI security and governance partnership with ISTARI →
Cranium and ISTARI partnership: what changes for AI governance teams?
Explore further
This partnership is a signal that AI governance is moving from policy design to operating-model enforcement. The article frames the problem correctly: enterprises can no longer treat AI oversight as a document set or a periodic review cycle. When AI adoption spreads across internal and third-party systems, governance only matters if it changes how decisions are made, who approves them, and what evidence is retained. Practitioners should read this as a sign that AI governance is becoming an execution discipline, not a compliance appendix.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities.
A question worth separating out:
Q: What should boards look for to tell whether AI governance is actually working?
A: Boards should look for evidence that governance findings change operational decisions. Useful signals include delayed releases, escalated exceptions, documented remediation ownership, and reduced reliance on manual approval chains. If governance only produces reports, it has not become part of the operating model.
👉 Read our full editorial: Cranium and ISTARI partnership expands enterprise AI governance