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.
Use individual accounts and give each person the access their work requires. Follow Users and permissions.
Treat API keys as credentials. Keep them out of source code, shared notes and ordinary messages. Follow API keys.
Review what each external integration or AI application can access and what information it sends elsewhere. Read AI assistant privacy.
Test an alert's real destination and delivery before depending on it. Decide who will respond and what to do if the route fails.
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 brings these tasks together. The Audit Trail 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.
Last updated