> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/deployment-resources/security-and-compliance/transport-layer-security-tls-support.md).
# Transport Layer Security (TLS) support
TLS support by controller, Command Centre service, and version.
## Overview
Transport Layer Security (TLS) is a security protocol that encrypts the sending of data to keep it private and safe.
\
How TLS works:
* **Handshake:** The client and the server agree on safety rules and create unique keys before sharing data.
* **Encryption:** Scrambles data so outside people cannot read it while it moves across the network.
* **Authentication:** Uses digital certificates to prove that servers are real and not fake.
* **Integrity:** Checks messages to make sure no one changed the data during transit.
The below information explains how TLS is use with Gallagher Security controllers and Command Centre.
### Controllers
Controller
TLS
Note
7000
1.2 and higher
TLS 1.3 requires Server 2022, Windows 11, or later.
6000
1.0 & 1.2
TLS 1.0 through to v7.70. v7.80+ supports TLS 1.2.
5000, 5000GL, and 3000
1.0
Legacy
### Command Centre
* Command Centre to Configuration Client uses TLS 1.2 only.
* Command Centre to CC Cloud tries TLS 1.3. It falls back to TLS 1.2 when unsupported by the operating system.
* Command Centre to Command Centre Client uses **OPCUA**, not TLS.
* The REST API supports TLS 1.3 from **v9.30**. The OS and client must support it.
* When Command Centre and SQL Server use separate machines, the host OS determines the TLS level.
---
# 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://help.security.gallagher.com/knowledge-hub/deployment-resources/security-and-compliance/transport-layer-security-tls-support.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.