2014
DOI: 10.1016/j.procs.2014.03.049
|View full text |Cite
|
Sign up to set email alerts
|

The Value Proposition for Assurance of JPL Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2014
2014
2023
2023

Publication Types

Select...
3
1
1

Relationship

1
4

Authors

Journals

citations
Cited by 6 publications
(1 citation statement)
references
References 1 publication
0
1
0
Order By: Relevance
“…For example, a category such as "Buffer overflow" represents different CWE entries that describe the type of buffer overflow (e.g., CWE-121 Stack-based buffer overflow, CWE-190 Integer overflow, etc). Therefore, we used security model categories in accordance with the "Center for Assured Software 2011" to generate a security model as part of a more general software quality model [35]. This security model facilitates interpretation of the Juliet test set results and thereby provides a connection between generic descriptions of software security attributes and specific software analysis approaches.…”
Section: Empirical Evaluation Of the Test-suitementioning
confidence: 99%
“…For example, a category such as "Buffer overflow" represents different CWE entries that describe the type of buffer overflow (e.g., CWE-121 Stack-based buffer overflow, CWE-190 Integer overflow, etc). Therefore, we used security model categories in accordance with the "Center for Assured Software 2011" to generate a security model as part of a more general software quality model [35]. This security model facilitates interpretation of the Juliet test set results and thereby provides a connection between generic descriptions of software security attributes and specific software analysis approaches.…”
Section: Empirical Evaluation Of the Test-suitementioning
confidence: 99%