ISO/IEC 9798-3:1998/Amd 1:2010
(Amendment)Information technology — Security techniques — Entity authentication — Part 3: Mechanisms using digital signature techniques — Amendment 1: .
Information technology — Security techniques — Entity authentication — Part 3: Mechanisms using digital signature techniques — Amendment 1: .
Technologies de l'information — Techniques de sécurité — Authentification d'entité — Partie 3: Mécanismes utilisant des techniques de signature numériques — Amendement 1: .
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 9798-3
Second edition
1998-10-15
AMENDMENT 1
2010-06-01
Information technology — Security
techniques — Entity authentication —
Part 3:
Mechanisms using digital signature
techniques
AMENDMENT 1
Technologies de l'information — Techniques de sécurité —
Authentification d'entité —
Partie 3: Mécanismes utilisant des techniques de signature numériques
AMENDEMENT 1
Reference number
ISO/IEC 9798-3:1998/Amd.1:2010(E)
©
ISO/IEC 2010
---------------------- Page: 1 ----------------------
ISO/IEC 9798-3:1998/Amd.1:2010(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2010
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2010 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 9798-3:1998/Amd.1:2010(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
Amendment 1 to ISO/IEC 9798-3:1998 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 27, IT Security techniques.
© ISO/IEC 2010 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 9798-3:1998/Amd.1:2010(E)
Information technology — Security techniques — Entity
authentication —
Part 3:
Mechanisms using digital signature techniques
AMENDMENT 1
Page 1, Clause 3
Replace the first paragraph of Clause 3 with the following:
For the purposes of this part of ISO/IEC 9798, the definitions and notation described in ISO/IEC 9798-1 and
the following apply:
I The identity of entity A, which is either A or CertA.
A
I The identity of entity B, which is either B or CertB.
B
ResX The result of verifying entity X’s public key or public key certificate.
Page 5, 5.2.3
Add the following after 5.2.3:
6 Mechanisms involving an on-line trusted third party
6.1 Introduction
The authentication mechanisms in this clause require the two entities A and B to validate each other's public
keys using an on-line trusted third party (with distinguishing identifier TP). This trusted third party shall
possess reliable copies of the public keys of A and B. The entities A and B shall possess a reliable copy of the
public key of TP.
This clause specifies two five pass authentication mechanisms, both of which achieve mutual authentication
between entities A and B.
In the specification of the two mechanisms, the form of tokens and text fields follow the description given at
the beginning of Clause 5, i.e. all paragraphs in Clause 5 before 5.1.
Implementations of the mechanisms shall use one of the signature schemes specified in ISO/IEC 14888 or
ISO/IEC 9796.
© ISO/IEC 2010 – All rights reserved 1
---------------------- Page: 4 ----------------------
ISO/IEC 9798-3:1998/Amd.1:2010(E)
6.2 Five pass authentication (initiated by A)
In this authentication mechanism, uniqueness/timeliness is controlled by generating and checking a random
number (see Annex B of ISO/IEC 9798-1:1997).
This authentication mechanism is illustrated in Figure 6.
TP
(4)
(5) Text7||TokenTA (3) R’ ||R ||I ||I ||Text4
A B A B
(1) R ||I ||Text1
A A
B
A
(6) (2) I ||TokenBA
B
(8)
(7) TokenAB
Figure 6 ― Five pass authentication (initiated by A)
The tokens shall be created according to one of the following two options.
Option 1:
TokenAB = Text9||ResA||sS (R ||ResA||Text5)||sS (R ||R ||B||A||Text8)
T B A B A
TokenBA = R ||R ||Text3||sS (B||R ||R ||A||Text2)
A B B A B
TokenTA = ResA||ResB||sS (R’ ||ResB||Text6)||sS (R ||ResA||Text5)
T A T B
Option 2:
TokenAB = R’ ||Text9||TokenTA||sS (R ||R ||B||A||Text8)
A A B A
TokenBA = R ||R ||Text3||sS (B||R ||R ||A||Text2)
A B B A B
TokenTA = ResA||ResB||sS (R’ ||R ||ResA||ResB||Text5)
T A B
The values of the fields I , I , ResA, ResB, Status and Failure shall have the following forms:
A B
I = A or CertA
A
I = B or CertB
B
ResA = (CertA||Status), (A||P ) or Failure
A
ResB = (CertB||Status), (B||P ) or Failure
B
2 © ISO/IEC 2010 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC 9798-3:1998/Amd.1:2010(E)
Status = True or False. The value of the field shall be set to False if the certificate is known to have been
revoked; otherwise it shall be set to True.
Failure: ResX (where X = {A, B}) will be set to Failure if neither a public key nor a certificate of entity X
can be found by TP.
In the mechanism, if TP knows the mapping between identity X and P (where X = {A, B}), then it shall set
X
I = X; otherwise, it shall set I = CertX, and X shall be set equal to the collection of distinguished identity
X X
fields in CertX. If either X or CertX is permitted to be used as an identity, then there should be a pre-arranged
means to allow TP to distinguish the two types of identity indications. The value of ResX (where X = {A, B})
shall be determined according to Table 1.
Table 1 — Value of ResX
Field Choice 1 Choice 2
I
X CertX
X
(X||P ) or Failure
ResX (CertX||Status) or Failure
X
The mechanism is performed as follows:
1) A sends a random number R , its identity I and, optionally, a text field Text1 to B.
A A
2) B sends the token TokenBA and I to A.
B
3) A sends a random number R’ , together with R , I , I and, optionally, a text field Text4 to TP.
A B A B
4) On receipt of the message in Step (3) from A, TP performs the following steps. If I = A and I = B,
A B
TP retrieves P and P ; If I = CertA and I = CertB, TP checks the validity of CertA and CertB. The
A B A B
process of certificate verification by TP may require protection from denial-of-service attacks. The
specification of mechanisms to be used to provide such protection is outside of the scope of this part
of ISO/IEC 9798.
5) Then TP sends TokenTA and, optionally, a text field Text7 to A. The fields ResA and ResB in
TokenTA shall be: the certificates of A and B and their status, the distinguishing identifiers of A and B
and their public keys, or an indication of Failure.
6) On receipt of the message in Step (5) from TP, A performs the following steps:
(i) Verify TokenTA by checking the signature of TP contained in the token, and by checking that
the random number R’ , sent to TP in Step (3), is the same as the random number R’
A A
contained in the signed data of TokenTA.
(ii) Retrieve the public key of B from the message, verify TokenBA received in Step (2) by
checking the signature of B contained in the token and checking that the value of identifier field
(A) in the signed data of TokenBA is equal to A’s distinguishing identifier, and then check that
the random number R , sent to B in Step (1), is the same as the random number R contained
A A
in TokenBA.
7) A sends TokenAB to B.
8) On receipt of the message in Step (7) from A, B performs the following steps:
(i) Verify TokenTA by checking the signature of TP contained in the token, and by checking that
the random number R , sent to A in Step (2), is the same as the random number R contained
B B
in the signed data of TokenTA.
© ISO/IEC 2010 – All rights reserved 3
---------------------- Page: 6 ----------------------
ISO/IEC 9798-3:1998/Amd.1:2010(E)
(ii) Retrieve the public key of A from the message, verify TokenAB by checking the signature of A
cont
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.