Replace legacy rule with a new one - #6241
Open
norbert791 wants to merge 2 commits into
Open
Conversation
github-actions
Bot
added
Rules
Review Needed
norbert791
force-pushed
the
norbert791/replace-rule
branch
from
August 18, 2026 17:09
8ef9e73 to
804058b
Compare
norbert791
marked this pull request as ready for review
August 18, 2026 17:09
norbert791
changed the title
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.
Summary of the Pull Request
This PR deprecates a rule that matched uses of
Test-NetConnectionpowershell command. It also introduces new rule meant to provide improved coverage for the retired rule. It includes additional commands, including .Net classes. It has broader scope and does not have explicit filter, since it introduced unexpected false negatives. The chosen severity for the new rule is 'low'.The CLI tools selection is limited, but includes what's likely available on any windows host and can be easliy used to probe TCP ports.
Changelog
new: Port Probing Via PowerShell Network Cmdlets Or .NET Sockets
remove: Testing Usage of Uncommonly Used Port - deprecated in favour of 0f0a89f7-0fae-48f6-bb47-26c7b9e3c5bd
Example Log Event
Fixed Issues
Closes #6132
SigmaHQ Rule Creation Conventions