ISO/IEC/IEEE 8802-1AR:2014
(Main)Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Part 1AR: Secure device identity
Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Part 1AR: Secure device identity
A secure device identifier (DevID) is a cryptographic identity bound to a device used for assertion of the device's identity. ISO/IEC/IEEE 8802-1AR:2014 specifies globally unique per-device identifiers and the management and cryptographic binding of a device to its identifiers, the relationship between an initially installed identity and subsequent locally significant identities, and interfaces and methods for use of DevIDs with existing and new provisioning and authentication protocols.
Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseaux locaux et métropolitains — Partie 1AR: Identité de dispositif sécurisé
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC/
STANDARD IEEE
8802-1AR
First edition
2014-02-15
Information technology —
Telecommunications and information
exchange between systems — Local and
metropolitan area networks —
Part 1AR:
Secure device identity
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Réseaux locaux et métropolitains —
Partie 1AR: Identité de dispositif sécurisé
Reference number
ISO/IEC/IEEE 8802-1AR:2014(E)
©
IEEE 2009
---------------------- Page: 1 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
© IEEE 2009
All rights reserved. Unless otherwise specified, 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 permission in writing from ISO,
IEC or IEEE at the respective address below.
ISO copyright office IEC Central Office Institute of Electrical and Electronics Engineers, Inc.
Case postale 56 3, rue de Varembé 3 Park Avenue, New York
CH-1211 Geneva 20 CH-1211 Geneva 20 NY 10016-5997, USA
Tel. + 41 22 749 01 11 Switzerland E-mail stds.ipr@ieee.org
Fax + 41 22 749 09 47 E-mail inmail@iec.ch Web www.ieee.org
E-mail copyright@iso.org Web www.iec.ch
Web www.iso.org
Published in Switzerland
ii © IEEE 2009 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees established
by the respective organization to deal with particular fields of technical activity. ISO and IEC technical
committees collaborate in fields of mutual interest. Other international organizations, governmental and non-
governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO
and IEC have established a joint technical committee, ISO/IEC JTC 1.
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards
through a consensus development process, approved by the American National Standards Institute, which
brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers
are not necessarily members of the Institute and serve without compensation. While the IEEE administers the
process and establishes rules to promote fairness in the consensus development process, the IEEE does not
independently evaluate, test, or verify the accuracy of any of the information contained in its standards.
The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards adopted
by the joint technical committee are circulated to national bodies for voting. Publication as an International
Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is called to the possibility that implementation of this standard may require the use of subject matter
covered by patent rights. By publication of this standard, no position is taken with respect to the existence or
validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential
patents or patent claims for which a license may be required, for conducting inquiries into the legal validity or
scope of patents or patent claims or determining whether any licensing terms or conditions provided in
connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if
any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly
advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is
entirely their own responsibility. Further information may be obtained from ISO or the IEEE Standards
Association.
ISO/IEC/IEEE 8802-1AR was prepared by the LAN/MAN Standards Committee of the IEEE Computer Society
(as IEEE Std 802.1AR-2009). It was adopted by Joint Technical Committee ISO/IEC JTC 1, Information
technology, Subcommittee SC 6, Telecommunications and information exchange between systems, in parallel
with its approval by the ISO/IEC national bodies, under the “fast-track procedure” defined in the Partner
Standards Development Organization cooperation agreement between ISO and IEEE. IEEE is responsible for
the maintenance of this document with participation and input from ISO/IEC national bodies.
ISO/IEC/IEEE 8802 consists of the following parts, under the general title Information technology —
Telecommunications and information exchange between systems — Local and metropolitan area networks:
— Part 11: Wireless LAN medium access control (MAC) and physical layer (PHY) specifications
— Part 1X: Port-based network access control
— Part 1AB: Station and media access control connectivity discovery
— Part 1AE: Media access control (MAC) security
— Part 1AR: Secure device identity
— Part 1AS: Timing and synchronization for time-sensitive applications in bridged local area networks
© IEEE 2009 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
— Part 15-4: Wireless medium access control (MAC) and physical layer (PHY) specifications for low-rate
wireless personal area networks (WPANs)
iv © IEEE 2009 – All rights reserved
---------------------- Page: 4 ----------------------
�����������������-�����������
�����������������
� ����������������������������������� !�
���"���#�$�����������%
�����&���"����������%
����������������
���������������������������
����
��������������
����������������������
���� ���!�� �"##"$%&’’(!�)����
�
**�+�,������*##’
-�
���������
---------------------- Page: 5 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
Abstract: A secure device identifier (DevID) is cryptographically bound to a device and supports
authentication of the device’s identity. Locally significant identities can be securely associated with
an initial manufacturer-provisioned DevID and used in provisioning and authentication protocols to
allow a network administrator to establish the trustworthiness of a device and select appropriate
policies for transmission and reception of data and control protocols to and from the device.
Keywords: access control, authentication, authorization, certificate, LANs, local area networks,
MAC security, MANs, metropolitan area networks, PKI, port-based network access control, secure
association, secure device identifier, security, X.509
The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA
Copyright © 2009 by the Institute of Electrical and Electronics Engineers, Inc.
All rights reserved. Published 22 December 2009. Printed in the United States of America.
IEEE and 802 are registered trademarks in the U.S. Patent & Trademark Office, owned by the Institute of Electrical and
Electronics Engineers, Incorporated.
PDF: ISBN 978-0-7381-6141-9 STD96035
Print: ISBN 978-0-7381-6142-6 STDPD96035
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior
written permission of the publisher.
ii Copyright © 2009 IEEE. All rights reserved.
---------------------- Page: 6 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the
IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus
development process, approved by the American National Standards Institute, which brings together volunteers representing
varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and
serve without compensation. While the IEEE administers the process and establishes rules to promote fairness in the
consensus development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the
information or the soundness of any judgments contained in its standards.
Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other
damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting
from the publication, use of, or reliance upon this, or any other IEEE Standard document.
The IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly disclaims
any express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or that
the use of the material contained herein is free from patent infringement. IEEE Standards documents are supplied “AS IS.”
The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market,
or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at the
time a standard is approved and issued is subject to change brought about through developments in the state of the art and
comments received from users of the standard. Every IEEE Standard is subjected to review at least every five years for
revision or reaffirmation, or every ten years for stabilization. When a document is more than five years old and has not been
reaffirmed, or more than ten years old and has not been stabilized, it is reasonable to conclude that its contents, although still
of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the
latest edition of any IEEE Standard.
In publishing and making this document available, the IEEE is not suggesting or rendering professional or other services for,
or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other person or entity to
another. Any person utilizing this, and any other IEEE Standards document, should rely upon his or her independent
judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the advice of a competent
professional in determining the appropriateness of a given IEEE standard.
Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specific
applications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepare
appropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is important to ensure that any
interpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of its
societies and Standards Coordinating Committees are not able to provide an instant response to interpretation requests
except in those cases where the matter has previously received formal consideration. A statement, written or oral, that is not
processed in accordance with the IEEE-SA Standards Board Operations Manual shall not be considered the official position
of IEEE or any of its committees and shall not be considered to be, nor be relied upon as, a formal interpretation of the
IEEE. At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall
make it clear that his or her views should be considered the personal views of that individual rather than the formal position,
explanation, or interpretation of the IEEE.
Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation with
IEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate
supporting comments. Recommendations to change the status of a stabilized standard should include a rationale as to why a
revision or withdrawal is required. Comments and recommendations on standards, and requests for interpretations should be
addressed to:
Secretary, IEEE-SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854
USA
Authorization to photocopy portions of any individual standard for internal or personal use is granted by The Institute of
Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. To
arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive,
Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for educational
classroom use can also be obtained through the Copyright Clearance Center.
Copyright © 2009 IEEE. All rights reserved. iii
---------------------- Page: 7 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
Introduction
This introduction is not part of IEEE Std 802.1AR-2009, IEEE Standard for Local and metropolitan area networks—
Secure Device Identity.
A secure device identifier (DevID) is a cryptographic identity bound to a device used for assertion of the
device’s identity. IEEE Std 802.1AR specifies
— globally unique per-device identifiers and the management and cryptographic binding of a device to
its identifiers,
— the relationship between an initially installed identity and subsequent locally significant identities,
and
— interfaces and methods for use of DevIDs with existing and new provisioning and authentication
protocols.
TM
IEEE Std 802.1AR can be used in conjunction with IEEE Std 802.1X [B2] and other IEEE and industry
standards that require a secure identifier or credential as part of authentication and provisioning processes
1
that establish trust in a device.
This is the first edition of IEEE Std 802.1AR.
Notice to users
Laws and regulations
Users of these documents should consult all applicable laws and regulations. Compliance with the
provisions of this standard does not imply compliance to any applicable regulatory requirements.
Implementers of the standard are responsible for observing or referring to the applicable regulatory
requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in
compliance with applicable laws, and these documents may not be construed as doing so.
Copyrights
This document is copyrighted by the IEEE. It is made available for a wide variety of both public and private
uses. These include both use, by reference, in laws and regulations, and use in private self-regulation,
standardization, and the promotion of engineering practices and methods. By making this document
available for use and adoption by public authorities and private users, the IEEE does not waive any rights in
copyright to this document.
Updating of IEEE documents
Users of IEEE standards should be aware that these documents may be superseded at any time by the
issuance of new editions or may be amended from time to time through the issuance of amendments,
corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the
document together with any amendments, corrigenda, or errata then in effect. In order to determine whether
a given document is the current edition and whether it has been amended through the issuance
ofamendments, corrigenda, or errata, visit the IEEE Standards Association website at http://
ieeexplore.ieee.org/xpl/standards.jsp, or contact the IEEE at the address listed previously.
1
The numbers in brackets correspond to those of the bibliography in Annex D.
iv Copyright © 2009 IEEE. All rights reserved.
---------------------- Page: 8 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
For more information about the IEEE Standards Association or the IEEE standards development process,
visit the IEEE-SA website at http://standards.ieee.org.
Errata
Errata, if any, for this and all other standards can be accessed at the following URL: http://
standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL for
errata periodically.
Interpretations
Current interpretations can be accessed at the following URL: http://standards.ieee.org/reading/ieee/interp/
index.html.
Patents
Attention is called to the possibility that implementation of this standard may require use of subject matter
covered by patent rights. By publication of this standard, no position is taken with respect to the existence or
validity of any patent rights in connection therewith. A patent holder or patent applicant has filed a statement
of assurance that it will grant licenses under these rights without compensation or under reasonable rates,
with reasonable terms and conditions that are demonstrably free of any unfair discrimination to applicants
desiring to obtain such licenses. Other Essential Patent Claims may exist for which a statement of assurance
has not been received. The IEEE is not responsible for identifying Essential Patent Claims for which a
license may be required, for conducting inquiries into the legal validity or scope of Patents Claims, or
determining whether any licensing terms or conditions provided in connection with submission of a Letter of
Assurance, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this
standard are expressly advised that determination of the validity of any patent rights, and the risk of
infringement of such rights, is entirely their own responsibility. Further information may be obtained from
the IEEE Standards Association.
Copyright © 2009 IEEE. All rights reserved. v
---------------------- Page: 9 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
Contents
1. Overview . 1
1.1 Scope. 2
1.2 Purpose. 2
1.3 Relationship to other standards. 2
2. Normative references . 3
3. Definitions . 5
4. Acronyms and abbreviations . 7
5. Conformance . 9
5.1 Requirements terminology. 9
5.2 Protocol Implementation Conformance Statement. 9
5.3 Required capabilities. 9
5.4 Optional capabilities . 10
5.5 Recommended capabilities . 10
6. Secure Device Identifier Module . 11
6.1 What is a device? . 11
6.2 Components of a DevID module . 11
6.3 DevID Service Interface . 14
6.4 DevID Management Interface .20
6.5 PKI hierarchy requirements . 22
6.6 Trust Model. 24
7. DevID Credential details . 27
7.1 DevID hierarchy credential fields. 27
7.2 DevID credential fields. 27
7.3 Cryptographic Primitives. 31
8. Management Information Base . 33
8.1 Internet-Standard Management Framework . 33
8.2 Relationship to other MIB modules. 33
8.3 Structure of the MIB . 33
8.4 Security considerations . 35
8.5 Definitions for Secure Device Identifier MIB . 36
Annex A (normative) PICS Proforma . 47
A.1 Introduction. 47
A.2 Abbreviations and special symbols.47
A.3 Instructions for completing the PICS proforma. 48
A.4 PICS proforma for IEEE 802.1AR . 50
A.5 Major capabilities and options. 51
A.6 DevID Service Interface . 51
A.7 DevID Management Interface .52
A.8 DevID Supplied Information . 52
Annex B (normative) Implementing a DevID with a TPM . 53
B.1 DevID goals . 53
B.2 DevID requirements. 54
vi Copyright © 2009 IEEE. All rights reserved.
---------------------- Page: 10 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
Annex C (informative) Scenarios for DevID . 59
C.1 DevID use in EAP-TLS . 59
C.2 DevID uses in consumer devices .60
C.3 DevID uses in enterprise devices. 60
Annex D (informative) Bibliography . 63
Annex ( (informative) /LVWRISDUWLFLSDQWV . 66
Copyright © 2009 IEEE. All rights reserved. vii
---------------------- Page: 11 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
---------------------- Page: 12 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
IEEE Standard for
Local and metropolitan area networks—
Secure Device Identity
IMPORTANT NOTICE: This standard is not intended to ensure safety, security, health, or
environmental protection in all circumstances. Implementers of the standard are responsible for
determining appropriate safety, security, environmental, and health practices or regulatory requirements.
This IEEE document is made available for use subject to important notices and legal disclaimers. These
notices and disclaimers appear in all publications containing this document and may be found under the
heading “Important Notice” or “Important Notices and Disclaimers Concerning IEEE Documents.”
They can also be obtained on request from IEEE or viewed at http://standards.ieee.org/IPR/
disclaimers.html.
1. Overview
®
IEEE 802 Local Area Networks (LANs) are often deployed in networks that provide publicly accessible
service access or that cannot be completely physically secured. The protocols that configure, manage, and
regulate access to these networks and network-based services and applications typically run over the
networks themselves. Secure and predictable operation of such networks depends on authenticating each
device attached to and participating in the network, so that the degree of trust and authorization to be
accorded to that device by its communicating peers can be determined.
Authentication of a human user, through a credential known to or possessed by that user, is often used to
authenticate users of devices such as laptop personal computers. However many of the devices that compose
a network are designed for unattended autonomous operation and might not support user authentication.
These include the routers and bridges that interconnect and provide access to the LANs. Further, the
previously common assumption that network access controls were to provide protection of the network
against abuse through unauthenticated and unauthorized access, while offering no protection to the
accessing devices, is now known not only to expose those devices but also the network itself. Failure to
provide devices that access the network with the mutual guarantee that they are connected to legitimate
network access points allows malicious devices to interpose themselves between the network and its
authenticated and authorized users, and effectively make use of the credentials of the latter. For these
reasons a secure device identifier, i.e., one that embodies an authentication credential that cannot be easily
removed or copied for use in a device under the control of someone who wishes to gain unauthorized access
to or attack the operation of a network, is highly desirable.
Protocols for configuring, managing and regulating access to a network depend on the existence of a device
identifier or human authentication of initial access to associate a device with an authentication credential.
Copyright © 2009 IEEE. All rights reserved. 1
---------------------- Page: 13 ----------------------
ISO/IEC/IEEE 8802-1AR:2014(E)
IEEE
Std 802.1AR-2009 IEEE STANDARD FOR LOCAL AND METROPOLITAN AREA NETWORKS—
This results in a “chicken-and-egg” scenario, wherein these credentials often must be installed during an
expensive “pre-provisioning” process before actual deployment. Even when device credentials are deployed
in-place, the process is often interactive, involving a physically secured connection to the device being
deployed and a knowledgeable system administrator.
Secure Device Identifiers (DevIDs) are designed to be used as interoperable secure device authentication
credentials with Extensible Authentication Protocol (EAP) and other industry standard authentication and
provisioning protocols. A standardized device identity facilitates interoperable secure device authentication
that helps simplify and standardize secure deployment and management of devices. This standard will be of
benefit to manufacturers of conformant LAN equipment, their customers, and users of LANs or LAN
services that are based on such equipment.
A device with DevID capability incorporates a globally unique manufacturer provided Initial Device
Identifier (IDevID), stored in a way that protects it from modification. The device may support the creation
of Locally Significant Device Identifiers (LDevIDs) by a network administrator. Each LDevID is bound to
the device in a way that makes it infeasible for it to be forged or transferred to a device with a different
IDevID without knowledge of the private key used to effect the cryptographic binding. LDevIDs can
incorporate, and fully protect, additional information specified by the network administrator to support local
authorization conventions. LDevIDs may also be used as the sole identifier (by disabling the IDevID) to
assure the privacy of the user of a DevID and the
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.