Why security testing is hard

IEEE Security and Privacy

Volumn 1, Issue 4, 2003, Pages 83-86

  Thompson, Herbert H ^a,b  

^a Security Innovation ^*  (Italy)

^b Security Innovation

Author keywords

[No Author keywords available]

Indexed keywords

PASSWORDS; SECURITY TESTING; SERVER SECURITY; UNIFIED MODELING LANGUAGE (UML);

CODES (SYMBOLS); COMPUTER PROGRAMMING LANGUAGES; COMPUTER SOFTWARE; DATA REDUCTION; DIGITAL LIBRARIES; INTERNET; SERVERS; WEB BROWSERS;

SECURITY OF DATA;

EID: 3042823607     PISSN: 15407993     EISSN: None     Source Type: Journal    
DOI: 10.1109/MSECP.2003.1219078     Document Type: Review

References (4)

1. J. Whittaker and H. Thompson, How to Break Software Security, Addison-Wesley, 2003.
2. H. Thompson, J. Whittaker, and F. Mottay, "Software Security Vulnerability Testing in Hostile Environments," Proc. 2002 ACM Software Applications Conf. (ACM-SAC 02), ACM Press, 2002, pp. 260-264.
3. M. Bishop, "Vulnerabilities Analysis," Proc. 2nd Int'l Symp. Recent Advances in Intrusion Detection (RAID 99), 1999, pp. 125-136.
4. T. Dyes, "Tracking Severity: Assessing and Classifying the Impact of Issues (a.k.a. Defects)," Software Test and Quality Engineering Magazine, vol. 1, no. 2, March/April 1999, pp. 43-46.