> 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/site-installation/server-properties/card-security.md).

# Card Security

### Introduction

MIFARE® high security cards, (i.e. MIFARE Plus® and MIFARE® DESFire® EV1 to EV3 are currently the only MIFARE high security cards supported), which are a replacement for the MIFARE (classic) card, feature multiple certified security levels, including Advanced Encryption Standard (AES) encryption.

**Note:** Command Centre only encodes MIFARE Plus cards to Security Level 3.

This tab enables you to set the site security information, as follows:

* site security information for encoding MIFARE high security cards,
* the MIFARE Enhanced Security feature which ensures MIFARE readers are able to prevent access through the use of replicated cards,
* MIFARE Plus/DESFire encoding information,
* configure readers to accept Admin cards,
* set the card technologies permitted on site,
* PIN settings for user PINs. The **Crypt Seed** number is used for PIN numbers, and is supplied by the Gallagher Group Limited, and
* enable a fast scan mode for Card Serial Number (CSN) on TSeries readers.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Card Security** tab.

   The **General** sub-tab displays by default.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a9e34224df976108f9b29e70ecebdb9432199502%2Fcardsecuritytab.png?alt=media)
3. Perform the required function(s):

<details>

<summary>Setting permitted card technologies</summary>

In the Permitted Card Technology section, by default **MIFARE DESFire EV1 to EV3** is selected, and **PIV** for sites with a PIV license.

**Important:** Gallagher recommends the use of MIFARE DESFire EV1 to EV3 or PIV card technologies. Some of the other options have known security vulnerabilities.

1. If you require other card types to be accepted at readers, select the appropriate checkboxes.
2. If your site is using MIFARE Plus cards with the ‘X’ feature set and you wish to prevent relay attacks occurring over HBUS, check the **MIFARE Plus** checkbox to enable the **Enforce MIFARE Plus X Card Proximity Checking** checkbox.
3. Check the **Enforce MIFARE Plus X Card Proximity Checking** checkbox.

   The terminal will perform proximity checks when reading a MIFARE Plus X card.

   **Notes:**

   * Checking this option disables all other card technologies.
   * The MIFARE Plus X Card Proximity Checking feature will only work if the site that issued the card is using the same MIFARE Plus/DESFire key seed as your site.
   * Operators need the "Edit Site" privilege to be able to amend this setting.
4. Click the **Find Noncompliant Readers** button to locate any readers that differ from your settings.

   The Find tool displays listing any applicable readers.

   **Note:** A Reader Bulk Change can be performed to change the card technologies accepted at readers, and Find tool results can be dragged onto the Reader Bulk Change wizard. See [Initiating a new Reader Bulk Change](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/bulk-changes/initiating-a-new-reader-bulk-change.md) for further detail.

</details>

<details>

<summary>PIN Settings</summary>

