ISO/IEC 19823-10

ISO/IEC DISFDIS 19823-10:2024(en)
ISO/IEC JTC 1/SC 31 N
Secretariat: ANSI
Date: 2025-10-03
Information technology — Conformance test methods for security
service crypto suites —
Part 10:
Crypto suite AES-128
Technologies de l’information — Conformance test methods for security service
cryptol'information — Méthodes d'essai de conformité pour les suites — cryptographiques des services de
sécurité —
Partie 10: Crypto suiteSuite cryptographique AES-128
Third edition
Date:  2024-12-03
Error! Reference source not found.
FDIS stage
ISO/IEC FDIS 19823-10:2025(en)
© ISO/IEC 20242025
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'sISO’s member body in the country of the requester.
ISO Copyright Officecopyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
Email: E-mail: copyright@iso.org
Website: www.iso.org
Published in Switzerland.
© ISO/IEC 2025 – All rights reserved
iii
ISO/IEC FDIS 19823-10:2025(en)
Contents Page
Foreword. v
Introduction . vi
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 methods with respect to the ISO/IEC 18000 series . 2
5.1 Test requirements for ISO/IEC 18000-3 Interrogators and Tags. 2
5.2 Test requirements for ISO/IEC 18000-63 Interrogators and Tags . 3
6 Test methods with respect to the ISO/IEC 29167-10 Interrogators and Tags. 3
6.1 Test map for optional features . 3
6.2 Additional parameters required as input for the test. 4
6.3 Crypto suite requirements . 5
7 Test patterns . 25
7.1 General . 25
7.2 Test pattern information . 25
7.3 Test pattern descriptions. 27
Bibliography . 50

© ISO/IEC 2025 – All rights reserved
iv
ISO/IEC FDIS 19823-10:2025(en)
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 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.
Field Code Changed
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 31, Automatic identification and data capture techniques.
This third edition cancels and replaces the second edition (ISO/IEC 19823-10:2020), which has been
technically revised.
The main changes arechange is as follows:
— Test 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 2025 – All rights reserved
v
ISO/IEC FDIS 19823-10:2025(en)
Introduction
The ISO/IEC 29167 series describes security services that are 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 series 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 the ISO/IEC 29167 series is related to the ISO/IEC 18000 series.
These relations mean that, for a product that is claimed to be conform to a pair of ISO/IEC 18000-n and
ISO/IEC 29167 documents-m, the test methods of the ISO/IEC 18047-n and ISO/IEC 19823 documents-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.
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.
NOTE 1 ISO/IEC 18047--6 contains 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 in the ISO/IEC 18046 series.
© ISO/IEC 2025 – All rights reserved
vi
ISO/IEC FDIS 19823-10:2025(en)
Information technology — Conformance test methods for security
service crypto suites —
Part 10:
Crypto suite AES-128
1 Scope
This document describes the test methods for the AES-128 crypto suite as standardized in ISO/IEC 29167--
10.
This document contains conformance tests for all mandatory and applicable optional functions.
Unless otherwise specified, the tests in this document are intendedonly applicable to be applied exclusively to
Radio Frequency Identificationradio frequency identification (RFID) Tagstags and Interrogatorsinterrogators
defined in the ISO/IEC 15693 series and in the ISO/IEC 18000 series using ISO/IEC 29167--10.
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 /TR 18047--3:20112022, Information technology — Radio frequency identification device
conformance test methods — Part 3: Test methods for air interface communications at 13,56 MHz
ISO/IEC 18000-63:2025, Information technology — Radio frequency identification device conformance test
1)
methods — Part 6: Test methods for air interface communications at 860 MHz to 960 MHz
ISO/IEC 18047--6:20172025, Information technology — Radio frequency identification device conformance test
2)
methods — Part 6: Test methods for air interface communications at 860 MHz to 930 960 MHz
ISO/IEC 19762, Information technology — Automatic identification and data capture (AIDC) techniques —
Harmonized vocabulary — Vocabulary
ISO/IEC 29167--10:20172025, Information technology — Automatic identification and data capture techniques
3)
— Part 10: Crypto suite AES-128 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 ISO/IEC 19762 and ISO/IEC 29167--10
apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:

