New Atomic - T1654 Log Enumeration #2584
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
clr2of8
approved these changes
Nov 7, 2023
There was a problem hiding this comment.
Excellent! Thank you for your first-time contribution. Keep it up! Don't forget to claim your free Atomic Red Team t-shirt
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.
Details:
New Mitre technique for log enumeration using the Powershell Get-EventLog. This technique was observed in a TheDFIRReport case [https://thedfirreport.com/2023/04/03/malicious-iso-file-leads-to-domain-wide-ransomware/] where the threat actor enumerated the Windows Security audit log to determine user accounts and associated IPv4 addresses.
Testing:
Local testing, YAML file generated via Atomic GUI. The test generates a staging file of matching Windows events based on the keyword 'SYSTEM'.
Associated Issues:
NA