1. Check the **Store user PINs for later viewing** checkbox.

   Checking this option means that user PINs will be encrypted and stored so that operators with the "View PIN's" operator privilege will be able to later decrypt and display them, if necessary.

   See the [View PINs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-privileges/which-operator-privileges-you-require/cardholder-access.md#view-pins) operator privilege for further detail describing the criteria for viewing PINs.

   **Note:** If a number already populates the **Crypt seed** field, this means that it was configured in your license file when Command Centre was installed.

   **CAUTION:** You can change the 5-digit Crypt Seed, however new PINs will have to be issued to every authorised cardholder.
2. Do you require a fast scan mode for CSN on TSeries readers, so that if no Gallagher data is found on a card, the reader will immediately read the CSN rather than reading every sector on the card?

   **Note:** This feature does not apply to TSeries readers connected as Cardax IV.

   <table><thead><tr><th width="85">If...</th><th>then...</th></tr></thead><tbody><tr><td>no,</td><td>go to Step 3.</td></tr><tr><td>yes,</td><td><p>check the <strong>Enable Fast CSN mode</strong> checkbox.<br>Checking this results in the following on the <strong>Advanced</strong> tab for all TSeries Readers:</p><ul><li>the <strong>Require MIFARE Enhanced Security encoded cards</strong> and <strong>Use MIFARE Serial Number as Card Data</strong> options will be disabled, and</li><li><strong>Use MIFARE Serial Number as Card Data</strong> will be checked.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c8c535447366925a110a7388255958c9b23f59a1%2Fenablecsnmode_readerresult.png?alt=media" alt="SP_Card Security - Generate Reader Configuration Card"></li></ul><p>If <strong>Require MIFARE Enhanced Security encoded cards</strong> was previously checked, it will now be unchecked. If <strong>Enable fast CSN mode</strong> is unchecked again on the server settings, those fields on the readers will no longer be disabled, and the setting on the readers will return to their earlier state.<br><strong>Note:</strong> The reader firmware must be updated, via vGR7.90.104 (or later) in order for the feature to work.</p></td></tr></tbody></table>

</details>

<details>

<summary>Disabling Legacy PINs</summary>

By default, the **Enable Gallagher Legacy PIN mode** checkbox is enabled on an upgrade. For clean Installs, or sites upgrading with a NPSA license, the checkbox is disabled.

If a Card Type has PINs enabled and a card of that type is not assigned a PIN, a PIN is calculated for it based on the Crypt Seed in the database, and that Card Number which can be seen using the **View PIN** button in both Command Centre and Configuration Client.

On a controller when a card is badged, and a PIN is required, if the card doesn't have a PIN this legacy mode is utilised and any PIN entered is checked against calculated PIN.

</details>

4. Click the **MIFARE Site Keys** sub-tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8cad4cff0df3aaa52eff4a761212e9bb2549f1aa%2Fcardsecuritytab_mifaresitekeyssubtab.png?alt=media)

<details>

<summary>Generate a custom key seed or import a key</summary>

1. Do you want to use a default MIFARE Plus/DESFire key seed for encoding MIFARE high security cards?

   **Note:** See [MIFARE DESFire Key Migration](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/card-security/mifare-desfire-key-migration.md) for the full procedure on migrating away from using the default MIFARE® key seed on DESFire® cards, to using a unique MIFARE® key seed.

   <table><thead><tr><th width="85">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes,</td><td>Click the <strong>Set To Default</strong> button.<br>The following warning message displays:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-69fc510b2f699439b6d9d5812398cd294dd03f0c%2Fcardsecuritytab_settodefault.png?alt=media" alt="SP_Card Security"><br>Click the <strong>Yes</strong> button.</td></tr><tr><td>no,</td><td>populate the <strong>MIFARE Plus/DESFire key seed</strong> field with a 32 hexadecimal character string and click the <strong>Apply</strong> button to save the key.<br><br><strong>Note:</strong> This can be done by either manually typing in a string, or by clicking the <strong>Generate</strong> button which will automatically populate the field with a random hexadecimal string. When the <strong>Apply</strong> button is clicked, the 32 characters are converted to 32 X's, (i.e. the key is hidden).</td></tr></tbody></table>
2. The MIFARE Plus/DESFire key seed is updated, as indicated by the message that displays in the lower part of the screen.
3. The MIFARE DESFire card key migration window by default will be for a period of one month from today’s date. Change the end date if required.
4. What readers do you want to use for migration?

   <table><thead><tr><th width="157">If...</th><th>then...</th></tr></thead><tbody><tr><td>All Readers,</td><td>click the <strong>All Readers</strong> radio button.</td></tr><tr><td>Selected Readers,</td><td><ol><li>Click the <strong>Selected Readers</strong> radio button.</li><li>Drag and drop the readers you want into the grid.</li></ol></td></tr><tr><td colspan="2">If you click <strong>Apply</strong> now, a warning message displays:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d8a3bd6b3a6ae72026dc927e1221e430d33c52ed%2Fcardsecuritytab_changekeyseedmessage.png?alt=media" alt="SP_Card Security"><br>See <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/card-security/mifare-desfire-key-migration.md">MIFARE DESFire Key Migration</a> for the full procedure on migrating away from using the default MIFARE® key seed on DESFire® cards, to using a unique MIFARE® key seed.</td></tr></tbody></table>
