Security Classes for IoT devices
draft-urien-lwig-security-classes-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-11-22
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
LWIG Working Group P. Urien
Internet Draft Telecom ParisTech
Intended status: Experimental
November 22 2018
Expires: May 2019
Security Classes for IoT devices
draft-urien-lwig-security-classes-00.txt
Abstract
This draft attempts to define security classes for constraint IoT
devices. A device security is characterized by five Boolean security
attributes: one time programmable memory (OTP), firmware loader
(FLD), secure firmware loader (FLD-SEC), tamper resistant key (TRT-
KEY) and diversified key (DIV-KEY).
This leads to the definition of 6 classes of devices, embedding or
not OTP resource, whose security increases with the class number (0
to 5). The suffix + indicates OTP availability.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 2019.
.
Urien Expires May 2019 [Page 1]
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
Urien Expires May 2019 [page 2]
Security Classes for IoT devices November 2018
Table of Contents
Abstract........................................................... 1
Requirements Language.............................................. 1
Status of this Memo................................................ 1
Copyright Notice................................................... 2
1 Overview......................................................... 4
2 Security Attributes.............................................. 6
2.1 One Time Programmable Memory, OTP........................... 6
2.2 Firmware Loader, FLD........................................ 6
2.3 Secure Firmware Loader, FLD-SEC............................. 6
2.4 Tamper Resistant Key, TRT-KEY............................... 6
2.5 Diversified Key, DIV-KEY.................................... 7
3 IANA Considerations.............................................. 7
4 Security Considerations.......................................... 7
5 References....................................................... 7
5.1 Normative References........................................ 7
5.2 Informative References...................................... 7
6 Authors' Addresses............................................... 7
Urien Expires May 2019 [Page 3]
Security Classes for IoT devices November 2018
1 Overview
This draft attempts to define security classes for IoT devices,
supporting SUIT [SUIT] protocols. The goal is to provide a
qualitative estimation of risks induced by firmware remote updates
according to device logical and hardware security resources.
According to this draft a device comprises a main processor (MP), an
Show full document text