WEBVTT
Language: en-US

1
00:00:02.680 --> 00:00:05.199
<v Jonas Norinder>So, welcome back to Digitalization Tech
Talks.

2
00:00:05.440 --> 00:00:09.220
<v Jonas Norinder>As always, your hosts are Don Mack and
myself, Jonas Navinder.

3
00:00:09.560 --> 00:00:15.000
<v Jonas Norinder>And today we're kicking off a special
two-part series on the realities of IT and OT

4
00:00:15.000 --> 00:00:19.510
<v Jonas Norinder>convergence and what new research is
showing about the current state of industrial

5
00:00:19.510 --> 00:00:20.319
<v Jonas Norinder>cybersecurity.

6
00:00:21.170 --> 00:00:24.969
<v Jonas Norinder>In this first episode, we're going to look
at major research efforts that are

7
00:00:24.969 --> 00:00:30.250
<v Jonas Norinder>focused on what's actually happening
across industrial environments in a paper

8
00:00:30.250 --> 00:00:35.330
<v Jonas Norinder>that's titled Intelligence Driven Active
Defense, Securing Operational Technology

9
00:00:35.330 --> 00:00:36.009
<v Jonas Norinder>Environments.

10
00:00:36.689 --> 00:00:42.090
<v Jonas Norinder>The researchers of this paper analyzed a
large amount of real world activity and

11
00:00:42.090 --> 00:00:45.909
<v Jonas Norinder>insights from past incidents, and one
theme stood out.

12
00:00:46.209 --> 00:00:52.189
<v Jonas Norinder>A lot happens long before an attack ever
reaches the plant floor, and too often

13
00:00:52.189 --> 00:00:56.049
<v Jonas Norinder>organizations miss those early warning
signs, even though they can make a huge

14
00:00:56.049 --> 00:00:58.349
<v Jonas Norinder>difference in potentially limiting the
impact.

15
00:00:59.240 --> 00:01:04.150
<v Jonas Norinder>We'll talk about what the data reveals
about why issues are happening at scale, the

16
00:01:04.150 --> 00:01:09.400
<v Jonas Norinder>early attacker behaviors that show up well
before crisis, and how organizations can

17
00:01:09.400 --> 00:01:13.099
<v Jonas Norinder>strengthen their defenses using the
framework that came out of this work.

18
00:01:14.029 --> 00:01:18.349
<v Jonas Norinder>Then in our March episode, part two of the
cybersecurity series, we'll bring back

19
00:01:18.349 --> 00:01:23.790
<v Jonas Norinder>Marco Ayala to show the practical industry
perspective, what OT teams are dealing

20
00:01:23.790 --> 00:01:29.029
<v Jonas Norinder>with day to day, where the blind spots
usually are, and how IT and OT convergence is

21
00:01:29.029 --> 00:01:32.970
<v Jonas Norinder>creating new challenges that many
organizations are still trying to manage.

22
00:01:33.470 --> 00:01:39.150
<v Jonas Norinder>But before we meet today's guests, and
yes, I did pluralize guests, as well as the

23
00:01:39.150 --> 00:01:42.489
<v Jonas Norinder>research behind all this, Don, I'll hand
it over to you.

24
00:01:43.010 --> 00:01:45.110
<v Jonas Norinder>Why do you think this conversation matters
right now?

25
00:01:46.489 --> 00:01:48.569
<v Speaker 2>Jonas, uh, I have a couple of thoughts on
this.

26
00:01:48.680 --> 00:01:52.379
<v Speaker 2>Uh, first, I think the approach we're
taking on this two-part series is a perfect

27
00:01:52.379 --> 00:01:53.919
<v Speaker 2>fit for our podcast series.

28
00:01:54.330 --> 00:01:58.000
<v Speaker 2>We like to look at the learnings from the
recent past to share with our process

29
00:01:58.000 --> 00:02:01.400
<v Speaker 2>industries' audience because it might be
useful for their own applications.

30
00:02:01.809 --> 00:02:05.569
<v Speaker 2>Often we're looking at a specific example
with one company, so it'll be really

31
00:02:05.569 --> 00:02:08.600
<v Speaker 2>interesting today, I think, to hear about
the information gathered across many

32
00:02:08.600 --> 00:02:09.149
<v Speaker 2>companies.

33
00:02:09.539 --> 00:02:13.970
<v Speaker 2>And specifically on the topic of
cybersecurity, I think we both agree that it's

34
00:02:13.970 --> 00:02:17.399
<v Speaker 2>becoming an increasingly prevalent issue
as we move forward.

35
00:02:17.740 --> 00:02:21.820
<v Speaker 2>The deployment of new technology should
consider the potential for cyberattacks.

36
00:02:21.899 --> 00:02:25.479
<v Speaker 2>So I'm eager to learn from the research
that's been conducted by our guests.

37
00:02:26.830 --> 00:02:28.050
<v Jonas Norinder>Yes, me too, Don.

38
00:02:28.380 --> 00:02:30.380
<v Jonas Norinder>So, today we have a full house.

39
00:02:30.550 --> 00:02:33.410
<v Jonas Norinder>Never before have we had 3 guests on the
show.

40
00:02:33.869 --> 00:02:38.710
<v Jonas Norinder>So, I have the pleasure of introducing
Adam Robbie, the head of threat research at

41
00:02:38.710 --> 00:02:44.830
<v Jonas Norinder>Palo Alto Networks, Brianjan Sharma,
senior key expert for security services at

42
00:02:44.830 --> 00:02:49.509
<v Jonas Norinder>Siemens, and Tilo Pinkat, also with
Siemens, is senior Director for Business

43
00:02:49.509 --> 00:02:53.309
<v Jonas Norinder>Development and Innovation Management for
the Cybersecurity Research Group.

44
00:02:53.750 --> 00:02:55.190
<v Jonas Norinder>So gentlemen, welcome to the show.

