Security against AI
Malicious AI agents scan, chain and exploit weaknesses faster than any human team can react. Opservant shrinks the window they have by fixing open ports, weak configurations and missing patches in minutes, not days.
Don't hold AI back: make it safe to act. Opservant closes the gap between detecting a threat and fixing it. AI selects among human-approved playbooks, and Spark, a simple client, runs only the approved operations on its own host.
Watch Opservant detect a vulnerability, analyze it with AI and deploy the fix, all in under a minute.
Malicious AI agents can move from reconnaissance to impact in minutes. Most organizations still detect in hours and respond in days. Every minute between MTTD and MTTR is time an attacker gets for free.
Illustrative comparison, not measured data. Measuring it for real is part of our research.
AI changes security twice: attackers get AI agents, and defenders start letting AI decide what happens on their own systems. Opservant is built for both.
Malicious AI agents scan, chain and exploit weaknesses faster than any human team can react. Opservant shrinks the window they have by fixing open ports, weak configurations and missing patches in minutes, not days.
When AI decides what runs on your machines, the AI becomes a target too: prompt injection, poisoned inputs, hijacked decisions. In Opservant the AI never touches your machines directly. It can only select among human-approved playbooks and cannot change commands, content or policy. A manipulated selection is limited to what people already approved, and approvals, the client and rollback each narrow it further.
The question isn't whether AI will run your security, it's whether it can do it safely. Opservant is the control layer that lets AI detect, decide and fix security issues across your infrastructure, while humans stay in control of every action that matters.
Continuously scans your assets for security issues: open ports, weak configurations, missing patches and more.
AI analyzes the situation, selects the right fix from human-approved playbooks. Actions marked for approval wait for a person first.
Executes the approved fix directly on the affected machine, closing vulnerabilities and hardening your systems in seconds instead of days.
People approve playbooks. AI selects among them. Spark, a simple client on your machine, runs only the approved operations, and only on its own host. The AI cannot change commands, playbook content or the approval policy.
AI selects only from playbooks people have reviewed and approved. It cannot write commands or change a playbook.
Actions you mark for approval wait for a yes on the machine itself. No answer means no.
Every action is logged. When a task fails, playbooks with a rollback revert their completed steps automatically.
Spark's playbook model is inspired by OASIS CACAO (Collaborative Automated Course of Action Operations), the open standard for describing, sharing and executing cybersecurity playbooks in a machine-readable format. AI selects among human-approved playbooks, and Spark runs each one on its own host through the steps below.
Here's what happens behind the scenes when Opservant protects your infrastructure.
One file, no dependencies. Runs as a background service and survives reboots.
Pick playbooks from the library and choose which ones need human approval.
Runs checks, closes vulnerabilities and reports every result back.
AI analyzes the results and selects the next approved playbook. 24/7, within your rules.
Every Opservant run produces something rare: a record of what AI selected on real infrastructure, what a human approved or rejected, and what happened next. We are building a shared, open database from these records for the AI control and security community.
A public, anonymized database of AI selections on real systems: which approved playbook, for which target, on what evidence, and the decision and outcome. Open to researchers, CERTs and the community.
Open benchmarks that measure how fast threats are detected and contained with AI in the loop, and without it.
A practical framework for which security actions AI may take alone, which need a human and which must always be reversible.
Work in progress. Data is shared only with consent, anonymized, and with tiered access for sensitive attack data.
A client with this much access must stay safe even when something goes wrong.
Spark checks in with the platform regularly, so you never open inbound ports on your machines.
Every action, every result, every heartbeat is stored for full visibility and later review.
All data between Spark and the platform is encrypted with TLS 1.3+.
A single, lightweight Go binary. No runtime dependencies. Installs in seconds and scales from 5 assets to 5,000.