Add packaged OCSF network detections - #172
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
mavam
marked this pull request as draft
August 7, 2026 21:00
mavam
marked this pull request as ready for review
August 7, 2026 21:10
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Add configurable UDOs for scan fan-out, beacon cadence, long connections, and outbound volume bursts. Emit OCSF Detection Findings and cover every operator with schema-checked fixture tests. Assisted-by: gpt-5.6-sol (pi)
Assisted-by: gpt-5.6-sol (pi)
Switch beacon_cadence and outbound_volume_burst from traffic.bytes to traffic.bytes_out. The bidirectional total differs across sources (the Zeek and Suricata mappings sum both directions), whereas bytes_out consistently carries the source-to-destination count and matches the originator-bytes signal that RITA scores.
Move the four detectors into tenzir::detect::network, mirroring how detection catalogs organize by data domain, so future detector families over other OCSF classes get their own namespace without breaking deployed pipelines. Stamp each finding with MITRE ATT&CK tactic and technique mappings in finding_info.attacks and add a version to the analytic identity.
mavam
force-pushed
the
mkt-64-packaged-detections
branch
from
August 7, 2026 21:17
504ef1d to
8a19cb5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔍 Problem
The companion network-detection article provides runnable TQL, but users still have to copy, adapt, and maintain each detector themselves.
🛠️ Solution
tenzir::detect::*UDOs for scan fan-out, beacon cadence, long connections, and outbound volume bursts.🧪 Validation
uvx tenzir-test . --match 'tenzir/*'./.github/scripts/check-tql-syntax.shcd tenzir/changelog && uvx tenzir-ship validateThe complete local repository suite has one unrelated baseline failure because a Microsoft assertion embeds the worktree-relative path. The touched-package test selection passes locally.
💬 Review
Please focus on the detector defaults, UDO parameter surfaces, and Detection Finding shapes.
CI remains blocked until the published Tenzir packages include the
📚 Content PR: tenzir/content#202deltas,mad, andskewnessfunctions merged in tenzir/mono#70.🎫 References MKT-64
📎 Related: tenzir/mono#70
⛓️ Depends on #173 (NetFlow traffic.bytes_out mapping)