Smart Cards: Technology for Secure Management of Information

Please download to get full document.

View again

of 37
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Similar Documents
Information Report
Category:

Documents

Published:

Views: 56 | Pages: 37

Extension: PDF | Download: 0

Share
Description
Smart Cards: Technology for Secure Management of Information . By- Saurabh pratap singh Pccs college gr.noida. Agenda. Machine readable plastic cards What are smart cards Security mechanisms Applications SCOSTA experience Indian Driving License application. Plastic Cards.
Transcript
Smart Cards: Technology for Secure Management of Information By-SaurabhpratapsinghPccs college gr.noidaAgendaMachine readable plastic cardsWhat are smart cardsSecurity mechanismsApplicationsSCOSTA experienceIndian Driving License applicationPlastic Cards
  • Visual identity application
  • Plain plastic card is enough
  • Magnetic strip (e.g. credit cards)
  • Visual data also available in machine readable form
  • No security of data
  • Electronic memory cards
  • Machine readable data
  • Some security (vendor specific)
  • Smart Cards
  • Processor cards (and therefore memory too)
  • Credit card size
  • With or without contacts.
  • Cards have an operating system too.
  • The OS provides
  • A standard way of interchanging information
  • An interpretation of the commands and data.
  • Cards must interface to a computer or terminal through a standard card reader.
  • Smart Cards devicesGNDVCCVPPResetI/OClockReservedWhat’s in a Card?CLKRSTVccRFUGNDRFUVppI/OTypical Configurations256 bytes to 4KB RAM.8KB to 32KB ROM.1KB to 32KB EEPROM.Crypto-coprocessors (implementing 3DES, RSA etc., in hardware) are optional.8-bit to 16-bit CPU. 8051 based designs are common.The price of a mid-level chip when produced in bulk is less than US$1.Smart Card Readers
  • Dedicated terminals
  • Usually with a small screen, keypad, printer, often alsohave biometric devices such as thumb print scanner.
  • Computer based readers
  • Connect through USB or COM (Serial) portsTerminal/PC Card Interaction
  • The terminal/PC sends commands to the card (through the serial line).
  • The card executes the command and sends back the reply.
  • The terminal/PC cannot directly access memory of the card
  • data in the card is protected from unauthorized access. This is what makes the card smart.
  • Communication mechanisms
  • Communication between smart card and reader is standardized
  • ISO 7816 standard
  • Commands are initiated by the terminal
  • Interpreted by the card OS
  • Card state is updated
  • Response is given by the card.
  • Commands have the following structure
  • Response from the card include 1..Le bytes followed by Response Code
  • Security Mechanisms
  • Password
  • Card holder’s protection
  • Cryptographic challenge Response
  • Entity authentication
  • Biometric information
  • Person’s identification
  • A combination of one or more
  • Password Verification
  • Terminal asks the user to provide a password.
  • Password is sent to Card for verification.
  • Scheme can be used to permit user authentication.
  • Not a person identification scheme
  • Cryptographic verification
  • Terminal verify card (INTERNAL AUTH)
  • Terminal sends a random number to card to be hashed or encrypted using a key.
  • Card provides the hash or cyphertext.
  • Terminal can know that the card is authentic.
  • Card needs to verify (EXTERNAL AUTH)
  • Terminal asks for a challenge and sends the response to card to verify
  • Card thus know that terminal is authentic.
  • Primarily for the “Entity Authentication”
  • Biometric techniques
  • Finger print identification.
  • Features of finger prints can be kept on the card (even verified on the card)
  • Photograph/IRIS pattern etc.
  • Such information is to be verified by a person. The information can be stored in the card securely.
  • MFEFDFDFEFEFDFEFEFData storage
  • Data is stored in smart cards in E2PROM
  • Card OS provides a file structure mechanism
  • File typesBinary file (unstructured)Fixed size record fileVariable size record fileFile Naming and Selection
  • Each files has a 2 byte file ID and an optional 5-bit SFID (both unique within a DF). DFs may optionally have (globally unique) 16 byte name.
  • OS keeps tack of a current DF and a current EF.
  • Current DF or EF can be changed using SELECT FILE command. Target file specified as either:
  • DF name
  • File ID
  • SFID
  • Relative or absolute path (sequence of File IDs).
  • Parent DF
  • Basic File Related Commands
  • Commands for file creation, deletion etc., File size and security attributes specified at creation time.
  • Commands for reading, writing, appending records, updating etc.
  • Commands work on the current EF.
  • Execution only if security conditions are met.
  • Each file has a life cycle status indicator (LCSI), one of: created, initialized, activated, deactivated, terminated.
  • Access control on the files
  • Applications may specify the access controls
  • A password (PIN) on the MF selection
  • For example SIM password in mobiles
  • Multiple passwords can be used and levels of security access may be given
  • Applications may also use cryptographic authentication
  • An example scenario (institute ID card)Read: FreeWrite: upon verification by K1, K2 or K3What happens if the user forgets his password?Solution1: Add supervisor passwordSolution2: Allow DOSA/DOFA/Registrar to modify EF3Solution3: Allow both to happenSelect: P2 verificationSecurity requirements:EF1: Should be modified only by the DOSA/DOFA/RegistrarReadable to allEF2:Card holder should be able to modifyEF1 (personal data)Name: Rajat MoonaPF/Roll: 2345MFRead: FreeWrite: Password Verification (P1)EF2 (Address)#320, CSE (off)475, IIT (Res)EF3 (password)P1 (User password)EF3 (password)P1 (User password)P2 (sys password)EF4 (keys)K1 (DOSA’s key)K2 (DOFA’s key)K3 (Registrar’s key)Read: NeverWrite: OnceRead: NeverWrite: Password Verification (P1)Bk#Bk#Bk#Bk#dt issuedt issuedt issuedt issuedt retndt retndt retndt retnAn example scenario (institute ID card)EF1 (personal data)Library manages its own keys in EF3 under DF1Institute manages its keys and data under MFThus library can develop applications independent of the rest.EF2 (Address)MFEF3 (password)EF4 (keys)Modifiable: By admin staff. Read: allDF1 (Lib)EF2 (Privilege info)Max Duration: 20 daysMax Books: 10Reserve Collection: YesEF1 (Issue record)EF3: KeysK1: Issue staff keyK2: Admin staff keyModifiable: By issue staff. Read allHow does it all work?Card is inserted in the terminalCard gets power. OS boots up. Sends ATR (Answer to reset)ATR negotiations take place to set up data transfer speeds, capability negotiations etc.Terminal sends first command to select MFCard responds with an error (because MF selection is only on password presentation)Terminal prompts the user to provide passwordCard verifies P2. Stores a status “P2 Verified”. Responds “OK”Terminal sends password for verificationCard responds “OK”Terminal sends command to select MF againCard supplies personal data and responds “OK”Terminal sends command to read EF1Another Application ScenarioTerminal withtwo card readersApplicationsoftware runshere1. Authenticate user to bank officer card: 1a. Get challenge from banker card. 1b. Obtain response for the challenge from passport (IAUTH). 1c. Validate response with officer card (EAUTH)2. Authenticate officer card to passport.3. Transfer money to the user’s cardUser’s cardBanker’s cardThe terminal itself does not store any keys, it’s the two cards that really authenticate each other. The terminal just facilitates the process.Status of smart card deployments
  • Famous Gujarat Dairy card
  • Primarily an ID card
  • GSM cards (SIM cards for mobiles)
  • Phone book etc. + authentication.
  • Cards for “credit card” applications.
  • By 2007 end all credit cards will be smart.
  • EMV standard
  • Card for e-purse applications
  • Bank cards
  • Card technology has advanced
  • Contactless smart cards,
  • 32-bit processors and bigger memories
  • JAVA cards
  • SCOSTA Experience
  • Part of E-governance initiative of the Government.
  • Government decided to
  • Create Smart driving licenses/registration certificate
  • Backend system is already in place
  • Various smart card vendors in the country
  • All with their own proprietary solutions
  • In a national case, proprietary solution was not acceptable.
  • NIC decides to ask IIT Kanpur to help.
  • SCOSTA: Smart Card OS for Transport ApplicationsGoals of this ProjectTo define a standard set of commands for smart cards for use in Indian applications.To provide a reference implementation of this standard.Transport Applications (Driving License and Vehicle Registration Certificate) were the pilot projects.Hence the OS standard is named SCOSTA.SCOSTA is defined by IIT Kanpur along with a technical subcommittee of SCAFI (Smart Card Forum of India).The OS is not really restricted to the transport applications and can be used in any ID applicationThe SCOSTA StandardBased on ISO 7816-4, -8, and -9.Removes ambiguities in ISO 7816.Has support for symmetric key cryptography (Triple DES algorithm) and internal and external authentication.Encryption/decryption and crypto checksum computation and verification using 3DES are also supported.SCOSTA Implementation - ChallengesPortability – should be easy to port to different processors.Resource Constraints – very limited memory (32 KB ROM, 512 byte RAM are typical). Usually 8 bit processors are used.Government processesVendors and their business interests.Challenges of the application
  • System must work nation wide
  • Cards are issued by the RTO
  • RTO officials may not be all that “clean”
  • Challans are done by police “on behalf of” RTO
  • “Clean”??
  • Challans are settled by the Judiciary.
  • RTOs are administered by the STA
  • But under the Union Ministry
  • Solution
  • A robust key management scheme was needed.
  • Solution was based on
  • Key derivations, usage counters etc.
  • Solution
  • The entire system is based on few “nation wide” generator keys.
  • Safely housed with the government.
  • Say the keys are k1, k2, k3, k4.
  • Keys are themselves never stored any where.
  • Instead five out of seven card scheme is used.
  • 5 out of 7 schemeConsider a polynomial k1 + k2.x + k3.x2 + k4.x3 + k5.x4 = bIf b1, b2, b3, b4, b5 are known for x = 1, 2, 3.., the system of equations can be solved and all k’s can be found.We use the SCOSTA cards to store (x1, b1), (x2, b2) etc.At any point in time, five such pairs are needed.For robustness, seven cards are generated and kept at 7 different locations.Operations
  • At RTOs, two RTO officers are required to create a DL
  • These two work in pair.
  • Have a usage counter of key built in.
  • RTO keys are generated and given in the RTO cards
  • STA can revalidate the usage counter.
  • STA keys are also generated.
  • OperationsDL can be completely given by the RTO.Some information is public readable on the DL.Some information is once writable by the police (challans) and readable by the police.The same information is updatable by the judiciary. (but can not be deleted)Operations
  • Therefore the DLs must carry
  • Police key, RTO keys and judiciary keys.
  • A big security risk.
  • Instead these keys for the DL are card specific.
  • Police has a master key to generate DL specific police key. Ditto with RTO and Judiciary.
  • NIC generates the cards (and therefore master keys) for RTO, Police and Judiciary.
  • AcknowledgementsProf. Deepak Gupta and Manindra Agrawal (CSE)S. Ravinder and Kapileshwar Rao (MTech students of CSE who worked on this project)National Informatics Centre (NIC) DelhiMCIT and MoSTReferences:Smart Card HandbookISO7816 standardswww.parivahan.nic.inQuestions are invited?Thanking you
    Recommended
    We Need Your Support
    Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

    Thanks to everyone for your continued support.

    No, Thanks
    SAVE OUR EARTH

    We need your sign to support Project to invent "SMART AND CONTROLLABLE REFLECTIVE BALLOONS" to cover the Sun and Save Our Earth.

    More details...

    Sign Now!

    We are very appreciated for your Prompt Action!

    x