jiebi/ids-paragraph-commentary-corpus huggingface dataset:
Draft: draft-ietf-sacm-terminology

Commentary: terms from the vulnerability assessment scenario 
 Hi Danny , I still want to highlight one last time that we will have 3 - 4 different kinds of capability in the terminology in -10 if we pull this in . I understand this to be a basis of discussion still :) I am not sure if that is the case , though ! Let me elaborate . We have in SACM used by the architecture : Capability : : The extent of an SACM component 's ability enabled by the functions it is composed of . Capabilities are propagated by a SACM component and can be discovered by or negotiated with other SACM components . For example , the capability of a SACM Provider may be to provide endpoint management data , or only a subset of that data . We have in i2nsf , referenced in the sacm terminology : We have the VA Terms : + Endpoint management capability : + : An enterprise IT capability managing endpoint identity , endpoint information , and associated metadata on an ongoing basis . + Vulnerability management capability : + : An enterprise IT capability managing endpoint vulnerabilities and associated metadata on an ongoing basis by ingesting vulnerability description information and vulnerability detection data , and performing a vulnerability assessment . " Managed " in i2nsf means " has interface on the management - plane " . I still do not understand what managing actually means in the context of an VA capability :) What potential functions are propagated as capabilities ? What is their input ? What is their output ? Is it possible that the two VA capabilities are actually tasks ?   , Henk TL;DR I will pull these terms in , but we will have to align these terms better . On 07/08/2016 01:56 PM ,   wrote :
An enterprise IT capability managing endpoint identity, endpoint
information, and associated metadata on an ongoing basis.
Information pertaining to the existence of a flaw or flaws in
software, hardware, and/or firmware, which could potentially have
an adverse impact on enterprise IT functionality and/or security.
Vulnerability description information should contain enough
information to support vulnerability detection.
A type of guidance extracted from vulnerability description
information that describes the specific mechanisms of
vulnerability detection that is used by an enterprise's
vulnerability management capability to determine if a
vulnerability is present on an endpoint.
An enterprise IT capability managing endpoint vulnerabilities and
associated metadata on an ongoing basis by ingesting vulnerability
description information and vulnerability detection data, and
performing a vulnerability assessment.
The process of determining whether a set of endpoints is
vulnerable according to the information contained in the
vulnerability description information.
Draft: draft-ietf-sacm-terminology

Commentary: Fixed a couple other typos .
The ongoing task of detecting previously unknown interaction of a
potential target endpoint in the SACM domain.  TE Discovery is not
directly targeted at a specfic target endpoint and therefore an
un-targeted task.  SACM Components conducting the discovery task
as a part of their function are typically distributed and located,
for example, on infrastructure components or collect from those
remotely via appropriate interfaces.  Examples of infrastructure
components that are of interest to the discovery task include
routers, switches, VM hosting or VM managing components, AAA
servers, or servers handling dynamic address distribution.
The ongoing task of detecting previously unknown interaction of a
potential target endpoint in the SACM domain.  TE Discovery is not
directly targeted at a specific target endpoint and therefore an
un-targeted task.  SACM Components conducting the discovery task
as a part of their function are typically distributed and located,
for example, on infrastructure components or collect from those
remotely via appropriate interfaces.  Examples of infrastructure
components that are of interest to the discovery task include
routers, switches, VM hosting or VM managing components, AAA
servers, or servers handling dynamic address distribution.
A bundle of expected or desired configurations and states
(typically a composition of endpoint attribute value pairs) that
can be associated with a target endpoint.  The corresponding task
by which the association with a target endpoint takes places is
the endpoint classification.  The task by which a endpoint profile
is created is the endpoint characterization.  A type or class of
target endpoints is defined within a target endpoint profile, e.g.
printer, smartphone, or an office PC.
A bundle of expected or desired configurations and states
(typically a composition of endpoint attribute value pairs) that
can be associated with a target endpoint.  The corresponding task
by which the association with a target endpoint takes places is
the endpoint classification.  The task by which an endpoint
profile is created is the endpoint characterization.  A type or
class of target endpoints is defined within a target endpoint
profile, e.g. printer, smartphone, or an office PC.