idnits 2.17.1 draft-ietf-sacm-terminology-15.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 13, 2018) is 2137 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'TBD' is mentioned on line 954, but not defined == Unused Reference: 'I-D.ietf-netmod-entity' is defined on line 1278, but no explicit reference was found in the text == Outdated reference: A later version (-08) exists of draft-ietf-i2nsf-terminology-05 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SACM Working Group H. Birkholz 3 Internet-Draft Fraunhofer SIT 4 Intended status: Informational J. Lu 5 Expires: December 15, 2018 Oracle Corporation 6 J. Strassner 7 Huawei Technologies 8 N. Cam-Winget 9 Cisco Systems 10 A. Montville 11 CIS 12 June 13, 2018 14 Security Automation and Continuous Monitoring (SACM) Terminology 15 draft-ietf-sacm-terminology-15 17 Abstract 19 This memo documents terminology used in the documents produced by 20 SACM (Security Automation and Continuous Monitoring). 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on December 15, 2018. 39 Copyright Notice 41 Copyright (c) 2018 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (https://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 2 58 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 59 4. Security Considerations . . . . . . . . . . . . . . . . . . . 22 60 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 61 6. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 22 62 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 26 63 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 64 8.1. Normative References . . . . . . . . . . . . . . . . . . 28 65 8.2. Informative References . . . . . . . . . . . . . . . . . 28 66 Appendix A. The Attic . . . . . . . . . . . . . . . . . . . . . 29 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 69 1. Introduction 71 Our goal with this document is to improve our agreement on the 72 terminology used in documents produced by the IETF Working Group for 73 Security Automation and Continuous Monitoring. Agreeing on 74 terminology should help reach consensus on which problems we're 75 trying to solve, and propose solutions and decide which ones to use. 77 2. Terms and Definitions 79 This section describes terms that have been defined by other RFC's 80 and defines new ones. The predefined terms will reference the RFC 81 and where appropriate will be annotated with the specific context by 82 which the term is used in SACM. Note that explanatory or 83 informational augmentation to definitions are segregated from the 84 definitions themselves. The definition for the term immediately 85 follows the term on the same line, whereas expositional text is 86 contained in subsequent paragraphs immediately following the 87 definition. 89 Assertion: Defined by the ITU in [X.1252] as "a statement made by an 90 entity without accompanying evidence of its validity". 92 In the context of SACM, an assertion is the output of a SACM 93 Component in the form of a SACM Statement (including metadata 94 about the data source and data origin, e.g. timestamps). While 95 the validity of an assertion about Content and Content Metadata 96 cannot be verified without, for example, Integrity Proofing of the 97 Data Source, an assertion (and therefore a SACM statement, 98 respectively) of the validity of Statement Metadata can by enabled 99 by including corresponding Integrity Evidence created by the Data 100 Origin. 102 Assessment: Defined in [RFC5209] as "the process of collecting 103 posture for a set of capabilities on the endpoint (e.g., host- 104 based firewall) such that the appropriate validators may evaluate 105 the posture against compliance policy." 107 Asset: Is a system resource, as defined in [RFC4949], that may be 108 composed of other assets. 110 Examples of Assets include: Endpoints, Software, Guidance, or 111 X.509 public key certificates. An asset is not necessarily owned 112 by an organization. 114 Asset Management: The IT process by which assets are provisioned, 115 updated, maintained and deprecated. 117 Attribute: Is a data element, as defined in [RFC5209], that is 118 atomic. 120 In the context of SACM, attributes are "atomic" information 121 elements and an equivalent to attribute-value-pairs. Attributes 122 can be components of Subjects. 124 Broken remnant of a term again, but this time left here to show how 125 much the last submit of -14 broke the document (this is actually not 126 a term definition, apparently, but if you are curious this was 127 "Authorization", became a second paragraph of expositional text to 128 the definition of Attribute and now became the universal disclaimer 129 of "please alter the structure of the document with care") - until 130 removal by a less annoyed editor: 131 Defined in [RFC4949] as "an approval that is granted to a system 132 entity to access a system resource." 134 Capability: A set of features that are available from a SACM 135 Component. 137 See also "capability" in [I-D.ietf-i2nsf-terminology]. 139 In the context of SACM, the extent of a SACM component's ability 140 is enabled by the functions it is composed of. Capabilities are 141 registered at a SACM broker (potentially also at a proxy or a 142 repository component if it includes broker functions) by a SACM 143 component via the SACM component registration task and can be 144 discovered by or negotiated with other SACM components via the 145 corresponding tasks. For example, the capability of a SACM 146 provider may be to provide target endpoint records (declarative 147 guidance about well-known or potential target endpoints), or only 148 a subset of that data. 150 A capability's description is in itself imperative guidance on 151 what functions are exposed to other SACM components in a SACM 152 domain and how to use them in workflows. 154 The SACM Vulnerability Assessment Scenario 155 [I-D.ietf-sacm-vuln-scenario] defines the terms Endpoint 156 Management Capabilities, Vulnerability Management Capabilities, 157 and Vulnerability Assessment Capabilities, which illustrate 158 specific sets of SACM capabilities on an enterprise IT 159 department's point of view and therefore compose sets of 160 declarative guidance. 162 Collection Result: Is a composition of one or more content elements 163 carrying information about a target endpoint, that is produced by 164 a collector when conducting a collection task. 166 Collection Task: A targeted task that collects attributes and/or 167 corresponding attribute values from target endpoint. 169 There are four types of frequency collection tasks can be 170 conducted with: 172 ad-hoc, e.g. triggered by a unsolicited query 174 conditional, e.g. triggered in accordance with policies included 175 in the compositions of workflows 177 scheduled, e.g. in regular intervals, such as every minute or 178 weekly 180 continuously, e.g. a network behavior observation 182 There are three types of collection methods, each requiring an 183 appropriate set of functions to be included in the SACM component 184 conducting the collection task: 186 Self-Reporting: A SACM component located on the target endpoint 187 itself conducts the collection task. 189 Remote-Acquisition: A SACM component located on an Endpoint 190 different from the target endpoint conducts the collection task 191 via interfaces available on the target endpoint, e.g. SNMP/ 192 NETCONF or WMI. 194 Behavior-Observation: A SACM component located on an Endpoint 195 different from the target endpoint observes network traffic 196 related to the target endpoint and conducts the collection task 197 via interpretation of that network traffic. 199 Collector: A piece of software that acquires information about one 200 or more target endpoints by conducting collection tasks. 202 A collector can be distributed across multiple endpoints, e.g. 203 across a target endpoint and a SACM component. The separate parts 204 of the collector can communicate with a specialized protocol, such 205 as PA-TNC [RFC5792]. At least one part of a distributed collector 206 has to take on the role of a provider of information by providing 207 SACM interfaces to propagate capabilities and to provide SACM 208 content in the form of collection results. 210 Configuration: A non-volatile subset of the endpoint attributes of a 211 endpoint that is intended to be unaffected by a normal reboot- 212 cycle. 214 Configuration is a type of imperative guidance that is stored in 215 files (files dedicated to contain configuration and/ or files that 216 are software components), directly on block devices, or on 217 specific hardware components that can be accessed via 218 corresponding software components. Modification of configuration 219 can be conducted manually or automatically via management (plane) 220 interfaces that support management protocols, such as SNMP or WMI. 221 A change of configuration can occur during both run-time and down- 222 time of an endpoint. It is common practice to scheduled a change 223 of configuration during or directly after the completion of a 224 boot-cycle via corresponding software components located on the 225 target endpoint itself. 227 Examples: The static association of an IP address and a MAC 228 address in a DHCP server configuration, a directory-path that 229 identifies a log-file directory, a registry entry. 231 Configuration Drift: The disposition of endpoint characteristics to 232 change over time. 234 Configuration drift exists for both hardware components and 235 software components. Typically, the frequency and scale of 236 configuration drift of software components is significantly higher 237 than the configuration drift of hardware components. 239 Consumer: A SACM Role that requires a SACM Component to include SACM 240 Functions enabling it to receive information from other SACM 241 Components. 243 Content Element: Content elements constitute the payload data (SACM 244 content) transferred via statement Subjects emitted by providers 245 of information. Every content element Subject includes a specific 246 content Subject and a corresponding content metadata Subject. 248 Content Metadata: Data about content Subjects. Every content- 249 element includes a content metadata Subject. The Subject can 250 include any information element that can annotate the content 251 transferred. Examples include time stamps or data provenance 252 Subjects. 254 Control Plane: An architectural component that provides common 255 control functions to all SACM components. 257 Typically used as a term in the context of routing, e.g. 258 [RFC6192]. SACM components may include authentication, 259 authorization, (capability) discovery or negotiation, registration 260 and subscription. The control plane orchestrates the flow on the 261 data plane according to imperative guidance (i.e. configuration) 262 received via the management plane. SACM components with 263 interfaces to the control plane have knowledge of the capabilities 264 of other SACM components within a SACM domain. 266 Controller: A controller is a SACM Role that is assigned to a SACM 267 component containing control plane functions managing and 268 facilitating information sharing or execute on security functions. 270 There are three types of SACM controllers: Broker, Proxy, and 271 Repository. Depending on its type, a controller can also contain 272 functions that have interfaces on the data plane. 274 Data Confidentiality: Defined in [RFC4949] as "the property that 275 data is not disclosed to system entities unless they have been 276 authorized to know the data." 278 Data In Motion: Data that is being transported via a network; also 279 referred to as "Data in Transit" or "Data in Flight". 281 Data in motion requires a data model to transfer the data using a 282 specific encoding. Typically, data in motion is serialized 283 (marshalling) into a transport encoding by a provider of 284 information and deserialized (unmarshalling) by a consumer of 285 information. The termination points of provider of information 286 and consumer of information data is transferred between are 287 interfaces. In regard to data in motion, the interpretation of 288 the roles consumer of information and provider of information 289 depends on the corresponding OSI layer (e.g. on layer2: between 290 interfaces connected to a broadcast domain, on layer4: between 291 interfaces that maintain a TCP connection). In the context of 292 SACM, consumer of information and provider of information are SACM 293 components. 295 Data At Rest: Data that is stored. 297 Data at rest requires a data model to encode the data to be 298 stored. In the context of SACM, data at rest located on a SACM 299 component can be provided to other SACM components via 300 discoverable capabilities. 302 Data Integrity: Defined in [RFC4949] as "the property that data has 303 not been changed, destroyed, or lost in an unauthorized or 304 accidental manner." 306 Data Origin: The SACM Component that initially acquired or produced 307 data about an endpoint. 309 Data Origin enables a SACM component to identify the SACM 310 component that initially acquired or produced data about a 311 (target) endpoint (e.g. via collection from a data source) and 312 made it available to a SACM domain via a SACM statement. Data 313 Origin can be expressed by an endpoint label information element 314 (e.g. to be used as metadata in statement). 316 Data Plane: Is an architectural component providing operational 317 functions enabling information exchange that is not command and 318 control or management related. 320 Typically used as a term in the context of routing (and used as a 321 synonym for forwarding plane, e.g. [RFC6192]). In the context of 322 SACM, the data plane is an architectural component providing 323 operational functions to enable a SACM component to provide and 324 consume SACM statements and therefore SACM content, which composes 325 the actual SACM content. The data plane in a SACM domain is used 326 to conduct distributed SACM tasks by transporting SACM content via 327 specific transport encodings and corresponding operations defined 328 by SACM data models. 330 Data Provenance: An historical record of the sources, origins and 331 evolution, as it pertains to data, that is influenced by inputs, 332 entities, functions and processes. 334 Additional Information - In the context of SACM, data provenance 335 is expressed as metadata that identifies SACM statements and 336 corresponding content elements a new statement is created from. 337 In a downstream process, this references can cascade, creating a 338 data provenance tree that enables SACM components to trace back 339 the original data sources involved in the creation of SACM 340 statements and take into account their characteristics and 341 trustworthiness. 343 Data Source: Is an endpoint from which a particular set of 344 attributes and/or attribute values have been collected. 346 Data Source enables a SACM component to identify - and potentially 347 characterize - a (target) endpoint that is claimed to be the 348 original source of endpoint attributes in a SACM statement. Data 349 Source can be expressed as metadata by an endpoint label 350 information element or a corresponding subject of identifying 351 endpoint attributes. 353 Endpoint: Defined in [RFC5209] as "any computing device that can be 354 connected to a network." 356 Additional Information - The [RFC5209] definition continues, "Such 357 devices normally are associated with a particular link layer 358 address before joining the network and potentially an IP address 359 once on the network. This includes: laptops, desktops, servers, 360 cell phones, or any device that may have an IP address." 362 To further clarify the [RFC5209] definition, an endpoint is any 363 physical or virtual device that may have a network address. Note 364 that, network infrastructure devices (e.g. switches, routers, 365 firewalls), which fit the definition, are also considered to be 366 endpoints within this document. 368 Physical endpoints are always composites that are composed of 369 hardware components and software components. Virtual endpoints 370 are composed entirely of software components and rely on software 371 components that provide functions equivalent to hardware 372 components. 374 The SACM architecture differentiates two essential categories of 375 endpoints: Endpoints whose security posture is intended to be 376 assessed (target endpoints) and endpoints that are specifically 377 excluded from endpoint posture assessment (excluded endpoints). 379 Based on the definition of an asset, an endpoint is a type of 380 asset. 382 Endpoint Attribute: Is a discreet endpoint characteristic that is 383 computably observable. 385 Endpoint Attributes typically constitute Attributes that can be 386 bundled into Subject (e.g. information about a specific network 387 interface can be represented via a set of multiple AVP). 389 Endpoint Characteristics: The state, configuration and composition 390 of the software components and (virtual) hardware components a 391 target endpoint is composed of, including observable behavior, 392 e.g. sys-calls, log-files, or PDU emission on a network. 394 In SACM work-flows, (Target) Endpoint Characteristics are 395 represented via Information Elements. 397 Endpoint Characterization Task: The task of endpoint 398 characterization that uses endpoint attributes that represent 399 distinct endpoint characteristics. 401 Endpoint Classification: The categorization of of the endpoint into 402 one or more taxonomic structures. 404 Endpoint classification requires declarative guidance in the form 405 of an endpoint profile, discovery results and potentially 406 collection results. Types, classes or the characteristics of an 407 individual target endpoint are defined via endpoint profiles. 409 Endpoint Classification Task: The task of endpoint classification 410 that uses an endpoint's characteristics to determine how to 411 categorize the given endpoint into one or more taxonomic 412 structures. 414 Endpoint Label: A unique label associated with a unique endpoint. 416 Endpoint specializations have corresponding endpoint label 417 specializations. For example, an endpoint label used on a SACM 418 Component is a SACM Component Label. 420 Endpoint Management Capabilities: Enterprise IT management 421 capabilities that are tailored to manage endpoint identity, 422 endpoint information, and associated metadata. 424 Evaluation Task: A task by which an endpoint's asserted attribute 425 value is evaluated against a policy-compliant attribute value. 427 Evaluation Result: The resulting value from having evaluated a set 428 of posture attributes. 430 Expected Endpoint Attribute State: The policy-compliant state of an 431 endpoint attribute that is to be compared against. 433 Sets of expected endpoint attribute states are transported as 434 declarative guidance in target endpoint profiles via the 435 management plane. This, for example, can be a policy, but also a 436 recorded past state. An expected state is represented by an 437 Attribute or a Subject that represents a set of multiple attribute 438 value pairs. 440 Guidance: Machine-processable input directing SACM processes or 441 tasks. 443 Examples of such processes/tasks include automated device 444 management, remediation, collection, evaluation. Guidance 445 influences the behavior of a SACM Component and is considered 446 content of the management plane. In the context of SACM, guidance 447 is machine-readable and can be manually or automatically generated 448 or provided. Typically, the tasks that provide guidance to SACM 449 components have a low-frequency and tend to be sporadic. 451 There are two types of guidance: 453 Declarative Guidance: Guidance that defines the configuration or 454 state an endpoint is supposed to be in, without providing specific 455 actions or methods to produce that desired state. Examples 456 include Target Endpoint Profiles or network topology based 457 requirements. 459 Imperative Guidance: Guidance that prescribes specific actions to 460 be conducted or methods to be used in order to achieve an outcome. 461 Examples include a targeted Collection Task or the IP-Address of a 462 SACM Component that provides a registration function. 464 Prominent examples include: modification of the configuration of a 465 SACM component or updating a target endpoint profile that resides 466 on an evaluator. In essence, guidance is transported via the 467 management plane. 469 Endpoint Hardware Inventory: The set of hardware components that 470 compose a specific endpoint representing its hardware 471 configuration. 473 Hardware Component: A distinguishable physical component used to 474 compose an endpoint. 476 The composition of an endpoint can be changed over time by adding 477 or removing hardware components. In essence, every physical 478 endpoint is potentially a composite of multiple hardware 479 components, typically resulting in a hierarchical composition of 480 hardware components. The composition of hardware components is 481 based on interconnects provided by specific hardware types (e.g. 482 FRU in a chassis are connected via redundant busses). In general, 483 a hardware component can be distinguished by its serial number. 484 Occasionally, hardware components are referred to as power sucking 485 aliens. 487 Information Element: A representation of information about physical 488 and virtual "objects of interest". 490 Information elements are the building blocks that constitute the 491 SACM information model. In the context of SACM, an information 492 element that expresses a single value with a specific name is 493 referred to as an Attribute (analogous to an attribute-value- 494 pair). A set of attributes that is bundled into a more complex 495 composite information element is referred to as a Subject. Every 496 information element in the SACM information model has a unique 497 name. Endpoint attributes or time stamps, for example, are 498 represented as information elements in the SACM information model. 500 Information Model: An abstract representation of data, their 501 properties, relationships between data and the operations that can 502 be performed on the data. 504 While there is some overlap with a data model, [RFC3444] 505 distinguishes an information model as being protocol and 506 implementation neutral whereas a data model would provide such 507 details. The purpose of the SACM information model is to ensure 508 interoperability between SACM data models (that are used as 509 transport encoding) and to provide a standardized set of 510 information elements for communication between SACM components. 512 Interaction Model: The definition of specific sequences regarding 513 the exchange of messages (data in motion), including, for example, 514 conditional branching, thresholds and timers. 516 An interaction model, for example, can be used to define 517 operations, such as registration or discovery, on the control 518 plane. A composition of data models for data in motion and a 519 corresponding interaction model is a protocol. 521 Internal Collector: A collector that runs on a target endpoint to 522 acquire information from that target endpoint. 524 Management Plane: An architectural component providing common 525 functions to steer the behavior of SACM components, e.g. their 526 behavior on the control plane. 528 Typically, a SACM component can fulfill its purpose without 529 continuous input from the management plane. In contrast, without 530 continuous availability of control plane functions a typical SACM 531 component could not function properly. In general, interaction on 532 the management plane is less frequent and less regular than on the 533 control plane. Input via the management plane can be manual (e.g. 534 via a CLI), or can be automated via management plane functions 535 that are part of other SACM components. 537 Network Address: A layer-specific address that follows a layer- 538 specific address scheme. 540 The following characteristics are a summery derived from the 541 Common Information Model and ITU-T X.213. Each Network Interface 542 of a specific layer can be associated with one or more addresses 543 appropriate for that layer. There is no guarantee that a network 544 address is globally unique. A dedicated authority entity can 545 provide a level of assurance that a network address is unique in 546 its given scope. In essence, there is always a scope to a network 547 address, in which it is intended to be unique. 549 Examples include: physical Ethernet port with a MAC address, layer 550 2 VLAN interface with a MAC address, layer 3 interface with 551 multiple IPv6 addresses, layer 3 tunnel ingress or egress with an 552 IPv4 address. 554 Network Interface: An Endpoint is connected to a network via one or 555 more Network Interfaces. Network Interfaces can be physical 556 (Hardware Component) or logical (virtual Hardware component, i.e. 557 a dedicated Software Component). Network Interfaces of an 558 Endpoint can operate on different layers, most prominently what is 559 now commonly called layer 2 and 3. Within a layer, interfaces can 560 be nested. 562 In SACM, the association of Endpoints and Network Addresses via 563 Network Interfaces is vital to maintain interdependent autonomous 564 processes that can be targeted at Target Endpoints, unambiguously. 566 Examples include: physical Ethernet port, layer 2 VLAN interface, 567 a MC-LAG setup, layer 3 Point-to-Point tunnel ingress or egress. 569 Metadata: Data about data. 571 In the SACM information model, data is referred to as Content. 572 Metadata about the content is referred to as Content-Metadata, 573 respectively. Content and Content-Metadata are combined into 574 Subjects called Content-Elements in the SACM information model. 575 Some information elements defined by the SACM information model 576 can be part of the Content or the Content-Metadata. Therefore, if 577 an information element is considered data or data about data 578 depends on which kind of Subject it is associated with. The SACM 579 information model also defines metadata about the data origin via 580 the Subject Statement-Metadata. Typical examples of metadata are 581 time stamps, data origin or data source. 583 Posture: Defined in [RFC5209] as "configuration and/or status of 584 hardware or software on an endpoint as it pertains to an 585 organization's security policy." 587 This term is used within the scope of SACM to represent the 588 configuration and state information that is collected from a 589 target endpoint in the form of endpoint attributes (e.g. software/ 590 hardware inventory, configuration settings, dynamically assigned 591 addresses). This information may constitute one or more posture 592 attributes. 594 Posture Attributes: Defined in [RFC5209] as "attributes describing 595 the configuration or status (posture) of a feature of the 596 endpoint. A Posture Attribute represents a single property of an 597 observed state. For example, a Posture Attribute might describe 598 the version of the operating system installed on the system." 600 Within this document this term represents a specific assertion 601 about endpoint configuration or state (e.g. configuration setting, 602 installed software, hardware) represented via endpoint attributes. 603 The phrase "features of the endpoint" highlighted above refers to 604 installed software or software components. 606 Provider: A provider is a SACM role assigned to a SACM component 607 that provides role-specific functions to provide information to 608 other SACM components. 610 Repository: A repository is a controller that contains functions to 611 consume, store and provide information of a particular kind. 613 Such information is typically data transported on the data plane, 614 but potentially also data and metadata from the control and 615 management plane. A single repository may provide the functions 616 of more than one specific repository type (i.e. configuration 617 baseline repository, assessment results repository, etc.) 619 SACM Broker Controller: A SACM Broker Controller is a controller 620 that contains control plane functions to provide and/or connect 621 services on behalf of other SACM components via interfaces on the 622 control plane. 624 A broker may provide, for example, authorization services and 625 find, upon request, SACM components providing requested services. 627 SACM Component: Is a component, as defined in 628 [I-D.ietf-i2nsf-terminology], that is composed of SACM 629 capabilities. 631 In the context of SACM, a set of SACM functions composes a SACM 632 component. A SACM component conducts SACM tasks, acting on 633 control plane, data plane and/or management plane via 634 corresponding SACM interfaces. SACM defines a set of standard 635 components (e.g. a collector, a broker, or a data store). A SACM 636 component contains at least a basic set of control plane functions 637 and can contain data plane and management plane functions. A SACM 638 component residing on an endpoint assigns one or more SACM roles 639 to the corresponding endpoint due to the SACM functions it is 640 composed of. A SACM component "resides on" an endpoint and an 641 endpoint "contains" a SACM component, correspondingly. For 642 example, a SACM component that is composed solely of functions 643 that provide information would only take on the role of a 644 provider. 646 SACM Component Discovery: The task of discovering the capabilities 647 provided by SACM components within a SACM domain. 649 This is likely to be performed via an appropriate set of control 650 plane functions. 652 SACM Component Label: A specific endpoint label that is used to 653 identify a SACM component. 655 In content-metadata, this label is called data origin. 657 SACM Content: The payload provided by SACM components to the SACM 658 domain on the data plane. 660 SACM content includes the SACM data models. 662 SACM Domain: Endpoints that include a SACM component compose a SACM 663 domain. 665 (To be revised, additional definition content TBD, possible 666 dependencies to SACM architecture) 668 SACM Function: A behavioral aspect of a SACM component that provides 669 external SACM Interfaces or internal interfaces to other SACM 670 Functionse. 672 For example, a SACM Function with SACM Interfaces on the Control 673 Plane can provide a brokering function to other SACM Components. 674 Via Data Plane interfaces, a SACM Function can act as a provider 675 and/or as a consumer of information. SACM Functions can be 676 propagated as the Capabilities of a SACM Component and can be 677 discovered by or negotiated with other SACM Components. 679 SACM Interface: An interface, as defined in 680 [I-D.ietf-i2nsf-terminology], that provides SACM-specific 681 operations. 683 [I-D.ietf-i2nsf-terminology] defines interface as a "set of 684 operations one object knows it can invoke on, and expose to, 685 another object," and further defines interface by stating that an 686 interface "decouples the implementation of the operation from its 687 specification. An interface is a subset of all operations that a 688 given object implements. The same object may have multiple types 689 of interfaces to serve different purposes." 691 In the context of SACM, SACM Functions provide SACM Interfaces on 692 the management, control, or data plane. Operations a SACM 693 Interface provides are based on corresponding data model defined 694 by SACM. SACM Interfaces are used for communication between SACM 695 components. 697 SACM Proxy Controller: A SACM Proxy Controller is a controller that 698 provides data plane and control plane functions, information, or 699 services on behalf of another component, which is not directly 700 participating in the SACM architecture. 702 SACM Role: Is a role, as defined in [I-D.ietf-i2nsf-terminology], 703 that requires the SACM Component assuming the role to bear a set 704 of SACM functions or interfaces. 706 SACM Roles provide three important benefits. First, it enables 707 different behavior to be supported by the same Component for 708 different contexts. Second, it enables the behavior of a 709 Component to be adjusted dynamically (i.e., at runtime, in 710 response)to changes in context, by using one or more Roles to 711 define the behavior desired for each context. Third, it decouples 712 the Roles of a Component from the Applications that use that 713 Component." 715 In the context of SACM, SACM roles are associated with SACM 716 components and are defined by the set of functions and interfaces 717 a SACM component includes. There are three SACM roles: provider, 718 consumer, and controller. The roles associated with a SACM 719 component are determined by the purpose of the SACM functions and 720 corresponding SACM interfaces the SACM component is composed of. 722 SACM Statement: Is an assertion that is made by a SACM Component. 724 Security Automation: The process of which security alerts can be 725 automated through the use of different components to monitor, 726 analyze and assess endpoints and network traffic for the purposes 727 of detecting misconfigurations, misbehaviors or threats. 729 Security Automation is intended to identify target endpoints that 730 cannot be trusted (see "trusted" in [RFC4949]. This goal is 731 achieved by creating and processing evidence (assessment 732 statements) that a target endpoint is not a trusted system 733 [RFC4949]. 735 Software Package: A generic software package (e.g. a text editor). 737 Software Component: A software package installed on an endpoint. 739 The software component may include a unique serial number (e.g. a 740 text editor associated with a unique license key). 742 Software Instance: A running instance of a software component. 744 For example, on a multi-user system, one logged-in user has one 745 instance of a text editor running and another logged-in user has 746 another instance of the same text editor running, or on a single- 747 user system, a user could have multiple independent instances of 748 the same text editor running. 750 State: A volatile set of endpoint attributes of a (target) endpoint 751 that is affected by a reboot-cycle. 753 Local state is created by the interaction of components with other 754 components via the control plane, via processing data plane 755 payload, or via the functional properties of local hardware and 756 software components. Dynamic configuration (e.g. IP address 757 distributed dynamically via an address distribution and management 758 services, such as DHCP) is considered state that is the result of 759 the interaction with another component (e.g. provided by a DHCP 760 server with a specific configuration). 762 Examples: The static association of an IP address and a MAC 763 address in a DHCP server configuration, a directory-path that 764 identifies a log-file directory, a registry entry. 766 Statement: A statement is the root/top-level subject defined in the 767 SACM information model. 769 A statement is used to bundle Content Elements into one subject 770 and includes metadata about the data origin. 772 Subject: A semantic composite information element pertaining to a 773 system entity that is a target endpoint. 775 Like Attributes, subjects have a name and are composed of 776 attributes and/or other subjects. Every IE that is part of a 777 subject can have a quantitiy associated with it (e.g. zero-one, 778 none-unbounded). The content IE of a subject can be an unordered 779 or an ordered list. 781 In contrast to the definitions of subject provided by [RFC4949], a 782 subject in the scope of SACM is neither "a system entity that 783 causes information to flow among objects or changes the system 784 state" nor "a name of a system entity that is bound to the data 785 items in a digital certificate". 787 In the context of SACM, a subject is a semantic composite of 788 information elements about a system entity that is a target 789 endpoint. Every acquirable subject-as defined in the scope of 790 SACM-about a target endpoint represents and therefore identifies 791 every subject-as defined by [RFC4949]-that is a component of that 792 target endpoint. The semantic difference between both definitions 793 can be subtle in practice and is in consequence important to 794 highlight. 796 Supplicant: A component seeking to be authenticated via the control 797 plane for the purpose of participating in a SACM domain. 799 System Resource: Defined in [RFC4949] as "data contained in an 800 information system; or a service provided by a system; or a system 801 capacity, such as processing power or communication bandwidth; or 802 an item of system equipment (i.e., hardware, firmware, software, 803 or documentation); or a facility that houses system operations and 804 equipment." 806 Target Endpoint: Is an endpoint that is under assessment at some 807 point in, or region of, time. 809 Every endpoint that is not specifically designated as an excluded 810 endpoint is a target endpoint. A target endpoint is not part of a 811 SACM domain unless it contains a SACM component (e.g. a SACM 812 component that publishes collection results coming from an 813 internal collector). 815 A target endpoint is similar to a device that is a Target of 816 Evaluation (TOE) as defined in Common Criteria and as referenced 817 by {{RFC4949}. 819 Target Endpoint Address: An address that is layer specific and which 820 follows layer specific address schemes. 822 Each interface of a specific layer can be associated with one or 823 more addresses appropriate for that layer. There is no guarantee 824 that an address is globally unique. In general, there is a scope 825 to an address in which it is intended to be unique. 827 Examples include: physical Ethernet port with a MAC address, layer 828 2 VLAN interface with a MAC address, layer 3 interface with 829 multiple IPv6 addresses, layer 3 tunnel ingress or egress with an 830 IPv4 address. 832 Target Endpoint Characterization: The description of the distinctive 833 nature of a target endpoint, that is based on its characteristics. 835 Target Endpoint Characterization Record: A set of endpoint 836 attributes about a target endpoint that was encountered in a SACM 837 domain, which are associated with that target endpoint as a result 838 of a Target Endpoint Characterization Task. 840 A characterization record is intended to be a representation of an 841 endpoint. It cannot be assured that a record distinctly 842 represents a single target endpoint unless a set of one or more 843 endpoint attributes that compose a unique set of identifying 844 endpoint attributes are included in the record. Otherwise, the 845 set of identifying attributes included in a record can match more 846 than one target endpoints, which are - in consequence - 847 indistinguishable to a SACM domain until more qualifying endpoint 848 attributes can be acquired and added to the record. A 849 characterization record is maintained over time in order to assert 850 that acquired endpoint attributes are either about an endpoint 851 that was encountered before or an endpoint that has not been 852 encountered before in a SACM domain. A characterization record 853 can include, for example, acquired configuration, state or 854 observed behavior of a specific target endpoint. Multiple and 855 even conflicting instances of this information can be included in 856 a characterization record by using timestamps and/or data origins 857 to differentiate them. The endpoint attributes included in a 858 characterization record can be used to re-identify a distinct 859 target endpoint over time. Classes or profiles can be associated 860 with a characterization record via the Classification Task in 861 order to guide collection, evaluation or remediation tasks. 863 Target Endpoint Characterization Task: An ongoing task of 864 continuously adding acquired endpoint attributes to a 865 corresponding record. The TE characterization task manages the 866 representation of encountered target endpoints in the SACM domain 867 in the form of characterization records. For example, the output 868 of a target endpoint discovery task or a collection task can be 869 processed by the characterization task and added to the record. 870 The TE characterization Task also manages these representations of 871 target endpoints encountered in the SACM domain by splitting or 872 merging the corresponding records as new or more refined endpoint 873 attributes become available. 875 Target Endpoint Classification Task: The task of associating a class 876 from an extensible list of classes with an endpoint 877 characterization record. TE classes function as imperative and 878 declarative guidance for collection, evaluation, remediation and 879 security posture assessment in general. 881 Target Endpoint Discovery Task: The ongoing task of detecting 882 previously unknown interaction of a potential target endpoint in 883 the SACM domain. TE Discovery is not directly targeted at a 884 specific target endpoint and therefore an un-targeted task. SACM 885 Components conducting the discovery task as a part of their 886 function are typically distributed and located, for example, on 887 infrastructure components or collect from those remotely via 888 appropriate interfaces. Examples of infrastructure components 889 that are of interest to the discovery task include routers, 890 switches, VM hosting or VM managing components, AAA servers, or 891 servers handling dynamic address distribution. 893 Target Endpoint Identifier: The target endpoint discovery task and 894 the collection tasks can result in a set of identifying endpoint 895 attributes added to a corresponding Characterization Record. This 896 subset of the endpoint attributes included in the record is used 897 as a target endpoint identifier, by which a specific target 898 endpoint can be referenced. Depending on the available 899 identifying attributes, this reference can be ambiguous and is a 900 "best-effort" mechanism. Every distinct set of identifying 901 endpoint attributes can be associated with a target endpoint label 902 that is unique in a SACM domain. 904 Target Endpoint Label: An endpoint label that identifies a specific 905 target endpoint. 907 Target Endpoint Profile: A bundle of expected or desired component 908 composition, configurations and states that is associated with a 909 target endpoint. 911 The corresponding task by which the association with a target 912 endpoint takes places is the endpoint classification task. The 913 task by which an endpoint profile is created is the endpoint 914 characterization task. A type or class of target endpoints can be 915 defined via a target endpoint profile. Examples include: 916 printers, smartphones, or an office PC. 918 In respect to [RFC4949], a target endpoint profile is a protection 919 profile as defined by Common Criteria (analogous to the target 920 endpoint being the target of evaluation). 922 SACM Task: Is a task conducted within the scope of a SACM domain by 923 one or more SACM functions that achieves a SACM-defined outcome. 925 A SACM task can be triggered by other operations or functions 926 (e.g. a query from another SACM component or an unsolicited push 927 on the data plane due to an ongoing subscription). A task is part 928 of a SACM process chain. A task starts at a given point in time 929 and ends in a deterministic state. With the exception of a 930 collection task, a SACM task consumes SACM statements provided by 931 other SACM components. The output of a task is a result that can 932 be provided (e.g. published) on the data plane. 934 The following tasks are defined by SACM: 936 Target Endpoint Discovery 938 Target Endpoint Characterization 940 Target Endpoint Classification 942 Collection 944 Evaluation [TBD] 946 Information Sharing [TBD] 948 SACM Component Discovery 950 SACM Component Authentication [TBD] 952 SACM Component Authorization [TBD] 954 SACM Component Registration [TBD] 956 Timestamps : Defined in [RFC4949] as "with respect to a data object, 957 a label or marking in which is recorded the time (time of day or 958 other instant of elapsed time) at which the label or marking was 959 affixed to the data object". 961 A timestamp always requires context, i.e. additional information 962 elements that are associated with it. Therefore, all timestamps 963 wrt information elements are always metadata. Timestamps in SACM 964 Content Elements may be generated outside a SACM Domain and may be 965 encoded in an unknown representation. Inside a SACM domain the 966 representation of timestamps is well-defined and unambiguous. 968 Virtual Endpoint: An endpoint composed entirely of logical system 969 components (see [RFC4949]). 971 The most common example is a virtual machine/host running on a 972 target endpoint. Effectively, target endpoints can be nested and 973 at the time of this writing the most common example of target 974 endpoint characteristics about virtual components is the 975 EntLogicalEntry in [RFC6933]. 977 Vulnerability Assessment: An assessment specifically tailored to 978 determining whether a set of endpoints is vulnerable according to 979 the information contained in the vulnerability description 980 information. 982 Vulnerability Description Information: Information pertaining to the 983 existence of a flaw or flaws in software, hardware, and/or 984 firmware, which could potentially have an adverse impact on 985 enterprise IT functionality and/or security. 987 Vulnerability description information should contain enough 988 information to support vulnerability detection. 990 Vulnerability Detection Data: A type of imperative guidance 991 extracted or derived from vulnerability description information 992 that describes the specific mechanisms of vulnerability detection 993 that is used by an enterprise's vulnerability management 994 capabilities to determine if a vulnerability is present on an 995 endpoint. 997 Vulnerability Management Capabilities: An IT management capability 998 tailored toward managing endpoint vulnerabilities and associated 999 metadata on an ongoing basis by ingesting vulnerability 1000 description information and vulnerability detection data, and 1001 performing vulnerability assessments. 1003 Vulnerability assessment capabilities: An assessment capability that 1004 is tailored toward determining whether a set of endpoints is 1005 vulnerable according to vulnerability description information. 1007 Workflow: A workflow is a modular composition of tasks that can 1008 contain loops, conditionals, multiple starting points and multiple 1009 endpoints. 1011 The most prominent workflow in SACM is the assessment workflow. 1013 3. IANA Considerations 1015 This memo includes no request to IANA. 1017 4. Security Considerations 1019 This memo documents terminology for security automation. While it is 1020 about security, it does not affect security. 1022 5. Acknowledgements 1024 6. Change Log 1026 Changes from version 00 to version 01: 1028 o Added simple list of terms extracted from UC draft -05. It is 1029 expected that comments will be received on this list of terms as 1030 to whether they should be kept in this document. Those that are 1031 kept will be appropriately defined or cited. 1033 Changes from version 01 to version 02: 1035 o Added Vulnerability, Vulnerability Management, xposure, 1036 Misconfiguration, and Software flaw. 1038 Changes from version 02 to version 03: 1040 o Removed Section 2.1. Cleaned up some editing nits; broke terms 1041 into 2 sections (predefined and newly defined terms). Added some 1042 of the relevant terms per the proposed list discussed in the IETF 1043 89 meeting. 1045 Changes from version 03 to version 04: 1047 o TODO 1049 Changes from version 04 to version 05: 1051 o TODO 1053 Changes from version 05 to version 06: 1055 o Updated author information. 1057 o Combined "Pre-defined Terms" with "New Terms and Definitions". 1059 o Removed "Requirements language". 1061 o Removed unused reference to use case draft; resulted in removal of 1062 normative references. 1064 o Removed introductory text from Section 1 indicating that this 1065 document is intended to be temporary. 1067 o Added placeholders for missing change log entries. 1069 Changes from version 06 to version 07: 1071 o Added Contributors section. 1073 o Updated author list. 1075 o Changed title from "Terminology for Security Assessment" to 1076 "Secure Automation and Continuous Monitoring (SACM) Terminology". 1078 o Changed abbrev from "SACM-Terms" to "SACM Terminology". 1080 o Added appendix The Attic to stash terms for future updates. 1082 o Added Authentication, Authorization, Data Confidentiality, Data 1083 Integrity, Data Origin, Data Provenance, SACM Component, SACM 1084 Component Discovery, Target Endpoint Discovery. 1086 o Major updates to Building Block, Function, SACM Role, Target 1087 Endpoint. 1089 o Minor updates to Broker, Capability, Collection Task, Evaluation 1090 Task, Posture. 1092 o Relabeled Role to SACM Role, Endpoint Target to Target Endpoint, 1093 Endpoint Discovery to Endpoint Identification. 1095 o Moved Asset Targeting, Client, Endpoint Identification to The 1096 Attic. 1098 o Endpoint Attributes added as a TODO. 1100 o Changed the structure of the Change Log. 1102 Changes from version 07 to version 08: 1104 o Added Assertion, Collection Result, Collector, Excluded Endpoint, 1105 Internal Collector, Network Address, Network Interface, SACM 1106 Domain, Statement, Target Endpoint Identifier, Target Endpoint 1107 Label, Timestamp. 1109 o Major updates to Attributes, Broker, Collection Task, Consumer, 1110 Controller, Control Plane, Endpoint Attributes, Expected Endpoint 1111 State, SACM Function, Provider, Proxy, Repository, SACM Role, 1112 Target Endpoint. 1114 o Minor updates to Asset, Building Block, Data Origin, Data Source, 1115 Data Provenance, Endpoint, Management Plane, Posture, Posture 1116 Attribute, SACM Component, SACM Component Discovery, Target 1117 Endpoint Discovery. 1119 o Relabeled Function to SACM Function. 1121 Changes from version 08 to version 09: 1123 o Updated author list. 1125 o Added Data Plane, Endpoint Characterization, Endpoint 1126 Classification, Guidance, Interaction Model, Software Component, 1127 Software Instance, Software Package, Statement, Target Endpoint 1128 Profile, SACM Task. 1130 o Removed Building Block. 1132 o Major updates to Control Plane, Endpoint Attribute, Expected 1133 Endpoint State, Information Model, Management Plane. 1135 o Minor updates to Attribute, Capabilities, SACM Function, SACM 1136 Component, Collection Task. 1138 o Moved Asset Characterization to The Attic. 1140 Changes from version 09 to version 10: 1142 o Added Configuration Drift, Data in Motion, Data at Rest, Endpoint 1143 Management Capability, Hardware Component, Hardware Inventory, 1144 Hardware Type, SACM Interface, Target Endpoint Characterization 1145 Record, Target Endpoint Characterization Task, Target Endpoint 1146 Classification Task, Target Endpoint Discovery Task, Vulnerability 1147 Description Information, Vulnerability Detection Data, 1148 Vulnerability Management Capability, Vulnerability Assessment 1150 o Added references to i2nsf definitions in Capability, SACM 1151 Component, SACM Interface, SACM Role. 1153 o Added i2nsf Terminology I-D Reference. 1155 o Major Updates to Endpoint, SACM Task, Target Endpoint Identifier. 1157 o Minor Updates to Guidance, SACM Component Discovery, Target 1158 Endpoint Label, Target Endpoint Profile. 1160 o Relabeled SACM Task 1162 o Removed Target Endpoint Discovery 1164 Changes from version 10 to version 11: 1166 o Added Content Element, Content Metadata, Endpoint Label, 1167 Information Element, Metadata, SACM Component Label, Workflow. 1169 o Major Updates to Assessment, Capability, Collector, Endpoint 1170 Management Capabilities, Guidance, Vulnerability Assessment 1171 Capabilities, Vulnerability Detection Data, Vulnerability 1172 Assessment Capabilities. 1174 o Minor updates to Collection Result, Control Plane, Data in Motion, 1175 Data at Rest, Data Origin, Network Interface, Statement, Target 1176 Endpoint Label. 1178 o Relabeled Endpoint Management Capability, Vulnerability Management 1179 Capability, Vulnerability Assessment. 1181 Changes from version 11 to version 12: 1183 o Added Configuration, Endpoint Characteristic, Event, SACM Content, 1184 State, Subject. 1186 o Major Updates to Assertion, Data in Motion, Data Provenance, Data 1187 Source, Interaction Model. 1189 o Minor Updates to Attribute, Control Plane, Data Origin, Data 1190 Provenance, Expected Endpoint State, Guidance, Target Endpoint 1191 Classification Task, Vulnerability Detection Data. 1193 Changes from version 12 to version 13: 1195 o Added Virtual Component. 1197 o Major Updates to Capability, Collection Task, Hardware Component, 1198 Hardware Type, Security Automation, Subject, Target Endpoint, 1199 Target Endpoint Profile. 1201 o Minor Updates to Assertion, Data Plane, Endpoint Characteristics. 1203 Changes from version 13 to version 14: 1205 o Handled a plethora of issues listed in GitHub. 1207 o Pruned some commonly understood terms. 1209 o Narrowing term labels per their definitions. 1211 o In some cases, excised expositional text. 1213 o Where expositional text was left intact, it has been separated 1214 from the actual definition of a term. 1216 7. Contributors 1217 David Waltermire 1218 National Institute of Standards and Technology 1219 100 Bureau Drive 1220 Gaithersburg, MD 20877 1221 USA 1223 Email: david.waltermire@nist.gov 1225 Adam W. Montville 1226 Center for Internet Security 1227 31 Tech Valley Drive 1228 East Greenbush, NY 12061 1229 USA 1231 Email: adam.w.montville@gmail.com 1233 David Harrington 1234 Effective Software 1235 50 Harding Rd 1236 Portsmouth, NH 03801 1237 USA 1239 Email: ietfdbh@comcast.net 1241 Brian Ford 1242 Lancope 1243 3650 Brookside Parkway, Suite 500 1244 Alpharetta, GA 30022 1245 USA 1247 Email: bford@lancope.com 1249 Merike Kaeo 1250 Double Shot Security 1251 3518 Fremont Avenue North, Suite 363 1252 Seattle, WA 98103 1253 USA 1255 Email: merike@doubleshotsecurity.com 1257 8. References 1258 8.1. Normative References 1260 [RFC5792] Sangster, P. and K. Narayan, "PA-TNC: A Posture Attribute 1261 (PA) Protocol Compatible with Trusted Network Connect 1262 (TNC)", RFC 5792, DOI 10.17487/RFC5792, March 2010, 1263 . 1265 [RFC6933] Bierman, A., Romascanu, D., Quittek, J., and M. 1266 Chandramouli, "Entity MIB (Version 4)", RFC 6933, 1267 DOI 10.17487/RFC6933, May 2013, 1268 . 1270 8.2. Informative References 1272 [I-D.ietf-i2nsf-terminology] 1273 Hares, S., Strassner, J., Lopez, D., Xia, L., and H. 1274 Birkholz, "Interface to Network Security Functions (I2NSF) 1275 Terminology", draft-ietf-i2nsf-terminology-05 (work in 1276 progress), January 2018. 1278 [I-D.ietf-netmod-entity] 1279 Bierman, A., Bjorklund, M., Dong, J., and D. Romascanu, "A 1280 YANG Data Model for Hardware Management", draft-ietf- 1281 netmod-entity-08 (work in progress), January 2018. 1283 [I-D.ietf-sacm-vuln-scenario] 1284 Coffin, C., Cheikes, B., Schmidt, C., Haynes, D., 1285 Fitzgerald-McKay, J., and D. Waltermire, "SACM 1286 Vulnerability Assessment Scenario", draft-ietf-sacm-vuln- 1287 scenario-02 (work in progress), September 2016. 1289 [RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between 1290 Information Models and Data Models", RFC 3444, 1291 DOI 10.17487/RFC3444, January 2003, 1292 . 1294 [RFC4949] Shirey, R., "Internet Security Glossary, Version 2", 1295 FYI 36, RFC 4949, DOI 10.17487/RFC4949, August 2007, 1296 . 1298 [RFC5209] Sangster, P., Khosravi, H., Mani, M., Narayan, K., and J. 1299 Tardo, "Network Endpoint Assessment (NEA): Overview and 1300 Requirements", RFC 5209, DOI 10.17487/RFC5209, June 2008, 1301 . 1303 [RFC6192] Dugal, D., Pignataro, C., and R. Dunn, "Protecting the 1304 Router Control Plane", RFC 6192, DOI 10.17487/RFC6192, 1305 March 2011, . 1307 [X.1252] "ITU-T X.1252 (04/2010)", n.d.. 1309 Appendix A. The Attic 1311 The following terms are stashed for now and will be updated later: 1313 Asset Characterization: Asset characterization is the process of 1314 defining attributes that describe properties of an identified 1315 asset. 1317 Asset Targeting: Asset targeting is the use of asset identification 1318 and categorization information to drive human-directed, automated 1319 decision making for data collection and analysis in support of 1320 endpoint posture assessment. 1322 Client: An architectural component receiving services from another 1323 architectural component. 1325 Endpoint Identification (TBD per list; was "Endpoint Discovery"): 1326 The process by which an endpoint can be identified. 1328 Authors' Addresses 1330 Henk Birkholz 1331 Fraunhofer SIT 1332 Rheinstrasse 75 1333 Darmstadt 64295 1334 Germany 1336 Email: henk.birkholz@sit.fraunhofer.de 1338 Jarrett Lu 1339 Oracle Corporation 1340 4180 Network Circle 1341 Santa Clara, CA 95054 1342 USA 1344 Email: jarrett.lu@oracle.com 1346 John Strassner 1347 Huawei Technologies 1348 2330 Central Expressway 1349 Santa Clara, CA 95138 1350 USA 1352 Email: john.sc.strassner@huawei.com 1353 Nancy Cam-Winget 1354 Cisco Systems 1355 3550 Cisco Way 1356 San Jose, CA 95134 1357 USA 1359 Email: ncamwing@cisco.com 1361 Adam Montville 1362 Center for Internet Security 1363 31 Tech Valley Drive 1364 East Greenbush, NY 12061 1365 USA 1367 Email: adam.w.montville@gmail.com