deliver:Agile 2018 has ended
Back To Schedule
Wednesday, May 2 • 10:30 - 12:00
How to fit threat modelling into agile development: slice it up (Irene Michlin)

Sign up or log in to save this to your schedule, view media, leave feedback and see who's attending!

Agile is focused on the creation and building of great software, we all agree on that. Can you claim a great software if this software is not secure? Would customers accept a feature, no matter how attractive and useful, if they suspect it puts their data at risk?
Security is therefore essential to all the software we build. As with many other software properties, security cannot be "bolted on". The earlier in the lifecycle you pay attention to security, the better are the outcomes.
Threat modelling is one of the best techniques for improving the security of your software. It is a structured method for identifying weaknesses on design level.
However, people who want to introduce it into their work on existing codebase often face time pressure and very rarely can a company afford “security push”, where all new development stops for a while in order to focus on security.
Incremental threat modelling that concentrates on current additions and modifications can be time-boxed to fit the tightest of agile life-cycles and still deliver security benefits.
Full disclosure is necessary at this point – threat modelling is not the same as adding tests to the ball of mud codebase and eventually getting decent test coverage. You will not be able to get away with doing just incremental modelling, without tackling the whole picture at some point.
But the good news are you will approach this point with more mature skills from getting the practice, and you will get a better overall model with less time spent than if you tried to build it upfront.
We will cover the technique of incremental threat modelling, and then the workshop will split into several teams, each one modelling an addition of a new feature to a realistic architecture. The participants will learn how to find the threats relevant to the feature while keeping the activity focused (i.e. not trying to boil an ocean).
This session targets mainly developers, qa engineers, and architects, but will be also beneficial for scrum masters and product owners.

Learning Outcomes:
  • Learn the technique for applying threat modelling in time-boxed sessions within each iteration. You will increase your confidence in delivering secure software to your customers.


avatar for Irene Michlin

Irene Michlin

Senior Managing Consultant & Europe Appsec Lead, IBM
Introducing security into software development lifecycle, threat modelling, security for Agile and Lean. @IreneMichlin

Wednesday May 2, 2018 10:30 - 12:00 CDT
Lone Star D