Using trust assumptions with security requirements.
Saved in:
| Title: | Using trust assumptions with security requirements. |
|---|---|
| Authors: | Haley, Charles1 C.B.Haley@open.ac.uk, Laney, Robin1 R.C.Laney@open.ac.uk, Moffett, Jonathan1 J.Moffett@open.ac.uk, Nuseibeh, Bashar1 B.Nuseibeh@open.ac.uk |
| Source: | Requirements Engineering. May2006, Vol. 11 Issue 2, p138-151. 14p. 9 Diagrams. |
| Subjects: | Computer security standards, Computer software development, Information technology, Computer systems, System analysis, Human-computer interaction |
| Abstract: | Assumptions are frequently made during requirements analysis of a system about the trustworthiness of its various components (including human components). These trust assumptions, whether implicit or explicit, affect the scope of the analysis, derivation of security requirements, and in some cases how functionality is realized. This paper presents trust assumptions in the context of analysis of security requirements. A running example shows how trust assumptions can be used by a requirements engineer to help define and limit the scope of analysis and to document the decisions made during the process. The paper concludes with a case study examining the impact of trust assumptions on software that uses the secure electronic transaction specification. [ABSTRACT FROM AUTHOR] |
| Copyright of Requirements Engineering is the property of Springer Nature and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.) | |
| Database: | Engineering Source |
Be the first to leave a comment!
