Home›Agents›ServiceNow Otto

AgentenCode evidence profileEnterprise

✓ Editorially reviewedChecked: October 7, 2026

Agent profile · Enterprise

ServiceNow Otto

ServiceNow Otto is classified by AgentenCode as an enterprise ai experience / agent from ServiceNow. It belongs to the Enterprise category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

Source update (2026-10-08): Source maintenance: The previous Otto release-notes URL is unavailable. The official Now Assist Suite release notes now serve as the reference. Autonomous Engineer belongs to AI Workflow Factory and requires the appropriate entitlement; it is not automatically available in every Otto plan. Official primary source ↗

ServiceNowEnterpriseOrganizations

View profile ↓Check sources ↓

Enterpriseeditorial classification

ServiceNowprovider

13 primary sourcessource status

October 7, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for ServiceNow Otto

Direct answer: AgentenCode currently documents 10 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.

EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.

GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.

Privacy contextPrivacy & data0 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access7 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.

Human controlHuman control0 of 10 documentedApproval, oversight, permissions and stop or rollback controls.

TraceabilityAudit & traceability3 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.

Field-level evidence

Documented controls and values from primary sources.

Documented yesDocumented valueUnknown remains unknown

High confidence

Deployment · License Requirement

ServiceNow Otto Pro Plus or Enterprise entitlement

Otto AI agent setup requires the documented Pro Plus or Enterprise entitlement.

Scope: servicenow_otto_ai_agents · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · API

Yes — documented

Otto actions are logged, and ServiceNow platform log/audit tables can be accessed through web services for export.

Scope: servicenow_instance_logs_including_otto_actions · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · Available

Yes — documented

ServiceNow explicitly documents action logging and governance for Otto.

Scope: servicenow_otto_actions · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · SIEM export

Yes — documented

ServiceNow platform logs that include governed Otto activity can be exported to external SIEM/logging systems.

Scope: servicenow_instance_logs_including_otto_actions · verified 2026-10-01 · Primary source ↗

High confidence

Governance · RBAC

Yes — documented

ServiceNow Otto AI agents use role-based administration and viewing permissions.

Scope: servicenow_otto_ai_agents · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Roles · Admin

sn_aia.admin

The documented AI Agent administrator role is sn_aia.admin.

Scope: servicenow_otto_ai_agents · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Roles · Viewer

sn_aia.viewer

The documented read-only AI Agent viewer role is sn_aia.viewer.

Scope: servicenow_otto_ai_agents · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SSO · Oidc

Yes — documented

Users accessing Otto through the ServiceNow AI Platform can use the platform's documented OIDC SSO.

Scope: servicenow_ai_platform_users_accessing_otto · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SSO · Saml

Yes — documented

Users accessing Otto through the ServiceNow AI Platform can use the platform's documented SAML 2.0 SSO.

Scope: servicenow_ai_platform_users_accessing_otto · verified 2026-10-01 · Primary source ↗

High confidence

Security · Customer-managed keys

Yes — documented

Where the relevant ServiceNow encryption option is licensed, platform data used by Otto can be protected with customer-managed/BYOK keys.

Scope: servicenow_platform_data_accessed_by_otto_where_cloud_encryption_is_licensed · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · At rest

ServiceNow Field Encryption for protected instance fields

Sensitive ServiceNow instance fields accessible to Otto/AI agents can be protected at rest with Field Encryption.

Scope: sensitive_instance_fields_accessed_by_otto_and_ai_agents · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · In transit

TLS 1.2

ServiceNow documents TLS 1.2 transport protection for the AI workload path used by Otto/Now Assist capabilities.

Scope: servicenow_otto_now_assist_ai_workloads · verified 2026-10-01 · Primary source ↗

High confidence

Security · Soc2 Type2

Yes — documented

Otto AI workloads run on ServiceNow's attested AI environment, which ServiceNow documents as SOC 2 Type 2.

Scope: servicenow_ai_environment_including_otto_ai_workloads · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is ServiceNow Otto?

Product-specific evidence for ServiceNow Otto

This profile links 13 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.

Customer-Managed Keys

Yes · Scope: servicenow_platform_data_accessed_by_otto_where_cloud_encryption_is_licensed · verified 2026-10-01.

Primary source ↗

Verschlüsselung at rest

ServiceNow Field Encryption for protected instance fields · Scope: sensitive_instance_fields_accessed_by_otto_and_ai_agents · verified 2026-10-01.

Primary source ↗

Verschlüsselung in transit

TLS 1.2 · Scope: servicenow_otto_now_assist_ai_workloads · verified 2026-10-01.

Primary source ↗

SOC 2 Type 2

Yes · Scope: servicenow_ai_environment_including_otto_ai_workloads · verified 2026-10-01.

Primary source ↗

Audit Log API

Yes · Scope: servicenow_instance_logs_including_otto_actions · verified 2026-10-01.

Primary source ↗

Audit Logs

Yes · Scope: servicenow_otto_actions · verified 2026-10-01.

Primary source ↗

AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.

13primary source

13field-level evidence claims

10documented trust controls

4history events

How to read the evidence

The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.

AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.

Decision context

Provider and category

ServiceNow Otto is documented under Enterprise and is associated with ServiceNow. Category labels help navigation but do not replace product-specific evidence.

Verification status

The public profile is marked editorially reviewed and was last checked on October 7, 2026.

Trust coverage

10 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.

Source-first use

For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.

Capabilities, strengths and deployment checks for ServiceNow Otto

ServiceNow Otto is classified as Enterprise AI Experience / Agent from ServiceNow. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.

Mitarbeiterassistenz

This use case is part of the stored profile for ServiceNow Otto. The related strength is “Einheitliche Oberfläche”. In a production evaluation, the practical boundary to verify is: Verfügbare Aktionen je Rolle prüfen.

Serviceprozesse

This use case is part of the stored profile for ServiceNow Otto. The related strength is “ServiceNow-Prozessnähe”. In a production evaluation, the practical boundary to verify is: Datenzugriffe und Identität sauber konfigurieren.

Workflow-Orchestrierung

This use case is part of the stored profile for ServiceNow Otto. The related strength is “Routing über Systeme und Agenten”. In a production evaluation, the practical boundary to verify is: Autonome Prozessschritte testen.

Unternehmenssuche

This use case is part of the stored profile for ServiceNow Otto. The related strength is “Für End-to-End-Aufgaben gedacht”. In a production evaluation, the practical boundary to verify is: Verfügbare Aktionen je Rolle prüfen.

What to verify before adoption

Verfügbare Aktionen je Rolle prüfen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Datenzugriffe und Identität sauber konfigurieren. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Autonome Prozessschritte testen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.

Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

Verified history

The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.

October 7, 2026 · Product change · ServiceNow documents Autonomous Engineer as a Build Agent-powered worker for plan-based parallel implementation and automated testing within AI Workflow Factory.
October 1, 2026 · Source Maintenance
September 30, 2026 · Verification Update
September 28, 2026 · Schema Upgrade

Official sources

Frequently asked questions

What is ServiceNow Otto?

ServiceNow Otto is listed by AgentenCode as an enterprise agent or agentic product from ServiceNow.

How much trust evidence is documented for ServiceNow Otto?

The current trust layer documents 10 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.

When was this profile last checked?

The current profile verification date is October 7, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.