Buy new:
$24.75$24.75
Delivery Monday, July 29
Ships from: Amazon Sold by: RuhiCan Store
Save with Used - Good
$19.26$19.26
Delivery Friday, July 26
Ships from: Amazon Sold by: Martistore
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Follow the authors
OK
Writing Secure Code, Second Edition 2nd ed. Edition
Purchase options and add-ons
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. 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.
- ISBN-100735617228
- ISBN-13978-0735617223
- Edition2nd ed.
- PublisherMicrosoft Press
- Publication dateJanuary 4, 2003
- LanguageEnglish
- Dimensions7.5 x 2 x 9 inches
- Print length798 pages
Frequently bought together

Customers who bought this item also bought
Code Complete: A Practical Handbook of Software Construction, Second EditionPaperback$21.67 shippingOnly 1 left in stock (more on the way).
The Pragmatic Programmer: Your Journey To Mastery, 20th Anniversary Edition (2nd Edition)David ThomasHardcover$17.57 shipping
Designing Secure Software: A Guide for DevelopersPaperback$16.55 shippingOnly 19 left in stock (more on the way).
Editorial Reviews
About the Author
Michael Howard, CISSP, is a leading security expert. He is a senior security program manager at Microsoft® and the coauthor of The Software Security Development Lifecycle. Michael has worked on Windows security since 1992 and now focuses on secure design, programming, and testing techniques. He is the consulting editor for the Secure Software Development Series of books by Microsoft Press.
David LeBlanc, Ph.D., is a founding member of the Trustworthy Computing Initiative at Microsoft®. He has been developing solutions for computing security issues since 1992 and has created award-winning tools for assessing network security and uncovering security vulnerabilities. David is a senior developer in the Microsoft Office Trustworthy Computing group.
Product details
- Publisher : Microsoft Press; 2nd ed. edition (January 4, 2003)
- Language : English
- Paperback : 798 pages
- ISBN-10 : 0735617228
- ISBN-13 : 978-0735617223
- Item Weight : 2.92 pounds
- Dimensions : 7.5 x 2 x 9 inches
- Best Sellers Rank: #879,544 in Books (See Top 100 in Books)
- #1,099 in Software Development (Books)
- #2,741 in Computer Software (Books)
- #8,316 in Mathematics (Books)
- Customer Reviews:
About the authors

Discover more of the author’s books, see similar authors, read author blogs and more

Discover more of the author’s books, see similar authors, read author blogs and more
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
The book starts rather philosophically and for any one who read Steve Maguire's book this might seem like a bit boring. But the real meat wont come until the part 2 where the author takes straight dive into the coding with lots of examples. Some of the web related examples deserve double clapping just for the effort the examples are bringing out the case of bad-news. This got to open up any programmer's eye and any managers mouth (in shock! that is).
The author takes us mostly into the world of Windows and C/C++ and some what into .NET and managed code behavior and security lapses one can get easily into.
While I enjoyed this book thoroughly, I just could not give it 5 stars because of its bia towards Windows and .NET framework. This can be accompanied with Steve Maguire's excellent book on Writing Solid "C" Code.
For an expert this book only offers few bits of additional information. This might be the case as the author tried to address many facets of programming and didn't concentrate on one subject alone. Ideally this book can be made into a separate series of books each concentrating on a single topic of interest.
I am not a internet programmer, but still this book covers lot of topics how my stand alone application
can be vulnerable if the system is hooked to net.
Must read for all programmrs in todays world.
same as I expected
- There's no such thing as a small security flaw,
- If you see more than one bug of a given type, there are lots more you didn't see, or
- It can still be a security flaw even if you haven't heard of an exploit.
And, as an example in itself, this helps programmers remember that security specialists really do know more about some things than developers with strengths in other areas. (An embarassing story from the early days of Java, not recounted here, described a blunder that any security specialist would have found in a minute - but it was shipped because the team decided they didn't need the specialist's review since they knew it all.)
Then, in a helpful turn, the authors give voluminous examples of what not to do, what to do instead, and finer point of some of the subtler Windows APIs - the APIs that were used in 2003 (when the book was published) or even earlier (when it was being written). Those details were valuable at the time, but aged incredibly rapidly. Some specifics, like resisting SQL injection attacks, remain salient. Others, like use of RC4 for encryption, have been overtaken by more recent findings. And a few statements just weren't true even when this was written. One, that compiler writers might find ways to optimize "volatile" references away (p.326), would break huge amounts of hardware-oriented code if it were to happen.
Lots of the content remains important and widely applicable - five stars for that part, even with a few glitches. But, because so much discussion depends on Windows-specific and aging APIs, I can't give it full marks for today's (or for a non-Windows) reader.
-- wiredweird
Top reviews from other countries
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.
The authors are very highly experienced however they are also a bit smug which does grate from time to time.
This version is from when Windows Server 2003 was still nick-named Windows Server .Net, so that should tell you the age; however, the information is very accurate, and insightful in how to write secure programs even in this day and age. I don't write in C or C++ as much as I'd like to learn it, so some examples went over my head when they got to the code. The information they provide helps a lot to understand *why* the programmers are choosing their insecure or secure methods, and helps to convey the message that security starts as you start planning the project, **before you write any actual code**. I recommend every programmer who wants to write for other people read this book!