45
00:02:55.309 --> 00:02:58.210
<v Jonas Norinder>It's a real pleasure having all of you on
the podcast today.

46
00:03:00.320 --> 00:03:01.410
<v Tilo>Nice being with you.

47
00:03:02.729 --> 00:03:04.039
<v Speaker 4>Thank you for inviting us.

48
00:03:04.889 --> 00:03:05.750
<v Speaker 4>Thanks for having us.

49
00:03:06.889 --> 00:03:07.639
<v Jonas Norinder>Fantastic.

50
00:03:07.770 --> 00:03:09.389
<v Jonas Norinder>So, why don't we get to it?

51
00:03:09.770 --> 00:03:13.889
<v Jonas Norinder>I want to point the first question or
direct the first question to you, Tilo.

52
00:03:14.449 --> 00:03:19.070
<v Jonas Norinder>Could you tell us about what prompted this
collaboration between Palo Alto Networks

53
00:03:19.289 --> 00:03:24.270
<v Jonas Norinder>and Siemens and also provide insights on
how you combined the latest research paper

54
00:03:24.270 --> 00:03:30.970
<v Jonas Norinder>with Idaho National Laboratory, and also
why was now the right time to initiate and

55
00:03:30.970 --> 00:03:32.270
<v Jonas Norinder>release this type of research?

56
00:03:35.130 --> 00:03:40.820
<v Tilo>That's a really good part because we
started the whole collaboration with Palo Alto

57
00:03:40.820 --> 00:03:45.419
<v Tilo>Networks and Siemens a couple of years ago
and actually all goes back already to

58
00:03:45.419 --> 00:03:46.600
<v Tilo>2018.

59
00:03:47.399 --> 00:03:54.380
<v Tilo>And then it deepened and a lot of products
and services got integrated and also

60
00:03:54.380 --> 00:04:00.940
<v Tilo>if you look into the latest more Up
to-date partnership

61
00:04:00.940 --> 00:04:05.470
<v Tilo>events, um, being there on, on, on stages
together, so we really work closely to

62
00:04:05.470 --> 00:04:10.039
<v Tilo>defend and protect uh to defend all the
attackers and protect our customers.

63
00:04:10.110 --> 00:04:16.920
<v Tilo>So it's really working great to have this
collaboration and, Already around 2 years

64
00:04:16.920 --> 00:04:23.239
<v Tilo>ago, I think it was on Adam Robbie who got
in more close contact with us and also um

65
00:04:23.239 --> 00:04:28.760
<v Tilo>for Prianshan, they both started to say
like, hey, besides our close commercial

66
00:04:28.760 --> 00:04:34.640
<v Tilo>collaboration part, why don't we go deeper
into our research part because both of

67
00:04:34.640 --> 00:04:39.820
<v Tilo>the companies, Palo Alto Networks and
Siemens, having a dedicated research

68
00:04:40.600 --> 00:04:41.140
<v Tilo>department.

69
00:04:41.630 --> 00:04:45.739
<v Tilo>We have it for all the cybersecurity and
Palo Alto have it for all the threat

70
00:04:45.739 --> 00:04:46.130
<v Tilo>research.

71
00:04:46.140 --> 00:04:51.480
<v Tilo>And so it started actually that we
released the first white paper together last

72
00:04:51.480 --> 00:04:58.320
<v Tilo>January in 2025 and now this year it was
time again to come up with a

73
00:04:58.320 --> 00:05:01.540
<v Tilo>follow up of that one and going even
deeper and doing even more.

74
00:05:01.959 --> 00:05:07.600
<v Tilo>And for doing even more, I hand this over
to Adam because it was on Adam to increase

75
00:05:07.600 --> 00:05:09.700
<v Tilo>the input for the new white paper.

76
00:05:10.269 --> 00:05:12.130
<v Tilo>With the Idaho National Labs.

77
00:05:13.450 --> 00:05:19.790
<v Adam Robbie>Thanks, Tilo, and it's really been a very
great pleasure working with uh Siemens in

78
00:05:19.790 --> 00:05:26.679
<v Adam Robbie>the past couple of years and this
collaboration is um very important

79
00:05:26.679 --> 00:05:33.500
<v Adam Robbie>for us as Tilo mentioned that um we are
deepening our uh partnership and

80
00:05:33.500 --> 00:05:36.799
<v Adam Robbie>on the uh threat research level and.

81
00:05:37.320 --> 00:05:43.799
<v Adam Robbie>Having also a third partner like uh INL
and a special thanks to Scott Pond

82
00:05:43.799 --> 00:05:49.980
<v Adam Robbie>for uh being also one of the main authors
helping us to make this happen.

83
00:05:50.690 --> 00:05:56.559
<v Adam Robbie>Uh, it did help to increase the value and
the insight that we are seeing in, um, in

84
00:05:56.559 --> 00:05:59.920
<v Adam Robbie>the research and bringing more value to
our readers as well.

85
00:06:02.390 --> 00:06:03.390
<v Speaker 2>Thanks, Tilo and Adam.

86
00:06:03.429 --> 00:06:04.429
<v Speaker 2>That was a great introduction.

87
00:06:04.510 --> 00:06:06.109
<v Speaker 2>Good to hear about this collaboration.

88
00:06:06.309 --> 00:06:08.529
<v Speaker 2>Uh, Pre, perhaps you can take this next
question.

89
00:06:09.109 --> 00:06:12.750
<v Speaker 2>What were you hoping to learn about the
state of industrial cyber risks when you set

90
00:06:12.750 --> 00:06:13.850
<v Speaker 2>out to do this work?

91
00:06:16.730 --> 00:06:18.619
<v Speaker 4>Um, thanks, John, for the question.

92
00:06:19.359 --> 00:06:25.119
<v Speaker 4>Uh, so, with our work, we weren't trying
to prove that OT risks exist, because

93
00:06:25.130 --> 00:06:27.600
<v Speaker 4>that's kind of already established.

