Software Inventory Message and Attributes (SWIMA) for PA-TNC
RFC 8412
Document | Type | RFC - Proposed Standard (July 2018; No errata) | |
---|---|---|---|
Authors | Charles Schmidt , Daniel Haynes , Chris Coffin , David Waltermire , Jessica Fitzgerald-McKay | ||
Last updated | 2018-07-05 | ||
Replaces | draft-ietf-sacm-nea-swid-patnc | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication (wg milestone: Dec 2017 - Submit SWIMA to IESG... ) | |
Document shepherd | Karen O'Donoghue | ||
Shepherd write-up | Show (last changed 2018-01-24) | ||
IESG | IESG state | RFC 8412 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Benjamin Kaduk | ||
Send notices to | Karen O'Donoghue <odonoghue@isoc.org>, sacm@ietf.org | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) C. Schmidt Request for Comments: 8412 D. Haynes Category: Standards Track C. Coffin ISSN: 2070-1721 The MITRE Corporation D. Waltermire National Institute of Standards and Technology J. Fitzgerald-McKay United States National Security Agency July 2018 Software Inventory Message and Attributes (SWIMA) for PA-TNC Abstract This document extends "PA-TNC: A Posture Attribute (PA) Protocol Compatible with Trusted Network Connect (TNC)" (RFC 5792) by providing specific attributes and message exchanges to allow endpoints to report their installed software inventory information to a NEA Server, as defined in "Network Endpoint Assessment (NEA): Overview and Requirements" (RFC 5209). Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8412. Schmidt, et al. Standards Track [Page 1] RFC 8412 SWIMA for PA-TNC July 2018 Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ....................................................4 1.1. Network Endpoint Assessment (NEA) ..........................6 1.2. Conventions Used in This Document ..........................7 1.3. Definitions ................................................7 2. Background ......................................................8 2.1. Supported Use Cases ........................................8 2.1.1. Use Software Inventory as an Access Control Factor ..8 2.1.2. Central Stores of Up-to-Date Endpoint Software Inventory Data .............................9 2.1.3. PA-TNC Use Cases ....................................9 2.2. Use Cases That Are Not Supported ...........................9 2.3. SWIMA Requirements ........................................10 2.4. Non-SWIMA Requirements ....................................11 2.5. Assumptions ...............................................12 2.6. Assumptions Not Made ......................................12 3. System Requirements ............................................12 3.1. Data Sources ..............................................13 3.2. Data Models ...............................................14 3.3. Basic Attribute Exchange ..................................16 3.4. Core Software-Reporting Information .......................17 3.4.1. Software Identifiers ...............................17 3.4.2. Data Model Type ....................................19 3.4.3. Record Identifiers .................................19 3.4.4. Software Locators ..................................20 3.4.5. Source Identifiers .................................21 3.4.6. Using Software and Record Identifiers in SWIMA Attributes ...................................22 3.5. Targeted Requests .........................................22 3.6. Monitoring Changes in an Endpoint's Software Inventory Evidence Collection .............................23 Schmidt, et al. Standards Track [Page 2] RFC 8412 SWIMA for PA-TNC July 2018 3.7. Reporting Change Events ...................................26 3.7.1. Event Identifiers ..................................27Show full document text