Skip to main content

Public Detection Rule Source Inventory

This document is a candidate-source inventory for Phase R5.2 sampling design. It does not create the corpus and does not authorize execution-phase collection. Until PROTOCOL.md Section 9 reads LOCKED, commands in this document are collection recipes only.

Recommended local storage root for later collection:

export BB_RULES_ROOT="$HOME/brittlebench-rule-sources/$(date -u +%Y%m%d)"
mkdir -p "$BB_RULES_ROOT"

Do not store downloaded rules in this repository before protocol lock. If temporary local storage is ever needed inside the checkout, use an ignored directory such as local-rule-sources/.

Inclusion Notes

  • Confirmatory Phase 1 candidate means directly aligned with the locked methodology: native YARA, native Elastic, or Sigma that can be translated to Elastic with high fidelity.
  • Secondary candidate means valuable for future expansion or exploratory comparison, but not part of confirmatory Phase 1 unless a later locked protocol amendment admits it.
  • Discovery index means useful for finding more sources, but not itself a rule corpus.
  • All sources require license review, duplicate detection, snapshot date recording, and exact inclusion/exclusion rules in PROTOCOL.md Section 5.2 before collection.

Candidate Sources

PrioritySourceRule family / formatPublic sourceLater collection methodCandidate local targetNotes for R5.2
Confirmatory Phase 1 candidateSigmaHQ main rule repositorySigma YAMLsourcegit clone --depth 1 https://github.com/SigmaHQ/sigma.git "$BB_RULES_ROOT/sigmahq-sigma"$BB_RULES_ROOT/sigmahq-sigmaStrong fit only for high-fidelity Sigma-to-Elastic translations. Record release tag or commit SHA.
Confirmatory Phase 1 candidateSigmaHQ releasesSigma YAML release packagessourcecurl -L -o "$BB_RULES_ROOT/sigmahq-sigma.tar.gz" https://github.com/SigmaHQ/sigma/archive/refs/heads/master.tar.gz$BB_RULES_ROOT/sigmahq-sigma.tar.gzPrefer release artifact or pinned commit if a release exists near snapshot date.
Confirmatory Phase 1 candidateElastic Detection RulesElastic Security detection rulessourcegit clone --depth 1 https://github.com/elastic/detection-rules.git "$BB_RULES_ROOT/elastic-detection-rules"$BB_RULES_ROOT/elastic-detection-rulesStrong fit. Focus on native rules; exclude deprecated, building-block, and promotion wrapper rules unless separate exploratory strata are defined.
Secondary candidateSplunk Security ContentSplunk detections / analytic storiessourcegit clone --depth 1 https://github.com/splunk/security_content.git "$BB_RULES_ROOT/splunk-security-content"$BB_RULES_ROOT/splunk-security-contentFuture/exploratory. SPL evaluator semantics are outside confirmatory Phase 1.
Confirmatory Phase 1 candidateYara-Rules community repositoryYARAsourcegit clone --depth 1 https://github.com/Yara-Rules/rules.git "$BB_RULES_ROOT/yara-rules"$BB_RULES_ROOT/yara-rulesStrong fit for public YARA. Requires module support and duplicate handling.
Confirmatory Phase 1 candidateNeo23x0 signature-baseYARA and IOC signaturessourcegit clone --depth 1 https://github.com/Neo23x0/signature-base.git "$BB_RULES_ROOT/neo23x0-signature-base"$BB_RULES_ROOT/neo23x0-signature-baseStrong YARA source. Exclude non-YARA IOC lists from confirmatory Phase 1.
Confirmatory Phase 1 candidateElastic Protections ArtifactsYARA and endpoint behavior rulessourcegit clone --depth 1 https://github.com/elastic/protections-artifacts.git "$BB_RULES_ROOT/elastic-protections-artifacts"$BB_RULES_ROOT/elastic-protections-artifactsConfirmatory only for native YARA artifacts. Endpoint behavior rules remain exploratory.
Confirmatory Phase 1 candidateReversingLabs YARA RulesYARAsourcegit clone --depth 1 https://github.com/reversinglabs/reversinglabs-yara-rules.git "$BB_RULES_ROOT/reversinglabs-yara-rules"$BB_RULES_ROOT/reversinglabs-yara-rulesPublic vendor-maintained YARA. Review prerequisites and supported YARA modules.
Confirmatory Phase 1 candidateInQuest YARA RulesYARAsourcegit clone --depth 1 https://github.com/InQuest/yara-rules.git "$BB_RULES_ROOT/inquest-yara-rules"$BB_RULES_ROOT/inquest-yara-rulesPublic YARA corpus. Verify current maintenance and license before inclusion.
Confirmatory Phase 1 candidateStratosphere IPS YARA RulesYARAsourcegit clone --depth 1 https://github.com/stratosphereips/yara-rules.git "$BB_RULES_ROOT/stratosphere-yara-rules"$BB_RULES_ROOT/stratosphere-yara-rulesSmaller public corpus; useful if sampling includes curated YARA repositories.
Confirmatory Phase 1 candidateMalpedia Signator RulesYARAsourcegit clone --depth 1 https://github.com/malpedia/signator-rules.git "$BB_RULES_ROOT/malpedia-signator-rules"$BB_RULES_ROOT/malpedia-signator-rulesAuto-generated YARA rules. Treat generated rules separately from human-authored rules.
Secondary candidateMicrosoft Sentinel public repositoryKQL analytics rules and hunting queriessourcegit clone --depth 1 https://github.com/Azure/Azure-Sentinel.git "$BB_RULES_ROOT/azure-sentinel"$BB_RULES_ROOT/azure-sentinelLarge public source. Include only if KQL/Sentinel rules are added to scope; likely paths: Detections/, Solutions/*/Analytic Rules/, Hunting Queries/.
Secondary candidateGoogle SecOps / Chronicle detection rulesYARA-Lsourcegit clone --depth 1 https://github.com/chronicle/detection-rules.git "$BB_RULES_ROOT/chronicle-detection-rules"$BB_RULES_ROOT/chronicle-detection-rulesPublic YARA-L examples. Needs separate evaluator design and may be out of initial multi-format scope.
Secondary candidateGoogle Cloud Community Security AnalyticsGCP audit and threat queriessourcegit clone --depth 1 https://github.com/GoogleCloudPlatform/security-analytics.git "$BB_RULES_ROOT/google-security-analytics"$BB_RULES_ROOT/google-security-analyticsGood cloud-detection source. Needs format mapping and ground-truth strategy.
Secondary candidatePanther AnalysisPython/YAML detection-as-codesourcegit clone --depth 1 https://github.com/panther-labs/panther-analysis.git "$BB_RULES_ROOT/panther-analysis"$BB_RULES_ROOT/panther-analysisPublic managed-detection content. Requires Python-rule execution model; likely future expansion.
Secondary candidateFalco RulesFalco YAML runtime/container rulessourcegit clone --depth 1 https://github.com/falcosecurity/rules.git "$BB_RULES_ROOT/falco-rules"$BB_RULES_ROOT/falco-rulesPublic cloud-native runtime rules. Requires syscall/container event model, likely separate from initial SIEM/YARA scope.
Secondary candidateWazuh rulesetWazuh / OSSEC XML rulessourcegit clone --depth 1 https://github.com/wazuh/wazuh-ruleset.git "$BB_RULES_ROOT/wazuh-ruleset"$BB_RULES_ROOT/wazuh-rulesetPublic XML rules and decoders. Verify whether this or wazuh/wazuh is the authoritative current source at snapshot time.
Secondary candidateWazuh main repository rulesetWazuh / OSSEC XML rulessourcegit clone --depth 1 https://github.com/wazuh/wazuh.git "$BB_RULES_ROOT/wazuh-main"$BB_RULES_ROOT/wazuh-mainUse if ruleset is maintained in the main repository. Include ruleset/rules/ only after authority check.
Secondary candidateOpenSearch Security AnalyticsSigma-derived prepackaged rulessourcegit clone --depth 1 https://github.com/opensearch-project/security-analytics.git "$BB_RULES_ROOT/opensearch-security-analytics"$BB_RULES_ROOT/opensearch-security-analyticsUses prepackaged open-source Sigma rules. Avoid double-counting SigmaHQ-derived rules.
Secondary candidateEmerging Threats Open for SuricataSuricata network IDS rulessourcecurl -L -o "$BB_RULES_ROOT/emerging-threats-open-suricata.tar.gz" https://rules.emergingthreats.net/open/suricata/emerging.rules.tar.gz$BB_RULES_ROOT/emerging-threats-open-suricata.tar.gzPublic network IDS rules. Requires packet/flow ground truth and separate evaluator; likely future scope.
Secondary candidateSnort Community RulesSnort IDS rulessourcecurl -L -o "$BB_RULES_ROOT/snort-community-rules.tar.gz" https://www.snort.org/downloads/community/community-rules.tar.gz$BB_RULES_ROOT/snort-community-rules.tar.gzFree community rules. Requires license review and network traffic evaluation model.
Discovery indexInQuest Awesome YARACurated YARA source indexsourcegit clone --depth 1 https://github.com/InQuest/awesome-yara.git "$BB_RULES_ROOT/awesome-yara-index"$BB_RULES_ROOT/awesome-yara-indexNot a corpus by itself. Use to discover additional YARA repos, then vet each source individually.
Discovery indexGitHub topic: yara-rulesPublic YARA repository discoverysourceManual review or GitHub API search after R5.2N/AUseful for expansion, but GitHub topic search is unstable and must not define the final sampling frame alone.
Discovery indexMicrosoft Sentinel Analytics Rules catalogCatalog over Azure-Sentinel rulessourceManual review; source URLs point back to Azure/Azure-SentinelN/AUseful metadata browser, not a canonical source. Prefer cloning Azure/Azure-Sentinel for actual data.
Discovery indexAwesome Threat Detection / Hunting listsCurated detection-source indexsourceManual review after R5.2N/ADiscovery only. Every linked source needs separate license, format, and maintenance review.

