系统安全工程能力成熟度模型SSE-CMMv3.0

(面向)系统安全工程能力的成熟度模型

需积分: 9 102 浏览量更新于2024-08-02 收藏 1022KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"ssecmmv3final" 是关于 "系统安全工程能力成熟度模型（SSE-CMM）项目" 的第三版文档，该模型用于评估和改进组织在系统安全工程领域的成熟度。该模型的版权归属于1995年的卡内基梅隆大学，由多个机构合作开发，包括休斯空间与通信、休斯电信和空间、洛克希德马丁、软件工程研究所、软件生产力联盟以及德州仪器公司。允许无版税复制和基于此产品创建衍生作品，但需包含版权信息。 SSE-CMM 是一个旨在提升系统安全工程能力的框架，它描述了从初始级到优化级的五个成熟度级别，每个级别代表了一组更高级别的过程管理和实践。以下是模型的五个级别及其核心概念： 1. 初始级：在这个级别，过程通常是随机的，依赖于个人的努力。组织缺乏系统的安全工程实践，可能导致不一致的结果。 2. 受管理级：组织开始定义和管理安全工程过程，这些过程是可重复的，但可能因项目而异。目标是提高过程的一致性和可靠性。 3. 定义级：在这一级，组织建立了标准化的安全工程过程，并将其集成到整个系统工程过程中。这些过程被详细记录并形成组织的标准实践。 4. 量化管理级：在这个阶段，组织使用量化数据来度量和控制安全工程过程，以实现更高的效率和效果。这包括对过程性能的统计控制和预测。 5. 优化级：最高级别，组织持续改进其安全工程过程，基于数据驱动的决策和创新方法来优化过程，减少浪费，提高质量和安全性。 SSE-CMM 模型描述文档版本3.0发布于2003年6月15日，强调了系统安全工程的重要性，特别是在复杂系统开发中的角色。该模型不仅关注技术实施，还关注过程改进、组织文化和人员培训，以确保安全成为系统工程的内在部分。通过采用SSE-CMM，组织可以系统地评估其安全工程能力，识别弱点，制定改进计划，从而提高整体安全性，降低风险，满足法规要求，并增强客户信任。此外，SSE-CMM 提供了一个通用的语言和基准，使得不同组织之间可以比较和交流其安全工程实践，促进了行业的最佳实践分享和标准的统一。

资源详情

资源推荐

Systems Security Engineering Capability Maturity Model 3.0

- 2 -

The SSE-CMM® has a relationship to ISO/IEC TR 15504, Information technology — Software

process assessment, particularly part 2, A reference model for processes and process capability, as

both are concerned with process improvement and capability maturity assessment. However, TR

15504 is specifically focussed on software processes, whereas the SSE-CMM is focussed on

security.

The SSE-CMM® has a closer relationship with the new versions of 15504, particularly CD

15504-2, and is compatible with its approaches and requirements.

Why Was the SSE-CMM Developed?

Both customers and suppliers are interested in improving the development of security products,

systems, and services. The field of security engineering has several generally accepted principles,

but it currently lacks a comprehensive framework for evaluating security engineering practices.

The SSE-CMM, by identifying such a framework, provides a way to measure and improve

performance in the application of security engineering principles.

It must be stressed that security engineering is a unique discipline, requiring unique knowledge,

skills, and processes which warrants the development of a distinct CMM for security engineering.

This does not conflict with the premise that security engineering is done in context with systems

engineering. In fact, having well-defined and accepted systems engineering activities will allow

security engineering to be practiced effectively in all contexts.

Modern statistical process control suggests that higher quality products can be produced more

cost-effectively by emphasizing the quality of the processes that produce them, and the maturity

of the organizational practices inherent in those processes. More efficient processes are

warranted, given the increasing cost and time required for the development of secure systems and

trusted products. The operation and maintenance of secure systems relies on the processes that

link the people and technologies. These interdependencies can be managed more cost effectively

by emphasizing the quality of the processes being used, and the maturity of the organizational

practices inherent in the processes.

The objective of the SSE-CMM Project is to advance security engineering as a defined, mature,

and measurable discipline. The SSE-CMM model and appraisal methods are being developed to

enable:

• Focused investments in security engineering tools, training, process definition,

management practices, and improvements by engineering groups

• Capability-based assurance, that is, trustworthiness based on confidence in the

maturity of an engineering group’s security practices and processes

• Selection of appropriately qualified providers of security engineering through

