"NIST SP 500-299云计算安全参考框架简介与重要性"

需积分: 15 181 浏览量更新于2023-12-19 收藏 8.35MB PDF 举报

NIST特别出版物500-299是一份关于云计算安全参考架构的重要文档。该框架旨在为IT行业提供一套标准化的安全指南，以确保云计算环境中的数据和系统得到最佳的保护。为了更好地理解和应用NIST SP 500-299，我们首先需要了解NIST云计算安全工作组和NIST云计算项目，以及它们在信息技术实验室下的工作。这些都是为了推动美国经济的发展和公共福祉。 NIST云计算安全参考框架的核心在于其安全参考架构，它提供了一种系统性的方法，用于识别和解决在云环境中可能出现的各种安全挑战。这个框架的目标是确保在云计算中采用最佳的安全实践，以应对日益复杂的网络威胁和安全漏洞。通过该框架的指导，组织和企业可以更好地规划和实施安全措施，以保护其云基础架构和相关数据资产。此外，NIST的云计算安全参考框架还将数据安全、身份验证、访问控制、合规性和监管等关键主题纳入考虑范围之内。这使得该框架成为一个全面的工具，可以帮助云计算环境中的用户和管理员应对各种安全挑战。通过了解并遵循这些安全指南，组织可以最大限度地降低在云环境中面临的风险，并提高其系统的安全性和稳定性。然而，需要注意的是，NIST SP 500-299并非一劳永逸的解决方案。云计算环境中的安全威胁和漏洞是不断变化的，因此安全参考框架也需要不断地更新和演进。NIST及其云计算安全工作组将继续监测和评估新的安全挑战，并相应地修订其安全框架，以确保其对最新的威胁和漏洞有着响应的能力。综上所述，NIST SP 500-299云计算安全参考框架是一份重要的安全文档，它为云计算环境中的安全管理提供了一套标准化的指导原则。通过遵循该框架的指导，组织可以更好地规划和实施安全措施，以应对各种安全挑战，并提高其云环境的安全性和稳定性。然而，需要注意的是，这份框架也需要不断地更新和演进，以应对不断变化的安全威胁和漏洞。 NIST及其云计算安全工作组将继续监测和评估新的安全挑战，并相应地修订其安全框架，以确保其对最新的威胁和漏洞有着响应的能力。

Page 16

cloud Ecosystem, the section provides a use case example – a generic USG agency service migrated

to the cloud – and highlights the necessary steps to secure the cloud Ecosystem and to determine the

high-level cloud architecture that meets the cloud Consumer’s security requirements. This section

concludes with the negotiation of the contractual terms and agreements in Service Level

Agreements (SLAs).

Annex A depicts the core set of Security Components and how to use it for a particular cloud

deployment model (Public cloud in this case), described in detail in Sec. 5.

Annex B depicts how the Security Components are mapped or paired to the NIST SP 800-53 (Rev.

4): Minimum Security Requirements for Federal Information and Information Systems security

control families using the color code presented in Table 3.

Annex C is the Generic Heat Map of cloud Actor responsibilities for implementing Security

Components and associated security controls in a cloud Ecosystem.

Annex D presents the Data Aggregation table, which indicates the shared responsibility of cloud

Actors to apply Security Components and control measures to varying degrees (i.e., least

responsible, solely responsible, shared responsibility) at the Service-based Ecosystem level.

Annex E presents a matrix that maps the high-level security components, and with them the NIST

SP 800-53 (Rev. 4): Security and Privacy Controls for Federal Information Systems and

Organizations security control families, to the Architectural Components and Sub-Components

defined for each cloud Actor.

Annex F presents the Security Index System (SIS) for the Confidentiality, Integrity, and

Availability (C/I/A) security triad and the Aggregated Security Index System (ASIS) used to

prioritize the Security Components for the Unified Messaging System (UMS) use case. The SIS

example given in this document is merely illustrative: it should not be considered guidance for any

UMS migration to the cloud.

1.5 USING THE DOCUMENT

Federal agencies may use the information presented in this document to help them follow the steps

presented below when migrating a service to the cloud.

• Describe the service that should be migrated to the cloud

• Identify the necessary capabilities of the service

• Categorize the Information System to determine the impact levels and the Security

Components and associated security control baselines (three sets of baseline controls

corresponding to low-impact, moderate-impact, and high-impact information systems).

Page 17

Baseline controls are chosen based on the security category and associated impact level of

information systems determined in accordance with Federal Information Processing

Standard (FIPS) 199: Standards for Security Categorization of Federal Information and

Information Systems and FIPS 200: Minimum Security Requirements for Federal

Information and Information Systems, respectively [16][17].

• Analyze and select the most appropriate instance of a cloud Ecosystem by identifying the

cloud composite architecture, such as the cloud deployment and service models:

o Public IaaS, Public PaaS, Public SaaS;

o Private IaaS, Private PaaS, Private SaaS;

o Hybrid IaaS, Hybrid PaaS, Hybrid SaaS;

o Community IaaS, Community PaaS, and Community SaaS.

• Identify the cloud Actors involved in orchestrating the Cloud Ecosystem (e.g., type of

Provider and Broker)

• Tailor the baseline Security Components to fulfill the security requirements for the

particular use case (i.e., system migrated to the cloud) by:

o Identifying and customizing the core set of Security Components to the assessed

impact level of the system migrated to the cloud by applying a SIS as described in

Sec. 5.2.2.1;

o Identifying the NIST SP 800-53 (Rev. 4): Security and Privacy Controls for Federal

Information Systems and Organizations security controls necessary for each Security

Component;

o Applying scoping considerations to the remaining baseline Security Components and

