Threat Modeling: Designing for Security (Anglais) Broché – 25 avril 2014
|Neuf à partir de||Occasion à partir de|
Produits fréquemment achetés ensemble
Les clients ayant acheté cet article ont également acheté
Descriptions du produit
Présentation de l'éditeur
The only security book to be chosen as a Dr. Dobbs Jolt Award Finalist since Bruce Schneier′s Secrets and Lies and Applied Cryptography!
Adam Shostack is responsible for security development lifecycle threat modeling at Microsoft and is one of a handful of threat modeling experts in the world. Now, he is sharing his considerable expertise into this unique book. With pages of specific actionable advice, he details how to build better security into the design of systems, software, or services from the outset. You′ll explore various threat modeling approaches, find out how to test your designs against threats, and learn effective ways to address threats that have been validated at Microsoft and other top companies.
Systems security managers, you′ll find tools and a framework for structured thinking about what can go wrong. Software developers, you′ll appreciate the jargon–free and accessible introduction to this essential skill. Security professionals, you′ll learn to discern changing threats and discover the easiest ways to adopt a structured approach to threat modeling.
- Provides a unique how–to for security and software developers who need to design secure products and systems and test their designs
- Explains how to threat model and explores various threat modeling approaches, such as asset–centric, attacker–centric and software–centric
- Provides effective approaches and techniques that have been proven at Microsoft and elsewhere
- Offers actionable how–to advice not tied to any specific software, operating system, or programming language
- Authored by a Microsoft professional who is one of the most prominent threat modeling experts in the world
As more software is delivered on the Internet or operates on Internet–connected devices, the design of secure software is absolutely critical. Make sure you′re ready with Threat Modeling: Designing for Security.
Quatrième de couverture
Use threat modeling to enhance software security
If you re a software developer, systems manager, or security professional, this book will show you how to use threat modeling in the security development lifecycle and in the overall software and systems design processes. Author and security expert Adam Shostack puts his considerable expertise to work in this book that, unlike any other, details the process of building improved security into the design of software, computer services, and systems from the very beginning.
- Find and fix security issues before they hurt you or your customers
- Learn to use practical and actionable tools, techniques, and approaches for software developers, IT professionals, and security enthusiasts
- Explore the nuances of software–centric threat modeling and discover its application to software and systems during the build phase and beyond
- Apply threat modeling to improve security when managing complex systems
- Manage potential threats using a structured, methodical framework
- Discover and discern evolving security threats
- Use specific, actionable advice regardless of software type, operating system, or program approaches and techniques validated and proven to be effective at Microsoft and other top IT companies
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.
Détails sur le produit
En savoir plus sur l'auteur
Dans ce livre(En savoir plus)
Commentaires en ligne
Meilleurs commentaires des clients
Commentaires client les plus utiles sur Amazon.com (beta)
The author, Adam Shostack is very honest in his approach that they are tools to be used, not an end in themselves. He provides multiple methodologies for threat modeling from the simple to the complex. He also helps the reader decide when to use the different tools and techniques to be most effective in threat management. Adam has been doing this for many years, and it shows.
This book is more than a summary that you can find on the Internet. It is a detailed explanation of methods for identifying and mitigating threats. It will walk you through the steps for determining the who, what, why, when, where, and most importantly how to threat model. It's also great reference on the variety of techniques and tools that you can adapt based on the organization and circumstance.
Even if you don't have the time to learn all of the skills contained in Threat Modeling, I recommend it for the simple steps you can take to improve your practice.
All organizations need to formalize their Threat Modeling process. Not to do so introduces unacceptable risks. This book provides the knowledge for you to "Dive In and Threat Model!"
The system was rushed into use and its output of colors was not clear. What was the difference between levels such as high, guarded and elevated? From a threat perspective, which color was more severe - yellow or orange? Former DHS chairman Janet Napolitano even admitted that the color-coded system presented “little practical information” to the public
While the DHS has never really provided meaningful threat levels, in Threat Modeling: Designing for Security, author Adam Shostack (full disclosure: Adam and I are friends) has done a remarkable job in detailing an approach that is both achievable and functional. More importantly, he details a system where organizations can obtain meaningful and actionable information, rather than vague color charts.
Rather than letting clueless bureaucrats and Federal agencies define threats, the book details a formal system in which you can understand and particularize the unique threats your organizations faces.
In the introduction, Shostack sums up his approach in four questions:
What are you building?
What can go wrong with it once it’s built?
What should you do about those things that can go wrong?
Did you do a decent job of analysis?
The remaining 600 densely packed pages provide the formal framework needed to get meaningful answers to those questions. The book sets a structure in which to model threats, be it in software, applications, systems, software or services, such as cloud computing.
While the term threat modeling may seem overly complex, the book notes that anyone can learn to threat model. Threat modeling is simply using models to find security problems. The book notes that using a model means abstracting away a lot of the details to provide a look at the bigger picture, rather than the specific item, or piece of software code.
An important point the book makes is that there is more than one way to model threats. People often place too much emphasis on the specifics of how to model, rather than focusing on what provides them the most benefit. Ultimately, the best model for your organization is the one that helps you determine what the main threats are. Finally, the point is not just to find the threats; the key is to address them and fix them.
The beauty of the book is that it focuses on gaining empirical data around threats for your organization. Rather than simply taking an approach based on Gartner, USA Today or industry best practices.
While the author states a few times that threat modeling is not necessarily a complex endeavor, it nonetheless does take time. He writes that threat modeling requires involvement from many players from different departments in an organization to provide meaningful input. Without broad input, the threat model will be lacking, and the output will be incomplete.
For those organizations that are willing to put the time and effort into threat modeling, the benefits will be remarkable. At the outset, they will have confidence that they understand the threats their organization is facing, likely spend less on hardware and software, and will be better protected.
Chapter 18 quotes programmer Henry Spencer who observed that “those who do not understand Unix are condemned to reinvent it, poorly”. Shostack writes that the same applies to threat modeling. The point he is making is that there are ways to fail at threat modeling. The first is simply not trying. The chapter then goes on into other approaches which can get in the way of an effective threat modeling program.
Why should you threat model for your IT and other technology environments? It should be self-evident from an architecture perspective. When an architect is designing an edifice, they first must understand their environment and requirements. A residence for a couple in Manhattan will be entirely different from the design for a residence for a family in Wyoming. But far too many IT architects take a monolithic approach to threats and that’s precisely the point the book is attempting to obviate.
As noted, threat modeling is not overly complex. But even if it was indeed complex, it is far too important not to be done. The message of the book is that organizations need to stop chasing vague threats and industry notions of what threats are, and customize things so they deal with their threats.
Risk modeling is so important that it must be seen as an essential part of a formal and mature information security program. Having firewalls, IDS, DLP and myriad other infosec appliances can be deceptive in thinking they provide protection. But if they are deployed in an organization that has not defined the threats these devices are expected to address, they only serve the purpose of giving an aura of infosec protection, and not real protection itself.
Amazon has over 800 Disney World guide books. Anyone who is going to invest their time and money to spend a few days at Disney World knows they have to do their research in order to get the most out of their visit.
There are only a handful of books on this topic and this is perhaps the finest of them. No tourist would be so naïve to go to Disney World uninformed. And conversely, no one should go into the IT world without adequate threat information.
Threat modeling provides compelling benefits in the ability to make better information security decisions, better focus on often limited resources, all while designing a model to protect against current and future threats.
For those serious about the topic, Threat Modeling: Designing for Security will be one of the most rewarding information security books they could hope for.
Building on the very understandable beginning, Threat Modeling: Designing for Security gradually explores the topic at deeper and deeper levels, the later chapters providing specific and actionable material for even the most experience threat modeling professionals.
This book should be useful whether you're just getting started in security design or you've been in the field for decades.
You'll also find discussions about cloud threats, privacy exploits, and identity lifecycles. If you're in charge of threat modeling at your company, you're no doubt actively worrying about all three topics. Clearly, Adam has been there and done that -- not just at a defender-versus-attacker tactical level, but in trying to implement threat modeling at an enterprise level. It's easy to model threats to a single program or process, but it's a lot harder to make it a part of an organization's DNA. The book helps by offering chapters dedicated to the success of enterprise implementations, including strategies, tools, and politics"