Platform

AI governance integrations for the systems you already run

Aicura's integrations find AI through the identity, device, cloud and code systems that already know about it, sync with data catalogues and GRC platforms, send signed events to your SIEM and ticketing tools, and enforce your rules through a gateway in your own network. When a team signs in to a new AI tool with their work account, it can show up in your next discovery scan.

Included in Pro and Enterprise. Discovery connectors start on the free Register plan. Compare plans

Discovery

Find AI through the systems that already know about it

Discovery reads these sources when you run a scan and surfaces AI tools in use that are not on the register. Nothing is registered on its own. Discovery proposes and a person decides.

ServiceNow CMDBRegister
OktaRegister
Microsoft Entra IDRegister
Google WorkspaceRegister
AWS ConfigRegister
Azure Resource GraphRegister
GCP Asset InventoryRegister
FreshserviceRegister
SlackRegister
Chrome EnterpriseRegister
Microsoft IntuneRegister
Jamf ProRegister
Fleet (osquery)Register
GitHubRegister
Generic connectorRegister
XeroEnterprise
QuickBooks OnlineEnterprise
MYOBEnterprise
AI WizardEnterprise

GitHub reads repository and app metadata only, never source code. AWS Config is keyless, through a read-only role gated by an ExternalId.

Data and GRC

Data catalogues and GRC platforms

Data platforms bring their datasets, classifications, owners and lineage into Aicura's record of where your AI's data comes from. GRC platforms take the risks, controls and actions your assessments produce.

Data catalogue, lineage and privacy platforms

Each sync brings in the platform's facts first, then evaluates findings. The platform owns definitional facts. Your governance fields are owned in Aicura and a sync never overwrites them.

  • Microsoft Purview Pro
  • Databricks Unity Catalog Pro
  • Unity Catalog (open source) Pro
  • Snowflake Horizon Pro
  • Atlan Pro
  • Alation Pro
  • Collibra Pro
  • BigID Pro
  • Generic connector Pro

AWS DataZone, Google Dataplex, Informatica and Varonis are coming soon.

Keep risks and controls in step with your GRC platform

When GRC Connect is on, your GRC platform operates the risk, control and action records, and Risks and Controls shows a mirrored badge. Map each platform before its first run, covering where the records live, which fields cross and what the values become. Every run shows on the Sync tab, and comments made in the GRC platform appear on the risk.

  • ServiceNow GRC
  • ReadiNow
  • Generic connector

GRC Connect from Pro.

Generic connector

Connect a platform Aicura has no connector for

The Generic connector reaches any platform you can put an endpoint in front of. You or your partner build the endpoint to Aicura's published connector contract, then save its address and a bearer token in Settings.

Aicura then calls your endpoint exactly as it calls a built-in connector. A discovery scan reads it for AI in use, a data provenance sync lands its assets and lineage, and a GRC sync writes risks, controls and actions to it. The same contract covers all three, and everything it returns goes through the same decisions, findings and mappings as any other source.

It is part of discovery from the Register plan, data provenance from Pro and GRC Connect from Pro.

Events

Send events to the tools your teams already watch

Aicura sends signed notices of what happens, such as a blocked request or a new guardrail deployment, to the SIEM, ticketing and prudential reporting tools your security, operations and risk teams already watch.

Proof each event came from Aicura, and a log of every delivery

Each subscription names its target, endpoint and event types, such as an enforcement event recorded or a guardrail deployment created. It gets a signing secret shown once at creation, so the receiver can check every delivery came from Aicura.

The delivery log records every attempt to every subscription. Open a row to inspect the signed envelope and the outcome of each attempt.

Webhooks
From Pro
SIEM export
From Pro
Ticketing and messaging
From Pro
Prudential process feeds
From Pro

Runtime

The parts that run inside your own network

A hub, AI gateways, usage collectors and engines for security testing, drift checks and checks before release run in your environment and connect it to Aicura. Your AI traffic never passes through Aicura.

Gateways and checks before release

Use the Aicura gateway, or a gateway you already run that pulls exported, signed bundles. A pipeline can ask a preflight engine before a release goes ahead.

Aicura AI gateway
From Pro
Bring your own gateway
From Pro
Preflight decision point
From Pro

Content scanners your rules can call

Guardrail rules call scanners that your gateways advertise. Bedrock Guardrails calls a guardrail in your own AWS account, and Granite Guardian calls a host you run that serves IBM's model. Your own scanner scripts sit beside them.

PII detection
From Pro
LLM Guard
From Pro
Local classifier serving
From Pro
Bring your own scanner
From Pro
Presidio
From Pro
Bedrock Guardrails
From Pro
Granite Guardian
From Pro

Questions

Which systems can Aicura discover AI in?

Discovery connectors cover device telemetry, identity providers, collaboration tools, endpoint management, cloud accounts, configuration management databases and code hosting, with finance systems on Enterprise. A connector is read when you run a scan, and every item it finds waits on a person's decision.

How are connector credentials held?

Integration credentials are write-only. They are kept in the platform secret store and never shown back, so changing one means replacing it. AWS Config is keyless, through a read-only role gated by an ExternalId, and the GitHub App is installed by your organisation's owner and can be revoked from GitHub.

Can we use our own AI gateway?

Yes. A gateway you run yourself pulls Aicura's signed guardrail bundles, exported per version. It is not a deploy target, so publishing and exporting are the steps you control. The Aicura gateway takes deployments directly and reports each enforcement event back.

How do events reach our SIEM or ticketing system?

Through webhooks. You subscribe an endpoint to the event types you want, and Aicura delivers signed lifecycle events to it. Each subscription gets a signing secret shown once, and a delivery log records every attempt with its signed envelope and outcome.

Which GRC platforms does Aicura sync with?

ServiceNow GRC and ReadiNow, and any other GRC platform through the Generic connector. A sync mirrors your published risks, controls and actions to the GRC platform after you map where the records live and which fields cross.

Fit Aicura into the stack you have

Most integrations are part of Pro. Contact us about the systems your AI governance needs to reach.