Terminology for Security Assessment
draft-ietf-sacm-terminology-00
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (sacm WG)
|
|
Last updated |
|
2013-10-14
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Security Automation and Continuous Monitoring WG D. Waltermire
Internet-Draft NIST
Intended status: Informational A. Montville
Expires: April 17, 2014 TW
D. Harrington
Effective Software
October 14, 2013
Terminology for Security Assessment
draft-ietf-sacm-terminology-00
Abstract
This memo documents terminology used in the documents produced by the
SACM WG (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 April 17, 2014.
Copyright Notice
Copyright (c) 2013 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.
Waltermire, et al. Expires April 17, 2014 [Page 1]
Internet-Draft Terminology for Security Assessment October 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 2
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
6. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. -00- draft . . . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
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.
This document is expected to be temorary work product, and will
probably be incorporated into the architecture or other document.
2. Terms and Definitions
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 this document 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 policy, (b)
intended to be protected by a countermeasure, or (c) required for
a system's mission.
Waltermire, et al. Expires April 17, 2014 [Page 2]
Internet-Draft Terminology for Security Assessment October 2013
attribute
Defined in [RFC5209] as "data element including any requisite
meta-data describing an observed, expected, or the operational
status of an endpoint feature (e.g., anti-virus software is
currently in use)."
endpoint
Defined in [RFC5209] as "any computing device that can be
Show full document text