Architectural Risk Assessments


2nd July 2020
Speaker Date: 1st July 2020
Speaker Time: PDT: 20:00-21:00
Attendee Date: 2nd July 2020
Attendee Time: IST: 08:30-09:30 | SGT: 11:00-12:00 | AEST: 13:00-14:00
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

6th, August

Time
Cloud Native Culture

The shift to cloud computing involves a veritable plethora of new technologies and approaches. From 12 factors to domain drive...

6th, August

Time
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...

6th, August

Time
SaaS @ Scale with Kubernetes

In this talk, we will start by describing the three major challenges faced by the Machine Learning team at Freshworks....

6th, August

Time
Communication Patterns in Microservices

Teams adopt microservices understanding the structure of the architecture but with a poor understanding of how to get all the...

7th, August

Time
15 Best Practices for Designing Enterprise RESTful APIs in Cloud Workshop

API Gateway is a way to connect Enterprise application in cloud-ready applications. New applications need to design the data model...

6th, August

Time
Running Microservices on Kubernetes – Best Practices

Yes, we have split the product functionality into separate independent Microservices, but how do we manage this distributed beast? There...