differentiating bidders by capability levels and associated programmatic risks

Systems Security Engineering Capability Maturity Model 3.0

- 3 -

Why Is Security Engineering Important?

With the increasing reliance of society on information, the protection of that information is

becoming increasingly important. Many products, systems, and services are needed to maintain

and protect information. The focus of security engineering has expanded from one primarily

concerned with safeguarding classified government data to broader applications including

financial transactions, contractual agreements, personal information, and the Internet. These

trends have elevated the importance of security engineering.

What Is the Scope of the SSE-CMM?

The scope of the SSE-CMM encompasses the following:

• The SSE-CMM addresses security engineering activities that span the entire

trusted product or secure system life cycle, including concept definition,

requirements analysis, design, development, integration, installation, operations,

maintenance, and decommissioning.

• The SSE-CMM applies to secure product developers, secure system developers

and integrators, and organizations that provide security services and security

engineering.

• The SSE-CMM applies to all types and sizes of security engineering

organizations, such as commercial, government, and academic.

While the SSE-CMM is a distinct model to improve and assess security engineering capability,

this should not imply that security engineering should be practiced in isolation from other

engineering disciplines. On the contrary, the SSE-CMM promotes such integration, taking the

view that security is pervasive across all engineering disciplines (e.g., systems, software,

hardware, and human factors) and defining components of the model to address such concerns.

The Common Feature “Coordinate Security Practices” recognizes the need to integrate security

with all disciplines and groups involved on a project or within an organization. Similarly, the

Process Area “Coordinate Security” defines the objectives and mechanisms to be used in

coordinating the security engineering activities.

Who Does the SSE-CMM Apply To?

A wide variety of organizations practice security engineering in the development of computer

programs, whether as operating systems software, security managing and enforcing functions,

software, middleware of applications programs. Appropriate methods and practices are therefore

required by product developers, service providers, system integrators, system administrators, and

even security specialists. Some of these organizations deal with high-level issues (e.g., ones

dealing with operational use or system architecture), others focus on low-level issues (e.g.,

mechanism selection or design), and some do both. Organizations may specialize in a particular

type of technology, or a specialized context (e.g. at sea).

Systems Security Engineering Capability Maturity Model 3.0

- 4 -

The SSE-CMM is designed for all these organizations. Use of the SSE-CMM should not imply

that one focus is better than another is or that any of these uses are required. An organization’s

business focus need not be biased by use of the SSE-CMM.

Based on the focus of the organization, some, but not all, of the security engineering practices

defined will apply. In addition, the organization may need to look at relationships between

different practices within the model to determine their applicability.

The examples below illustrate ways in which the SSE-CMM® may be applied to software,

systems, facilities development and operation by a variety of different organizations.

Security Service Providers

To measure the process capability of an organization that performs risk assessments, several

groups of practices come into play. During system development or integration, one would need to

assess the organization with regard to its ability to determine and analyze security vulnerabilities

and assess the operational impacts. In the operational case, one would need to assess the

organization with regard to its ability to monitor the security posture of the system, identify and

analyze security vulnerabilities, and assess the operational impacts.

Countermeasure Developers

In the case of a group that focuses on the development of countermeasures, the process capability

of an organization would be characterized by a combination of SSE-CMM practices. The model

contains practices to address determining and analyzing security vulnerabilities, assessing

operational impacts, and providing input and guidance to other groups involved (such as a

software group). The group that provides the service of developing countermeasures needs to

understand the relationships between these practices.

Product Developers

The SSE-CMM includes practices that focus on gaining an understanding of the customer’s

security needs. Interaction with the customer is required to ascertain them. In the case of a

product, the customer is generic as the product is developed a priori independent of a specific

customer. When this is the case, the product marketing group or another group can be used as the

hypothetical customer, if one is required.

Practitioners in security engineering recognize that the product contexts and the methods used to

accomplish product development are as varied as the products themselves. However, there are

some issues related to product and project context that are known to have an impact on the way

products are conceived, produced, delivered, and maintained. The following issues in particular

have significance for the SSE-CMM:

• Type of customer base (products, systems, or services)

• Assurance requirements (high vs. low)

• Support for both development and operational organizations

Systems Security Engineering Capability Maturity Model 3.0

- 5 -

The differences between two diverse customer bases, differing degrees of assurance

requirements, and the impacts of each of these differences in the SSE-CMM are discussed below.

These are provided as an example of how an organization or industry segment might determine

