> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/docs/docs-ja/hajimeni/core-functionalities/aikido-security-checks.md).

# Aikidoセキュリティチェック

### はじめに <a href="#introduction" id="introduction"></a>

Aikido は堅牢なセキュリティチェック群を使用します。Aikido はそれらを Repository、Cloud、Container、Domain の概要に整理しているため、導入されているセキュリティ対策を簡単に確認し、把握できます。

### チェック <a href="#checks" id="checks"></a>

* [**リポジトリスキャンのチェック**](https://app.aikido.dev/repositories/checks)：OSS、Secrets、Licences、SAST、IaC、マルウェア検出、モバイルの問題に関するチェックの詳細を確認できます
* [**クラウド設定チェック**](https://app.aikido.dev/clouds/checks)**:** 使っているクラウドの種類でフィルタリングすれば、簡単に概要を確認できます。
* [**コンテナスキャンのチェック**](https://app.aikido.dev/containers/checks)：オープンソースの依存関係の監視とサポート終了済みランタイム
* [**ドメインスキャンのチェック**](https://app.aikido.dev/domains/checks)**:** ドメインと API に対するチェック

### その他の推奨ビュー <a href="#other-recommended-views" id="other-recommended-views"></a>

* [**ライセンスとライセンスグループの概要**](https://app.aikido.dev/licenses)
* [**マルウェアスキャン**](https://app.aikido.dev/reports/malware/software-supply-chain-attacks)
* [**ランタイムとフレームワーク**](https://app.aikido.dev/reports/runtimes)


---

# 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://help.aikido.dev/docs/docs-ja/hajimeni/core-functionalities/aikido-security-checks.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.
