Boardwalk Verity Integration extends ServiceNow compliance workflows with automated control testing powered by Verity’s agentic AI.
The integration securely retrieves selected compliance policy statements from ServiceNow and applies configured Verity test procedures. When a test identifies a control failure, the integration can create a ServiceNow incident for investigation and remediation, connecting automated testing to the workflows customers already use.
Guided Verity Setup helps ServiceNow administrators provision a Verity tenant, configure secure bidirectional connectivity, and validate the connection.
Bring AI-powered controls automation and testing execution into your ServiceNow workflows.
- Guided ServiceNow onboarding and provisioning for a dedicated Boardwalk Verity tenant.
- Secure bidirectional integration between ServiceNow and Boardwalk Verity.
- Retrieves ServiceNow control objectives and entity scope for Verity processing and testing.
- Creates ServiceNow Issues when applicable Verity tests fail.
- OAuth 2.0 Client Credentials authentication for Verity-to-ServiceNow calls, with authentication for ServiceNow-to-Verity calls configurable to match customer requirements.
- Guided connection-readiness validation through Verity Setup.
Verity features:
- AI Agents automate control execution, testing and monitoring
- AI agents test both control design and operating effectiveness across the full control population, calibrated by risk rather than periodic sampling
- Automatically collects, tags, and structures evidence for every test, audit-ready without manual assembly.
- Test results and control status populate ServiceNow's native IRM workspace, so users stay in a single system of record.
Boardwalk Verity Integration 1.3.7 – certification remediation release
- Removed the packaged OAuth client and client secret. The Verity Integration Client is configured locally on each customer instance.
- Added HTTPS and domain allowlisting for outbound Verity destinations.
- Added admin-only write ACLs for sensitive configuration fields.
- Removed sn_compliance.reader containment from the application role; it is assigned directly to the dedicated OAuth integration user during customer configuration.
- Removed the orphaned VerityProvisioningAjax ACL.
- Preserved instance-local OAuth configuration across application upgrades.
- Updated certification documentation and validation for version 1.3.7.
ServiceNow Australia release.
GRC: Policy and Compliance Management (sn_compliance) is required.
A ServiceNow administrator must complete Verity Setup after installation. Internet connectivity to Boardwalk Verity services is required.
Verity-to-ServiceNow authentication uses OAuth 2.0 Client Credentials. The customer administrator creates the Verity Integration Client and associated customer-specific OAuth configuration during setup; OAuth client credentials are not included with the application.
ServiceNow inbound OAuth Client Credentials support must be enabled on the customer instance in accordance with the customer’s platform security policy. Boardwalk Verity Integration does not create or modify this instance-wide setting.
Customer-specific Verity connection configuration and authentication tokens are established during setup and are not included with the application.