94
00:06:28.100 --> 00:06:33.000
<v Speaker 4>We're trying to move past that headline
and understand what the risk actually looks

95
00:06:33.000 --> 00:06:38.200
<v Speaker 4>like on the ground, and how these cyber
risks show up and behaves inside real

96
00:06:38.200 --> 00:06:39.579
<v Speaker 4>industrial environments.

97
00:06:40.119 --> 00:06:45.079
<v Speaker 4>Now, there's a lot of narrative around
industrial cyber threats like nation states,

98
00:06:45.239 --> 00:06:47.279
<v Speaker 4>targeted disruption, ransomware.

99
00:06:47.970 --> 00:06:53.739
<v Speaker 4>But no large scale empirical data behind
those conversations and compared to IT

100
00:06:53.739 --> 00:06:58.380
<v Speaker 4>there aren't many well documented cyber
incidents we can reference when we talk

101
00:06:58.380 --> 00:07:02.179
<v Speaker 4>about industrial environments, and there
are several reasons for that, but that's a

102
00:07:02.179 --> 00:07:03.420
<v Speaker 4>whole separate discussion.

103
00:07:03.899 --> 00:07:08.579
<v Speaker 4>What we focused on instead were a few
practical questions, um, like.

104
00:07:08.899 --> 00:07:11.329
<v Speaker 4>What kind of threats are actually hitting
OT networks?

105
00:07:11.619 --> 00:07:16.760
<v Speaker 4>Is it mostly random noise, or are we
seeing structured intentional attack behavior?

106
00:07:17.179 --> 00:07:20.500
<v Speaker 4>How does the observed activity map to an
industrial attack chain?

107
00:07:20.779 --> 00:07:25.059
<v Speaker 4>Where does it typically begin and how far
it can realistically progress?

108
00:07:25.660 --> 00:07:29.880
<v Speaker 4>Uh, another one was, were organizations
blind in terms of detection capabilities?

109
00:07:30.100 --> 00:07:35.579
<v Speaker 4>And finally, like, what telemetry is truly
required to detect these threats, not in

110
00:07:35.579 --> 00:07:37.859
<v Speaker 4>theory, but based on what we're actually
seeing.

111
00:07:38.369 --> 00:07:43.899
<v Speaker 4>And what we learned is that OT
environments are definitely not invisible to

112
00:07:43.899 --> 00:07:46.320
<v Speaker 4>attackers, and they're far from quiet.

113
00:07:46.660 --> 00:07:51.730
<v Speaker 4>There's a significant amount of risky
activities happening inside these networks,

114
00:07:52.019 --> 00:07:56.619
<v Speaker 4>and more importantly, there's a noticeable
gap between monitoring coverage and the

115
00:07:56.619 --> 00:07:59.679
<v Speaker 4>actual level of exposure organizations
have in place.

116
00:08:01.959 --> 00:08:06.959
<v Jonas Norinder>So, I think it sounds like a very sound
approach to study real risks based on actual

117
00:08:06.959 --> 00:08:07.420
<v Jonas Norinder>data.

118
00:08:07.720 --> 00:08:13.640
<v Jonas Norinder>So, based on all this data that you
gathered and you analyzed, when you looked at

119
00:08:13.640 --> 00:08:18.279
<v Jonas Norinder>activity happening across these industrial
environments, what was it that stood out

120
00:08:18.279 --> 00:08:22.140
<v Jonas Norinder>most about the kinds of risks that
organizations are facing today?

121
00:08:23.859 --> 00:08:30.220
<v Adam Robbie>So here is the breakdown of what stood out
for us in these uh analysis, and I would

122
00:08:30.220 --> 00:08:37.140
<v Adam Robbie>say the top three, main point or one is
what we call like the well

123
00:08:37.140 --> 00:08:37.500
<v Adam Robbie>time.

124
00:08:38.299 --> 00:08:43.849
<v Adam Robbie>Where We try to know or understand how
long it takes from.

125
00:08:45.140 --> 00:08:51.500
<v Adam Robbie>The initial access for a threat actor or
adversary that comes in the network or

126
00:08:51.500 --> 00:08:57.609
<v Adam Robbie>comes to the environment all the way until
it has a huge impact or they completely

127
00:08:57.609 --> 00:09:03.559
<v Adam Robbie>complete successfully their mission of
disruption or ransomware or whatever their

128
00:09:04.179 --> 00:09:04.880
<v Adam Robbie>purpose are.

129
00:09:05.219 --> 00:09:11.859
<v Adam Robbie>And as you're going to read in the on the
paper, you will see it's it takes like 80%

130
00:09:11.859 --> 00:09:18.739
<v Adam Robbie>of the adversary activities are happening
before their impact, and

131
00:09:18.739 --> 00:09:22.500
<v Adam Robbie>it takes around 185 days to do that.

132
00:09:23.659 --> 00:09:30.640
<v Adam Robbie>Then the second part also was very
interesting is the The mystery about

133
00:09:30.640 --> 00:09:37.429
<v Adam Robbie>the air gap, we hear sometimes clients or
some companies, they will say like,

134
00:09:37.760 --> 00:09:43.880
<v Adam Robbie>we don't have that problem or this is
threats are not going to impact us because we

135
00:09:43.880 --> 00:09:46.080
<v Adam Robbie>are air gapped, then.

136
00:09:46.830 --> 00:09:52.030
<v Adam Robbie>What we did, we looked, we scanned, like,
what can we see from outside, what

137
00:09:52.030 --> 00:09:54.590
<v Adam Robbie>devices, what OT devices are exposed.

138
00:09:55.669 --> 00:10:01.510
<v Adam Robbie>And we can identify around 20 million OT
related devices are exposed to the

139
00:10:01.510 --> 00:10:01.650
<v Adam Robbie>internet.

140
00:10:01.669 --> 00:10:06.969
<v Adam Robbie>That includes a systems like an HVAC
system and building management system, and

