# TLS certificate management

TLS certificates are used to protect both the clients' information while it's in transfer and to authenticate the system identity to ensure users are interacting with legitimate system owners.

By default, the system deploys a self-signed certificate to access the GUI, CLI, and API through HTTPS.  You can deploy your certificate by providing an unencrypted private key and certificate PEM files.

The system supports TLS 1.2 and higher with at least 128-bit ciphers.

**Related topics**

[manage-the-tls-certificate-using-the-gui](https://docs.weka.io/4.2/usage/security/tls-certificate-management/manage-the-tls-certificate-using-the-gui "mention")

[manage-the-tls-certificate-using-the-cli](https://docs.weka.io/4.2/usage/security/tls-certificate-management/manage-the-tls-certificate-using-the-cli "mention")


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.weka.io/4.2/usage/security/tls-certificate-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.