ISO/IEC 19823-22:2026

International
Standard
ISO/IEC 19823-22
Second edition
Information technology —
2026-03
Conformance test methods for
security service crypto suites —
Part 22:
Crypto suite SPECK
Technologies de l'information — Méthodes d'essai de conformité
pour les suites cryptographiques des services de sécurité —
Partie 22: Suite cryptographique SPECK
Reference number
© ISO/IEC 2026
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
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2026 – All rights reserved
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, symbols and abbreviated terms . 1
3.1 Terms and definitions .1
3.2 Symbols and abbreviated terms .2
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-22 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-22:2026, Clauses 4 to 8 and
Annexes A to C .3
6.2.3 Crypto suite requirements of ISO/IEC 29167-22:2026, Clauses 9 to 12 and
Annex E .3
6.3 Test patterns . . 12
6.3.1 General . 12
6.3.2 Test Pattern 1 . 12
6.3.3 Test Pattern 2 . 12
6.3.4 Test Pattern 3 . 13
6.3.5 Test Pattern 4 . 13
6.3.6 Test Pattern 5 .14
6.3.7 Test Pattern 6 .14
6.3.8 Test Pattern 7 . 15
6.3.9 Test Pattern 8 . 15
6.3.10 Test Pattern 9 .16
6.3.11 Test Pattern 10 .16
6.3.12 Test Pattern 11 .17
Bibliography .18

© ISO/IEC 2026 – 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 or www.iec.ch/members_experts/refdocs).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
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.
In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 31, Automatic identification and data capture techniques.
This second edition cancels and replaces the first edition (ISO/IEC 19823-22:2019), which has been
technically revised.
The main change is as follows: test items have been updated to reflect changes to the over-the-air protocol.
A list of all parts in the ISO/IEC 19823 series can be found on the ISO and IEC websites.
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 and
www.iec.ch/national-committees.

© ISO/IEC 2026 – All rights reserved
iv
Introduction
The ISO/IEC 29167 series describes security services as applicable for the ISO/IEC 18000 series. The various
parts of the ISO/IEC 29167 series describe crypto suites that are optional extensions to the ISO/IEC 18000
air interfaces.
The ISO/IEC 19823 series describes conformance test methods for security service crypto suites.
The ISO/IEC 19823 series is related to the ISO/IEC 18047 series, which describes the radio frequency
identification device conformance test methods, in the same way as the ISO/IEC 29167 series is related
to the ISO/IEC 18000 series. These relations mean that, for a product that is claimed to conform to a pair
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 the ISO/IEC 18000 series or the ISO/IEC 29167 series, all related
parts of the ISO/IEC 18047 series and the ISO/IEC 19823 series apply.
The conformance parameters are:
— parameters that apply directly affecting system functionality and inter-operability;
— protocol including commands and replies;
— nominal values and tolerances.
NOTE 1 ISO/IEC 18047-6 provides the conformance test requirements of ISO/IEC 18000-6, ISO/IEC 18000-61,
ISO/IEC 18000-62, ISO/IEC 18000-63 and ISO/IEC 18000-64.
NOTE 2 Test methods for Interrogator and Tag performance are covered by the ISO/IEC 18046 series.

© ISO/IEC 2026 – All rights reserved
v
International Standard ISO/IEC 19823-22:2026(en)
Information technology — Conformance test methods for
security service crypto suites —
Part 22:
Crypto suite SPECK
1 Scope
This document describes the test methods for determining conformance for the security crypto suite SPECK
defined in ISO/IEC 29167-22.
This document contains conformance tests for all mandatory functions.
Unless otherwise specified, the tests in this document are only applicable to radio frequency identification
(RFID) Tags and Interrogators defined in the ISO/IEC 18000 series using ISO/IEC 29167-22.
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:2025, 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 —
Vocabulary
ISO/IEC 29167-22:2026, Information technology — Automatic identification and data capture techniques —
Part 22: Crypto suite SPECK security services for air interface communications
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in in ISO/IEC 19762 and ISO/IEC 29167-22
apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/

