CAN/CSA-ISO/IEC 25185-1:18 (R2022)

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Symbols and abbreviated terms
5 Data dictionary
6 Authentication Protocol Description
7 Application identification
8 Command set
9 Status bytes and error handling
10 Key diversification
11 Session key generation
12 Default mode
Annex A (normative) - Test vectors
Annex B (informative) - Key management policy
Annex C (informative) - Keyset management
Annex D (informative) - Reference implementation
Annex E (informative) - Identity leakage considerations
Annex F (informative) - Operational mode management
Annex G (informative) - PLAID security features
Bibliography

Standards development within the Information Technology sector is harmonized with international standards development. Through the CSA Technical Committee on Information Technology (TCIT), Canadians serve as the SCC Mirror Committee (SMC) on ISO/IEC Joint Technical Committee 1 on Information Technology (ISO/IEC JTC1) for the Standards Council of Canada (SCC), the ISO member body for Canada and sponsor of the Canadian National Committee of the IEC. Also, as a member of the International Telecommunication Union (ITU), Canada participates in the International Telegraph and Telephone Consultative Committee (ITU-T). Scope This International Standard provides an authentication protocol suitable for use in physical and logical access control systems based on ICCs and related systems which support standards based AES-128 and RSA-2048 ciphers and the SHA-256 hashing algorithm. The standard specifies PLAID and its implementation in sufficient detail to allow any two or more implementations to be interoperable. This International Standard does not address how implementations share cryptographic keys, access control system credential records (including revocation) or manage payload entities such as PIN, PINHash, or biometric templates or other payload objects.

CSA Preface Standards development within the Information Technology sector is harmonized with international standards development. Through the CSA Technical Committee on Information Technology (TCIT), Canadians serve as the SCC Mirror Committee (SMC) on ISO/IEC Joint Technical Committee 1 on Information Technology (ISO/IEC JTC1) for the Standards Council of Canada (SCC), the ISO member body for Canada and sponsor of the Canadian National Committee of the IEC. Also, as a member of the International Telecommunication Union (ITU), Canada participates in the International Telegraph and Telephone Consultative Committee (ITU-T). For brevity, this Standard will be referred to as “CAN/CSA-ISO/IEC 25185-1” throughout. At the time of publication, ISO/IEC 25185-1:2016 is available from ISO and IEC in English only. CSA Group will publish the French version when it becomes available from ISO and IEC. This Standard was reviewed by the CSA TCIT under the jurisdiction of the CSA Strategic Steering Committee on Information and Communications Technology and deemed acceptable for use in Canada. From time to time, ISO/IEC may publish addenda, corrigenda, etc. The TCIT will review these documents for approval and publication. For a listing, refer to the Current Standards Activities page at standardsactivities.csa.ca. This Standard has been formally approved, without modification, by the Technical Committee and has been developed in compliance with Standards Council of Canada requirements for National Standards of Canada. It has been published as a National Standard of Canada by CSA Group.  Scope This International Standard provides an authentication protocol suitable for use in physical and logical access control systems based on ICCs and related systems which support standards based AES-128 and RSA-2048 ciphers and the SHA-256 hashing algorithm. The standard specifies PLAID and its implementation in sufficient detail to allow any two or more implementations to be interoperable. This International Standard does not address how implementations share cryptographic keys, access control system credential records (including revocation) or manage payload entities such as PIN, PINHash, or biometric templates or other payload objects.