Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.
Python agentic-aiai-securityalert-triageblue-teamcybersecuritydetection-engineeringincident-responselanggraphllm-agentsmcpmitre-attackmodel-context-protocolpurple-teamsecurity-operationsself-hostedsiemsoarsocthreat-detectionthreat-intelligence
chore(release): v20.1.0 (#1476)
Beenu Aroraf2955c7c1677
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 40f245bc3..34dd8dcc0 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0## [Unreleased]+## [20.1.0] - 2026-10-22+### Security- `@vitest/mocker` moves to 4.1.12 in all three npm lockfiles (rootdiff --git a/README.md b/README.mdindex 3b684173c..dd923c68d 100644--- a/README.md+++ b/README.md@@ -6,7 +6,7 @@**An open-source, self-hostable AI Security Operations Center.** It ingests your security telemetry, detects and correlates threats, investigates them with AI agents whose reasoning is fully auditable, and proposes responses a human approves.-[](https://opensource.org/licenses/MIT) [](CHANGELOG.md) [](https://github.com/beenuar/AiSOC/actions/workflows/ci.yml)+[](https://opensource.org/licenses/MIT) [](CHANGELOG.md) [](https://github.com/beenuar/AiSOC/actions/workflows/ci.yml)[](https://github.com/beenuar/AiSOC/actions/workflows/codeql.yml) [](https://securityscorecards.dev/viewer/?uri=github.com/beenuar/AiSOC) [](https://raw.githubusercontent.com/beenuar/AiSOC/main/apps/web/public/papers/aisoc-technical-guide.pdf)**[Technical Guide (PDF)](https://raw.githubusercontent.com/beenuar/AiSOC/main/apps/web/public/papers/aisoc-technical-guide.pdf)** · [Docs](https://beenuar.github.io/AiSOC/) · [Architecture](docs/architecture/README.md) · [What actually works](docs/audit/REPOSITORY_REALITY.md) · [Discussions](https://github.com/beenuar/AiSOC/discussions)diff --git a/RELEASES.md b/RELEASES.mdindex ae1702865..443b27b0b 100644--- a/RELEASES.md+++ b/RELEASES.md@@ -2,7 +2,9 @@This file mirrors what used to live in the "What's new" section of [`README.md`](README.md). The complete, machine-readable inventory (with file paths, env-var diffs, and per-release test counts) lives in [`CHANGELOG.md`](CHANGELOG.md).-> **TL;DR for first-time visitors:** AiSOC is on `v20.0.0`, released 2026-10-21. **The security-response release: four published advisories, the SSRF guard on every connector egress path, and the dependency queue worked to zero.** Four vulnerability reports were each reproduced against a production-mode stack, fixed, and published as advisories: [GHSA-wwq7-2xvh-qgq6](https://github.com/beenuar/AiSOC/security/advisories/GHSA-wwq7-2xvh-qgq6) (cases GET routes enforced no `cases:read`, so an API key minted with only `alerts:read` could list cases and read their comments, timeline and evidence chain), [GHSA-9mc5-hqgh-j6wf](https://github.com/beenuar/AiSOC/security/advisories/GHSA-9mc5-hqgh-j6wf) (any `cases:write` holder could author a comment the console renders as an unattributed "System note"), [GHSA-898c-wxrw-hx6c](https://github.com/beenuar/AiSOC/security/advisories/GHSA-898c-wxrw-hx6c) (outbound webhooks: registration 500ed against row-level security for every tenant, and destinations were never SSRF-validated), and [GHSA-cq4g-g6wp-4m2w](https://github.com/beenuar/AiSOC/security/advisories/GHSA-cq4g-g6wp-4m2w) (a tenant-controlled connector `base_url` could reach cloud metadata, loopback and internal services from the stateless test route, resource reads and scheduled polls — the guard now sits on every construction path, and the API refuses those destinations before they are stored). **This is the breaking change:** `POST /api/v1/cases/{case_id}/comments` no longer accepts `is_system` in the request body — the server ignores the field rather than refusing the request, so existing clients keep succeeding and only generated SDK request types lose the property; system notes are written by the server itself. Supply-chain pinning tightened in both directions: the semgrep rule packs the scanner ratchet was measured with are vendored into the tree with a rules-digest arm, and the Oct-21 advisory wave (a critical `certifi`, `aiohttp`, `pillow`, the MCP SDK, and the npm floors) is cleared across every lockfile — with one recorded, expiring exception where upstream `fastembed` still caps `pillow` below the fixed version in `services/threatintel`. Four connectors (Lacework, Tines, Datadog, PagerDuty) stopped collapsing their vendor's own top severity into `high`, an OpenCTI feed client validated against a live platform joins threat intel, and the LLM gateway image is pinned to the exact version the stack was measured against after upstream deleted the floating tag it referenced. **39 defects were fixed across this release and the two before it** (12 here, 11 in v19.0.0, 16 in v18.0.0). The chart publishes as **`7.9.0`**. Everything below describes v19.0.0 and earlier, which this release does not change.+> **TL;DR for first-time visitors:** AiSOC is on `v20.1.0`, released 2026-10-22. **The harness-honesty release: the measurements and safety nets around the product were made as truthful as the product itself, and one real data-loss defect in every connector's poll loop is closed.** The data-loss fix is externally contributed ([meshreyy](https://github.com/meshreyy)): ingest reports per-event normalization failures as HTTP 200 with accepted/rejected counts, and the connector scheduler advanced its checkpoint on HTTP success alone — so a partially rejected batch moved the cursor past events that were never stored, permanently and silently. The cursor now advances only when every submitted event was accepted; a rejected page is re-fetched on the next overlapping poll and deduplicated by the sink. The live-agent eval was flattering itself two ways — per-incident `asyncio.run` left the model client on a dead event loop so most incidents silently ran heuristics, and failed incidents were dropped from the sample — it now runs one loop per run, scores failures as **0 with the reason recorded**, and the 0.40 groundedness floor was re-derived under the fixed harness (it holds, now 0.04 below the lowest honest run rather than 0.13 below a flattered one). The weekly chaos store-outage legs grade real behaviour instead of artifacts of their own probe contract, which is also why the API gained unauthenticated **`GET /api/v1/health` and `GET /api/v1/health/ready`** probes (database blocks at 503, cache degrades at 200) — the redis and qdrant legs pass end to end; the postgres leg stays red **by design**, naming the services that do not yet export the store keys the contract reads ([#1446](https://github.com/beenuar/AiSOC/issues/1446) stays open). The chart `stable` channel is now guarded by **both version lines** — v20.0.0 (chart 7.9.0, not a chart major) had carried chart `stable` across an application major while every image `stable` tag correctly held at v19 — and a dispatchable repair workflow exists and was used to roll the channel back to 7.8.0, where it stays until a deliberate promotion; **this release moves neither `stable` channel**. `fastapi` moves to 0.146.0 across all 32 declaration sites and 13 locks in one change, the Oct-22 Dependabot waves are folded, and `@vitest/mocker` 4.1.12 closes CVE-2026-112949/112950 in all three npm lockfiles. **11 defects were fixed in this release, 34 across it and the two before** (11 here, 12 in v20.0.0, 11 in v19.0.0 — counting distinct product or CI defects named in each release's Fixed and Security sections, dependency-version advisories excluded). The chart publishes as **`7.10.0`**. Everything below describes v20.0.0 and earlier, which this release does not change.+>+> **Previously:** AiSOC was on `v20.0.0`, released 2026-10-21. **The security-response release: four published advisories, the SSRF guard on every connector egress path, and the dependency queue worked to zero.** Four vulnerability reports were each reproduced against a production-mode stack, fixed, and published as advisories: [GHSA-wwq7-2xvh-qgq6](https://github.com/beenuar/AiSOC/security/advisories/GHSA-wwq7-2xvh-qgq6) (cases GET routes enforced no `cases:read`, so an API key minted with only `alerts:read` could list cases and read their comments, timeline and evidence chain), [GHSA-9mc5-hqgh-j6wf](https://github.com/beenuar/AiSOC/security/advisories/GHSA-9mc5-hqgh-j6wf) (any `cases:write` holder could author a comment the console renders as an unattributed "System note"), [GHSA-898c-wxrw-hx6c](https://github.com/beenuar/AiSOC/security/advisories/GHSA-898c-wxrw-hx6c) (outbound webhooks: registration 500ed against row-level security for every tenant, and destinations were never SSRF-validated), and [GHSA-cq4g-g6wp-4m2w](https://github.com/beenuar/AiSOC/security/advisories/GHSA-cq4g-g6wp-4m2w) (a tenant-controlled connector `base_url` could reach cloud metadata, loopback and internal services from the stateless test route, resource reads and scheduled polls — the guard now sits on every construction path, and the API refuses those destinations before they are stored). **This is the breaking change:** `POST /api/v1/cases/{case_id}/comments` no longer accepts `is_system` in the request body — the server ignores the field rather than refusing the request, so existing clients keep succeeding and only generated SDK request types lose the property; system notes are written by the server itself. Supply-chain pinning tightened in both directions: the semgrep rule packs the scanner ratchet was measured with are vendored into the tree with a rules-digest arm, and the Oct-21 advisory wave (a critical `certifi`, `aiohttp`, `pillow`, the MCP SDK, and the npm floors) is cleared across every lockfile — with one recorded, expiring exception where upstream `fastembed` still caps `pillow` below the fixed version in `services/threatintel`. Four connectors (Lacework, Tines, Datadog, PagerDuty) stopped collapsing their vendor's own top severity into `high`, an OpenCTI feed client validated against a live platform joins threat intel, and the LLM gateway image is pinned to the exact version the stack was measured against after upstream deleted the floating tag it referenced. **39 defects were fixed across this release and the two before it** (12 here, 11 in v19.0.0, 16 in v18.0.0). The chart publishes as **`7.9.0`**. Everything below describes v19.0.0 and earlier, which this release does not change.>> **Previously:** AiSOC was on `v19.0.0`, released 2026-10-12. **The release that finished the depth plan's analyst, collection and governance phases.** Nineteen workstreams landed as one verified tree. A session now has **one producer and three stores** that cannot disagree about which session an event belongs to; a real security **posture is collected and versioned** so a detection reads the posture that was true when an event happened; behavioural **baselines moved into CORE** as a fusion module. Collection meets an estate the way it emits — an **OTLP logs receiver, a Kafka input** for customer topics, and a **real TAXII 2.1 server** over the tenant IOC store — and a **cold-tier lake query reports a cost estimate and a progress state** instead of timing out silently. The **Helm chart installs CORE** with exactly one scheduler replica leading through a Postgres lease. A playbook can **ask the person who signed in, then their manager, and branch on the signed answer**; AiSOC's own **MCP server speaks streamable HTTP**, authorized and audited per call; a case opens a **war room** that syncs decisions back; a **hunt that finds something becomes a cited report**; the **responder app is an installable build** with real APNs and FCM delivery. Governance closed the 8.1 clauses: **WebAuthn** as a console second factor enforceable per role, an **enforced audit retention window** that leaves the surviving chain verifiable, **axe accessibility** on the case workspace and alert list, and a tenant's **entitlement limit that can refuse work** when the tenant opts in. **This is the breaking change:** `PATCH /api/v1/alerts/{id}` used to answer **200 while silently dropping** any field outside its five writable ones — a success for a write that did not happen — and now answers **422** naming the field and the route that applies it. If you call that endpoint with `disposition`, `severity`, `confidence` or `snoozed_until`, read the BREAKING section before upgrading. **67 defects were fixed across this release and the two before it** (11 here, 16 in v18.0.0, 40 in v17.1.0), including **tenant deletion**, which had been impossible on any database holding audit rows because the audit immutability trigger refused the cascade its own foreign key declares. The chart publishes as **`7.8.0`**. Everything below describes v18.0.0 and earlier, which this release does not change.>@@ -22,7 +24,29 @@ This file mirrors what used to live in the "What's new" section of [`README.md`]## What's new-`VERSION` is `20.0.0`. The **v20.0.0** release (2026-10-21) is the+`VERSION` is `20.1.0`. The **v20.1.0** release (2026-10-22) closes a+data-loss defect in every connector's poll loop (an externally+contributed fix: the checkpoint advanced past events ingest rejected,+and now advances only when every submitted event was accepted), makes+the measurement harnesses as honest as what they measure (the live-agent+eval runs one event loop per run and scores failed investigations as 0+with reasons, with the 0.40 groundedness floor re-derived under the+fixed harness; the chaos store-outage legs grade real behaviour, with+the redis and qdrant legs passing end to end and the postgres leg red+by design on #1446), adds unauthenticated liveness and readiness probes+to the API (`GET /api/v1/health`, `GET /api/v1/health/ready` — database+blocks, cache degrades), guards the chart `stable` channel on both+version lines with a dispatchable repair workflow, and moves `fastapi`+to 0.146.0 across every declaration site and lock in one change, with+the Oct-22 Dependabot waves folded and `@vitest/mocker` 4.1.12 closing+CVE-2026-112949/112950. No breaking changes, and **neither `stable`+channel moves**. 11 defects were fixed (34 across this release and the+two before it). See the TL;DR above and the `[20.1.0]` section of+[`CHANGELOG.md`](CHANGELOG.md) for the full inventory.++### Previously: v20.0.0++The **v20.0.0** release (2026-10-21) is thesecurity-response release: four vulnerability reports reproduced,fixed and published as advisories (cases read-scope, system-notespoofing, webhook RLS + SSRF, and the SSRF guard adopted on everydiff --git a/VERSION b/VERSIONindex e88320d7c..e43bba47d 100644--- a/VERSION+++ b/VERSION@@ -1 +1 @@-20.0.0+20.1.0diff --git a/apps/docs/static/data/scoreboard.json b/apps/docs/static/data/scoreboard.jsonindex e4952d93d..bde25d9f2 100644--- a/apps/docs/static/data/scoreboard.json+++ b/apps/docs/static/data/scoreboard.json@@ -4,8 +4,8 @@"rows": [{"date": "2026-10-22",- "agent_version": "v20.0.0",- "commit_sha": "b6fcc11f",+ "agent_version": "v20.1.0",+ "commit_sha": "40d97bee","substrate": true,"eval_mode": "substrate-only","mitre_accuracy": 0.97,diff --git a/apps/docs/static/img/console/ai-triage-verdict.png b/apps/docs/static/img/console/ai-triage-verdict.pngindex a7eb96a25..dece2b612 100644Binary files a/apps/docs/static/img/console/ai-triage-verdict.png and b/apps/docs/static/img/console/ai-triage-verdict.png differdiff --git a/apps/docs/static/img/console/alerts-queue.png b/apps/docs/static/img/console/alerts-queue.pngindex 83e7afcdc..7687a26e8 100644Binary files a/apps/docs/static/img/console/alerts-queue.png and b/apps/docs/static/img/console/alerts-queue.png differdiff --git a/apps/docs/static/img/console/soc-operations.png b/apps/docs/static/img/console/soc-operations.pngindex e154f83fd..23d239575 100644Binary files a/apps/docs/static/img/console/soc-operations.png and b/apps/docs/static/img/console/soc-operations.png differdiff --git a/apps/docs/static/img/console/threat-intel-kev.png b/apps/docs/static/img/console/threat-intel-kev.pngindex 6afabab22..6379a2850 100644Binary files a/apps/docs/static/img/console/threat-intel-kev.png and b/apps/docs/static/img/console/threat-intel-kev.png differdiff --git a/apps/docs/static/llms-full.txt b/apps/docs/static/llms-full.txtindex dc35e51e7..6c4dfc9f0 100644--- a/apps/docs/static/llms-full.txt+++ b/apps/docs/static/llms-full.txt@@ -3,7 +3,7 @@<!-- Generated by scripts/generate_llms_txt.py. Do not edit by hand; run the script and commit the result. -->> AiSOC is an open-source, self-hostable AI Security Operations Center, MIT-> licensed and maintained by the AiSOC community. Version 20.0.0.+> licensed and maintained by the AiSOC community. Version 20.1.0.> Repository: https://github.com/beenuar/AiSOC. Documentation: https://beenuar.github.io/AiSOC/.This file exists so an automated reader can answer questions about AiSOC@@ -127,7 +127,7 @@ plans/ Historical prototype subtree — reference only, never editedEvery number in this file is generated from the artefact that owns it. If youneed to state one, re-derive it rather than quoting a figure from prose —-including from this file, which is a snapshot of version 20.0.0.+including from this file, which is a snapshot of version 20.1.0.```python3 scripts/generate_corpus_stats.py --check # executable + on-disk rulesdiff --git a/apps/docs/static/llms.txt b/apps/docs/static/llms.txtindex cb58026ec..46b0d74ec 100644--- a/apps/docs/static/llms.txt+++ b/apps/docs/static/llms.txt@@ -6,7 +6,7 @@> security telemetry from 87 first-party connectors, normalises it to OCSF,> correlates it into alerts, and runs LLM agents that triage and investigate them.> Every agent decision is written to an investigation ledger, so the reasoning-> behind a verdict can be replayed step by step. MIT licensed. Current version 20.0.0.+> behind a verdict can be replayed step by step. MIT licensed. Current version 20.1.0.AiSOC is built and maintained by the AiSOC community. It is a complete SOCplatform rather than a single tool: ingestion, detection, correlation, agentdiff --git a/apps/web/package.json b/apps/web/package.jsonindex cdfac0f72..9ff393592 100644--- a/apps/web/package.json+++ b/apps/web/package.json@@ -1,6 +1,6 @@{"name": "@aisoc/web",- "version": "20.0.0",+ "version": "20.1.0","private": true,"description": "AiSOC SOC Console - Next.js 14 Frontend","license": "MIT",diff --git a/apps/web/public/screenshots/ai-triage-verdict.png b/apps/web/public/screenshots/ai-triage-verdict.pngindex a7eb96a25..dece2b612 100644Binary files a/apps/web/public/screenshots/ai-triage-verdict.png and b/apps/web/public/screenshots/ai-triage-verdict.png differdiff --git a/apps/web/public/screenshots/alerts-queue.png b/apps/web/public/screenshots/alerts-queue.pngindex 83e7afcdc..7687a26e8 100644Binary files a/apps/web/public/screenshots/alerts-queue.png and b/apps/web/public/screenshots/alerts-queue.png differdiff --git a/apps/web/public/screenshots/attack-graph-core-degraded.png b/apps/web/public/screenshots/attack-graph-core-degraded.pngindex 03ad2e6e1..767899805 100644Binary files a/apps/web/public/screenshots/attack-graph-core-degraded.png and b/apps/web/public/screenshots/attack-graph-core-degraded.png differdiff --git a/apps/web/public/screenshots/cases-empty.png b/apps/web/public/screenshots/cases-empty.pngindex 80f55b6b7..bbda5b566 100644Binary files a/apps/web/public/screenshots/cases-empty.png and b/apps/web/public/screenshots/cases-empty.png differdiff --git a/apps/web/public/screenshots/connector-wizard.png b/apps/web/public/screenshots/connector-wizard.pngindex 38bbb4d20..9df750fee 100644Binary files a/apps/web/public/screenshots/connector-wizard.png and b/apps/web/public/screenshots/connector-wizard.png differdiff --git a/apps/web/public/screenshots/connectors.png b/apps/web/public/screenshots/connectors.pngindex 2567a3de3..41022c927 100644Binary files a/apps/web/public/screenshots/connectors.png and b/apps/web/public/screenshots/connectors.png differdiff --git a/apps/web/public/screenshots/dashboard.png b/apps/web/public/screenshots/dashboard.pngindex e1a2a4e69..7f7d30137 100644Binary files a/apps/web/public/screenshots/dashboard.png and b/apps/web/public/screenshots/dashboard.png differdiff --git a/apps/web/public/screenshots/detection-rules.png b/apps/web/public/screenshots/detection-rules.pngindex 06a8ea322..b01491979 100644Binary files a/apps/web/public/screenshots/detection-rules.png and b/apps/web/public/screenshots/detection-rules.png differdiff --git a/apps/web/public/screenshots/federated-search.png b/apps/web/public/screenshots/federated-search.pngindex eefbc39ca..96f300522 100644Binary files a/apps/web/public/screenshots/federated-search.png and b/apps/web/public/screenshots/federated-search.png differdiff --git a/apps/web/public/screenshots/hunt.png b/apps/web/public/screenshots/hunt.pngindex 48bb41666..3caf5be03 100644Binary files a/apps/web/public/screenshots/hunt.png and b/apps/web/public/screenshots/hunt.png differdiff --git a/apps/web/public/screenshots/investigation-rail.png b/apps/web/public/screenshots/investigation-rail.pngindex 7243ee6c1..43e3b9319 100644Binary files a/apps/web/public/screenshots/investigation-rail.png and b/apps/web/public/screenshots/investigation-rail.png differdiff --git a/apps/web/public/screenshots/playbook-editor.png b/apps/web/public/screenshots/playbook-editor.pngindex fa1a8aa9e..2fff29184 100644Binary files a/apps/web/public/screenshots/playbook-editor.png and b/apps/web/public/screenshots/playbook-editor.png differdiff --git a/apps/web/public/screenshots/playbooks.png b/apps/web/public/screenshots/playbooks.pngindex 3c58bb501..bb9dc306b 100644Binary files a/apps/web/public/screenshots/playbooks.png and b/apps/web/public/screenshots/playbooks.png differdiff --git a/apps/web/public/screenshots/soc-operations.png b/apps/web/public/screenshots/soc-operations.pngindex e154f83fd..23d239575 100644Binary files a/apps/web/public/screenshots/soc-operations.png and b/apps/web/public/screenshots/soc-operations.png differdiff --git a/apps/web/public/screenshots/threat-intel-kev.png b/apps/web/public/screenshots/threat-intel-kev.pngindex 6afabab22..6379a2850 100644Binary files a/apps/web/public/screenshots/threat-intel-kev.png and b/apps/web/public/screenshots/threat-intel-kev.png differdiff --git a/infra/helm/aisoc/Chart.yaml b/infra/helm/aisoc/Chart.yamlindex 0d86c84ab..891e9adda 100644--- a/infra/helm/aisoc/Chart.yaml+++ b/infra/helm/aisoc/Chart.yaml@@ -25,13 +25,13 @@ type: application# the chart refuses grants it used to accept (see the v14.0.0 BREAKING# section), and the chart's major is the only coordinate a consumer pulling# `oci://ghcr.io/beenuar/charts/aisoc` sees before they install it.-version: 7.9.0+version: 7.10.0# Used as the image tag wherever a `tag:` in values.yaml is left empty, so# it has to be a tag the registry actually holds — it read "5.2.0", which# exists for no image, so every pod of a default install would have gone to# ImagePullBackOff. scripts/check_published_images.py resolves it the same# way the templates do and fails when it names nothing.-appVersion: "v20.0.0"+appVersion: "v20.1.0"keywords:- security