idnits 2.17.1 draft-ietf-sacm-terminology-08.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 (October 14, 2015) is 3110 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'TBD' is mentioned on line 278, but not defined Summary: 0 errors (**), 0 flaws (~~), 2 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 October 14, 2015 5 Expires: April 16, 2016 7 Secure Automation and Continuous Monitoring (SACM) Terminology 8 draft-ietf-sacm-terminology-08 10 Abstract 12 This memo documents terminology used in the documents produced by 13 SACM (Security Automation and Continuous Monitoring). 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on April 16, 2016. 32 Copyright Notice 34 Copyright (c) 2015 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Terms and Definitions . . . . . . . . . . . . . . . . . . . . 2 51 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 52 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 53 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 54 6. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 10 55 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 12 56 8. Informative References . . . . . . . . . . . . . . . . . . . 14 57 Appendix A. The Attic . . . . . . . . . . . . . . . . . . . . . 14 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 14 60 1. Introduction 62 Our goal with this document is to improve our agreement on the 63 terminology used in documents produced by the IETF Working Group for 64 Security Automation and Continuous Monitoring. Agreeing on 65 terminology should help reach consensus on which problems we're 66 trying to solve, and propose solutions and decide which ones to use. 68 2. Terms and Definitions 70 This section describes terms that have been defined by other RFC's 71 and defines new ones. The predefined terms will reference the RFC 72 and where appropriate will be annotated with the specific context by 73 which the term is used in SACM. 75 Assertion: Defined by the ITU in [X.1252] as "a statement made by an 76 entity without accompanying evidence of its validity". In the 77 context of SACM, an assertion is a collection result that includes 78 metadata about the data source (and optionally a timestamp 79 indicating the point in time the assertion was created at). The 80 validity of an assertion cannot be verified. 82 Assessment: Defined in [RFC5209] as "the process of collecting 83 posture for a set of capabilities on the endpoint (e.g., host- 84 based firewall) such that the appropriate validators may evaluate 85 the posture against compliance policy." 87 Within SACM the use of the term is expanded to support other uses 88 of collected posture (e.g. reporting, network enforcement, 89 vulnerability detection, license management). The phrase "set of 90 capabilities on the endpoint" includes: hardware and software 91 installed on the endpoint." 93 Asset: Defined in [RFC4949] as "a system resource that is (a) 94 required to be protected by an information system's security 95 policy, (b) intended to be protected by a countermeasure, or (c) 96 required for a system's mission". In the scope of SACM, an asset 97 can be composed of other assets. Examples of Assets include: 98 Endpoints, Software, Guidance, or X.509 public key certificates. 99 An asset is not necessarily owned by an organization. 101 Asset Characterization: Asset characterization is the process of 102 defining attributes that describe properties of an identified 103 asset. 105 Asset Management: The process by which assets are provisioned, 106 updated, maintained and deprecated. 108 Attribute: Defined in [RFC5209] as "data element including any 109 requisite meta-data describing an observed, expected, or the 110 operational status of an endpoint feature (e.g., anti-virus 111 software is currently in use)." If not indicated otherwise, 112 attributes in SACM are represented and processed as attribute 113 value pairs, and the terms attribute and endpoint attribute are 114 synonyms. 116 Authentication: Defined in [RFC4949] as "the process of verifying a 117 claim that a system entity or system resource has a certain 118 attribute value." 120 Authorization: Defined in [RFC4949] as "an approval that is granted 121 to a system entity to access a system resource." 123 Broker: A broker is a specific controller type that contains control 124 plane functions to provide and/or connect services on behalf of 125 other SACM components via interfaces on the control plane. A 126 broker may provide, for example, authorization services and find, 127 upon request, SACM components providing requested services. 129 Building Block: For SACM, a building block is a unit of 130 functionality that is used to compose SACM components. It 131 contains SACM functions and may apply to one or more use cases. 132 The functions of a building block can have interfaces on the data 133 plane, the control plane, or on the management plane. 135 Capability: The extent of an SACM component's ability enabled by the 136 functions (bundled into building blocks) it is composed of. 137 Capabilities are propagated by a SACM component and can be 138 discovered by or negotiated with other SACM components. For 139 example, the capability of a SACM Provider may be to provide 140 endpoint management data, or only a subset of that data. 142 Collection Result: Information about a target endpoint that is 143 produced by a collector conducting a collection task. A 144 collection result is composed of one or more endpoint attributes. 146 Collection Task: The task by which endpoint attributes and/or 147 corresponding attribute values about a target endpoint are 148 collected. There are three types of collection tasks, each 149 requiring an appropriate set of functions to be included in the 150 SACM component conducting the collection task: 152 Self-Reported: A SACM component located on the target endpoint 153 itself conducts the collection task. 155 Remote: A SACM component located on an Endpoint different from the 156 target endpoint conducts the collection task via interfaces 157 available on the target endpoint, e.g. SNMP/NETCONF or WMI. 159 Observed: A SACM component located on an Endpoint different from 160 the target endpoint observes network traffic related to the target 161 endpoint and conducts the collection task via interpretation of 162 that network traffic. 164 Collector: A piece of software that acquires information about one 165 or more target endpoints by conducting collection tasks. A 166 collector provides acquired information to SACM components in the 167 form of collection results. A SACM component that consumes 168 collection results may take on the role of a provider and publish 169 the collection results in a SACM domain. (TBD: A collector may 170 not be a SACM component and therefore not part of a SACM domain). 172 Consumer: A consumer is a SACM role that is assigned to a SACM 173 component that contains functions to receive information from 174 other SACM components. 176 Control Plane: An architectural component providing common control 177 functions to all SACM components, including authentication, 178 authorization, capability discovery or negotiation. The control 179 plane orchestrates the flow on the data plane according to 180 guidance and/or input from the management plane. 182 Controller: A controller is a SACM role that is assigned to a SACM 183 component containing control plane functions that manage and 184 facilitate information sharing or execute on security functions. 185 There are three types of SACM controllers: Broker, Proxy, and 186 Repository. Depending on its type, a controller can also contain 187 functions that have interfaces on the data plane. 189 Data Confidentiality: Defined in [RFC4949] as "the property that 190 data is not disclosed to system entities unless they have been 191 authorized to know the data." 193 Data Integrity: Defined in [RFC4949] as "the property that data has 194 not been changed, destroyed, or lost in an unauthorized or 195 accidental manner." 197 Data Source: One or more properties that enable a SACM component to 198 identify an (target) endpoint that is claimed to be the original 199 source of received data. 201 Data Origin: One or more properties that enable a SACM component to 202 identify the SACM component that initially acquired or produced 203 data about a (target) endpoint (e.g. via collection from a data 204 source). 206 Data Provenance: A historical record of the sources, origins and 207 evolution of data that is influenced by inputs, entities, 208 functions and processes. 210 Endpoint: Defined in [RFC5209] as "any computing device that can be 211 connected to a network. Such devices normally are associated with 212 a particular link layer address before joining the network and 213 potentially an IP address once on the network. This includes: 214 laptops, desktops, servers, cell phones, or any device that may 215 have an IP address." 217 To further clarify the [RFC5209] definition, an endpoint is any 218 physical or virtual device that may have a network address. Note 219 that, network infrastructure devices (e.g. switches, routers, 220 firewalls), which fit the definition, are also considered to be 221 endpoints within this document. 223 The SACM architecture differentiates two essential categories of 224 endpoints: Endpoints whose security posture is intended to be 225 assessed (target endpoints) and endpoints that are specifically 226 excluded from endpoint posture assessment (excluded endpoints). 228 Based on the definition of an asset, an endpoint is a type of 229 asset. 231 Endpoint Attribute: In the context of SACM, endpoint attribute is a 232 synonym for the term attribute. Endpoint Attributes are typically 233 represented as AVP. 235 Evaluation Task: The task by which endpoint attributes are 236 evaluated. 238 Evaluation Result: The resulting value from having evaluated a set 239 of posture attributes. 241 Excluded Endpoint: A specific designation, which is assigned to an 242 endpoint that is not supposed to be the subject of a collection 243 task (and therefore is not a target endpoint). Typically but not 244 necessarily, endpoints that contain a SACM component (and are 245 therefore part of the SACM domain) are designated as excluded 246 endpoints. Target endpoints that contain a SACM component cannot 247 be designated as excluded endpoints and are part of the SACM 248 domain. 250 Expected Endpoint State: The required state of an endpoint that is 251 to be compared against. This, for example, can be a policy or a 252 recorded past state. A state is represented via a single or an 253 associated set of attribute value pairs. 255 SACM Function: A behavioral aspect or capacity of a particular 256 building block that is part of a SACM component, which belies that 257 SACM component's purpose. For example, a SACM function with 258 interfaces on the control plane can provide a brokering function 259 to other SACM components. Via data plane interfaces, a function 260 can act as a provider and/or as a consumer of information. SACM 261 functions can be propagated as the capabilities of a SACM 262 component and can be discovered by or negotiated with other SACM 263 components. 265 Information Model: An information model is an abstract 266 representation of data, their properties, relationships between 267 data and the operations that can be performed on the data. While 268 there is some overlap with a data model, [RFC3444] distinguishes 269 an information model as being protocol and implementation neutral 270 whereas a data model would provide such details. 272 Internal Collector: Internal Collector: a collector that runs on a 273 target endpoint to acquire information from that target endpoint. 274 (TBD: An internal collector is not a SACM component and therefore 275 not part of a SACM domain). 277 Management Plane: An architectural component providing common 278 functions to all SACM participants, including [TBD]. 280 Network Address: Network addresses are layer specific and follow 281 layer specific address schemes. Each interface of a specific 282 layer can be associated with one or more addresses appropriate for 283 that layer. There is no guarantee that an address is globally 284 unique. In general, there is a scope to an address in which it is 285 intended to be unique. 287 Examples include: physical Ethernet port with a MAC address, layer 288 2 VLAN interface with a MAC address, layer 3 interface with 289 multiple IPv6 addresses, layer 3 tunnel ingress or egress with an 290 IPv4 address. 292 Network Interface: An endpoint is connected to a network via one or 293 more interfaces. Interfaces can be physical or virtual. 294 Interfaces of an endpoint can operate on different layers, most 295 prominently what is now commonly called layer 2 and 3. Within a 296 layer, interfaces can be nested. On layer 2, a root interface is 297 typically associated with a physical interface port and nested 298 interfaces are virtual interfaces. In the case of a virtual 299 endpoint, a root interface can be a virtual interface. Virtual 300 layer 2 interfaces of one or more endpoints can also constitute an 301 aggregated group of links that act as one. On layer 3, nested 302 interfaces typically constitute virtual tunnels or networks. 304 Examples include: physical Ethernet port, layer 2 VLAN interface, 305 a MC-LAG setup, layer 3 Point-to-Point tunnel ingress or egress. 307 Posture: Defined in [RFC5209] as "configuration and/or status of 308 hardware or software on an endpoint as it pertains to an 309 organization's security policy." 311 This term is used within the scope of SACM to represent the 312 configuration and state information that is collected from a 313 target endpoint in the form of endpoint attributes (e.g. software/ 314 hardware inventory, configuration settings, dynamically assigned 315 addresses). This information may constitute one or more posture 316 attributes. 318 Posture Attributes: Defined in [RFC5209] as "attributes describing 319 the configuration or status (posture) of a feature of the 320 endpoint. A Posture Attribute represents a single property of an 321 observed state. For example, a Posture Attribute might describe 322 the version of the operating system installed on the system." 324 Within this document this term represents a specific assertion 325 about endpoint configuration or state (e.g. configuration setting, 326 installed software, hardware) represented via endpoint attributes. 327 The phrase "features of the endpoint" highlighted above refers to 328 installed software or software components. 330 Provider: A provider is a SACM role that is assigned to a SACM 331 component that contains functions to provide information to other 332 SACM components. 334 Proxy: A proxy is a specific controller type that provides data 335 plane and control plane functions, information, or services on 336 behalf of another component, which is not directly participating 337 in the SACM architecture. 339 Repository: A repository is a specific controller type that contains 340 functions to store information of a particular kind - typically 341 data transported on the data plane, but potentially also data and 342 metadata from the control and management plane. A single 343 repository may provide the functions of more than one specific 344 repository type (i.e. configuration baseline repository, 345 assessment results repository, etc.) 347 SACM Role: SACM roles are associated with SACM components and are 348 defined by the set of functions and interfaces a SACM component 349 includes. There are three SACM roles: provider, consumer, and 350 controller. The roles associated with a SACM component are 351 determined by the purpose of the functions and corresponding 352 interfaces the SACM component is composed of. 354 SACM Component: A composition of building blocks that contain SACM 355 functions (acting on control plane, data plane or management 356 plane). SACM defines a set of standard components (e.g. a 357 collector, a broker, or a data store). A SACM component contains 358 at least a basic set of control plane building blocks and can 359 contain data plane and management plane building blocks. A SACM 360 component residing on an endpoint assigns one or more SACM roles 361 to the corresponding endpoint due to the SACM functions it is 362 composed of. A SACM component "resides on" an endpoint and an 363 endpoint "contains" a SACM component, correspondingly. For 364 example, a SACM component that is composed solely of building 365 blocks that provide information is a provider. 367 SACM Component Discovery: The function by which a SACM component 368 (e.g. by role, capabilities, or data provided/consumed) can be 369 discovered. 371 SACM Domain: Endpoints that include a SACM component compose a SACM 372 domain. (To be revised, additional definition content TBD, 373 possible dependencies to SACM architecture) 375 Security Automation: The process of which security alerts can be 376 automated through the use of different tools to monitor, evaluate 377 and analyze endpoint and network traffic for the purposes of 378 detecting misconfigurations, misbehaviors or threats. 380 Statement: The output of a provider, e.g. a report or an assertion 381 acquired via a collection result from a collector, that includes 382 metadata about the data origin and the point in time the statement 383 was created at. A statement can be accompanied by evidence of the 384 validity of its metadata. 386 Supplicant: The entity seeking to be authenticated by the Management 387 Plane for the purpose of participating in the SACM architecture. 389 System Resource: Defined in [RFC4949] as "data contained in an 390 information system; or a service provided by a system; or a system 391 capacity, such as processing power or communication bandwidth; or 392 an item of system equipment (i.e., hardware, firmware, software, 393 or documentation); or a facility that houses system operations and 394 equipment. 396 Target Endpoint: A target endpoint is an "endpoint under assessment" 397 (even if it is not actively under assessment at all times) or 398 "endpoint of interest". Every endpoint that is not specifically 399 designated as an excluded endpoint is a target endpoint. A target 400 endpoint is not part of a SACM domain unless it contains a SACM 401 component (e.g. a SACM component that publishes collection results 402 coming from an internal collector). 404 A target endpoint is similar to a device that is a Target of 405 Evaluation (TOE) as defined in Common Criteria. 407 Target Endpoint Discovery: The function by which target endpoints 408 can be discovered. The output of target endpoint discovery 409 typically includes identifying endpoint attributes. 411 Target Endpoint Identifier: The target endpoint discovery process 412 and collection tasks targeted at target endpoints can result in a 413 set of identifying endpoint attributes. This set of identifying 414 endpoint attributes is used as a target endpoint identifier 415 referring to a specific target endpoint. Depending on the 416 available identifying attributes this reference can be ambiguous 417 and is a "best-effort" mechanism. Every distinct set of 418 identifying endpoint attributes can be associated with a unique 419 target endpoint label. 421 Target Endpoint Label: An artificially created id that references a 422 distinct set of identifying attributes (Target Endpoint 423 Identifier). A target endpoint label is unique in a SACM domain 424 and created by a SACM component that contains an appropriate 425 building block of functions. 427 Timestamps : Defined in [RFC4949] as "with respect to a data object, 428 a label or marking in which is recorded the time (time of day or 429 other instant of elapsed time) at which the label or marking was 430 affixed to the data object" and as "with respect to a recorded 431 network event, a data field in which is recorded the time (time of 432 day or other instant of elapsed time) at which the event took 433 place.". 435 This term is used in SACM to describe a recorded point in time at 436 which an endpoint attribute is created or updated by a target 437 endpoint and observed, transmitted or processed by a SACM 438 component. Timestamps can be created by target endpoints or SACM 439 components and are associated with endpoint attributes provided or 440 consumed by SACM components. Outside of the domain of SACM 441 components the assurance of correctness of time stamps is 442 typically significantly lower than inside a SACM domain. In 443 general, it cannot be simply assumed that the source of time a 444 target endpoint uses is synchronized or trustworthy. 446 3. IANA Considerations 448 This memo includes no request to IANA. 450 4. Security Considerations 452 This memo documents terminology for security automation. While it is 453 about security, it does not affect security. 455 5. Acknowledgements 457 6. Change Log 459 Changes from version 00 to version 01: 461 o Added simple list of terms extracted from UC draft -05. It is 462 expected that comments will be received on this list of terms as 463 to whether they should be kept in this document. Those that are 464 kept will be appropriately defined or cited. 466 Changes from version 01 to version 02: 468 o Added Vulnerability, Vulnerability Management, xposure, 469 Misconfiguration, and Software flaw. 471 Changes from version 02 to version 03: 473 o Removed Section 2.1. Cleaned up some editing nits; broke terms 474 into 2 sections (predefined and newly defined terms). Added some 475 of the relevant terms per the proposed list discussed in the IETF 476 89 meeting. 478 Changes from version 03 to version 04: 480 o TODO 482 Changes from version 04 to version 05: 484 o TODO 486 Changes from version 05 to version 06: 488 o Updated author information. 490 o Combined "Pre-defined Terms" with "New Terms and Definitions". 492 o Removed "Requirements language". 494 o Removed unused reference to use case draft; resulted in removal of 495 normative references. 497 o Removed introductory text from Section 1 indicating that this 498 document is intended to be temporary. 500 o Added placeholders for missing change log entries. 502 Changes from version 06 to version 07: 504 o Added Contributors section. 506 o Updated author list. 508 o Changed title from "Terminology for Security Assessment" to 509 "Secure Automation and Continuous Monitoring (SACM) Terminology". 511 o Changed abbrev from "SACM-Terms" to "SACM Terminology". 513 o Added appendix The Attic to stash terms for future updates. 515 o Added Authentication, Authorization, Data Confidentiality, Data 516 Integrity, Data Origin, Data Provenance, SACM Component, SACM 517 Component Discovery, Target Endpoint Discovery. 519 o Major updates to Building Block, Function, SACM Role, Target 520 Endpoint. 522 o Minor updates to Broker, Capability, Collection Task, Evaluation 523 Task, Posture. 525 o Relabled Role to SACM Role, Endpoint Target to Target Endpoint, 526 Endpoint Discovery to Endpoint Identification. 528 o Moved Asset Targeting, Client, Endpoint Identification to The 529 Attic. 531 o Endpoint Attributes added as a TODO. 533 o Changed the structure of the Change Log. 535 Changes from version 07 to version 08: 537 o Added Assertion, Collection Result, Collector, Excluded Endpoint, 538 Internal Collector, Network Address, Network Interface, SACM 539 Domain, Statement, Target Endpoint Identifier, Target Endpoint 540 Label, Timestamp. 542 o Major updates to Attributes, Broker, Collection Task, Consumer, 543 Controller, Control Plane, Endpoint Attributes, Expected Endpoint 544 State, SACM Function, Provider, Proxy, Repository, SACM Role, 545 Target Endpoint. 547 o Minor updates to Asset, Building Block, Data Origin, Data Source, 548 Data Provenance, Endpoint, Management Plane, Posture, Posture 549 Attribute, SACM Component, SACM Component Discovery, Target 550 Endpoint Discovery. 552 o Relabled Function to SACM Function. 554 7. Contributors 556 David Waltermire 557 National Institute of Standards and Technology 558 100 Bureau Drive 559 Gaithersburg, MD 20877 560 USA 562 Email: david.waltermire@nist.gov 564 Adam W. Montville 565 Center for Internet Security 566 31 Tech Valley Drive 567 East Greenbush, NY 12061 568 USA 570 Email: adam.w.montville@gmail.com 571 David Harrington 572 Effective Software 573 50 Harding Rd 574 Portsmouth, NH 03801 575 USA 577 Email: ietfdbh@comcast.net 579 Nancy Cam-Winget 580 Cisco Systems 581 3550 Cisco Way 582 San Jose, CA 95134 583 USA 585 Email: ncamwing@cisco.com 587 Jarrett Lu 588 Oracle Corporation 589 4180 Network Circle 590 Santa Clara, CA 95054 591 USA 593 Email: jarrett.lu@oracle.com 595 Brian Ford 596 Lancope 597 3650 Brookside Parkway, Suite 500 598 Alpharetta, GA 30022 599 USA 601 Email: bford@lancope.com 603 Merike Kaeo 604 Double Shot Security 605 3518 Fremont Avenue North, Suite 363 606 Seattle, WA 98103 607 USA 609 Email: merike@doubleshotsecurity.com 611 8. Informative References 613 [RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between 614 Information Models and Data Models", RFC 3444, DOI 615 10.17487/RFC3444, January 2003, 616 . 618 [RFC4949] Shirey, R., "Internet Security Glossary, Version 2", FYI 619 36, RFC 4949, DOI 10.17487/RFC4949, August 2007, 620 . 622 [RFC5209] Sangster, P., Khosravi, H., Mani, M., Narayan, K., and J. 623 Tardo, "Network Endpoint Assessment (NEA): Overview and 624 Requirements", RFC 5209, DOI 10.17487/RFC5209, June 2008, 625 . 627 [X.1252] "ITU-T X.1252 (04/2010)", n.d.. 629 Appendix A. The Attic 631 The following terms are stashed for now and will be updated later: 633 Asset Targeting: Asset targeting is the use of asset identification 634 and categorization information to drive human-directed, automated 635 decision making for data collection and analysis in support of 636 endpoint posture assessment. 638 Client: An architectural component receiving services from another 639 architectural component. 641 Endpoint Identification (TBD per list; was "Endpoint Discovery"): 642 The process by which an endpoint can be identified. 644 Author's Address 646 Henk Birkholz 647 Fraunhofer SIT 648 Rheinstrasse 75 649 Darmstadt 64295 650 Germany 652 Email: henk.birkholz@sit.fraunhofer.de