Haley, Charles B; Laney, Robin; Moffett, Jonathan D and Nuseibeh, Bashar
|Google Scholar:||Look up in Google Scholar|
When considering the security of a system, the analyst must simultaneously work with two types of properties: those that can be shown to be true, and those that must be argued as being true. The first consists of properties that can be demonstrated conclusively, such as the type of encryption in use or the existence of an authentication scheme. The second consists of things that cannot be so demonstrated but must be considered true for a system to be secure, such as the trustworthiness of a public key infrastructure or the willingness of people to keep their passwords secure. The choices represented by the second case are called trust assumptions, and the analyst should supply arguments explaining why the trust assumptions are valid.
The chapter will present a process for security requirements elicitation and analysis, based around the construction of a satisfaction argument for the security of a system. The process starts with the enumeration of security goals based on assets in the system, then uses these goals to derive security requirements in the form of constraints. The satisfaction argument is then constructed using a problem-centered representation, a formal proof to analyze properties that can be demonstrated, and structured informal argumentation of the trust assumptions exposed during construction of the argument.
|Item Type:||Book Chapter|
|Copyright Holders:||2008 Information Science Reference|
|Academic Unit/Department:||Faculty of Science, Technology, Engineering and Mathematics (STEM) > Computing and Communications
Faculty of Science, Technology, Engineering and Mathematics (STEM)
|Interdisciplinary Research Centre:||Centre for Research in Computing (CRC)
Centre for Policing Research and Learning (CPRL)
|Depositing User:||Charles Haley|
|Date Deposited:||02 Dec 2009 15:30|
|Last Modified:||04 Oct 2016 10:29|
|Share this page:|