SpecterOps / SpecterOps/AzureHound
AdministrativeUnits Not showing within Azure Role for Role
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 961
- Forks
- 148
- Avg merge
- 22h 26m
- Merged PRs (30d)
- 4
Description
Bloodhound entry related to the Azure Role:
{"kind":"AZRole","data":{"id":"729827e3-9c14-49f7-bb1b-9608f156bbb8","description":"Can reset passwords for non-administrators and Helpdesk Administrators.","displayName":"Helpdesk Administrator","isBuiltIn":true,"isEnabled":true,"resourceScopes":["/"],"rolePermissions":[{"allowedResourceActions":["microsoft.azure.serviceHealth/allEntities/allTasks","microsoft.azure.supportTickets/allEntities/allTasks","microsoft.directory/bitlockerKeys/key/read","microsoft.directory/deviceLocalCredentials/standard/read","microsoft.directory/users/invalidateAllRefreshTokens","microsoft.directory/users/password/update","microsoft.office365.serviceHealth/allEntities/allTasks","microsoft.office365.supportTickets/allEntities/allTasks","microsoft.office365.webPortal/allEntities/standard/read"]}],"templateId":"729827e3-9c14-49f7-bb1b-9608f156bbb8","version":"1","tenantId":"2e0d024c-5e44-47f7-b4b8-....","tenantName":"tenant name"}}
The AdministrativeUnit entry is not showing within Bloodhound, and wanted to see if there's a way to actually have this enumerated.
Contributor guide
No contributing guide indexed for this repository
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
No implementation files or tests are identified in the issue. Start with the supplied AZRole entry and investigate how AdministrativeUnit data is represented and expected to appear in BloodHound. Done means AdministrativeUnit entries are enumerated and visible in the relevant BloodHound view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- authorization, cloud, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100