Interactive Demos

Attack Scenarios & Defenses

Watch Kavros enforce policy, DLP, and cryptographic proof across all three AI surfaces — hijacked agents, leaking chats, and drifting workflows — in real time.

AI agents — hijacked actions

An agent reads a poisoned feed and tries to upload the customer dataset. The prompt-direction rule matches, the request is refused before model routing, and the workload is quarantined automatically — no "suspected" hand-wave, the trigger and the evidence are both on screen.

kavros-agent · governed egress

Halt semantics without the guesswork: the flag is a deterministic prompt-direction rule match, the quarantine is automatic, and every decision lands in the audit band.

The kill switch

A governed agent misbehaves. The operator halts it with a reason on the record — every request is then refused outside the agent, quoting that reason, until an admin resumes it. Watch the full halt → evidence → resume loop.

Control: halt / resume

The attack playbook

Attack classes against autonomous agents — and the control that stops each one:

  • treasury drain — a tricked agent transfers $100,000 in ETH to an attacker wallet. Stopped by: signed allowlist — unapproved target.
  • PII exfiltration — an agent dumps customer SSNs to an external API. Stopped by: DLP pattern before egress.
  • runaway compute — a manipulated bot spins up 10,000 instances. Stopped by: policy limits.
▸ Run the live injection block demo on the homepage

Employee AI chat — well-meant leakage

Nobody's malicious: an employee pastes a customer record into a prompt to get a reply drafted faster. DLP scans the prompt before it leaves — run it, or watch the real product beside it.

kavros-chat · governed employee AI

The rule name, the match, and the refusal appear on screen — then the redacted re-run sails through the same TEE.

DLP in production

A card number and an AWS key, blocked before the model ever sees them — with the rule that matched on the record.

Control: DLP before egress

AI workflows — silent drift

A nightly workflow runs unattended. What happens when a capability it depends on changes after approval — or its source schema moves without re-approval? Run the drift scenario, or watch a real governed run — database to summarized report — beside it.

kavros-scheduler · nightly-revenue-report

The signed revision pins the run; when the source drifts without re-approval, the tool is suspended and the incident opens by itself.

A governed run, end to end

From your database to a summarized Excel — the summary, model, and prompt travel with the file, and every step is signed.

Control: signed revision

Want to test Kavros against your own traffic?

Run the 15-business-day paid proof in your own VPC: a fixed $7,500 Business-tier pilot against your specific attack vectors — credited in full if you sign an annual contract within 30 days.

Apply to the Program