Collection Metadata Required Later

For every source admitted into the final sampling frame, record:

  • Source name and canonical URL.
  • Retrieval method: git clone, GitHub archive download, release download, curl/wget, or manual copy.
  • Snapshot timestamp in UTC.
  • Git commit SHA, release tag, or archive checksum.
  • License and redistribution constraints.
  • Included paths and excluded paths.
  • Rule count before and after parsing, deduplication, and eligibility filtering.
  • Whether the source is human-authored, vendor-authored, community-authored, generated, aggregated, or mixed.
  • Whether rules are primary detections, hunting queries, building blocks, policies, decoders, correlation rules, or metadata.

Post-R5 Scope Notes

  • Microsoft Sentinel KQL, Chronicle YARA-L, Panther Python rules, Falco YAML, Wazuh XML, Suricata rules, Snort rules, and Splunk SPL are future or exploratory sources, not confirmatory Phase 1 inputs.
  • Whether generated YARA corpora such as Malpedia Signator Rules are analyzed separately from human-authored rule corpora.
  • Whether derived or mirrored Sigma corpora are excluded to avoid double-counting SigmaHQ content.
  • Whether hunting queries are included, excluded, or analyzed separately from alerting detections.
  • Whether network IDS rules are compatible with the planned mutation model, which currently emphasizes commands, scripts, files, registry events, process behavior, and malware/file artifacts.