> 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/security-controls.md).

# Security controls

Prepare account access, credentials, integrations and alert delivery before relying on your Kilo deployment.

Before connecting equipment, check who can administer your organisation, which permissions each person needs and where its credentials are stored. Remove access when it is no longer needed.

1. Use individual accounts and give each person the access their work requires. Follow [Users and permissions](/account/users-and-permissions.md).
2. Treat API keys as credentials. Keep them out of source code, shared notes and ordinary messages. Follow [API keys](/settings/api-keys.md).
3. Review what each external integration or AI application can access and what information it sends elsewhere. Read [AI assistant privacy](/ai-assistant/privacy.md).
4. Test an alert's real destination and delivery before depending on it. Decide who will respond and what to do if the route fails.
5. For a customer-run installation, maintain the host and protect the local network. Use the security instructions for the installed product and version.

The [Customer security guide](/customer-security-guide.md) brings these tasks together. The [Audit Trail](/reports/audit-trail.md) describes its recorded event types. Confirm that the records and retention cover your use case before relying on them for an investigation.

If you find unexpected access or exposed credentials, use the [vulnerability-reporting instructions](/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/security-controls.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.