> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeperpam/jp/commander-cli/command-reference/enterprise-management-commands/risk-management-commands.md).

# リスク管理コマンド

サブコマンドのリファレンス

## リスク管理ドキュメント

本ページでは、リスク管理Pythonツールで使用できるコマンドについて、その機能と対応するエイリアスを記載しています。

### サブコマンド一覧

| サブコマンド                             | 説明                                                                                                                                                                                                                                        | エイリアス          |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- |
| enterprise-stat                    | リスク管理における直近のログイン数を表示します                                                                                                                                                                                                                   | es             |
| enterprise-stat-details            | 直近30日以内にログインしたユーザー数と、ボルト内に少なくとも1件のレコードを持つユーザー数を取得します                                                                                                                                                                                      | esd            |
| security-alerts-summary            | 直近30日間に発生したイベントの概要を、前の30日間と比較して取得します                                                                                                                                                                                                      | sas            |
| security-alerts-detail **aet**     | 直近30日間に発生したイベントの詳細を、前の30日間と比較して取得します。aetは監査イベントタイプ (ID) を表します (aetの例: **account\_recovery\_decline**)                                                                                                                                     | sad **aet**    |
| security-benchmarks-get            | 呼び出し元エンタープライズに設定されているセキュリティベンチマークの一覧を取得します                                                                                                                                                                                                | sbg            |
| security-benchmarks-set **fields** | <p>セキュリティベンチマークの一覧を設定します。対応する監査イベントが記録されます (<strong>fields</strong>指定例:<br>SB\_DEPLOY\_ACROSS\_ENTIRE\_ORGANIZATION:UNRESOLVED<br>SB\_DEPLOY\_ACROSS\_ENTIRE\_ORGANIZATION:RESOLVED<br>SB\_ENFORCE\_LEAST\_PRIVILEGE\_POLICY:IGNORED)</p> | sbs **fields** |


---

# 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.keeper.io/keeperpam/jp/commander-cli/command-reference/enterprise-management-commands/risk-management-commands.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.