> 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/zh/active-directory/acl-security-descriptors-and-permissions/permissions-audit-and-permission-entries.md).

# 权限、审计和 ACE

面向权限、审计和 ACE 的 Active Directory 安全笔记，涵盖枚举、Kerberos、凭据、ACL 滥用、横向移动、利用流程和验证步骤。

在 Active Directory 对象的高级安全设置中，通常有几个重要部分。

#### 权限

该 **权限** 选项卡显示对该对象拥有权限的用户或组。

可能的权限示例：

* 读取对象；
* 修改某些属性；
* 更改所有者；
* 修改权限；
* 向组中添加成员；
* 删除对象。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-8df7f302c74ab161bce55b672549297029e7a6a9%2Fimage%20(3244).png?alt=media" alt=""><figcaption></figcaption></figure>

#### 审核

该 **审核** 选项卡允许你定义必须记录哪些访问。

它用于跟踪用户何时对对象执行某些操作。

示例：

* 读取尝试；
* 修改；
* 权限更改；
* 删除；
* 访问被拒绝。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-b04bd1adde33c8138c9fcfd4537ff1c9b74445aa%2Fimage%20(3245).png?alt=media" alt=""><figcaption></figcaption></figure>

#### 权限条目

**权限条目** 对应于 ACL 中的详细行。

每个条目称为一个 **ACE**或 **访问控制项**.

ACE 表示：

* 相关的用户或组；
* 访问类型；
* 授予的权限；
* 相关对象；
* 权限是否继承。


---

# 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/zh/active-directory/acl-security-descriptors-and-permissions/permissions-audit-and-permission-entries.md?ask=<question>&goal=<user_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.
