Seguimos recomendando que los equipos continúen haciendo uso del modelado de amenazas — un conjunto de técnicas que ayudan a identificar y clasificar amenazas potenciales durante el proceso de desarrollo — pero queremos enfatizar que esto no es una actividad a realizar únicamente al comienzo de los proyectos; los equipos deben evitar el security sandwich. Esto sucede porque durante todo el ciclo de vida de cualquier software, nuevas amenazas surgirán y las existentes continuarán evolucionando debido a eventos externos y constantes cambios de requisitos y arquitecturas. Esto significa que el modelado de amenazas se tiene que repetir de forma periódica — la frecuencia de repetición dependerá de las circunstancias y necesitará considerar factores como el coste de realizar el ejercicio y el riesgo potencial para el negocio. En combinación con otras técnicas, como el establecimiento de requisitos de seguridad multifuncionales para manejar riesgos comunes de las tecnologías del proyecto y el uso de escáneres de seguridad automatizados, el modelado de amenazas puede ser un poderoso recurso.
With the number of high-profile security breaches in the past months, software development teams no longer need convincing that they must place an emphasis on writing secure software and dealing with their users' data in a responsible way. The teams face a steep learning curve, though, and the vast number of potential threats—ranging from organized crime and government spying to teenagers who attack systems "for the lulz"—can be overwhelming. Threat Modeling provides a set of techniques that help you identify and classify potential threats early in the development process. It is important to understand that it is only part of a strategy to stay ahead of threats. When used in conjunction with techniques such as establishing cross-functional security requirements to address common risks in the technologies a project uses and using automated security scanners, threat modeling can be a powerful asset.
With the number of high-profile security breaches in the past months, software development teams no longer need convincing that they must place an emphasis on writing secure software and dealing with their users’ data in a responsible way. The teams face a steep learning curve, though, and the vast number of potential threats - ranging from organized crime and government spying to teenagers who attack systems 'for the lulz' can be overwhelming. Threat Modeling provides a set of techniques, mostly from a defensive perspective, that help you understand and classify potential threats. Turned into 'evil-user stories', threat models can give a team a manageable and effective approach to making their systems more secure.
At this point the vast majority of development teams are aware of the importance of writing secure software and dealing with their users’ data in a responsible way. They do face a steep learning curve and a vast number of potential threats, ranging from organized crime and government spying to teenagers who attack systems 'for the lulz'. Threat Modelingis a set of techniques, mostly from a defensive perspective, that help understand and classify potential threats. When turned into 'evil user stories' this can give a team a manageable and effective approach to making their systems more secure.
