draft-morais-iotops-inxu-01.xml

<?xml version='1.0' encoding='utf-8'?>
<!-- This template is for creating an Internet Draft using xml2rfc,
    which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<rfc
      xmlns:xi="http://www.w3.org/2001/XInclude"
      category="std"
      docName="draft-morais-iotops-inxu-00"
      ipr="trust200902"
      obsoletes=""
      updates=""
      submissionType="IETF"
      xml:lang="en"
      tocInclude="true"
      tocDepth="4"
      symRefs="true"
      sortRefs="true"
      version="3">

 <!-- ***** FRONT MATTER ***** -->

 <front>

   <title abbrev="INXU">Intra-Network eXposure analyzer Utility Specification</title>
   <!--<workgroup>IOT Operations Working Group</workgroup>-->
    <seriesInfo name="Internet-Draft" value="draft-morais-iotops-inxu-00"/>

   <author fullname="Sávyo Vinícius de Morais" initials="S.V." surname="Morais">
      <organization>IFRN</organization>
      <address>
        <postal>
          <street/>

         <city>Natal</city>
          <region/>
          <code/>
          <country>BR</country>
        </postal>
        <email>savyovm@gmail.com</email>
     </address>
    </author>

   <author fullname="Claudio Miceli de Farias" initials="C.M." surname="Farias">
      <organization>UFRJ</organization>
      <address>
        <postal>
          <street/>

         <city>Rio de Janeiro</city>
          <region/>
          <code/>
          <country>BR</country>
        </postal>
        <email>cmicelifarias@gmail.com</email>
     </address>
    </author>
    <date year="2022"/>

   <!-- Meta-data Declarations -->

   <area>Operations and Management</area>
    <workgroup>IOT Operations Working Group</workgroup>

   <keyword>MTD, INXU</keyword>

   <abstract>
      <t>
        This document proposes the Intra-Network eXposure analyzer Utility (INXU) as a vulnerability management solution for IoT networks. The goal of INXU is to take advantage of the functions of the RFC 8520 to allow a Security Experts Team on protecting multiple heterogeneous IoT networks, even when there is a few or none private information of the networks.
      </t>
      <t>
        INXU identifies and analyzes the capability of an IoT device being exploited by an well known malicious activity. We also propose the Malicious Traffic Description (MTD), a data-model to describe traffic related to malicious activities.
      </t>
    </abstract>
  </front>
  <middle>
    <section numbered="true" toc="default">
      <name>Introduction</name>
      <t>
        While more Internet of Things (IoT) devices are deployed, the vulnerability management process turns even more difficult. This is mostly caused by the high heterogeneity and density of the IoT systems and devices, and challenges security teams on keeping Firewall and Intrusion Detection/Prevention Systems (IDS/IPS) rules up to date.
      </t>
      <t>
        In some way, the Manufacturer Usage Description (MUD) <xref target="RFC8520" format="default"/> provides an alternative protection by reducing the capability of an IoT device being exploited -- as vector or target -- by malicious activities over the Internet. MUD does this by providing means to automatically build an allow-list of the IoT devices in a network based on the device manufacturers specification of expected traffic. This improves devices security by reducing their threat surface by blocking traffic with unexpected nodes/protocols, but still allows attacks which exploit vulnerabilities into the allowed traffic.
      </t>
      <t>
        Besides this lack, the implementation of the <xref target="RFC8520" format="default"/> provides information that can support the identification of well-known vulnerabilities, as mentioned in its specification. This can be done by combining the allow-lists provided by the MUD manager into a communication graph of the connected IoT devices. With the communication graph, we can compare the traffic allowed by MUD with signatures of well-known malicious activities to identify -- and potentially block -- exposure of vulnerabilities into the network.
      </t>
      <t>
        Integrating this analysis in traditional IDS or IPS can improve their efficacy and cover the MUD lack, but they only apply for scenarios where there is a security management team, such as corporate, smart grid and industrial IoT networks. On the other hand, in scenarios where there is a high heterogeneity of devices and low (or none) specialized support, such as in Home IoT Networks and Smart Cities, the process for keeping the attack signatures updated is not that simple.
      </t>
      <t>
        Therefore, envisioning to overcome this gap, this document proposes INXU (Intra Network eXposure analyzer Utility) as a security tool that takes advantage of the MUD-based network communication graph to prevent the exploitation of well-known vulnerabilities. To do this, INXU blocks threats on the Local Area Network (LAN) after identifying them by comparing the signature of well-known malicious activities with the traffic flow allowed by the MUD. In short words, while MUD builds allow-lists, INXU builds a blocklist on top of MUD's allow-lists.
      </t>
      <t>
        The core component of INXU is Malicious Traffic Description (MTD), a document produced by a security specialist that describes ongoing malicious activities and well-known vulnerabilities and helps INXU find chains of connected IoT devices that can expose them to a threat. On top of MUD's threat surface reduction, INXU adds another security layer that enables protection against incidents not addressed or even caused by the manufacturers.
      </t>
      <t>
        The MTD data model, as in MUD, abstracts network addresses to allow describing the traffic without the need to know the network's addressing schema or the connected devices. This resource allows creating portable descriptions of malicious traffic and protects the privacy in the LAN by not exposing private information to third parties in the security decision-making process. At the same time, it simplifies the sharing of knowledge about attacks between distinct networks.
      </t>
      <t>
        Another relevant feature in INXU is its architecture that enables one Security Operation Center (SOC) to protect multiple distinct networks by sharing MTDs in a process similar to computer antivirus vaccines. This feature makes INXU a tool to protect LANs and the entire Internet ecosystem by making the operation of botnets and other attacks that affect the Internet's stability more difficult.
      </t>
      <section numbered="true" toc="default">
        <name>Simple Example</name>
        <t>
          An Internet Service Provider (ISP) connects tens to hundreds of houses to the Internet. Each one of these homes contains a wide range of IoT devices connected in their internal networks, in diverse topologies, and with different usages by each end-user. By the variety of scenarios, these home networks potentially contain a few devices infected by a DDoS capable botnet.
        </t>
        <t>
          Due to the attacks carried by this botnet, frequently the ISP has a considerable part of its traffic being consumed by DDoS attacks, and often the clients call helpdesk for problems with devices caused by the botnet. The ISP knows that the malware's infection occurs by a TCP/23 connection with a neighbour host, and the command and control occurs by a TCP/80 connection with a server located at mybotnet.example.com.
        </t>
        <t>
          With this information, the ISP releases an MTD File describing this traffic, which can be used by its clients. In the home networks, the Customer Premises Equipment (CPE) collects the MTD File and compares it to the network communication graph provided by MUD, identifies exposures of vulnerabilities internally into the network, INXU evaluates the risk of the exposures and suggests blocks to prevent exploitations.
        </t>
      </section>
      <section numbered="true" toc="default">
        <name>Key Aspects</name>
        <t>
          This work in progress aims to propose a tool that reinforces IoT networks' security by taking advantage of the functions provided by the <xref target="RFC8520" format="default"/>. The specific contributions of INXU are listed below:
        </t>
        <ul spacing="normal">
          <li>Simplify the process of sharing attack signatures that targets or exploits IoT systems;</li>
          <li>Allow a small team of security specialists to protect multiple distinct IoT networks without expose the networks’ privacy;</li>
          <li>Protect the Internet’s ecosystem by hindering distributed attacks that targets its infrastructure.</li>
        </ul>
      </section>
      <section numbered="true" toc="default">
        <name>INXU Intended Use</name>
        <t>
          The intended use for INXU is in the support of the vulnerability management of diverse heterogeneous IoT networks in scenarios where there is a small team of security specialists (e.g. Smart Cities). It is also intended to be used in scenarios where the end networks need their privacy kept, as Home IoT networks.
        </t>
        <t>
          The deployment of INXU in networks populated by both IoT and general purpose devices is NOT RECOMMENDED. Due to the greater computing power and wider openness to other attacks, general purpose devices might expose the IoT network to unnecessary risk. Instead of having both types on the same sub-network, we recomend to isolate IoT devices in a separate sub-network as they announce their MUD URLs, and developers should take advantage of MUD's "controller" and "my-controller" hosts as application gateway between general purpose and IoT devices. In the case of needing a direct communication between the two categories, this could be specified with MUD's "local-networks" specification.
        </t>
      </section>
      <section numbered="true" toc="default">
        <name>Terminology</name>

        <ul>
          <li>INXU:         Intra-Network eXposure analyzer Utility.</li>
          <li>INXU Module:  a system that crosses data from malicious activities and MUD’s allow-lists to identify and analyze the exposure of vulnerabilities in the connected IoT devices.</li>
          <li>MTD:          Malicious Traffic Description data model.</li>
          <li>MTD File:     a file that contains descriptions of traffic associated with malicious activities that targets or exploits IoT devices.</li>
          <li>MTD Manager:  a system that requests and receives the MTD File. It is responsible for verifying MUD File’s authenticity and integrity. The MTD Manager also requests the MTD File after it’s cache validity expires.</li>
          <li>MTD URL:      a URL, configured in the MTD Manager, that locates the MTD File provided by the SOC in charge to protect the client network.</li>
          <li>MTD Server:   a web server, managed by the SOC, that hosts the MTD File.</li>
        </ul>

        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119" format="default"/><xref target="RFC8174" format="default"/> when, and only when, they appear in all capitals, as shown here.</t>
      </section>
    </section>
    <section anchor="mtd" numbered="true" toc="default">
      <name>The MTD Data Model</name>
      <t>
        The main aim of this data model is to enable describing malicious traffic so that distinct networks can interpret and implement security measures, no matter the connected IoT devices or network topology. Another feature addressed by this data model is allowing the association between the detected exposure and the malicious activity that exploits it, as well as the grouping of vulnerabilities related to the same malicious activity.
      </t>
      <t>
        The MTD data model makes use of Access Control Lists (ACLs) <xref target="RFC8519" format="default"/> under YANG language <xref target="RFC7950" format="default"/> to describe the malicious traffic, addressing the classification feature. Furthermore, such as in MUD, there are available two network address abstractions to describe the traffic so that different networks can adapt the description to its context: one abstraction for addresses in the local networks, and the other for using domain names to hosts on the Internet. The data model also includes control fields that support the manageability of the MTD File, so the contained data can be categorized in control data and description data.
      </t>
      <t>
        This data model covers the complete description of malicious activities from simple attacks with just a few ACE inputs to complex malware that exploits many different vulnerabilities and network resources. Furthermore, to prevent false-positive threat detections, the MTD data model allows inserting context information into the descriptions. The context information in the MTD data model plays the role of specifying the correlation between the described malicious traffic, determining the combinations of exposures that become a risk, and suggesting the action to be taken with each detected threat. This feature supports reducing false-positive detection, as a single traffic exposure may not represent a threat itself.
      </t>
      <t>
        Basically the context information supports the categorization of a set of vulnerabilities as an effective threat or not. To incorporate the contextual information, we considered the statements listed below, which were assimilated from the IoTSec ontology in <xref target="Mozzaquatro2015" format="default"/>:
      </t>
      <ul>
        <li>A Threat represents an effective risk if the exposure of one or more vulnerabilities can be exploited by an attacker;</li>
        <li>A Vulnerability does not represent a risk by itself, as it can be hidden behind security mechanisms, such as blocking its exposure for potential attackers.</li>
      </ul>
      <t>
        So, in short words, an asset is under threat only when an attacker can exploit one or more vulnerabilities to take advantage of it. Thus, merging the concepts from the ontology and the aims on MTD data model, this document considers the following statements:
      </t>
      <ul>
        <li>
          Each Access Control Entry (ACE) has an associated severity defined by the unsigned integer field named risk. When the exposure to the ACE is detected, its risk is considered part of its ACL's vulnerability classification;
        </li>
        <li>
          Each ACL has alert-threshold and risk-threshold fields, both represented by unsigned integer values. When the sum of the exposed ACEs risks reaches the risk threshold, the exposure to the ACL is considered as a vulnerability;
        </li>
        <li>
          Each malicious activity described contains a list of critical ACL sets. A malware or attack is classified as a threat when at least one set of critical ACLs contains all its ACLs classified as a vulnerability exposure. When one set's condition is satisfied, its associated action-to-take has to be triggered.
        </li>
      </ul>
      <t>
        The three possible actions to be taken are listed below:
      </t>
      <ul>
        <li>
          block-all: blocks all ACLs that expose vulnerabilities related to the description. Expected to be used when any traffic associated with the malware or attack threatens the IoT device;
        </li>
        <li>
          block-attack: blocks all ACLs that expose vulnerabilities under the attack-traffic group. Expected to be used when only risky ACLs associated with attacks (isolated or in the context of a malware) threatens the IoT device;
        </li>
        <li>
          block-not-attack: blocks all ACLs that expose vulnerabilities under the malware's not-attack-traffic group. Expected to be used when just blocking the operation traffic of a malware prevents exploitation.
        </li>
      </ul>
      <section numbered="true" toc="default">
        <name>The draft-inxu-mtd YANG Module</name>
        <t>
          A simplified graphical representation of the data models is used in this document. The meaning of the symbols in these diagrams is explained in <xref target="RFC8340" format="default"/>.
        </t>
        <artwork name="" type="" align="left" alt=""><![CDATA[
module: draft-inxu-mtd
  +--rw mtd!
     +--rw mtd-url                   inet:uri
     +--rw last-update               yang:date-and-time
     +--rw mtd-signature?            inet:uri
     +--rw cache-validity?           uint8
     +--rw malicious-descriptions
        +--rw malicious-list* [name]
           +--rw name                       string
           +--rw specific-devices*          inet:uri
           +--rw critical-acl-sets* [name]
           |  +--rw name                string
           |  +--rw critical-acl-set*   -> /acl:acls/acl/name
           |  +--rw action-to-take      draft-inxu-mtd:action-to-take
           +--rw to-device-attacks
           |  +--rw traffic-lists
           |     +--rw traffic-list* [name]
           |        +--rw name                -> /acl:acls/acl/name
           |        +--rw specific-devices*   inet:uri
           +--rw from-device-attacks
           |  +--rw traffic-lists
           |     +--rw traffic-list* [name]
           |        +--rw name                -> /acl:acls/acl/name
           |        +--rw specific-devices*   inet:uri
           +--rw to-device-not-attacks
           |  +--rw traffic-lists
           |     +--rw traffic-list* [name]
           |        +--rw name                -> /acl:acls/acl/name
           |        +--rw specific-devices*   inet:uri
           +--rw from-device-not-attacks
              +--rw traffic-lists
                 +--rw traffic-list* [name]
                    +--rw name                -> /acl:acls/acl/name
                    +--rw specific-devices*   inet:uri

  augment /acl:acls/acl:acl/acl:aces/acl:ace/acl:matches:
    +--rw mtd
       +--rw local-networks?   empty
  augment /acl:acls/acl:acl/acl:aces/acl:ace:
    +--rw risk?   uint8
  augment /acl:acls/acl:acl:
    +--rw risk-threshold?    uint8
    +--rw alert-threshold?   uint8
  augment /acl:acls/acl:acl/acl:aces/acl:ace/acl:matches/acl:l4/acl:tcp/acl:tcp:
    +--rw direction-initiated?   mud:direction
  augment /acl:acls/acl:acl/acl:aces/acl:ace/acl:matches/acl:l3/acl:ipv4/acl:ipv4:
    +--rw src-dnsname?   inet:host
    +--rw dst-dnsname?   inet:host
  augment /acl:acls/acl:acl/acl:aces/acl:ace/acl:matches/acl:l3/acl:ipv6/acl:ipv6:
    +--rw src-dnsname?   inet:host
    +--rw dst-dnsname?   inet:host
        ]]></artwork>
      </section>
      <section numbered="true" toc="default">
        <name>MTD Data Model Definition of Control Fields in the Root “mtd” Container</name>
        <t>
          Here we describe the leafs placed into the “mtd” root container that plays the role of controlling the operation of the MTD File.
        </t>
        <section numbered="true" toc="default">
          <name>mtd-url</name>
          <t>
            Required field that stores the URL where the security authority hosts the MTD File.
          </t>
        </section>
        <section numbered="true" toc="default">
          <name>mtd-signature</name>
          <t>
            Optional field used to store a URL where the MTD File signature file can be found. It is applicable for offline authenticity verification of the file.
          </t>
        </section>
        <section numbered="true" toc="default">
          <name>last-update</name>
          <t>
            Required field that contains the timestamp information of the MTD File generation.
          </t>
        </section>
        <section numbered="true" toc="default">
          <name>cache-validity</name>
          <t>
            Optional field that contains the number of hours to the expiration of the MTD File, starting from “last-update”. This field supports integer values between 1 and 160, and if not defined, it is assumed to be 48 hours by the MTD Manager.
          </t>
        </section>
      </section>
      <section numbered="true" toc="default">
        <name>MTD Data Model Definition of Traffic Description Fields in the Root “mtd” Container</name>
        <t>
          The traffic description fields are organized under the “malicious-descriptions” container. The description of a malicious activity allows the aggregation of different attacks, and also other not attack traffic that only turn into malicious when related to the malware operation. This aggregation is important for the security measures decision-making process, as sometimes only a traffic combination makes the threat effective or blocking just one type of traffic can almost disable it, such as the Mirai's Command and Control traffic.
        </t>
        <t>
          The description of each leaf is detailed in the Sub-Sections below.
        </t>
        <section numbered="true" toc="default">
          <name>traffic-list</name>
          <t>
            List type field to specify all the traffic in the same direction (incoming/outgoing) that is associated with one attack-traffic or not-attack-traffic.
          </t>
          <section numbered="true" toc="default">
            <name>name</name>
            <t>
              Required string field with the name of the ACL that describes one attack-traffic or not-attack-traffic;
            </t>
          </section>
          <section numbered="true" toc="default">
            <name>specific-devices</name>
            <t>
              Optional list to specify the MUD URLs of the IoT devices affected by the described traffic. When this field is filled, INXU only considers the devices here listed as targets of these ACLs.
            </t>
          </section>
        </section>
        <section numbered="true" toc="default">
          <name>malicious-descriptions</name>
          <t>
            List that holds the traffic description of all the malicious activities covered by the MTD File.
          </t>
          <section numbered="true" toc="default">
            <name>name</name>
            <t>
              Required string field to uniquely name the described malicious activity.
            </t>
          </section>
          <section numbered="true" toc="default">
            <name>specific-devices</name>
            <t>
              Optional list to specify the MUD URLs of the IoT devices that can be affected by the malicious activity. When this field is filled, INXU only considers the devices here listed as affected by this malicious activity.
            </t>
          </section>
          <section numbered="true" toc="default">
            <name>critical-acl-sets</name>
            <t>
              List to specify all the sets of critical ACL and their respective actions to take when all listed ACLs get classified as risky.
            </t>
            <section numbered="true" toc="default">
              <name>critical-acl-set</name>
              <t>
                List to specify a set of ACLs that, when all listed ACLs get classified as risky, represents a threat caused by the malicious activity.
              </t>
            </section>
            <section numbered="true" toc="default">
              <name>action-to-take</name>
              <t>
                Mandatory leaf to specify the action to be taken when the respective set of critical ACLs turns into a threat. The action can be “block-all”, “block-attack”, or “block-not-attack”.
              </t>
            </section>
          </section>
          <section numbered="true" toc="default">
            <name>to-device-attacks</name>
            <t>
              Container that holds all the malicious activity's attack traffic targeting an IoT device on the LAN.
            </t>
          </section>
          <section numbered="true" toc="default">
            <name>from-device-attacks</name>
            <t>
              Container that holds all the malicious activity's attack traffic outgoing from an IoT device on the LAN.
            </t>
          </section>
          <section numbered="true" toc="default">
            <name>not-attack-traffic</name>
            <t>
              Container that holds the traffic not related to attacks, but that turns into malicious when in this context.
            </t>
            <section numbered="true" toc="default">
              <name>to-device-not-attack-traffic</name>
              <t>
                List with all the ACLs that describe malicious not attack traffic targeting an IoT device on the LAN.
              </t>
            </section>
            <section numbered="true" toc="default">
              <name>from-device-not-attack-traffic</name>
              <t>
                List with all the ACLs that describe malicious not attack traffic outgoing from an IoT device on the LAN.
              </t>
            </section>
          </section>
        </section>
      </section>
      <section numbered="true" toc="default">
        <name>Augmentation to the ACL Model</name>
        <t>
          This section describes the proposed augments to the ACL model. These augments are responsible for creating the abstraction for the traffic descriptions, enabling the portability of the knowledge to the different networks, and supporting the risk assessment of each vulnerability exposure.
        </t>
        <section numbered="true" toc="default">
          <name>mtd:local-networks</name>
          <t>
            Optional leaf that, when present, means that the current ACE applies to any device on the local IP networks.
          </t>
        </section>
        <section numbered="true" toc="default">
          <name>direction-initiated</name>
          <t>
            Optional field incorporated from MUD to specify the TCP initiator.
          </t>
        </section>
        <section numbered="true" toc="default">
          <name>src-dnsname and dst-dnsname</name>
          <t>
            Optional field to enable the usage of DNS domain names to specify the remote host instead of using IPv4 or IPv6 addresses.
          </t>
        </section>
        <section numbered="true" toc="default">
          <name>risk</name>
          <t>
            Optional unsigned integer field to specify the risk associated with the exposure of the specified ACE. Its default value is 1.
          </t>
        </section>
        <section numbered="true" toc="default">
          <name>risk-threshold</name>
          <t>
            Optional unsigned integer field to specify the minimal ACL risk value to classify it as a vulnerability exposure. The ACL's risk value is calculated by the sum of all its child ACE exposures' risks. Its default value is 1.
          </t>
        </section>
        <section numbered="true" toc="default">
          <name>alert-threshold</name>
          <t>
            Optional unsigned integer field to specify the minimal ACL risk value to trigger an alert to the exposure. The ACL's risk value is calculated by the sum of all its child ACE exposures' risks. Its default value is 1.
          </t>
        </section>
      </section>
      <section numbered="true" toc="default">
        <name>The MTD YANG Model</name>
        <artwork align="left" name="" type="" alt=""><![CDATA[
<CODE BEGINS>file "draft-inxu-mtd@2021-11-22.yang"
module draft-inxu-mtd{
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:draft-inxu-mtd";
  prefix draft-inxu-mtd;

  import ietf-yang-types {
    prefix yang;
  }

  import ietf-access-control-list {
    prefix acl;
  }

  import ietf-inet-types {
    prefix inet;
  }

  import ietf-mud {
    prefix mud;
  }

  import ietf-acldns {
    prefix acldns;
  }

  organization "IETF IOTOPS (IOT Operations) Working Group";
  contact
    "WG Web: http://tools.ietf.org/wg/iotops/
     WG List: iotops@ietf.org
     Author: Sávyo Morais
     savyovm@gmail.com
     Author: Claudio Farias
     cmicelifarias@gmail.com";

  description 
    "This module is a data-model to describe malicious network 
    traffic.

    This module is intended to be serialized via JSON and stored
    as a file, as described in I-D draft-morais-iotops-inxu-01.

    The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
    NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
    'MAY', and 'OPTIONAL' in this document are to be interpreted as
    described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
    they appear in all capitals, as shown here.

    Copyright (c) 2022 IETF Trust and the persons identified as
    authors of the code.  All rights reserved.

    Redistribution and use in source and binary forms, with or
    without modification, is permitted pursuant to, and subject
    to the license terms contained in, the Simplified BSD License
    set forth in Section 4.c of the IETF Trust's Legal Provisions
    Relating to IETF Documents
    (http://trustee.ietf.org/license-info).

    This version of this YANG module is part of 
    I-D draft-morais-iotops-inxu-01; see the I-D itself for 
    full legal notices.";

  revision 2022-05-15{
    description
      "Simplifying the data model to one single description of 
      malicious traffic.";
    reference
      "draft-morais-iotops-inxu-01: Intra-Network eXposure analyzer 
                                    Utility Specification";
  }

  typedef action-to-take {
    description
      "Type to specify the action to take when a threat is detected";

    type enumeration {
      enum "alert" {
        value 0;
        description
          "Alert user about a risky exposure";
      }
      enum "block-not-attack" {
        value 1;
        description
          "Block risky exposures of not-attack-traffic and warns uses 
          about attack-traffic alert exposures";
      }
      enum "block-attack" {
        value 2;
        description
          "Block attack-traffic risky exposures and alert users about 
          the block";
      }
      enum "block-all" {
        value 3;
        description
          "Block all risky exposures and alert users about the block";
      }
    }
  }

  container mtd {
    presence "Enabled for this particular MTD URL";
    description "MTD-related information";
    uses mtd-groupig;
  }

  grouping mtd-groupig {
    description 
      "This grouping is to create a set of definitions of 
      malicious traffic of malware and attacks.";

    leaf mtd-url{
      type inet:uri;
      mandatory true;
      description 
        "This is the MTD URL associated with the entry found 
        in a MTD File";
    }

    leaf last-update {
      type yang:date-and-time;
      mandatory true;
      description 
        "This is intended to be set when the current MTD File is 
        generated. MTD Managers SHOULD NOT check for updates 
        between this time plus cache validity.";
    }

    leaf mtd-signature {
      type inet:uri;
      description 
        "A URI that resolves to a signature file to verify the 
        autenticity of the MTD File.";
     }

    leaf cache-validity {
      type uint8 {
        range "1..168";
      }

      units "hours";
      default "48";
      description 
        "The information retrieved from the MTD Server is
        valid for these many hours, after which it should be 
        refreshed. MTD Manager implementations do not need to
         discard MTD Files beyond this period.";
    }

    container malicious-descriptions {
      description 
        "This container has the descriptions of the malware and 
        attacks that can exploit or target the devices";

      uses malicious-list;
    }
  }

  grouping traffic-lists {
    description 
      "A grouping for acess lists of malicious traffic in the context 
      of malware or attacks.";

    container traffic-lists {
      description 
        "The access lists of the attack's malicious traffic 
        targeting or departing from the local IoT devices.";

      list traffic-list {
        key "name";

        description 
          "Each entry on this list refers to an malicious 
          traffic defined by an ACL that should present the
           overall network communication of the attack.";

        leaf name {
          type leafref{
            path "/acl:acls/acl:acl/acl:name";
          }

          description
            "The name of the ACL for this entry.";
        }

        leaf-list specific-devices {
          type inet:uri;

          description 
            "List of MUD URLs of specific devices 
            related with the vulnerability";
        }
      }
    }
  }

  grouping malicious-list {
    description 
      "A grouping for acess control lists of malicious traffic in the 
      context of malware or attacks.";

    list malicious-list {
      key "name";

      description 
        "The access lists of the malware's or attack's malicious 
        traffic targeting or departing from the local IoT devices,";

      leaf name {
        type string;

        description
          "The unique name of the described malicious activity for 
          each entry.";
      }

      leaf-list specific-devices {
        type inet:uri;

        description 
          "List of MUD URLs of specific devices 
          related with the vulnerability";
      }

      list critical-acl-sets{
        key "name";

        description
          "Each list entry represents a malicious activity's critical 
          set of risky ACL exposures, followed by the action to take 
          when a critical set be detected.";

        leaf name {
          type string;

          description
            "The critical ACL set name";
        }

        leaf-list critical-acl-set {
          type leafref{
            path "/acl:acls/acl:acl/acl:name";
          }

          description
            "A list to specify a set of ACLs that, when all listed 
            ACLs get classified as risky, represents a threat caused 
            by the malicious activity";
        }

        leaf action-to-take {
          type draft-inxu-mtd:action-to-take;
          mandatory true;
          description
            "A leaf to specify the action to be taken when 
            the respective set of critical ACLs turns into 
            a threat.";
        }
      }

      container to-device-attacks {
        description 
          "The set of attack traffic performed by the 
          infected IoT device";

        uses traffic-lists;
      }

      container from-device-attacks {
        description 
          "The set of attack traffic performed targeting 
          the infected IoT device";

        uses traffic-lists;
      }

      container to-device-not-attacks {
        description 
          "The set of attack traffic performed by the 
          infected IoT device";

        uses traffic-lists;
      }

      container from-device-not-attacks {
        description 
          "The set of attack traffic performed targeting 
          the infected IoT device";

        uses traffic-lists;
      }
    }
  }

  augment "/acl:acls/acl:acl/acl:aces/acl:ace/acl:matches" {
    description
      "adding abstraction to avoid the need of IP addresses.";
    container mtd {
      description
        "MTD-specific match.";
      leaf local-networks {
        type empty;
        description
          "IP addresses will match this node if they are
          considered local addresses. A local address may be
          a list of locally defined prefixes and masks
          that indicate a particular administrative scope.";
      }
    }
  }

  augment "/acl:acls/acl:acl/acl:aces/acl:ace" {
    description
      "Add the risk level information associated to the ACE";
    leaf risk {
      type uint8;
      default "1";
      description
        "Represents risk level of a device being exploited
        when exposes the device through traffic matching the 
        described ACE.";
    }

  }

  augment "/acl:acls/acl:acl" {
    description
      "Add an acceptable risk threshold and an alert risk threshold 
      to the ACL";
    leaf risk-threshold {
      type uint8;
      default "1";
      description
        "The acceptable risk threshold represents the minimum 
        risk value for the exposure be considered a risk.
        The actual risk of an ACL is calculated by the sum of 
        all the ACEs that matched on the INXU Module analysis";
    }

    leaf alert-threshold {
      type uint8;
      default "1";
      description
        "The acceptable alert threshold represents the minimum 
        risk value for the exposure trigger an alert.
        The actual risk of an ACL is calculated by the sum of 
        all the ACEs that matched on the INXU Module analysis";
    }
  }

  augment "/acl:acls/acl:acl/acl:aces/acl:ace/acl:matches"
    + "/acl:l4/acl:tcp/acl:tcp" {
    description
      "Add direction-initiated";
    leaf direction-initiated {
      type mud:direction;
      description
        "This node matches based on which direction a
        connection was initiated.";
       }
  }

  augment "/acl:acls/acl:acl/acl:aces/acl:ace/acl:matches" 
    + "/acl:l3/acl:ipv4/acl:ipv4" {
    description
      "Adding domain names to matching.";
    uses acldns:dns-matches;
  }
  
  augment "/acl:acls/acl:acl/acl:aces/acl:ace/acl:matches" 
    + "/acl:l3/acl:ipv6/acl:ipv6" {
    description
      "Adding domain names to matching.";
    uses acldns:dns-matches;
  }

  deviation "/acl:acls/acl:acl/acl:aces/acl:ace/acl:actions" {
    deviate not-supported;
    description
      "Field not used in this specification";
  }
}
<CODE ENDS>
        ]]></artwork>
      </section>
      <section numbered="true" toc="default">
        <name>MTD File Example</name>
        <t>
          This MTD file describes the traffic of an hipotetic variant of the Mirai botnet. In its attack model, this malware scans for other vulnerable devices in the same network, and its management services (Command and Control, Scan Report, and Loader) are placed in the network edge.
        </t>
        <artwork align="left" name="" type="" alt=""><![CDATA[
<CODE BEGINS>file "mirai-lan-variant.json"
  {
    "draft-inxu-mtd":"mtd",
    "mtd-url":"https://example.com/mirai-lan-variant.json",
    "last-update":"2022-05-15T18:17:00-03:00",
    "malicious-descriptions":{
      "malicious-list":[
        {
          "name":"Mirai-Example",
          "critical-acl-sets":[
            {
              "name":"mirai-prevent-spread",
              "critical-acl-set":
              [
                {"name":"mirai_infect_v4from"},
                {"name":"mirai_infect_v4to"},
                {"name":"mirai_scan_v4from"},
                {"name":"mirai_scan_v4to"}
              ],
              "action-to-take": "BLOCK_ATTACK"
            },
            {
              "name":"mirai-prevet-cnc",
              "critical-acl-set":
              [
                {"name":"mirai_cnc_v4from"},
                {"name":"mirai_cnc_v4to"}
              ],
              "action-to-take": "BLOCK_N_ATTACK"
            },
            {
              "name":"mirai-prevet-minimal",
              "critical-acl-set":
              [
                {"name":"mirai_cnc_v4from"},
                {"name":"mirai_cnc_v4to"},
                {"name":"mirai_infect_v4from"},
                {"name":"mirai_infect_v4to"}
              ],
              "action-to-take": "BLOCK_ALL"
            },
          ],
          "to-device-attacks": {
            "traffic-lists": {
              "traffic-list": [
                {"name":"mirai_infect_v4to"},
                {"name":"mirai_scan_v4to"}
              ]
            }
          },
          "from-device-attacks": {
            "traffic-lists": {
              "traffic-list": [
                {"name":"mirai_infect_v4from"},
                {"name":"mirai_scan_v4from"}
              ]
            }
          },
          "to-device-not-attacks": {
            "traffic-lists": {
              "traffic-list": [
                {"name":"mirai_cnc_v4to"}
              ]
            }
          },
          "from-device-not-attacks": {
            "traffic-lists": {
              "traffic-list": [
                {"name":"mirai_cnc_v4from"}
              ]
            }
          },
        }
      ]
    },
    "ietf-access-control-list:acls": {
      "acl": [
        {
          "name":"mirai_infect_v4to",
          "risk-threshold":11,
          "type": "ipv4-acl-type",
          "aces": {
            "ace": [
              {
                "name":"infect_23_to",
                "risk":10,
                "matches":{
                  "ipv4":{
                    "ietf-acldns:dst-dnsname":"urn:ietf:params:\
                      mud:gateway",
                    "protocol":6
                  },
                  "tcp":{
                    "destination-port":{
                      "operator":"eq",
                      "port":23
                    }
                  }
                }
              },
              {
                "name":"infect_2323_to",
                "risk":10,
                "matches":{
                  "ipv4":{
                    "ietf-acldns:dst-dnsname":"urn:ietf:params:\
                      mud:gateway",
                    "protocol":6
                  },
                  "tcp":{
                    "destination-port":{
                      "operator":"eq",
                      "port":2323
                    }
                  }
                }
              },
              {
                "name":"bin_download_to",
                "risk":1,
                "matches":{
                  "ipv4":{
                    "ietf-acldns:dst-dnsname":"urn:ietf:params:\
                      mud:gateway",
                    "protocol":6
                  },
                  "tcp":{
                    "source-port":{
                      "operator":"eq",
                      "port":80
                    },
                  }
                }
              }
            ]
          }
        },
        {
          "name":"mirai_scan_v4to",
          "risk-threshold":11,
          "type": "ipv4-acl-type",
          "aces": {
            "ace": [
              {
                "name":"scan_23_to",
                "risk":10,
                "matches":{
                  "ietf-mud:mud":{
                    "local-networks":[ null ]
                  },
                  "ipv4":{
                    "protocol":6
                  },
                  "tcp":{
                    "source-port":{
                      "operator":"eq",
                      "port":23
                    },
                  }
                }
              },
              {
                "name":"scan_2323_to",
                "risk":10,
                "matches":{
                  "ietf-mud:mud":{
                    "local-networks":[ null ]
                  },
                  "ipv4":{
                    "protocol":6
                  },
                  "tcp":{
                    "source-port":{
                      "operator":"eq",
                      "port":2323
                    },
                  }
                }
              },
              {
                "name":"scan_report_to",
                "risk":1,
                "matches":{
                  "ipv4":{
                    "ietf-acldns:dst-dnsname":"urn:ietf:params:\
                      mud:gateway",
                    "protocol":6
                  },
                  "tcp":{
                    "source-port":{
                      "operator":"eq",
                      "port":48101
                    },
                  }
                }
              }
            ]
          }
        },
        {
          "name":"mirai_infect_v4from",
          "risk-threshold":11,
          "type": "ipv4-acl-type",
          "aces": {
            "ace": [
              {
                "name":"infect_23_from",
                "risk":10,
                "matches":{
                  "ipv4":{
                    "ietf-acldns:dst-dnsname":"urn:ietf:params:\
                      mud:gateway",
                    "protocol":6
                  },
                  "tcp":{
                    "source-port":{
                      "operator":"eq",
                      "port":23
                    },
                  }
                }
              },
              {
                "name":"infect_2323_from",
                "risk":10,
                "matches":{
                  "ipv4":{
                    "ietf-acldns:dst-dnsname":"urn:ietf:params:\
                      mud:gateway",
                    "protocol":6
                  },
                  "tcp":{
                    "source-port":{
                      "operator":"eq",
                      "port":2323
                    },
                  }
                }
              },
              {
                "name":"bin_download_from",
                "risk":1,
                "matches":{
                  "ipv4":{
                    "ietf-acldns:dst-dnsname":"urn:ietf:params:\
                      mud:gateway",
                    "protocol":6
                  },
                  "tcp":{
                    "destination-port":{
                      "operator":"eq",
                      "port":80
                    }
                  }
                }
              }
            ]
          }
        },
        {
          "name":"mirai_scan_v4from",
          "risk-threshold":11,
          "type": "ipv4-acl-type",
          "aces": {
            "ace": [
              {
                "name":"scan_23_from",
                "risk":10,
                "matches":{
                  "ietf-mud:mud":{
                    "local-networks":[ null ]
                  },
                  "ipv4":{
                    "protocol":6
                  },
                  "tcp":{
                    "destination-port":{
                      "operator":"eq",
                      "port":23
                    }
                  }
                }
              },
              {
                "name":"scan_2323_from",
                "risk":10,
                "matches":{
                  "ietf-mud:mud":{
                    "local-networks":[ null ]
                  },
                  "ipv4":{
                    "protocol":6
                  },
                  "tcp":{
                    "destination-port":{
                      "operator":"eq",
                      "port":2323
                    }
                  }
                }
              },
              {
                "name":"scan_report_from",
                "risk":1,
                "matches":{
                  "ipv4":{
                    "ietf-acldns:dst-dnsname":"urn:ietf:params:\
                      mud:gateway",
                    "protocol":6
                  },
                  "tcp":{
                    "destination-port":{
                      "operator":"eq",
                      "port":48101
                    }
                  }
                }
              }
            ]
          }
        },
        {
          "name":"mirai_cnc_v4to",
          "type": "ipv4-acl-type",
          "aces": {
            "ace": [
              {
                "name":"cnc_socket_to",
                "risk":1,
                "matches":{
                  "ipv4":{
                    "ietf-acldns:dst-dnsname":"urn:ietf:params:\
                      mud:gateway",
                    "protocol":6
                  },
                  "tcp":{
                    "source-port":{
                      "operator":"eq",
                      "port":2030
                    },
                  }
                }
              }
            ]
          }
        },
        {
          "name":"mirai_cnc_v4from",
          "type": "ipv4-acl-type",
          "aces": {
            "ace": [
              {
                "name":"cnc_socket_from",
                "risk":1,
                "matches":{
                  "ipv4":{
                    "ietf-acldns:dst-dnsname":"urn:ietf:params:\
                      mud:gateway",
                    "protocol":6
                  },
                  "tcp":{
                    "destination-port":{
                      "operator":"eq",
                      "port":2030
                    }
                  }
                }
              }
            ]
          }
        }
      ]
    }
  }
<CODE ENDS>
        ]]></artwork>
      </section>
    </section>
    <section numbered="true" toc="default">
      <name>The Intra-Network eXposure analyzer Utility</name>
      <t>
        INXU was designed to have as main features: (i) enable quick responses to new vulnerabilities; (ii) allow mitigation of the damages of a new vulnerability, simultaneously in multiple distinct networks; and (iii) enable a decision-making process about security measures on the network edge, avoiding the disclosure of private information to third parties.
      </t>
      <t>
        To cover these requirements, INXU enables a security expert team — such as a SOC or an ISP Abuse Desk — to describe the traffic of ongoing malicious activities using the MTD data model (more details of the MTD data model are discussed in Section 3). With these descriptions, the security experts team can use the INXU to prevent multiple distinct networks when releasing new MTD Files for every new malicious activity discovered, in a process similar to the antivirus programs vaccines.
      </t>
      <section numbered="true" toc="default">
        <name>INXU Architecture and Components</name>
        <t>
          The ASCII diagram below shows the architecture of INXU. The proposed architecture contains 4 main components: MTD Server, MTD Manager, INXU Module, and MUD manager <xref target="RFC8520" format="default"/>.
        </t>
        <artwork align="left" name="" type="" alt=""><![CDATA[
...................................................
. End system network edge                        .
.  _____________                                 .
. |             |                                .
. | MUD manager | Communication                  .
. | [RFC 8520]  |--->graph>----+                 .
. |_____________|              |      ________   .
.                              +---->|        |  .
.  ___________                       |  INXU  |  .
. |           |                +---->|________|  .
. |    MTD    |                |                 .
. |  Manager  |---->MTD File>--+                 .
. |___________|                                  .
.    |  ^                                        .
......|..|.........................................
      |  |
      |  |               __________
      |  +--<MTD File<--|          |
      |      (https)    |   MTD    |
      +----->get URL>-->|  Server  |
                        |__________|
        ]]></artwork>
        <t>
          The MTD Server is responsible for storing and delivering the malicious traffic descriptions made by a security expert. This component was designed to enable trusted third-party specialists to share knowledge about well-known malicious activities affecting IoT and allow IoT networks to make use of this knowledge to protect themselves. The MTD Server is composed by a HTTPS server that hosts and delivers the MTD File for the clients. The MTD File is a file where the network traffic associated with malicious activities are described to INXU. This component also contains data for version control, authenticity, and validity time. The content of a MTD File is defined by a security expert in a JSON file, following the YANG data model described in the <xref target="mtd" format="default" />.
        </t>
        <t>
          The MTD Manager has the function of managing the MTD File on the system. It is responsible for requesting the file to the MTD Server, verifying authenticity, and requesting a new file when the current file validity expires. The default way to ensure MTD File authenticity is by HTTPS protocol, but the MTD Manager can also use the means described in the Section 3.1 of the <xref target="RFC2818" format="default"/>. At the end of the process, the MTD Manager forwards the MTD File to the INXU Module.
        </t>
        <t>
          The INXU (Intra-Network eXposure analyzer Utility) module is the main component of this proposal. It is responsible for verifying all the network communications trying to identify possible exposures to malicious traffic. To do this, the INXU Module compares the malicious traffic described in a MTD File with the network graph generated by MUD manager. The exposure analysis process is detailed in <xref target="inxu_alg" format="default"/>.
        </t>
      </section>
      <section numbered="true" toc="default">
        <name>Workflow</name>
        <t>
          The workflow adopted to INXU may vary, but it will mostly follow the process described below.
        </t>
        <ol>
          <li>MTD Manager fetches the MTD File.</li>
          <li>
            After confirming MTD File authenticity, the MTD Manager sends it for the INXU Module.
          </li>
          <li>
            The MUD manager sends the network communication graph -- including the devices’ MUD URLs -- to the INXU Module.
          </li>
          <li>
            INXU Module identifies potential vulnerability exposures into the network.
          </li>
          <li>
            INXU analyzes the detected vulnerabilities to evaluate if they represent an effective threat. After detecting threats, INXU may act as an Intrusion Prevention System and block the exposures, or serve as input source for other security systems, depending on the implementation.
          </li>
          <li>
            If the MUD manager detects any change in the network topology, or the MTD Manager gets new definitions from MTD Files, the process returns to step 4.
          </li>
        </ol>
      </section>
      <section numbered="true" toc="default">
        <name>Acquiring a MTD File</name>
        <t>
          The main method for acquiring a MTD File is by configuring the MTD URL into the MTD Manager. The MTD URL is a Universal Resource Locator (URL) <xref target="RFC3986" format="default"/> provided by the Security Experts team designated for protecting the network.
        </t>
        <t>
          MTD URLs MUST use the "https" scheme <xref target="RFC7230" format="default"/>.
        </t>
        <t>
          An alternative manner for acquiring a MTD File is by manually importing and its respective signature file into the MTD Manager. The mechanisms for doing so are not described in this document.
        </t>
      </section>
      <section numbered="true" toc="default">
        <name>Processing a MTD URL</name>
        <t>
          Disclaimer: The specification in this section is in our roadmap but still not done. Our initial intention is to use the same specification as <xref target="RFC8520" format="default"/> in Section 1.6. To simplify understanding, we copied the original MUD text, pasted it below, and replaced the MUD references with MTD.
        </t>
        <t>
          MTD Managers that are able to do so SHOULD retrieve MTD URLs and signature files as per <xref target="RFC7230" format="default"/>, using the GET method <xref target="RFC7231" format="default"/>. They MUST validate the certificate using the rules in <xref target="RFC2818" format="default"/>, Section 3.1.
        </t>
        <t>
          Requests for MTD URLs SHOULD include an "Accept" header field (<xref target="RFC7231" format="default"/>, Section 5.3.2) containing "application/mtd+json", an "Accept-Language" header field (<xref target="RFC7231" format="default"/>, Section 5.3.5), and a "User-Agent" header field (<xref target="RFC7231" format="default"/>, Section 5.5.3).
        </t>
        <t>
          MTD Managers SHOULD automatically process 3xx response status codes.
        </t>
        <t>
          If a MTD Manager is not able to fetch a MTD URL, other means MAY be used to import the MTD File and its associated signature file. So long as the signature of the file can be validated, the file can be used. In such environments, controllers SHOULD warn administrators when cache-validity expiry is approaching so that they may check for new files.
        </t>
      </section>
      <section anchor="inxu_alg" numbered="true" toc="default">
        <name>INXU Vulnerability Analysis Process</name>
        <t>
          The exposure analysis algorithm of the INXU Module uses malicious traffic descriptions from a MTD File to compare with the IoT traffic flows allowed by MUD -- provided by the network communication graph generated by MUD manager -- and tries to detect vulnerabilities on the network. In this context, INXU identifies one exposure when some graph edge matches with any entry of the MTD File.
        </t>
        <t>
          Based on the MUD files, each host expected to communicate with the IoT devices, or the IoT devices themselves, are represented by nodes on the network communication graph generated by MUD manager. The host network address represents the nodes, and in the case of IoT devices on the LAN, the MUD URL is associated with the node information. The graph edges represent TCP or UDP sockets, or ICMP communications, where a directed edge represents a communication path.
        </t>
        <section numbered="true" toc="default">
          <name>Exposure Identification</name>
          <t>
            For each IoT node in the MUD-based communication graph, the Exposure Identification process verifies if five information match between edge and ACEs: source and destination host addresses, communication protocol, and source and destination ports -- for transport protocols -- or ICMP message type and code. We only consider an exposure when all five information match.
          </t>
          <t>
            The ACEs considered here MUST be applicable for any device OR include the IoT device’s MUD URL in the specific-devices list.
          </t>
          <t>
            A match on source or destination host address happens when the addresses are equals OR when the ACE uses the local address abstraction and the node is local.
          </t>
          <t>
            Protocols match when the specified protocols (TCP, UDP, ICMP, or any) are equal both on ACE and edge OR when the ACE specifies any protocol.
          </t>
          <t>
            For the ICMP message type and code or for transport’s source and destination ports, a match happens when the specified values are equals OR when the ACE specifies any value.
          </t>
        </section>
        <section numbered="true" toc="default">
          <name>ACL Risk Assessment</name>
          <t>
            Each vulnerability exposure is associated with an ACE and is in the context of an ACL. Therefore, a set of vulnerability exposures of a device becomes a risk when the sum of their ACE risks is bigger than the ACL’s risk threshold. There is also a possibility of triggering an alert state when the ACL’s risk exceeds the alert threshold.
          </t>
          <t>
            The risk threshold SHOULD be equals or bigger than the alert threshold.
          </t>
        </section>
        <section numbered="true" toc="default">
          <name>Threat Analysis</name>
          <t>
            After assessing the risk of each ACL, the next step in the process is the threat analysis. This analysis iterates over the list of the critical ACL sets of a malicious activity.
          </t>
          <t>
            In this step, the INXU Module verifies if all the ACLs contained in a critical set are classified as risky for a device. If this condition becomes true, the INXU Module SHOULD take the action specified in the set’s action-to-take field. If a malicious activity threatens the device with more than one set of critical ACLs, the INXU Module MUST take an action based into a merge of all the threatening sets’ action-to-take.
          </t>
        </section>
      </section>
    </section>
    <section numbered="true" toc="default">
      <name>Further Considerations and Next Steps</name>
      <t>
        During the development of INXU, we found some important points that could further enhance the proposal in the near future. First of all, although INXU sticks to the Network and Transport layers, many recently reported DDoS attacks exploited the DNS platform to cause damage. This issue requires some treatment in this application layer protocol of the TCP/IP model. As it is a crucial application for the Internet's functioning as we know it today, it is impossible to block traffic over the protocol completely, but we believe that some level of filtering will not negatively impact the devices' usability nor the network's performance.
      </t>
      <t>
        Another interesting future direction is that although INXU allows identifying, classifying, and mitigating malicious activities on the other hand it does that without any intervention from the user. All the blocking processes do not allow the end-users intervention on the blocks and may lead them to not adopt INXU. An option to overcome this issue is by integrating Software Bill of Materials (SBOM) related information into the MTD data model and in the Threat Analysis process, and allowing end-users feedback on blocking decisions. This may reduce INXU’s impact on usability with low security loss and consequently improve its adoption.
      </t>
      <t>
        Also in this sense, we could use the MTD as a standard data model for attacks signatures involving IoT. It is a useful way to share how attacks can alter the network traffic to be used in controlled experiments and simulations. Also it can be seen also as a systematic way to share information on attacks -- in this sense network administrators, scientists and security analysts could have the same view over a given event in the network.
      </t>
      <t>
        Finally, also coming from the previous statement, INXU's output could be used as an input filter for IPS/IDS systems in order to prevent attacks and any other malicious event in the network. Since by using the MTD we could classify the traffic into appropriate or not. Furthermore INXU -- specially the MTD -- could be paired with an AI engine to learn about new network patterns and classify them as an attack or some new device in the network -- the system could write some new MTDs as it learns from the network. 
      </t>
    </section>

    <section anchor="Security" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>
        Since INXU uses MUD as a data source, the problems presented at the Security Considerations session of the <xref target="RFC8520" format="default"/> are still valid for this proposal, and some new ones arise.
      </t>
      <t>
        The first new risk is the possibility of INXU causing Denial of Service on their protected IoT devices depending on how the malicious activities are described in the MTD File. To prevent this issue, while describing a malicious activity, the Security Specialist SHOULD be as specific as possible by describing, for example, the specific devices that can be affected by the attack or malware and being assertive while defining ACE risks and ACL risk thresholds.
      </t>
      <t>
        As with MUD, the MTD Manager may receive a fake MTD File from a rogue MTD Server with a certificate issued by an accredited certification authority (CA). In this case, the same MUD mitigations apply: First, if the signer changes, this may be flagged as an exception by the MTD manager. Second, if the MTD file also changes, the MTD manager SHOULD seek administrator approval (it should do this in any case). In all circumstances, the MUD manager MUST maintain a cache of trusted CAs for this purpose.  When such a rogue is discovered, it SHOULD be removed.
      </t>
      <t>
        Finally, INXU is not effective against attacks that are occurring prior to a new MTD file arriving or ongoing at the moment of an update. The classification of the attack is not accurate since it does not know the rules. A countermeasure is to use an anomaly detection system to identify such attacks. INXU is not responsible for that part.
      </t>
      <t>Further security considerations might arise during this document’s evolution.</t>
    </section>
   <section anchor="IANA" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This memo includes no request to IANA.</t>
    </section>
  </middle>
  <!--  *****BACK MATTER ***** -->

 <back>

   <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
     <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <seriesInfo name="DOI" value="10.17487/RFC2119"/>
            <seriesInfo name="RFC" value="2119"/>
            <seriesInfo name="BCP" value="14"/>
            <author initials="S." surname="Bradner" fullname="S. Bradner">
              <organization/>
            </author>
            <date year="1997" month="March"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
        </reference>

        <reference anchor="RFC8520" target="https://rfc-editor.org/rfc/rfc8520.txt">
          <front>
            <title>Manufacturer Usage Description Specification</title>
            <author fullname="Eliot Lear" surname="Lear" />
            <author fullname="Ralph Droms" surname="Droms" />
            <author fullname="Dan Romascanu" surname="Romascanu" />
            <date month="March" year="2019" />
          </front>
        </reference>
        <reference anchor="RFC8174" target="https://rfc-editor.org/rfc/rfc8174.txt">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="Barry Leiba" surname="Leiba" />
            <date month="May" year="2017" />
          </front>
        </reference>
        <reference anchor="RFC8519" target="https://rfc-editor.org/rfc/rfc8519.txt">
          <front>
            <title>YANG Data Model for Network Access Control Lists (ACLs)</title>
            <author fullname="Mahesh Jethanandani" surname="Jethanandani" />
            <author fullname="Sonal Agarwal" surname="Agarwal" />
            <author fullname="Lisa Huang" surname="Huang" />
            <author fullname="Dana Blair" surname="Blair" />
            <date month="March" year="2019" />
          </front>
        </reference>
        <reference anchor="RFC7950" target="https://rfc-editor.org/rfc/rfc7950.txt">
          <front>
            <title>The YANG 1.1 Data Modeling Language</title>
            <author fullname="Martin Bjorklund" surname="Bjorklund" />
            <date month="August" year="2016" />
          </front>
        </reference>
        <reference anchor="RFC8340" target="https://rfc-editor.org/rfc/rfc8340.txt">
          <front>
            <title>YANG Tree Diagrams</title>
            <author fullname="Martin Bj&#246;rklund" surname="Bj&#246;rklund" />
            <author fullname="Lou Berger" surname="Berger" />
            <date month="March" year="2018" />
          </front>
        </reference>
        <reference anchor="RFC2818" target="https://rfc-editor.org/rfc/rfc2818.txt">
          <front>
            <title>HTTP Over TLS</title>
            <author fullname="Eric Rescorla" surname="Rescorla" />
            <date month="May" year="2000" />
          </front>
        </reference>
        <reference anchor="RFC3986" target="https://rfc-editor.org/rfc/rfc3986.txt">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <author fullname="Tim Berners-Lee" surname="Berners-Lee" />
            <author fullname="Roy T. Fielding" surname="Fielding" />
            <author fullname="Larry M Masinter" surname="Masinter" />
            <date month="January" year="2005" />
          </front>
        </reference>
        <reference anchor="RFC7230" target="https://rfc-editor.org/rfc/rfc7230.txt">
          <front>
            <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
            <author fullname="Roy T. Fielding" surname="Fielding" />
            <author fullname="Julian Reschke" surname="Reschke" />
            <date month="June" year="2014" />
          </front>
        </reference>
        <reference anchor="RFC7231" target="https://rfc-editor.org/rfc/rfc7231.txt">
          <front>
            <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
            <author fullname="Roy T. Fielding" surname="Fielding" />
            <author fullname="Julian Reschke" surname="Reschke" />
            <date month="June" year="2014" />
          </front>
        </reference>

      </references>
      <references>
        <name>Informative References</name>
        <reference anchor="Mozzaquatro2015" target="https://doi.org/10.1109/IWMN.2015.7322984">
          <front>
            <title>Towards a reference ontology for security in the Internet of Things</title>
            <author fullname="B A Mozzaquatro" surname="Mozzaquatro" />
            <author fullname="R Jardim-Goncalves" surname="Jardim-Goncalves" />
            <author fullname="C Agostinho" surname="Agostinho" />
            <date year="2015" />
          </front>
        </reference>

      </references>
    </references>
    <!--
    <section anchor="app-additional" numbered="true" toc="default">
      <name>Additional Stuff</name>
      <t>This becomes an Appendix.</t>
    </section>
  -->
 </back>
</rfc>