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

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04

SACM Working Group                                          A. Montville
Internet-Draft                                                 B. Munyan
Intended status: Standards Track                                     CIS
Expires: May 1, 2020                                    October 29, 2019

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

Abstract

   This document defines an architecture enabling a cooperative Security
   Automation and Continuous Monitoring (SACM) ecosystem.  This work 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 May 1, 2020.

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
   publication of this document.  Please review these documents

Montville & Munyan         Expires May 1, 2020                  [Page 1]
Internet-Draft              SACM Architecture               October 2019

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Requirements notation . . . . . . . . . . . . . . . . . .   3
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   3
   3.  Architectural Overview  . . . . . . . . . . . . . . . . . . .   3
     3.1.  SACM Role-based Architecture  . . . . . . . . . . . . . .   4
     3.2.  Architectural Roles/Components  . . . . . . . . . . . . .   5
       3.2.1.  Orchestrator(s) . . . . . . . . . . . . . . . . . . .   5
       3.2.2.  Repositories/CMDBs  . . . . . . . . . . . . . . . . .   5
       3.2.3.  Integration Service . . . . . . . . . . . . . . . . .   5
     3.3.  Downstream Uses . . . . . . . . . . . . . . . . . . . . .   6
       3.3.1.  Reporting . . . . . . . . . . . . . . . . . . . . . .   6
       3.3.2.  Analytics . . . . . . . . . . . . . . . . . . . . . .   6
     3.4.  Sub-Architectures . . . . . . . . . . . . . . . . . . . .   7
       3.4.1.  Collection Sub-Architecture . . . . . . . . . . . . .   7
       3.4.2.  Evaluation Sub-Architecture . . . . . . . . . . . . .   9
   4.  Interactions  . . . . . . . . . . . . . . . . . . . . . . . .  11
   5.  Security Domain Workflows . . . . . . . . . . . . . . . . . .  12
     5.1.  IT Asset Management . . . . . . . . . . . . . . . . . . .  12
       5.1.1.  Components, Capabilities and Workflow(s)  . . . . . .  13
     5.2.  Vulnerability Management  . . . . . . . . . . . . . . . .  13
       5.2.1.  Components, Capabilities and Workflow(s)  . . . . . .  14
     5.3.  Configuration Management  . . . . . . . . . . . . . . . .  15
       5.3.1.  Components, Capabilities and Workflow(s)  . . . . . .  16
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  18
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  19
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  19
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  19
   Appendix A.  Mapping to RFC8248 . . . . . . . . . . . . . . . . .  21
   Appendix B.  Example Components . . . . . . . . . . . . . . . . .  24
     B.1.  Policy Services . . . . . . . . . . . . . . . . . . . . .  24
     B.2.  Software Inventory  . . . . . . . . . . . . . . . . . . .  25
     B.3.  Datastream Collection . . . . . . . . . . . . . . . . . .  26