# Privileged groups with members count should be investigated

Privileged groups with members require continuous monitoring as they provide administrative access:

Source: https://maester.dev/docs/tests/AD-GMC-10

<!-- This file is generated by website/scripts/generate-test-docs.mjs. Do not edit manually. -->

<div class="test-byline"><div class="test-byline-avatars"><a class="test-byline-avatar test-byline-avatar--author" href="/contributors/soulemike" title="Michael Soule · Original author"><img src="https://github.com/soulemike.png" alt="Michael Soule" width="28" height="28" loading="lazy" decoding="async" /></a></div><div class="test-byline-meta"><span class="test-byline-text">Contributed by <a href="/contributors/soulemike">Michael Soule</a></span><a class="test-byline-link" href="/contributors">All contributors →</a></div></div>

<p class="test-part">Part of <a href="/docs/tests/ad">Active Directory</a> · Active Directory · Groups · <a href="/docs/tests">All checks</a></p>

```powershell title="Run this check"
Invoke-Maester -TestId AD-GMC-10
```

## Overview

Privileged groups with members require continuous monitoring as they provide administrative access:

- **Privileged access**: Members have elevated permissions in the domain
- **Attack surface**: More members increases the risk of credential compromise
- **Compliance requirements**: Most regulations require monitoring of privileged access
- **Change detection**: New memberships may indicate unauthorized elevation
- **Access review**: Supports regular attestation of privileged access

Well-known privileged groups include:
- **Domain Admins (RID 512)**: Full control of the domain
- **Enterprise Admins (RID 519)**: Full control of the forest
- **Schema Admins (RID 518)**: Can modify the Active Directory schema
- **Account Operators (RID 548)**: Can manage user and group accounts
- **Server Operators (RID 549)**: Can manage domain servers
- **Print Operators (RID 550)**: Can manage print queues
- **Backup Operators (RID 551)**: Can bypass file system security for backup

#### Control Type

**Operational**

#### Security Recommendation

Implement strict controls for privileged groups:
- Minimize membership in Domain Admins and Enterprise Admins
- Use Privileged Access Workstations (PAWs) for privileged accounts
- Implement just-in-time administration where possible
- Monitor and alert on privileged group changes
- Conduct regular access reviews of privileged group membership
- Document business justifications for all privileged access

#### How the Test Works

This test identifies privileged groups (those with adminCount = 1 or well-known RIDs) and counts:
- Total privileged groups
- Privileged groups with members
- Privileged groups without members
- Well-known privileged groups with members

#### Related Tests

- `Test-MtAdGroupPrivilegedWithMembersDetails` - Lists privileged groups with member details
- `Test-MtAdGroupEmptyNonPrivilegedCount` - Reviews non-privileged empty groups

## Details

<details>
<summary>Every attribute of this check</summary>

| Field | Value |
| --- | --- |
| Test ID | AD-GMC-10 |
| Severity | Info |
| Suite | Active Directory |
| Product | Active Directory |
| Feature | Groups |
| Area | Privileged access |
| Resource type | Group |
| MITRE ATT&CK | T1098.007 Additional Local or Domain Groups, T1078.002 Domain Accounts |
| PowerShell test | [Test-MtAdGroupPrivilegedWithMembersCount](https://github.com/maester365/maester/blob/main/tests/ad/group/Test.AD-GMC-10.ps1) |
| Services | ActiveDirectory |
| Permissions | ActiveDirectory:Ldap:group:ReadProperty, ActiveDirectory:Ldap:group.member:ReadProperty |

</details>

## Source

- Test: [`tests/ad/group/Test.AD-GMC-10.ps1`](https://github.com/maester365/maester/blob/main/tests/ad/group/Test.AD-GMC-10.ps1)
- Documentation: [`tests/ad/group/Test.AD-GMC-10.md`](https://github.com/maester365/maester/blob/main/tests/ad/group/Test.AD-GMC-10.md)
