Connector · ServiceNow
A governance event becomes a ticket.
Planned · no date set
Risk and operations teams work in ServiceNow, and an event that does not become a record there does not get worked. The planned connector maps your agent inventory from the CMDB, writes governance events and receipts into GRC audit records, and links them to ITSM tickets. A refused utterance or a blocked dial then has somewhere to go besides a dashboard.
What the connector writes
{
"table": "sn_grc_audit_record",
"source": "audact",
"ci_ref": "cmdb_ci:audact_agent_dental_intake_v2",
"event": "governance_gate_blocked",
"policy": "commercial_commitment",
"severity": "hard",
"receipt_id": "rcpt_gov_01HX7...",
"incident": { "create": true, "assignment_group": "AI Risk" }
}Worked example. Acme GmbH and Nova Industries are fictional; no customer data appears here.
The incident block is optional and per event type. Not every refusal deserves a ticket; the ones that do should not depend on someone watching a screen.
What the connector will carry
- Agent inventory mapped from the ServiceNow CMDB.
- Planned
- Governance events and receipts into GRC audit records.
- Planned
- ITSM ticket creation per event type, with an assignment group.
- Planned
- The governance itself (disclosure, gate, eligibility) does not depend on the connector; it is In controlled testing (Germany: national policy layer active. Netherlands: in development. Belgium and Austria: planned.).
- In controlled testing
Who it is for
Where the workflow is the control.
In a large organisation, a control that is not a workflow is a suggestion. ServiceNow is where the workflow lives, and an AI deployment whose exceptions land somewhere else quietly opts out of the control environment the rest of the company runs on.
That is the whole argument for this connector. It does not add governance; it puts the governance where the organisation already assigns, escalates and closes.
Setup
Five steps, once the connector ships.
- Connect Audact to ServiceNow with an API token.
- Map your CMDB configuration items to the Audact agent inventory.
- Configure the per-jurisdiction policy packs in the Audact policy engine.
- Enable evidence export into GRC audit records.
- Switch to live. Events flow into the workflows as they happen.
Questions
- Is this in the ServiceNow Store?
- Not yet. A listing is planned and this page will say when it exists.
- Does every governance event create a ticket?
- Only the types you choose. The rest land as audit records, which is where most of them belong — a ticket for every refusal trains people to close tickets without reading them.
The same primitives, without the connector
A connector is a shorter path into one platform. Underneath it are six endpoints that run inside the managed platform, and an evidence chain that is identical either way.
Related
All connectors OneTrust The same events, in privacy.
Observability Layer The same stream, natively.
The API Six endpoints, inside the managed platform.
