Automated IoT Security

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-07-02
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)
Network Working Group                                  O. Garcia-Morchon
Internet-Draft                                                   Philips
Intended status: Informational                                   T. Dahm
Expires: January 3, 2019                                          Google
                                                           July 02, 2018

                         Automated IoT Security


   The Internet of Things (IoT) concept refers to the usage of standard
   Internet protocols to allow for human-to-thing and thing-to-thing
   communication.  The security needs are well-recognized and and many
   standardization steps for providing security have been taken, for
   example, the specification of Constrained Application Protocol (CoAP)
   over Datagram Transport Layer Security (DTLS).  However, the design
   space of IoT applications and systems is complex and exposed to
   multiple types of threats.  In particular, threats keep evolving at a
   fast pace while many IoT systems are rarely updated and still remain
   operational for decades.

   This document has three main parts: First, it summarizes exemplary
   security threats and suitable mitigation strategies to protect
   against multiple types of threats.  Second, it describes a
   comprehensive agile security framework to integrate existing security
   processes such as risk asssement or vulnerability assessment in the
   lifecycle of a smart object in an IoT application.  Thus, instead of
   having a security configuration that is fixed at manufacturing time,
   our approach allows us to apply a - security profile - on the device
   tailored for a specific environment at any point of time.  Third, we
   discuss the concept of security profiles and give examples of them.

   The core of our agile security approach relies on two protocols: the
   Protocol for Automatic Security Configuration (PASC) and the Protocol
   for Automatic Vulnerability Assessment (PAVA).  PACS is executed
   during the onboarding phase of a smart object in an IoT system and is
   in charge of automatically performing a risk assessment and assigning
   a security profile to defeat the identified risks.  The assigned
   security profile fits the specific environment and threat model of
   the application in which the device has been deployed.  PAVA is
   executed during the operation of the IoT object and ensures that
   vulnerabilities in the smart object and IoT system are discovered in
   a proactive way.  These two protocols can benefit users, manufactures
   and operators by automating IoT security.  We describe a few
   examplary security profiles that could be applicable in different

Garcia-Morchon & Dahm    Expires January 3, 2019                [Page 1]
Internet-Draft           Automated IoT Security                July 2018

   application areas and automatically configured by means of PASC and

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

   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 January 3, 2019.

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
   ( 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.

Table of Contents

   1.  Conventions and Terminology Used in this Document . . . . . .   3
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The design space of secure IoT systems  . . . . . . . . . . .   5
     3.1.  The Thing Lifecycle . . . . . . . . . . . . . . . . . . .   5
     3.2.  Classifying IoT Use Cases . . . . . . . . . . . . . . . .   6
     3.3.  Examplary use cases and security challenges . . . . . . .   7
   4.  Security Threats  . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Security Mitigations  . . . . . . . . . . . . . . . . . . . .   8
Show full document text