TPM可信网络连接技术规范：TCG TNC interoperability架构

需积分: 1 76 浏览量更新于2024-06-22 收藏 1.37MB PDF 举报

"TCG-TNC-Architecture-for-Interoperability.pdf 是一份关于可信网络连接（Trusted Network Connections, TNC）的技术规范文档，主要关注基于 Trusted Platform Module (TPM) 的实现。该文档由 Trusted Computing Group (TCG) 发布，版本为2.0，修订版13，发布于2017年10月16日。" 这篇文档详细阐述了如何通过TPM来实现可信网络连接的互操作性架构。TPM是一种硬件安全模块，旨在提供计算平台上的安全性，如加密、密钥存储和平台状态验证等功能。TNC架构的目标是确保不同设备和系统之间的安全通信，尤其是在网络接入控制方面。在TNC架构中，TPM作为核心组件，负责验证计算平台的完整性，包括操作系统、固件以及应用程序等。这有助于防止恶意软件和未经授权的修改对网络造成威胁。TNC框架通常包括以下组件： 1. 客户端：即包含TPM的设备或系统，它需要连接到网络，并执行平台完整性检查。 2. 网络访问点（NAP）：如无线接入点、交换机或路由器，它们执行网络策略检查，决定设备是否可以接入网络。 3. 管理服务器：提供策略决策和管理功能，如确定客户端的安全状态并执行恢复策略。 TNC技术规范详细定义了这些组件之间的通信协议，包括信息交换格式、认证过程和策略实施。这些协议可能基于IETF的EAP（Extensible Authentication Protocol）和其他相关标准，确保了跨平台和设备的互操作性。文档还可能涵盖以下几个方面： - TCG的网络认证协议（TNC Network Authentication Protocol, TNCP）：这是一种用于在网络接入过程中进行身份验证和策略评估的协议。 - 客户端健康检查（Client Health Checking, CHC）：这是评估客户端安全状态的过程，可能包括硬件状态、操作系统状态、防病毒软件状态等。 - 恢复机制：当客户端未能满足安全策略时，管理服务器会触发恢复流程，例如更新补丁、隔离设备或限制网络访问权限。此规范强调，尽管提供了详细的技术指导，但TCG不对任何因使用本规范或其实施导致的损失承担责任，包括但不限于侵犯知识产权、利润损失、数据丢失或间接损害等。 "TCG-TNC-Architecture-for-Interoperability.pdf" 是一份关于如何利用TPM实现安全、可互操作的网络连接的技术规范，对于理解和实施基于TPM的网络安全策略具有重要价值。

Specification Version 2.0

Revision 13 Page 11 of 61

TCG PUBLISHED

Figure 1: TNC Architecture Overview

2.1.4 Measuring Endpoint State

One of the primary purposes of the TNC standards is to enable the collection and evaluation of

endpoint state information, enabling assessment of endpoint and network health. Endpoint

posture is the aggregate state of the endpoint [1], composed by collecting measurements of

specific aspects of endpoint state. TNC originally focused on integrity measurements, primarily

around integrity of the BIOS / operating system and security controls (such as current anti-virus

signature file or running endpoint firewall); TNC measurements have since expanded to include

broader posture measurements, such as endpoint provisioning, installed software, and/or

configuration. All of these measurements are collected via an integrity check handshake, an

exchange of information between TNC components. Endpoint compliance indicates whether the

endpoint posture meets the requirements of its environment.

2.2 Relationships to Other Standards

2.2.1 Relationship to TPM

The TCG's Trusted Platform Module (TPM) [2] [3] supports hardware-based "roots of trust", which

help establish platform integrity, user security, and privacy. The TPM enables a “chain of trust”

for a device’s core components responsible for its boot process and ultimately the execution of

the OS and applications.

In the context of TNC architecture and solutions, TNC can leverage a TPM to increase trust in

endpoint measurements, which improves detection of compromised devices so that appropriate

controls can be applied. TNC mechanisms enable expression of that trust to a third party or

back-end verifier, increasing confidence both in endpoint evaluation and in resulting actions such

as access control decisions. See section 8 for a discussion of TNC with TPM.

2.2.2 Relationship to TCG IWG Architecture

The TNC Architecture builds upon the original architecture developed by the TCG's Infrastructure

Working Group (IWG), which outlines a Platform Authentication model [4]. See Appendix B:

Relation to TCG IWG Architecture for discussion of the TNC Architecture in relation to the IWG

Specification Version 2.0

Revision 13 Page 12 of 61

TCG PUBLISHED

Architecture.

2.2.3 Relationship with IETF NEA

Several TNC endpoint posture-related specifications have been adopted by IETF as the basis for

the IETF Network Endpoint Assessment standards. The IETF NEA Posture Assessment [5],

Posture Broker [6], and Posture Transport [7] [8] protocols are all based on TNC interfaces. See

Section 7.1.1 for a more detailed mapping between TNC and NEA terms and concepts.

2.3 Aim and Purposes

TCG’s Trusted Network Communications (TNC) network security architecture and open

standards enable intelligent policy decisions, dynamic security enforcement, and communication

between security systems. TNC standards facilitate network and endpoint visibility, helping

network managers know who and what is on their network and whether devices are compliant