© ISO/IEC 2026 – All rights reserved
3.2 Symbols and abbreviated terms
For the purposes of this document, the symbols and abbreviated terms given in ISO/IEC 19762 and
ISO/IEC 29167-22 apply.
4 Test methods
4.1 General
This document describes the test methods for ISO/IEC 29167-22. As parts of the ISO/IEC 19823 series are
always intended to be tested in conjunction with the ISO/IEC 18047 series, duplication of information,
requirements and specifications present in the ISO/IEC 18047 series has been avoided.
Clause 5 describes elements that are covered in the respective part of the ISO/IEC 18047 series.
Clause 6 describes elements that are not covered by the ISO/IEC 18047 series and that 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 meeting 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 either the verification of design parameters or theoretical analysis, or
both, 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 requirements and recommendations of ISO/IEC 18047-6:2025, Clauses 4 and 5 shall be fulfilled.
Before a device under test is tested according to this document, it shall successfully pass ISO/IEC 18047-6:2025,
Clause 7.
6 Test methods with respect to ISO/IEC 29167-22 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.

© ISO/IEC 2026 – All rights reserved
Table 1 — Test map for optional features
Mark item to be
Item Test
Feature Additional requirement tested for
no. result
supplied product
Shall be tested with the Authenticate command of
1 Tag authentication
ISO/IEC 18000-63.
Shall be tested with the Authenticate command of
2 Interrogator authentication
ISO/IEC 18000-63.
Shall be tested with the Authenticate command of
3 Mutual authentication
ISO/IEC 18000-63.
Shall be tested with the SecureComm command of
4 Secure Communication
ISO/IEC 18000-63.
6.2 Crypto suite requirements
6.2.1 General
Subclause 6.2 refers to the requirements of ISO/IEC 29167-22.
6.2.2 Crypto suite requirements of ISO/IEC 29167-22:2026, Clauses 4 to 8 and Annexes A to C
All the requirements of ISO/IEC 29167-22:2026, Clauses 4 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-22:2026, Clauses 9 to 12 and Annex E
The requirements of ISO/IEC 29167-22:2026, 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-22 which, together, provide a full explanation of
the terms used.
Table 2 — Crypto suite requirements of ISO/IEC 29167-22:2026, Clauses 9 to 12 and Annex E
Item Protocol Verification
a
Requirement M/O Applies to
a
no. subclause method
The Interrogator shall generate a random Interrogator
1 9.3.2 challenge (IChallenge-b/k) that is carried in the TAM1 M Interrogator By design
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 receipt of the message
2 9.3.3 M Tag By design
with valid parameters, the Tag shall abort any cryp-
tographic 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 value of
3 9.3.3 Step is different, the Tag shall return a "Not Supported" M Tag Test Pattern 2
error.
The Tag shall check if the RFU is "00 ". If the value of
4 9.3.3 RFU is different, the Tag shall return a "Not Supported" M Tag Test Pattern 2
error.
Key
M mandatory; items are mandatory and shall be tested for all devices
O optional; items are optional and shall be tested only for devices that support the feature that is indicated by the requirement
a
All clauses, subclauses and tables referenced are from ISO/IEC 29167-22:2026.

