Software Inventory Message and Attributes (SWIMA) for PA-TNC

Coffin, Chris; Fitzgerald-McKay, Jessica; Haynes, Daniel; Waltermire, David; Schmidt, Charles

doi:10.17487/rfc8412

Cited by 1 publication

(1 citation statement)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Internet Engineering Task Force (IETF) NEA and SWIMA: The NEA family of protocols [6] supports the standardized collection of endpoint posture information, and provide an extensible framework for defining standardized and proprietary posture collection capabilities. The Software Inventory Message and Attributes for PA-TNC (SWIMA) [7] is a NEA extension that supports the collection of software inventory information, including SWID tag data. By using the NEA framework, SWIMA can focus on software inventory data collection mechanics, while leaving the details of network transport and delivery to the underlying NEA layers.…”

Section: Iso/iec 19770-2:2015mentioning

confidence: 99%

Transitioning to the Security Content Automation Protocol (SCAP) Version 2

Waltermire¹,

Fitzgerald-McKay²

2018

View full text Add to dashboard Cite

The Security Content Automation Protocol (SCAP) version 2 (v2) automates endpoint posture information collection and the incorporation of that information into network defense capabilities using standardized protocols. SCAP v2 expands the endpoint types supported by SCAP v1 through the explicit inclusion of network equipment, Internet of Things (IoT), and mobile devices in its scope. To automate self-reporting of posture information from endpoint machines, SCAP v2 will integrate with existing network management protocols that include the Internet Engineering Task Force (IETF) Network Endpoint Assessment (NEA) protocols. SCAP v2 will streamline SCAP content acquisition and reuse through its use of the IETF Resource Oriented Lightweight Information Exchange (ROLIE) protocol. Improvements to software version identification and the incorporation of patch information will be made by transitioning from the Common Platform Enumeration (CPE) to Software Identification (SWID) Tags. SCAP v2 provides component-level interoperability via a modular and extensible architecture. This white paper provides a gap analysis of SCAP v1 and an overview of how SCAP v2 will address these gaps; describes the SCAP 2.0 architecture; and provides a plan for completing the work necessary to finalize SCAP v2.

show abstract

Section: Iso/iec 19770-2:2015mentioning

confidence: 99%

Transitioning to the Security Content Automation Protocol (SCAP) Version 2

Waltermire¹,

Fitzgerald-McKay²

2018

View full text Add to dashboard Cite

show abstract

Software Inventory Message and Attributes (SWIMA) for PA-TNC

Cited by 1 publication

References 11 publications

Transitioning to the Security Content Automation Protocol (SCAP) Version 2

Transitioning to the Security Content Automation Protocol (SCAP) Version 2

Contact Info

Product

Resources

About