> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/ja/sekyuriti/privacy-and-security-disclosure/verkada-bug-bounty-program.md).

# Bug Bounty Program

Verkada Bug Bounty Programに関する情報

Verkada は Bugcrowd を通じて非公開のセキュリティバグ報奨金プログラムを実施しています。Verkada の Bugcrowd プログラムへの招待をご希望の場合は、次の宛先にメールを送信してください <security@verkada.com> 件名を「Bugcrowd Invite」とし、Bugcrowd アカウントに関連付けられているメールアドレスを必ず含めてください。Verkada は、Bugcrowd 経由で報告された脆弱性に対してのみ報奨金を支払います。

Bugcrowd 以外で Verkada にセキュリティ脆弱性を直接報告したい場合は、このフォームにご記入ください <https://www.verkada.com/security/report-issue/> 。フォームに関する問題については、次までお問い合わせください <security@verkada.com>.


---

# 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.verkada.com/command/ja/sekyuriti/privacy-and-security-disclosure/verkada-bug-bounty-program.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.