© ISO/IEC 2026 – All rights reserved
TTaabbllee 22 ((ccoonnttiinnueuedd))
Item Protocol Verification
a
Requirement M/O Applies to
a
no. subclause method
The Tag shall check whether the values of BlockSize and
KeySize are supported by the Tag. If at least one of these
5 9.3.3 M Tag By design
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
6 9.3.3 is authorized for use in Tag authentication. If either or M Tag By design
both of these checks is failed, the Tag shall return a "Not
Supported" error.
The Tag shall check whether the parameter set PS is
7 9.3.3 supported. If the parameter set PS is not supported, the M Tag Test Pattern 2
Tag shall return a "Not Supported" error.
Assuming that the TAM1 message is successfully parsed
8 9.3.3 M Tag By design
by the Tag, the Tag shall prepare the TAM1 response.
The Tag shall generate a random salt TRnd-b/k of length
9 9.3.3 M Tag By design
r bits were r is given for the parameter set in Table 4.
The Tag shall use Key.KeyID and SPECK encryption to
form a b-bit string TResponse such that
10 9.3.4 M Tag Test Pattern 1
TResponse = SPECK-b/k-ENC ( Key.KeyID, C_TAM-b/k ‖
TRnd-b/k ‖ IChallenge-b/k )
11 9.3.4 The Tag shall return TResponse to the Interrogator. M Tag By design
After receiving TAM1 response, the Interrogator shall
use Key.KeyID to compute the b-bit string S where:
12 9.3.5 S = SPECK-b/k-DEC ( Key.KeyID, TResponse ). M Interrogator By design
The Interrogator shall check that S[t-1:0] = IChal-
lenge-b/k.
The Interrogator shall send an initial message IAM1 to
the Tag prompting the Tag to start a challenge-response
exchange.
13 9.4.2 O Interrogator By design
The Interrogator shall also indicate the variant of SPECK
to be used.
The Tag shall accept this message at any time (unless
occupied by internal processing and not capable of re-
ceiving messages); i.e. upon receipt of the message with
14 9.4.3 O Tag By design
valid parameters, the Tag shall abort any cryptographic
protocol that has not yet been completed and shall re-
main in the Initial state.
If Interrogator authentication is not supported on the
15 9.4.3 Tag, i.e. if "01 " is not a valid value for AuthMethod, then O Tag By design
the Tag shall return a "Not Supported" error condition.
The Tag shall check if the Step is "00 ". If the value of
16 9.4.3 Step is different, the Tag shall return a "Not Supported" O Tag Test Pattern 3
error.
The Tag shall check if the RFU is "00 ". If the value of
17 9.4.3 RFU is different, the Tag shall return a "Not Supported" O Tag Test Pattern 3
error.
Key
M mandatory; items are mandatory and shall be tested for all devices
O optional; items are optional and shall be tested only for devices that support the feature that is indicated by the requirement
a
All clauses, subclauses and tables referenced are from ISO/IEC 29167-22:2026.

© ISO/IEC 2026 – All rights reserved
TTaabbllee 22 ((ccoonnttiinnueuedd))
Item Protocol Verification
a
Requirement M/O Applies to
a
no. subclause method
The Tag shall check whether the values of BlockSize and
KeySize are supported by the Tag. If at least one of these
18 9.4.3 O Tag By design
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
19 9.4.3 is authorized for use in Interrogator authentication. If at O Tag By design
least one of these checks is failed, the Tag shall return a
"Not Supported" error.
The Tag shall check whether the value of parameter set
20 9.4.3 PS is supported by the Tag. If not, the Tag shall return a O Tag Test Pattern 3
"Not Supported" error.
If the IAM1 message is successfully parsed by the Tag,
21 9.4.3 O Tag By design
the Tag shall calculate the IAM1 response.
The Tag shall generate a random challenge TChal-
22 9.4.4 lenge-b/k of length t bits, where t is determined by the O Tag By design
parameter set, and shall send this to the Interrogator.
23 9.4.5 The Interrogator shall construct the IAM2 message. O Interrogator By design
The Interrogator shall form a b-bit string IResponse such
that
IResponse = SPECK-b/k-DEC ( Key.KeyID, C_IAM-b/k ‖
24 9.4.6 O Interrogator Test Pattern 4
IRnd-b/k ‖ TChallenge-b/k ).
The Interrogator shall send IResponse to the Tag as part
of the IAM2 message; see Table 10.
The Tag shall only accept the IAM2 message when the
25 9.4.7 O Tag By design
cryptographic engine is in state PA1.
If Interrogator authentication is not supported on the
26 9.4.7 Tag, i.e. if "01 " is not a valid value for AuthMethod, then O Tag By design
the Tag shall return a "Not Supported" error condition.
The Tag shall check if the Step is "01 ". If the value of
27 9.4.7 Step is different, the Tag shall return a "Not Supported" O Tag Test Pattern 5
error.
The Tag shall check if the RFU is "0000 ". If the value of
28 9.4.7 RFU is different, the Tag shall return a "Not Supported" O Tag Test Pattern 5
error.
The Tag shall use Key.KeyID to compute the b-bit string
S where:
29 9.4.7 O Tag By design
S = SPECK -b/k-ENC ( Key.KeyID, IResponse ).
30 9.4.7 The Tag shall check that: S[t-1:0] = TChallenge-b/k. O Tag By design
31 9.4.7 The Tag shall prepare IAM2 response. O Tag By design
The Tag shall return the value of TStatus to the Interro-
32 9.4.8 O Tag Test Pattern 6
gator.
If, under conditions laid out in the over-the-air proto-
col, there is no response from the Tag or if the returned
33 9.4.9 O Interrogator By design
value of TStatus is 0 , then the Interrogator shall aban-
don the cryptographic protocol.
Key
M mandatory; items are mandatory and shall be tested for all devices
O optional; items are optional and shall be tested only for devices that support the feature that is indicated by the requirement
a
All clauses, subclauses and tables referenced are from ISO/IEC 29167-22:2026.

