Open
Conversation
Collaborator
swachchhanda000
left a comment
There was a problem hiding this comment.
Hi @davidljohnson,
Thanks for the PR.
Before we dive in, I have some questions. How do we know that CasPol.exe doesn't make any network connections in general? In Windows, unexpected/weird things happen, so we cannot just assume things. For example if it makes some connections locally, it's going to create tons of false positives, which is very bad for a high-level rule.
Do you have any supporting resources you can share to confirm that's not the case? In fact, if you could look at the telemetry of some enterprise environment and test whether it creates some false positives, that would be helpful.
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 of the Pull Request
New rule to detect network connections initiated by CasPol.exe (.NET Framework CAS Policy Manager). CasPol.exe has no legitimate reason to make network connections and is abused as a process hollowing target by malware including XWorm.
There are no existing SigmaHQ rules covering CasPol.exe. This follows the established pattern of per-binary network connection rules (similar to the existing rundll32, wuauclt, and dllhost network connection rules).
Validated via attack emulation on Windows 10 with Sysmon v15.15. The emulation was based on techniques documented in a real XWorm v5.6 LATAM campaign analyzed by ANY.RUN.
Changelog
new: CasPol.EXE Initiated Network Connection
Example Log Event
Fixed Issues
N/A
SigmaHQ Rule Creation Conventions