> For the complete documentation index, see [llms.txt](https://www.axisnow.io/zh/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.axisnow.io/zh/docs/edge/policies/access-control.md).

# 通用访问控制

按单个请求的特征放行或拦截请求

通用访问控制（General ACL）按单个请求的特征匹配规则并执行动作：跳过、阻断、IP 封禁或挑战。

## 在防护体系里的位置 <a href="#position" id="position"></a>

通用访问控制是[纵深安全防护](/zh/docs/edge/architecture/security.md#layer-4-access-control)的第 4 层，也是**策略**下的一个插件。在请求链路上，它排在真实客户端 IP、认证与授权之后，速率控制和缓存之前：

<table data-search="false"><thead><tr><th width="200">相邻的插件</th><th>关系</th></tr></thead><tbody><tr><td><a href="/zh/docs/edge/policies/real-ip.md">真实客户端 IP</a>（之前）</td><td>「客户端 IP 地址」「客户端 IP 区域」「客户端 IP ASN」取它还原出的真实地址</td></tr><tr><td><a href="/zh/docs/edge/policies/authn-authz.md">认证与授权</a>（之前）</td><td>认证失败的请求在那一层就被拒绝，不进入访问控制</td></tr><tr><td><a href="/zh/docs/edge/policies/rate-limiting.md">速率控制</a>（之后）</td><td>被访问控制拦截的请求不进入限速计数；跳过可以绕过速率控制插件；挑战通过后写入「挑战通过」字段，限速规则可以用它做条件</td></tr></tbody></table>

三个插件的分工：认证与授权按身份，通用访问控制按请求特征，速率控制按频率。本插件只处理 HTTP 和 HTTPS 端点，TCP 转发端点不经过它。

## 下一步 <a href="#next-steps" id="next-steps"></a>

<table data-search="false"><thead><tr><th width="160">页面</th><th>内容</th></tr></thead><tbody><tr><td><a href="/zh/docs/edge/policies/access-control/how-it-works.md">工作原理</a></td><td>规则评估顺序、四种动作的行为与配置要点</td></tr><tr><td><a href="/zh/docs/edge/policies/access-control/use-cases.md">防护场景</a></td><td>可直接套用的规则</td></tr><tr><td><a href="/zh/docs/edge/policies/access-control/insight.md">洞察与日志</a></td><td>指标定义、IP 封禁记录、日志入口</td></tr><tr><td><a href="/zh/docs/edge/policies/access-control/faq.md">常见问题</a></td><td>疑问与排错</td></tr></tbody></table>


---

# 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://www.axisnow.io/zh/docs/edge/policies/access-control.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.