AdministrativeUnits Not showing within Azure Role for Role
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, go
- Domain
- authorization, cloud, security
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.
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.
- Dominant language
- Go
- Stars
- 968
- Forks
- 147
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from SpecterOps/AzureHound
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SpecterOps/AzureHound#128 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
SpecterOps/AzureHound#197 ·
-
Improvement: Add a Feature to Allow Users to Specify Custom User AgentsPossibly taken @ChrisJr404 claimed this 157 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 45/100
SpecterOps/AzureHound#135 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
SpecterOps/AzureHound#112 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
SpecterOps/AzureHound#91 ·
All issues in SpecterOps/AzureHound
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug good first issue load-balancing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ktrubilo9/edge-proxy#53 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug needs triage receiver/dockerstats
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
open-telemetry/opentelemetry-collector-contrib#51948 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LanternOps/breeze#8353 ·
Maintainers usually reply within 1 day