Scribd Logo
Upload

Welcome to Scribd!

  • 1470 Token - DESFire Technology

    Uploaded by

    spiros-rianelis kyriazatis
    8 views1 page
    This document specifies requirements for contactless smart cards using Mifare DESFire technology. The cards must use DESFire EV2 and AES-128 encryption to protect the encoded card data, which includes the assigned card number and a 48-character site-specific key sourced from an optional customer key-safe. Card encoding is required as part of the card production process, and the application and DESFire unlock keys must be user-definable.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This document specifies requirements for contactless smart cards using Mifare DESFire technology. The cards must use DESFire EV2 and AES-128 encryption to protect the encoded card data, which includes the assigned card number and a 48-character site-specific key sourced from an optional customer key-safe. Card encoding is required as part of the card production process, and the application and DESFire unlock keys must be user-definable.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    8 views1 page

    1470 Token - DESFire Technology

    Uploaded by

    spiros-rianelis kyriazatis
    This document specifies requirements for contactless smart cards using Mifare DESFire technology. The cards must use DESFire EV2 and AES-128 encryption to protect the encoded card data, which includes the assigned card number and a 48-character site-specific key sourced from an optional customer key-safe. Card encoding is required as part of the card production process, and the application and DESFire unlock keys must be user-definable.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    <SpecificationName>

    1. Token – Mifare DESFire Technology

    1.1. The cards shall incorporate DESFire technology.

    1.2. The card number must be a number specifically encoded to an application on the card.
    It shall not be the CSN.

    1.3. The card data encoded shall use a secure sector authentication level of security to
    protect against card cloning. AES-128 shall be used.

    1.4. The DESFire EV2 variant shall be provided.

    1.5. The encoded card data shall incorporate data consisting of:

    1.5.1. the assigned card number.

    1.5.2. a site-specific key consisting of 48 hexadecimal characters.

    1.6. The 48 hexadecimal key shall optionally be sourced from a customer specified key-safe

    1.7. Card encoding shall be an integral part of card production.

    1.8. The application unlock key and the DESFire CAD unlock key shall be user definable.

    <SpecDate> Page 1

    You might also like