ISO/IEC 7816-4:2020 識別カード—集積回路カード—パート4：組織、セキュリティ、および交換のためのコマンド | ページ 6

3.1

access rule

data element (3.15) containing an access mode referring to an action and security conditions to fulfil before acting

3.2

Answer-to-Reset file

information file

EF.ATR/INFO

optional EF (3.22) indicating operating characteristics of the card

3.3

application

structures (3.55) , data elements (3.15) and program modules needed for performing a specific functionality

3.4

application DF

dedicated file ( DF (3.18) ) hosting an application (3.3) in a card

3.5

application identifier

AID

data element (3.15) (up to sixteen bytes) that identifies an application (3.3)

3.6

application label

data element (3.15) for use at the man-machine interface

3.7

application provider

entity providing the components that make up an application (3.3) in the card

3.8

application template

set of application-relevant data objects (3.16) including one application identifier (3.5) data object (3.16)

3.9

asymmetric cryptographic technique

cryptographic technique that uses two related operations: a public operation defined by public numbers or by a public key (3.41) and a private operation defined by private numbers or by a private key (3.39)

Note 1 to entry: The two operations have the property that, given the public operation, it is computationally infeasible to derive the private operation.

3.10

base template

value field of constructed data object (3.16) excluding DOs resulting from resolution of indirect referencing

3.11

certificate

digital signature (3.20) binding a particular person or object (3.32) and its associated public key (3.41)

Note 1 to entry: The entity issuing the certificate also acts as tag allocation authority with respect to the data elements in the certificate.

3.12

command-response pair

C-RP

set of two messages at the interface: a command APDU followed by a response APDU in the opposite direction

3.13

command chaining

means used by the outside world to tell the card that the command data of a sequence of successive command-response pairs (3.12) shall be processed together

3.14

context-specific class

class of a tag with its first or only byte from '80' to 'BF'

3.15

data element

item of information seen at the interface for which are specified a name, a description of logical content, a format and a coding

3.16

data object

information seen at the interface consisting of the concatenation of a mandatory tag field, a mandatory length field and a conditional value field

3.17

data unit

smallest set of bits that can be unambiguously referenced within an EF (3.22) supporting data units

3.18

dedicated file

DF

structure (3.55) containing file control information and, optionally, memory available for allocation

3.19

DF name

data element (3.15) (up to sixteen bytes) that uniquely identifies a DF (3.18) in the card

3.20

digital signature

data appended to, or cryptographic transformation of, a data string that proves the origin and the integrity of the data string and protects against forgery, e.g. by the recipient of the data string

3.21

directory file

EF.DIR

optional EF (3.22) containing a list of applications (3.3) supported by the card and optional related data elements (3.15)

3.22

elementary file

EF

set of data units (3.17) or records (3.42) or data objects (3.16) sharing the same file identifier (3.26)

3.23

extended header

data element (3.15) referencing one or several DOs in a constructed DO

3.24

extended header list

concatenation of extended headers (3.23)

3.25

file

structure (3.55) for application (3.3) and/or data in the card, as seen at the interface when processing commands

3.26

file identifier

data element (3.15) (two bytes) used to address a file (3.25)

3.27

header list

concatenation of pairs of tag field and length field without delimiter

3.28

interindustry

items specified in the ISO/IEC 7816 ^[4] series

3.29

internal EF

EF (3.22) for storing data interpreted by the card

3.30

key

sequence of symbols controlling a cryptographic operation

3.31

master file

MF

unique DF (3.18) representing the root in a card using a hierarchy of DFs (3.18)

3.32

object

structure (3.55) plus security object (3.52)

3.33

offset

number sequentially referencing a data unit (3.17) in an EF (3.22) supporting data units (3.17) , or a byte in a record (3.42)

3.34

oversize payload

payload (3.38) which exceeds the current size constraints of the APDU

3.35

parent file

DF (3.18) immediately preceding a given file (3.25) within a hierarchy of DFs (3.18)

3.36

password

data that may be required by the application (3.3) to be presented to the card by its user (3.63) for authentication purpose

3.37

path

concatenation of file identifiers (3.26) without delimiter

3.38

payload

data of arbitrary length, to be sent to the card or by the card, in order to be processed together

3.39

private key

key (3.30) of an entity's asymmetric key pair which should only be used by that entity

3.40

provider

authority who has or who obtained the right to create a DF (3.18) in the card

3.41

public key

key (3.30) of an entity's asymmetric key pair that can be made public

3.42

record

string of bytes referenced and handled by the card within an EF (3.22) supporting records

3.43

record identifier

number used to reference one or more records (3.42) within an EF (3.22) supporting records

3.44

record number

sequential number that uniquely identifies each records (3.42) within an EF (3.22) supporting records

3.45

registered application provider identifier

RID

data element (3.15) (five bytes) that uniquely identifies an application provider (3.7)

3.46

resetting code

data to be presented to a card in order to modify the value of a counter

3.47

response chaining

means used by the card to tell the outside world that the response data of any command-response pair (3.12) followed by the response data of a sequence of get response command-response pairs should be processed together

3.48

secret key

key (3.30) used with symmetric cryptographic techniques (3.56) by a set of specified entities

3.49

secure messaging

sm

set of means for cryptographic protection of (parts of) command-response pairs (3.12)

3.50

security attribute

condition of use of objects (3.32) in the card including stored data and data processing functions, expressed as a data element (3.15) containing one or more access rules (3.1)

3.51

security environment

se

set of components required by an application (3.3) in the card for secure messaging (3.49) or for security operations

3.52

security object

standalone object nested in an EF (3.22) , a record (3.42) , a data object (3.16) , a DataString or a combination thereof that endorses security handling according to this document

3.53

self-controlled DO

constructed DO which nests at least a DO'62' nesting security attributes (3.50)

3.54

short EF identifier

data element (3.15) (five bits) used to address an elementary file

3.55

structure

DF (3.18) , EF (3.22) , record (3.42) , DataString or DO

3.56

symmetric cryptographic technique

cryptographic technique using the same secret key (3.48) for both the originator's and the recipient's operation (without the secret key, it is computationally infeasible to compute either operation)

3.57

tag list

concatenation of tag fields without delimiter

3.58

tagged wrapper

wrapper (3.67) which provides a tag for local addressing of the DO it references

3.59

template

concatenation of ber-tlv data objects (3.16) , forming the value field of a constructed ber-tlv data object (3.16)

3.60

template extension

part of the value field of a constructed DO resulting from automatic resolution of indirect referencing

3.61

transient selection

structure (3.55) selection needed when performing a C-RP (3.12) , the success of which will not modify the current validity area (3.64)

3.62

transient VA

validity area (3.64) set transiently during execution of a command which handles DOs

3.63

user

user of the card, also known as cardholder

3.64

validity area

VA

result of all successful selections performed on a logical channel

3.65

virtual root DO

virtual constructed DO'7F70' made current by the selection of a file (3.25) , a record (3.42) or a DataString supporting DO handling

3.66

working EF

EF (3.22) for storing data not interpreted by the card

3.67

wrapper

concatenation of DOs referencing a DO