AiSOC
AiSOC is an open-source, self-hostable security operations center. Per the README, it ingests security telemetry, normalises it, runs detection rules, groups what fires into incidents, has an AI agent investigate each one with every prompt and tool call recorded in an Investigation Ledger, and proposes a response that a human approves before anything executes. Data comes in through an ingest API or from 84 click-and-connect connectors, with vendor-specific handling for Splunk, Microsoft Sentinel, Elastic, CrowdStrike, Okta, AWS, Wiz and Kubernetes audit logs.
The README is unusually candid. It says 2,603 of the 6,991 rules in the library are executable, and a rule only counts as executable after it has been replayed and watched to fire, which proves reachability but not that it detects a real attack. Triage runs on a bundled ~2 GB `llama3.2:3b` model that works on CPU, which it says is not a frontier model: over 50 alerts it gave usable output 44 times before the reply was constrained to JSON and 50 times after. It states that no hosted provider has ever been exercised, and it separates real, synthetic and benchmark data, linking a "reality audit" document.
Setup is `git clone` then `make up`, with `make smoke` to check an event travels through ingest, detection and the API. It needs Docker Compose v2 with 8 GB memory and 20 GB free disk, and the first run downloads the local model. A core profile runs 14 services, and a full profile with an event lake and entity graph runs 22 and needs about 12 GB. The licence is MIT and the last push was 2026-10-12. This review is based on the README and repository data; we have not run it ourselves.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-17
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 26
- Latest release
- v19.0.0 (2026-10-12)
- Open issues
- 41
- Recent issues with at least one comment
- 0/5
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #1099 Semgrep rule packs are unpinned, so the ratchet compares against a moving target2 comments · 2026-10-02
- #356 Connector wishlist — what should AiSOC ingest next?2 comments · 2026-06-30
- #353 First time contributing? Start here.2 comments · 2026-06-30
- #1410 fix(connectors): preserve critical severity for PagerDuty P1 incidents0 comments · 2026-10-19
- #1408 fix(connectors): preserve critical severity for Datadog logs0 comments · 2026-10-19
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Who it fits
- You want a self-hosted SOC where an AI agent investigates incidents, logs every prompt and tool call, and a human approves each response.
- You want to run with no API key: it bundles a local `llama3.2:3b` model.
- Your telemetry is in Splunk, Sentinel, Elastic, CrowdStrike, Okta, AWS, Wiz or Kubernetes, among 84 connectors.
- You cannot give it 8 GB memory and 20 GB disk for the core profile, or about 12 GB for the full one.
- You need a hosted model: the README says no hosted model provider has been tested.
- You need proven detection: 2,603 of 6,991 rules are executable, which proves reachability, not that they catch attacks.
How it differs
ADR is research code for detecting attacks on MCP agents. AiSOC is a broader security operations stack for your existing telemetry.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!