Update rule regarding other named pipe #1505
Merged
Conversation
This file contains 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
This was referenced May 27, 2021
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.
Hi,
I added three more named pipe to this rule. According Cobalt Strike documentation (https://blog.cobaltstrike.com/2021/02/09/learn-pipe-fitting-for-all-of-your-offense-projects/) and some test especial \.\pipe\postex_ is use during e.g. fork&run post-exploitation jobs. And status is use by command jump psexec_psh (lateral movement).
I also changed naming convention in "selection" section. I think looking for \msagent_ is a valid detection that's why I would suggest to put it also to condition section.
If you need some other info, proof - let me know. I tested this update with powershell generated by sigmac
Get-WinEvent -LogName "Microsoft-Windows-Sysmon/Operational"| where {(($_.ID -eq "17" -or $_.ID -eq "18") -and (($_.message -match "PipeName.*\\MSSE-.*" -and $_.message -match "PipeName.*.*-server") -or $_.message -match "PipeName.*\\postex_.*" -or $_.message -match "PipeName.*\\postex_ssh_.*" -or $_.message -match "PipeName.*\\status_.*" -or $_.message -match "PipeName.*\\msagent_.*")) } | select TimeCreated,Id,RecordId,ProcessId,MachineName,Message-LogName "Microsoft-Windows-Sysmon/Operational"|was added manually.And one more thing - for consideration if the rule should change its status to test.