141
00:10:07.179 --> 00:10:13.989
<v Adam Robbie>those systems, even though they may not
sound like our manufacturing devices, but

142
00:10:13.989 --> 00:10:16.869
<v Adam Robbie>those systems also are crucial in some
environment.

143
00:10:16.950 --> 00:10:20.809
<v Adam Robbie>If HUVAC goes down or the building
management system gets locked, right?

144
00:10:21.840 --> 00:10:26.880
<v Adam Robbie>And also we have seen a huge increment
from the last white paper to this white paper

145
00:10:26.880 --> 00:10:31.020
<v Adam Robbie>on how many devices are exposed, OT
devices exposed to the internet.

146
00:10:32.520 --> 00:10:39.229
<v Adam Robbie>Then the, the last part, which is one of
my very interesting points, is the

147
00:10:39.229 --> 00:10:42.320
<v Adam Robbie>age of the CVEs that's being exploited.

148
00:10:43.239 --> 00:10:46.239
<v Adam Robbie>We talk a lot about legacy systems.

149
00:10:46.940 --> 00:10:48.609
<v Adam Robbie>And we know it's a risk.

150
00:10:48.739 --> 00:10:49.880
<v Adam Robbie>You have a legacy system.

151
00:10:50.140 --> 00:10:51.729
<v Adam Robbie>It's not bad, you know.

152
00:10:51.859 --> 00:10:57.099
<v Adam Robbie>We talk also about how many CVEs or
vulnerabilities can exist in our environment.

153
00:10:57.710 --> 00:11:03.070
<v Adam Robbie>That's also an important topic, but what's
really high or critical topic we are

154
00:11:03.070 --> 00:11:09.820
<v Adam Robbie>talking about now is that these CVEs and
legacy systems are being exploited,

155
00:11:10.030 --> 00:11:16.590
<v Adam Robbie>are actively under attack, and we have
seen over like 50% of these

156
00:11:16.590 --> 00:11:21.289
<v Adam Robbie>CVEs that are under attack are aged
between 6 to 10 years old.

157
00:11:21.590 --> 00:11:27.049
<v Adam Robbie>Even worse than that, there's 15% are 16
to 20 years old.

158
00:11:27.859 --> 00:11:34.280
<v Adam Robbie>So, those brings back to the conversation,
legacy systems still exist, air gap is

159
00:11:34.280 --> 00:11:37.760
<v Adam Robbie>not is a mess, and you have time to
protect your environment.

160
00:11:39.789 --> 00:11:44.309
<v Speaker 2>A couple of good points, Adam, there, um,
relative to A lot of things to watch out

161
00:11:44.309 --> 00:11:47.270
<v Speaker 2>for, but good to know that there's a
window of time that that could be addressed up

162
00:11:47.270 --> 00:11:47.630
<v Speaker 2>front.

163
00:11:47.989 --> 00:11:50.270
<v Speaker 2>Um, Adam, if we can continue, I have
another question for you.

164
00:11:50.510 --> 00:11:55.789
<v Speaker 2>I understand your studies included
analysis of over 60,000 firewalls in correlation

165
00:11:55.789 --> 00:12:00.900
<v Speaker 2>with, uh, Idaho National Labs research of
two decades of industrial incidents.

166
00:12:01.390 --> 00:12:07.289
<v Speaker 2>What did that long-term view reveal about
how attacks usually unfold and why

167
00:12:07.289 --> 00:12:09.929
<v Speaker 2>organizations sometimes struggle to spot
the warning signs early?

168
00:12:11.340 --> 00:12:16.900
<v Adam Robbie>So this is a really great question, like
to dive deeper about like what we have seen

169
00:12:16.900 --> 00:12:18.599
<v Adam Robbie>and why that struggle.

170
00:12:18.859 --> 00:12:20.179
<v Adam Robbie>I will answer in two points.

171
00:12:20.260 --> 00:12:26.130
<v Adam Robbie>The first one is the anatomy of the slow
motion of the attack, right?

172
00:12:26.419 --> 00:12:29.179
<v Adam Robbie>What are the TTPs we are seeing?

173
00:12:29.469 --> 00:12:33.380
<v Adam Robbie>Um, that's been used in these incidents.

174
00:12:33.460 --> 00:12:37.510
<v Adam Robbie>So what we did, we took a few billions of
signatures that's fired on those

175
00:12:37.510 --> 00:12:44.090
<v Adam Robbie>firewalls, and we mapped them to miter
TTPs, and we identified a lots of TTPs

176
00:12:44.349 --> 00:12:48.190
<v Adam Robbie>are very similar to living on the land
techniques.

177
00:12:48.710 --> 00:12:53.549
<v Adam Robbie>And these shiftings from previous
techniques we have seen in the past like remote

178
00:12:53.549 --> 00:12:59.309
<v Adam Robbie>access or privilege escalation, some
techniques are easy to spot, but others are

179
00:12:59.309 --> 00:13:05.489
<v Adam Robbie>very difficult because they seem legit,
but it's still gets hidden in the traffic.

180
00:13:05.989 --> 00:13:11.590
<v Adam Robbie>Like an example for that, like a command
line interface, a CLI that could be used to

181
00:13:11.590 --> 00:13:13.169
<v Adam Robbie>execute some commands well.

182
00:13:13.559 --> 00:13:17.239
<v Adam Robbie>It's very difficult to know if this
command is legit or malicious if you don't have

183
00:13:17.239 --> 00:13:23.349
<v Adam Robbie>a really great visibility, and you also
identify who is doing what and who's

184
00:13:23.349 --> 00:13:28.659
<v Adam Robbie>authorized to do what on these devices,
especially like in OT environment, it's a

185
00:13:28.659 --> 00:13:35.599
<v Adam Robbie>little bit easy to do that than IT because
you have some expectations, you have

