> 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/products/integrations/third-party-readers/idemia-morpho/reference/idemia-readers-morpho-ma2g-vs-ma5g-modes.md). # MA2G and MA5G communication modes Compare IDEMIA reader communication modes, encryption behavior, and Command Centre compatibility. IDEMIA readers use one of two communication modes between the Command Centre server and the reader: **Legacy MA2G** or **Native MA5G**. Command Centre supports both. * **Legacy MA2G** is the older mode (MA J-Series, MA 520). VP Dual Finger Vein supports **only** MA2G. **Not supported from 9.30.** * **Native MA5G** is recommended for **vEL7.80+**. It is **encrypted** with TLS 1.2 (RSA-2048, SHA-256 certificates), and each reader has a unique certificate and key pair. Wave Compact supports **only** MA5G. ### Legacy mode (MA2G) {% hint style="warning" %} From **9.30**, MA2G Legacy mode is no longer supported. {% endhint %} Legacy mode is the older connection mode. It was traditionally used with previous reader models, for example MA J-Series and MA 520 readers. Gallagher recommends Native mode for sites with Command Centre **vEL7.80 and above**, because it allows encrypted communication between the Command Centre server and the IDEMIA readers. ### Encryption (Native MA5G) Native mode lets sites use more secure TCP/IP communications for IDEMIA readers. IDEMIA readers set to Native mode (MA5G) with encryption enabled use **TLS 1.2** between the Command Centre server and the reader. Encryption is **RSA2048 with SHA256 hash** on certificates. **Each encrypted Sigma reader is issued its own unique certificate and a unique set of public and private keys.** There are two securing methods for Morpho Sigma readers. Both are documented in "MorphoAccess Installation Guide.pdf" on the Command Centre install media: * Over the network via Command Centre **vEL7.80 and above**. * The **Biometric Encryption Utility**, a non-network solution. ### Encryption defaults * **vEL7.80 to 7.90:** "Encrypt Communications" was **ON by default**. This caused reader lockouts for some Channel Partners when a reader was moved from a demo system to a live site without disabling encryption first. The readers became locked and unusable. * **vEL8.00+:** "Encrypt Communications" is **OFF by default**, with a maintenance alarm noting that the reader is unencrypted. {% hint style="warning" %} **Before removing an encrypted reader from Command Centre, disable its encryption.** If you forget, a tool can retrieve the certificate from Command Centre, but only if you can identify which reader it was. This only works for sites on 7.90 and above. {% endhint %} ### Connection modes by Command Centre version | Command Center Version | SIGMA Lite | SIGMA Lite Multi | SIGMA Lite + | SIGMA Lite + Multi | SIGMA BIO | SIGMA Multi | SIGMA Extreme Multi | VP BIO | Wave Compact | | ---------------------- | ---------- | ---------------- | ------------ | ------------------ | --------- | ----------- | ------------------- | ------------- | ------------ | | vEL7.30 | MA2G | MA2G | MA2G | MA2G | | | | MA2G | | | vEL7.40 | MA2G | MA2G | MA2G | MA2G | MA2G | MA2G | | MA2G | | | vEL7.50 | MA2G | MA2G | MA2G | MA2G | MA2G | MA2G | MA2G | MA2G | | | vEL7.60 | MA2G | MA2G | MA2G | MA2G | MA2G | MA2G | MA2G | MA2G | | | vEL7.70 | MA2G | MA2G | MA2G | MA2G | MA2G | MA2G | MA2G | MA2G | | | vEL7.80 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | | | vEL7.90 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | | | vEL8.00 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | | | vEL8.10 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL8.20 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL8.30 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL8.40 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL8.50 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL8.60 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL8.70 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL8.80 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL8.90 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL9.00 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL9.10 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL9.20 | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G/MA5G | MA2G | MA5G | | vEL9.30 | MA5G | MA5G | MA5G | MA5G | MA5G | MA5G | MA5G | not supported | MA5G | {% hint style="info" %} This grid uses the model names **SIGMA BIO**, **SIGMA Multi** and **VP BIO**, which the reader support grid on [IDEMIA reader compatibility and specifications](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/reference/idemia-readers-supported-morpho-readers.md) does not use. Both are shown as the source gives them. {% endhint %} New readers ship locked to secure communication. For security-by-default readers, see [Enable On-Demand Security](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/configure/idemia-readers-morpho-how-to-enable-the-on-demand-security-state.md), which explains how to put a Morpho reader into the On-demand Security state. For the related encrypted OSDP option, see [Configure IDEMIA readers over OSDP](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/configure/idemia-readers-idemia-morpho-osdp.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/products/integrations/third-party-readers/idemia-morpho/reference/idemia-readers-morpho-ma2g-vs-ma5g-modes.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.