ISO/IEC 18014-2:2009 情報技術—セキュリティ技術—タイムスタンプサービス—パート2：独立したトークンを生成するメカニズム | ページ 5

3.1

asymmetric key pair

pair of related keys where the private key defines the private transformation and the public key defines the public transformation

Note 1 to entry: Adapted from ISO/IEC 9798-1.

3.2

asymmetric signature system

system based on asymmetric techniques whose private transformation is used for signing and whose public transformation is used for verification

Note 1 to entry: Adapted from ISO/IEC 9798-1.

3.3

authentication

provision of assurance of the claimed identity of an entity

Note 1 to entry: Adapted from ISO/IEC 18028-4.

3.4

certification authority

ca

authority trusted by one or more users to create and assign public-key certificates

Note 1 to entry: Optionally, the certification authority can create the users' keys.

[SOURCE: ISO/IEC 9594-8:2005, definition 3.3.16]

3.5

cryptography

discipline that embodies principles, means, and mechanisms for the transformation of data in order to hide its information content, prevent its undetected modification and/or prevent its unauthorized use

[SOURCE: ISO/IEC 7498-2:1989, definition 3.3.20]

3.6

data integrity

property that data has not been altered or destroyed in an unauthorized manner

[SOURCE: ISO/IEC 7498-2:1989, definition 3.3.21]

3.7

data origin authentication

corroboration that the source of data received is as claimed

[SOURCE: ISO/IEC 7498-2:1989, definition 3.3.22]

3.8

digital signature

data appended to, or a cryptographic transformation (see cryptography) of, a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery, e.g. by the recipient

[SOURCE: ISO/IEC 7498-2:1989, definition 3.3.26]

3.9

distinguished encoding rules

DER

encoding rules that may be applied to values of types defined using the ASN.1 notation

Note 1 to entry: As defined in the introduction to ISO/IEC 18028-4.

Note 2 to entry: Application of these encoding rules produces a transfer syntax for such values. It is implicit that the same rules are also to be used for decoding. The DER is more suitable if the encoded value is small enough to fit into the available memory and there is a need to rapidly skip over some nested values.

3.10

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.11

hash-value

string of bits which is the output of a hash-function

Note 1 to entry: Adapted from hash-code as defined in ISO/IEC 10118-1.

3.12

message authentication code

MAC

string of bits which is the output of a MAC algorithm

Note 1 to entry: A MAC is sometimes called a cryptographic check value (see for example ISO 7498-2).

[SOURCE: ISO/IEC 9797-1:1999, definition 3.2.4]

3.13

message authentication code (MAC) algorithm

Note 1 to entry: A MAC algorithm is sometimes called a cryptographic check function (see for example ISO 7498-2).

Note 2 to entry: Computational feasibility depends on the user's specific security requirements and environment.

[SOURCE: ISO/IEC 9797-1:1999, definition 3.2.6]

3.14

private key

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

[SOURCE: ISO/IEC 9798-1:1997, definition 3.3.17]

3.15

public key

that key of an entity's asymmetric key pair which can be made public

Note 1 to entry: In the case of an asymmetric signature scheme the public key defines the verification transformation. In the case of an asymmetric encipherment system the public key defines the encipherment transformation. A key that is 'publicly known' is not necessarily globally available. The key may only be available to all members of a pre-specified group.

[SOURCE: ISO/IEC 11770-3:2008, definition 3.32]

3.16

public key certificate

public key information of an entity signed by the certification authority and thereby rendered unforgeable

[SOURCE: ISO/IEC 11770-3:2008, definition 3.33]

3.17

time-stamp requester

entity which possesses data it wants to be time-stamped

[SOURCE: ISO/IEC 18014-1:2008, definition 3.14]

3.18

time-stamp token

TST

data structure containing a verifiable cryptographic binding between a data item's representation and a time-value

Note 1 to entry: A time-stamp token can also include additional data items in the binding.

[SOURCE: ISO/IEC 18014-1:2008, definition 3.15]

3.19

time-stamp verifier

entity which possesses data and wants to verify that it has a valid time-stamp bound to it

Note 1 to entry: The verification process can be performed by the verifier itself or by a trusted third party.

[SOURCE: ISO/IEC 18014-1:2008, definition 3.16]

3.20

time-stamping authority

TSA

trusted third party trusted to provide a time-stamping service

[SOURCE: ISO/IEC 18014-1:2008, definition 3.17]

3.21

time-stamping policy

named set of rules that indicates the applicability of a time-stamp token to a particular community or class of application with common security requirements

3.22

time-stamping service

TSS

service providing evidence that a data item existed before a certain point in time

[SOURCE: ISO/IEC 18014-1:2008, definition 3.18]

3.23

time-stamping unit

TSU

set of hardware and software which is managed as a unit and generates time-stamp tokens

3.24

trusted third party

security authority, or its agent, trusted by other entities with respect to security related activities

[SOURCE: ISO/IEC 10181-1:1996, definition 3.3.30]