186
00:13:35.599 --> 00:13:38.960
<v Adam Robbie>some more realistic expectation what to
expect from these devices.

187
00:13:39.000 --> 00:13:45.150
<v Adam Robbie>If you have an engineering workstation on
a Windows machine, you Know what to

188
00:13:45.150 --> 00:13:47.820
<v Adam Robbie>expect, what happened or what behavior to
expect from these uh machine.

189
00:13:50.159 --> 00:13:53.770
<v Adam Robbie>And then you're talking about like the
background noise problem, right?

190
00:13:53.890 --> 00:13:58.159
<v Adam Robbie>So techniques like the native API
execution, the standard application layer for

191
00:13:58.159 --> 00:14:03.979
<v Adam Robbie>command control, those also without like
OT specific analytics, these malicious

192
00:14:03.979 --> 00:14:09.640
<v Adam Robbie>actions look like a routine software
update or a standard server query.

193
00:14:09.880 --> 00:14:16.880
<v Adam Robbie>Those again are very Challenging point to
capture and of course the last thing

194
00:14:16.880 --> 00:14:21.760
<v Adam Robbie>which is similar to what I talked about is
the the the concept of air gap.

195
00:14:22.320 --> 00:14:28.919
<v Adam Robbie>Sometimes operators or asset owners, they
may take this for granted, we are air gap,

196
00:14:29.159 --> 00:14:33.090
<v Adam Robbie>so we don't need to monitor, we don't need
to worry so much about what's going on.

197
00:14:33.929 --> 00:14:39.210
<v Jonas Norinder>So, as part of the research, you also
outlined an approach that organizations can

198
00:14:39.210 --> 00:14:43.929
<v Jonas Norinder>use to strengthen their defense against
some of these things that are maybe not so

199
00:14:43.929 --> 00:14:47.890
<v Jonas Norinder>visible and that might need a little bit
more research to figure out what's really

200
00:14:47.890 --> 00:14:48.510
<v Jonas Norinder>going on.

201
00:14:49.250 --> 00:14:53.599
<v Jonas Norinder>Tilo, can you walk us through how that
came together and what makes it practical for

202
00:14:53.599 --> 00:14:55.150
<v Jonas Norinder>teams in the process industries?

203
00:14:56.409 --> 00:15:02.690
<v Tilo>Yes, we looked into the topic and we also
looked at how we both are set up for this

204
00:15:02.690 --> 00:15:03.809
<v Tilo>from our own perspective.

205
00:15:03.890 --> 00:15:09.000
<v Tilo>For example, how Palo Alto is tackling it
for its own topics, how Siemens is going

206
00:15:09.000 --> 00:15:14.210
<v Tilo>in there for the for its own topics to
secure Siemens, and also what we bring to our

207
00:15:14.210 --> 00:15:19.369
<v Tilo>customers, and we combined it all with
this research results we have here.

208
00:15:19.780 --> 00:15:24.289
<v Tilo>So we gotten to the point that we said,
Through the threat analysis, through all the

209
00:15:24.289 --> 00:15:30.330
<v Tilo>threat research combined with the
predictive insights, we generate some nice

210
00:15:30.330 --> 00:15:32.760
<v Tilo>results, but who needs to handle these
results?

211
00:15:32.770 --> 00:15:38.450
<v Tilo>And there really came our point that we
have been diving into the topic around the

212
00:15:38.450 --> 00:15:44.710
<v Tilo>OTSOC, so a real good secure operational
center for OT specific topics.

213
00:15:45.250 --> 00:15:48.770
<v Tilo>And then we analyzed what we can do about
this point specifically.

214
00:15:48.929 --> 00:15:54.590
<v Tilo>So how could we set it up in a way That it
becomes easier to handle that it becomes

215
00:15:54.590 --> 00:16:01.190
<v Tilo>also more understandable in terms of where
are the interactions between IT and OT

216
00:16:01.190 --> 00:16:03.830
<v Tilo>and where the OTO should really focus on.

217
00:16:04.159 --> 00:16:08.710
<v Tilo>So we did some analysis on that as well
and then we came up with a recommended

218
00:16:08.710 --> 00:16:14.510
<v Tilo>framework to actually include our results
from the research and the predictive

219
00:16:14.510 --> 00:16:17.330
<v Tilo>insights and come up with an OTSOC
framework.

220
00:16:18.179 --> 00:16:19.130
<v Tilo>What could handle that.

221
00:16:19.169 --> 00:16:23.289
<v Tilo>And that's the whole idea where we say
like if you have all that insights and you

222
00:16:23.289 --> 00:16:28.409
<v Tilo>have some time to deal with it until you
need to react because you know the travel

223
00:16:28.409 --> 00:16:35.159
<v Tilo>time and you know the average age of the
CVEs, basically you also have time to set

224
00:16:35.159 --> 00:16:41.770
<v Tilo>up an OTSOC and I think that the times on
how to walk us through that and um how how

225
00:16:41.780 --> 00:16:45.280
<v Tilo>how fast it can be to have a certain setup
of OTSOCriansion is coming later to that.

226
00:16:47.960 --> 00:16:53.039
<v Tilo>And for us it was really an idea on how to
set it up because there are many papers

227
00:16:53.039 --> 00:16:58.400
<v Tilo>around OTSOC and there is a lot of input
and we thought we really need to focus on

228
00:16:58.659 --> 00:17:03.559
<v Tilo>some guiding principles on a on a clear
vision about it, especially the safety first

229
00:17:03.559 --> 00:17:08.209
<v Tilo>topic for OTSOC, but we also dive very
much into the topic on how to handle

230
00:17:08.209 --> 00:17:14.239
<v Tilo>governance and operating model around
behind it and That is a clear

231
00:17:14.818 --> 00:17:15.698
<v Tilo>interpretation.

232
00:17:15.909 --> 00:17:20.098
<v Tilo>So if you're going to have a look into the
white paper, you see, for example, where

