Add dual_signal_containment_gate custom function - #239
Open
AAH20 wants to merge 1 commit into
Open
Conversation
Deny auto-contain when the event is SnortML GID 411 / ML-only / EVE-high without a classic signature, so playbooks do not treat ML confidence as a signature true positive. Co-authored-by: Cursor <cursoragent@cursor.com>
6 tasks
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
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.
Summary
Adds a reusable community custom function so Splunk SOAR playbooks can deny auto-contain when an event is ML-only.
Community
block ip/risk_notable_block_indicatorspaths currently flatten SnortML probability into a signature true positive. False containment is an outage and a change ticket.Hard rule: ML confidence ≠ signature true positive.
This follows the same contribution shape as
ip_classify(#238) andgenerate_password(#237): a Python 3.13 / platform 8.6 custom function, not a fork of every historicalblock_indicatorsbranch.Behavior
Call
community/dual_signal_containment_gatewith notable/container text plus optionalgenerator_id,classification, andeve_threat_confidence. Filter beforeblock ip:dispositionallow_auto_containml_onlyfalseis_ml_only, or EVE ≥ 80 without a classic signaturesignaturetruecorroboratedtrueunknownfalseGID 411 plus a leftover
class_descis still ML-only (that field is not a classic signature TP).Filter example:
allow_auto_contain == "false"→ prompt or stop; do not launchblock ip.Wiring
Intended consumers (no edits in this PR):
risk_notable_block_indicatorsand taggedblock, risk_notablechild playbooksblock ipactions on Cisco Secure Firewall notablesPass
container.name+container.description(and CEF GeneratorID / classification / EVE when present).Compounds
Optional production Gate/Prove consumer (paid Continuous Trust, not unpaid R&D): https://github.com/AAH20/aegis-decision-fabric · https://a2zsoc.com/consultation
Test plan
is_ml_only/ EVE 92 →ml_only+ denyattempted-admin→signature+ allowcorroborated+ allowattempted-adminclass_desc → stillml_onlyunknown+ deny--disable=W,C,R,I,E0401) 10/10custom_functions/*.pyblock ipon a SnortML notableMade with Cursor