One document matched: draft-ietf-sacm-terminology-07.xml

<?xml version="1.0" encoding="us-ascii"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.0.26 -->

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>

<?rfc toc="yes"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>

<rfc ipr="trust200902" docName="draft-ietf-sacm-terminology-07" category="info">

  <front>
    <title abbrev="SACM Terminology">Secure Automation and Continuous Monitoring (SACM) Terminology</title>

    <author initials="H." surname="Birkholz" fullname="Henk Birkholz">
      <organization abbrev="Fraunhofer SIT">Fraunhofer SIT</organization>
      <address>
        <postal>
          <street>Rheinstrasse 75</street>
          <city>Darmstadt</city>
          <code>64295</code>
          <country>Germany</country>
        </postal>
        <email>henk.birkholz@sit.fraunhofer.de</email>
      </address>
    </author>

    <date year="2015" month="July" day="06"/>

    <area>Security</area>
    <workgroup>SACM Working Group</workgroup>
    <keyword>Internet-Draft</keyword>

    <abstract>


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



    </abstract>


  </front>

  <middle>


<section anchor="introduction" title="Introduction">

<t>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.</t>

</section>
<section anchor="terms-and-definitions" title="Terms and Definitions">

<t>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.</t>

<t><list style="hanging">
  <t hangText='Assessment:'>
  Defined in <xref target="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.”</t>
  <t>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.”</t>
  <t hangText='Asset:'>
  Defined in <xref target="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.</t>
  <t hangText='Asset Characterization:'>
  Asset characterization is the process of defining attributes that describe properties of an identified asset.</t>
  <t hangText='Asset Management:'>
  The process by which assets are provisioned, updated, maintained and deprecated.</t>
  <t hangText='Attribute:'>
  Defined in <xref target="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).”</t>
  <t hangText='Authentication:'>
  Defined in <xref target="RFC4949"/> as “the process of verifying a claim that a system entity or system resource has a certain attribute value.”</t>
  <t hangText='Authorization:'>
  Defined in <xref target="RFC4949"/> as “an approval that is granted to a system entity to access a system resource.”</t>
  <t hangText='Broker:'>
  A standard SACM component providing and/or connecting services on the behalf of other SACM components via the control plane.  Within the SACM Architecture, for example, a broker may provide authorization services and find, upon request, SACM components providing requested services.</t>
  <t hangText='Building Block:'>
  For SACM, a building block is a unit of functionality that is used to compose SACM components. It contains functions and may apply to one or more use cases. A Building Block can have interfaces on the data plane, the control plane, or on the management plane.</t>
  <t hangText='Capability:'>
  The extent of an SACM component’s ability enabled by the building blocks it is composed of.  For example, a Posture Information Provider may only provide endpoint management data, and then only a subset of that data.</t>
  <t hangText='Collection Task:'>
  The task by which endpoint attributes and/or corresponding attribute values are collected.</t>
  <t hangText='Consumer:'>
  An architectural component receiving information from another architectrual component.</t>
  <t hangText='Data Confidentiality:'>
  Defined in <xref target="RFC4949"/> as “the property that data is not disclosed to system entities unless they have been authorized to know the data.”</t>
  <t hangText='Data Integrity:'>
  Defined in <xref target="RFC4949"/> as “the property that data has not been changed, destroyed, or lost in an unauthorized or accidental manner.”</t>
  <t hangText='Data Origin:'>
  One or more properties that enable a SACM component to identify an Endpoint that is claimed to be the original source of received data.</t>
  <t hangText='Data Provenance:'>
  A historical record of the origins and evolution of data that is influenced by inputs, entities, functions and processes.</t>
  <t hangText='Endpoint:'>
  Defined in <xref target="RFC5209"/> as “any computing device that can be connected to a network.  Such devices normally are associated with a particular link layer address before joining the network and potentially an IP address once on the network.  This includes: laptops, desktops, servers, cell phones, or any device that may have an IP address.”</t>
  <t>To further clarify the <xref target="RFC5209"/> definition, an endpoint is any physical or virtual device that may have a network address.  Note that, network infrastructure devices (e.g. switches, routers, firewalls), which fit the definition, are also considered to be endpoints within this document.</t>
  <t>Based on the previous definition of an asset, an endpoint is a type of asset.</t>
  <t hangText='Endpoint Attributes:'>
  [TODO] (Definition of content, structure, and relationship to Posture Attributes)</t>
  <t hangText='Evaluation Task:'>
  The task by which endpoint attributes are evaluated.</t>
  <t hangText='Evaluation Result:'>
  The resulting value from having evaluated a set of posture attributes.</t>
  <t hangText='Expected Endpoint State:'>
  The required state of an endpoint that is to be compared against.</t>
  <t hangText='Function:'>
  A behavioral aspect or capacity of a particular building block, which belies that building blocks’s purpose.  For example, a building block on the control plane can provide a brokering function to other SACM components. On the data plane, a function can act as a provider and/or as a consumer of information.</t>
  <t hangText='Information Model:'>
  An information model is an abstract representation of data, their properties, relationships between data and the operations that can be performed on the data.  While there is some overlap with a data model, <xref target="RFC3444"/> distinguishes an information model as being protocol and implementation neutral whereas a data model would provide such details.</t>
  <t hangText='Management Plane (TBD per list; was “Control Plane”):'>
  Architectural component providing common functions to all SACM participants, including authentication, authorization, capabilities mappings, and the like.</t>
  <t hangText='Posture:'>
  Defined in <xref target="RFC5209"/> as “configuration and/or status of hardware or software on an endpoint as it pertains to an organization’s security policy.”</t>
  <t>This term is used within the scope of SACM to represent the configuration and state information that is collected from an endpoint (e.g. software/hardware inventory, configuration settings, dynamically assigned addresses).  This information may constitute one to many Posture Attributes.</t>
  <t hangText='Posture Attributes:'>
  Defined in <xref target="RFC5209"/> as “attributes describing the configuration or status (posture) of a feature of the endpoint.  A Posture Attribute represents a single property of an observed state.  For example, a Posture Attribute might describe the version of the operating system installed on the system.”</t>
  <t>Within this document this term represents a specific assertion about endpoint configuration or state (e.g. configuration setting, installed software, hardware).  The phrase “features of the endpoint” refers to installed software or software components.</t>
  <t hangText='Provider:'>
  An architectural component providing information to another architectrual component.</t>
  <t hangText='Proxy:'>
  An architectural component providing functions, information, or services on behalf of another component, which is not directly participating in the architecture.</t>
  <t hangText='Repository:'>
  An architectural component intended to store information of a particular kind.  A single repository may provide the functions of more than one repository type (i.e. configuration baseline repository, assessment results repository, etc.)</t>
  <t hangText='SACM Role:'>
  A label representing a collection of building blocks (containing functions and composing SACM components) residing on a particular endpoint. If a particular endpoint does not contain any SACM components it takes on the role of a target endpoint unless indicated otherwise.</t>
  <t hangText='SACM Component:'>
  A composition of building blocks that contain control plane, data plane or management plane functions. SACM defines a set of standard components (e.g. a collector, a broker, or a data store). A SACM component MUST contain at least a basic set of control plane building blocks and MAY contain data plane and managment plane building blocks. A SACM component residing on an endpoint assigns one or more SACM roles to the corresponding endpoint. A SACM component “resides on” an endpoint and an endpoint “contains” a SACM component, correspondingly.</t>
  <t hangText='SACM Component Discovery:'>
  The function by which a SACM component (or subsets, such as SACM roles or other functions) can be discovered.</t>
  <t hangText='Security Automation:'>
  The process of which security alerts can be automated through the use of different tools to monitor, evaluate and analyze endpoint and network traffic for the purposes of detecting misconfigurations, misbehaviors or threats.</t>
  <t hangText='Supplicant:'>
  The entity seeking to be authenticated by the Management Plane for the purpose of participating in the SACM architecture.</t>
  <t hangText='System Resource:'>
  Defined in <xref target="RFC4949"/> as “data contained in an information system; or a service provided by a system; or a system capacity, such as processing power or communication bandwidth; or an item of system equipment (i.e., hardware, firmware, software, or documentation); or a facility that houses system operations and equipment.</t>
  <t hangText='Target Endpoint:'>
  A target endpoint is a SACM Role. An endpoint that takes on the target endpoint role either contains no SACM component or contains an internal SACM component. A target endpoint is an “endpoint under assessment” (even if it is not actively under assessment at all times). If an endpoint takes on both the role of target endpoint and <spanx style="emph">Not A Target Endpoint</spanx> [TBD] it is not a Target Endpoint.</t>
  <t>A target endpoint is similar to a device that is a Target of Evaluation (TOE) as defined in Common Criteria.</t>
  <t hangText='Target Endpoint Discovery:'>
  The function by which target endpoints can be discovered.</t>
