Security Requirements for the Prevention of Modern Software Vulnerabilities and a Process for Incorporation into Classic Software Development Lifecycles

dc.contributor.authorClagett II, Lee Manningen
dc.contributor.committeechairArthur, James D.en
dc.contributor.committeememberMarchany, Randolph C.en
dc.contributor.committeememberBalci, Osmanen
dc.contributor.departmentComputer Scienceen
dc.date.accessioned2014-03-14T20:50:12Zen
dc.date.adate2010-01-06en
dc.date.available2014-03-14T20:50:12Zen
dc.date.issued2009-12-14en
dc.date.rdate2010-01-06en
dc.date.sdate2009-12-17en
dc.description.abstractSoftware vulnerabilities and their associated exploits have been increasing over the last several years - this research attempts to reverse that trend. Currently, security experts recommend that concerns for security start at the earliest stage possible, generally during the requirements engineering phase. Having a set of security requirements enables the production of a secure design, and product implementation. Approaches for creating security requirements exist, but all have a similar limitation - a security expert is required. This research provides a set of software security requirements that mitigate the introduction of software vulnerabilities, and reduces the need for security expertise. The security requirements can be implemented by software engineers with limited security experience, and be used with any computer language or operating system. Additionally, a tree structure, called the software security requirements tree (SSRT), is provided to support security requirement selection, based on project characteristics. A graphical interface for the SSRT is provided through a prototype Java tool, to support the identification and selection of appropriate software security requirements. This research also provides a set of security artifacts to support a comprehensive verification, validation, and testing (VV&T) strategy. Those artifacts are generic, and represent design and implementation elements reflecting software security requirements. The security artifacts are used in verification strategies to confirm their necessity and existence in the actual design and implementation products.en
dc.description.degreeMaster of Scienceen
dc.identifier.otheretd-12172009-231623en
dc.identifier.sourceurlhttp://scholar.lib.vt.edu/theses/available/etd-12172009-231623/en
dc.identifier.urihttp://hdl.handle.net/10919/36244en
dc.language.isoenen
dc.publisherVirginia Techen
dc.relation.haspartClagett_LM_T_2009.pdfen
dc.rightsIn Copyrighten
dc.rights.urihttp://rightsstatements.org/vocab/InC/1.0/en
dc.subjectAccess Driven VV&Ten
dc.subjectAssumptionsen
dc.subjectConstraintsen
dc.subjectRequirementsen
dc.subjectVulnerabilitiesen
dc.subjectSoftware Securityen
dc.titleSecurity Requirements for the Prevention of Modern Software Vulnerabilities and a Process for Incorporation into Classic Software Development Lifecyclesen
dc.typeThesisen
thesis.degree.disciplineComputer Scienceen
thesis.degree.grantorVirginia Polytechnic Institute and State Universityen
thesis.degree.levelmastersen
thesis.degree.nameMaster of Scienceen

Files

Original bundle
Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
Clagett_LM_T_2009.pdf
Size:
2.38 MB
Format:
Adobe Portable Document Format

Collections