1)
Under preparation. Stage at the time of publication: ISO/IEC DIS 18000‑63:2025.
2)
Under preparation. Stage at the time of publication: ISO/IEC FDIS 18047‑6:2025.
3)
Under preparation. Stage at the time of publication: ISO/IEC FDIS 29167‑10:2025.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
— — ISO Online browsing platform: available at https://www.iso.org/obp
— — IEC Electropedia: available at https://www.electropedia.org/
3.2 Symbols and abbreviated terms
For the purposes of this document, the symbols and abbreviated terms given in ISO/IEC 19762 apply.
4 Test methods
4.1 General
This clause describes the general test methods for ISO/IEC 29167--10. As the parts of the ISO/IEC 19823
series are always tested in relation with the ISO/IEC 18047 series, a duplication of information requirements
and specifications should be avoided.
5Clause 5 defines provides elements that are covered in the respective part of the ISO/IEC 18047 series and,
therefore, are not addressed in the ISO/IEC 19823 series. They may only be defined in theThe ISO/IEC 19823
series only defines them, if the ISO/IEC 18047 series does not define them, although. However, if applicable, a
revision of the respective part of the ISO/IEC 18047 series iswould be the preferredbetter option instead of
adding it to the ISO/IEC 19823 series.
6Clause 6 defines provides elements that are not covered by the ISO/IEC 18047 series and, therefore, are
addressed in the respective parts of the ISO/IEC 19823 series.
4.2 By demonstration
“By demonstration” means that laboratory testing of one or, if required for statistical reasons, multiple
products, processes or services to ensure conformance.
A test laboratory meeting the requirements of ISO/IEC 17025 shall be selected for the performance of the
indicated testing to ensure conformance of the component or system.
For protocol requirements that are verified by demonstration, the test conditions are specified by this
document. The detailed test plan is at the discretion of the test laboratory.
4.3 By design
“By design” means that either design parameters and/or theoretical analysis that, or both, 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 certificate 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 methods with respect to the ISO/IEC 18000 series
5.1 Test requirements for ISO/IEC 18000--3 Interrogators and Tags
The mandatory requirements and applicable optional requirementsrecommendations given in ISO/IEC TR
18047--3:20112022, 5.2 on default conditions applicable to the test methods shall be fulfilled.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Before a device under test (DUT) is tested according to this document, it shall successfully pass the following
prerequisite from ISO/IEC TR 18047--3:20112022, 5.3 on conformance tests for ISO/IEC 18000--3,
Mode:2010, MODE 1.
5.2 Test requirements for ISO/IEC 18000--63 Interrogators and Tags
The mandatory requirements and applicable optional requirementsrecommendations of ISO/IEC 18047--
6:20172025, Clauses 4 and 5 on default conditions applicable to the test methods and on set up of test
equipment, respectively, shall be fulfilled.
Before a DUT is tested according to this document, it shall successfully pass the following prerequisite from
ISO/IEC 18047--6:2017, 2025, Clause 8 on conformance tests for ISO/IEC 18000--63.
6 Test methods with respect to the ISO/IEC 29167--10 Interrogators and Tags
6.1 Test map for optional features
Table 1Table 1 lists all optional features of this crypto suite and shall be used as a template to report the test
results.
Table 1 — Test map for optional features
Mark items
Item to be tested
Feature Additional requirements Test results
for supplied
no.
product
1 TAM2 Shall be tested with the Authenticate
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
Shall be tested for all the declared memory
1.1 Memory profiles and MPI
profiles and for every supported key.
MAX_Profiles=Number of memory profiles.
MAX_KeyID=Number of keys supported.
1.21 ProtMode=0000 Shall be tested with the Authenticate
b
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
1.22 ProtMode=0001 Shall be tested with the Authenticate
b
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
1.23 ProtMode=0010 Shall be tested with the Authenticate
b
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
1.24 ProtMode=0011 Shall be tested with the Authenticate
b
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
2 IAM1 Shall be tested with the Authenticate
command of the relevant part of the
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Mark items
Item to be tested
Feature Additional requirements Test results
no. for supplied
product
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
3 IAM2 Shall be tested with the Authenticate
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
4 IAM3 Shall be tested with the Authenticate
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
5.1 Memory profiles and MPI Shall be tested for all the declared memory
profiles and for every supported key.
MAX_Profiles=Number of memory profiles.
MAX_KeyID=Number of keys supported.
5.21 ProtMode=0000b Shall be tested with the Authenticate
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
5.22 ProtMode=0001 Shall be tested with the Authenticate
b
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
5.23 ProtMode=0010 Shall be tested with the Authenticate
b
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
5.24 ProtMode=0011 Shall be tested with the Authenticate
b
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
Shall be tested with the Authenticate
6 MAM1
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
7 MAM2 Shall be tested with the Authenticate
command of the relevant part of the
ISO/IEC 15693 series or the
ISO/IEC 18000 series.
Table 3Table 3 lists all crypto suite requirements that shall be tested in dependence of the features of
Table 1Table 1 as supported by the DUT. Items marked with M are mandatory and shall be tested for each
DUT.
6.2 Additional parameters required as input for the test
Table 2Table 2 lists all additional test parameters of this crypto suite.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Table 2 — Additional test parameters
Item Feature Additional requirement Value
no.
1 Maximum BlockSize Shall be provided to ensure that only test results for
supported parameters are taken into consideration.
2 TAM2 Revision Shall be provided to ensure that only test results for 0 or 1
supported parameters are taken into consideration.
6.3 Crypto suite requirements
6.3.1 General
This clause contains allrefers to the requirements of ISO/IEC 29167--10.
6.3.2 Crypto suite requirements of ISO/IEC 29167--10:20172025, Clauses 14 to 6
All the requirements of ISO/IEC 29167--10:20172025, Clauses 14 to 6 are mandatory, inherentlyshall be
satisfied by design only.
6.3.3 Crypto suite requirements of ISO/IEC 29167--10:20172025, Clauses 7 to 12
Table 3Table 3 contains all the requirements of ISO/IEC 29167--10:20172025, Clauses 7 to 12.
Table 3 — Crypto suite requirements of ISO/IEC 29167--10:20172025, Clauses 7 to 12
Protocol
Item Verification
b
subclausesub Requirement in ISO/IEC 29167-10 M/O O Applies to
a b
no. method method
a
clause
0020 Clause 7 The Tag shall transition from the Start State to M Tag By design
Crypto suite the Next State conforming to the requirements
state diagram specified in Annex A.
Clause 8 After power-up and after a reset, the crypto
0030 M Tag By design
Initialization suite shall transition into the Initial state.
and resetting
0040 Clause 8 After the Tag encounters an error condition, it M Tag By design
shall transition into the Initial state.
0050 Clause 8 After the Tag encounters an error condition, it M Tag By design
may send an error reply to the Interrogator,
but in that case the Tag shall select one Error
Condition from the list that is specified in
Annex B.
0060 Clause 8 A transition to Initial state shall also cause a M Tag By design
reset of all variables used by the crypto suite.
0070 Clause 8 Implementations of this crypto suite shall M Tag By design
assure that all memory used for intermediate
results is cleared after each operation
(message-response pair) and after reset.
0080 9.2 The authentication message shall include the M Interrogator By design
Adding reference KeyID to select an encryption key in
custom data Table 27 (see Clause 11).
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Protocol
Item Verification
b
subclausesub Requirement in ISO/IEC 29167-10 M/O O Applies to
a b
no. method method
a
clause
0090 9.2 If protection of integrity and authenticity of M Interrogator By design
the data is requested, the selected reference
KeyID shall also contain a MAC key.
0100 9.2 A Tag that supports including custom data in M Tag By demonstration
the authentication process shall define at least using test pattern 08
one and at most 16 memory profiles.
0110 9.2 The memory profiles may also be linked to a M Tag By demonstration
key in Table 27 that shall be used for the using test pattern 07
encryption process to protect the data.
0120 9.2 The custom data block shall be defined by the M Interrogator / By design
parameters BlockSize, Profile, Offset and Tag
BlockCount.
0130 9.2 The mode of operation that shall be used for M Interrogator / By design
both the encryption and/or protection of the Tag
custom data is, as specified by ProtMode.
0140 9.2 BlockSize shall select the size of the custom M Interrogator / By design
data block; "0 " specifies custom data in 64-bit
b Tag
blocks, "1 " specifies custom data as 16-bit
b
blocks.
0150 9.2 Profile shall select one of the memory profiles M Interrogator / By design
that are supported by the Tag. The memory Tag
profiles are specified in Annex E.
0160 9.2 Maximum binary value is "1111b", or decimal M Tag By design
15, corresponding to a maximum number of
16 blocks of custom data that shall be
included.
0170 9.2 If the number of included bits of the custom M Tag By design
data including the header is not a multiple of
128, then padding with zeroes shall be applied
to the least significant bits of the last block
that has a non-zero block size of less than
128 bits.
The Interrogator shall maintain the value of
0180 9.2 M Interrogator By design
BlockCount for use as part of the MAC
verification process.
0190 9.2 The Tag manufacturer shall specify the M  By design
number of custom data blocks that can be
included.
The minimum value of D shall be 1. The
0200 9.2 M  By design
maximum value of D supported by the Tag is
specified by the Tag manufacturer.
0210 9.2 ProtMode specifies the mode of operation that M Interrogator / By design
shall be used for either the encryption and/or Tag
protection of the custom data, or both.
0220 9.3 The crypto suite shall parse the Messages and M Tag By design
Message and process the data based on the value of
response AuthMethod, which is the first parameter
formatting (first two bits) of all Messages.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Protocol
Item Verification
b
subclausesub Requirement in ISO/IEC 29167-10 M/O O Applies to
a b
no. method method
a
clause
0230 9.3 The Messages for Tag M Interrogator / By design
Authentication, Interrogator Tag
Authentication and Mutual
Authentication shall be distinguished by
AuthMethod.
0240 9.3 If AuthMethod = "00b", the Tag shall parse the M Tag By design
Message for Tag Authentication as described
in 9.4.
0250 9.3 If AuthMethod = "01b", the Tag shall parse M Tag By design
Message for Interrogator Authentication as
described in 9.5.
0260 9.3 If AuthMethod = "10 ", the Tag shall parse M Tag By design
b
Message for Mutual Authentication as
described in 9.6.
0270 9.3 If AuthMethod = "11 ", then the Tag shall M Tag By demonstration,
b
using the test pattern
return a "Not Supported" error condition.
0280 9.4.1 If CustomData = "0 ", the Tag shall parse the M Tag By demonstration,
b
TAM TAM1 Message for Tag Authentication without using the test pattern
custom data as described in 9.4.2. 03
0280 9.4.1 If CustomData = "1b", the Tag shall parse the M Tag By demonstration,
TAM2 Message for Tag Authentication with using the test pattern
TAM
custom data as described in 9.4.5. 08
9.4.2 For Tag authentication, the Interrogator shall Interrogator / By demonstration,
0280 M
TAM1 generate an 80-bit random TAM1 Interrogator Tag using the test pattern
challenge and include that in the TAM1 03
message.
The TAM1 message shall also include the
reference KeyID to select an encryption key in
Table 27 (see Clause 11).
KeyID: 8-bit value that specifies the key that
shall be used for TAM1.
0310 9.4.2 The Tag shall accept this message in any state. M Tag By design
If the value of the parameters of the message
is invalid, then the Tag shall transition to the
Initial state, thereby aborting any
cryptographic protocol that has not yet been
completed.
0330 9.4.2 If the length of the TAM1 message is <> 96 M Tag By demonstration,
bits, then the Tag shall return an "Other Error" using the test pattern
error condition. 02
0340 9.4.2 If TAM1_RFU[4:0] is <> "00000b", then the Tag M Tag By demonstration,
shall return a "Not Supported" error using the test pattern
condition. 02
0350 9.4.2 If the Tag does not support M Tag By demonstration
key[KeyID].ENC_key, then the Tag shall return using
a "Not Supported" error condition. test pattern 02
(test pattern 5)
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Protocol
Item Verification
b
subclausesub Requirement in ISO/IEC 29167-10 M/O O Applies to
a b
no. method method
a
clause
0360 9.4.3 If all parameters have been successful verified, M Tag By demonstration
then the Tag shall generate a response as using
specified in Table 5.
test pattern 03
The Tag shall generate the random data
TRnd_TAM1[31:0] and encrypt the
concatenation of the constant C_TAM1[15:0],
the random data TRnd_TAM1[31:0] and the
challenge
IChallenge_TAM1[79:0] using
Key[KeyID].ENC_key.
0380 9.4.3 After returning the TAM1 Response M Tag By design
(TResponse), the Tag shall remain in the
Initial state.
0390 9.4.4 The Interrogator (or the external application M Interrogator By demonstration
controlling the Interrogator) decrypts the using
TAM1 Response (TResponse) and shall verify test pattern 03
whether C_TAM1 and IChallenge_TAM1 have
the correct value.
9.4.5 The Interrogator shall generate an 80-bit
0400 M Interrogator By design
TAM2 random number for use as TAM2 Interrogator
Message challenge.
0410 9.4.5 BlockCount[3:0]: number that defines the size M Interrogator By design
of the custom data as a number of 16-bit or
64-bit blocks. If the number of included bits of
the custom data including header is not a
multiple of 128, then padding with zeroes
shall be applied to the least significant bits of
the last block that has a non-zero block size of
less than 128 bits.
0420 9.4.5 The Interrogator shall maintain the value of M Interrogator By design
BlockCount for use as part of the MAC
verification process.
The Tag manufacturer shall specify the
0430 9.4.5 M Tag By design
number of custom data blocks that can be
included.
0440 9.4.5 ProtMode[3:0]: value to select the mode of M Interrogator By design
operation that shall be used to process the
custom data as specified in Table 3.
0450 9.4.5 The Tag shall accept this message in any state. M Tag By design
0460 9.4.5 If the parameters of the message are invalid, M Tag By design
then the Tag shall transition to the Initial
state, thereby aborting any cryptographic
protocol that has not yet been completed.
0470 9.4.5 If the length of the TAM2 message is M Tag By demonstration
<> 120 bits, then the Tag shall return an using
"Other Error" error condition. test pattern 06
0480 9.4.5 If BlockSize = "1b" and the Tag does not M Tag By design
support value "1 ", then the Tag shall return a
b
"Not Supported" error condition.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Protocol
Item Verification
b
subclausesub Requirement in ISO/IEC 29167-10 M/O O Applies to
a b
no. method method
a
clause
0490 9.4.5 If TAM2_Rev specifies a TAM2 message format M Tag By design
that is not supported by the Tag, then the Tag
shall return a "Not Supported" error
condition.
0500 9.4.5 If TAM2_RFU[2:0] is <> "000b", then the Tag M Tag By demonstration
shall return a "Not Supported" error using
condition. test pattern 06
0510 9.4.5 If the Tag does not support M Tag By demonstration
key[KeyID].ENC_key, then the Tag shall return using
a "Not Supported" error condition. test pattern 06
0520 9.4.5 If the memory profile specified in Profile is not M Tag By demonstration
supported by the Tag, then the Tag shall using
return a "Not Supported" error condition. test pattern 06
0530 9.4.5 The Tag shall check if the specified memory M Tag By demonstration
profile has the right to use KeyID for further using
processing: else key[KeyID] is not authorized
test pattern 07
for this memory profile and the Tag shall
return a "Not Supported" error condition.
0550 9.4.5 If the block of custom data specified by M Tag By demonstration
BlockSize, Profile, Offset and BlockCount is not using
supported by the Tag, then the Tag shall test pattern 06
return a "Memory Overrun" error condition.
0560 9.4.5 If the ProtMode value is not supported by the M Tag By design
Tag, then the Tag shall return a “Not
Supported” error condition.
0570 9.4.6.1 If all parameters have been successfully M Tag By demonstration
TAM2 verified, then the Tag shall proceed with using
Response parsing the TAM2 message. test pattern 08
0580 9.4.6.1 After returning the TAM2 Response M Tag By design
(TResponse), the Tag shall remain in the
Initial state.
0590 9.4.6.2 The Tag shall add custom data in plaintext to O Tag By demonstration
TAM2_Rev = the authentication block and generate a using
"0 " and response as specified in Table 7. test pattern 08, with
b
ProtMode = profile that is
supported by the Tag
"0000b"
and ProtMode =
"0000b"
0600 9.4.6.3 The Tag shall add custom data with O Tag By demonstration
TAM2_Rev = confidentiality protection to the using
"0b" and authentication block and generate a response test pattern 08, with
ProtMode = as specified in Table 8. profile that is
"0001 " The Tag shall use AES encryption in CBC mode supported by the Tag
b
to encrypt all D custom data blocks. and ProtMode =
"0001 "
b
0620 9.4.6.4 The Tag shall add custom data with integrity O Tag By demonstration
TAM2_Rev = protection to the authentication block and using
"0 " and generate a response as specified in Table 9. test pattern 08, with
b
The Tag shall use AES-CMAC-96 to calculate profile that is
the truncated 96-bit CMAC over the supported by the Tag
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Protocol
Item Verification
b
subclausesub Requirement in ISO/IEC 29167-10 M/O O Applies to
a b
no. method method
a
clause
ProtMode = authentication block and the D following and ProtMode =
"0010 " plaintext custom data blocks. "0010 "
b b
0640 9.4.6.5 The Tag shall add custom data with O Tag By demonstration
TAM2_Rev = confidentiality and integrity protection to the using
"0 " and authentication block and generate a response test pattern 08, with
b
ProtMode = as specified in Table 10. profile that is
"0011b" The Tag shall use AES encryption in CBC mode supported by the Tag
to encrypt the initial authentication block and and ProtMode =
all following D custom data blocks. "0011b"
The Tag shall use AES-CMAC-96 to calculate
the truncated 96-bit CMAC over the
authentication block and the D following
encrypted custom data blocks.
0670 9.4.6.6 The Tag shall compute the authentication O Tag By demonstration
TAM2_Rev = block as the encryption of C_TAM2_0[15:0], using
"1 " and TRnd_TAM2[31:0] and test pattern 08, with
b
ProtMode = IChallenge_TAM2[79:0]. profile that is
"0000 " The Tag shall add the header and the custom supported by the Tag
b
data in plaintext to the authentication block and ProtMode =
and generate a response as specified in
"0000b"
Table 11.
9.4.6.7 The Tag shall compute the authentication By demonstration
0690 O Tag
TAM2_Rev = block as the encryption of C_TAM2_1[15:0], using
"1b" and TRnd_TAM2[31:0] and test pattern 08, with
ProtMode = IChallenge_TAM2[79:0]. profile that is
"0001b" The Tag shall add the header and the custom supported by the Tag
data with confidentiality protection to the and ProtMode =
authentication block and generate a response "0001b"
as specified in Table 12.
The Tag shall use AES encryption in CBC mode
to encrypt all D data blocks composed of the
header and the custom data.
0720 9.4.6.8 The Tag shall compute the authentication O Tag By demonstration
TAM2_Rev = block as the encryption of C_TAM2_2[15:0], using
"1 " and TRnd_TAM2[31:0] and test pattern 08, with
b
ProtMode = IChallenge_TAM2[79:0]. profile that is
The Tag shall add the header and the custom supported by the Tag
"0010b"
data with integrity protection to the and ProtMode =
authentication block and generate a response "0010b"
as specified in Table 13.
The Tag shall use AES-CMAC-96 to calculate
the truncated 96-bit CMAC over the
authentication block and the D following
plaintext data blocks composed of the header
and the custom data.
0750 9.4.6.9 The Tag shall add the header and the custom O Tag By demonstration
TAM2_Rev = data with confidentiality and integrity using
"1 " and protection to the authentication block and test pattern 08, with
b
ProtMode = generate a response as specified below and in profile that is
Table 14. supported by the Tag
"0011b"
The Tag shall use AES encryption in CBC mode and ProtMode =
to encrypt the initial authentication block and "0011b"
all following D data blocks composed of the
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Protocol
Item Verification
b
subclausesub Requirement in ISO/IEC 29167-10 M/O O Applies to
a b
no. method method
a
clause
header and the custom data.
The Tag shall use AES-CMAC-96 to calculate
the truncated 96-bit CMAC over the
authentication block and the D following
encrypted custom data blocks.
0780 9.4.7.2 The Interrogator (or the external application M Interrogator By demonstration
TAM2 Final controlling the Interrogator) decrypts the using test pattern 08
Interrogator TAM2 Response (TResponse) and shall verify and verifying that the
processing whether C_TAM2 and IChallenge_TAM2 have interrogator aborts if
TAM2_Rev = the local key at the
the correct value.
"0b" interrogator is
changed to a value
different from that in
the Tag
0790 9.4.7.3 The Interrogator (or the external application M Interrogator By demonstration
TAM2 Final controlling the Interrogator) decrypts the first using test pattern 08
Interrogator block of TAM2 Response (TResponse) and and verifying that the
processing shall verify whether C_TAM2 constant and interrogator aborts if
TAM2_Rev = IChallenge_TAM2 have the correct value. the local key at the
interrogator is
"1b"
changed to a value
different from that in
the Tag
0800 9.4.7.3 If ProtMode = 0000b, C_TAM2 shall be M Interrogator By design
C_TAM2_0.
0810 9.4.7.3 If ProtMode = 0001b, C_TAM2 shall be M Interrogator By design
C_TAM2_1.
0820 9.4.7.3 If ProtMode = 0010b, C_TAM2 shall be M Interrogator By design
C_TAM2_2.
0830 9.4.7.3 If ProtMode = 0011b, C_TAM2 shall be M Interrogator By design
C_TAM2_3
0840 9.5.1 If Step = "00b", the Tag shall parse the IAM1 M Tag By design
IAM Message for Interrogator Authentication as
described in 9.5.2.
0850 9.5.1 If Step = "01 ", the Tag shall parse the IAM2 M Tag By design
b
IAM and IAM3 Messages and process the data
based on the value of CustomData, which is
the third parameter in the IAM2 and IAM3
Messages.
0860 9.5.1 If Step = "01 " and CustomData = "0 ", the Tag M Tag By design
b b
shall parse the IAM2 Message for Interrogator
IAM
Authentication without custom data as
described in 9.5.5.
0870 9.5.1 If Step = "01b" and CustomData = "1b", the Tag M Tag By design
IAM shall parse the IAM3 Message for Interrogator
Authentication with custom data as described
in 9.5.8.
0880 9.5.1 If Step = "10b", the Tag shall return a "Not M Tag By design
IAM Supported" error condition.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Protocol
Item Verification
b
subclausesub Requirement in ISO/IEC 29167-10 M/O O Applies to
a b
no. method method
a
clause
0890 9.5.1 If Step = "11 ", the Tag shall return a "Not M Tag By design
b
IAM Supported" error condition.
0900 9.5.2 The Tag shall accept this message only in the M Tag By design
IAM1 Initial or the IA-OK state (unless occupied by
internal processing and not capable of
receiving messages).
0910 9.5.2 If the parameters of the message are invalid, M Tag By design
IAM1 then the Tag shall transition to the Initial
state, thereby aborting any cryptographic
protocol that has not yet been completed.
0920 9.5.2 If the length of the IAM1 message is <> 16 bits, M Tag By design
IAM1 then the Tag shall return an "Other Error"
error condition.
0930 9.5.2 If the value of IAM1_RFU[3:0] is <> "0000 ", M Tag By design
b
IAM1 then the Tag shall return a "Not Supported"
error condition.
9.5.2 If the Tag does not support
0940 M Tag By design
IAM1 key[KeyID].ENC_key, then it shall return a "Not
Supported" error condition.
0950 9.5.3 The Tag shall generate a random challenge M Tag By design
IAM1 TChallenge_IAM1[79:0] and store a copy of
TChallenge_IAM1 for subsequent verification
Response
(see 9.5.5 or 9.5.8).
The Tag shall store a copy of KeyID for use in
0960 9.5.3 M Tag By design
9.5.5 or 9.5.8.
0970 9.5.3 The Tag shall send the challenge M Tag By design
TChallenge_IAM1 in the IAM1 Response as
specified in Table 16.
0980 9.5.3 After returning the IAM1 Response M Tag By design
(TResponse), the Tag shall transition to the
IAM-Init state.
0990 9.5.4 The Interrogator (or the external application M Interrogator By design
Final controlling the Interrogator) shall decrypt a
Interrogator concatenation of C_IAM2 (DA8 ),
h
processing Purpose_IAM2[3:0], IRnd_IAM2[31:0] and
IAM1 TChallenge_IAM1 as input for the IAM2
Message or IAM3 Message.
1000 9.5.5 The Tag shall accept this message only in the M Tag By design
IAM2 IAM-Init state (unless occupied by internal
Message processing and not capable of receiving
messages).
If the Tag is not in the IAM-Init state, it shall
abort any cryptographic protocol that has not
yet been completed
and shall transition to the Initial state.
1030 9.5.5 If the length of the IAM2 message is M Tag By design
<> 136 bits, then the Tag shall return an
"Other Error" error condition.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Protocol
Item Verification
b
subclausesub Requirement in ISO/IEC 29167-10 M/O O Applies to
a b
no. method method
a
clause
1040 9.5.5 If the value of IAM2_RFU[2:0] is <> "000 ", M Tag By design
b
then the Tag shall return a "Not Supported"
error condition.
1050 9.5.5 If the parameter verifications have been M Tag By design
completed successfully, the Tag shall perform
an AES encryption of IResponse and retrieve
C_IAM2[11:0], Purpose_IAM2[3:0],
IRnd_IAM2[31:0] and TChallenge_IAM1[79:0])
for further verification.
1060 9.5.5 Cryptographic errors shall only be returned M Tag By design
after all checks have been completed.
1070 9.5.5 If the value of C_IAM2[11:0] is <> "DA8 ", then M Tag By design
h
the Tag shall return a "Not Supported" error
condition.
1080 9.5.5 If the value of Purpose_IAM2[3:0] is <> "0000 " M Tag By design
b
and not supported by the Tag, then the Tag
shall return a "Not Supported" error
condition.
1090 9.5.5 If the value for TChallenge_IAM1[79:0] is not M Tag By design
equal to the copy of TChallenge_IAM1[79:0]
that has been stored in IAM1 (see 9.5.3), then
the Tag shall return a “Cryptographic Error”
error condition.
1100 9.5.6 If the Interrogator Authentication has been M Tag By design
IAM2 completed successfully, the Tag shall respond
Response with an IAM2 Response that shall be empty
(zero bits).
1110 9.5.6 After returning the IAM2 Response M Tag By design
(TResponse), the Tag shall transition to the
IA-OK state.
1120 9.5.8.1 The Interrogator shall use IAM3 if it wants to M Interrogator By design
IAM3 write custom data in the Tag’s memory using
Message Interrogator Authentication.
1130 9.5.8.1 If ciphertext is required, the Interrogator shall M Interrogator By design
use AES in CBC decryption mode on the
custom data, using the AuthenticationBlock as
the Initialization Vector.
1140 9.5.8.1 If required, the interrogator shall use AES- M Interrogator By design
CMAC-96 to protect the integrity of the
message by calculating a message
authentication code over the authentication
block and the following D custom data blocks.
1150 9.5.8.1 If the number of included bits of the header M Interrogator By design
and custom data is not a multiple of 128, then
padding with zeroes shall be applied to the
least significant bits of the last block that has a
non-zero block size of less than 128 bits.
© ISO/IEC 2025 – All rights reserved
ISO/IEC FDIS 19823-10:2025(en)
Protocol
Item Verification
b
subclausesub Requirement in ISO/IEC 29167-10 M/O O Applies to
a b
no. method method
a
clause
1160 9.5.8.1 The Interrogator shall maintain the value of M Interrogator By design
BlockCount for use as part of the MAC
verification process.
1170 9.5.8.1 The Tag manufacturer shall specify the M  By design
number of custom data blocks that can be
included.
1180 9.5.8.1 ProtMode[3:0]: value to select the mode of M Interrogator / By design
operation that shall be used to process the Tag
custom data as specified in Table 3.
1190 9.5.8.1 The Tag shall accept this message only in the M Tag By design
IAM-Init state (unless occupied by internal
processing and not capable of receiving
messages).
1200 9.5.8.1 If the Tag is not in the IAM-Init state, it shall M Tag By design
abort any cryptographic protocol that has not
yet been completed and shall transition to the
Initial state.
1210 9.5.8.1 The Tag shall verify the length of the IAM3 M Tag By design
message.
1220 9.5.8.1 If ProtMode is "0000 " or "0001 " and the M Tag By design
b b
length of the IAM3 message is
<> (32 + 128 + D*128) bits, then the Tag shall
return an "Other Error" error condition.
If ProtMode is "0010 " or "0011 " and the
1230 9.5.8.1 b b M Tag By design
length of the IAM3 message is
<> (32 + 128 + D*128 + 96) bits, then the Tag
shall return an "Other Error" error condition.
1240 9.5.8.1 If the ProtMode value is not supported by the M Tag By design
Tag, then the Tag shall return a “Not
Supported” error condition.
1250 9.5.8.1 If the value of IAM3_RFU[1:0] is <> "00 ", t
...