1996
DOI: 10.1002/j.2334-5837.1996.tb02124.x
|View full text |Cite
|
Sign up to set email alerts
|

Experience With the Systems Security Engineering Capability Maturity Model

Abstract: The Systems Security Engineering Capability Maturity Model (SSE-CMM) is a tool for appraising and improving an organization's security engineering practices, and for augmenting existing assurance methods. The SSE-CMM was developed through a government-industry collaboration involving the nation's leading providers of security systems, products, and services. It does not specify how a particular process should be performed, but identifies practices generally accepted by industry. The SSE-CMM can also be used to… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
5
0

Year Published

1997
1997
2023
2023

Publication Types

Select...
3
1

Relationship

1
3

Authors

Journals

citations
Cited by 4 publications
(5 citation statements)
references
References 2 publications
0
5
0
Order By: Relevance
“…This support is captured in a set of Common Features and Generic Practices for each level. Further details are in (SSE-CMM Project, 1996) and (Hefner, et al, 1996). An assessment against this model involves determining the appropriate capability level for each Process Area, forming a spectrum of capability across the domain.…”
Section: Figure 2 Domain Aspectmentioning
confidence: 99%
See 1 more Smart Citation
“…This support is captured in a set of Common Features and Generic Practices for each level. Further details are in (SSE-CMM Project, 1996) and (Hefner, et al, 1996). An assessment against this model involves determining the appropriate capability level for each Process Area, forming a spectrum of capability across the domain.…”
Section: Figure 2 Domain Aspectmentioning
confidence: 99%
“…This support is captured in a set of Common Features and Generic Practices for each level. Further details are in (SSE-CMM Project, 1996) and (Hefner, et al, 1996).…”
Section: Figure 2 Domain Aspectmentioning
confidence: 99%
“…Environmental, typical lifecycle-associated failure or human-induced (accidental or malicious) system degradation may be sources of adverse conditions. 2 While cybersecurity is widely understood in the Information Technology (IT) context, it is less understood in the control system context. For example, the malicious actor group that launched the ransomware attack on the Colonial Pipeline business system claimed the goal was monetary rather than creating problems in the physical systems.…”
Section: Introductionmentioning
confidence: 99%
“…Finally, Section 5 presents the conclusions and suggestions for future study. Research on the selection/evaluation of security tools and related issues are considerably few ( [5], [11], [15], [16]). Polk and Bassham [17] introduced a guide with criteria for judging the functionality, practicality, and convenience of anti-virus tools.…”
Section: ⅰ Introductionmentioning
confidence: 99%
“…Moreover, the objective of these evaluation schemes is often to produce an official certification for each specific security tool, making it difficult to evaluate and select among those which have similar levels of certification [7]. Others based on two aspects which are annual loss expected (ALE) and return on security investment (ROSI) to evaluate information security system ( [11], [15]). Recently, there is a new approach which uses security criteria and experts' estimations as the input data.…”
Section: ⅰ Introductionmentioning
confidence: 99%