233
00:17:20.098 --> 00:17:23.279
<v Tilo>we draw a line for a line for joint
accountability.

234
00:17:23.698 --> 00:17:27.979
<v Tilo>And this line for joint accountability was
one thing for us where we really said

235
00:17:27.979 --> 00:17:28.438
<v Tilo>yes.

236
00:17:29.530 --> 00:17:31.420
<v Tilo>Below that, it's all about OT stock.

237
00:17:31.520 --> 00:17:34.099
<v Tilo>You really need to understand your process
levels.

238
00:17:34.140 --> 00:17:37.780
<v Tilo>You really need to understand how your
historians are working, what they are

239
00:17:37.780 --> 00:17:42.459
<v Tilo>producing, what locks they are doing, how
that can interchange and actually bring

240
00:17:42.459 --> 00:17:46.260
<v Tilo>context and what you need to measure and
which KPIs you can result from that.

241
00:17:46.699 --> 00:17:53.650
<v Tilo>And then going up to different levels, you
come to the DMC and with the DMC you are

242
00:17:53.650 --> 00:17:57.319
<v Tilo>coming to this joint accountability issue
and we draw.

243
00:17:57.810 --> 00:18:03.469
<v Tilo>A whole circle around it because we said
like if you set it up there's always a next

244
00:18:03.469 --> 00:18:07.180
<v Tilo>step to develop it a little bit further,
do it a little bit better, etc.

245
00:18:07.219 --> 00:18:07.819
<v Tilo>etc.

246
00:18:08.219 --> 00:18:13.579
<v Tilo>and it all needs to be guided by the same
principles and still needs to be evolving

247
00:18:13.579 --> 00:18:14.949
<v Tilo>because all the threats are evolving.

248
00:18:14.979 --> 00:18:17.969
<v Tilo>So this is our way of going forward with
that.

249
00:18:18.060 --> 00:18:20.650
<v Tilo>That is the way we say like this is our
recommendation.

250
00:18:21.709 --> 00:18:26.550
<v Tilo>And to bring all that what we have done
here together into the point and saying play

251
00:18:26.550 --> 00:18:29.069
<v Tilo>active defense with DOToC.

252
00:18:29.310 --> 00:18:36.069
<v Tilo>Once you have the OT sock there, it's
really about you can be proactive from day one

253
00:18:36.469 --> 00:18:41.349
<v Tilo>because you have time to learn from the,
from everything you've got from the

254
00:18:41.349 --> 00:18:45.670
<v Tilo>predictive analysis, and then you can
think about how to set things up and learn

255
00:18:45.670 --> 00:18:46.089
<v Tilo>from it.

256
00:18:46.510 --> 00:18:49.160
<v Tilo>And while you're there, you have your time
to react.

257
00:18:50.500 --> 00:18:53.689
<v Tilo>And then you're not just reactive, you
really are proactive with the OTSOC

258
00:18:53.689 --> 00:18:58.979
<v Tilo>framework, and you have all your time to
also work on your compliance topics and set

259
00:18:58.979 --> 00:18:59.439
<v Tilo>this all up.

260
00:18:59.500 --> 00:19:04.979
<v Tilo>So that's what we combined and that is the
way we say we should put forward for all

261
00:19:04.979 --> 00:19:07.459
<v Tilo>the organizations on strengthening their
defenses.

262
00:19:09.609 --> 00:19:11.510
<v Speaker 2>So, quite a bit to consider here.

263
00:19:11.579 --> 00:19:15.319
<v Speaker 2>And Pre, maybe, uh, Tito had mentioned you
were gonna cover this coming up, so maybe

264
00:19:15.319 --> 00:19:16.520
<v Speaker 2>we can talk about that now.

265
00:19:16.849 --> 00:19:20.290
<v Speaker 2>Um, one of the things we like to talk
about for our, our listeners is, you know,

266
00:19:20.369 --> 00:19:22.589
<v Speaker 2>what are some of the steps they can take
to get started?

267
00:19:23.170 --> 00:19:27.150
<v Speaker 2>Could you share the best ways to learn
more about your work, explore the framework,

268
00:19:27.160 --> 00:19:30.589
<v Speaker 2>and, and begin applying some of these
insights inside their own companies?

269
00:19:32.239 --> 00:19:33.180
<v Speaker 4>Uh, definitely, Don.

270
00:19:33.780 --> 00:19:38.250
<v Speaker 4>So for listeners, they obviously need to
start with reading the white paper, but I

271
00:19:38.250 --> 00:19:44.760
<v Speaker 4>have like 3 practical steps, which can
help them take this white paper in and create

272
00:19:44.760 --> 00:19:47.400
<v Speaker 4>some actionable, uh, items from that.

273
00:19:47.520 --> 00:19:51.920
<v Speaker 4>So, the first one is, while you're reading
the white paper, uh, focus on the model,

274
00:19:52.030 --> 00:19:53.020
<v Speaker 4>not just the data.

275
00:19:53.560 --> 00:19:56.729
<v Speaker 4>The white paper isn't just about
publishing statistics.

276
00:19:57.000 --> 00:20:00.000
<v Speaker 4>It's about presenting like a working
defensive model.

277
00:20:00.339 --> 00:20:07.020
<v Speaker 4>The key takeaway is not that 332% increase
in exposed OD devices, but the

278
00:20:07.020 --> 00:20:12.439
<v Speaker 4>understanding that over 80% of adversary
behavior happened in the precursor phase

279
00:20:12.680 --> 00:20:14.839
<v Speaker 4>and long before the operational impact.

280
00:20:15.180 --> 00:20:19.260
<v Speaker 4>So the key here really is to understand
what this precursor phase looks like for

281
00:20:19.260 --> 00:20:20.219
<v Speaker 4>your organization.

282
00:20:21.270 --> 00:20:24.910
<v Speaker 4>Second, examine your own exposure versus
visibility.

