Polyguard brings high-assurance identity verification into the Incident form. When a caller asks for a password reset, account recovery, or any other sensitive action, a service desk agent can launch a secure trust check in one click, the end user verifies on their phone in seconds, and the result, including a verified name and signed proof, lands back on the same Incident automatically. Stop social-engineering attacks at the service desk without slowing your agents down.
- Verify identity without leaving the Incident. One click on Create Trust Check Link starts a secure check directly from the record the agent is already working in.
- Mobile-first for end users. The customer receives a link, completes verification on their phone in seconds, and never installs or learns anything inside ServiceNow.
- Results land where the work happens. Verified name, identifier, and proof of verification are written to the incident's Trust Check automatically, so the agent's next decision is informed in real time.
- Built for service desks. A dedicated agent role lets you choose exactly who can request trust checks, while a separate integration role keeps the Polyguard backend tightly scoped.
Welcome to the first release of Polyguard for ServiceNow. Polyguard brings high-assurance identity verification into the place your agents already live: the Incident form. When a caller asks for a password reset, account recovery, or any other sensitive action, an agent can launch a trust check with one click and confirm the person is who they say they are before acting.
What you get in this release:
- A Create Trust Check Link button on the Incident form, so authorized agents can launch identity verification in one click.
- Automatic results on the incident's Trust Check the moment the user finishes verifying on their phone.
- Role-based access so only the people you choose can initiate verifications.
- A quick Polyguard Console-driven setup, no shared keys or manual credential copying required.
Questions or feedback? Reach us at support@polyguard.ai.
- ServiceNow instance running Yokohama or Zurich.
- Administrator (admin role) access on the target ServiceNow instance to install the app, create the integration user, and create the inbound OAuth client (Application Registry on Yokohama, Inbound Integrations on Zurich).
- The Incident plugin must be active. The application does not add fields to the Incident table; it adds its own tables and references Incident.
- The ServiceNow instance must accept inbound HTTPS connections from the Polyguard backend so verification results can reach the application's Scripted REST APIs (this is the default for standard ServiceNow instances).
- A modern browser (Chrome, Edge, Safari, or Firefox in a recent version) for the agent UI.
Other Requirements:- An active Polyguard Enterprise account with access to the Polyguard Console at https://console.polyguard.ai. The Console is used to register the ServiceNow instance and push credentials into the application's private configuration table.
- End users completing a trust check need an internet-connected mobile device. No mobile app installation in ServiceNow is required.
- The administrator performing the install should be able to create a Web Services Only user and an OAuth API endpoint for external clients (both standard ServiceNow capabilities, no separate plugin required).