On bricks and walls: Why building secure software is hard

Computers and Security

Volumn 21, Issue 3, 2002, Pages 229-238

  McGraw, Gary ^a  

^a Cigital   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER ARCHITECTURE; COMPUTER NETWORKS; COMPUTER SOFTWARE; COMPUTER SYSTEM FIREWALLS; CRYPTOGRAPHY; DATA PRIVACY; ELECTRONIC COMMERCE; INTERFACES (COMPUTER); INTERNET; PERSONAL COMPUTERS; RISK ASSESSMENT; RISK MANAGEMENT;

ELECTRONIC BUSINESS; INTERNET SOFTWARE; SOFTWARE SECURITY;

SECURITY OF DATA;

EID: 0036273351     PISSN: 01674048     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0167-4048(02)00305-X     Document Type: Note

References (13)

1. Windows of vulnerability: A case study analysis
2. Checking for race conditions in file access
3. Stackguard: Automatic adaptive detection and prevention of buffer-overflow attacks
4. Testing for security during development: Why we should scrap penetrate-and-patch
5. Software assurance for security
6. Securing Java: Getting down to business with mobile code
7. Attacking malicious code: A report to the Infosec Research Council
8. ITS4: A static vulnerability scanner for C and C++ code
9. A first step towards automated detection of buffer overrun vulnerabilities
10. A case study in detecting security vulnerabilities using constraint optimization