283
00:20:25.189 --> 00:20:29.709
<v Speaker 4>The paper emphasizes on threat-informed
logging and not the log overload.

284
00:20:30.569 --> 00:20:34.359
<v Speaker 4>Use the attach chain models to prioritize
telemetry from systems.

285
00:20:34.569 --> 00:20:37.189
<v Speaker 4>You don't need every log from each and
every device.

286
00:20:37.369 --> 00:20:41.040
<v Speaker 4>Understand what matters the most from for
your tailored organization.

287
00:20:42.380 --> 00:20:46.560
<v Speaker 4>And third, start applying the OTSOC
framework incrementally.

288
00:20:46.819 --> 00:20:52.579
<v Speaker 4>You don't need a full redesign or
transform overnight, but use a phased roadmap

289
00:20:52.579 --> 00:20:53.859
<v Speaker 4>approach to the framework.

290
00:20:54.180 --> 00:20:58.699
<v Speaker 4>Look at your quick wins, look what you can
achieve with the current resources, and

291
00:20:58.699 --> 00:20:59.849
<v Speaker 4>then plan the next steps.

292
00:21:00.140 --> 00:21:05.479
<v Speaker 4>We do describe a 36 month journey for
ODSoC, but it's going to be different for each

293
00:21:05.479 --> 00:21:08.050
<v Speaker 4>organization as everyone is at different
maturity levels.

294
00:21:08.739 --> 00:21:14.069
<v Speaker 4>Now, But what doesn't change is the
guiding principles for that Otisoc.

295
00:21:14.920 --> 00:21:20.060
<v Speaker 4>And these guiding principles, I guess Tilo
hinted towards them earlier, but they

296
00:21:20.060 --> 00:21:22.500
<v Speaker 4>start with, what does Otisoc mean?

297
00:21:22.719 --> 00:21:28.250
<v Speaker 4>The One thing that OT prioritizes is
safety, and the safety first should be the

298
00:21:28.250 --> 00:21:29.520
<v Speaker 4>guiding principle of ODSOC.

299
00:21:30.130 --> 00:21:32.390
<v Speaker 4>It should be aligned with the business.

300
00:21:32.449 --> 00:21:37.609
<v Speaker 4>It should be aligned with the operational,
uh, continuance, operational readiness.

301
00:21:37.890 --> 00:21:40.209
<v Speaker 4>Uh, it should be complying to regulatory.

302
00:21:40.314 --> 00:21:45.944
<v Speaker 4>Frameworks wherever needed and complying
to industry standards, which are the

303
00:21:45.944 --> 00:21:49.114
<v Speaker 4>organization is following, there should be
defense in depth models followed.

304
00:21:49.435 --> 00:21:54.155
<v Speaker 4>Uh, there should be effective ITOT
integration, which also Tino mentioned is really

305
00:21:54.155 --> 00:21:56.655
<v Speaker 4>important to have this joint joint
accountability.

306
00:21:58.040 --> 00:22:03.579
<v Speaker 4>Now These are the top important things I
would ask the readers to keep in mind while

307
00:22:03.579 --> 00:22:07.500
<v Speaker 4>they're reading the white paper as they
provide like this essential context on how

308
00:22:07.500 --> 00:22:12.260
<v Speaker 4>the report should be applied in practice,
rather than simply reading it passively.

309
00:22:14.150 --> 00:22:14.869
<v Speaker 2>OK, thanks, Pree.

310
00:22:14.989 --> 00:22:16.410
<v Speaker 2>That's some good suggestions.

311
00:22:16.439 --> 00:22:20.280
<v Speaker 2>And, um, in the pre-release version of the
white paper, I had an opportunity to

312
00:22:20.280 --> 00:22:23.229
<v Speaker 2>read, you guys did a great job at the end
of kind of wrapping up with the

313
00:22:23.229 --> 00:22:25.359
<v Speaker 2>conclusions and bringing everything
together.

314
00:22:25.390 --> 00:22:27.479
<v Speaker 2>And, and in our podcast, we like to do the
same thing.

315
00:22:27.560 --> 00:22:29.660
<v Speaker 2>We like to end with some key takeaways.

316
00:22:30.079 --> 00:22:33.119
<v Speaker 2>So I'd like to ask if each of you, maybe
starting with Adam, could start out with

317
00:22:33.119 --> 00:22:37.160
<v Speaker 2>one clear takeaway that you'd like to
leave with our audience as we wrap up the

318
00:22:37.160 --> 00:22:37.300
<v Speaker 2>episode.

319
00:22:37.780 --> 00:22:38.599
<v Speaker 2>Adam, do you wanna start?

320
00:22:39.719 --> 00:22:40.199
<v Adam Robbie>Sure.

321
00:22:41.180 --> 00:22:45.780
<v Adam Robbie>What I would like to say is the biggest
shift we have seen is that OT security is no

322
00:22:45.780 --> 00:22:48.430
<v Adam Robbie>longer no longer a hidden problem.

323
00:22:48.500 --> 00:22:50.560
<v Adam Robbie>It is a visibility problem.

324
00:22:51.060 --> 00:22:56.280
<v Adam Robbie>Most adversary activities happen months
before operational impact.

325
00:22:56.619 --> 00:23:01.579
<v Adam Robbie>So if you can see what's happening on the
network edge, you still have time to

326
00:23:01.579 --> 00:23:02.099
<v Adam Robbie>intervene.

327
00:23:03.609 --> 00:23:06.489
<v Tilo>I think I also can add a point here.

328
00:23:06.810 --> 00:23:11.989
<v Tilo>For me, it's really about the whole
organizational setup.

329
00:23:12.609 --> 00:23:19.369
<v Tilo>So each company should define that and
always need to think about where to spend the

330
00:23:19.369 --> 00:23:24.250
<v Tilo>money because it's not just for production
improvements, it's really also for

