 Let's get started. This is Stefan. He's going to tell you about protect your data objects, not your network connections Please give him a warm welcome Thank you very much. Thank you for the invitation for stem and for the organization I'm here again like last year with Eliza and Marvin our colleagues Yeah A couple of while ago I talked to Eliza and we talked about our IT architecture So we wanted to explore a little bit a little bit about our business capabilities We wanted to explore about the impact from any legal Things that could be upfront and we were discussing some cloud strategies and then suddenly Eliza interrupted me and told and asked me Have you seen Marvin lately? So I just gave him a few things to do To increase our efficiency and I asked her what exactly was that And she said well, we just wanted to move some of our processes to the cloud. So that's very easy You just move that box over there Then we wanted to have this digital twin data sensor data because we wanted to improve our product with the data from our production line The third item was that we wanted to have some cloud analytics for our factory to have some predictive maintenance data And that last but not least we wanted to receive Data from the supply chain and we wanted to actually also give back data to the supply chain Not speak about software updates, which is another topic so I Was a bit afraid what you all gave to Marvin and maybe You can answer how long would it take you to? apply all those changes One week hands up for one week. I'm glad it works out as in my demo one month Okay, last option one year It's the only last option So last week we had the chance to catch up with Marvin and Eliza Pointed out it's actually important that we would like to have this happening in one week because that's the business Agility so that is what in the end defines if your company survives or not But and data interactions are the driving factor actually in the future it's It's wrong to do to Take a look at anything different And it switched to a different service provider should be very easy And then we asked a Marvin. So what do we need to change? And he said okay So if you look at this picture, then what is clear is that the trust perimeter has changed So before we were used to define zones where everything was secure That doesn't exist anymore Because our fragmented information and information flows and interactions are far more Versatile than they have been until now so a device produces and consumes data at the same time and There are different data owners on each device that we that we are using So actually you have to be able to do authentication and authorization throughout your whole landscape The concept behind this That is zero trust So you define your trust levels for much smaller groups or even for data objects And by looking at data objects, you're getting a fine a fine-grained view of your enterprise and Fine-grained view means let's last but not least you can minimize your risk on a better base those dots on the on the On the they might be of when I was a child and when I played Lego And that's actually true because if you would like to then combine data or push out data You are actually able With zero trust to combine them in that way by just defining access policies So it's a different view on on your architecture that enables you to Include usage control and to do access policy automation So you are able to use different access policies to control where your data is flowing in your company That is actually something that you should avoid so Security gateway that is not securing anything But you can you can mix your trust efforts or your zero trust efforts with Looking at your it architecture And then you can create a map most probably most of the information that you need for it are is already available It's just spread out and not Put together in why in a way that everybody can see it can have a look at it There's a second Concept named data networks that we find very interesting In the old world we all we were used to The so-called our glass model So we are centered everything around our IP connections and on this IP connection on this IP address I know that there is a certain data type or a certain resource So everything has to go through this IP And we need to address IPs and so on And This is our abstraction layer the IP addresses our abstraction layer, but for our data centric world It's not suitable anymore the name data network architecture Takes into account that 90% of our data is coming from streaming services So one sender and multiple receivers and instead of using the IP the IP as the abstraction layer You can also use a name a data chunk the name a name a name of a resource And that is a little twist But actually it is possible So it's a new hourglass model the IP address is not important anymore and security becomes the first citizen Yeah becomes very important Um How can a receiver see what kind of data he would like to have he has a name and so he first sent out Sends out an intent to to retrieve the data and then he gets the data from this from the publisher Why Security is improved Because the sender can always put the Put a signature around his data so a receiver can see there are no Two or more sender and he can decide which of them are most trustworthy That's one part Another part which is not so easy is multi-party encryption because you could have several receivers That is something that you will need And I want to mention that also there are a couple of more projects Dealing with new architectures like coasts here and I put a link up here so that you can compare the security architectures of these Of these new approaches So that's it from my side Eliza and Marvin are still happy and they are still in action and they are happy to support you with anything that comes up Thank you very much Yeah, some questions anybody last chance Okay, it's not really the last chance it probably afterwards you can reach out to him and get those questions answered Thank you