> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/compliance-status.md).

# Security assessment status

Understand Kilo’s current security assessment status and the distinction between platform and hosting-provider assurance.

Kilo is implementing and checking its information security management system for the hosted platform and applicable software products. This is the set of policies, responsibilities and working controls used to protect the service.

Kilo does not currently publish an ISO/IEC 27001 certification, SOC 2 report, BSI C5 attestation or CSA STAR listing. Internal documentation and checks are not independent certification.

When an assessment is complete and approved for publication, the published information will identify the company and service assessed, scope, assessor, date, limitations and supporting evidence. A hosting provider's assessment covers that provider's stated services and period; it does not automatically extend to Kilo.

For practical setup and ongoing use, read the [Customer security guide](/customer-security-guide.md). For a possible vulnerability, follow [Report a security vulnerability](/incident-response-and-vulnerability-reporting.md).


---

# 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.kiloiot.io/compliance-status.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.