Security threat modeling and analysis: A goal-oriented approach

Proceedings of the 10th IASTED International Conference on Software Engineering and Applications, SEA 2006

Volumn , Issue , 2006, Pages 178-185

  Oladimeji, Ebenezer A ^a   Supakkul, Sam ^b   Chung, Lawrence ^b  

^a IT Verizon Communications   (United States)

^b The University of Texas at Dallas   (United States)

Author keywords

Inverse contributions; Negative softgoal; Security requirements engineering; Software security; Threat modeling

Indexed keywords

COMPUTER CRIME; COMPUTER SIMULATION; OBJECT ORIENTED PROGRAMMING; SOFTWARE ENGINEERING;

INVERSE CONTRIBUTIONS; NEGATIVE SOFTGOAL; SECURITY REQUIREMENTS ENGINEERING; SOFTWARE SECURITY; THREAT MODELING;

SECURITY OF DATA;

EID: 38049161526     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (31)

1. C. J. Alberts, S. G. Behrens, R. D. Pethia, and W. R. Wilson. Operationally critical threat, asset, and vulnerability evaluation (octave) framework. Technical Report CMU/SEI-99-TR-017, SEL Carnegie Mellon University, May 2005.
2. A. I. Antonn and C. Potts. The use of goals to surface requirements for evolving systems. In Proc. of the Inter'l Conference on Software Engineering (ICSE '98), Kyoto, Japan, 1998.
3. M. Bishop. Computer Security: Art and Science. Addison-Wesley, 2002.
4. L. Chung. Dealing with security requirements during the development of information systems. In Proceedings of 5th Int. Conference on Advanced Information Systems Engineering (CAiSE), June 1993.
5. L. Chung, B. A. Nixon, E. Yu, and J. Mylopolos. Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers, 2000.
6. R. Crook, D. Ince, L. Lin, and B. Nuseibeh. Security requirements engineering: When anti-requirements hit the fan. In Proceedings of IEEE Int'l Requirements Engineering Conference (RE'02), 2002.
7. A. Dardenne, A. van Lamsweerde, and S. Fickas. Goal-directed requirements acquisition. Science of Computer Programming, 20(1-2):3-50, 1993.
8. F. den Braber, M. S. Lund, K. Stølen, and F. Vraalsen. Integrating security in the development process with UML. In Encyclopedia of Information Science and Technology (III), pages 1560-1566, 2005.
9. J. A. Goguen and C. Linde. Techniques for requirements elicitation. In Proc. of the IEEE Int. Symposium on Requirements Engineering, pages 152-164, Los Alamitos, CA, Jan. 1993.
10. M. Howard and D. LeBlane. Writing Secure Code. Microsoft Press, 2nd edition, 2002.
11. J. Jrjens. UMLsec: Extending UML for secure systems development. UML 2002, LNCS 2460, Springer-Verlag, 2002.
12. M. Keeney, E. Kowalski, D. Cappelli, A. Moore, T. Shimeall, and S. Rogers. Insider threat study: Computer system sabotage in critical infrastructure sectors. Technical report. Software Eng. Institute, Carnegie Mellon University, May 2005.
13. C. E. Landwehr, A. R. Bull, J. P. McDermott, and W. S. Choi. A taxonomy of computer program security flaws, with examples. Technical Report NRL/FR/5542-93-9591, Naval Research Laboratory, Washington, DC, Nov. 1993.
14. L. Liu, E. Yu, and J. Mylopoulos. Security and privacy requirements analysis within a social setting. In Proceedings 11th IEEE International Requirements Engineering Conference (RE'03), pages 151-161. IEEE Press, Sept. 2003.
15. T. Lodderstedt, D. Basin, and J. Doser. SecureUML: A UML-based modeling language for model-driven security. UML 2002, LNCS 2460, Springer-Verlag, pages 426-441, 2002.
16. P. G. F. Massacci, J. Mylopoulos, and N. Zannone. Requirements engineering meets trust management: Model, methodology, and reasoning. In Proceedings of iTrust'04, LNCS 2995, pages 176-190, 2004.
17. P. G. F. Massacci, J. Mylopoulos, and N. Zannone. Modeling security requirements through ownership, permission and delegation. In Proc. of 13th IEEE International Conference on Requirements Engineering (RE'05), Aug./Sept. 2005.
18. J. P. McDermott and C. Fox. Using abuse case models for security requirements analysis. In Proc. of the 15th IEEE Annual Computer Security Applications Conference (ACSAC'99), pages 55-67, Phoenix, 1999. IEEE CS Press.
19. A. P. Moore, R. J. Ellison, and R. C. Linger. Attack modeling for information security and survivability. Technical Report CMU/SEI-2001-TN-OOT, Software Engineering Institute, Carnegie Mellon University, March 2001.
20. S. Myagmar, A. Lee, and W. Yurcik. Threat modeling as a basis for security requirements. In Proceedings of the Symposium on Requirements Engineering for Information Security (SREIS'05), Paris, France, Aug. 2005.
21. NIST Software errors costs U.S. economy $59.5 billion annually. Technical Report NIST 2002-10, National Institute of Standards and Technology, June 2002.
22. J. Rushby. Security requirements specifications: How and what. In Proceedings of the IEEE Symposium on Requirements Engineering for Information Security (SREIS'01), Indianapolis, March 2001.
23. B. Schneier. Attack trees: Modeling security threats. Dr. Dobbs Journal, pages 21-29, December 1999.
24. G. Sindre and A. L. Opdahl. Eliciting security requirements with misuse cases. Requirements Engineering, 10(1):34-44, January 2005.
25. A. Sutcliffe. Scenario-based requirements analysis. Requirements Engineering, 3(1):48-65, 1995.
26. F. Swiderski and W. Snyder. Threat Modeling. Microsoft Press, 2004.
27. H. H. Thompson. Application penetration testing. IEEE Security and Privacy, 03(1):66-69, 2005.
28. P. Torr. Demystifying the threat-modeling process. IEEE Security and Privacy, 03(5):66-70, Sept/Oct 2005.
29. A. van Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour. In Proceedings of the 5th IEEE Inter'I Symposium on Requirements Engineering (RE'01), pages 249-263, Toronto, Canada, 2001.
30. A. van Lamsweerde. Goal-oriented requirements engineering: A roundtrip from research to practice, invited keynote paper. In Proc. of the I2th IEEE Joint Inter'l Requirements Engineering Conference (RE'04), pages 4-8, Kyoto, Sept. 2004.
31. A. van Lamsweerde, S. Brohez, R. D. Landtsheer, and D. Janssens. From system goals to intruder Anti-Goals: Attack generation and resolution for security requirements engineering. In Proc. of the Workshop on Requirements for High Assurance Systems (RHAS'03), Monterey (CA), Sept. 2003.