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.

5.4 KB
Raw Blame

Sigma compilation report

Imported Sigma rules are metadata until something translates them into the language the detection matcher evaluates. This is the result of that translation, and — more importantly — of replaying every translated rule through the real connector and the real engine to check it actually fires.

  • Imported Sigma rules considered: 3,132
  • Compiled and proven to fire: 1,770
  • Refused: 1,362

A rule ships only when a vendor-shaped event replayed through its connector's normalize() and the DetectionEngine produces a hit for that rule id, and an empty event of the same shape does not. The proof is that the rule is reachable and fires on a well-formed event of its own log source; it is not a claim that the rule detects an attack.

Shipping rules by emitting connector

Connector Rules proven to fire
windows_event 1,687
aws_cloudtrail 39
azure_activity 28
okta 16

Why the rest were refused

Refusing is deliberate. A translation that is merely close changes what a rule means, and rules that fire on the wrong events are worse than rules that do not ship.

Reason Rules Example
no connector emits this log source 556 access-of-sudoers-file-content.yaml: linux/None
negation is not faithfully expressible (missing field would flip) 464 a-rule-has-been-deleted-from-the-windows-firewall-exception-list.yaml: ModifyingApplication|startswith
compiled, but did not fire on its own proof event 133 abusable-dll-potential-sideloading-from-suspicious-location.yaml
|re is case-sensitive upstream and the matcher forces IGNORECASE 71 add-potential-suspicious-new-download-source-to-winget.yaml: CommandLine|re
field is a dotted path and the matcher has no path traversal 59 account-created-and-deleted-within-a-close-time-frame.yaml: properties.message
the connector rejected the proof event 30 azure-application-gateway-modified-or-deleted.yaml
|cidr has no matcher operator 17 communication-to-uncommon-destination-ports.yaml: DestinationIp|cidr
|all on a non-contains modifier has no matcher operator 14 aws-iam-s3browser-templated-s3-bucket-policy-creation.yaml: requestParameters|contains|all with wildcards
bare keywords search the whole event; the matcher is field-scoped 10 granting-of-permissions-to-an-account.yaml: keywords block
|base64/|base64offset has no matcher operator 7 cobaltstrike-service-installations-security.yaml: ServiceFileName|base64offset
|fieldref compares two fields and has no matcher operator 1 process-deletion-of-its-own-executable.yaml: TargetFilename|fieldref

Upstream lifecycle status

The importer quarantined rules by their SigmaHQ status, which put 2,844 test and 211 experimental rules behind a flag. That conflated two different facts: whether a rule can execute on this engine, and how confident its authors are in its content. Only the first is about AiSOC, and it was the actual blocker the whole time.

So status no longer decides. Fireability does, and status is carried through to the rule and onto the alert so it can still be filtered:

Upstream status Rules shipped Treatment
test 1,599 Shipped. In SigmaHQ this means reviewed and in community use — the normal state for most of the corpus, not a warning.
experimental 125 Shipped and labelled. Genuine false-positive risk, but that is a tuning problem, and hiding the rule does not help someone who wants the coverage.
(none recorded) 46 Shipped. No upstream status was recorded on import.

deprecated and unsupported are refused outright: upstream withdrew those, which is not a judgement call for a downstream consumer to revisit.

Licence

The imported corpus is licensed under the Detection Rule License 1.1, which permits redistribution in modified form — a translation is exactly that — provided author identification, a link to the rule, and the licence travel with it. Every compiled rule therefore carries a provenance block, and the engine stamps that attribution onto each alert, because DRL-1.1 also requires messages produced by a match to identify the rule's author.

Known gap: the author is not the person

What travels today is the upstream repository, the rule's upstream UUID, its path in that repository and the licence — enough to find the rule, not enough to name who wrote it. provenance.author is empty on all 1,770 compiled rules, because the Sigma importer never read the upstream author: field, and the compiler can only carry forward what the importer recorded. _attribution() in the detection engine is built from whatever the block actually holds, so the alert reads Translated from SigmaHQ/sigma (rules/...), licensed under DRL-1.1 rather than naming an author called "" — the sentence is short rather than false, which is the right behaviour for a gap but is not the same as closing it.

Closing it needs a re-import: the field has to be captured at import time and the corpus recompiled. It is reported here rather than left implicit because a licence obligation that is partly met is not met, and a reader comparing this corpus against DRL-1.1 should not have to discover that by reading the JSON.