Integrating formal analysis and design to preserve security properties

Proceedings of the 42nd Annual Hawaii International Conference on System Sciences, HICSS

Volumn , Issue , 2009, Pages

  Hassan, Riham ^a   Bohner, Shawn ^a   El Kassas, Sherif ^b   Hinchey, Michael ^c  

^a VIRGINIA POLYTECHNIC INSTITUTE AND STATE UNIVERSITY   (United States)

^b The American University in Cairo   (Egypt)

^c UNIVERSITY OF LIMERICK   (Ireland)

Author keywords

[No Author keywords available]

Indexed keywords

FORMAL ANALYSIS; NETWORK SYSTEMS; SECURE SYSTEMS; SECURITY DESIGNS; SECURITY PROPERTIES; SECURITY REQUIREMENTS; SECURITY VULNERABILITIES;

DESIGN; KNOWLEDGE ACQUISITION; REAL TIME SYSTEMS; SPECIFICATION LANGUAGES; SPECIFICATIONS;

FORMAL METHODS;

EID: 78650760435     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/HICSS.2009.267     Document Type: Conference Paper

References (16)

1. A. van Lamsweerde, "Elaborating Security Requirements by Construction of Intentional Anti-Models", Proc. ICSE'04: 26th Intl. Conf. on Software Engineering, May 2004.
2. Wilander, J. & Gustavsson, J., "Security requirements -A field study of current practice", Symposium on Requirement Engineering for Information Security (SREIS ' 2005), Paris, France, 2005.
3. CERT, http://www.cert.org/stats/cert-stats.html.
4. A. van Lamsweerde and E. Letier, "Handling Obstacles in Goal-Oriented Requirements Engineering", IEEE Transactions on Software Engineering, Special Issue on Exception Handling, Vol. 26 No. 10, Oct. 2000, 978-1005.
5. Lehman M. M. "On understanding Laws, evolution and conversation in the large program lifecycle.", Journal of Software & Systems, vol. 1, pp. 213 - 221, 1980.
6. Cimitile, A.; Fasolino, A.R.; Visaggio, G. "A Software Model for Impact Analysis: A Validation Experiment", Proceedings of the Sixth Working Conference on Reverse Engineering, Oct. 1999, pg. 212-222.
7. P.J. Fontaine, Goal-Oriented Elaboration of Security Requirements, M.S. Thesis, Dept. Computing Science, University of Louvain, June 2001.
8. Abdel-Moneim, Riham, et. al., "Goal-Oriented, B-Based, Formal Derivation of Security Design Specifications from Security Requirements", Symposium on Requirements Engineering for Information Security, Barcelona, Spain, 2008.
9. J. Viega and G. McGraw, Building Secure Software: How to Avoid Security Problems the Right Way, Addison-Wesley, 2001.
10. Massacci, Fabio, et. al., "Using a Security Requirements Engineering Methodology in Practice: The Compliance with The Italian Data Protection Legislation", Computer Standards & Interfaces, issue 27, pg. 445-455, 2005.
11. Cansell, Dominique and Méry, Dominique, "Foundations of the B Method", Proceedings of Computing and Informatics, vol. 22, pg. 1-31, 2003.
12. Sekerinski, Emil, et. al., "Program Development by Refinement: Case Studies Using the B Method", Springer, 1999.
13. Cimitile, A.; Fasolino, A.R.; Visaggio, G. "A Software Model for Impact Analysis: A Validation Experiment", Proceedings of the Sixth Working Conference on Reverse Engineering, Oct. 1999, pg. 212-222.
14. Bowen, J., and Hinchey, M., Application of Formal Methods, Prentice Hall, 1995
15. Stepney, Susan, Cooper, et. al., "An Electronic Purse Specification, Refinement, and Proof, Programming Research Group, Oxford University Computing Labarotory, England, July 2000.
16. Abrial, J.-R., The B Book: Assigning Programs to Meanings, Prentice-Hall.