Split faulty APT29 Emulation Plan into 4 separate emulation plans #120
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
…uted; Rename 16.C to 16.C-16.D
|
Added two more fixes for APT29 Day2 Scenario. I committed the changes to the same PR since they fix errors that persist through the splitting of the faulty APT29 emulation plan. Problem 1: The payload Problem 2: Step 16.C also included commands for step 16.D (see emulation plan) |
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.
This pull request should fix the faulty APT29 Emulation Plan by splitting it into four separate emulation plans: APT29-Day1.A, APT29-Day1.B, APT29-Day2 and APT3. The splitting was performed by looking at the respective archived adversary profiles. The emulation plan for APT3 was moved to a new directory (with no further information about APT3).
The underlying issue and its solution was described in much detail in #118. For more information see the linked issue and feel free to ask me.
Changes:
APT29.yamlNote: Even though the contribution guidelines state that pull request should target the
developbranch, this pull request targets the main branch since all other recent pull request did so as well and the develop branch has not been touched for over a year. Sorry if this is wrong.