Product Description

Keep black-hat hackers at bay with the tips and techniques in this entertaining, eye-opening book! Developers will learn how to padlock their applications throughout the entire development process—from designing secure applications to writing robust code that can withstand repeated attacks to testing applications for security flaws. Short, easily digested chapters reveal proven principles, strategies, and coding techniques. The authors—two battle-scarred veterans who have solved some of the industry’s toughest security problems—provide sample code in several languages. This edition includes updated information about threat modeling, designing a security process, international issues, file-system issues, adding privacy to applications, and performing security code reviews. It also includes enhanced coverage of buffer overruns, Microsoft® .NET security, and Microsoft ActiveX® development, plus practical checklists for developers, testers, and program managers.

Product Details

• Amazon Sales Rank: #244746 in Books
• Published on: 2002-12-01
• Original language: English
• Number of items: 1
• Binding: Paperback
• 798 pages

Customer Reviews

required reading
Some years ago i worked for a software house with over 30 developers, of which only one other had read the first edition of this book. I don't think that was uncommon. Few developers cared about application security in general terms, their encounters with security being an inconvenience that either 'broke' code or (often post-exploit) resulted in 'extra work' bug-fixing.
I use the past-tense, but i've really no evidence to suggest that things have changed all that much. Hopefully the wider distribution and publicity granted this second edition will help change that.
The book is organised into four major sections. The first provides background material that outlines the need to secure systems and techniques for designing secure systems. It is carefully written, appropriately illustrated and has only two very small code examples (one of which pseudo-code, the other a couple of lines of asp), making it good for photocopying and distribution to project managers...
The second and third sections provide the bulk of the book - secure coding techniques. As you'd expect buffer overruns, acls, least privilege, crypto, canonical mistakes, sql injection, cross site scripting, dos attacks, to name a few are all covered, and there are chapters on internalisation, sockets, rpc, and one - surprisingly small - on .net. I say surprisingly because a good part of the marketing for this book was that it was updated to cover .net, which it has - but not to the extent you'd think. if you're looking for an in-depth analysis of .net security, this work doesn't have it.
but it doesnt needs it - if there is one single message in the second and third sections it is that there is no replacement for responsible, informed programming regardless of the syntax or technology used. The chapter entitled 'All Input Is Evil' makes that point well, it - like the others - applies whether you use .net or not. The final section covers 'everything else' - testing, code reviews, installation, error messages, and a good - but brief - chapter on privacy and data security, and an excellent chapter on general good practises.
Part of what made the first edition a classic, to my mind, is that it addressed the security fundamentals *every* programmer on a microsoft platform should be aware of. after reading it i was in doubt of the importance of application security, the core principles, threats and coding countermeasures, and i went on to apply those in subsequent projects.
this edition builds, updates and expands on the first and is, simply, required reading. unlike many sequels, it does not disappoint.

From vuagely interested in security to a security convert
When I started to read this book, I was convinced that security was an issue, but that I could not do much more than have a good firewall between my users and my app... now I know that my code, and configuration & settings this side of the firewall (all within my control) can make a significant difference to the security of my solutions.

Everyone that codes, review code, design code, design solutions, every one that ever have valuable info on their hard disks should probably read this great book.

Mandatory
If you are a developer then this book is mandatory.

You do not realise the threats (from the desktop, the web, Intranet) until you read this book. Attacks come from everywhere.

Reading this together with "Code Complete 2" (Steve McConnell) will surely make you a better developer and your software safer, faster and more secure.

Imagine the consequences of a simple SQL injection attack or a cross site script attack on your customers. Your reputation, your job and your company are at risk. Its as simple as that. Getting a few copies of this for yourself and your colleagues makes sense.