> 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/4.1/usage/security.md). # Security management This page describes important security considerations for WEKA cluster management. The WEKA system is a secure environment. It deploys a combination of security controls to ensure secured communication and user data. The security controls include the following: * **HTTPS access:** To access the WEKA GUI, you connect only to one of the system servers using HTTPS through port 14000. * **Authentication tokens:** The authentication tokens are used for accessing the WEKA system API and to allow the mounting of secure filesystems. * **KMS:** When creating an encrypted filesystem, a KMS must be used to properly secure the encryption keys. The KMS encrypts and decrypts filesystem keys. * **TLS certificates:** By default, the system deploys a self-signed certificate to access the GUI, CLI, and API through HTTPS. You can deploy your certificate with an unencrypted private key and certificate PEM files. * **CA certificates:** The system uses well-known CA certificates to establish trust with external services. For example, when using a KMS. * **Account lockout:** To prevent brute force attacks, if several login attempts fail (default: 5), the user account is locked for several minutes (default: 2 minutes). * **Login banner:** The login banner provides a security statement or a legal message on the sign-in page. * **GUI session automatic termination:** The user is signed out after 30 minutes of inactivity. **Related topics** [Obtain authentication tokens](/4.1/usage/security/obtain-authentication-tokens.md) [KMS management](/4.1/usage/security/kms-management.md) [TLS certificate management](/4.1/usage/security/tls-certificate-management.md) [CA certificate management](/4.1/usage/security/ca-certificate-management.md) [Account lockout threshold policy management](/4.1/usage/security/account-lockout-threshold-policy-management.md) [Organizations management](/4.1/usage/organizations.md)\ (security topics related to mounting and separation of organizations) [User management](/4.1/usage/user-management.md)\ (authentication of different user roles and AD/LDAP) --- # 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/4.1/usage/security.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.