> 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/cc-hardware/credentials/mifare-technologies.md).

# MIFARE technologies

Compare MIFARE card variants supported by Command Centre and understand DESFire security features.

Command Centre supports the full range of MIFARE card technologies. This page compares supported variants and explains why DESFire suits new sites.

### Supported variants

| Variant                  | Status                                                  |
| ------------------------ | ------------------------------------------------------- |
| MIFARE Classic           | Supported, **not recommended** (compromised since 2008) |
| MIFARE Plus              | Supported                                               |
| MIFARE Plus S and Plus X | Supported                                               |
| MIFARE DESFire EV1       | Supported from vEL7.00                                  |
| MIFARE DESFire EV2       | Supported from vEL7.60                                  |
| MIFARE DESFire EV3       | Supported from vEL8.30                                  |

### DESFire

DESFire is the recommended technology for new sites. It has no known compromises at publication.

DESFire has the following features:

* **File-system architecture.** Applications (folders) each have independent encryption keys.
* Third parties cannot access the Gallagher-encoded folder without its [Site Specific Key (SSK)](/knowledge-hub/products/cc-hardware/credentials/credential-information/credentials-site-specific-key-ssk-vs-d.md).
* Up to **15 Gallagher objects** can coexist on a single card. Each one requires a unique Facility Code and SSK.
* Command Centre does **not** prevent third parties from writing additional application folders to a card it has encoded.

***

🔗 **Related**

* [Credentials - Keys](/knowledge-hub/products/cc-hardware/credentials/credential-information/credentials-keys.md). The Card Master Key, Default Application Key, and where to find them.
* [Credentials - Non Diversified DESFire object](/knowledge-hub/products/cc-hardware/credentials/credential-information/credentials-non-diversified-desfire-ob.md). Writing an object third parties can read without the Gallagher object keys.
* [Legacy Credentials](/knowledge-hub/products/cc-hardware/credentials/legacy-credentials.md). MIFARE Classic and the older technologies retained for backwards compatibility.


---

# 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/cc-hardware/credentials/mifare-technologies.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.