Skip to content

feat: labeled dual-signal SnortML+signature and Splunk-notable triage corpus - #389

Open
AAH20 wants to merge 2 commits into
Cisco-Talos:mainfrom
AAH20:feat/dual-signal-triage-corpus
Open

feat: labeled dual-signal SnortML+signature and Splunk-notable triage corpus#389
AAH20 wants to merge 2 commits into
Cisco-Talos:mainfrom
AAH20:feat/dual-signal-triage-corpus

Conversation

@AAH20

@AAH20 AAH20 commented Aug 16, 2026

Copy link
Copy Markdown

Summary

Adds a labeled dual-signal triage corpus for SnortML-style (GID:411) scores,
classic signature alerts, and Splunk-notable-shaped events.

Why

SnortML documentation and agentic-SOC practice require that ML probability
not be treated as equivalent to a signature true positive. Training corpora
that flatten alerts into a single "bad" label teach the wrong automation habit
and inflate false containment and agent compute burn.

What's included

  • Labeled events: signature-only, ML-only high, corroborated, ML-low, Splunk notables
  • Disposition labels suitable for T1-T3 automation evaluation
  • Validator that rejects corpora marking ML-only high as auto_contain or fix_now
  • Unit tests and README scenario entry

Out of scope

Engine parser CVEs, which belong in Cisco PSIRT rather than this PR.

Production application

Aegis Decision Fabric exercises this corpus for composite-confidence evaluation,
gated remediation, and FP/TP feedback:
https://github.com/AAH20/aegis-decision-fabric

Secure Firewall and Splunk teams can review the fixed-scope implementation offer
at https://a2zsoc.com/consultation.

Test plan

  • python scripts/validate_dual_signal_triage_corpus.py scenarios/dual-signal-triage-corpus/corpus/labeled_events.json
  • pytest tests/unit/test_dual_signal_triage_corpus.py --no-cov
  • Maintainer CI green on this branch

… corpus

Add a disposition-labeled eval pack that encodes ML ≠ signature TP, with a
validator that rejects ML-only high auto-contain/fix_now labels for agentic SOC training.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant