> For the complete documentation index, see [llms.txt](https://coky-t.gitbook.io/owasp-top-10-ci-cd-security-risks-ja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coky-t.gitbook.io/owasp-top-10-ci-cd-security-risks-ja/readme.md).

# OWASP Top 10 CI/CD Security Risks ja

This is the unofficial Japanese translation of the [OWASP Top 10 CI/CD Security Risks](https://github.com/OWASP/www-project-top-10-ci-cd-security-risks).

* Document Site - <https://coky-t.gitbook.io/owasp-top-10-ci-cd-security-risks-ja/>
* Document Repository - <https://github.com/coky-t/owasp-top-10-ci-cd-security-risks-ja>

### Originator

* Project Site - <https://owasp.org/www-project-top-10-ci-cd-security-risks/>
* Project Repository - <https://github.com/OWASP/www-project-top-10-ci-cd-security-risks>
* Project Repository - <https://github.com/cider-security-research/top-10-cicd-security-risks>

## OWASP Top 10 CI/CD セキュリティリスク 日本語版

* [OWASP Top 10 CI/CD セキュリティリスク](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/index.md)
* [リーダー](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/leaders.md)
* [CICD-SEC-1](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/cicd-sec-01-insufficient-flow-control-mechanisms.md): 不十分なフロー制御メカニズム (Insufficient Flow Control Mechanisms)
* [CICD-SEC-2](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/cicd-sec-02-inadequate-identity-and-access-management.md): 不十分な ID およびアクセス管理 (Inadequate Identity and Access Management)
* [CICD-SEC-3](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/cicd-sec-03-dependency-chain-abuse.md): 依存チェーンの悪用 (Dependency Chain Abuse)
* [CICD-SEC-4](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/cicd-sec-04-poisoned-pipeline-execution.md): 有毒なパイプライン実行 (Poisoned Pipeline Execution (PPE))
* [CICD-SEC-5](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/cicd-sec-05-insufficient-pbac.md): 不十分なパイプラインベースのアクセス制御 (Insufficient PBAC (Pipeline-Based Access Controls))
* [CICD-SEC-6](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/cicd-sec-06-insufficient-credential-hygiene.md): 不十分な認証情報衛生 (Insufficient Credential Hygiene)
* [CICD-SEC-7](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/cicd-sec-07-insecure-system-configuration.md): 安全でないシステム構成 (Insecure System Configuration)
* [CICD-SEC-8](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/cicd-sec-08-ungoverned-usage-of-3rd-party-services.md): サードパーティサービスの無秩序な使用 (Ungoverned Usage of 3rd Party Services)
* [CICD-SEC-9](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/cicd-sec-09-improper-artifact-integrity-validation.md): 不適切なアーティファクト完全性バリデーション (Improper Artifact Integrity Validation)
* [CICD-SEC-10](/owasp-top-10-ci-cd-security-risks-ja/owasp-top-10-cicd-sekyuritirisuku/cicd-sec-10-insufficient-logging-and-visibility.md): 不十分なログ記録と可視化 (Insufficient Logging and Visibility)

## License

[Creative Commons Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/)

## Translator (Japanese)

[Koki Takeyama](https://github.com/coky-t)

* Document Site - <https://coky-t.gitbook.io/owasp-docs-ja/>
* Document Repository - <https://github.com/coky-t/owasp-docs-ja>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://coky-t.gitbook.io/owasp-top-10-ci-cd-security-risks-ja/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
