Security Automation and Continuous Monitoring (SACM) Architecture
draft-ietf-sacm-arch-01

Document Type Active Internet-Draft (sacm WG)
Last updated 2019-02-22
Replaces draft-mandm-sacm-architecture
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
SACM Working Group                                          A. Montville
Internet-Draft                                                 B. Munyan
Intended status: Standards Track                                     CIS
Expires: August 26, 2019                               February 22, 2019

   Security Automation and Continuous Monitoring (SACM) Architecture
                        draft-ietf-sacm-arch-01

Abstract

   This memo defines a Security Automation and Continuous Monitoring
   (SACM) architecture.  This work is built upon
   [I-D.ietf-mile-xmpp-grid], and is predicated upon information gleaned
   from SACM Use Cases and Requirements ([RFC7632] and [RFC8248]
   respectively), and terminology as found in
   [I-D.ietf-sacm-terminology].

   WORKING GROUP: The source for this draft is maintained in GitHub.
   Suggested changes should be submitted as pull requests at
   https://github.com/sacmwg/ietf-mandm-sacm-arch/.  Instructions are on
   that page as well.

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 https://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 August 26, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://trustee.ietf.org/license-info) in effect on the date of

Montville & Munyan       Expires August 26, 2019                [Page 1]
Internet-Draft              SACM Architecture              February 2019

   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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Open Questions  . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements notation . . . . . . . . . . . . . . . . . .   3
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   4
   3.  Architectural Overview  . . . . . . . . . . . . . . . . . . .   4
     3.1.  SACM Roles  . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Exploring An XMPP-based Solution  . . . . . . . . . . . .   5
     3.3.  Example Architecture using XMPP-Grid and Endpoint Posture
           Collection Protocol . . . . . . . . . . . . . . . . . . .   8
   4.  Components, Capabilities, Interfaces, and Workflows . . . . .  10
     4.1.  Components  . . . . . . . . . . . . . . . . . . . . . . .  10
     4.2.  Capabilities  . . . . . . . . . . . . . . . . . . . . . .  11
     4.3.  Interfaces  . . . . . . . . . . . . . . . . . . . . . . .  11
     4.4.  Workflows . . . . . . . . . . . . . . . . . . . . . . . .  12
       4.4.1.  IT Asset Management . . . . . . . . . . . . . . . . .  12
       4.4.2.  Vulnerability Management  . . . . . . . . . . . . . .  12
       4.4.3.  Configuration Management  . . . . . . . . . . . . . .  14
   5.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  15
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  16
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Appendix A.  Mapping to RFC8248 . . . . . . . . . . . . . . . . .  18
   Appendix B.  Example Components . . . . . . . . . . . . . . . . .  21
     B.1.  Policy Services . . . . . . . . . . . . . . . . . . . . .  21
     B.2.  Software Inventory  . . . . . . . . . . . . . . . . . . .  22
     B.3.  Datastream Collection . . . . . . . . . . . . . . . . . .  23
     B.4.  Network Configuration Collection  . . . . . . . . . . . .  23
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  24

1.  Introduction

   The purpose of this draft is to define an architectural solution for
   a SACM Domain.  This draft also defines an implementation of the
   architecutre, built upon [I-D.ietf-mile-xmpp-grid] and
   [I-D.ietf-sacm-ecp].  These approaches complement each other to more
Show full document text