Information technology — Conformance test methods for security service crypto suites — Part 21: Crypto suite SIMON

This document describes methods for determining conformance to the security crypto suite defined in ISO/IEC 29167‑21. This document contains conformance tests for all mandatory functions. The conformance parameters are the following: — parameters that apply directly affecting system functionality and inter-operability, — protocol including commands and replies, — nominal values and tolerances. Unless otherwise specified, the tests in this document are intended to be applied exclusively to RFID tags and interrogators defined in the ISO/IEC 18000 series using ISO/IEC 29167‑21.

Technologies de l'information — Méthodes d'essai de conformité pour les suites cryptographiques des services de sécurité — Partie 21: Suite cryptographique SIMON

General Information

Status
Published
Publication Date
20-May-2019
Current Stage
Ref Project

Buy Standard

Standard
ISO/IEC 19823-21:2019 - Information technology -- Conformance test methods for security service crypto suites
English language
20 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
REDLINE ISO/IEC 19823-21:2019 - Information technology — Conformance test methods for security service crypto suites — Part 21: Crypto suite SIMON Released:5/21/2019
English language
20 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


INTERNATIONAL ISO/IEC
STANDARD 19823-21
First edition
2019-05
Information technology —
Conformance test methods for
security service crypto suites —
Part 21:
Crypto suite SIMON
Technologies de l'information — Méthodes d'essai de conformité pour
les suites cryptographiques des services de sécurité —
Partie 21: Suite cryptographique SIMON
Reference number
©
ISO/IEC 2019
© ISO/IEC 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2019 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, symbols and abbreviated terms . 1
4 Test methods . 2
4.1 General . 2
4.2 By demonstration . 2
4.3 By design . 2
5 Test requirements for ISO/IEC 18000-63 interrogators and tags .2
6 Test methods with respect to ISO/IEC 29167-21 interrogators and tags .2
6.1 Test map for optional features . 2
6.2 Crypto suite requirements . 3
6.2.1 General. 3
6.2.2 Crypto suite requirements of ISO/IEC 29167-21:2018, Clauses 1 to 8 and
Annexes A to C . . 3
6.2.3 Crypto suite requirements of ISO/IEC 29167-21:2018, Clauses 9 to 12
and Annex E. 3
6.3 Test patterns .13
6.3.1 General.13
6.3.2 Test_Pattern 1 .14
6.3.3 Test_Pattern 2 .14
6.3.4 Test_Pattern 3 .15
6.3.5 Test_Pattern 4 .15
6.3.6 Test_Pattern 5 .16
6.3.7 Test_Pattern 6 .16
6.3.8 Test_Pattern 7 .17
6.3.9 Test_Pattern 8 .17
6.3.10 Test_Pattern 9 .18
6.3.11 Test_Pattern 10 .18
6.3.12 Test_Pattern 11 .19
Bibliography .20
© ISO/IEC 2019 – All rights reserved iii

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.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/directives).
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. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www .iso .org/patents) or the
IEC list of patent declarations received (see http: //patents .iec .ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see www .iso
.org/iso/foreword .html.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 31, Automatic identification and data capture techniques.
A list of all parts in the ISO/IEC 19823 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/members .html.
iv © ISO/IEC 2019 – All rights reserved

Introduction
The ISO/IEC 29167 series describes security services as applicable for the ISO/IEC 18000 series. The
various parts of ISO/IEC 29167 describe crypto suites that are optional extensions to the ISO/IEC 18000
air interfaces.
The ISO/IEC 19823 series describes the conformance test methods for security service crypto suites.
It is related to the ISO/IEC 18047 series, which describes the radio frequency identification device
conformance test methods, in the same way as ISO/IEC 29167 is related to ISO/IEC 18000.
These relations mean that, for a product that is claimed to be compliant to a pair of ISO/IEC 18000-n
and ISO/IEC 29167-m, the test methods of ISO/IEC 18047-n and ISO/IEC 19823-m apply. If a product
supports more than one part of ISO/IEC 18000 or ISO/IEC 29167, all related parts of ISO/IEC 18047 and
ISO/IEC 19823 apply.
NOTE 1 The conformance test requirements of ISO/IEC 18000-6, ISO/IEC 18000-61, ISO/IEC 18000-62, ISO/
IEC 18000-63, ISO/IEC 18000-64 are currently all in ISO/IEC 18047-6.
This document describes the test methods for the SIMON crypto suite as standardized in ISO/
IEC 29167-21.
NOTE 2 Test methods for interrogator and tag performance are covered by ISO/IEC 18046 (all parts).
© ISO/IEC 2019 – All rights reserved v

INTERNATIONAL STANDARD ISO/IEC 19823-21:2019(E)
Information technology — Conformance test methods for
security service crypto suites —
Part 21:
Crypto suite SIMON
1 Scope
This document describes methods for determining conformance to the security crypto suite defined in
ISO/IEC 29167-21.
This document contains conformance tests for all mandatory functions.
The conformance parameters are the following:
— parameters that apply directly affecting system functionality and inter-operability,
— protocol including commands and replies,
— nominal values and tolerances.
Unless otherwise specified, the tests in this document are intended to be applied exclusively to RFID
tags and interrogators defined in the ISO/IEC 18000 series using ISO/IEC 29167-21.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 17025, General requirements for the competence of testing and calibration laboratories
ISO/IEC 18000-63, Information technology — Radio frequency identification for item management —
Part 63: Parameters for air interface communications at 860 MHz to 960 MHz Type C
ISO/IEC 18047-6:2017, Information technology — Radio frequency identification device conformance test
methods — Part 6: Test methods for air interface communications at 860 MHz to 960 MHz
ISO/IEC 19762, Information technology — Automatic identification and data capture (AIDC) techniques —
Harmonized vocabulary
ISO/IEC 29167-21:2018, Information technology — Automatic identification and data capture
techniques — Part 21: Crypto suite SIMON security services for air interface communications
3 Terms, definitions, symbols and abbreviated terms
For the purposes of this document, the terms, definitions, symbols and abbreviated terms given in ISO/
IEC 19762 and in ISO/IEC 29167-21 apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https: //www .iso .org/obp
— IEC Electropedia: available at http: //www .electropedia .org/
© ISO/IEC 2019 – All rights reserved 1

4 Test methods
4.1 General
This document describes test methods for ISO/IEC 29167-21. As parts of ISO/IEC 19823 are always
tested in relation to ISO/IEC 18047, duplication of information requirements and specifications is meant
to be avoided.
Clause 5 defines elements that are covered in the respective part of ISO/IEC 18047.
Clause 6 defines elements that are not covered by ISO/IEC 18047 and are therefore addressed in this
document.
4.2 By demonstration
If tests are labelled “by demonstration” then laboratory testing of one or (if required for statistical
reasons) multiple products, processes or services is required to ensure conformance. A test laboratory
that meets the requirements of ISO/IEC 17025 shall perform the indicated testing to ensure conformance
of the component or system.
For protocol requirements that are verified by demonstration, the test conditions are specified in this
document. The detailed test plan is left to the discretion of the test laboratory.
4.3 By design
If tests are labelled “by design” then verification of design parameters and/or theoretical analysis is
used to ensure conformance. A vendor submitting a component or system for conformance testing shall
provide the necessary technical information, in the form of a technical memorandum or similar. A test
laboratory shall issue a test report indicat
...


Deleted: PRF
ISO/IEC 19823-21 :2019(E)
Information technology — Conformance test methods for security service crypto
suites — Part 21: Crypto suite SIMON
Technologies de l'information — Méthodes d'essai de conformité pour les suites cryptographiques
des services de sécurité— Partie 21: Suite cryptographique SIMON

Deleted: PRF
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.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
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.
Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the
IEC list of patent declarations received (see http://patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT)
see www.iso.org/iso/foreword.html.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 31, Automatic identification and data capture techniques.
A list of all parts in the ISO/IEC 19823 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
ii © ISO/IEC 2019 – All rights reserved

Deleted: PRF
Introduction
The ISO/IEC 29167 series describes security services as applicable for the ISO/IEC 18000 series. The
various parts of ISO/IEC 29167 describe crypto suites that are optional extensions to the
ISO/IEC 18000 air interfaces.
The ISO/IEC 19823 series describes the conformance test methods for security service crypto suites. It
is related to the ISO/IEC 18047 series, which describes the radio frequency identification device
conformance test methods, in the same way as ISO/IEC 29167 is related to ISO/IEC 18000.
These relations mean that, for a product that is claimed to be compliant to a pair of ISO/IEC 18000‐n
and ISO/IEC 29167‐m, the test methods of ISO/IEC 18047‐n and ISO/IEC 19823‐m apply. If a product
supports more than one part of ISO/IEC 18000 or ISO/IEC 29167, all related parts of ISO/IEC 18047
and ISO/IEC 19823 apply.
NOTE 1 The conformance test requirements of ISO/IEC 18000‐6, ISO/IEC 18000‐61, ISO/IEC 18000‐62,
ISO/IEC 18000‐63, ISO/IEC 18000‐64 are currently all in ISO/IEC 18047‐6.
This document describes the test methods for the SIMON crypto suite as standardized in
ISO/IEC 29167‐21.
NOTE 2 Test methods for interrogator and tag performance are covered by ISO/IEC 18046 (all parts).
© ISO/IEC 2019 – All rights reserved iii

Deleted: PRF
Error! Reference source not found. ISO/IEC 19823-21:2019(E)

Information technology — Conformance test methods for security
service crypto suites — Part 21: Crypto suite SIMON
1 Scope
This document describes methods for determining conformance to the security crypto suite defined in
ISO/IEC 29167‐21.
This document contains conformance tests for all mandatory functions.
The conformance parameters are the following:
— parameters that apply directly affecting system functionality and inter‐operability,
— protocol including commands and replies,
— nominal values and tolerances.
Unless otherwise specified, the tests in this document are intended to be applied exclusively to RFID
tags and interrogators defined in the ISO/IEC 18000 series using ISO/IEC 29167‐21.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/IEC 17025, General requirements for the competence of testing and calibration laboratories
ISO/IEC 18000‐63, Information technology — Radio frequency identification for item management —
Part 63: Parameters for air interface communications at 860 MHz to 960 MHz Type C
ISO/IEC 18047‐6:2017, Information technology — Radio frequency identification device conformance test
methods — Part 6: Test methods for air interface communications at 860 MHz to 960 MHz
ISO/IEC 19762, Information technology — Automatic identification and data capture (AIDC)
techniques — Harmonized vocabulary
ISO/IEC 29167‐21:2018, Information technology — Automatic identification and data capture
techniques — Part 21: Crypto suite SIMON security services for air interface communications
3 Terms, definitions, symbols and abbreviated terms
For the purposes of this document, the terms, definitions, symbols and abbreviated terms given in
ISO/IEC 19762 and in ISO/IEC 29167‐21 apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
© ISO/IEC 2019 – All rights reserved 1

Deleted: PRF
— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at http://www.electropedia.org/
4 Test methods
4.1 General
This document describes test methods for ISO/IEC 29167‐21. As parts of ISO/IEC 19823 are always
tested in relation to ISO/IEC 18047, duplication of information requirements and specifications is
meant to be avoided.
Clause 5 defines elements that are covered in the respective part of ISO/IEC 18047.
Clause 6 defines elements that are not covered by ISO/IEC 18047 and are therefore addressed in this
document.
4.2 By demonstration
If tests are labelled “by demonstration” then laboratory testing of one or (if required for statistical
reasons) multiple products, processes or services is required to ensure conformance. A test laboratory
that meets the requirements of ISO/IEC 17025 shall perform the indicated testing to ensure
conformance of the component or system.
For protocol requirements that are verified by demonstration, the test conditions are specified in this
document. The detailed test plan is left to the discretion of the test laboratory.
4.3 By design
If tests are labelled “by design” then verification of design parameters and/or theoretical analysis is
used to ensure conformance. A vendor submitting a component or system for conformance testing shall
provide the necessary technical information, in the form of a technical memorandum or similar. A test
laboratory shall issue a test report indicating whether the technical analysis was sufficient to ensure
conformance of the component or system.
For protocol requirements that are verified by design, the method of technical analysis is at the
discretion of the submitting vendor and is not specified by this document. In general, the technical
analysis shall have sufficient rigor and technical depth to convince a test engineer knowledgeable of the
protocol that the particular requirement has been met.
5 Test requirements for ISO/IEC 18000-63 interrogators and tags
The mandatory requirements and applicable optional requirements of ISO/IEC 18047‐6:2017, Clauses 4
and 5 shall be fulfilled.
Before a DUT is tested according to this document, it shall successfully pass ISO/IEC 18047‐6:2017,
Clause 7.
6 Test methods with respect to ISO/IEC 29167-21 interrogators and tags
6.1 Test map for optional features
Table 1 lists all optional features of this crypto suite and shall be used as a template to report the test
results. Furthermore, it is used to refer to the test requirements in 6.2.
2 © ISO/IEC 2019 – All rights reserved

Deleted: PRF
Table 1 — Test map for optional features
To be tested for
Test
# Feature Additional requirement supplied
results
product?
Shall be tested with the Authenticate command of
1 TA
ISO/IEC 18000‐63
Shall be tested with the Authenticate command of
2 IA
ISO/IEC 18000‐63
Shall be tested with the Authenticate command of
3 MA
ISO/IEC 18000‐63
Secure Shall be tested with the SecureComm command
Communication of ISO/IEC 18000‐63
6.2 Crypto suite requirements
6.2.1 General
This clause refers to the requirements of ISO/IEC 29167‐21.
6.2.2 Crypto suite requirements of ISO/IEC 29167-21:2018, Clauses 1 to 8 and Annexes A to C
All the requirements of ISO/IEC 29167‐21:2018, Clauses 1 to 8 and Annexes A to C shall be met and
conformance shall be verified by design only.
6.2.3 Crypto suite requirements of ISO/IEC 29167-21:2018, Clauses 9 to 12 and Annex E
The requirements of ISO/IEC 29167‐21:2018, Clauses 9 to 12 and Annex E listed in Table 2 shall be met.
This document shall be read in conjunction with ISO/IEC 29167‐21 to provide a full explanation of the
terms used.
Table 2 — Crypto suite requirements for ISO/IEC 29167-21
Protocol MO
a
Item Requirement Applies to How verified
a b
subclause
The Interrogator shall generate a random
Interrogato
1 9.3.2 Interrogator challenge (IChallenge‐b/k) that is M By design
r
carried in the TAM1 message.
The Tag shall accept the TAM1 message at any
time (unless occupied by internal processing
and not capable of receiving messages), i.e. upon
2 9.3.3 receipt of the message with valid parameters, M Tag By design
the Tag shall abort any cryptographic protocol
that has not yet been completed and shall
remain in the Initial state.
The Tag shall check if the Step is "00". If the
3 9.3.3 value of Step is different, the Tag shall return a M Tag Test_Pattern 2
"Not Supported" error.
The Tag shall check if the RFU is "00". If the
4 9.3.3 value of RFU is different, the Tag shall return a M Tag Test_Pattern 2
"Not Supported" error.
The Tag shall check whether the values of
5 9.3.3 M Tag By design
BlockSize and KeySize are supported by the Tag.
© ISO/IEC 2019 – All rights reserved 3

Deleted: PRF
If at least one of these checks is failed, the Tag
shall return a "Not Supported" error.
The Tag shall check whether the values of
BlockSize and KeySize are supported by
Key.KeyID and that Key.KeyID is authorized for
6 9.3.3 M Tag By design
use in Tag authentication. If either or both of
these checks is failed, the Tag shall return a "Not
Supported" error.
The Tag shall check whether the parameter set
PS is supported. If the parameter set PS is not
7 9.3.3 M Tag Test_Pattern 2
supported, the Tag shall return a "Not
Supported" error.
Assuming that the TAM1 message is successfully
8 9.3.3 parsed by the Tag, the Tag shall prepare the M Tag By design
TAM1 response.
The Tag shall generate a random salt TRnd‐b/k
9 9.3.4 of length r bits were r is given for the parameter M Tag By design
set in Table 4.
The Tag shall use Key.KeyID and SIMON
encryption to form a b‐bit string TResponse
such that
10 9.3.4 M Tag Test_Pattern 1
TResponse = SIMON‐b/k‐ENC ( Key.KeyID,
C_TAM‐b/k ‖ TRnd‐b/k ‖ IChallenge‐b/k )
The Tag shall return TResponse to the
11 9.3.4 M Tag By design
Interrogator.
After receiving TAM1 response, the Interrogator
shall use Key.KeyID to compute the b‐bit string S
where:
Interrogato
12 9.3.5 M By design
S = SIMON‐b/k‐DEC ( Key.KeyID, TResponse ). r
The Interrogator shall check that S[t‐1:0] =
IChallenge‐b/k.
The Interrogator shall send an initial message
IAM1 to the Tag prompting the Tag to start a
Interrogato
challenge‐response exchange.
13 9.4.2 O By design
r
The Interrogator shall also indicate the variant
of SIMON to be used.
The Tag shall accept this message at any time
(unless occupied by internal processing and not
capable of receiving messages), i.e. upon receipt
14 9.4.3 of the message with valid parameters, the Tag O Tag By design
shall abort any cryptographic protocol that has
not yet been completed and shall remain in the
Initial state.
If Interrogator authentication is not supported
on the Tag, i.e. if "01" is not a valid value for
15 9.4.3 O Tag By design
AuthMethod, then the Tag shall return a "Not
Supported" error condition.
The Tag shall check if the Step is "00". If the
16 9.4.3 value of Step is different, the Tag shall return a O Tag Test_Pattern 3
"Not Supported" error.
4 © ISO/IEC 2019 – All rights reserved

Deleted: PRF
The Tag shall check if the RFU is "00". If the
17 9.4.3 value of RFU is different, the Tag shall return a O Tag Test_Pattern 3
"Not Supported" error.
The Tag shall check whether the values of
BlockSize and KeySize are supported by the Tag.
18 9.4.3 O Tag By design
If at least one of these checks is failed, the Tag
shall return a "Not Supported" error.
The Tag shall check whether the values of
BlockSize and KeySize are supported by
Key.KeyID and that Key.KeyID is authorized for
19 9.4.3 O Tag By design
use in Interrogator authentication. If at least one
of these checks is failed, the Tag shall return a
"Not Supported" error.
The Tag shall check whether the value of
20 9.4.3 parameter set PS is supported by the Tag. If not, O Tag Test_Pattern 3
the Tag shall return a "Not Supported" error.
If the IAM1 message is successfully parsed by
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.