> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/active-directory/acl-security-descriptors-and-permissions/permissions-audit-and-permission-entries.md).
# Permissions, Auditing, and ACEs
Active Directory security notes for Permissions, Auditing, and ACEs, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
In the advanced security settings of an Active Directory object, there are generally several important parts.
#### Permissions
The **Permissions** tab displays users or groups who have rights to the object.
Examples of possible permissions:
* read the object;
* modify certain attributes;
* change the owner;
* modify permissions;
* add members to a group;
* delete the object.
#### Audit
The **Audit** tab allows you to define which accesses must be logged.
It is used to keep track of when a user performs certain actions on the object.
Examples:
* read attempt;
* modification;
* permission change;
* deletion;
* Access denied.
#### Permission entries
**Permissions entries** correspond to the detailed lines present in an ACL.
Each entry is called an **ACE**, or **Access Control Entry**.
An ACE indicates:
* the user or group concerned;
* the type of access;
* the rights granted;
* the object concerned;
* whether the permission is inherited or not.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/active-directory/acl-security-descriptors-and-permissions/permissions-audit-and-permission-entries.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
.png?alt=media)
.png?alt=media)