5. Do you want to encode MIFARE cards with the MIFARE Enhanced Security feature?

   <table><thead><tr><th width="94">If...</th><th>then...</th></tr></thead><tbody><tr><td>no,</td><td>go to Step 6.</td></tr><tr><td>yes,</td><td><ol><li>Populate the <strong>MIFARE enhanced security key</strong> field with a 32 hexadecimal character string and click the <strong>Apply</strong> button to save the key.<br><br><strong>Note:</strong> This can be done by either manually typing in a string, or by clicking the <strong>Generate</strong> button which will automatically populate the field with a random hexadecimal string. When the <strong>Apply</strong> button is clicked, the 32 characters are converted to 32 X's, (i.e. the key is hidden).<br>The following warning message displays:<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5a6a8d82cac9c3dc9c9bfc7fb045d40c8f403a44%2Fcardsecuritytab_changeenhancedsecuritykeymessage.png?alt=media" alt="SP_Card Security"></li><li>Click <strong>Yes</strong> and go to Step 6.</li></ol></td></tr></tbody></table>
6. The DESFire Default Application Key field is editable and can be imported and exported (including for bureau encoding) using the **Import Keys…** and **Export Keys…** buttons as appropriate.

   On upgrade to a version that supports key migration, (i.e. v8.30 onwards), the MIFARE DESFire Default Application Key is set to a value derived from the MIFARE Plus/DESFire key seed.

   If a key file from a pre-8.30 version of Command Centre is imported into a version v8.30 or later, the Default Application Key is overwritten with one that is derived from the MIFARE Plus/DESFire key seed.

   **Note:** The **MIFARE Plus MAD write key** read-only field displays a 32 hexadecimal character key that allows third parties or other Gallagher sites to re-encode and update the MAD for MIFARE Plus cards issued by this site. It will change whenever the MIFARE key seed is changed.

</details>

<details>

<summary>Export MIFARE keys</summary>

1. Click the **Export Keys...** button.

   A 'Please choose a password' dialog displays.
2. Enter a password.

   **Note:** The password must be at least eight characters long, and can be a maximum of 32 characters.
3. Click the **OK** button.

   A 'Save As' dialog displays with a default filename **MifareKeys.txt**
4. Change the default filename if required, and path your way to the location where you want to save the Site Key file.
5. Click the **Save** button.

   The message *"Key successfully exported and protected by your password"* displays.

   A "\[SiteSerial]" section will also be created in the file under \[MifareSiteKey] section including three fields: 1)Serial 2)Encryption and 3)KeyDerivation.

   Serial number is encrypted to a random hex string 32 characters long in the same way MIFARE Plus/DESFire key seed does so that it can be verified which particular site the exported file belongs to.

</details>

<details>

<summary>Import MIFARE keys</summary>

1. Click the **Import Keys...** button.
2. Path your way to the location where the MIFARE key file you want to import is located and click on the MIFARE key file you want to import.
3. Click the **Open** button.

   An 'Enter password' dialog displays.
4. Enter the correct password for the selected MIFARE key file (this password will need to be supplied by the site that exported the MIFARE key).
5. Click the **OK** button.

   The **MIFARE Plus/DESFire key seed** field displays the text 'XXXXXXXXX IMPORTED KEY XXXXXXXXX' to confirm the key has been imported successfully.

   **Note:** Keys exported by earlier versions than vEL8.00 of Command Centre cannot be imported.
6. Click the **Apply** button to save the new key.

</details>

<details>

<summary>Encode an Admin card</summary>

An Admin card is required if the site needs to update T series readers with the MIFARE key and/or needs to load a list of Facility Codes on a T series reader to support multiple applications.

Refer to the **Sharing MIFARE Classic and Plus cards between sites.pdf** document located in the `'Documentation'` directory of the Command Centre installation files for more information regarding multiple applications.

