Add simulated mitigations functionality #326
Open
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
By choosing a mitigation in the new mitigation menu, you can delete edges in the current mitigation. Then, doing path finding or using the pre built queries will disregard this edge. This can allow you to check what happens if you remove some edges in your environment, for instance group memberships.
|
Very good idea! What I do currently is that I backup the db and delete edges just to see, then restore. But that would be way more convenient! |
|
Now also remembering how many mitigations has been added. :) |
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.
By choosing a mitigation in the new mitigation menu, you can delete edges in the current mitigation. Then, doing path finding or using the pre built queries will disregard this edge. This can allow you to check what happens if you remove some edges in your environment, for instance group memberships.
This functionality makes the Adversary Resilience Methodology (https://posts.specterops.io/introducing-the-adversary-resilience-methodology-part-one-e38e06ffd604) easier to perform, as you no longer need to perform destructive actions on your database in order to find what a change does in your environment.
I'm not sure if "Mitigations" is a descriptive enough term, but I couldn't think of anything else. Open to suggestions here.
Things missing: