- ServiceNow expanded its AI Control Tower at Knowledge 2026 into a cross-platform governance layer.
- The Control Tower governs AI agents on Salesforce Agentforce, Microsoft Copilot, and other enterprise systems.
- NVIDIA’s BlueField data processing units provide hardware-level enforcement for the Control Tower.
At Knowledge 2026 in October 2026, ServiceNow expanded its AI Control Tower into a cross-platform governance layer, one that claims authority over AI agents running on Salesforce, Microsoft Copilot and other enterprise systems, not just its own Now Platform. The pitch is blunt: as enterprises accumulate agents from multiple vendors, the custom integration code holding them together creates audit gaps, compliance exposure and sprawl that no single team can track.
At Knowledge 2026, ServiceNow expanded its AI Control Tower into a cross-platform governance layer, one that claims authority over AI agents running on Salesforce, Microsoft Copilot and other enterprise systems, not just its own Now Platform.
Custom Code Creates Blind Spots
Connecting AI agents to enterprise applications, Salesforce CRM, NetSuite ERP, ServiceNow ITSM, has historically meant building substantial custom glue code. Enterprise data lives in siloed systems with inconsistent formats and terminologies, so teams reach for API wrappers, custom scripts and middleware like n8n or Zapier to bridge agents built on LangChain or CrewAI to their core platforms. It works, until it doesn’t.
The ad-hoc approach produces integrations that are hard to monitor, hard to secure and harder still to update. Data compatibility issues compound under concurrent agent workloads. Observability gaps widen as more agents ship. When employees start building their own personal agents alongside vendor-deployed ones, the lack of consistent governance becomes a live compliance problem, not just a technical debt item.
ServiceNow’s Control Plane Play
NVIDIA is part of that architecture, ServiceNow’s partnership brings hardware-level enforcement via NVIDIA’s BlueField data processing units, pushing policy decisions down to the silicon layer.
The strategic ambition is to make the Control Tower the mandatory checkpoint for agent actions across Salesforce Agentforce and Microsoft Copilot, two platforms with substantial enterprise install bases. ServiceNow has been building toward tighter agent controls for some time, the Control Tower expansion formalises that direction as a cross-vendor governance product rather than a platform-specific feature.
Formalizing Access and Data Flows
Agent-specific identities are the foundation. With per-agent credentials, the Control Tower can enforce scoped data access and predefined operational boundaries, something shared credentials make impossible to audit after the fact. Policy definitions centralised in the Tower apply regardless of whether an agent originates from Salesforce, NetSuite or a custom build: data masking, redaction rules, approved routing channels for sensitive information. The goal is a complete record of every agent interaction, from model calls to API executions, that holds up under regulatory scrutiny.
This matters most in environments where cascading agent failures can propagate quickly across connected systems. Formalising the access layer is what makes incident response tractable, without attributed actions, diagnosing what an agent did and why is largely guesswork.
Containing Shadow AI
Shadow AI is the predictable outcome of agent proliferation without governance: undocumented agents operating outside sanctioned infrastructure, invisible to compliance and security teams. The Control Tower’s cross-platform mandate is designed to pull those agents into a monitored perimeter. If a Salesforce Agentforce agent attempts an action that violates a corporate policy, the Tower can intercept before execution, log the attempt and fire an alert. That proactive enforcement matters most in regulated industries where human oversight of high-risk AI actions is a legal requirement, not a preference.
Automated evidence collection and continuous monitoring reduce the manual compliance work that otherwise falls on overstretched governance teams, the same teams that have been scrambling to build oversight frameworks as agent counts scale faster than headcount.
Where the Gaps Remain
Microsoft, Salesforce, Google and Oracle are all building application-native governance layers.
The data compatibility layer underneath all of this, schema mismatches, format inconsistencies between systems, still requires dedicated integration infrastructure before agents can operate reliably. The Control Tower addresses the governance layer; it does not dissolve the integration problem beneath it.


