Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure - Administrative Units are ignored, leading to false positives in edges #677

Open
EnriqueHernandezL opened this issue Jun 20, 2023 · 0 comments
Labels

Comments

@EnriqueHernandezL
Copy link

Describe the bug
A few roles, like "Helpdesk Administrator" can be scoped to "Administrative Units", so that in this example, only other users in that administrative unit can get their password reset by the Helpdesk Admin in question. Bloodhound ignores this, which leads to false positives in PasswordReset edges.

To Reproduce
Steps to reproduce the behavior:

  1. Setup an administrative units "AU1".
  2. Give a user user1 "Helpdesk Administrator" scoped to the "AU1" AU.
  3. Create a second user user2 which is not in "AU1".
  4. Bloodhound thinks that user1 owns user2 through PasswordReset.

Expected behavior
Bloodhound should consider that AzureAD roles can be scoped to Administrative Units.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant