> 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/ja/active-directory/acl-security-descriptors-and-permissions/sensitive-rights-to-identify.md).

# 特定すべき機密権限

特定すべき機密権限のためのActive Directoryセキュリティノート。列挙、Kerberos、資格情報、ACL悪用、ラテラルムーブメント、攻撃のワークフロー、検証手順を扱う。

ACLを分析する際、特定の権利が特に重要です。

| 権利                  | 潜在的な影響             |
| ------------------- | ------------------ |
| `GenericAll`        | オブジェクトに対する完全な制御    |
| `GenericWrite`      | オブジェクトの複数の属性を変更できる |
| `WriteOwner`        | 所有者を変更できる可能性       |
| `WriteDACL`         | 権限を変更できる           |
| `WriteMembers`      | グループにメンバーを追加できる    |
| `AllExtendedRights` | いくつかの機微な拡張権限へのアクセス |

これらの権利は、Active Directory内に特権への経路を生み出す可能性があります。


---

# 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/ja/active-directory/acl-security-descriptors-and-permissions/sensitive-rights-to-identify.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.