> For the complete documentation index, see [llms.txt](https://docs.elite.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elite.cloud/faq/security-permissions.md).

# 安全性與權限驗證

本頁說明雲端雙效健檢在授權、資料存取與風險控管上的設計原則：我們會讀取哪些資訊、不會碰哪些內容、需要哪些 IAM 權限，以及您如何驗證我們確實是唯讀（Read-only）且可隨時撤銷，讓企業能安心進行檢測。

<details>

<summary>雲端雙效健檢需要哪些 IAM 權限？</summary>

我們採用 Read-only 的方式做非侵入式檢測，重點是：不改設定、不動資源、不讀資料內容，且權限您隨時可撤銷。

**我們會讀（Read-only）**

* 帳單與用量相關資訊（用於節費估算、趨勢與占比分析）
* 雲端設定中繼資料（metadata）（用於資安/合規檢測，例如：權限設定、加密狀態、日誌/可追溯性、網路規則等）
* 資源清單與狀態資訊（用於判斷閒置/低利用率/不合理配置）

**我們不會碰**

* 不會修改任何雲端設定與資源
* 不會做開關機、調整規格、刪除資源等操作
* 不會讀取資料庫內容、檔案內容、程式碼或使用者資料
* 不會影響效能與可用性

**您可做的事**

* 您可以檢視授權內容
* 您可以隨時撤銷或移除 CloudFormation Stack

</details>


---

# 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://docs.elite.cloud/faq/security-permissions.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.
