Integrations · Your tools

AI events in the SIEM your team already watches.

Refused and blocked calls, changes, sign-ins and models going out of service, sent as they happen. In order, signed, and never containing what a call said.

Vidai Control room · Settings
Event destinations: a security webhook and a Splunk collector, each with its state.
Event destinations: a security webhook and a Splunk collector, each with its state.

Where events go

Wherever your security team already looks.

Splunk

Straight to Splunk's HTTP Event Collector.

Microsoft Sentinel, Elastic, CrowdStrike Falcon Next-Gen SIEM

Through their HTTP intake, from a signed webhook.

Your own systems

A signed webhook to chat and paging tools such as Slack, Teams or PagerDuty, or anything of your own.

What arrives

Choose every event, or only some.

Topics

  • Calls refused or blocked
  • Models out of service
  • Keys and tokens; people, teams and sign-in
  • Budgets, cost and prices; rules and compliance
  • Tamper evidence

Signed, in order, caught up

  • Each post carries a timestamp and an HMAC-SHA256 signature you check in a few lines
  • Names and ids, never secrets and never what a call said
  • If your side doesn't answer, Vidai keeps the events and catches up in order

Defence in depth

Alongside your endpoint and web security.

Endpoint and web security tools, such as CrowdStrike or Zscaler, watch devices, browsers and the AI apps people use. Vidai checks every AI call where it goes to a model, including server-side apps and agents that never touch a laptop. Each layer checks a different place, and their alerts land side by side in your SIEM.

Devices and browsers

Your endpoint and web security tools watch laptops, browsers and SaaS apps, and the AI used inside them.

Every AI call

Vidai checks each call at the point it goes to a model, and blocks injection and sensitive data before the model sees them.

Event webhooks come with Enterprise. Product names are trademarks of their owners, given as examples; no endorsement or certification is implied.

Setup steps for every SDK, provider and integration are in the docs.

Related

How we start together

Start with one team, on your own AI traffic.

After a 20-minute demo, we agree a two-week pilot with you: one app or team, your traffic, your infrastructure.
  1. 01

    Pick one app or team

    Point it at the Control room. One configuration change; nothing else changes.

  2. 02

    Watch for two weeks

    Every call priced, checked and recorded. Rules start in observe mode.

  3. 03

    See the evidence

    What it cost, what it caught and what it would have stopped, from your own traffic.