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

Update Appendix-G--Securing-Administrators-Groups-in-Active-Directory.md #8001

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Air-Git
Copy link

@Air-Git Air-Git commented Dec 7, 2024

The document says "There should be no day-to-day user accounts in the Administrators group with the exception of the Built-in Administrator account for the domain". But it also says "Additionally, DAs and EAs inherit a number of their rights and permissions by virtue of their default membership in the Administrators group. Default group nesting for privileged groups in Active Directory should not be modified".

This is unclear and possibly contradictory. The term "day-to-day user accounts" is not defined or standard. Does it include the Administrator account and the DA and EA groups? If it does, then the part about not modifying nesting groups is contradictory. If it does not, then the Administrator account cannot be excluded, because it is not included.

It is not clear whether the intention is to remove ALL members, with the possible exception of the Administrators account; or to remove ALL members EXCEPT the default members.

The document says "There should be no day-to-day user accounts in the Administrators group with the exception of the Built-in Administrator account for the domain". But it also says "Additionally, DAs and EAs inherit a number of their rights and permissions by virtue of their default membership in the Administrators group. Default group nesting for privileged groups in Active Directory should not be modified".

This is unclear and possibly contradictory. The term "day-to-day user accounts" is not defined or standard. Does it include the Administrator account and the DA and EA groups? If it does, then the part about not modifying nesting groups is contradictory. If it does not, then the Administrator account cannot be excluded, because it is not included.

It is not clear whether the intention is to remove ALL members, with the possible exception of the Administrators account; or to remove ALL members EXCEPT the default members.
Copy link
Contributor

@Air-Git : Thanks for your contribution! The author(s) have been notified to review your proposed change. @iainfoulds

Copy link
Contributor

Learn Build status updates of commit f91819a:

✅ Validation status: passed

File Status Preview URL Details
WindowsServerDocs/identity/ad-ds/plan/security-best-practices/Appendix-G--Securing-Administrators-Groups-in-Active-Directory.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Air-Git
Copy link
Author

Air-Git commented Dec 7, 2024

Additionally, the text and screenshot refer to removing all members. I have not proposed a change to that text because it is not clear what the recommendation is. My own reading is that "no day-to-day user accounts" means no custom (non-default) accounts and, by extension, any groups of them. But it could also mean "no accounts or groups at all, normally" i.e. except in build or disaster recovery situations.

It's the same with Appendix F.

@ttorble
Copy link
Contributor

ttorble commented Dec 9, 2024

#assign: @robinharwood, @Xelu86

@robinharwood @Xelu86

Can you review the proposed changes?

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants