Security Automation and Continuous Monitoring (SACM) Terminology
draft-ietf-sacm-terminology-16
SACM Working Group H. Birkholz
Internet-Draft Fraunhofer SIT
Intended status: Informational J. Lu
Expires: June 17, 2019 Oracle Corporation
J. Strassner
Huawei Technologies
N. Cam-Winget
Cisco Systems
A. Montville
CIS
December 14, 2018
Security Automation and Continuous Monitoring (SACM) Terminology
draft-ietf-sacm-terminology-16
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 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 June 17, 2019.
Copyright Notice
Copyright (c) 2018 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
carefully, as they describe your rights and restrictions with respect
Birkholz, et al. Expires June 17, 2019 [Page 1]
Internet-Draft SACM Terminology December 2018
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. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 2
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
4. Security Considerations . . . . . . . . . . . . . . . . . . . 21
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22
6. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 22
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 26
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 27
8.1. Normative References . . . . . . . . . . . . . . . . . . 28
8.2. Informative References . . . . . . . . . . . . . . . . . 28
Appendix A. The Attic . . . . . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
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. Note that explanatory or
informational augmentation to definitions are segregated from the
definitions themselves. The definition for the term immediately
follows the term on the same line, whereas expositional text is
contained in subsequent paragraphs immediately following the
definition.
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 the output of a SACM
Component in the form of a SACM Statement (including metadata
about the data source and data origin, e.g. timestamps). While
the validity of an assertion about Content and Content Metadata
cannot be verified without, for example, Integrity Proofing of the
Birkholz, et al. Expires June 17, 2019 [Page 2]
Show full document text