A practical approach to security assessment

Proceedings New Security Paradigms Workshop

Volumn Part F129303, Issue , 1998, Pages 5-16

  Kienzle, Darrell M ^a   Wulf, William A ^b  

^a MITRE CORPORATION   (United States)

^b University of Virginia   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

CRYPTOGRAPHY; RISK ASSESSMENT; RISK PERCEPTION; SOFTWARE ENGINEERING; SPECIFICATIONS;

ANALYSIS TECHNIQUES; BUILDING SOFTWARES; CONVENTIONAL APPROACH; DEVELOPMENT PROCESS; SECURITY ASSESSMENT; SECURITY REQUIREMENTS; SOFTWARE DEVELOPMENT PROCESS; SPECIFICATION AND VERIFICATION;

SOFTWARE DESIGN;

EID: 35048902231     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/283699.283731     Document Type: Conference Paper

References (20)

1. Bowen, J., M. Hinchey, "Seven More Myths of Formal Methods", Oxford University Computing Lab, Technical Report PRG-TR-7-94, June 1994.
2. Boehm, B., "A Spiral Model of Software Development", IEEE Computer, May 1988, pp. 61-72.
3. Boswell, A., "Specification and Validation of a Security Policy Model", IEEE Transactions on Software Engineering, Vol. 21, No. 2, Feb. 1995, pp. 63-68.
4. Craigen, D., S. Gerhart, and T. Ralston, "Formal Methods Reality Check: Industrial Usage", IEEE Transactions on Software Engineering, Vol. 21, No. 2, Feb. 1995, pp. 90-98.
5. Cornwell, M., "A Software Engineering Approach to Designing Trustworthy Software", Proceedings of the IEEE Symposium on Security and Privacy, Oakland 1989, pp. 148-156.
6. DeMillo, R., R. Lipton, and A. Perlis, Social Processes and Proofs of Theorems and Programs, Communications of the ACM, Vol. 22, No. 5, May 1979, pp. 271-280.
7. Fetzer, J., "Program Verification: The Very Idea", Communications of the ACM, Vol. 31, No. 9, Sept. 1988.
8. Fraser, M., K. Kumar, and V. Vaishnavi, Strategies for Incorporating Formal Specifications in Software Development, Communications of the ACM, Vol. 37, No. 10, Oct. 1994, pp. 74-86.
9. th National Information Systems Security Conference, Baltimore Maryland, October 1996, pp. 410-419.
10. Hall, A., "Seven Myths of Formal Methods", IEEE Software, Vol. 7, No. 5, Sept. 1990.
11. Hayes, I., "Applying Formal Specification to Software Development in Industry", IEEE Transactions on Software Engineering, Vol. SE-11, No. 2, Feb. 1985, pp. 169-178.
12. Heninger, K, "Specifying Software Requirements for Complex Systems: New Techniques and their Application", IEEE Transactions on Software Engineering, Vol. SE-6, No. 1, Jan. 1980.
13. Henley, E. J. and H. Kumamoto, Designing for Reliability and Safety Control, Prentice-Hall, Inc., Englewood Cliffs, New Jersey, 1985, pp. 407-458.
14. Kemmerer, R. A., "Integrating Formal Methods into the Development Process", IEEE Software, Sept. 1990, pp. 37-50.
15. McCormick, N. J., Reliability and Risk Analysis, Academic Press, San Diego, California, 1981, pp. 154-228.
16. Pamas, D., P. Clements, "A Rational Design Process: How and Why to Fake It", IEEE Transactions on Software Engineering, Vol. SE-12, No. 2, Feb. 1986.
17. Roland, H. E. and B. Moriarty, System Safety Engineering and Management, John Wiley and Sons, New York, 1983, pp. 215-271.
18. Rushby, J., "Formal Methods and their Role in the Certification of Critical Systems", SRI-CSL-95-01, January 1995. http://www.csl.sri.com/csl-95-l.html
19. th National Information Systems Security Conference, Baltimore Maryland, October 1996, pp. 420-427.
20. Wulf, W. A., C. Wang, and D. M. Kienzle, "A New Model of Security for Distributed Systems", Proceedings of the New Paradigms in Security Workshop, Lake Arrowhead, California, 1996.