Assets

Assets

1. CMS Pub Key

   • gen in the backend

2. RGK

   • gen in the client
   • encrypted using CMS Pub Key

3. Mobile Keys

   • gen in the backend
   • used to encrypt communication with the backend
   • encrypted using RGK to send to client
   • main output of the bootstrap
   • Transport Key
     • enc payload
   • Data Encryption Key
     • enc sensitive data
   • MAC Key
     • integrity/authenticity
   • Mobile Session Keys
     • enc/dec payload
     • only in session context

4. Session Code

   • received via RNS (push)
   • used to calculate session keys
   • used to gen Authentication Code

5. Authentication Code

   • derived from
     • dev fingerprint
   • used for securing HTTP comm with CMS

6. ICC KEK

   • used to enc ICC Private Key

7. ICC Private Key

   • used to sign CDA Transactions
   • comes in card profile

8. Session Keys

   • used for dev auth
   • unique for each transaction

9. Single Use Key

   • used for dev and user auth (if used)
   • unique for each transaction
   • combined with PIN code (prev registered with the server

10. ATC

    • Unique counter

11. IDN

    • Random number used in transaction processing

12. PIN

    • req during the transaction processing

13. Dev fingerprint

    • unique for device
    • registered with the backend

14. PAS Keys

    • used in comm with PAS Server
    • PAS comm proto is proprietary (not covered by MP SDK)

15. CPE

    • The CPE is not responsible for the storage of encrypted assets (this is the role of the database component) but the API is designed so that outside of the component sensitive assets are always encrypted and need to be passed back into the CPE in order to be used. The idea is that a suitably hardened (securing a system by reducing its surface of vulnerability) implementation of the CPE, taken together with the guidance provided in this document can be a major step forward in creating a hardened MPA
    • Data Storage Key
      • enc all data at rest in the SDK storage
    • Data Storage MAC key
      • integrity for data at rest in SDK
    • Remote Mgnt KEK
      • enc keys used for backend comm
    • Local DEK
      • re-encrypt all data encrypted with DEK (in transit?)
    • Wallet DEK
      • the SDK only accepts data from the MPA encrypted with this key
      • E.g: PIN, Dev Fingerprint.
    • contains KEK for (almost) all other keys