BCP72 - A Problem Statement
draft-mcfadden-smart-threat-changes-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized 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)
Independent Submission                                      M. McFadden
Internet Draft                                 internet policy advisors
Intended status: Informational                            March 9, 2020
Expires: September 9, 2020

                        BCP72 - A Problem Statement
                draft-mcfadden-smart-threat-changes-00.txt

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), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on September 9, 2020.

Copyright Notice

   Copyright (c) 2020 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.

Mark McFadden         Expires September 9, 2020                [Page 1]
Internet-Draft       BCP72 - A Problem Statement             March 2020

Abstract

   RFC3552/BCP72 describes an Internet Threat model that has been used
   in Internet protocol design. More than sixteen years have passed
   since RFC3552 was written and the structure and topology of the
   Internet has changed. With those changes comes a question: has the
   Internet Threat Model really changed? Or, is the model described in
   RFC3552 still largely accurate?  This draft attempts to describe an
   non-exhaustive list of changes in the current threat environment. It
   suggests that there are both qualitative and quantitative differences
   from the environment described in RFC3552 and is intended as input to
   the IAB program on the Internet threat model started in 2020.

Table of Contents

   1. Introduction...................................................2
   2. BCP72 Threat Model.............................................3
      2.1. BCP72 Passive Attacks.....................................3
      2.2. BCP72 Active Attacks......................................4
   3. Changes to the Attack Landscape................................4
      3.1. Quantifiable Changes......................................4
      3.2. Qualitative Changes.......................................5
      3.3. Data at Rest..............................................6
   4. Observations...................................................6
   5. Problem Statement..............................................7
   6. Security Considerations........................................8
   7. IANA Considerations............................................8
   8. References.....................................................8
      8.1. Normative References......................................8
      8.2. Informative References....................................8
   9. Acknowledgments................................................8

1. Introduction

   [RFC3552] describes an Internet threat model. According to that RFC
   the threat model "describes the capabilities that an attacker is
   assumed to be able to deploy against a resource. It should contain
   such information as the resources available to an attacker in terms
   of information, computing capability, and control of a system."

   In 2020, the IAB approved an IAB program on the Internet threat
   model. One of its goals was to explore how the world has changed in
   terms of threats experienced and how protocol endpoints are
   implemented and deployed.  During early discussions for that IAB
   program - called model-t - a natural question was raised: has the

McFadden              Expires September 9, 2020                [Page 2]
Internet-Draft       BCP72 - A Problem Statement             March 2020

   Internet Threat Model really changed?  Or, is the model described in
   RFC3552 still largely accurate?
Show full document text