-
Will software development be hit by a Cyclone?
[View Detail]
http://www.securityfocus.com/guest/9094
An overview of the Cyclone programming language as of Dec. 2001. Cyclone is a dialect of C that avoids common security issues (particularly the buffer overflow).
-
"A Programmers Checklist"
[View Detail]
http://www.aspalliance.com/chrisg/default.asp?article=1
A checklist with some basic things that web developers should ensure before deployment, originally intended for an ASP audience, but widely applicable.
-
Best Practices for Secure Development
[View Detail]
http://members.rogers.com/razvan.peteanu/best_prac_for_sec_dev4.pdf
Guidelines for secure program development. It's a somewhat cursory overview, so one should suppliment with one of the better introductory books.
-
Eavesdropping Risks of CRT Displays
[View Detail]
http://www.cl.cam.ac.uk/~mgk25/ieee02-optical.pdf
A discussion of how to eavesdrop on a CRT from a distance without using the Van Eck approach, even without direct line of site. This is a risk many system designers fail to consider. The widespread belief is that such attacks aren't practical, but they are.
-
Federal Agencies Tackle Software Security
[View Detail]
http://msnbc-cnet.com.com/2100-7348_3-5053545.html?tag=lh
"Five federal agencies, led by the U.S. Department of Energy, plan to discuss a new set of government contracting practices that hold software makers accountable for making their products more resistant to viruses and hackers. "
-
Fending Off Future Attacks by Reducing Attack Surface
[View Detail]
http://msdn.microsoft.com/library/en-us/dncode/html/secure02132003.asp
Michael Howard discusses why you should reduce the amount of code that is open to future attack by installing only the needed features of a product.
-
OWASP Top Ten Web Application Vulnerabilities
[View Detail]
http://www.owasp.org/documentation/topten
This is a high-level discussion of some of the major security issues affecting web applications.
-
Scrubbing Secrets in Memory + Cross-Site Scripting Remediation
[View Detail]
http://msdn.microsoft.com/library/en-us/dncode/html/secure10102002.asp
A description of problems with the traditional scrubbing of data in memory. Plus, a discussion of an Internet Explorer extension to cookies (HttpOnly) that mitigates cross-site scripting problems.
-
Secure Programming Techniques
[View Detail]
http://www.onlamp.com/pub/a/onlamp/excerpt/PUIS3_chap16/index3.html
An excerpt of the Secure Programming advice from the book Practical Unix & Internet Security. It's a good overview, but supplement it with dedicated references. The article has three parts, and the link is to the final part. Follow the links to the first two portions.
-
The Right Mentality Is Half the Battle
[View Detail]
http://www-106.ibm.com/developerworks/linux/library/l-sp1.html
An article aimed at getting developers into a good mindset for secure programming. The first article in a series written by David Wheeler and published by IBM's DeveloperWorks.
-
The Web Services Security Specification
[View Detail]
http://www-106.ibm.com/developerworks/library/ws-secure/
Extensions to SOAP messaging to provide message integrity, secrecy, etc.
-
Twelve Rules for developing more secure Java code
[View Detail]
http://www.javaworld.com/javaworld/jw-12-1998/jw-12-securityrules.html
A very high-level article of early tips for more secure Java programming. It is a good set of guidelines to keep in mind, but there are many practical worries one should have beyond what is covered in this article.
-
When XML Gets Ugly
[View Detail]
http://www.xml.com/pub/a/2000/02/xtech/megginson.html
Risks with XML over the web.