© ISO/IEC 2026 – All rights reserved
TTaabbllee 22 ((ccoonnttiinnueuedd))
Item Protocol Verification
a
Requirement M/O Applies to
a
no. subclause method
The Interrogator shall generate a random Interrogator
34 9.5.2 challenge (IChallenge-b/k) that is carried in the MAM1 O Interrogator By design
message.
The Interrogator shall indicate the variant of SPECK to
35 9.5.2 O Interrogator By design
be used.
The Tag shall accept MAM1 message at any time (unless
occupied by internal processing and not capable of re-
ceiving messages); i.e. upon receipt of the message with
36 9.5.3 O Tag By design
valid parameters, the Tag shall abort any cryptographic
protocol that has not yet been completed and shall re-
main in the Initial state.
If Mutual authentication is not supported on the Tag, i.e.
37 9.5.3 if "10 " is not a valid value for AuthMethod, then the Tag O Tag By design
shall return a "Not Supported" error condition.
The Tag shall check if the Step is "00 ". If the value of
38 9.5.2 Step is different, the Tag shall return a "Not Supported" O Tag Test Pattern 7
error.
The Tag shall check if the RFU is "00 ". If the value of
39 9.5.3 RFU is different, the Tag shall return a "Not Supported" O Tag Test Pattern 7
error.
The Tag shall check whether the values of BlockSize and
KeySize are supported by the Tag. If at least one of these
40 9.5.3 O Tag By design
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
41 9.5.3 is authorized for use in Interrogator-Tag Mutual authen- O Tag By design
tication. 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 parameter set
42 9.5.3 PS is supported by the Tag. If not, the Tag shall return a O Tag By design
"Not Supported" error.
The Tag shall generate a random challenge TChal-
43 9.5.3 O Tag By design
lenge-b/k.
The Tag shall construct a b-bit string by concatenat-
44 9.5.3 ing C_MAM-b/k with the (b-t-c) most significant bits of O Tag By design
TChallenge-b/k and the entirety of IChallenge-b/k.
The Tag shall use Key.KeyID to compute the b-bit string
S where:
45 9.5.3 S = SPECK-b/k-ENC ( Key.KeyID, C_MAM-b/k ‖ TChal- O Tag Test Pattern 8
lenge-b/k [t-1:2t-b+c] ‖
IChallenge-b/k ).
After receiving MAM1 Response, the Interrogator shall
use Key.KeyID to compute the b-bit string T where:
46 9.5.5 T = SPECK-b/k-DEC ( Key.KeyID, TResponse[b-1:0] ). O Interrogator By design
The Interrogator shall check that T[t-1:0] = IChal-
lenge-b/k.
Key
M mandatory; items are mandatory and shall be tested for all devices
O optional; items are optional and shall be tested only for devices that support the feature that is indicated by the requirement
a
All clauses, subclauses and tables referenced are from ISO/IEC 29167-22:2026.

© ISO/IEC 2026 – All rights reserved
TTaabbllee 22 ((ccoonnttiinnueuedd))
Item Protocol Verification
a
Requirement M/O Applies to
a
no. subclause method
If the cryptographic protocol has not been abandoned,
the Interrogator shall form a b-bit string IResponse de-
pending on the parameter set PS as follows:
a) If PS = 00 , then IResponse is equal to
SPECK-b/k-DEC ( Key.KeyID, C_MAM-b/k ‖ T[b-t-c-1:0] ‖
T[b-c-1:t] ‖
TResponse[2t+c-1:b] ).
47 9.5.6 O Interrogator By design
b) If PS = 01 , then IResponse is equal to T[b-c:t].
The Interrogator shall set SecureComm = 0001 if secure
communications as described in Clause 10 will be used
after Mutual authentication is completed. Otherwise, the
Interrogator shall set SecureComm = 0000 .
The I
...