appropriate use of the SSE-CMM in their environment.

Specific Industry Segments

Every industry reflects its own particular culture, terminology, and communication style. By

minimizing the role dependencies and organization structure implications, it is anticipated that the

SSE-CMM concepts can be easily translated by all industry segments into their own language and

culture.

How Should the SSE-CMM Be Used?

The SSE-CMM and the method for applying the model (i.e., appraisal method) are intended to be

used as a:

• Tool for engineering organizations to evaluate their security engineering

practices and define improvements to them,

• Method by which security engineering evaluation organizations such as certifiers

and evaluators can establish confidence in the organizational capability as one

input to system or product security assurance,

• Standard mechanism for customers to evaluate a provider’s security engineering

capability.

The appraisal techniques can be used in applying the model for self improvement and in selecting

suppliers, if the users of the model and appraisal methods thoroughly understand the proper

application of the model and its inherent limitations. The appraisal process is outlined in Chapter

4. Further description of the appraisal method is documented in the SSE-CMM Appraisal Method

Description [SSECMM97].

Additional Information

Questions, further information, or contacts concerning this model or pilot appraisals using this

model can be referred to the SSE-CMM Web Site http://www.sse-cmm.org.

Data Rights Associated with the SSE-CMM

The members of the SSE-CMM Project are committed to free use of project materials by the

systems engineering, and security engineering communities. Participants have agreed that this

and future versions of this document, when released to the public, will retain the concept of free

access via a permissive copyright notice. Permission to reproduce this work and to prepare

derivative works from this product is granted royalty-free, provided the copyright is included with

all reproductions and derivative works.

Systems Security Engineering Capability Maturity Model 3.0

- 6 -

1.2 Benefits of Using the SSE-CMM

The trend for security is a shift from protecting classified government data to a broader spectrum

of concerns including financial transactions, contractual agreements, personal information, and

the Internet. A corresponding proliferation of products, systems, and services that maintain and

protect information has emerged. These security products and systems typically come to market

in one of two ways: through lengthy and expensive evaluation or without evaluation. In the

former case, trusted products often reach the market long after their features are needed and

secure systems are being deployed that no longer address current threats. In the latter, acquirers

and users must rely solely on the security claims of the product or system developer or operator.

Further, security engineering services traditionally were often marketed on this caveat emptor

basis.

This situation calls for organizations to practice security engineering in a more mature manner.

Specifically, the following qualities are needed in the production and operation of secure systems

and trusted products:

• Continuity – knowledge acquired in previous efforts is used in future efforts

• Repeatability – a way to ensure that projects can repeat a successful effort

• Efficiency – a way to help both developers and evaluators work more efficiently

• Assurance – confidence that security needs are being addressed

To provide for these requirements, a mechanism is needed to guide organizations in

understanding and improving their security engineering practices. To address these needs, the

SSE-CMM is being developed to advance the state of the practice of security engineering with

the goal of improving the quality and availability of and reducing the cost of delivering secure

systems, trusted products, and security engineering services. In particular, the following benefits

are envisioned:

To Engineering Organizations

Engineering organizations include System Integrators, Application Developers, Product Vendors,

and Service Providers. Benefits of the SSE-CMM to these organizations include:

• Savings with less rework from repeatable, predictable processes and practices

• Credit for true capability to perform, particularly in source selections

• Focus on measured organizational competency (maturity) and improvements

To Acquiring Organizations

Acquirers include organizations acquiring systems, products, and services from external/internal

sources and end users. Benefits of the SSE-CMM to these organizations include:

• Reusable standard Request for Proposal language and evaluation means

剩余339页未读，继续阅读

moonpluto

粉丝: 1
资源: 32

系统安全工程能力成熟度模型SSE-CMMv3.0

机动车整车出厂合格证管理信息系统二次开发套件SDK和Demo----VB程序

BT3 各种版本下载地址 （BackTrack_3_Final）

static final和final的区别

static、static final、final的区别

Java中静态成员变量加上final和不加final有什么区别

final关键字理解与使用

final String type = "动作片"; static final String rank = "A";final 的用法是什么

Variable used in lambda expression should be final or effectively final)

Variable used in lambda expression should be final or effectively final 如何解决

final关键字底层原理

static和static final区别

java中的final

variable used in lambda expression should be final or effectively final

Variable used in lambda expression should be final or effectively final该如何解决

最新资源

BT3 各种版本下载地址（BackTrack_3_Final）