</list></t>

</section>
<section anchor="iana-considerations" title="IANA Considerations">

<t>This memo includes no request to IANA.</t>

</section>
<section anchor="security-considerations" title="Security Considerations">

<t>This memo documents terminology for security automation.  While it is about security, it does not affect security.</t>

</section>
<section anchor="acknowledgements" title="Acknowledgements">

</section>
<section anchor="change-log" title="Change Log">

<t>Changes from version 00 to version 01:</t>

<t><list style="symbols">
  <t>Added simple list of terms extracted from UC draft -05.  It is expected that comments will be received on this list of terms as to whether they should be kept in this document.  Those that are kept will be appropriately defined or cited.</t>
</list></t>

<t>Changes from version 01 to version 02:</t>

<t><list style="symbols">
  <t>Added Vulnerability, Vulnerability Management, xposure, Misconfiguration, and Software flaw.</t>
</list></t>

<t>Changes from version 02 to version 03:</t>

<t><list style="symbols">
  <t>Removed Section 2.1.  Cleaned up some editing nits; broke terms into 2 sections (predefined and newly defined terms).  Added some of the relevant terms per the proposed list discussed in the IETF 89 meeting.</t>
</list></t>

<t>Changes from version 03 to version 04:</t>

<t><list style="symbols">
  <t>TODO</t>
