Repository navigation
AiSOC v23.1.0
Added
- The first community detection rule: an AI agent's file tool reading a
credential-bearing file.
community-toufiqtoufiqbo-ai-agent-credential-file-read(high,
application, T1552.001) matches theai_runtimefields the
aisoc-ai-sdkactually emits (tool_name,resource), names the files
that hold long-lived credentials —id_rsa,.aws/credentials,
/etc/shadowand their kin — and excludes public-key reads (*.pub,
authorized_keys). Prompt-level secret scanning cannot see this path: the
prompt is clean, and the disclosure happens on the way out — into the
model context, a tool argument, or a second call. It ships
enabled: falsewith aquarantine_reason, which is what the truth-table
gate requires of a tier the engine does not load, with positive and
negative fixtures alongside. The published counts follow: 7408 rules on
disk, and the community tier moves 1 → 2. Contributed by @Toufiqtoufiqbo
(#1804).
Fixed
-
The first
make upon a fresh install built the schema and then refused
to start the stack it had just built. The Postgres initdb hook
(infra/postgres/initdb/10_apply_migrations.sh) applied the whole migration
chain but recorded none of it, so toscripts/pending_migrations.pythe
database it produced — every table present, noaisoc_schema_migrations—
read as behind the entire chain.make up's schema guard then stopped the
very first run with "behind — 157 migration(s) pending" and sent the
operator tomake upgrade, which re-applied all ~160 files under strict
mode. The hook now records each migration as it lands, in the same table the
runtime runner (app.scripts.run_migrations) uses, so a fresh install reads
as up to date, an interrupted chain leaves an accurate record of what did
apply, and the first in-place upgrade starts from the truth instead of from
zero. A live regression test boots a container with the repository's own
init hooks mounted and asserts the detector's verdict — and CI executes it
rather than skipping it: the docker guard is for machines without a
daemon, and the merge'sPython — Testsjob ran it to a pass. Reported by
@Dhanu188 on #353. -
Datadog Cloud SIEM read 100 signals per poll and lost the rest.
DatadogCloudSIEMConnector.fetch_alertssentpage[limit]=100with
sort=-timestampand ignoredmeta.page.after, which Datadog documents as
"the cursor used to get the next results" and its OpenAPI document declares as
thex-paginationcursor forGET /api/v2/security_monitoring/signals. A poll
window opens where the last one closed, so a window holding more than 100
signals lost its oldest ones for good, and those are the start of whatever
caused the burst. It now reads throughread_token_pages, sending the cursor
back aspage[cursor]with the window, order and page size unchanged.
read_token_pagesgainsempty_page_ends, off by default: Datadog's
generated Python, Go and TypeScript clients all end this read on an empty page
as well as on an absent cursor, so a cursor beside an empty page must not
spend the page cap on a quiet window. Every existing caller keeps the rule that
an empty page carrying a token is followed.MAX_UNCLASSIFIEDfalls from 54
to 53. Contributed by @officialasishkumar (#1801). -
make demofailed before seeding anything — the demo seeder wrote case
statuses the schema refuses. The two random case makers in
app.scripts.seed_demodrew from the pre-consolidationcasesvocabulary
("open" / "in_progress" / "pending", 75% of the weighted draw), while
migration 083 repointed the ORMCasemodel ataisoc_cases, whose CHECK
constraint (migration 012) admits only the console's states. The first
invalid case aborted the whole seed transaction, so nothing landed — not the
catalogue, not theINC-RT-001LockBit showcase the contributor guide tells
newcomers to open. The makers now draw fromapp.services.case_status, and
_alert_status_for_casekeys on the live vocabulary instead of answering
its default for every real status. New tests pin the seeder's vocabulary to
the constants, the constants to the CHECK constraint text in migration 012,
and the incident specs to both; verified live both ways against a
schema-complete Postgres (unfixed:CheckViolationErroron the first batch;
fixed: 43 cases includingINC-RT-001, only schema-valid statuses on disk).
Reported by @Dhanu188 on #353. -
Duo authentication logs read 100 entries per poll and lost the rest.
DuoSecurityConnector.fetch_alertsread the first response of
GET /admin/v2/logs/authenticationand ignoredmetadata.next_offset. Duo
documents that endpoint as a paged list, 100 entries by default, and says "to
fetch all results, call repeatedly with the next_offset paging parameter as
long as the result metadata has next_offset values". A poll window opens where
the last one closed, so a window holding more than 100 authentications lost
the rest for good. It now asks for Duo's documented maximum of 1,000 per page
and followsnext_offset, sent back as the timestamp and txid "separated by a
comma" with the window unchanged and each page signed for its own parameters.
A failed later page keeps what was read, the 25-page bound is announced when
it binds, and a refused opening request still raises so the scheduler records
a failed poll.MAX_UNCLASSIFIEDfalls from 53 to 52. Contributed by
@officialasishkumar (#1802, carried as #1805). -
The marketplace builder asserted
enabled: falseabout rule files it
never opened.build_marketplace.py's fallbackquarantine_reasontold
every non-quarantined, non-executable row it was "disabled in the rule
file (enabled: false)" — a claim reached precisely when the builder had
not looked. The reason now names the real cause per tier, a rule file's
ownquarantine_reasonstill wins when it carries one, and a new test
walks every published entry whose reason quotesenabled: false(99
today), reads the rule file it cites, and fails if the flag disagrees — or
if it ever ends up checking nothing. (#1804) -
Five artefact generators'
--checkmodes compared text that line-ending
translation had already corrected. The marketplace, curation,
corpus-stats, truth-table and llms generators wrote the platform's line
endings andstr(Path)separators, and their checks read in text mode —
so a CRLF artefact and an LF template agreed with each other and the drift
was invisible, whilepnpm marketplace:curate --checkcould never pass on
Windows at all (601 backslashed paths, rewritten on every regenerate).
Every artefact write is now explicit\nwith.as_posix()manifest
paths, and the checks compare bytes and rejectb"\r". (#1804) -
Every in-run IOC enrichment failed during a deep investigation. The
investigator'senrich_ioctool defaulted tohttp://enrichment:8080—
the host-published port, not the8082the enrichment service listens on
inside the compose network — and postedtypewherePOST /enrich
requiresioc_type. The agents service sets noENRICHMENT_SERVICE_URL
override in compose, so the broken default is what ran: every
investigation IOC enrichment raised "All connection attempts failed" and
the case recorded "IP enrichment failed", while fusion, which pins the
correct URL, enriched the same IP correctly. The tool now defaults to
:8082like the two other in-process consumers and sendsioc_type,
pinned by a respx test that drives the module's default URL against the
real/enrichcontract and fails on either the old port or the old field
name. Contributed by @43n51c (#1806). -
A federated Splunk search against a self-hosted index returned nothing
useful.SplunkConnector.querykept the configuredsaved_searchwhole
when it began withindex=, soindex=main— the common self-hosted case
— rendered assearch index=index=main …, which Splunk parses as a
literal and answers with zero rows; a connector on the defaultnotable
index was unaffected, which is why it slipped through. And the SPL
translator emitted no field projection, so even matching events came back
carrying only Splunk's default fields, missing thesignature/src_ip
/dest_ip-class fields the pivot exists to show. Theindex=prefix is
now stripped before the name reachesto_spl(falling back tonotable
only when none is configured), and the rendered SPL appends| fields *
before| head N. Both halves are pinned by tests that fail on the
pre-fix tree. Contributed by @43n51c (#1807). -
The Hello, hunt tutorial claimed community rules are replay-graded; they
are not.scripts/validate_detections.pyreplays fixtures only for
native-tier rules (the ones with a compiled spec) — community-tier fixtures
ship alongside the rule and are first replayed at promotion. The tutorial's
enabledbullet now says exactly that instead of promising a grading that
never runs at that tier.
Security
- The Splunk connector validates the operator-supplied
index=token
before splicing it into SPL. Both ad-hoc search paths —_dispatch()on
the polling side andquery()on the federated side — stripindex=from
the configuredsaved_searchand interpolated the remainder unquoted, so a
value likemain | collect index=otherdispatched a two-stage pipeline the
configuration never meant to write. Not exploitable across a trust boundary
(the operator holds the Splunk token already), but nothing downstream
re-validated, so the connector now holds the same line the AQL translator
holds: a token outside[A-Za-z0-9_*:-]falls back to the default
notableindex with a warning naming the rejected value. Wildcards,
cluster prefixes, underscores and dashes pass through unchanged, pinned by
tests on both paths.
Documentation
-
The Wazuh guide said the connection test needs no cluster permissions;
it callsGET /_cluster/health. The connector page now documents the
minimalcluster:monitor/healthpermission and the Indexer role-mapping
steps that grant it, notes that the defaultcluster_composite_ops_ro
does not include health monitoring, explains the 401/403 error message the
two causes share, adds a CA-verified cURL probe, and says plainly that a
successful health probe does not prove alert-index search permission.
Contributed by @knowlet (#1800). -
The Hello, hunt tutorial told contributors to ship community rules
enabled: true— the one thingdetection_truth_table.py --check
rejects. Nothing loads a community rule into the compiled set, so the
tutorial's claim that community rules run in production by default was
false on both halves. Theenabledbullet now says what the gate
enforces:enabled: falseplus aquarantine_reasonnaming what
promotion would take. (#1804)