ISO/IEC 29192-4:2013 情報技術—セキュリティ技術—軽量暗号化—パート4：非対称技術を使用したメカニズム | ページ 6

3.1

asymmetric cryptographic technique

cryptographic technique that uses two related operations: a public operation defined by a public data item, and a private operation defined by a private data item

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

[SOURCE:ISO/IEC 9798-5:2009, definition 2.3]

3.2

asymmetric pair

two related data items where the private data item defines a private operation and the public data item defines a public operation

[SOURCE:ISO/IEC 9798-5:2009, definition 2.5]

3.3

challenge

procedure parameter used in conjunction with secret parameters to produce a response

[SOURCE:ISO/IEC 9798-5:2009, definition 2.6]

3.4

claimant

entity whose identity can be authenticated, including the functions and the private data necessary to engage in authentication exchanges on behalf of a principal

[SOURCE:ISO/IEC 9798-5:2009, definition 2.7]

3.5

claimant parameter

public data item, number or bit string, specific to a given claimant within the domain

[SOURCE:ISO/IEC 9798-5:2009, definition 2.9]

3.6

collision-resistant hash-function

hash-function satisfying the following property: it is computationally infeasible to find any two distinct inputs which map to the same output

Note 1 to entry: computational feasibility depends on the specific security requirements and environment.

[SOURCE:ISO/IEC 10118-1:2000, definition 3.2]

3.7

coupon

pair of pre-computed numbers to be used only once

Note 1 to entry: One of the numbers shall be kept secret, and the other shall remain secret until the time of use.

[SOURCE:ISO/IEC 9798-5:2009, definition 2.8, modified]

3.8

domain

collection of entities operating under a single security policy

Note 1 to entry: For instance, public key certificates created either by a single certification authority, or by a collection of certification authorities using the same security policy.

[SOURCE:ISO/IEC 9798-5:2009, definition 2.11]

3.9

domain parameter

public key, or function, agreed and used by all entities within the domain

[SOURCE:ISO/IEC 9798-5:2009, definition 2.12]

3.10

entity authentication

corroboration that an entity is the one claimed

[SOURCE:ISO/IEC 9798-1:2010, definition 3.14]

3.11

exchange multiplicity parameter

number of exchanges of information involved in one instance of an authentication mechanism

[SOURCE:ISO/IEC 9798-5:2009, definition 2.15]

3.12

hash-function

Note 1 to entry: Computational feasibility depends on the specific security requirements and environment.

[SOURCE:ISO/IEC 10118-1:2000, definition 3.5]

3.13

master secret key

secret data item

Note 1 to entry: Master secret key should only be used by the trusted server in accordance with the process of generation of signer private data.

3.14

private key

private data item of an asymmetric pair

Note 1 to entry: Private key shall be kept secret and should only be used by a claimant in accordance with an appropriate response formula, thereby establishing its identity.

[SOURCE:ISO/IEC 9798-5:2009, definition 2.21]

3.15

procedure parameter

transient public data item used in an instance of an authentication mechanism, e.g. a witness, challenge or response

[SOURCE:ISO/IEC 9798-5:2009, definition 2.22]

3.16

public key

public data item of an asymmetric pair, that can be made public and shall be used by every verifier for establishing the claimant's identity

[SOURCE:ISO/IEC 9798-5:2009, definition 2.23]

3.17

random number

time variant parameter whose value is unpredictable

[SOURCE:ISO/IEC 9798-1:2010, definition 3.29]

3.18

response

procedure parameter produced by the claimant, and processed by the verifier for checking the identity of the claimant

[SOURCE:ISO/IEC 9798-5:2009, definition 2.25]

3.19

secret parameter

number or bit string that does not appear in the public domain and is only used by a claimant

Note 1 to entry: For instance, a private key.

[SOURCE:ISO/IEC 9798-5:2009, definition 2.26]

3.20

sign

signature generation process that takes a message and a signing key of a signer to produce a signature

3.21

signer

entity with a unique bit string as an identity, including the functions and the private data necessary to engage in generation of a signature

3.22

signing key

secret data item given by the trusted server

Note 1 to entry: Signing key should only be used by a signer in accordance with the process of generation of a signature.

3.23

token

message consisting of data fields relevant to a particular communication and which contains information that has been produced using a cryptographic technique

[SOURCE:ISO/IEC 9798-5:2009, definition 2.27]

3.24

unilateral authentication

entity authentication which provides one entity with assurance of the other's identity but not vice versa

[SOURCE:ISO/IEC 9798-1:2010, definition 3.39]

3.25

verifier

entity including the functions necessary for engaging in authentication exchanges on behalf of an entity requiring an entity authentication or for engaging in verifying a signature of a given message and signer

[SOURCE:ISO/IEC 9798-5:2009, modified ─ Added the signature verification case]

3.26

verify

verification process that takes a message, a signature and an identity of a signer to output accept meaning the given signature is generated by the signer with the corresponding signing key, or reject otherwise

3.27

witness

procedure parameter that provides evidence of the claimant's identity to the verifier

[SOURCE:ISO/IEC 9798-5:2009, definition 2.31]