</list></t>

<t>Changes from version 04 to version 05:</t>

<t><list style="symbols">
  <t>TODO</t>
</list></t>

<t>Changes from version 05 to version 06:</t>

<t><list style="symbols">
  <t>Updated author information.</t>
  <t>Combined “Pre-defined Terms” with “New Terms and Definitions”.</t>
  <t>Removed “Requirements language”.</t>
  <t>Removed unused reference to use case draft; resulted in removal of normative references.</t>
  <t>Removed introductory text from Section 1 indicating that this document is intended to be temporary.</t>
  <t>Added placeholders for missing change log entries.</t>
</list></t>

<t>Changes from version 06 to version 07:</t>

<t><list style="symbols">
  <t>Added Contributors section.</t>
  <t>Updated author list.</t>
  <t>Changed title from “Terminology for Security Assessment” to “Secure Automation and Continuous Monitoring (SACM) Terminology”.</t>
  <t>Changed abbrev from “SACM-Terms” to “SACM Terminology”.</t>
  <t>Added appendix The Attic to stash terms for future updates.</t>
  <t>Added Authentication, Authorization, Data Confidentiality, Data Integrity, Data Origin, Data Provenance, SACM Component, SACM Component Discovery, Target Endpoint Discovery.</t>
  <t>Major updates to Building Block, Function, SACM Role, Target Endpoint.</t>
  <t>Minor updates to Broker, Capability, Collection Task, Evaluation Task, Posture.</t>
  <t>Relabled Role to SACM Role, Endpoint Target to Target Endpoint, Endpoint Discovery to Endpoint Identification.</t>
  <t>Moved Asset Targeting, Client, Endpoint Identification to The Attic.</t>
  <t>Endpoint Attributes added as a TODO.</t>
  <t>Changed the structure of the Change Log.</t>
</list></t>

</section>
<section anchor="contributors" title="Contributors">

<figure><artwork><![CDATA[
David Waltermire
National Institute of Standards and Technology
100 Bureau Drive
Gaithersburg, Maryland  20877
USA

Email: david.waltermire@nist.gov


Adam W. Montville
Center for Internet Security
31 Tech Valley Drive
East Greenbush, New York  12061
USA

Email: adam.w.montville@gmail.com


David Harrington
Effective Software
50 Harding Rd
Portsmouth, NH  03801
USA

Email: ietfdbh@comcast.net


Nancy Cam-Winget
Cisco Systems
3550 Cisco Way
San Jose, CA  95134
US
Jarrett Lu
Oracle Corporation
4180 Network Circle
Santa Clara, California  95054

Email: jarrett.lu@oracle.com

Jarrett Lu
Oracle Corporation
4180 Network Circle
Santa Clara, California  95054

Email: jarrett.lu@oracle.com


Brian Ford
Lancope
3650 Brookside Parkway, Suite 500
Alpharetta, Georgia  30022

Email: bford@lancope.com


Merike Kaeo
Double Shot Security
3518 Fremont Avenue North, Suite 363
Seattle, Washington  98103

Email: merike@doubleshotsecurity.com
]]></artwork></figure>

