How to address security as collective systems

Architects are often the ones making the decisions about how to build in the right security for systems while making systems usable and delivering them on time. James Stewart shares techniques for considering security of whole systems and explores ways of bringing together cross-disciplinary teams to collectively own secure designs.

Architects are often the ones making the decisions about how to build in the right security for systems while making systems usable and delivering them on time. It can be tough to get buy-in to do the right thing, particularly as we increasingly recognize that security isn’t purely a technical consideration but is instead about systems as a whole: technology, human behaviors, and basic design decisions. Security needs to be everyone’s problem to solve and responsibility to understand. It’s vital that modern teams are able to understand the security issues affecting their work so that team members are aligned and can communicate their challenges clearly to the rest of their organization. James Stewart shares techniques for considering security of whole systems and explores ways of bringing together cross-disciplinary teams to collectively own secure designs. You’ll learn strategies for understanding the various types of bad actors who want to break the systems and ways to help the whole team contribute to a conversation about how to address those issues and prioritize them against other user needs.