Continuamos recomendando que os times executem modelagem de ameaças — um conjunto de técnicas para ajudar a identificar e classificar ameaças potenciais durante o processo de desenvolvimento — mas queremos enfatizar que esta não é uma atividade pontual realizada apenas no início dos projetos; as equipes precisam evitar o sanduíche de segurança. Isso ocorre porque ao longo da vida útil de qualquer software, novas ameaças surgirão e as existentes continuarão a evoluir graças a eventos externos e mudanças contínuas nos requisitos e na arquitetura. Isso significa que a modelagem de ameaças precisa ser repetida periodicamente — a frequência de repetição dependerá das circunstâncias e precisará considerar fatores como o custo de execução do exercício e o risco potencial para o negócio. Quando usada em conjunto com outras técnicas, como estabelecer requisitos de segurança multifuncionais para lidar com riscos comuns nas tecnologias do projeto e usar verificadores de segurança automatizados, a modelagem de ameaças pode ser um ativo poderoso.
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.
