رونوشت 🔗
WEBVTT
00:00:00.000 --> 00:00:08.760
Hello, everybody and welcome to a new episode of our tech podcast by Bosch Rexroth.
00:00:08.760 --> 00:00:12.960
My name is Robert Weber and today we are going to talk about the Cyber Resilience
00:00:12.960 --> 00:00:17.040
Act and Cyber Security and I invited two guests.
00:00:17.040 --> 00:00:18.560
One guest is Michael Langfinger.
00:00:18.560 --> 00:00:20.080
Michael, welcome to the podcast.
00:00:20.080 --> 00:00:21.080
Hi, Robert.
00:00:21.080 --> 00:00:22.440
And Sebastian Krauskopf.
00:00:22.440 --> 00:00:24.280
Sebastian, welcome to the podcast.
00:00:24.280 --> 00:00:25.280
Hey, Robert.
00:00:25.280 --> 00:00:26.280
Nice to be here.
00:00:26.280 --> 00:00:30.800
Before we start, please introduce yourself briefly to the listeners.
00:00:30.800 --> 00:00:32.400
Michael, first, please.
00:00:32.400 --> 00:00:38.040
Yes, I'm the product owner of Cyber Security and also the product security officer of our
00:00:38.040 --> 00:00:41.920
business unit, automation and electrification.
00:00:41.920 --> 00:00:44.520
So very long introduction.
00:00:44.520 --> 00:00:47.280
So maybe let me split it up into the product owner part.
00:00:47.280 --> 00:00:54.360
This means that my team and I, we are developing the base security framework of Control XOS
00:00:54.360 --> 00:01:00.120
and as a product security officer, I'm responsible for multiple topics, mostly ensuring that
00:01:00.120 --> 00:01:05.400
all the security requirements are fulfilled in our development, raising awareness in the
00:01:05.400 --> 00:01:10.440
company or in the business unit in this case and yes, also providing technical tools and
00:01:10.440 --> 00:01:12.240
methods to our colleagues.
00:01:12.240 --> 00:01:13.240
Okay.
00:01:13.240 --> 00:01:14.240
Thanks, Michael.
00:01:14.240 --> 00:01:15.240
Sebastian.
00:01:15.240 --> 00:01:18.600
Yeah, I'm the lead software architect with the focus of the control platforms of Contra
00:01:18.600 --> 00:01:19.600
X automation.
00:01:19.600 --> 00:01:24.920
So this means I'm responsible for the design of our control hardware, Control X core and
00:01:24.920 --> 00:01:30.200
our software platform, Control X OS and the corresponding apps.
00:01:30.200 --> 00:01:33.880
And at the same time, I take care of the software development process.
00:01:33.880 --> 00:01:39.920
So that means the process of making software designs, creating architectural documentation,
00:01:39.920 --> 00:01:42.520
testing software and delivering software.
00:01:42.520 --> 00:01:47.920
So Cyber Security and the Cyber Resilience are huge topic in the whole industry.
00:01:47.920 --> 00:01:53.760
From my point of view, modern automation system consists of large number of network connections,
00:01:53.760 --> 00:01:58.360
connected machines, industry 4.0 is a huge topic.
00:01:58.360 --> 00:02:03.720
Cyber attacks in industry runs into billions of damage caused by cyber attacks and then
00:02:03.720 --> 00:02:10.760
we have some regulation topic, Cyber Resilience Act for every product that can communicate
00:02:10.760 --> 00:02:12.560
with another product.
00:02:12.560 --> 00:02:17.520
So when you talk to your customer, Sebastian, what are the biggest misconceptions?
00:02:17.520 --> 00:02:20.960
When it comes to the cyber security in automation?
00:02:20.960 --> 00:02:27.520
Well, at the beginning, many people for them, Cyber Security was only about encryption of
00:02:27.520 --> 00:02:30.720
communication protocols, what it was in their mind.
00:02:30.720 --> 00:02:32.440
But of course, this is not sufficient.
00:02:32.440 --> 00:02:38.120
As we all know, it's not only about the objective of privacy, but it's also about to improve
00:02:38.120 --> 00:02:44.320
the availability of an automation system or to ensure the platform integrity.
00:02:44.320 --> 00:02:49.000
And also an assumption is often that security can be implemented in a single feature in
00:02:49.000 --> 00:02:51.440
a single component and then I'm done.
00:02:51.440 --> 00:02:53.320
It's not so easy.
00:02:53.320 --> 00:03:00.040
So it would be like saying if the security lock on my front door of my house is big enough,
00:03:00.040 --> 00:03:01.040
then I'm done.
00:03:01.040 --> 00:03:03.360
But of course, this is not the case.
00:03:03.360 --> 00:03:05.960
What are you tired of hearing?
00:03:05.960 --> 00:03:11.560
I'm actually tired of hearing that Cyber Security is not part of my business.
00:03:11.560 --> 00:03:13.360
I don't need to care about Cyber Security.
00:03:13.360 --> 00:03:14.800
Do you still hear that?
00:03:14.800 --> 00:03:16.000
Yes, indeed.
00:03:16.000 --> 00:03:22.760
We still have talks where we hear on the one side that it's not my deal or what we also
00:03:22.760 --> 00:03:28.000
often hear, but this is getting better is about people who not yet really looked into
00:03:28.000 --> 00:03:32.360
it, who just start to look into what does this mean for me.
00:03:32.360 --> 00:03:33.800
But time is ticking, right?
00:03:33.800 --> 00:03:35.360
Yes, that's true.
00:03:35.360 --> 00:03:36.360
Time is ticking.
00:03:36.360 --> 00:03:43.120
In 2027, there will be the enforcement of the Cyber Resilience Act and I can only encourage
00:03:43.120 --> 00:03:48.280
everyone, every machine builder to really have a look into this, to build a Cyber Security
00:03:48.280 --> 00:03:51.400
strategy to be prepared.
00:03:51.400 --> 00:03:55.600
What are the biggest obstacles for your customers?
00:03:55.600 --> 00:03:58.640
Actually where do they need help?
00:03:58.640 --> 00:04:05.320
The new thing for them is that the first time the security is something which affects the
00:04:05.320 --> 00:04:09.040
whole life cycle of the product of the machine.
00:04:09.040 --> 00:04:12.320
So it does not end with the commissioning of the machine.
00:04:12.320 --> 00:04:16.520
The machine is gone, sold to the customer, everything
Load full transcript
works, I'm done.
00:04:16.520 --> 00:04:22.400
But now it still can be, there will be a vulnerability years after the machine has been deployed to
00:04:22.400 --> 00:04:30.360
the plant and you need to do a software update to fix a vulnerability even if the machine
00:04:30.360 --> 00:04:32.480
is working perfectly.
00:04:32.480 --> 00:04:36.600
You mentioned already the Cyber Resilience Act in 27, everybody needs to fulfill the
00:04:36.600 --> 00:04:39.120
regulation of the Cyber Resilience Act.
00:04:39.120 --> 00:04:44.880
But the Cyber Resilience Act, is it a baseline or do you offer more to your customer when
00:04:44.880 --> 00:04:47.800
it comes to Cyber Security?
00:04:47.800 --> 00:04:53.640
Well the Cyber Resilience Act is the first time where we have a regulatory list of requirements
00:04:53.640 --> 00:04:57.120
that you need to fulfill in order to sell your product.
00:04:57.120 --> 00:05:03.520
But of course for us Cyber Security is more, our ambition is also to provide more than what
00:05:03.520 --> 00:05:05.440
the Cyber Resilience Act requires.
00:05:05.440 --> 00:05:09.480
This means we have additional apps, we have additional features which really go beyond
00:05:09.480 --> 00:05:10.480
the Cyber Resilience Act.
00:05:10.480 --> 00:05:13.200
Michael, can you go a little bit deeper, what means "beyond"?
00:05:13.200 --> 00:05:19.640
Yeah, of course when we started developing Control X OS, the Cyber Resilience Act was not
00:05:19.640 --> 00:05:22.600
even, nobody could foresee that obviously.
00:05:22.600 --> 00:05:24.960
So this has not been on our mind.
00:05:24.960 --> 00:05:29.960
But of course we had to for example align to already existing standards to mention one
00:05:29.960 --> 00:05:35.840
would be the IEC62443, to which we have also certified our Control X OS.
00:05:35.840 --> 00:05:38.720
So we have already.. certified by who?
00:05:38.720 --> 00:05:40.760
By TÜV in this case.
00:05:40.760 --> 00:05:46.760
So we have quite some requirements already fulfilled on the one hand side.
00:05:46.760 --> 00:05:52.800
But of course, as Sebastian mentioned, the ambition is not to only fulfill the bare minimum
00:05:52.800 --> 00:05:57.080
that you must fulfill to bring your product to the market, but to offer our customers
00:05:57.080 --> 00:06:00.680
solutions that they can use to improve their security as well, so that they can profit from
00:06:00.680 --> 00:06:01.680
our expertise.
00:06:01.680 --> 00:06:02.680
Can you share three?
00:06:02.680 --> 00:06:08.680
Yeah, of course, for example, the base system brings a lot of security functionalities already
00:06:08.680 --> 00:06:14.200
now that are more than the CRA demands where you can benefit from, for example, if you
00:06:14.200 --> 00:06:19.720
use Control X OS on your device, if you sell a device with Control X OS, or if you use it in
00:06:19.720 --> 00:06:23.000
your machine, even if you are developing an app for that.
00:06:23.000
--> 00:06:27.040
So yeah, we have lots of benefits for different stakeholders, let's say.
00:06:27.040 --> 00:06:28.480
You have different stakeholders.
00:06:28.480 --> 00:06:32.600
That's important, I think, because you have maybe four stakeholders, right?
00:06:32.600 --> 00:06:34.560
Yeah, around about, I would say.
00:06:34.560 --> 00:06:38.800
I mean, in the end, obviously, the one that operates the machine is also a stakeholder
00:06:38.800 --> 00:06:39.800
for us.
00:06:39.800 --> 00:06:45.000
And as already mentioned, app developers, machine builders, other vendors, selling the
00:06:45.000 --> 00:06:50.960
products, and they, like I said, they benefit from different functions that we provide.
00:06:50.960 --> 00:06:57.040
How have you prepared for the Cyber Resilience Act, Sebastian?
00:06:57.040 --> 00:07:03.560
Well, actually, even before the Cyber Resilience Act came up, Cyber Security was a very important
00:07:03.560 --> 00:07:05.360
topic for us.
00:07:05.360 --> 00:07:10.240
Control X OS and Control X Core are new platforms, pretty new platforms.
00:07:10.240 --> 00:07:16.120
And our goal, our ambition was to create an automation product which combines the robustness
00:07:16.120 --> 00:07:21.680
and the performance of an OT device with the flexibility and the connectivity of an IT
00:07:21.680 --> 00:07:22.680
device.
00:07:22.680 --> 00:07:28.800
So it was pretty clear for us that Cyber Security is an important, so to say, architectural
00:07:28.800 --> 00:07:29.800
driver.
00:07:29.800 --> 00:07:31.200
Cybersecurity by design.
00:07:31.200 --> 00:07:33.000
Cybersecurity by design.
00:07:33.000 --> 00:07:38.240
So we started right from the beginning with a secure engineering process.
00:07:38.240 --> 00:07:42.440
We analyzed threats and risk, implemented countermeasures.
00:07:42.440 --> 00:07:48.720
We applied principles like the defense in depth principle, which means that we have multiple
00:07:48.720 --> 00:07:56.400
layers of defense mechanisms, like you can think of an onion, or in order to harden the
00:07:56.400 --> 00:07:59.240
system and to make it as secure as possible.
00:07:59.240 --> 00:08:02.560
Is that a USP you can sell on the market?
00:08:02.560 --> 00:08:03.640
Yes, definitely.
00:08:03.640 --> 00:08:04.640
We think so.
00:08:04.640 --> 00:08:08.400
There is room and there are applications which highly benefit for it.
00:08:08.400 --> 00:08:15.360
I mean, in the end, it's about creating availability to improve the overall availability of your
00:08:15.360 --> 00:08:16.560
system.
00:08:16.560 --> 00:08:20.920
And we see that the threats and the risk, they increase.
00:08:20.920 --> 00:08:27.160
Michael, when we talk about Cyber Resilience Act, it's not about a product, right?
00:08:27.160 --> 00:08:31.520
It's about the competence to build products on the regulation.
00:08:31.520 --> 00:08:33.080
Yeah, exactly.
00:08:33.080 --> 00:08:35.240
You do it once, for example, and you're done.
00:08:35.240 --> 00:08:39.360
I mean, Sebastian mentioned a lot of very important topics that, of course, have to
00:08:39.360 --> 00:08:44.000
be covered, especially coming back, for example, the defense in depth approach, which means
00:08:44.000 --> 00:08:49.160
that to identify which layer of protection you need to implement, you have to think like
00:08:49.160 --> 00:08:50.160
an attacker.
00:08:50.160 --> 00:08:52.000
So this is something I would say that's...
00:08:52.000 --> 00:08:56.160
How difficult is that for you and your team to think like an attacker?
00:08:56.160 --> 00:09:02.320
I mean, if you design your system from scratch based on such assumptions, you get used to
00:09:02.320 --> 00:09:04.680
that and it's part of your daily work.
00:09:04.680 --> 00:09:08.260
But if you have not in the past considered this in a product development, and I would
00:09:08.260 --> 00:09:12.880
assume that a lot of companies have not done this yet and are not doing this today, then
00:09:12.880 --> 00:09:15.920
it's increasingly difficult to think so.
00:09:15.920 --> 00:09:20.720
But this is one important competence that you have to learn as a company now, and you
00:09:20.720 --> 00:09:22.720
have to keep on learning that.
00:09:22.720 --> 00:09:28.480
So it must be part of your daily business to implement this in your daily work, let's
00:09:28.480 --> 00:09:29.480
say.
00:09:29.480 --> 00:09:35.200
So as one example, of course, you have to follow your secure coding guidelines, but it's more
00:09:35.200 --> 00:09:36.760
than just developing...
00:09:36.810 --> 00:09:39.330
something concentrating on one product or so.
00:09:39.330 --> 00:09:43.450
It's, it's more, it's the whole life cycle you have to cover and you have to think of
00:09:43.450 --> 00:09:48.510
this whole life cycle at the very beginning when you start developing the product to
00:09:48.510 --> 00:09:51.410
have in mind that later on you must provide patches.
00:09:51.410 --> 00:09:55.970
You must to have all these processes in place you need everything Sebastian mentioned.
00:09:55.970 --> 00:09:58.370
So this is a huge paradigm shift, I would say.
00:09:58.370 --> 00:10:01.010
I want to come back to your products.
00:10:01.010 --> 00:10:03.450
You already mentioned Control X OS.
00:10:03.450 --> 00:10:06.370
It's a Linux based operating system.
00:10:06.370 --> 00:10:08.330
So it's an open source based system.
00:10:08.330 --> 00:10:10.170
It's also a security topic, right?
00:10:10.170 --> 00:10:12.570
To rely on an open source project.
00:10:12.570 --> 00:10:13.690
Yeah, of course.
00:10:13.690 --> 00:10:19.490
I mean, for almost all open source projects, they have been refued by lots and
00:10:19.490 --> 00:10:20.810
lots of people over the time.
00:10:20.810 --> 00:10:25.810
I mean, we're talking about projects like the Linux kernel or open SSL or similar projects.
00:10:25.810 --> 00:10:28.850
They are not some smaller
projects done by one or two people.
00:10:28.850 --> 00:10:31.610
Those are huge projects used by huge companies.
00:10:31.730 --> 00:10:36.570
So of course you benefit from the experience that's there in those projects.
00:10:36.570 --> 00:10:38.930
And this is also something that's important.
00:10:38.930 --> 00:10:40.570
We do not want to reinvent the wheel.
00:10:40.570 --> 00:10:44.050
We want to base on established secure standards.
00:10:44.050 --> 00:10:46.250
Establish IT standards.
00:10:46.250 --> 00:10:47.130
Yeah, exactly.
00:10:47.130 --> 00:10:49.890
I think that's what Sebastian I think mentioned before.
00:10:49.890 --> 00:10:54.850
It's this kind of these worlds that already have started to merge, right?
00:10:54.850 --> 00:10:57.770
The OT and the IT, you cannot separate them anymore.
00:10:58.210 --> 00:11:03.850
And our goal is to use the benefits of the IT technologies also in the OT world.
00:11:03.850 --> 00:11:09.090
And this, to my understanding, also involves all the security aspects, which
00:11:09.090 --> 00:11:12.690
yeah, have not been a top priority in the past in OT.
00:11:12.690 --> 00:11:16.330
Control X core is your control platform.
00:11:16.330 --> 00:11:21.730
What is the added value in terms of security when it comes to control X core?
00:11:21.730 --> 00:11:27.930
I mean, what you get is a part from obviously the software contracts as running on it.
00:11:28.130 --> 00:11:33.570
You get hardware, which, for example, has a mechanism in place where you can detect
00:11:33.570 --> 00:11:35.850
whether the case or the housing has been opened.
00:11:35.850 --> 00:11:37.610
And of course you can use it.
00:11:37.610 --> 00:11:39.210
It's an industrial grade hardware.
00:11:39.210 --> 00:11:44.410
You can use it to, for example, build your own security gateway based on the control
00:11:44.410 --> 00:11:49.970
X core, allowing you, in this case, as a machine builder to secure your whole machinery.
00:11:49.970 --> 00:11:52.250
So you have also existing machines.
00:11:52.250 --> 00:11:53.050
Yes, of course.
00:11:53.050 --> 00:11:54.090
That's the idea behind it.
00:11:54.090 --> 00:11:54.490
Okay.
00:11:54.570 --> 00:11:59.530
You have a very flexible modular system, which brings everything with it and which
00:11:59.530 --> 00:12:04.170
you can further extend to realize the security gateway in this case as an example.
00:12:04.170 --> 00:12:05.530
You want to add something Sebastian?
00:12:05.530 --> 00:12:09.490
Yeah, basically with control X core, you have an out of the box solution, a hardware
00:12:09.490 --> 00:12:12.930
software platform, which is out of the box security certified.
00:12:12.930 --> 00:12:17.010
And you can start using it, building your application right out of the box.
00:12:17.010 --> 00:12:21.250
Let's talk a little bit about updates and patches.
00:12:21.250 --> 00:12:22.770
What happens in the future?
00:12:23.090 --> 00:12:29.370
What happens 27 when you have to update your machine, when you have to deliver patches?
00:12:29.370 --> 00:12:30.410
How do you do that?
00:12:30.410 --> 00:12:37.370
I mean, patches and updates, they are increasingly important because it's a security risk too.
00:12:37.370 --> 00:12:37.730
Right?
00:12:37.730 --> 00:12:38.730
Yeah, of course.
00:12:38.730 --> 00:12:43.730
I mean, in the past, there was always the thinking I've now developed my, my machine.
00:12:43.730 --> 00:12:48.810
I have shipped it to the customer and it's securely stashed away somewhere in some factory.
00:12:48.810 --> 00:12:50.210
And it's not connected to the internet.
00:12:50.210 --> 00:12:51.170
So everything is fine.
00:12:51.410 --> 00:12:51.930
Exactly.
00:12:51.930 --> 00:12:57.330
That's what's the, the perfect world, which I, in my opinion, never existed, but this
00:12:57.330 --> 00:12:58.130
was the assumption.
00:12:58.130 --> 00:13:01.490
And nowadays you want to connect those devices.
00:13:01.490 --> 00:13:03.250
You want to get data out of them.
00:13:03.250 --> 00:13:06.370
You want to work with this data, yeah, with AI model, things like that.
00:13:06.370 --> 00:13:07.610
Do you want to process the data?
00:13:07.610 --> 00:13:08.810
So you have to connect there.
00:13:08.810 --> 00:13:12.810
And then of course, those devices must be secure as well.
00:13:12.810 --> 00:13:14.490
And to keep them secure.
00:13:14.490 --> 00:13:19.450
I mean, they can be secure, but the moment you ship them, it can happen.
00:13:19.530 --> 00:13:23.450
And it happens on a daily basis that somebody discovers a vulnerability and then you're
00:13:23.450 --> 00:13:24.730
forced.. which is good.
00:13:24.730 --> 00:13:25.850
Yeah, of course.
00:13:25.850 --> 00:13:26.610
That's a good thing.
00:13:26.610 --> 00:13:32.570
So, but then you as a vendor, you're forced to provide those patches as soon as possible.
00:13:32.570 --> 00:13:34.290
How fast do you need to deliver them?
00:13:34.290 --> 00:13:35.610
I mean, it depends.
00:13:35.610 --> 00:13:40.930
The CRA in this case, for example, just states that if you're becoming aware of an
00:13:40.930 --> 00:13:44.130
availability that's being exploited, then you have to react very quickly.
00:13:44.130 --> 00:13:48.570
So you have to give a first analysis, I would say in 24 hours even.
00:13:48.570 --> 00:13:49.730
So that's very quick.
00:13:49.730 --> 00:13:54.330
I mean, of course, we're able to actually ship updates that takes a while.
00:13:54.330 --> 00:13:59.410
You have to test them, but you have to also provide to your customers the information.
00:13:59.410 --> 00:14:02.450
Okay, what can they do until the patches were available, for example?
00:14:02.450 --> 00:14:05.370
So that's more than just providing the technical patch.
00:14:05.370 --> 00:14:07.090
And so, yeah.
00:14:07.090 --> 00:14:07.290
Yeah.
00:14:07.290 --> 00:14:10.290
And I mean, our part here is to make the life easier for our
customers.
00:14:10.290 --> 00:14:15.690
I mean, think how you applied patches back then in Windows 95 and how easy, how
00:14:15.690 --> 00:14:17.970
automatically this is now done on your smartphone.
00:14:17.970 --> 00:14:22.850
And the same is true for Control-X OS, where we apply basically security patches as
00:14:22.850 --> 00:14:24.130
simple as on your smartphone.
00:14:24.130 --> 00:14:28.250
I mean, we even provide the portal for you if you want to use that.
00:14:28.250 --> 00:14:32.410
The Control X device portal in this case allows you to deploy and ship patches
00:14:32.410 --> 00:14:36.330
easily to your machines as a fleet management, defining when you want to
00:14:36.330 --> 00:14:38.410
distribute them, update them.
00:14:38.410 --> 00:14:40.930
So you can have this in a very easy way.
00:14:40.930 --> 00:14:43.370
But if you say no, that's not what I want to do.
00:14:43.370 --> 00:14:48.090
I want to integrate this into my own update management tooling.
00:14:48.090 --> 00:14:50.810
That's also no problem because the interfaces are there.
00:14:50.810 --> 00:14:51.530
They are open.
00:14:51.530 --> 00:14:53.050
You can use them easily.
00:14:53.050 --> 00:15:00.690
Can you please share what are your two big misconceptions or errors in reasoning
00:15:00.690 --> 00:15:02.570
when it comes to the Cyber Resilience Act?
00:15:02.570 --> 00:15:05.050
Maybe two of Michael, one of Sebastian.
00:15:05.050 --> 00:15:07.450
What are the biggest misconceptions?
00:15:07.450 --> 00:15:13.090
I mean, what I often hear is, yeah, I can be relaxed because it does not affect me.
00:15:13.330 --> 00:15:18.970
I'm just providing the sensor here that grabs some digital data and transforms them.
00:15:18.970 --> 00:15:21.370
But that's actually not the case.
00:15:21.370 --> 00:15:23.650
I mean, also sensor is a digital component.
00:15:23.650 --> 00:15:25.450
So I have to take care of that as well.
00:15:25.450 --> 00:15:28.570
Sebastian, you want to share your biggest misconception?
00:15:28.570 --> 00:15:33.610
The biggest misconception is at the moment that there is still time left.
00:15:33.610 --> 00:15:34.690
This is not true.
00:15:34.690 --> 00:15:35.570
The clock is ticking.
00:15:35.570 --> 00:15:38.610
You have to get your cybersecurity strategy.
00:15:38.610 --> 00:15:40.330
Now you need to be prepared.
00:15:40.330 --> 00:15:44.530
Twenty twenty seven, the regulatory will go live.
00:15:44.530 --> 00:15:47.970
So we talked a lot about the Cyber Resilience Act.
00:15:47.970 --> 00:15:54.170
What do you offer to machine building companies with a whole existing machine
00:15:54.170 --> 00:15:56.010
park when it comes to cybersecurity?
00:15:56.010 --> 00:15:58.370
Is there also solutions for them?
00:15:58.370 --> 00:16:00.010
Yeah, of course.
00:16:00.010 --> 00:16:03.690
And that's one thing I like a lot about Control X OS.
00:16:03.730 --> 00:16:09.850
And in this case, Control X Core, because
you can realize so many different use cases.
00:16:09.850 --> 00:16:14.850
And this case, talking about machine builders or existing machines, what you often need
00:16:14.850 --> 00:16:17.970
I'm already know is a security gateway.
00:16:17.970 --> 00:16:23.690
So why not take your Control X Core and make a security gateway out of it using the existing apps?
00:16:23.690 --> 00:16:29.450
So you have this solution bundle, let's say, which is combined of the firewall app,
00:16:29.450 --> 00:16:33.090
the VPN app and the security scanner, for example, that you can use to
00:16:33.090 --> 00:16:37.290
place it at the edge of your machine to protect all the components that are
00:16:37.290 --> 00:16:40.850
at the legacy components, brownfield devices that are not secure.
00:16:40.850 --> 00:16:47.210
So yeah, use the firewall to protect access to them to control data that is transmitted there.
00:16:47.210 --> 00:16:50.130
You have your VPN for security mode maintenance.
00:16:50.130 --> 00:16:56.330
And you, in this case, you take the security scanner and you can even use that to have
00:16:56.330 --> 00:16:59.850
an overview about all the components in there.
00:17:00.010 --> 00:17:04.970
And especially not only an overview, you get a detailed overview about the security status.
00:17:04.970 --> 00:17:09.650
So you can easily determine, hey, there is suddenly a new device in there.
00:17:09.650 --> 00:17:12.250
There is a device doing things I do not expect.
00:17:12.250 --> 00:17:19.850
And you get a result as a really good comprehensive report that can also be read
00:17:19.850 --> 00:17:24.770
and interpreted by, let's say, a non expert, somebody not from the field of cybersecurity.
00:17:25.250 --> 00:17:31.410
At the end, Michael, let's talk about your favorite security features apps when it
00:17:31.410 --> 00:17:33.010
comes to control X core.
00:17:33.010 --> 00:17:39.370
I would say one of the biggest features that I really like is the flexibility and the
00:17:39.370 --> 00:17:43.610
choices that I have when using Control X OS in this case.
00:17:43.610 --> 00:17:49.370
So, for example, with the security apps, I can install Control X OS on my device or I
00:17:49.370 --> 00:17:53.490
take a Control X Core and then I can decide what I'm going to do with it.
00:17:53.650 --> 00:17:59.090
For example, I could decide I take the security scanner and I use this to make
00:17:59.090 --> 00:18:01.050
an inventory of my machine.
00:18:01.050 --> 00:18:06.170
So then I have a nice looking, easy readable report even for somebody
00:18:06.170 --> 00:18:07.610
which is not a security expert.
00:18:07.610 --> 00:18:13.650
And I'm very quickly able to determine whether I might have a problem in my machine or not.
00:18:13.650 --> 00:18:16.370
So it's extremely simple to fulfill such a use case.
00:18:16.370 --> 00:18:20.290
And Sebastian, what are your favorite security features or apps?
00:18:20.850 --> 00:18:25.730
I think my highlight is actually how nicely it integrates and how good the
00:18:25.730 --> 00:18:28.770
ease of use over all ease of use still is of the system.
00:18:28.770 --> 00:18:34.050
Often I hear the misconception that security would be bad for also for the
00:18:34.050 --> 00:18:37.650
performance of a system or it would be bad for the usability of the system.
00:18:37.650 --> 00:18:42.850
And I think my highlight is that it really nicely integrates in the overall
00:18:42.850 --> 00:18:46.330
experience without getting in your way of being productive.
00:18:46.330 --> 00:18:47.650
Thank you.
00:18:47.650 --> 00:18:48.650
That is a good ending.
00:18:48.650 --> 00:18:49.490
Thanks a lot, Michael.
00:18:49.490 --> 00:18:50.690
Thanks a lot, Sebastian.
00:18:51.050 --> 00:18:55.610
For talking, for explaining us Cyber Security, Cyber Resilience Act and
00:18:55.610 --> 00:18:59.770
everything around this whole big topic when it comes to industrial automation.
00:18:59.770 --> 00:19:00.330
Thanks a lot.
00:19:00.330 --> 00:19:01.010
Thank you.
00:19:01.010 --> 00:19:01.610
It was a pleasure
00:19:01.610 --> 00:19:02.410
Thank you, Robert.
00:19:02.410 --> 00:19:05.770
[MUSIC PLAYING]
00:19:05.770 --> 00:19:09.110
[MUSIC PLAYING]
00:19:09.110 --> 00:19:11.110
[music fades out]
00:19:11.110 --> 00:19:14.110
[Choir Chimes]