AD-USER-17: User profile path count should be retrievable
| ID | AD-USER-17 |
| Severity | Info |
| Suite | Active Directory (on-premises) |
| Product | Active Directory |
| Feature | Users |
| Security area | Infrastructure hardening |
| Resource type | User |
| Reads from | On-premises Active Directory |
What this checks and how to fix it
Section titled “What this checks and how to fix it”The ProfilePath attribute is commonly associated with roaming profiles and centralized workstation state. It often points to legacy file server infrastructure that should be reviewed for resilience and access control.
- Legacy profile management: Identifies users depending on roaming profiles
- Data exposure review: Highlights centralized storage paths that may require tighter controls
- Operational dependency mapping: Helps quantify reliance on older desktop management models
Control Type
Section titled “Control Type”Detective
Security Recommendation
Section titled “Security Recommendation”- Review profile share permissions and access paths
- Confirm roaming profiles are still necessary for affected users
- Consider modern endpoint and profile management approaches where appropriate
How the Test Works
Section titled “How the Test Works”This test counts user objects where the ProfilePath attribute contains a non-empty value.
Related Tests
Section titled “Related Tests”Test-MtAdUserHomeDirectoryCount- Highlights related file share dependenciesTest-MtAdUserScriptPathCount- Finds additional legacy sign-in configuration
Mito check. Author: soulemike. Open-source licences.
Open-source licences. CIS Benchmark material © Center for Internet Security, Inc.; CISA SCuBA baselines are public domain (CC0).
© 2026 Virtual Petals. Mito is a Virtual Petals service, hosted in Microsoft Azure UAE North.