associated controls;

o Identifying, when necessary, additional compensating Security Components and

security controls;

o Assigning specific values to organization-defined security parameters via explicit

assignment and selection statements;

o Supplementing baselines with additional Security Components and control

enhancements, if needed; and

o Providing additional specification information for Security Components

implementation.

Sec. 5.2 provides a more concrete example of how a new cloud Ecosystem for a UMS can be

orchestrated by leveraging the information presented in this document.

Page 18

2 BACKGROUND

This document presents the NIST Cloud Computing Security Reference Architecture formal model

derived from NIST SP 500-292: NIST Cloud Computing Reference Architecture, an associated set

of Security Components derived from the CSA TCI-RA, and a methodology for using the formal

model and the security components to orchestrate a secure cloud Ecosystem.

2.1 REVIEW OF THE FEDERAL CLOUD COMPUTING STRATEGY

In the Federal Cloud Computing Strategy published in 2011, U.S. Chief Information Officer Vivek

Kundra advises that Federal agencies “should make risk-based decisions which carefully consider

the readiness of commercial or government providers to fulfill their Federal needs. These can be

wide-ranging, but likely will include: security requirements, service and marketplace characteristics,

application readiness, government readiness, and program’s stage in the technology lifecycle” [12].

The approach to securing a cloud Ecosystem is intrinsically related to the cloud computing service

model (SaaS, PaaS, or IaaS) and to the deployment model (Public, Private, Hybrid, or Community)

that best fits the Consumer’s business missions and security requirements. As previously stated, for

each use case of data migrated to the cloud, it is necessary for the Consumer to evaluate the

particular security requirements in the specific cloud architectural context, and to map them to

proper security controls and practices in technical, operational, and management classes. Even

though the Cloud Security Reference Architecture inherits a rich body of knowledge of general

network security and information security, both in theory and in practice, it also addresses the

cloud-specific security requirements triggered by characteristics unique to the cloud, such as:

• Broad network access,

• Decreased visibility and control by consumers,

• Dynamic system boundaries and comingled roles/responsibilities between consumer and

provider,

• Multi-tenancy,

• Data residency,

• Measured service, and

• Significant increase in scale (on demand), dynamics (elasticity, cost optimization), and

complexity (automation, virtualization).

The above-listed cloud computing characteristics often present an agency with security risks that are

different from those in traditional information technology solutions. To preserve the pre-migration

security level of their data once it has been moved to the Cloud, agencies need the ability to identify

all cloud-specific risk-adjusted security controls or components in advance and request from the

cloud Providers through contractual means and SLAs that all Security Components are identified

and controls fully and accurately implemented.

Page 20

As introduced in Fig. 1 above, the NCC-SRA provides a formal model, a set of Security

Components, and a methodology for using this information to orchestrate a secure cloud Ecosystem.

The NCC-SRA formal model was derived from the NIST SP 500-292: NIST Cloud Computing

Reference Architecture, and is described in detail in Sec. 3.

The NCC-SRA also provides a set of Security Components deemed important in securing the data

and operations of a Cloud Computing Ecosystem. In defining this set, the document leverages the

CSA TCI-RA shown in Annex A. The set of Security Components and guidance on how to use

them for a particular cloud model is introduced in detail in Sec. 3.

The NCC-SRA is presented using a cloud Ecosystem that can be constructed employing all possible

combinations of the four deployment models with the three service models. These combinations

result in the following twelve instances of cloud architectures:

• Public IaaS, Public PaaS, Public SaaS;

• Private IaaS, Private PaaS, Private SaaS;

• Hybrid IaaS, Hybrid PaaS, Hybrid SaaS;

• Community IaaS, Community PaaS, and Community SaaS.

The NCC-SRA (the formal model, the set of Security Components and the methodology for

applying cloud-adapted Risk Management Framework) is agnostic with respect to cloud

deployment model, and its methodology can easily be applied to data pertaining to Private,

Community, or Hybrid clouds. For purposes of example, this document describes the approach

using a Public cloud deployment model because it best supports illustrative examples of all of the

NCC-SRA Security Components and security considerations.

The NCC-SRA introduces a risk-based approach to determine each cloud Actor’s responsibility for

implementing specific controls throughout the life cycle of the cloud Ecosystem. Specifically, for

each instance of the cloud Ecosystem, the Security Components are analyzed to identify the level of

involvement of each cloud Actor in implementing those components. The ultimate objective of this

document is to demystify the process of describing, identifying, categorizing, analyzing, and

selecting cloud-based services for the cloud Consumer seeking to determine which cloud service

offering most effectively addresses their cloud computing requirement(s) and supports their

business and mission-critical processes and services in the most secure and efficient manner.

Figure 2, below provides a graphical representation of the NCC-SRA three-dimensional approach

that leads to the twelve cloud instances for which data is collected, aggregated, and analyzed for

each cloud type.

剩余203页未读，继续阅读

vR搬砖人

粉丝: 0
资源: 3

"NIST SP 500-299云计算安全参考框架简介与重要性"

云计算安全框架.docx

NIST SP800-147：云计算决策指南与 BIOS 保护推荐

NIST SP 500-291 NIST Cloud Computing Standards Roadmap

行业分类-设备装置-用于云计算平台安全性的认证和授权方法.zip

NIST-SP-800-207-ZTA_final_中文版.zip

nist sp800-53

XACML与NGAC：基于ABAC的NIST SP 800-178数据服务应用权限控制比较

NIST SP800-53安全控制措施标准中英文版发布

云计算参考架构（NIST）（2011-9-8）（英文）.pdf

美国NIST云计算安全标准跟踪及研究

最新资源