Prospective Architecture for SACM
draft-schaad-sacm-architecture-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
SACM                                                           J. Schaad
Internet-Draft                                            August Cellars
Intended status: Informational                             D. Waltermire
Expires: May 4, 2017      National Institute of Standards and Technology
                                                        October 31, 2016

                   Prospective Architecture for SACM
                   draft-schaad-sacm-architecture-00

Abstract

   This document describes the high level architecture for Security
   Automation and Continuous Monitoring (SACM).  The architecture
   identifies the components that provide for the collection, storage,
   dissemination, and evaluation of posture information.  This
   architecture also describes the interfaces and associated operations
   that define the interactions between these components.  This
   information will inform future engineering work around identifying
   existing standards for collecting, storing, disseminating, and
   evaluating endpoint posture information.  This architecture will also
   help in identifying standardization gaps that require new engineering
   effort.

   Security practitioners need to request, analyze, and aggregate
   posture information from disparate sources that use differing means
   to identify endpoints, hardware, software, and configurations.  This
   task is made harder by the large number of different protocols and
   formats needed to bring together all of this information into a
   single view.  This architecture provides a means to automatically
   gather posture data together for standardized dissemination to
   downstream components.  This allows security practitioners that
   leverage this architecture to focus on managing security problems,
   not data.

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 http://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

Schaad & Waltermire        Expires May 4, 2017                  [Page 1]
Internet-Draft      Prospective Architecture for SACM       October 2016

   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 4, 2017.

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  SACM Components . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Combining Roles . . . . . . . . . . . . . . . . . . . . .   7
     2.2.  SACM Collection . . . . . . . . . . . . . . . . . . . . .   8
       2.2.1.  Use of Existing Management Protocols  . . . . . . . .  10
       2.2.2.  The Need for Collection Choreography  . . . . . . . .  10
       2.2.3.  Collected Information Dissemination . . . . . . . . .  12
   3.  SACM Protocols  . . . . . . . . . . . . . . . . . . . . . . .  12
   4.  Information Model . . . . . . . . . . . . . . . . . . . . . .  14
   5.  Data Model  . . . . . . . . . . . . . . . . . . . . . . . . .  15
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   8.  Informational References  . . . . . . . . . . . . . . . . . .  15
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   This document represents some views of the authors but should not be
   considered to be the opinions of them either individually or
   collectively.  The document is designed both to clarify the thinking
   of the authors as well as to create some discussion on what the
   architecture looks like.  As such, it is entirely reasonable that
Show full document text