Software Assurance Using Structured Assurance Case Models.

Thomas Rhodes, Frederick Boland, Elizabeth Fong, Michael Kass
Author Information
  1. Thomas Rhodes: Software and Systems Division, Information Technology Laboratory, National Institute of Standards and Technology, Gaithersburg, MD 20899-8970.
  2. Frederick Boland: Software and Systems Division, Information Technology Laboratory, National Institute of Standards and Technology, Gaithersburg, MD 20899-8970.
  3. Elizabeth Fong: Software and Systems Division, Information Technology Laboratory, National Institute of Standards and Technology, Gaithersburg, MD 20899-8970.
  4. Michael Kass: Software and Systems Division, Information Technology Laboratory, National Institute of Standards and Technology, Gaithersburg, MD 20899-8970.

Abstract

Software assurance is an important part of the software development process to reduce risks and ensure that the software is dependable and trustworthy. Software defects and weaknesses can often lead to software errors and failures and to exploitation by malicious users. Testing, certification and accreditation have been traditionally used in the software assurance process to attempt to improve software trustworthiness. In this paper, we examine a methodology known as a structured assurance model, which has been widely used for assuring system safety, for its potential application to software assurance. We describe the structured assurance model and examine its application and use for software assurance. We identify strengths and weaknesses of this approach and suggest areas for further investigation and testing.

Keywords

Word Cloud

Created with Highcharts 10.0.0assurancesoftwarestructuredmodelSoftwareprocessweaknessesusedexamineapplicationAssurancecaseimportantpartdevelopmentreducerisksensuredependabletrustworthydefectscanoftenleaderrorsfailuresexploitationmalicioususersTestingcertificationaccreditationtraditionallyattemptimprovetrustworthinesspapermethodologyknownwidelyassuringsystemsafetypotentialdescribeuseidentifystrengthsapproachsuggestareasinvestigationtestingUsingStructuredCaseModelsproductsecurity

Similar Articles

Cited By (1)