# Group Policy Preferences
**ATT\&CK ID:** [T1552.006](https://attack.mitre.org/techniques/T1552/006/)
**Permissions Required:** **User**
**Description**
Adversaries may attempt to find unsecured credentials in Group Policy Preferences (GPP). GPP are tools that allow administrators to create domain policies with embedded credentials. These policies allow administrators to set local accounts.
These group policies are stored in SYSVOL on a domain controller. This means that any domain user can view the SYSVOL share and decrypt the password (using the AES key that has been made [public](https://msdn.microsoft.com/library/cc422924.aspx)).
## Techniques
### CMD
```
findstr /S cpassword %logonserver%\sysvol\*.xml
findstr /S /I cpassword \\\sysvol\\policies\*.xml
```
### Empire
```
usemodule powershell/privesc/gpp
usemodule python/privesc/windows/get_gpppasswords
```
### Metasploit
```
use post/windows/gather/credentials/gpp
```
## Further Reading
{% content-ref url="/pages/-MZCyqGfsSSBn6tTdl\_E" %}
[GPP Passwords](/pentest-everything/everything/everything-active-directory/credential-access/unsecured-credentials/group-policy-preferences/gpp-password.md)
{% endcontent-ref %}
## Mitigation
The same methods of searching for GPP passwords offensively, exists to find the same issue from a defense perspective.
### CMD
```
findstr /S cpassword %logonserver%\sysvol\*.xml
findstr /S /I cpassword \\\sysvol\\policies\*.xml
```
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://viperone.gitbook.io/pentest-everything/everything/everything-active-directory/credential-access/unsecured-credentials/group-policy-preferences.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.