331
00:23:24.250 --> 00:23:27.050
<v Tilo>securing everything and come to a
resilience level.

332
00:23:27.079 --> 00:23:29.189
<v Tilo>And therefore you need a proper
organization set up.

333
00:23:29.780 --> 00:23:36.209
<v Tilo>Which includes a very proper handover
process between the IT and the OT events

334
00:23:36.790 --> 00:23:38.589
<v Tilo>to have that covered properly.

335
00:23:40.079 --> 00:23:43.489
<v Speaker 4>From my point of view, most industrial
cyberattacks don't start with a physical

336
00:23:43.489 --> 00:23:48.569
<v Speaker 4>disruption, so don't wait around for
something to happen within your industrial

337
00:23:48.569 --> 00:23:49.079
<v Speaker 4>environment.

338
00:23:49.369 --> 00:23:52.550
<v Speaker 4>They start with observable precursor
behaviors.

339
00:23:52.770 --> 00:23:56.920
<v Speaker 4>If you can detect and act during that
early phase, you can change the outcomes

340
00:23:56.920 --> 00:23:57.430
<v Speaker 4>entirely.

341
00:23:58.310 --> 00:24:00.640
<v Jonas Norinder>Thank you for those last comment,
gentlemen.

342
00:24:00.719 --> 00:24:01.719
<v Jonas Norinder>I really appreciate it.

343
00:24:01.959 --> 00:24:06.719
<v Jonas Norinder>With that, we are going to wrap up part
one of our two-part series on IT and OT

344
00:24:06.719 --> 00:24:11.739
<v Jonas Norinder>convergence and the evolving state of
industrial cybersecurity, which seems to be

345
00:24:11.880 --> 00:24:13.260
<v Jonas Norinder>continuously evolving.

346
00:24:13.680 --> 00:24:16.219
<v Jonas Norinder>Thank you very much for walking us through
the research.

347
00:24:16.819 --> 00:24:21.099
<v Jonas Norinder>Some of the data and the framework behind
this white paper, I think there's a lot

348
00:24:21.099 --> 00:24:26.939
<v Jonas Norinder>for organizations to unpack from how early
attacker behavior shows up long before a

349
00:24:26.939 --> 00:24:32.219
<v Jonas Norinder>crisis to why defenders so often miss
them, to how the right approach at the network

350
00:24:32.219 --> 00:24:33.760
<v Jonas Norinder>edge can make a measurable difference.

351
00:24:33.859 --> 00:24:37.160
<v Jonas Norinder>So thank you very much to all three of you
for being on the show.

352
00:24:37.619 --> 00:24:38.540
<v Adam Robbie>Thanks for having us.

353
00:24:39.719 --> 00:24:42.699
<v Speaker 4>Yeah, thank you, and I'm looking forward
to this podcast.

354
00:24:43.760 --> 00:24:45.579
<v Tilo>It was really great being with you.

355
00:24:46.199 --> 00:24:46.599
<v Jonas Norinder>Awesome.

356
00:24:46.760 --> 00:24:52.239
<v Jonas Norinder>So, in part two, we are shifting from the
data insights and visibility from the

357
00:24:52.239 --> 00:24:54.819
<v Jonas Norinder>firewalls to the reality of the shop
floor.

358
00:24:55.180 --> 00:24:59.439
<v Jonas Norinder>We'll be joined by industry expert Marco
Ayala, who will give us the perspective

359
00:24:59.439 --> 00:25:00.500
<v Jonas Norinder>from the plant floor.

360
00:25:01.030 --> 00:25:05.859
<v Jonas Norinder>What OT teams are facing day to day, where
the biggest blind spots are, and how IT

361
00:25:05.859 --> 00:25:10.979
<v Jonas Norinder>and OT convergence is creating new
operational challenges that many organizations

362
00:25:10.979 --> 00:25:14.500
<v Jonas Norinder>are still trying to catch up with and
hopefully some of this research, research that

363
00:25:14.500 --> 00:25:16.869
<v Jonas Norinder>we talked about today can help with that
as well.

364
00:25:17.219 --> 00:25:22.260
<v Jonas Norinder>So make sure you come back to listen to
our next episode that drops on March

365
00:25:22.260 --> 00:25:23.079
<v Jonas Norinder>twenty-sixth.

366
00:25:23.520 --> 00:25:27.189
<v Jonas Norinder>And if you have any questions about any of
the topics we discussed here today,

367
00:25:27.359 --> 00:25:30.869
<v Jonas Norinder>please feel free to reach out to Adam, T
Li, and Prianjan.

368
00:25:31.160 --> 00:25:37.400
<v Jonas Norinder>We've included a link to both of their
emails and LinkedIn profiles as well in the

369
00:25:37.400 --> 00:25:38.040
<v Jonas Norinder>show notes.

370
00:25:38.280 --> 00:25:41.979
<v Jonas Norinder>Also go to the show notes to find a link
to the research paper.

371
00:25:42.199 --> 00:25:46.680
<v Jonas Norinder>As usual, Don and I are always open to
your comments, your thoughts, your feedback

372
00:25:46.680 --> 00:25:48.160
<v Jonas Norinder>on the show, or the topics.

373
00:25:48.239 --> 00:25:51.400
<v Jonas Norinder>You can also find our contact information
in the show notes.

374
00:25:51.719 --> 00:25:52.680
<v Jonas Norinder>We'd love to hear from you.

375
00:25:53.500 --> 00:25:57.900
<v Jonas Norinder>So if you liked what you heard today,
please help spread the word by rating the

376
00:25:57.900 --> 00:26:03.380
<v Jonas Norinder>show, and if you're not already a
subscriber and would like to be notified when new

377
00:26:03.380 --> 00:26:06.319
<v Jonas Norinder>episodes are released, please subscribe to
the series.

378
00:26:06.939 --> 00:26:10.979
<v Jonas Norinder>Thank you so much for listening to this
episode of Digitalization T Tech Talks.