The **Allow Admin card update at readers** checkbox allows you to put T series readers into a mode that will allow the MIFARE key or facility code list of the reader to be changed via an Admin card. This checkbox should be disabled after all the sites T series readers MIFARE key or facility code list have been updated with an Admin card.

**Note:** An Admin card should only be presented at a T series reader configured for Cardax IV.

1. Do you want to encode an Admin card to update readers MIFARE key and/or facility code list?

   <table><thead><tr><th width="85">If...</th><th>then...</th></tr></thead><tbody><tr><td>no,</td><td>go to Step 4.</td></tr><tr><td>yes,</td><td><ol><li>Check the <strong>Allow Admin Card update at readers</strong> checkbox.</li><li>Click the <strong>Generate Admin Card</strong> button.<br>The 'Generate Reader Configuration Card' dialog displays.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ee97afa80a29775af401fb6e96e0967195e78504%2Fgenerateadmincard_dialog.png?alt=media" alt="SP_Card Security - Generate Reader Configuration Card"></li><li>Select the appropriate encoder from the <strong>Encoder</strong> drop-down list, (i.e. either <em>SCM Microsystems Inc. SDI010 Contactless Reader 0</em> or <em>SCM Microsystems Inc. SDI011G Contactless Reader 0</em>).<br>The <strong>Encode Card</strong> button becomes enabled.<br><br><strong>Note:</strong> If no USB Encoder is attached to the workstation, the message <em>"No USB Encoder was detected"</em> appears in the Status bar.</li><li>Check the <strong>Update facility code list</strong> checkbox (depending on whether you want key change only, facility code list only, or key change and facility code list).</li><li>Click the <strong>Encode Card</strong> button to encode a MIFARE Plus or MIFARE DESFire EV1 to EV3 card, and encode the MIFARE key seed to it, which when presented at a T series reader (when <strong>Allow Admin card update at readers</strong> is checked), will update the MIFARE key on the reader.<br><strong>IMPORTANT:</strong> Should you need to return T series Cardax IV connected readers to the factory default settings, this can be done by clicking the <strong>Reset to Factory Defaults</strong> button (on the <strong>Status and Overrides</strong> tab) for each individual reader. An event will be generated stating who returned the readers to the factory default settings. The <strong>Reset to Factory Defaults</strong> button only appears for users with the "Maintenance Override" operator privilege, and either the "Edit Site" or "View Site" operator privilege.<br><br><strong>Note:</strong> You should NOT re-encode Admin cards.</li></ol></td></tr></tbody></table>

</details>

5. Click the **FIDO2** sub-tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-dfa090c41da13577ae8388b003c204450a5ab31f%2Fcardsecuritytab_fido2subtab.png?alt=media)
6. The **FIDO2 MDS Root Certificate** section allows operators with the "Manage Keys" privilege to load a new MDS (Meta Data Service) Root Certificate.

   It displays the Embedded Certificate Name, Serial Number and Expiry Date. The **Update Certificate** button is used to load new certificates (when FIDO Alliance update their blob and sign it with certificate chained to a different root).

   **Note:** The **Update Certificate** button will be disabled if you do not have the "Manage Keys" privilege.

   1. Click the **Update Certificate** button.
   2. Locate and select the certificate you want.
   3. Click the **Apply** button to save the new certificate.

      The MDS Root Certificate will be validated once FIDO2 credentials are enrolled against a Cardholder.

      **Note:** An Invalid or expired certificate cannot be loaded. If attempted a warning message will display, (e.g. *"FIDO2 Certificate is not a valid PEM format"*, *"New FIDO2 MDS Root Certificate has expired"*).
7. Click the **OK** button.

### In This Section

* [MIFARE DESFire Key Migration](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/card-security/mifare-desfire-key-migration.md)
* [Identifying unmigrated cardholders after Key Migration](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/card-security/identifying-unmigrated-cardholders-after-key-migration.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/site-installation/server-properties/card-security.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.
