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

# Security

- [Security overview](https://docs.weka.io/security/security.md): The system implements a comprehensive security framework with multiple controls to ensure secure communication and protect user data in the cluster.
- [Obtain authentication tokens](https://docs.weka.io/security/obtain-authentication-tokens.md): Obtain and manage WEKA access, refresh, and long-lived API tokens.
- [Manage token expiration](https://docs.weka.io/security/manage-token-expiration.md): Configure default and maximum lifetimes for WEKA access and refresh tokens.
- [Manage account lockout policy](https://docs.weka.io/security/account-lockout-threshold-policy-management.md): Configure, reset, and view account lockout settings using the GUI or CLI.
- [Manage KMS](https://docs.weka.io/security/kms-management.md): Manage KMS integration for cluster and per-filesystem encryption keys.
- [Manage KMS using the GUI](https://docs.weka.io/security/kms-management/kms-management.md): Configure, view, update, and remove Key Management System integrations using the GUI.
- [Manage KMS using the CLI](https://docs.weka.io/security/kms-management/kms-management-1.md): Configure Key Management System integrations, rewrap filesystem keys, and prepare Vault or KMIP using the CLI.
- [Manage TLS certificates](https://docs.weka.io/security/tls-certificate-management.md): Manage TLS certificates to encrypt data in transit and verify system identity, ensuring secure communication in the WEKA cluster.
- [Manage TLS certificates using the GUI](https://docs.weka.io/security/tls-certificate-management/manage-the-tls-certificate-using-the-gui.md): Set, replace, download, and manage TLS and custom CA certificates using the GUI.
- [Manage TLS certificates using the CLI](https://docs.weka.io/security/tls-certificate-management/manage-the-tls-certificate-using-the-cli.md): Manage TLS and CA certificates, including certificate status and downloads, using the CLI.
- [Manage Cross-Origin Resource Sharing](https://docs.weka.io/security/manage-cross-origin-resource-sharing.md): Manage trusted sites for Cross-Origin Resource Sharing using CLI commands.
- [Manage CIDR-based security policies](https://docs.weka.io/security/manage-cidr-based-security-policies.md): Manage CIDR-based security policies to control access to WEKA clusters based on client IP address ranges, enhancing security and simplifying administration.
- [Manage login banner](https://docs.weka.io/security/manage-the-login-banner.md): Configure, enable, disable, and reset the login banner using the GUI or CLI.
- [Secure cluster membership with join secret authentication](https://docs.weka.io/security/secure-cluster-membership-with-join-secret-authentication.md): Enable and manage join secret authentication for secure on-premises cluster membership.
- [Security hardening](https://docs.weka.io/security/security-hardening.md): Harden the security of a WEKA deployment. This guide covers Linux best practices, architectural requirements, port configurations, and auditing capabilities.


---

# 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.weka.io/security.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.
