# AiSOC

> A self-hostable AI Security Operations Center that ingests security telemetry, correlates detections into incidents and has LLM agents triage them with an auditable ledger

- Category: Agents & Automation / Security Agents
- Language: Python
- Licence: MIT
- Repository: https://github.com/beenuar/AiSOC
- Website: https://beenuar.github.io/AiSOC/
- Canonical page: https://ai-tldr.dev/tools/aisoc/
- Updated: 2026-10-22

## In short

AiSOC is an open-source, self-hostable AI Security Operations Center. It sits in the Security Agents category of the Agents & Automation tools and is open-source, written in Python and licensed MIT. To get started: clone and bring the stack up.

## Overview

AiSOC is an open-source, self-hostable AI Security Operations Center. It takes in telemetry from your security tools, normalizes it, runs a detection rule library over it, groups what fires into incidents and hands each one to an AI agent for triage, then proposes a response that a human approves before anything reaches a vendor. It is written mostly in Python with a web console, runs under Docker Compose, and is licensed MIT.

Events arrive by push to an ingest API or by pull from click-and-connect data connectors such as Splunk, Sentinel, Elastic, CrowdStrike, Okta, AWS and Kubernetes audit logs, plus collectors for CloudTrail on S3 via SQS, GCP Pub/Sub, Azure Event Hubs and syslog/CEF. Kafka carries the normalized events to a fusion stage that runs the executable rules of the bundled library, applies each tenant's own tuning, and decides what becomes an alert; correlation then groups related alerts. A `packages/aisoc-migrate` tool translates existing Splunk SPL, Sentinel KQL and Elastic EQL detections and refuses rather than approximates what it cannot carry.

The agents read an alert, its correlated siblings, entity context and prior verdicts, and call typed tools for lake queries, graph traversals and enrichment instead of writing SQL. Every prompt, tool call, citation, verdict and token cost goes to an Investigation Ledger that exports as a signed evidence bundle, and a verdict citing an indicator the evidence never contained is demoted to human review. The core profile ships its own small local model through Ollama (a pinned `llama3.2:3b-instruct-q4_K_M`), so a fresh install produces real triage verdicts with no API key; the README says plainly that no hosted model provider has been exercised by the project.

## What it does

- End-to-end pipeline from ingest through detection, correlation and alerting to AI triage and a web console
- Push ingest API, dozens of data connectors with vendor-specific normalization, and cloud log collectors for AWS, GCP, Azure and syslog/CEF
- LLM triage agents restricted to typed tools, with every step recorded in an Investigation Ledger and exportable as a signed evidence bundle
- A bundled local model through Ollama so triage works offline, with options to run on a GPU, a host model or your own provider
- Playbooks that preview before they act and require deployment, tenant and playbook switches plus human approval to touch a vendor
- Threat intelligence from the public CISA Known Exploited Vulnerabilities catalog out of the box, with retro-hunts when new intel arrives

## Getting started

The README asks for Docker Compose v2 with 8 GB of memory and 20 GB of free disk in the Docker VM, plus python3 (3.9+) and bash. The first run downloads a ~2 GB model into a volume.

1. Clone and bring the stack up

   `make up` creates `.env`, generates the stack's secrets, creates an administrator and prints its password once. `make doctor` checks the prerequisites if something is missing.

```bash
git clone https://github.com/beenuar/AiSOC && cd AiSOC
make up
```

2. Prove the pipeline works

   `make smoke` posts one real event to the ingest API, follows it through Kafka, detection, correlation and Postgres, and reads the alert back from the public API, reporting PASS or FAIL for each stage.

```bash
make smoke
```

3. Sign in and load sample data

   Open the address `make up` printed. A tenant with nothing connected lands on a setup wizard; its Load sample data button sends five labelled scenarios through the same ingest path a real connector uses.

4. Connect real telemetry

   Push events with a credential from `make ingest-token`, or configure a data connector under Settings → Connectors. `make up-full` adds the event lake, entity graph, full-text search and enrichment.

```bash
curl -X POST http://localhost:8081/v1/ingest/batch \
  -H 'Content-Type: application/json' -H "Authorization: Bearer $AISOC_INGEST_TOKEN" \
  -d '{"connector_id":"edr-1","connector_type":"crowdstrike","events":[{"severity":"high",
       "title":"Encoded PowerShell from Office","host":"WIN-FIN-01"}]}'
```

## When to use it

- Stand up a self-hosted SOC pipeline for a small security team that wants AI triage without sending alerts to a hosted model
- Keep an auditable record of every AI triage decision, exportable as signed evidence for review
- Move existing Splunk, Sentinel or Elastic detections onto an open-source stack with an explicit report of what did not translate

## Version history

- 2026-10-22 v20.1.0: Adds unauthenticated liveness and readiness health endpoints to the API and closes dependency CVEs in the npm lockfiles.
