C.I.E – Carta di Identità Elettronica Functional Specification Version 2.0

More documents

Recommendations

Info

11. Security ArchitectureThe security architecture of the card is based on the following components:• Current Security Status• Access Conditions (AC)• Base Security Objects (BSO)• Current Security Environment (CSE)• Security Environment Object (SEO)Together, they set the rules for using the resources of the card.11.1 Access Conditions and Security StatusEvery command has specific security conditions to meet for its execution. The specific conditionsdepend on the current framework, and on the operation to perform.The information that links the object, the operation to control and the rules to apply is the AccessCondition (AC).An Access Condition can be attached to a file (EF, DF or MF), or to other card objects, as describedlater in the document. It tells in which status the card has to be in order to allow a specific operationon a specific object.The Access Conditions relative to an object are grouped in a byte string logically attached to theobject, where each byte is associated to one operation or to a group of operations, and can assumeone of the values in the next table:Byte Value Condition00h01h..1FhFFhALWAYSID of a BSONEVERTable 6: AC valuesThe values ALWAYS and NEVER mean that the operation is respectively always or never allowed.In the other cases, the value of the AC is the ID of a TEST BSO (see Section 11.2) that contains therules for the access.CIE - Functional Specification v 2.0 -Page 26/76
The card maintains an internal Security Status (Current Security Status) that records which accessconditions are granted at a given time. “The Current Security Status may be regarded as a set ofboolean conditions one for each TEST BSO to use”.By default, at card reset, all access rights are in the status ‘not granted’. The commands VERIFY,EXTERNAL AUTHENTICATE, RESET RETRY COUNTER may change the Current SecurityStatus, granting some rights, changing the value of a given boolean condition. In this case, we saythat the “access has been granted”, or that the “access condition has been verified”.Access Conditions related to files (MF, DF, EF) are represented by a 9-byte string, whose meaningis shown in the following tables:Byte Nr. ACProtected Commands1 RFU Reserved For Future Use2 AC_UPDATE PUT DATA (DATA_OCI)PUT DATA (DATA SECI)3 AC_APPEND PUT DATA (DATA_OCI)PUT DATA (DATA SECI)4 RFU Set to FFh5 RFU Set to FFh6 RFU Set to FFh7 AC_ADMIN PUT DATA (DATA FCI)8 AC_CREATE CREATE FILE9 RFU Reserved For Future Use (Set to FFh)Table 7: MF/DF AC codingByte Nr. ACProtected Commands1 AC_READ READ BINARYREAD RECORD2 AC_UPDATE UPDATE BINARYUPDATE RECORD3 AC_APPEND APPEND RECORDCIE - Functional Specification v 2.0 -Page 27/76
Page 1 and 2: C.I.E. - Carta di Identità Elettro
Page 3 and 4: Table of Contents1. Revision Histor
Page 5 and 6: 12.17 GENERATE KEY PAIR ...........
Page 7 and 8: 2. IntroductionThis document is the
Page 9 and 10: 4. Reference Documents1. ISO/IEC 78
Page 11 and 12: Public Key - That key of an entity
Page 13 and 14: lsbLSBMACMFmsbMSBMSEMTSCOSOCIPINPPP
Page 15 and 16: 6. Electrical ParametersFor all ele
Page 17 and 18: 8. Answer To Reset (ATR)The Answer
Page 19 and 20: XXh XXh H5/H6 Y02h H7 Y49h H8 Y54h
Page 21 and 22: 9. Application SelectionNo explicit
Page 23 and 24: Record structure:The EF is seen at
Page 25: Linear Variable TLV or Cyclic EFSiz
Page 29 and 30: BSO ID 1 01h to 1FhOPTION 1 See Tab
Page 31 and 32: RSA public key Exponent for Authent
Page 33 and 34: 11.4 Secure MessagingThe Secure Mes
Page 35 and 36: Byte Nr. SM Condition1 ENC USE IN2
Page 37 and 38: • Step 4: APDU command set up in
Page 39 and 40: 11.4.5 SM Response in SM_ENCOrigina
Page 41 and 42: 11.4.7 SM Response in SM_ENC_SIGOri
Page 43 and 44: 12. APDU ReferenceThe CIE supports
Page 45 and 46: 6A 86 Incorrect P1-P26A 87 Lc incon
Page 47 and 48: The PUT DATA - DATA_OCI acts on the
Page 49 and 50: 3DES - SM Cipher 10h 83h 03h3DES -
Page 51 and 52: 3 8Fh 6 BYTE 1: Not used - MUST be
Page 53 and 54: Table35Table 34: SELECT FILE Comman
Page 55 and 56: The operation is possible if the ac
Page 57 and 58: n has to be different from FFh.P1=0
Page 59 and 60: First and NextLast and PreviousSecu
Page 61 and 62: acktrackingallowed.b6 = 0b5 = 0b4 -
Page 63 and 64: 12.13 RESET RETRY COUNTERCLA INS P1
Page 65 and 66: 12.15 GIVE RANDOMCLA INS P1 P2 P3 D
Page 67 and 68: Security:The access condition to sa
Page 69 and 70: The access condition to satisfy is
Page 71 and 72: 0X 04 00 00 LC = 00 EmptyTable 59:
Page 73 and 74: • The length in bits of the priva
Page 75 and 76: • a sequence of q cipher text blo

C.I.E – Carta di Identità Elettronica Functional Specification Version 2.0

Create successful ePaper yourself

Delete template?

Save as template?