> For the complete documentation index, see [llms.txt](https://docs.bizon.one/08.01/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bizon.one/08.01/help/vulnerability-disclosure.md).

# Vulnerability disclosure

Find out how to report a potential security vulnerability at Bizon.

### Report a Vulnerability

At Bizon, we are eager to protect our customers' accounts and ensure the security of our services at all times.\
We are deeply grateful to researchers and our community who report issues so that we can coordinate a fix and responsible disclosure. All reports are thoroughly investigated internally.\
\
To make a security vulnerability report, email [security@bizon.one](https://bizon.one) with the full details, including steps to reproduce the issue.

### When should you NOT perform reporting?

* You think you discovered a potential security vulnerability in Bizon's APIs or services
* You are unsure how a vulnerability affects Bizon's APIs or services
* You think you discovered a vulnerability in another project that Bizon depends on

### When should a vulnerability be reported?

* You need help tuning Bizon components for security
* Your issue is not security-related

<br>


---

# 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.bizon.one/08.01/help/vulnerability-disclosure.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.