</section>


  </middle>

  <back>


    <references title='Informative References'>





<reference anchor='RFC3444'>

<front>
<title>On the Difference between Information Models and Data Models</title>
<author initials='A.' surname='Pras' fullname='A. Pras'>
<organization /></author>
<author initials='J.' surname='Schoenwaelder' fullname='J. Schoenwaelder'>
<organization /></author>
<date year='2003' month='January' />
<abstract>
<t>There has been ongoing confusion about the differences between Information Models and Data Models for defining managed objects in network management.  This document explains the differences between these terms by analyzing how existing network management model specifications (from the IETF and other bodies such as the International Telecommunication Union (ITU) or the Distributed Management Task Force (DMTF)) fit into the universe of Information Models and Data Models.  This memo documents the main results of the 8th workshop of the Network Management Research Group (NMRG) of the Internet Research Task Force (IRTF) hosted by the University of Texas at Austin.  This memo provides information for the Internet community.</t></abstract></front>

<seriesInfo name='RFC' value='3444' />
<format type='TXT' octets='18596' target='http://www.rfc-editor.org/rfc/rfc3444.txt' />
</reference>



<reference anchor='RFC4949'>

<front>
<title>Internet Security Glossary, Version 2</title>
<author initials='R.' surname='Shirey' fullname='R. Shirey'>
<organization /></author>
<date year='2007' month='August' />
<abstract>
<t>This Glossary provides definitions, abbreviations, and explanations of terminology for information system security.  The 334 pages of entries offer recommendations to improve the comprehensibility of written material that is generated in the Internet Standards Process (RFC 2026).  The recommendations follow the principles that such writing should (a) use the same term or definition whenever the same concept is mentioned; (b) use terms in their plainest, dictionary sense; (c) use terms that are already well-established in open publications; and (d) avoid terms that either favor a particular vendor or favor a particular technology or mechanism over other, competing techniques that already exist or could be developed.  This memo provides information for the Internet community.</t></abstract></front>

<seriesInfo name='RFC' value='4949' />
<format type='TXT' octets='867626' target='http://www.rfc-editor.org/rfc/rfc4949.txt' />
</reference>



<reference anchor='RFC5209'>

<front>
<title>Network Endpoint Assessment (NEA): Overview and Requirements</title>
<author initials='P.' surname='Sangster' fullname='P. Sangster'>
<organization /></author>
<author initials='H.' surname='Khosravi' fullname='H. Khosravi'>
<organization /></author>
<author initials='M.' surname='Mani' fullname='M. Mani'>
<organization /></author>
<author initials='K.' surname='Narayan' fullname='K. Narayan'>
<organization /></author>
<author initials='J.' surname='Tardo' fullname='J. Tardo'>
<organization /></author>
<date year='2008' month='June' />
<abstract>
<t>This document defines the problem statement, scope, and protocol requirements between the components of the NEA (Network Endpoint Assessment) reference model.  NEA provides owners of networks (e.g., an enterprise offering remote access) a mechanism to evaluate the posture of a system.  This may take place during the request for network access and/or subsequently at any time while connected to the network.  The learned posture information can then be applied to a variety of compliance-oriented decisions.  The posture information is frequently useful for detecting systems that are lacking or have out-of-date security protection mechanisms such as: anti-virus and host-based firewall software.  In order to provide context for the requirements, a reference model and terminology are introduced.  This memo provides information for the Internet community.</t></abstract></front>

<seriesInfo name='RFC' value='5209' />
<format type='TXT' octets='132227' target='http://www.rfc-editor.org/rfc/rfc5209.txt' />
</reference>




    </references>


<section anchor="the-attic" title="The Attic">

<t>The following terms are stashed for now and will be updated later:</t>

<t><list style="hanging">
  <t hangText='Asset Targeting:'>
  Asset targeting is the use of asset identification and categorization information to drive human-directed, automated decision making for data collection and analysis in support of endpoint posture assessment.</t>
  <t hangText='Client:'>
  An architectural component receiving services from another architectural component.</t>
  <t hangText='Endpoint Identification (TBD per list; was “Endpoint Discovery”):'>
  The process by which an endpoint can be identified.</t>
</list></t>

</section>


  </back>
</rfc>