> 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/encryption-using-the-biometric-encryption-utility.md).

# Encryption using the Biometric Encryption Utility

The Biometric Encryption Utility provides a secure method of encrypting TCP/IP communications on Morpho readers using on a laptop or similar in a safe room/network to connect to Morpho readers and assign them the appropriate keys and certificates. We recommend to directly connect to the readers when using the Biometric Encryptions Utility.

### Prerequisites

Before you begin this procedure ensure:

* you are using the Biometric Encryption Utility on a laptop or similar in a safe room/network.
* the **Send encryption keys via network** option is disabled (unchecked) on the **Advanced** tab of the Biometric Card Type.
* the Microsoft Redistributables must be installed on the machine the utility is run on. See [Installing Microsoft Redistributables](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/installation/installing-microsoft-redistributables.md) for the procedure.

### Procedure

1. In Command Centre Configuration Client, click **Configure** from the menu bar, then **Hardware**.

   The Hardware List Window opens.
2. Highlight the Morpho Biometric Reader you want to encrypt communications for.
3. **Right-click** and select **Properties**.
4. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-dfdbf9ed2eb33401a6dcbdc29b32f5ebf3a12ce0%2Fmorphobiometricreader_setuptab.png?alt=media)
5. Tick the **Encrypt TCP/IP Communications** checkbox.

   **Note:** This option is OFF (disabled) by default.
6. Click the **Generate New Certificates** button to generate and export the certificates/keys, and export the Biometric Encryption Utility.

   **Notes**:

   * This button will be disabled if the **Send encryption keys via network** option is checked on the biometric card type.
   * The **Export Certificates** button is also available for exporting the existing communications certificate.
   * Export Certificate requires "Manage Keys" operator privilege to work.
7. From the displayed **Browse for Folder** dialog, path your way to the directory to export the reader’s certificate/key file to, and click the **OK** button.

   **Notes**:

   * Once the certificate has been generated and you click **Apply**, Command Centre will not communicate with the reader until the certificate and encryption has been applied to the reader.
   * The readers certificate/key files are only valid for seven days.

   A pop-up displays the password which is used to protect the exported key files for securing the reader.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-31833c85f59c5654a13729de515a60b0b29c4b0d%2Fexportedkeyspassword.png?alt=media)
8. Transfer the password securely from here into the Biometric Encryption Utility.
9. Take exported files and transfer them to the PC that will be connecting to the reader.
10. Ensure the reader is connected to the PC.
11. Go to the directory you specified the reader’s certificate/key file to be exported to.
12. Run the **BiometricEncryptionUtility.exe** executable.

    The Biometric Encryption Utility opens.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-db08a1f00c1a1a737ef45fb2ddeb923abe3c8811%2Fbiometricencryptionutility.png?alt=media)
13. Enter the path to the reader’s communication certificate in the **Key File Path** field.

    By default, the directory name will be the same as the name of the reader that you have exported from.
14. Enter the password from the popup at Step 6 into the **File Password** field.
15. Enter the IP address of the reader to connect to in the **Reader IPv4 Address** field.
16. Click the **Set to Encrypted communication** radio button.
17. Click the **Configure Reader** button.

    The utility sends down the key and securely connects to the reader. It then deletes the certificate/key files from disk to prevent accidental re-use on another reader.

    **Note:** The reader will update and reboot after the certificate has been downloaded.


---

# 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/encryption-using-the-biometric-encryption-utility.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.
