Architectural Risk Assessments


Duration: 50 mins
Brian Sletten
Forward Leaning Software Engineer

We think about architecture in terms of its capacity to describe existing systems or its ability to induce runtime properties, but we often do not spend enough time thinking about its role in security. An architectural risk assessment (ARA) is an organizational activity that should be done periodically, usually at the beginning of a project or prior to a major refactoring. It is an attempt to align security goals with business goals and to measure and describe the risks associated with systems and the people who use and design them. It is also a useful approach for considering potential for abuse and how that can be mediated. We will discuss an overview of the approach and its various activities.

You may also be interested in

25 mins
Getting Cloud Migration Right

Attend this session to learn about cloud migration and it's challenges. You will also go back with insights on a...

25 mins
SRE or Devops - I am an Architect - Why Do I Care?

The most important thing about applications developed for the cloud - is keeping them running. More important than even writing...

50 mins
What Next After Microservices?

Creating good distributed applications is not an easy task: such systems often follow the 12-factor app and microservices principles. They...

25 mins
Automated Failure Injection and Testing across Microservices

How do you test your failure scenarios explicitly across Service APIs?. How can you take control of writing Automated Integration...

25 mins
Self Service Kubernetes for Early Adopters

Kubernetes has ushered in an era of complex and often large-scale micro service applications running as containers. As with any...

50 mins
From my Machine to the Cloud with Cloud-Native Tools

With great scalability comes great responsibility. Individual deployments, updatability and development of microservices comes with advantages as well as challenges....