In most organisations, the task of the architect and the task of system security fall to two different people. Architecture is the decisions about how to lay out software functionality across modules, and systems architecture is how those modules communicate with each other. Security is different: it's all about how and where to apply authentication, what permissions to grant to each user, and regulating how code updates are pushed tot o repository.

How’s that approach working for you? Do you feel safe?

In this workshop, Jules demonstrates why our present approaches to security are ineffective, and why security and reliability should be treated as architectural matters. We will cover:
— Why current approaches to security are only minimally effective, and why they’re misguided in principle;
— What a secure-by-design architecture looks like, and why it’s capable of delivering genuine security even through misconfigurations and software failures;
— Why the most important thing to to secure is the data, and how the data itself can defend against unauthorised infiltration, exfiltration, and vandlalism
— Why every security breach is actually a failure of software reliability, and how to construct your software such that, even if it’s imperfect, will never fail in a way which compromises security.

This is how to build systems that are inherently secure, by design.