This repository has been archived by the owner on Sep 2, 2022. It is now read-only.
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.
I added support for collecting local membership of the group "Remote Management Users", which can be used to define users that can access a target machine using PowerShell remoting.
For example, I am pushing the group "Domain Users" in the local group "Remote Management Users", as it is possible to see in the screenshot below from my test domain:
and, as you can see, the user RANCARANI is able to
Enter-PSSession
in the domain controller:The result within BloodHound is the following:
I added the edge
CanPSRemote
.I will create the pull request for the Electron app as soon as I can.