Mastering the AI Control Tower NOW book cover
Part of the ServiceNow Success series

Mastering the AI Control Tower NOW

A Practitioner's Guide to AI Strategy, Governance, and Security in ServiceNow
Aligned to the ServiceNow Australia release

Turn enterprise AI governance into records, workflows, and drilled runbooks. From the AI asset inventory and lifecycle gates to risk, compliance, security monitoring, and the kill switch, this is the field manual for discovering, governing, securing, observing, and measuring every AI asset your organization runs. Thirteen hands-on labs, seventeen architecture diagrams, and three deployment blueprints.

BY MICHAEL J. MURPHY  |  PRINCIPAL TECHNICAL ARCHITECT
What You Will Learn

From scattered AI to a governed estate

Thirteen chapters and seven appendices, each built around working configuration, real JavaScript and Flow Designer code, REST integrations, and the failure modes that quietly break real programs.

Map the whole AI estate

Build the AI asset inventory with automated discovery across ServiceNow, AWS, Azure, Google Cloud, and your vendors, so governance starts from an honest answer to "what AI do we run?"

Govern the lifecycle

Take every asset from Proposed to Retired with classification at intake, hard approval gates, change control that catches risky modifications, and offboarding that produces evidence.

Make compliance an export

Translate NIST AI RMF and the EU AI Act into controls, versioned assessments, and attestations, with an evidence machine that makes audit season a download instead of a scramble.

Master the AI ecosystem

Deep technical coverage of Now Assist, ServiceNow Otto, Virtual Agent, AI Agents, and the Autonomous Workforce, from skill anatomy to agent instructions and supervision points.

Secure and contain

Defense in depth against prompt injection, goal deviation, and data exfiltration, plus the kill switch protocol treated as a drilled, timed capability rather than a checkbox.

Deploy with a blueprint

Three reference blueprints matched to your organization's situation, a phased roadmap with evidence-based exit criteria, and the five metrics that keep the program honest.

Inside the Book

Seventeen architecture diagrams you can rebuild

Every major concept is drawn as a fully styled diagram, with the complete Mermaid source printed in the book so you can regenerate and extend each one in your own documentation.

The ServiceNow AI Ecosystem diagram
The ServiceNow AI Ecosystem. Otto, Now Assist, AI Agents, and Action Fabric organized into experience, execution, and governance planes.
AI Asset Lifecycle State Machine diagram
The AI Asset Lifecycle. Proposed to Retired, with the gates and reclassification edges that make states mean something.
AI Control Tower Logical Architecture diagram
AI Control Tower Architecture. Connectors feed the inventory, five engines act on it, and the kill switch reaches back into the estate.
Free Sample

From Chapter 1: The ServiceNow AI Ecosystem in the Australia Release

Every large organization now runs more AI than it can name. Copilots arrive embedded in productivity suites. Data science teams deploy models on hyperscaler platforms. Business units subscribe to SaaS products that quietly added generative features. Each of these is individually defensible. Collectively, they form an unmanaged estate with real regulatory, security, and financial exposure, and until recently nobody owned the map.

The ServiceNow Australia release is the point at which the platform's answer to this problem stopped being a collection of features and became an operating model. AI Control Tower, introduced in earlier releases as a governance workspace, matured in Australia into a command plane organized around five verbs: discover, govern, secure, observe, and measure. The same release rebranded the platform's assistive AI under a single identity, ServiceNow Otto, expanded the AI Agent ecosystem with hardened controls such as runaway trigger detection and a kill switch protocol, and shipped regulatory content packs that map platform controls to the NIST AI Risk Management Framework and the EU Artificial Intelligence Act.

For practitioners, the consequence is simple: the skills that mattered in the earlier era, prompt configuration and skill activation, are now table stakes. The differentiating skill in the Australia era is governance engineering: the ability to model an AI estate as data, wire lifecycle and risk workflows around it, and prove compliance to an auditor without a spreadsheet scramble.

Three Planes and a Foundation

The ServiceNow AI ecosystem in the Australia release is best understood as three planes plus a foundation, and holding this map in your head makes every later chapter easier:

  1. The experience plane is where humans meet AI. Its flagship is ServiceNow Otto, the unified AI experience that consolidates Now Assist panels, Virtual Agent conversations, AI Search, and the conversational intelligence acquired with Moveworks. Otto understands intent, routes work to the appropriate agent or workflow, and carries tasks to completion rather than merely answering questions.
  2. The execution plane is where AI does work: the Now Assist skill families that generate, summarize, and resolve inside applications; the AI Agents built in AI Agent Studio; the packaged AI Specialists of the Autonomous Workforce; and Action Fabric, which lets external agents execute governed ServiceNow workflows over the Model Context Protocol.
  3. The governance plane is AI Control Tower. It discovers AI assets wherever they run, maintains the AI asset inventory and its lifecycle, runs risk and compliance management against regulatory frameworks, monitors security posture and agent behavior at runtime, and measures whether the estate is worth what it costs.
  4. The platform foundation sits beneath all three: the workflow data fabric, CMDB and Service Graph, Flow Designer, the Generative AI Controller that brokers every model call, and the RaptorDB performance engine that accelerates the query patterns these AI workloads generate.

The critical architectural insight is that the governance plane does not sit in the request path as a proxy. It observes and constrains the execution plane through policy, telemetry, and enforcement hooks, which means governance can be adopted incrementally without re-architecting every AI workload. That design decision is why AI Control Tower can plausibly govern AI that does not run on ServiceNow at all.

The full chapter continues with runtime flow diagrams, licensing and entitlement realities under the 365-day burn-down model, a hands-on lab that assesses your own instance's AI readiness, and the failure modes that quietly undermine first-year programs.

Table of Contents

Thirteen chapters, thirteen labs, one governed estate

The ServiceNow Success Series

More from Michael J. Murphy

Practical, framework-driven guides for people who build on the ServiceNow platform.

About the Author

Michael J. Murphy

Michael J. Murphy

Michael J. Murphy is a Principal Platform Technical Architect with more than 30 years of experience across enterprise IT, and deep ServiceNow expertise spanning ITSM, CMDB, integrations, governance, and compliance. Michael has been delivering solutions for Fortune 500 organizations, the Pentagon, NASA, the Department of Defense (DoD), and other high-growth technology companies. He is currently the author of the ServiceNow Success series and writes for practitioners who want to avoid where organizations consistently fail.

His work focuses on helping organizations navigate complex technical environments, align technology with business outcomes, and build highly scalable, secure platforms. As an entrepreneur and venture capitalist, he brings a business owner’s perspective to this collection of books, helping close the gaps between technical decisions and business outcomes.

Visit ServiceNow Success