Add SSH brute force detection rule #5792
Draft
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 adds a new Sigma rule for detecting repeated SSH authentication failures on Linux systems.
The rule identifies potential brute-force activity based on multiple failed login attempts from the same source.
Changelog
new: Add SSH Multiple Authentication Failures detection rule
Example Log Event
{
"timestamp": "2025-12-03T10:15:22Z",
"host": "ubuntu-server",
"process": "sshd",
"event": "Failed password",
"source_ip": "192.168.1.50",
"username": "root"
}
Fixed Issues
N/A – new rule, no fixes included.
SigmaHQ Rule Creation Conventions
This rule follows SigmaHQ conventions, uses valid ATT&CK tags, modern condition syntax, and a UUID-based rule identifier.