and secure. TNC standards also enable network-based access control enforcement - granting or

blocking access based on authentication, device compliance, and user behavior - and security

system integration - real-time information sharing enabling dynamic integration of network and

security products.

The aim of the TNC architecture is to provide a framework for the development of standards to

support multi-vendor solutions for:

 Endpoint compliance: TNC specifies schema and protocols for standardized endpoint

posture reporting, both self-reporting and by observing parties. TNC-enabled technology

provides systems administrators the ability to know the aggregate endpoint compliance

status of their environment with near-real-time updates, and reduce the fragmentation of

endpoint posture reports in proprietary databases. This allows the data to be shared

across the network, with network and administrative tools and with other TNC

Architecture elements, to support asset management, threat detection, security

automation and vulnerability analysis use cases.

The TNC Architecture facilitates remediation of endpoints which fail posture verification

by assisting in detection of endpoints requiring remediation and providing a transport

mechanism for remediation instructions; however, it does not standardize specific

methods of remediation. See Appendix C: Assessment, Isolation, and Remediation for

details.

 Control of access to resources: TNC-enabled technology can serve as a gatekeeper for

endpoints accessing sensitive resources, including but not limited to access to a given

network, particular services on the network, specific applications, and/or information.

TNC enables this control either by dynamic configuration of devices (such as switches

and firewalls) that are specifically intended to allow or deny access to resources based

on policy decisions, or by making information available to specific services, which then

used this provided information to make their own access control decisions. The result is

that TNC facilitates a coordinated, multi-level, and comprehensive approach to ensuring

that sensitive resources and actions are only available to authorized parties. See

Appendix D: Basic Message Flows for Network Admission for details.

 Policy enforcement: As noted above, TNC can help prevent unauthorized endpoints and

users from accessing sensitive information and resources. TNC gives administrators a

great deal of power to defined what "unauthorized" means in each case. Decisions as to

whether a given request is authorized can hinge on many factors, including but not

limited to user identity, device identity, the degree to which the endpoint is considered

compliant with policy, time of day, location of the accessing device, type of device (e.g.,

laptop, mobile device, etc.), and other contextual information that sensors and other

parties may have reported about the requesting device and its activities. The criteria for

authorization can be as simple or sophisticated as necessary. Since TNC allows access

Specification Version 2.0

Revision 13 Page 13 of 61

TCG PUBLISHED

to such a broad array of information, the sources of information are extensible, and all

such information can be given weight in making an authorization decision, administrators

benefit from the ability to carefully tune when, how, why, and by whom a given action is

performed.

 Security automation: Security automation is the ability to automate and streamline known

default tasks or responses, so they can be repeated quickly and as needed. TNC

architecture and elements provide robust means of detection of and response to security

events across the enterprise. TNC-enabled technology can share information in real

time, using standard protocols and extensible data formats, which helps all security

systems to be more intelligent by giving them the information they need to get their job

done better and faster. TNC enables security automation protections needed to help

defend resources and networks against today’s security threats as well as the evolving

security landscape in the future.

 Threat detection and response: In addition to the ability to limit access for unauthorized

endpoints, TNC enables continuous monitoring of endpoint posture and behavior, which

gives administrators an expanded ability to find and remediate vulnerabilities. TNC

standards facilitate measurement of how effectively network policy was implemented,

enable dynamic, intelligent response to non-compliant endpoint state and/or behavior,

and allow the enterprise policy to be responsive to external factors such as new threat

intelligence, new vulnerability reports, etc.

2.4 Benefits of TNC

TNC standards deliver a wide range of benefits:

 TNC standards have a proven track record of delivering interoperable solutions to

address endpoint, network, and server security. Products based on TNC standards have

been shipping since 2005. There are many open-source implementations as well.

 TNC standards are widely deployed in real production scenarios. A broad range of

customers across many sectors (Government, Healthcare, Finance, Retail and

Education, among others) are benefitting from interoperable security solutions based on

TNC standards.

 TNC standards are completely vendor-neutral. TNC based solutions leverage existing

network infrastructure in a production environment, adding value to the existing

investment.

 TNC standards are flexible. They support a broad range of assessment options (identity,

health, behavior, and location; hardware-based & software-based security; and pre-

admission & post-admission evaluation and monitoring). TNC standards also

accommodate rapid change and can adapt to the evolving security landscape.

 TNC standards can and do easily integrate with other standards both existing and

emerging, e.g. SWID Tags (ISO 19770-2) [9].

剩余60页未读，继续阅读

书香度年华

粉丝: 1w+
资源: 383

TPM可信网络连接技术规范：TCG TNC interoperability架构

MPWG-tcg-mobile-reference-architecture-1.pdf

ds-tcg205-b说明书

DS-TCG405-E通讯

海康ds-tcg205-e车辆识别设备怎样设置布防

tcg_tpm2_r1p59_part1_architecture

tcg 三次握手四次挥手

截断共轭梯度法MATLAB代码示例

Eigen::Matrix4d gHc = transl(Tcg) * Rcg

Cannot determine archive format of C:\Users\Administrator\AppData\Local\Temp\pip-req-build-tr_t1tcg

linux内核TCG TPM驱动说明

最新资源