> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/trust-center/security/vulnerability-disclosure.md). # Vulnerability Disclosure ilert welcomes responsible security research and accepts vulnerability reports from the security community. ## Scope Vulnerability reports should relate to security issues found in: * The ilert platform (app.ilert.com) * ilert APIs (api.ilert.com) * ilert mobile applications (iOS and Android) * ilert's public-facing web properties (ilert.com) ## How to Report Send vulnerability reports to: **Email:** Please include: * A description of the vulnerability and its potential impact * Steps to reproduce the issue * Any supporting evidence (screenshots, logs, proof-of-concept) ## Response ilert's security team investigates all reports and works to quickly fix valid issues. The reporter will be kept informed about the status of the investigation. ## Recognition ilert maintains a Hall of Honors recognizing researchers who submit valid vulnerability reports and cooperate with ilert during the investigation and remediation process. --- # 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.ilert.com/trust-center/security/vulnerability-disclosure.md?ask=&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.