AI-driven SOAR and threat response agents can act faster than any human — but an unchecked agent blocking the wrong endpoint or wiping the wrong host is a bigger incident than the one it was trying to stop. Kynara enforces analyst approval before any containment or remediation action.
// Allow enrichment + investigation freely
{ "display_name": "Allow threat intel reads",
"effect": "allow", "priority": 100,
"actions": ["siem.query", "edr.read", "threat_intel.lookup"],
"condition": {} }
// Require analyst approval for containment
{ "display_name": "Require approval for containment",
"effect": "require_approval", "priority": 200,
"actions": ["endpoint.isolate", "ip.block", "credentials.revoke"],
"condition": {} }
// Deny remediation without MFA + high confidence
{ "display_name": "Deny low-confidence remediation",
"effect": "deny", "priority": 50,
"actions": ["host.wipe", "service.terminate", "data.delete"],
"condition": {
"op": "or",
"args": [
{ "op": "lt", "args": ["ctx.resource.attrs.threat_confidence", 0.9] },
{ "op": "eq", "args": ["ctx.context.mfa_verified", false] }
]
}}
Every Kynara decision event — allow, deny, require_approval, and approval resolutions — streams into your SIEM via the polling cursor API. Analysts get a complete picture of AI agent activity alongside human activity in the same platform.
| SIEM | Setup | Kynara events |
|---|---|---|
| Splunk | Kynara Add-on with polling cursor | All events |
| Microsoft Sentinel | Data connector; built-in rules for agent.killed and audit.chain_broken | All events |
| Datadog | Log pipeline from cursor endpoint | All events |
| Elastic / ECS | Filebeat module with ECS field mapping | All events |
| PagerDuty | Webhook on agent.killed + anomaly.deny_rate_spike | Critical events |
Free plan to get started. Enterprise plans include custom SIEM connectors, dedicated deployment, and SLA.