What is MULTOS ? MULTOS is a Open Standard Multi Application Smart Card Platform • Trusted Assured security evaluated as highest level (ITSEC E6 high, EAL 4+) Strictly controlled key management architecture and card life cycle management • Proven Over 100M MULTOS cards issued, 12M cards in 2005 Secure dynamic downloading and post issuance over any channel • Open Multos ensure Interoperability across suppliers(single platform with multi source) Supported by the industry - application, personalization, system integrator, issuers Slide 1 Smart Card platform : Native OS Proprietary OS A The code is fixed in the ROM of the chip , and can not be changed after the chip is manufactured. Chip Hardware A Chip Hardware A EEPROM(E2) : Electrical Erasable Programmable Read Only Memory Slide 2 Data Native Native EMV EMV Code Code Native Loyalty Code Proprietary OS B Chip Hardware B Chip Hardware B ROM Native Loyalty Code Data E2 Native EMV Code ROM Proprietary Chip OS is developed in “native” code - specific to a particular silicon chip. Data E2 Data Smart Card platform : Standard OS Multos JAVA Develop application ONCE and run on ANY Multos ! Java Compiler MEL Editor C Compiler / Translator EMV EMV Open Standard OS is available in interoperable version from lots of different suppliers. MEL: MULTOS Executable Language Slide 3 Loyalty MULTOS API MULTOS VM Infineon Silicon ROM MULTOS API MULTOS VM PKI E2PROM Applications are loaded into the Programmable chip memory (EEPROM) , so can be changed or added to during the life of the card. Loyalty ROM PKI E2PROM API and Virtual Machine are defined chip hardware independently , and application can be load and execute on virtual machine in a standard manner. Renesas Silicon MULTOS Type approval Security and inter-operability are assured Maosco defines and TYPE APPROVES the multi-application smart card environment from end to end .(API, Virtual Machine & OS) It is independent 3rd party testing that provides the assurance of interoperability of MULTOS chip products. MULTOS KMA MULTOS specification scope API interoperability testing API On-card App On-card App Security Enforcing Features API ITSEC E6 High certification (Fire Wall) MULTOS Application Abstract Machine (MEL Virtual Machine) Type approve cryptographic implementations crypto functions OS Hardware ITSEC: Information Technology Security Evaluation Criteria, http://www.itsec.gov.uk Slide 4 On-card App Security / tamper resistance H/W evaluation Comparison between Multos and Java MULTOS is a real fully interoperable products OS Multos JAVA Interoperabilit Interoperability is assured No organization assure y by MAOSCO interoperability Key management Card life cycle scheme is totally managed by Multos KMA Post issuance Dynamic downloading is available Security Card life cycle is defined by issuer Not ready Required ITSEC E6 High (Fire wall) Optional(No regulation) KMA:key Management Authority Slide 5 Secure Network is not required Multos application is distributed in a confidential format Multos Scheme Other Schemes Secure Session Secure Packet Content Provider Content Provider Secure Channel Packet Mobile Device 1:1 Slide 6 Download Email Physical Mail Remote Site Pickup Mobile Device Scale 1:1 or 1:Many Real Time Online Connection Real Time or Non Real Time Online or Offline Secures the Transport Technology Secures the Transport, Data, and Access Why MULTOS ? Great advantage of adopting MULTOS MULTOS personalization mechanism is the same for all MULTOS implementations, so issuers are never locked-in to a supplier If the issuer wishes to have second source. Cost effective Branch Issuance is available. (Field proven post-issuance = no need to re-issue) applications written once run anywhere without change Slide 7 MAOSCO Multi-Application Operating System Consortium MAOSCO is a not-for-profit company MAOSCO Ltd. role to support and promote the MULTOS operating system consortium (exhibitions, conferences, press, industry forums) Manages the development of MULTOS specifications (Documents, Type Approves, & Licenses MULTOS) Consortium role to control, evolve and ensure MULTOS open standard Slide 8 on behalf of the StepNexus - Introduction StepNexus - Secure Trusted Environment Provisioning – nexus - “a means of connection between things, persons or events” StepNexus - Formed in November 2005 –Joint venture between MasterCard International, Keycorp, Hitachi and Oak Hill Venture Partners –Acquired IP and operations for: •MULTOS – world’s highest security, open standard smart card platform •Global MULTOS Key Management Authority (KMA) –Assumes the management of the secretariat of the 16-member MULTOS Consortium •Consortium will continue to develop MULTOS as an open std. smart card platform Slide 9 StepNexus & MAOSCO Consortium MAOSCO Ltd Slide 10 StepNexus holding company now owns MULTOS IP, MAOSCO Ltd and the MULTOS KMA operation MAOSCO Ltd – the holding company that manages the “MULTOS” multi-application smart card operating system standard MAOSCO Consortium will continue to build products and govern MULTOS as an “open standard”. MULTOS scheme -Issuer Centric Model- Issuer Registration Card Issuer MULTOS Application AP Slide 11 MULTOS KMA Card Issuer Control ‘owner’ of the card has full control over application loading and deletion Card Issuer requests certificates from the MULTOS KMA Card Issuer can distribute certificates in order for 3rd parties to load applications Application Load Certificate (ALC) + Interoperability and Application Portability FULL specification coverage for all aspects of smart card operation - AAM, load, delete, etc… guaranteed by MAOSCO Type Approval process MULTOS scheme - post issuance MULTOS Application MULTOS supports all these requirements today • Confidentiality and Integrity guaranteed – during pre-issuance loading, post-issuance loading, over insecure channels – on-card confidentiality and integrity maintained by firewalled environment • MULTOS Application MULTOS Application MULTOS Application Open, competitive MULTOS marketplace – non-discriminatory licensing – only ‘MULTOS OS’ license is chargeable – multiple supply sources – silicon manufacture, MULTOS implementations, card manufacture, applications, development tools, consulting services, etc... Slide 12 MULTOS KMA & Issuer managing the card lifecycle Protected Card Chip Manufacture Module Manufacture MULTOS KMA Delete Permissions Card Expiry Slide 13 Application Deletion Card Manufacture Enablement Data Card Issuer ADC ALC Card Enablement Enabled Card Card Physical Customisation Load Permissions Application Usage Application Loading & Customisation Application Load & Delete Overview Application Load Unit (ALU) Application Load Certificate (ALC) CODE DATA MULTOS Silicon (Hardware) Application Delete Certificate (ADC) Slide 14 MULTOS Codelets ■ Divide application into two areas , code and data, and store program in ROM as “codelet”. Then, only stub program which call Codelet can be stored in EEPROM and utilize EEPROM. EEPROM Application M/chip stub Codelet M/chip codelet Cash card Finger Vein stub stub Cash card Finger Vein codelt codelet ROM MULTOS OS Finger Vein app Application M/chip Cash card stub stub Codelet M/chip Cash card codelet codelt EEPROM ROM MULTOS OS Utilize Finger Vein codelet App without Finger Vein codelet (EEPROM contains only data area) (EEPROM contains code and data area) Slide 15 Architecture Read/write access Key Features • MULTOS apps can communicate over ISO compatible ISO Type A & B interfaces • Delegation between MEL Contact & C’less apps possible Contact- Contactless- Contact or only only Contactless Application Application Application • Simple MULTOS apps possible • RSA can be supported MULTOS API • Native contactless OS (e.g. Mifare1 OS) separate to MULTOS. MULTOS applications has R/W access to Mifare1 memory but Mifare has NO access to MULTOS memory) MULTOS VM T=0, T=1 Contact 7816 T=CL C’Less 14443 B Silicon chip Mifare 1 functions T=Mifare1 C’Less 14443 A Platform requirements of EMV card issuers EMV Biometrics Access control ID Health care ID ID Bank/Cash Ability to support all current applications Ability to support EMV with SDA and DDA/CDA Security to pass certification requirements of international bodies Ability to develop own applications and add them later Future proofed technology that will not become obsolete MULTOS supports all these requirements today Slide 17 Passport Transit ID Loyalty ID MULTOS Issuance Partner (MIP) • • • The MIP was introduced by the Global MULTOS KMA, in order to simplify the process of issuing MULTOS cards. Card Issuers may choose to have an indirect relationship with the Global MULTOS KMA, via a MULTOS Issuance Partner. These organizations are usually card manufacturers or data processing services who are experienced with the MULTOS scheme, and perform the day-to-day processing of MULTOS smart card enablement and application certificate requests on behalf of the Card Issuer. MIP M-SPI Card Bureau M-SPI : MULTOS Service Provider Interface Slide 18
© Copyright 2024