memdocs icon indicating copy to clipboard operation
memdocs copied to clipboard

principal of least privilege

Open poortom1004 opened this issue 3 years ago • 2 comments
trafficstars

There's no way that Full Control is required for autopilot to hybrid join a computer to AD. I'm still surprised that we see principal of least privilege being violated in today's world. And yet there's no "doc" from Microsoft on how to delegate the domain join privilege using the principal of least privilege.

https://docs.microsoft.com/en-us/answers/questions/764328/delegate-34domain-join-only34-permission-to-a-stan.html Take a look at answer proposed by "GaryReynolds". This answer uses the principal of least privilege for domain-joining a computer.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

poortom1004 avatar Jul 26 '22 20:07 poortom1004

the list of properties that you need to write to are:

  • displayName
  • samAccountName
  • userAccountControl
  • distinguishedName (to support renames and moves, but not needed for Autopilot)
  • cn (to support renames and moves, but not needed for Autopilot)

The list of extended rights that you need are:

  • Reset password (for joining to an existing object, but not needed for Autopilot)
  • Validated write to dns host name
  • Validated write to service principal name

And you still need to delegate the right to create computer objects (I doubt that Autopilot needs the right to delete computer objects).

Anything beyond this list is not related to domain joining computers, like updating the description or any other attributes is associated to managing computer objects, which is a separate task from domain joining. So I'd leave any other attributes out of the delegation for a service account which only has a job of domain-joining computers.

poortom1004 avatar Jul 26 '22 21:07 poortom1004

@dougeby Please help us in resolving this issue. Thanks

yogkumgit avatar Aug 01 '22 13:08 yogkumgit