Skip to content

armgit / AiSOC

Public Imported from GitHub
0

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.

chore(release): v12.2.0 (#1011)

Beenu Arora6014ae92706c
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 527330208..15462c88a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,49 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
+## [12.2.0] - 2026-09-28
+
+### Fixed
+
+- **Four package READMEs deferred publication to a release that had already
+ shipped.** Each offered its install command under `v8.0+ (once <package>
+ lands on PyPI)`; v8.0 shipped four major versions ago, so by v12 the label
+ read as availability rather than as a caveat. None of the eight first-party
+ packages has ever been uploaded — asking the registries directly returns
+ **404 for all eight** — and the release workflow's publish jobs report
+ *success* regardless, because only the final upload step is
+ credential-gated and this repository's sole secret is `FLY_API_TOKEN`. The
+ job runs, skips the upload, and goes green.
+
+ The state is deliberate and the blocker is an account action rather than a
+ code change; what was wrong was what the READMEs said about it. They now say
+ it in the present tense, and `tests/test_package_install_claims.py` asks the
+ registry rather than trusting a workflow: a package that is not published
+ must carry the disclaimer, and one that later is published stops requiring
+ it, so publishing cannot leave a stale "not yet" behind either.
+
+### Changed
+
+- The claim-to-gate matrix reaches **238 rows, 238 GATED, 0 PARTIAL, 0 NO
+ GATE**. The final two rows were not blocked on a scheduling window, as the
+ tracker said: the live-agent workflow dispatched a class that exists nowhere
+ in the service, so its first-ever run failed in 92 seconds. The groundedness
+ floor is now 0.40, set from twelve runs across two environments rather than
+ from the local runs alone, which are a point mass under greedy decoding.
+ Phase 4 stays unchecked; every figure here came from a locally-served model
+ and no hosted provider has been exercised.
+
+- **Completion bounds now reach the bundled model.** Every investigator call
+ was unbounded — one ran to 40,960 tokens over twenty minutes — and the
+ obvious repair would have been inert, because langchain renders the bound as
+ `max_completion_tokens` and Ollama reads only `max_tokens`, ignoring the new
+ name in silence. Measured at a limit of 64: 64 tokens and `finish_reason:
+ length` under the legacy name, 72 and `stop` under the new one.
+
+- **CI installs each service's committed lock as an exact closure**, so the
+ version CI grades is the version the image ships.
+
+
### Fixed
- **The live-agent eval had never run, and could not have.** `live-agent-eval.yml`
diff --git a/README.md b/README.md
index a5f578aa5..89ad2271b 100644
--- a/README.md
+++ b/README.md
@@ -7,7 +7,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.
[![License: MIT](https://img.shields.io/badge/License-MIT-22c55e.svg?style=flat-square)](https://opensource.org/licenses/MIT)
-[![Version](https://img.shields.io/badge/version-12.1.0-f59e0b?style=flat-square)](CHANGELOG.md)
+[![Version](https://img.shields.io/badge/version-12.2.0-f59e0b?style=flat-square)](CHANGELOG.md)
[![CI](https://img.shields.io/github/actions/workflow/status/beenuar/AiSOC/ci.yml?branch=main&label=CI&style=flat-square)](https://github.com/beenuar/AiSOC/actions/workflows/ci.yml)
[![CodeQL](https://img.shields.io/github/actions/workflow/status/beenuar/AiSOC/codeql.yml?branch=main&label=CodeQL&style=flat-square)](https://github.com/beenuar/AiSOC/actions/workflows/codeql.yml)
[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/beenuar/AiSOC/badge)](https://securityscorecards.dev/viewer/?uri=github.com/beenuar/AiSOC)
diff --git a/RELEASES.md b/RELEASES.md
index b57d41e39..f954217dd 100644
--- a/RELEASES.md
+++ b/RELEASES.md
@@ -2,44 +2,40 @@
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 `v12.1.0`, released 2026-09-28 — the release where two services stopped serving unauthenticated and started refusing to serve instead. **Read the BREAKING section of the changelog before upgrading.** The actions service had skipped authentication entirely whenever its token was empty and `AISOC_DEV_MODE` was set, and compose defaults that flag on while nothing generated the token, so every stock install dispatched `isolate_host`, `disable_user`, `block_ip` and `run_script` to anything that could reach the port; the realtime edge verified connection tickets against a constant committed to this repository and treated an unset internal token as authorized; and a `viewer` role could write to cases on all nine write routes where the permission was enforced nowhere. Each was a reported vulnerability — four advisories across the three items — and each now returns 503 or 401 until the credential it needs is set, which is the intended failure and the reason this is a major. The upgrade action for all three is `make up`, because `scripts/ensure_env.py` backfills generated secrets into an **existing** `.env` and not only a new one. Alongside that, hunting stopped being a library of hunts somebody had already written: an agent turns a hypothesis into a plan whose fields and operators are closed enums, so there is no string it can produce that becomes SQL text, and the hunt corpus went from 5 to 68. Every product claim is backed by a failing CI test (claim-to-gate matrix at the v12.0.0 cut: 236 rows — 228 GATED / 8 PARTIAL / 0 NO GATE, counted by `scripts/check_claim_gate_matrix.py`, which is the figure to recount rather than to quote). The latest GitHub release with notes and downloads: <https://github.com/beenuar/AiSOC/releases/latest>.
+> **TL;DR for first-time visitors:** AiSOC is on `v12.2.0`, released 2026-09-28 — the release where two services stopped serving unauthenticated and started refusing to serve instead. **Read the BREAKING section of the changelog before upgrading.** The actions service had skipped authentication entirely whenever its token was empty and `AISOC_DEV_MODE` was set, and compose defaults that flag on while nothing generated the token, so every stock install dispatched `isolate_host`, `disable_user`, `block_ip` and `run_script` to anything that could reach the port; the realtime edge verified connection tickets against a constant committed to this repository and treated an unset internal token as authorized; and a `viewer` role could write to cases on all nine write routes where the permission was enforced nowhere. Each was a reported vulnerability — four advisories across the three items — and each now returns 503 or 401 until the credential it needs is set, which is the intended failure and the reason this is a major. The upgrade action for all three is `make up`, because `scripts/ensure_env.py` backfills generated secrets into an **existing** `.env` and not only a new one. Alongside that, hunting stopped being a library of hunts somebody had already written: an agent turns a hypothesis into a plan whose fields and operators are closed enums, so there is no string it can produce that becomes SQL text, and the hunt corpus went from 5 to 68. Every product claim is backed by a failing CI test (claim-to-gate matrix at the v12.0.0 cut: 236 rows — 228 GATED / 8 PARTIAL / 0 NO GATE, counted by `scripts/check_claim_gate_matrix.py`, which is the figure to recount rather than to quote). The latest GitHub release with notes and downloads: <https://github.com/beenuar/AiSOC/releases/latest>.
---
## What's new
-`VERSION` is `12.1.0`. The **v12.1.0** release (2026-09-28) is a security and
-correctness release. Its theme is narrower than v12.0.0's and worth stating
-plainly: several controls were reading a description of the system rather than
-the system, and reported success about the case they could not see.
-
-**v12.1.0 highlights (September 28, 2026)**
-- **A firewall containment action could be made to release a block.** The PAN-OS
- user-id client interpolated the caller's `ip` and `tag` into XML with
- f-strings, and the injected payload is valid PAN-OS — so `block_ip` emitted a
- message telling the firewall to *unregister* an address of the attacker's
- choosing, and the firewall answered success
- ([GHSA-w754-prh8-m56j](https://github.com/beenuar/AiSOC/security/advisories/GHSA-w754-prh8-m56j)).
-- **The published API image answered 500 to every `/api/v1` request.** A tracing
- middleware raised on the FastAPI version the lock resolved. CI installed the
- same package with no version bound, resolved a newer one, and passed — so CI
- and production were running different code, and the version CI never graded
- was the broken one.
-- **Sigma rules were evaluated by substring containment**, which cannot express
- a boolean, so every multi-clause rule matched nothing while reporting no
- error. The published executable-rule count does not rest on that path and did
- not change.
-- **Eight advisories fixed in v12.0.0 are now published.** They had remained in
- triage since the release that fixed them.
-- **A marketplace catalogue of 7,155 items now says which are executable** —
- 2,767 executable against 4,388 reference-only, tied to the detection truth
- table rather than to a flag that the compiler does not rewrite.
-- **The audit hash chain can no longer fork.** Appends are serialized per tenant
- and a unique index makes two rows claiming the same predecessor
- unrepresentable; measured at 500 concurrent appends, 0 forks against 401
- before.
-
-The full inventory — 16 entries — lives under `[12.1.0]` in [`CHANGELOG.md`](CHANGELOG.md).
+`VERSION` is `12.2.0`. The **v12.2.0** release (2026-09-28) finishes the
+verification work v12.1.0 started, and its one user-facing correction is an
+honesty fix rather than a feature.
+
+**v12.2.0 highlights (September 28, 2026)**
+- **Four package READMEs told you to install packages that do not exist.** Each
+ deferred to `v8.0+`, a release that shipped four major versions ago, so the
+ label read as availability. None of the eight first-party packages has ever
+ been uploaded — the registries return 404 for all eight — while the release
+ workflow's publish jobs report success, because only the upload step is
+ credential-gated. A gate now asks the registry instead of trusting the
+ workflow.
+- **The claim-to-gate matrix is complete**: 238 rows, all GATED, no PARTIAL
+ and no NO GATE. Phase 4 stays unchecked, because a funded hosted-model key
+ is not something code can supply.
+- **Completion bounds now reach the bundled model.** They had been rendered as
+ `max_completion_tokens`, which Ollama ignores silently, so every investigator
+ call was effectively unbounded — one ran to 40,960 tokens.
+- **CI installs each service's committed lock as an exact closure**, so the
+ version CI grades is the version the image ships.
+
+The full inventory — 11 entries — lives under `[12.2.0]` in [`CHANGELOG.md`](CHANGELOG.md).
+
+---
+
+## v12.1.0 (2026-09-28)
+
+A security and correctness release: several controls were reading a description of the system rather than the system. Full detail under `[12.1.0]` in [`CHANGELOG.md`](CHANGELOG.md).
---
diff --git a/VERSION b/VERSION
index 77903b35f..685332623 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-12.1.0
+12.2.0
diff --git a/apps/docs/static/data/scoreboard.json b/apps/docs/static/data/scoreboard.json
index b4c7138e6..ef928d8df 100644
--- a/apps/docs/static/data/scoreboard.json
+++ b/apps/docs/static/data/scoreboard.json
@@ -4,8 +4,8 @@
"rows": [
{
"date": "2026-09-28",
- "agent_version": "v12.1.0",
- "commit_sha": "c55d3afa",
+ "agent_version": "v12.2.0",
+ "commit_sha": "3a191e17",
"substrate": true,
"eval_mode": "substrate-only",
"mitre_accuracy": 0.97,
diff --git a/apps/docs/static/llms-full.txt b/apps/docs/static/llms-full.txt
index cb28d3e0e..372126239 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 12.1.0.
+> licensed and maintained by the AiSOC community. Version 12.2.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
diff --git a/apps/docs/static/llms.txt b/apps/docs/static/llms.txt
index b8805a01e..98c766e0a 100644
--- a/apps/docs/static/llms.txt
+++ b/apps/docs/static/llms.txt
@@ -6,7 +6,7 @@
> security telemetry from 84 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 12.1.0.
+> behind a verdict can be replayed step by step. MIT licensed. Current version 12.2.0.
AiSOC is built and maintained by the AiSOC community. It is a complete SOC
platform rather than a single tool: ingestion, detection, correlation, agent
diff --git a/apps/web/package.json b/apps/web/package.json
index 667a5ab53..1f1552072 100644
--- a/apps/web/package.json
+++ b/apps/web/package.json
@@ -1,6 +1,6 @@
{
"name": "@aisoc/web",
- "version": "12.1.0",
+ "version": "12.2.0",
"private": true,
"description": "AiSOC SOC Console - Next.js 14 Frontend",
"license": "MIT",
diff --git a/infra/helm/aisoc/Chart.yaml b/infra/helm/aisoc/Chart.yaml
index f8198e071..2ea2a57fe 100644
--- a/infra/helm/aisoc/Chart.yaml
+++ b/infra/helm/aisoc/Chart.yaml
@@ -2,13 +2,13 @@ apiVersion: v2
name: aisoc
description: AiSOC - the open-source, AI-native Security Operations Center
type: application
-version: 5.7.0
+version: 5.8.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: "v12.1.0"
+appVersion: "v12.2.0"
keywords:
- security
diff --git a/packages/aisoc-cli/README.md b/packages/aisoc-cli/README.md
index 0aeb52546..910299122 100644
--- a/packages/aisoc-cli/README.md
+++ b/packages/aisoc-cli/README.md
@@ -11,10 +11,11 @@ Developer CLI for building, validating, and publishing AiSOC plugins and detecti
git clone https://github.com/beenuar/AiSOC.git
cd AiSOC && pip install -e packages/aisoc-cli
-# v8.0+ (once aisoc-cli lands on PyPI):
-pipx install aisoc-cli # recommended (isolated venv)
-# or:
-pip install aisoc-cli
+# Not yet on PyPI — the upload is blocked on registry credentials,
+# which is an account action rather than a code change. Until then, install
+# from source with the command above.
+# pipx install aisoc-cli # recommended (isolated venv)
+# pip install aisoc-cli
```
## Commands
diff --git a/packages/plugin-sdk-py/README.md b/packages/plugin-sdk-py/README.md
index 12f1bff29..6322a89dd 100644
--- a/packages/plugin-sdk-py/README.md
+++ b/packages/plugin-sdk-py/README.md
@@ -12,8 +12,10 @@ response actions, and data-source connectors.
git clone https://github.com/beenuar/AiSOC.git
cd AiSOC && pip install -e "packages/plugin-sdk-py[dev]"
-# v8.0+ (once aisoc-plugin-sdk lands on PyPI):
-pip install aisoc-plugin-sdk
+# Not yet on PyPI — the upload is blocked on registry credentials,
+# which is an account action rather than a code change. Until then, install
+# from source with the command above.
+# pip install aisoc-plugin-sdk
```
## Quick Start
diff --git a/packages/sdk-py/README.md b/packages/sdk-py/README.md
index 39f702596..91e650e0c 100644
--- a/packages/sdk-py/README.md
+++ b/packages/sdk-py/README.md
@@ -14,8 +14,10 @@ Async Python client SDK for [AiSOC](https://github.com/beenuar/AiSOC).
git clone https://github.com/beenuar/AiSOC.git
cd AiSOC && pip install -e packages/sdk-py
-# v8.0+ (once aisoc-sdk lands on PyPI):
-pip install aisoc-sdk
+# Not yet on PyPI — the upload is blocked on registry credentials,
+# which is an account action rather than a code change. Until then, install
+# from source with the command above.
+# pip install aisoc-sdk
```
## Quick start
diff --git a/packages/sdk-ts/README.md b/packages/sdk-ts/README.md
index aad0b36cb..c39312551 100644
--- a/packages/sdk-ts/README.md
+++ b/packages/sdk-ts/README.md
@@ -14,10 +14,11 @@ TypeScript client SDK for [AiSOC](https://github.com/beenuar/AiSOC) — auto-gen
git clone https://github.com/beenuar/AiSOC.git
cd AiSOC && pnpm --filter @aisoc/sdk-ts install
-# v8.0+ (once @aisoc/sdk lands on npm):
-npm install @aisoc/sdk
-# or
-pnpm add @aisoc/sdk
+# Not yet on npm — the upload is blocked on registry credentials,
+# which is an account action rather than a code change. Until then, install
+# from source with the command above.
+# npm install @aisoc/sdk
+# pnpm add @aisoc/sdk
```
## Quick start
diff --git a/tests/test_package_install_claims.py b/tests/test_package_install_claims.py
new file mode 100644
index 000000000..8ac961303
--- /dev/null
+++ b/tests/test_package_install_claims.py
@@ -0,0 +1,99 @@
+"""A package README must not imply an install command that cannot resolve.
+
+None of the eight first-party packages has ever been uploaded. The release
+workflow's publish jobs report **success** anyway, because only the final
+upload step is credential-gated and the repository's sole secret is
+`FLY_API_TOKEN` — so the job runs, skips the upload, and goes green. Asking
+the registries is the only way to know: all eight return 404.
+
+That is a deliberate, documented state and not a defect. The defect is what
+the READMEs said about it. Four of them offered the install command under the
+heading `v8.0+ (once <package> lands on PyPI)`, and v8.0 shipped four major
+versions ago — so by v12 the label read as "this should already work" rather
+than "not yet". A reader runs it, gets `No matching distribution found`, and
+concludes the project is broken.
+
+This gate holds the two together: for every package that is *not* on its
+registry, the README that advertises it must say so in the present tense. If
+a package is later published, the gate stops requiring the disclaimer for it
+rather than needing to be edited — so publishing cannot leave a stale "not
+yet" behind either.
+"""
+
+from __future__ import annotations
+
+import json
+import pathlib
+import re
+import urllib.error
+import urllib.request
+
+import pytest
+
+REPO = pathlib.Path(__file__).resolve().parents[1]
+
+#: (README, registry, distribution name, the install command it advertises).
+PACKAGES: tuple[tuple[str, str, str, str], ...] = (
+ ("packages/sdk-py/README.md", "pypi", "aisoc-sdk", "pip install aisoc-sdk"),
+ ("packages/aisoc-cli/README.md", "pypi", "aisoc-cli", "pip install aisoc-cli"),
+ ("packages/plugin-sdk-py/README.md", "pypi", "aisoc-plugin-sdk", "pip install aisoc-plugin-sdk"),
+ ("packages/aisoc-sandbox/README.md", "pypi", "aisoc-sandbox", "pip install aisoc-sandbox"),
+ ("packages/sdk-ts/README.md", "npm", "@aisoc/sdk", "npm install @aisoc/sdk"),
+)
+
+#: Wording that tells a reader, in the present tense, that the command above
+#: will not resolve yet. Any one of these satisfies the gate — the point is
+#: that the reader is warned, not that a particular sentence is used.
+DISCLAIMERS = ("not yet on pypi", "not yet on npm", "ready, unpublished", "will not resolve")
+
+#: A label naming a release that has already shipped. It reads as availability
+#: rather than as a caveat, which is precisely how these went stale.
+STALE_LABEL = re.compile(r"v\d+\.\d+\+?\s*\(once\b", re.I)
+
+
+def _published(registry: str, name: str) -> bool:
+ url = f"https://pypi.org/pypi/{name}/json" if registry == "pypi" else f"https://registry.npmjs.org/{name.replace('/', '%2f')}"
+ try:
+ with urllib.request.urlopen(url, timeout=20) as response: # noqa: S310 - fixed https hosts
+ return response.status == 200 and bool(json.loads(response.read() or b"{}"))
+ except urllib.error.HTTPError as exc:
+ if exc.code == 404:
+ return False
+ pytest.skip(f"{registry} answered {exc.code} for {name}; cannot establish publication")
+ except OSError as exc:
+ pytest.skip(f"no network to {registry} ({exc}); cannot establish publication")
+ return False
+
+
[email protected]("relative,registry,name,command", PACKAGES, ids=[p[2] for p in PACKAGES])
+def test_an_unpublished_package_says_so(relative: str, registry: str, name: str, command: str) -> None:
+ readme = REPO / relative
+ assert readme.is_file(), f"{relative} is gone but still listed here"
+ text = readme.read_text(encoding="utf-8")
+
+ if command not in text:
+ return # it does not advertise the command, so there is nothing to qualify
+
+ if _published(registry, name):
+ return # the command resolves; no disclaimer needed, and none required
+
+ lowered = text.lower()
+ assert any(d in lowered for d in DISCLAIMERS), (
+ f"{relative} shows `{command}` but {name} is not on {registry} (404). Say so in the present tense next to the command."
+ )
+
+
[email protected]("relative", [p[0] for p in PACKAGES], ids=[p[2] for p in PACKAGES])
+def test_no_readme_defers_to_a_release_that_already_shipped(relative: str) -> None:
+ """`v8.0+ (once ... lands on PyPI)` on a v12 tree is not a caveat.
+
+ Checked separately from the disclaimer because the two fail differently:
+ a missing disclaimer says nothing, while a stale one says something false
+ with more confidence than saying nothing would.
+ """
+ text = (REPO / relative).read_text(encoding="utf-8")
+ found = STALE_LABEL.search(text)
+ assert not found, (
+ f"{relative} defers publication to {found.group(0)!r}, a release that has shipped. "
+ f"The tree is at v{(REPO / 'VERSION').read_text().strip()}."
+ )