mandiant / mandiant/VM-Packages
split sysinternals (commando-vm vs flare-vm shortcuts)
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 246
- Forks
- 98
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 7
Description
### Details
Since https://github.com/mandiant/VM-Packages/commit/f55f6f51e3aea53d1ec82f42d76bc4cdee45b930 sysinternals is creating a shortcut for ADExplorer in Reconnaissance. Do we want this tool in FLARE-VM? If not, how do we do it to install different shortcuts for flare-vm and command-vm? Ideas:
- introducing flare.sysinsternals.vm and commando.sysinternals.vm packages that require sysinternals.vm and create the specific shortcuts
- install different shortcuts depending on an env variable (for commando-vm and flare-vm) in sysinternals.vm
@mandiant/vms opinions?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the sysinternals.vm package and the referenced VM-Packages commit to understand how the ADExplorer shortcut is created. Compare the shortcut requirements for FLARE-VM and Commando VM, then establish a package or environment-based approach whose result is the correct shortcut set for each environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100