-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[New Rule] Potential Forced Authentication - SMB Named Pipes #3916
base: main
Are you sure you want to change the base?
Conversation
Rule: New - GuidelinesThese guidelines serve as a reminder set of considerations when proposing a new rule. Documentation and Context
Rule Metadata Checks
New BBR Rules
Testing and Validation
|
sequence by source.ip, user.name with maxspan=1s | ||
[authentication where host.os.type == "windows" and event.action == "logged-in" and | ||
winlog.event_data.AuthenticationPackageName : "NTLM" and winlog.event_data.SubjectUserSid == "S-1-0-0"] | ||
[file where host.os.type == "windows" and event.code == "5145" and file.name : ("Spoolss", "netdfs", "lsarpc", "lsass", "netlogon", "samr", "efsrpc", "FssagentRpc")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had some unrelated hits in the lsarpc
pipe, will measure the noise as this one is used in EFSRPC related forced auth, and will remove it and create a BBR if the volume is too high
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lsarpc, lsass, spoolss, netlogon and samr are all very frequent and risk to be very noisy, I would suggest to use a new term rule type and limit to the 5145 event (no need for a sequence with logon event) and use 3 terms user.name
, source.ip
, host.id
and file.name limited to spoolss, "efsrpc", "FssagentRpc" and "netdfs".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I'll work on that
rules/windows/credential_access_forced_authentication_pipes.toml
Outdated
Show resolved
Hide resolved
references = [ | ||
"https://github.com/p0dalirius/windows-coerced-authentication-methods", | ||
"https://www.thehacker.recipes/a-d/movement/mitm-and-coerced-authentications", | ||
"https://attack.mitre.org/techniques/T1187/", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need MITRE URL as ref if mapped already?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Issue
Part of #3544
Summary
Identifies a potential forced authentication using related SMB named pipes. Attackers may attempt to force targets to authenticate to a host controlled by them to capture hashes or enable relay attacks.
Data
Events/Sample Data