Most systems that have been around for a while has at least some form of integration with other services, software or systems around it. If your IT platform is a bit mature, you might also have an integration platform - a central hub that handles all your integrations and data flow.

But how about security? Your data is flowing around between all these systems and services, but who and how is it ensured that your precious data doesn't end up in someone that's not authorized to access it? Do you ensure that all systems only see what hey need, and how do you handle this?

Are you using passwords or API keys to secure your endpoint? And how does your systems exchange data between them on the "back side"? It may be hard to see where your back-end systems are more accessible than what you actually wish for.

The services in Azure is easy to set up. API Management, set up using some Logic Apps or Functions to do the data load and processing. But hos secure is it? Can you access your Functions omitting the security you built in to the API management?

The security isn't necessarily built in "out of the box", and you really need to consider this - and the earlier in the process the better. You can end up with your back-end systems being wide open to the world, and not even see the unauthorized access in your logs, because you are logging on the wrong level (the level where security actually is handled).

In this session we'll take a deeper dive into how to handle security and network isolation in an integration platform deployed in Microsoft Azure. The principals will absolutely be transferrable to other cloud platforms as well.

We'll discuss the implications of complexity and pricing, what considerations and trade-offs you might have to look into. All taken into consideration your project's budget and data sensitivity.

We'll look in to three main models, ranging from full network isolation to no network isolation. The lesser network isolation, the more work and planning has to be put down into how to secure your platform and your data.

We will guide you through some of the mistakes, so you don't have to make (and correct) them in your own projects, some of the most important pitfalls and some of the biggest cost drivers.