Secure Automation and Continuous Monitoring (SACM) Terminology
draft-ietf-sacm-terminology-09

The information below is for an old version of the document
Document Type Active Internet-Draft (sacm WG)
Last updated 2016-03-21
Replaces draft-dbh-sacm-terminology
Stream IETF
Intended RFC status (None)
Formats plain text 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                                           H. Birkholz
Internet-Draft                                            Fraunhofer SIT
Intended status: Informational                                     J. Lu
Expires: September 22, 2016                           Oracle Corporation
                                                           N. Cam-Winget
                                                           Cisco Systems
                                                          March 21, 2016

     Secure Automation and Continuous Monitoring (SACM) Terminology
                     draft-ietf-sacm-terminology-09

Abstract

   This memo documents terminology used in the documents produced by
   SACM (Security Automation and Continuous Monitoring).

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
   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 September 22, 2016.

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.

Birkholz, et al.       Expires September 22, 2016               [Page 1]
Internet-Draft              SACM Terminology                  March 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   2
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   6.  Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .  13
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  15
   8.  Informative References  . . . . . . . . . . . . . . . . . . .  17
   Appendix A.  The Attic  . . . . . . . . . . . . . . . . . . . . .  17
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   Our goal with this document is to improve our agreement on the
   terminology used in documents produced by the IETF Working Group for
   Security Automation and Continuous Monitoring.  Agreeing on
   terminology should help reach consensus on which problems we're
   trying to solve, and propose solutions and decide which ones to use.

2.  Terms and Definitions

   This section describes terms that have been defined by other RFC's
   and defines new ones.  The predefined terms will reference the RFC
   and where appropriate will be annotated with the specific context by
   which the term is used in SACM.

   Assertion:  Defined by the ITU in [X.1252] as "a statement made by an
      entity without accompanying evidence of its validity".  In the
      context of SACM, an assertion is a collection result that includes
      metadata about the data source (and optionally a timestamp
      indicating the point in time the assertion was created at).  The
      validity of an assertion cannot be verified.

   Assessment:  Defined in [RFC5209] as "the process of collecting
      posture for a set of capabilities on the endpoint (e.g., host-
      based firewall) such that the appropriate validators may evaluate
      the posture against compliance policy."

      Within SACM the use of the term is expanded to support other uses
      of collected posture (e.g. reporting, network enforcement,
      vulnerability detection, license management).  The phrase "set of
      capabilities on the endpoint" includes: hardware and software
      installed on the endpoint."

   Asset:  Defined in [RFC4949] as "a system resource that is (a)
      required to be protected by an information system's security

Birkholz, et al.       Expires September 22, 2016               [Page 2]
Internet-Draft              SACM Terminology                  March 2016

      policy, (b) intended to be protected by a countermeasure, or (c)
Show full document text