> 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/ko/security/privacy-and-security-disclosure/verkada-bug-bounty-program.md).

# 버그 바운티 프로그램

Verkada 버그 바운티 프로그램 정보

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/ko/security/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.
