T1021.006 - Change default target for MMC remote exec to localhost #1218
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
…mote execution through MMC
clr2of8
approved these changes
Sep 15, 2020
MDF636162
pushed a commit
to MDF636162/atomic-red-team
that referenced
this pull request
Nov 8, 2020
…mote execution through MMC (redcanaryco#1218) Co-authored-by: Didier Cambefort <[email protected]> Co-authored-by: Carrie Roberts <[email protected]>
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:
The remote execution through MMC (which btw should probably not be in this technique, as suggested in #1042 ) has a default value of
computer1for the execution target. Defaulting tolocalhostso it may run without additional argument. The detection is likely based upon the process tree anyway.Testing:
Ran locally and remotely, comparing artefacts in Sysmon and Security event logs to see what may be missed be running it locally (4624/3, that's all)
Associated Issues: