> 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/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption.md).

# Communications Encryption

Native mode allows sites to implement more secure TCP/IP communications for Morpho Sigma readers if required. Sites can use either of the two methods for securing Morpho Sigma readers:

* Gallagher Command Centre vEL7.80 (via the network)

  (see [Encryption using Command Centre](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/encryption-using-command-centre.md)), or
* Biometric Encryption Utility (a non-network solution)

  (see [Encryption using the Biometric Encryption Utility](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/encryption-using-the-biometric-encryption-utility.md))

Each encrypted Sigma reader will be issued with its own unique certificate, and a unique set of public and private keys.

**Notes:**

* Readers set to Native Mode (MA5G) will use TLS1.2 encryption. Encryption is RSA2048 with SHA256 hash on certificates.
* Reader encryption is recommended to avoid possible interception and tampering.
* Encrypted communications, which is OFF (disabled) by default, MUST be disabled on Morpho Readers before being removed and/or deleted from Command Centre. The reader will not allow communications outside of Command Centre if the encrypted communications are not disabled. Stateful alarms are generated when a Morpho Readers encrypted communications are disabled.

[Encryption using Command Centre](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/encryption-using-command-centre.md)

[Encryption using the Biometric Encryption Utility](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/encryption-using-the-biometric-encryption-utility.md)

[Known Issue](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/known-issue.md)

[Unencryption](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/unencryption/unencryption-using-the-biometric-encryption-utility.md)

### In This Section

* [Encryption using Command Centre](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/encryption-using-command-centre.md)
* [Encryption using the Biometric Encryption Utility](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/encryption-using-the-biometric-encryption-utility.md)
* [Known Issue](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/known-issue.md)
* [Unencryption](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption/unencryption.md)


---

# 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/configuration-client/integrated-systems/morpho-biometric-integration/communications-encryption.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.
