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.

Merge remote-tracking branch 'origin/main' into fix/ingest-auth-and-blocking-scanners

Beenu Aroradd902b81a65d
diff --cc CHANGELOG.md
index 75fa26d45,84939699a..85fff81fc
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -232,29 -189,28 +232,51 @@@ number is the one the requirement is si
### Added
+- `make ingest-token` / `python -m app.scripts.mint_ingest_token` mints the
+ push credential for a fresh deployment, the role `bootstrap_admin` plays
+ for the console login. Idempotent — a second run returns the same token
+ rather than leaving a trail of live credentials nobody revokes.
+- `connector-push`, `ai-runtime`, `ai-finding` and `k8s-audit` are now
+ mintable inbox templates. The last three already shipped as YAML and were
+ named in the AI SDK's own setup instructions and in the Kubernetes
+ connector docs, but none was in `ALLOWED_TEMPLATE_IDS`, so the documented
+ setup for the AI-estate feature returned 400 and the templates were
+ unreachable.
+- `scripts/check_inbox_templates.py` compares shipped templates against
+ mintable ids **in both directions**, plus the console catalog, and carries
+ a `--self-test` that injects drift in each direction and requires the gate
+ to catch it. A one-directional check would have printed OK throughout the
+ defect above.
+- The golden pipeline asserts that an unauthenticated push is refused, not
+ only that an authenticated one succeeds — the happy path would go on
+ passing if authentication were removed.
+- `/v1/ingest` now bounds the request body (`INGEST_MAX_BODY_BYTES`, 10 MiB
+ default). `MAX_BATCH_SIZE` only counts events after the payload is
+ decoded, so nothing bounded the decode itself.
+
+
+ - **`RENDER_FALLBACK_EXEMPT` is now checked in both directions.**
+ `ALLOWED_ILLUSTRATIVE` had a staleness check from the start and this list
+ had none, so an exemption could outlive the code it excused and go on
+ covering whatever was written next under that name.
+ - **A corpus floor.** The gate refuses a root holding no `.ts`/`.tsx` rather
+ than certifying it: a renamed directory or a changed suffix produces zero
+ findings over zero files, and found-nothing and scanned-nothing print the
+ same word. It also names what it scanned, rooted at `git rev-parse`.
+ - **A real `--self-test`.** Twenty-six cases, each asserting the *rule* that
+ must account for it rather than that something fired — the conditional rules
+ overlap by construction, so a boolean check would pass with half the fixes
+ reverted. Each case builds its own source and its own tree.
+ - **`KNOWN_UNGATED`**, a shrink-only ledger of sites the detector reports and
+ the tree has not fixed, each with a reason, so a stricter rule can land
+ without weakening it. Not an exemption: while an entry stands the gate
+ prints the outstanding count instead of the unqualified "all gated"
+ sentence. Recorded by count, so an entry cannot survive its own fix and a
+ second violation cannot hide behind a recorded one. It shipped holding the
+ seven sites this revision first detected and is **empty** — they were fixed
+ in a parallel change, the counts stopped matching, and the entries had to be
+ deleted before the build would pass. The console is now genuinely clean:
+ 21 module-scope fabricated-record literals, 21 of them gated.
- **`scripts/generate_corpus_stats.py`** — generates
`apps/web/src/data/corpus-stats.json` + `corpusStats.ts` from the compiled