WEBVTT
Language: en-US

1
00:00:10.329 --> 00:00:14.029
<v Jon Lester>Hello and welcome to Buildings of
Tomorrow, your Smart Buildings podcast.

2
00:00:14.289 --> 00:00:19.469
<v Jon Lester>My name is Jon Lester, and in today's
episode, we are doing a buzzword buster about

3
00:00:19.469 --> 00:00:20.479
<v Jon Lester>cybersecurity.

4
00:00:20.569 --> 00:00:24.250
<v Jon Lester>Now, a buzzword buster in this episode, we
spend a little bit of time talking about

5
00:00:24.250 --> 00:00:29.409
<v Jon Lester>those industry terms, uh, some of the, the
words or the acronyms that you hear in

6
00:00:29.409 --> 00:00:32.729
<v Jon Lester>the industry about these specific topics
to try and make it a little bit easier for

7
00:00:32.729 --> 00:00:37.009
<v Jon Lester>you to understand what's going on and what
are people talking about in these topics.

8
00:00:37.090 --> 00:00:40.069
<v Jon Lester>And as I mentioned, today is all about
cybersecurity.

9
00:00:40.500 --> 00:00:43.540
<v Jon Lester>And I'm joined by Alina Matthewhina.

10
00:00:43.659 --> 00:00:50.419
<v Jon Lester>She is the cybersecurity manager of
building automation at Siemens, uh, building

11
00:00:50.419 --> 00:00:50.889
<v Jon Lester>products.

12
00:00:51.139 --> 00:00:53.159
<v Jon Lester>Uh, Alina, thank you very much for joining
us.

13
00:00:53.819 --> 00:00:54.380
<v Alina Matyukhina>Hi, John.

14
00:00:54.459 --> 00:00:55.110
<v Alina Matyukhina>Hi everyone.

15
00:00:55.259 --> 00:00:56.540
<v Alina Matyukhina>Thank you so much for inviting.

16
00:00:56.650 --> 00:01:02.060
<v Alina Matyukhina>I'm very happy to be in this podcast and
speak more about my favorite topic,

17
00:01:02.130 --> 00:01:03.220
<v Alina Matyukhina>cybersecurity.

18
00:01:03.630 --> 00:01:05.309
<v Jon Lester>And we're very, very happy to have you.

19
00:01:05.419 --> 00:01:10.069
<v Jon Lester>We've, we've had several conversations in
the past, uh, on different cybersecurity

20
00:01:10.069 --> 00:01:12.250
<v Jon Lester>topics, a lot about Bnet Secure Connect.

21
00:01:12.589 --> 00:01:17.389
<v Jon Lester>So thank you again for, for giving us your
time and expertise to do this buzzword

22
00:01:17.389 --> 00:01:17.790
<v Jon Lester>buster.

23
00:01:17.830 --> 00:01:23.750
<v Jon Lester>And if there is ever a topic that is just
loaded with buzzwords, it's cybersecurity,

24
00:01:23.830 --> 00:01:24.000
<v Jon Lester>right?

25
00:01:24.099 --> 00:01:26.150
<v Jon Lester>There are so many different things.

26
00:01:26.620 --> 00:01:31.750
<v Jon Lester>You know, from different types of, of
cybersecurity attacks right through to more

27
00:01:31.750 --> 00:01:36.169
<v Jon Lester>industry-specific topics that it's almost
impossible to keep, keep ahead of.

28
00:01:36.260 --> 00:01:37.970
<v Jon Lester>So, thank you so much for joining us.

29
00:01:37.980 --> 00:01:42.580
<v Jon Lester>We're going to focus a little bit more,
let's say, in our, our building industry,

30
00:01:42.669 --> 00:01:46.980
<v Jon Lester>let's call it, um, initially, uh, but I
could also imagine this is not the last time

31
00:01:46.980 --> 00:01:50.239
<v Jon Lester>we talk about buzzwords when it comes to
cybersecurity.

32
00:01:50.779 --> 00:01:52.000
<v Jon Lester>Now, Alina, are you ready?

33
00:01:52.550 --> 00:01:59.250
<v Jon Lester>Because we have a list of, of buzzwords
that we put together, um, and

34
00:01:59.650 --> 00:02:03.330
<v Jon Lester>there's a lot there, and we're going to,
we're going to keep your brain, your brain

35
00:02:03.330 --> 00:02:05.730
<v Jon Lester>running, keep your, the ideas flowing for
this one.

36
00:02:05.889 --> 00:02:08.850
<v Jon Lester>So it's going to be quickfire, and we'll
keep you busy.

37
00:02:09.410 --> 00:02:11.210
<v Jon Lester>Um, let's dive straight in.

38
00:02:11.399 --> 00:02:15.690
<v Jon Lester>The, the first buzzword or, or first buzz
phrase that we have for cybersecurity is

39
00:02:15.690 --> 00:02:16.729
<v Jon Lester>defense in depth.

40
00:02:16.800 --> 00:02:18.929
<v Jon Lester>What does defense in depth mean?

41
00:02:19.979 --> 00:02:26.179
<v Alina Matyukhina>So this is, uh, I would say a very um
common uh cybersecurity concept uh and you

42
00:02:26.179 --> 00:02:30.619
<v Alina Matyukhina>will see, I would say it's a best practice
for the industry.

43
00:02:31.220 --> 00:02:35.940
<v Alina Matyukhina>So the goal is uh to build the multiple
layers of cybersecurity.

44
00:02:36.669 --> 00:02:43.350
<v Alina Matyukhina>And in case of, let's say cyberattack, if
there is one mechanism which

45
00:02:43.350 --> 00:02:49.990
<v Alina Matyukhina>doesn't work or fail or interrupted, there
is always in place other,

46
00:02:50.210 --> 00:02:56.990
<v Alina Matyukhina>other cybersecurity layers, cybersecurity
mechanisms which can provide adequate

47
00:02:56.990 --> 00:02:58.470
<v Alina Matyukhina>level of cybersecurity.

48
00:02:58.940 --> 00:03:04.979
<v Alina Matyukhina>For example, in our building automation,
we are saying that um we need to protect

49
00:03:04.979 --> 00:03:11.539
<v Alina Matyukhina>everything from operational level to field
level, from physical access control to

50
00:03:11.539 --> 00:03:18.419
<v Alina Matyukhina>network protection, and defense in depth
only will work if this

51
00:03:18.419 --> 00:03:20.639
<v Alina Matyukhina>protection will work simultaneously.

52
00:03:21.690 --> 00:03:22.339
<v Jon Lester>OK, perfect.

53
00:03:22.460 --> 00:03:27.580
<v Jon Lester>So it's It's having multiple different
systems, multiple approaches to give you the

54
00:03:27.580 --> 00:03:32.779
<v Jon Lester>best chance to, to remain secure, and if
someone bypasses or is able to get past the

55
00:03:32.779 --> 00:03:36.000
<v Jon Lester>first level, the second level is there to
help protect you and so on.

56
00:03:36.639 --> 00:03:36.880
<v Alina Matyukhina>Exactly.

57
00:03:37.080 --> 00:03:37.740
<v Jon Lester>OK, perfect.

58
00:03:37.779 --> 00:03:38.130
<v Jon Lester>I like it.

59
00:03:38.149 --> 00:03:40.940
<v Jon Lester>It's, it's almost like, uh, you know, the
castles in the Middle eagle.

60
00:03:40.979 --> 00:03:44.539
<v Jon Lester>If you got through the first wall of
defense, the second wall is there to back up.

61
00:03:44.660 --> 00:03:46.539
<v Jon Lester>So I think this makes sense to me.

62
00:03:46.580 --> 00:03:47.199
<v Jon Lester>I like it.

63
00:03:47.639 --> 00:03:50.380
<v Jon Lester>Uh, the next one is separation of duties.

64
00:03:51.169 --> 00:03:51.860
<v Alina Matyukhina>Mhm.

65
00:03:52.610 --> 00:03:58.850
<v Alina Matyukhina>So separation of duties, uh, I would say
you will see this buzzwords in the access

66
00:03:58.850 --> 00:04:04.529
<v Alina Matyukhina>management access controls, um, it means,
uh, that, um.

67
00:04:05.550 --> 00:04:12.190
<v Alina Matyukhina>We need to don't have, don't put a lot of
power to one

68
00:04:12.190 --> 00:04:12.699
<v Alina Matyukhina>individual.

69
00:04:13.149 --> 00:04:18.269
<v Alina Matyukhina>For example, software developers, they
don't need to have access to, let's say,

70
00:04:18.510 --> 00:04:20.130
<v Alina Matyukhina>production data and systems.

71
00:04:20.940 --> 00:04:26.649
<v Alina Matyukhina>Another example would be access rights of
system management and system administrator

72
00:04:26.649 --> 00:04:32.850
<v Alina Matyukhina>have to be separated from, for example,
access rights of database administrator.

73
00:04:33.359 --> 00:04:40.040
<v Alina Matyukhina>Because in case of cyberattack, if a user
or account is compromised, there

74
00:04:40.040 --> 00:04:46.959
<v Alina Matyukhina>is no, there is no impact to another

75
00:04:46.959 --> 00:04:48.029
<v Alina Matyukhina>account or service.

76
00:04:48.760 --> 00:04:54.399
<v Jon Lester>OK, so it's not putting all the eggs in
one basket, ensuring that, you know, if, if

77
00:04:54.399 --> 00:04:58.239
<v Jon Lester>we do have a compromise situation with one
particular user or one particular

78
00:04:58.239 --> 00:05:00.799
<v Jon Lester>account, it doesn't open the door to
absolutely everything.

79
00:05:01.119 --> 00:05:01.239
<v Jon Lester>Yeah,

80
00:05:01.359 --> 00:05:01.799
<v Alina Matyukhina>that's true.

81
00:05:02.089 --> 00:05:03.290
<v Jon Lester>Perfect, I like it.

82
00:05:03.690 --> 00:05:07.170
<v Jon Lester>Uh I think we're going a little bit in the
same direction when we talk about least

83
00:05:07.170 --> 00:05:08.429
<v Jon Lester>privileged principle.

84
00:05:08.529 --> 00:05:10.890
<v Jon Lester>What's the least privileged principle?

85
00:05:11.709 --> 00:05:18.519
<v Alina Matyukhina>Uh, so yeah, least privilege, uh, I would
say it's also, um, you

86
00:05:18.519 --> 00:05:24.200
<v Alina Matyukhina>will see in access management, but it's a
little bit different from separated of

87
00:05:24.200 --> 00:05:30.899
<v Alina Matyukhina>duties principle, uh, because, um, uh, for
example, if you have a service

88
00:05:30.899 --> 00:05:36.880
<v Alina Matyukhina>or account or user, uh, they need a bare
minimum of

89
00:05:36.880 --> 00:05:39.179
<v Alina Matyukhina>privileges to.

90
00:05:39.869 --> 00:05:42.399
<v Alina Matyukhina>To make done a certain task.

91
00:05:42.839 --> 00:05:49.670
<v Alina Matyukhina>So for example, if there is a service
running on the system and it has a user

92
00:05:49.670 --> 00:05:54.640
<v Alina Matyukhina>root privileges, it means that it can
actually, you can access everything on the

93
00:05:54.640 --> 00:05:57.220
<v Alina Matyukhina>device and you can manipulate everything
on the device.

94
00:05:57.350 --> 00:06:01.750
<v Alina Matyukhina>And in case of cyberattack, if there are a
lot of processes they're running with.

95
00:06:02.174 --> 00:06:07.484
<v Alina Matyukhina>router privilege, cyber like hacker can
take down the whole system.

96
00:06:07.734 --> 00:06:13.005
<v Alina Matyukhina>So that's why we are saying in billing
automation that all systems, they all

97
00:06:13.005 --> 00:06:18.524
<v Alina Matyukhina>services, all applications you have on the
device, they should really run with the

98
00:06:18.524 --> 00:06:19.825
<v Alina Matyukhina>least privileges.

99
00:06:20.204 --> 00:06:26.445
<v Jon Lester>OK, so making sure that again rather than
a user, if a device or something like this

100
00:06:26.445 --> 00:06:28.024
<v Jon Lester>is, is then breached.

101
00:06:28.429 --> 00:06:33.100
<v Jon Lester>You you still have only a certain amount
of access, a certain ability to make, make

102
00:06:33.100 --> 00:06:37.910
<v Jon Lester>changes within the system, perfect, um, I
think some of these things go together,

103
00:06:37.989 --> 00:06:41.839
<v Jon Lester>but the next buzzword we have is
hardening, or cybersecurity hardening.

104
00:06:42.350 --> 00:06:42.489
<v Alina Matyukhina>Mhm.

105
00:06:43.290 --> 00:06:50.010
<v Alina Matyukhina>Uh, hardinin, uh, so you will see this
term, I would say, um, in documentation,

106
00:06:50.420 --> 00:06:53.459
<v Alina Matyukhina>for example, uh, manufacturers, uh, they,
um.

107
00:06:54.670 --> 00:06:57.450
<v Alina Matyukhina>Publishing cybersecurity or hardening
guidelines.

108
00:06:57.950 --> 00:07:04.910
<v Alina Matyukhina>So these guidelines, they provide
configuration information of the products, for

109
00:07:04.910 --> 00:07:11.415
<v Alina Matyukhina>example, how they should be installed in
the In the

110
00:07:11.994 --> 00:07:17.295
<v Alina Matyukhina>project, uh, what kind of services have to
be disabled or enabled?

111
00:07:17.915 --> 00:07:24.595
<v Alina Matyukhina>what kind of, uh, for example, firewall
rules that you need to also configure in

112
00:07:24.595 --> 00:07:26.125
<v Alina Matyukhina>your project and so on.

113
00:07:26.515 --> 00:07:31.554
<v Alina Matyukhina>So this is the kind of standard
information which you need to provide secure

114
00:07:31.554 --> 00:07:37.575
<v Alina Matyukhina>commissioning and also secure operation of
the product and system.

115
00:07:37.915 --> 00:07:38.274
<v Alina Matyukhina>Thank you.

116
00:07:39.079 --> 00:07:43.040
<v Jon Lester>So guidance for anyone who's actually put
deploying a system, guidance who's taking

117
00:07:43.040 --> 00:07:48.799
<v Jon Lester>a product and putting it into situ, uh, of
what they should do or the, the, the

118
00:07:48.799 --> 00:07:53.399
<v Jon Lester>minimum or the level of expectation of
some of the actions they should take to give

119
00:07:53.399 --> 00:07:58.200
<v Jon Lester>you the best chance to be successful, to,
to, to make it as secure as, or part of a,

120
00:07:58.239 --> 00:07:59.929
<v Jon Lester>a, a secure approach.

121
00:08:01.320 --> 00:08:05.480
<v Jon Lester>Um, I almost said the next buzzword just
then in the last sentence, um.

122
00:08:05.880 --> 00:08:10.040
<v Jon Lester>Uh, this cybersecurity approach, we talk
about a holistic approach.

123
00:08:10.119 --> 00:08:12.059
<v Jon Lester>What is a holistic cybersecurity approach?

124
00:08:13.179 --> 00:08:18.149
<v Alina Matyukhina>So a lot of companies, they are applying
this holistic approach to security, which

125
00:08:18.149 --> 00:08:21.989
<v Alina Matyukhina>means they are concentrated on 4 basic
factors.

126
00:08:22.660 --> 00:08:25.380
<v Alina Matyukhina>To improve security in the organization.

127
00:08:25.700 --> 00:08:30.540
<v Alina Matyukhina>So these four factors there, it's the
people, communication processes, and

128
00:08:30.540 --> 00:08:31.390
<v Alina Matyukhina>technologies.

129
00:08:31.820 --> 00:08:36.140
<v Alina Matyukhina>So people, they have to be educated on
cybersecurity.

130
00:08:36.219 --> 00:08:42.099
<v Alina Matyukhina>They should have a broad awareness about
possible cyber threats, for example, what

131
00:08:42.099 --> 00:08:48.900
<v Alina Matyukhina>is it, phishing emails, how to recognize
malicious links in the mail,

132
00:08:49.140 --> 00:08:49.820
<v Alina Matyukhina>and so on.

133
00:08:50.190 --> 00:08:55.880
<v Alina Matyukhina>Uh, that's why, yeah, I would say that you
cannot provide a secure solution if your

134
00:08:55.880 --> 00:08:58.690
<v Alina Matyukhina>employees, they're not trained on
cybersecurity.

135
00:08:59.380 --> 00:09:03.789
<v Alina Matyukhina>And then communication, of course, uh,
when it's clear and concise, uh, it actually

136
00:09:03.789 --> 00:09:08.210
<v Alina Matyukhina>helps your organization to build a culture
of cybersecurity.

137
00:09:09.380 --> 00:09:15.270
<v Alina Matyukhina>Processes, which are actively applied,
they are becoming as important as

138
00:09:15.270 --> 00:09:16.369
<v Alina Matyukhina>technologies.

139
00:09:17.200 --> 00:09:22.500
<v Alina Matyukhina>in protecting organization and of course
technology has to be tested, also improved

140
00:09:22.500 --> 00:09:27.359
<v Alina Matyukhina>to fight with this sophisticated
increasing number of cyberattacks.

141
00:09:28.179 --> 00:09:28.580
<v Jon Lester>OK.

142
00:09:29.130 --> 00:09:34.539
<v Jon Lester>So, the holistic approach, and you'll
probably have to remind me of the 4 again, but

143
00:09:34.539 --> 00:09:36.340
<v Jon Lester>there's people, communications

144
00:09:36.890 --> 00:09:38.059
<v Alina Matyukhina>processes and technology.

145
00:09:38.280 --> 00:09:42.849
<v Jon Lester>OK, so all of these combined give you the
best chance to have something that not

146
00:09:42.849 --> 00:09:48.530
<v Jon Lester>only works today but will continue to work
and be maintained and give you this,

147
00:09:48.619 --> 00:09:51.919
<v Jon Lester>this, this cybersecurity delivery as
expected.

148
00:09:52.419 --> 00:09:55.890
<v Alina Matyukhina>Exactly for your organization, these four
key factors, yeah, perfect,

149
00:09:55.940 --> 00:10:00.650
<v Jon Lester>and I guess this links a little bit back
to one of the The first buzzword that we

150
00:10:00.650 --> 00:10:05.479
<v Jon Lester>talked about was defense in depth, you
know, this is training your people, physical

151
00:10:05.479 --> 00:10:09.679
<v Jon Lester>access control, all of these different
things combined, um, you need to work

152
00:10:09.679 --> 00:10:13.840
<v Jon Lester>together, because training your people,
but then not communicating some of the

153
00:10:13.840 --> 00:10:18.080
<v Jon Lester>things that you find is a breakdown in
that process, which, which means that you

154
00:10:18.080 --> 00:10:19.340
<v Jon Lester>have a failure at some point.

155
00:10:20.669 --> 00:10:21.760
<v Jon Lester>Perfect, thank you.

156
00:10:21.880 --> 00:10:27.750
<v Jon Lester>Uh, now the next two, Uh, are relatively
similar, but I guess it's important that we

157
00:10:27.750 --> 00:10:31.700
<v Jon Lester>differentiate between the two, there's
cybersecurity by design, and there's

158
00:10:31.700 --> 00:10:35.039
<v Jon Lester>cybersecurity by default, let's start with
cybersecurity by design.

159
00:10:36.559 --> 00:10:40.559
<v Alina Matyukhina>OK, so this is a very common term in
product security.

160
00:10:40.780 --> 00:10:45.659
<v Alina Matyukhina>Uh, it means that, uh, for example,
manufacturers, they include in cybersecurity in

161
00:10:45.659 --> 00:10:48.440
<v Alina Matyukhina>the initial design of the products.

162
00:10:49.239 --> 00:10:56.190
<v Alina Matyukhina>A cybersecurity by default, another term
which you mentioned, it's actually when for

163
00:10:56.190 --> 00:11:01.679
<v Alina Matyukhina>example you already developed a product
and then you want to release it for

164
00:11:01.679 --> 00:11:02.479
<v Alina Matyukhina>customers to use.

165
00:11:02.559 --> 00:11:08.340
<v Alina Matyukhina>Yes, so cybersecurity by default, it means
that you actually

166
00:11:09.190 --> 00:11:15.809
<v Alina Matyukhina>Remove all insecure features in your
product, so you make like

167
00:11:15.809 --> 00:11:18.169
<v Alina Matyukhina>a product secure by default.

168
00:11:18.539 --> 00:11:23.729
<v Alina Matyukhina>For example, let's say Port 80 have to be
closed because it's insecure.

169
00:11:24.179 --> 00:11:30.820
<v Alina Matyukhina>So if Port 80 is closed on the product, it
means that it's secure by by default,

170
00:11:31.299 --> 00:11:32.020
<v Alina Matyukhina>and yeah.

171
00:11:32.450 --> 00:11:35.039
<v Alina Matyukhina>There are a lot of other examples can be
provided.

172
00:11:35.950 --> 00:11:36.080
<v Alina Matyukhina>So,

173
00:11:36.229 --> 00:11:42.669
<v Jon Lester>so secure or cybersecure by design is, as
you mentioned, during the, the design

174
00:11:42.669 --> 00:11:46.630
<v Jon Lester>process, the research and development
process, you've always got cybersecurity as

175
00:11:46.630 --> 00:11:50.669
<v Jon Lester>part of the workflow to make sure the
decisions you make along that development

176
00:11:50.669 --> 00:11:54.780
<v Jon Lester>process, um, will deliver a product that,
that has the right capabilities at the

177
00:11:54.780 --> 00:11:55.130
<v Jon Lester>end.

178
00:11:55.349 --> 00:11:59.450
<v Jon Lester>Um, and then cybersecurity by default is
if you take that product and plug it in.

179
00:11:59.820 --> 00:11:59.909
<v Jon Lester>Yes.

180
00:11:59.989 --> 00:12:03.750
<v Jon Lester>The standard settings, the, the, you know,
the, the default settings within the

181
00:12:03.750 --> 00:12:08.549
<v Jon Lester>system, are the most secure that that
product is capable of doing, and, and I like

182
00:12:08.549 --> 00:12:14.789
<v Jon Lester>the example you use, you, you plug it in,
uh, you know, port 80 is, is disabled, you

183
00:12:14.789 --> 00:12:19.830
<v Jon Lester>could as a, as an engineer, make changes
to those if you wanted to, but the the

184
00:12:19.830 --> 00:12:26.239
<v Jon Lester>standard default system settings would,
Give you the most secure system settings

185
00:12:26.239 --> 00:12:28.330
<v Jon Lester>that that are possible as an example.

186
00:12:28.559 --> 00:12:28.770
<v Jon Lester>Yes,

187
00:12:28.960 --> 00:12:29.070
<v Alina Matyukhina>yes,

188
00:12:29.400 --> 00:12:33.799
<v Jon Lester>perfect, I like that, I think, and they're
also very different, so but they stand,

189
00:12:33.919 --> 00:12:37.039
<v Jon Lester>they sound or look a little bit similar,
so I think they're a good one to, to, to

190
00:12:37.039 --> 00:12:37.859
<v Jon Lester>differentiate from.

191
00:12:38.599 --> 00:12:39.969
<v Jon Lester>Uh, the next 10 trust.

192
00:12:40.049 --> 00:12:41.229
<v Jon Lester>What is zero trust?

193
00:12:41.890 --> 00:12:46.969
<v Alina Matyukhina>Well, zero trust is a very new term in our
industry in operational technology, but

194
00:12:46.969 --> 00:12:53.669
<v Alina Matyukhina>it's already exists in IT, I would say,
and zero trust, it's when

195
00:12:55.169 --> 00:13:01.799
<v Alina Matyukhina>there is a belief that organization, they
shouldn't trust anything inside or

196
00:13:01.799 --> 00:13:03.549
<v Alina Matyukhina>outside of its perimeter.

197
00:13:04.179 --> 00:13:08.030
<v Alina Matyukhina>They like organizations should verify
everything we try to access.

198
00:13:08.859 --> 00:13:14.309
<v Alina Matyukhina>Uh, and, um, of course, uh, I would say
it's very different from traditional

199
00:13:14.309 --> 00:13:17.020
<v Alina Matyukhina>approach which we all used to nowadays.

200
00:13:17.669 --> 00:13:22.429
<v Alina Matyukhina>Uh, so in traditional approach, uh, if
there is something in corporate network

201
00:13:22.429 --> 00:13:26.010
<v Alina Matyukhina>inside of corporate network, it's already
by default, it's trusted.

202
00:13:27.130 --> 00:13:33.210
<v Alina Matyukhina>Uh, but zero trust, it's like really you
don't trust anything and you verify

203
00:13:33.210 --> 00:13:34.080
<v Alina Matyukhina>everything before.

204
00:13:35.979 --> 00:13:37.780
<v Alina Matyukhina>Before release access.

205
00:13:38.049 --> 00:13:44.719
<v Jon Lester>OK, so you, you authenticate every device,
every user, every communication,

206
00:13:45.460 --> 00:13:50.299
<v Jon Lester>every piece of information that's passed,
all needs to be authenticated, whether it

207
00:13:50.299 --> 00:13:51.039
<v Jon Lester>comes from.

208
00:13:51.500 --> 00:13:56.409
<v Jon Lester>The device next door which sits in your
system, which is in your building or it

209
00:13:56.409 --> 00:13:57.059
<v Jon Lester>comes from outside.

210
00:13:57.150 --> 00:13:57.159
<v Jon Lester>OK,

211
00:13:59.890 --> 00:14:03.539
<v Alina Matyukhina>yeah, I mean why we are changing this from
traditional approach to zero trust is

212
00:14:03.539 --> 00:14:08.059
<v Alina Matyukhina>because for example, in corporate network
you can find right now a lot of IUT

213
00:14:08.059 --> 00:14:14.864
<v Alina Matyukhina>devices like Also cloud connection and
this is somehow breaks the paradigm,

214
00:14:15.155 --> 00:14:20.275
<v Alina Matyukhina>you know, as it was before corporate
network was separated from, for example,

215
00:14:20.705 --> 00:14:25.294
<v Alina Matyukhina>operational technology and so on, but
right now we really need to improve security.

216
00:14:25.354 --> 00:14:31.494
<v Alina Matyukhina>That's why we are saying that zero trust
it will be our future

217
00:14:32.434 --> 00:14:32.715
<v Alina Matyukhina>technology.

218
00:14:32.994 --> 00:14:33.775
<v Jon Lester>OK, so.

219
00:14:34.159 --> 00:14:38.390
<v Jon Lester>So the advent of some of these new
technologies you mentioned IoT there, cloud

220
00:14:38.390 --> 00:14:42.960
<v Jon Lester>connectivity, device connectivity, all of
these things enable some great features

221
00:14:42.960 --> 00:14:48.190
<v Jon Lester>and functionalities, but they are all
connections outside that corporate network,

222
00:14:48.929 --> 00:14:52.750
<v Jon Lester>which means that they're, You know, we
either start to look at every single one of

223
00:14:52.750 --> 00:14:56.820
<v Jon Lester>those connections and ensure that they're
secure, or we take a zero trust approach,

224
00:14:57.159 --> 00:15:01.349
<v Jon Lester>which means no one is trusted, everyone
needs to be authenticated, and everyone

225
00:15:01.349 --> 00:15:03.880
<v Jon Lester>needs to be tested before communication

226
00:15:03.880 --> 00:15:05.039
<v Jon Lester>can, can ensue.

227
00:15:05.640 --> 00:15:05.969
<v Alina Matyukhina>Exactly, yes.

228
00:15:06.559 --> 00:15:06.880
<v Jon Lester>Beautiful.

229
00:15:07.039 --> 00:15:08.020
<v Jon Lester>I like it, thank you.

230
00:15:08.479 --> 00:15:11.080
<v Jon Lester>Um, the next one is threat and risk
assessment.

231
00:15:11.159 --> 00:15:13.960
<v Jon Lester>What do we mean when we talk about threat
and risk assessment?

232
00:15:15.070 --> 00:15:21.369
<v Alina Matyukhina>Uh, so strate risk assessment, um, it's a
very good term and it's applied every time

233
00:15:21.369 --> 00:15:23.450
<v Alina Matyukhina>when, uh, you are dealing with the
products.

234
00:15:24.250 --> 00:15:29.229
<v Alina Matyukhina>Uh, during the whole, uh, product life
cycle, you need to manufacturers they are

235
00:15:29.229 --> 00:15:30.150
<v Alina Matyukhina>doing this product.

236
00:15:30.690 --> 00:15:36.119
<v Alina Matyukhina>threat and risk assessment to verify if
there is, uh, for example, potential risks

237
00:15:36.599 --> 00:15:42.219
<v Alina Matyukhina>inside of the product or develop like
features, uh, functionality of this product,

238
00:15:42.359 --> 00:15:45.140
<v Alina Matyukhina>and also to fix these potential risks.

239
00:15:45.919 --> 00:15:51.479
<v Alina Matyukhina>Uh, so I would say that uh this threat and
risk assessment, it started really from

240
00:15:51.479 --> 00:15:57.799
<v Alina Matyukhina>initial design of the product and also uh
repeats uh from like during the whole life

241
00:15:57.799 --> 00:15:58.400
<v Alina Matyukhina>cycle.

242
00:15:59.109 --> 00:16:05.200
<v Alina Matyukhina>Uh, for example, if you have a significant
change of your product, uh, then you need

243
00:16:05.200 --> 00:16:07.239
<v Alina Matyukhina>to do a strategy assessment again.

244
00:16:07.830 --> 00:16:07.979
<v Jon Lester>Thank you.

245
00:16:08.460 --> 00:16:14.140
<v Jon Lester>So start of the part of the standard
operating procedure, do, do an assessment, go

246
00:16:14.140 --> 00:16:17.700
<v Jon Lester>through the process to understand where
the risks live, and then whenever there's

247
00:16:17.700 --> 00:16:22.820
<v Jon Lester>serious updates or significant updates to
the product or portfolio or software or

248
00:16:22.820 --> 00:16:25.059
<v Jon Lester>whatever it might be, go through that
process

249
00:16:25.059 --> 00:16:25.239
<v Alina Matyukhina>again.

250
00:16:26.239 --> 00:16:26.539
<v Jon Lester>OK.

251
00:16:27.059 --> 00:16:28.010
<v Jon Lester>Perfect, thank you.

252
00:16:28.330 --> 00:16:30.559
<v Jon Lester>Um, the next is pen testing.

253
00:16:30.650 --> 00:16:34.200
<v Jon Lester>Now, I'd be interested in, you know, pen
testing is a shortened phrase.

254
00:16:34.289 --> 00:16:37.359
<v Jon Lester>What does pen testing stand for, and then,
and then what do we talk about that?

255
00:16:38.349 --> 00:16:44.950
<v Alina Matyukhina>So pen testing, it's a penetration
testing, and it's done usually by third

256
00:16:44.950 --> 00:16:49.369
<v Alina Matyukhina>party organizations who are very
professional in this pen testing for what they are

257
00:16:49.369 --> 00:16:49.669
<v Alina Matyukhina>doing.

258
00:16:50.109 --> 00:16:54.989
<v Alina Matyukhina>So it's actually the idea is to break a
system to make it more secure.

259
00:16:56.049 --> 00:17:00.750
<v Alina Matyukhina>Yeah, and if it's, for example, threat and
risk assessment is done by manufacturer

260
00:17:00.979 --> 00:17:06.489
<v Alina Matyukhina>for pen testing, it's better to involve a
really third party organization who is

261
00:17:06.489 --> 00:17:13.410
<v Alina Matyukhina>specialized in this and can find those
risks which is not, for

262
00:17:13.410 --> 00:17:16.709
<v Alina Matyukhina>example, couldn't find companies.

263
00:17:16.969 --> 00:17:22.050
<v Jon Lester>OK, OK, so it's, it's, it's a process of
getting a product or a solution or a system

264
00:17:22.050 --> 00:17:25.109
<v Jon Lester>or whatever it might be and trying to
break in, trying to break it.

265
00:17:25.489 --> 00:17:31.819
<v Jon Lester>Trying to, to circumvent the security
features, and by doing that identifying

266
00:17:31.819 --> 00:17:35.839
<v Jon Lester>potential weaknesses so they can be fixed
and and updated or whatever it might be,

267
00:17:36.260 --> 00:17:37.040
<v Alina Matyukhina>yeah, very true.

268
00:17:38.040 --> 00:17:38.959
<v Jon Lester>Perfect, I like it.

269
00:17:39.319 --> 00:17:40.599
<v Jon Lester>Uh, the next one is security patch.

270
00:17:40.680 --> 00:17:43.800
<v Jon Lester>I guess if you did a pen test, after
you've done a threat and risk assessment and

271
00:17:43.800 --> 00:17:48.239
<v Jon Lester>then you've gone through the pen testing
process, maybe you find an issue, uh, and

272
00:17:48.239 --> 00:17:49.640
<v Jon Lester>you get to a security patch.

273
00:17:49.719 --> 00:17:51.829
<v Jon Lester>What do we mean when we talk about
security patch?

274
00:17:52.239 --> 00:17:53.920
<v Alina Matyukhina>So it's a security fix.

275
00:17:54.630 --> 00:18:01.349
<v Alina Matyukhina>Um, and, uh, you're right, after, for
example, we are done with

276
00:18:01.349 --> 00:18:08.329
<v Alina Matyukhina>the pen testing, uh, uh, or some
organizations uh reaching us, uh,

277
00:18:08.349 --> 00:18:13.630
<v Alina Matyukhina>regarding vulnerability, uh, then, uh, uh,
next step is to release a patch.

278
00:18:13.949 --> 00:18:20.319
<v Alina Matyukhina>Uh, to remove this vulnerability in the
product, so you can remove like known and

279
00:18:20.319 --> 00:18:26.479
<v Alina Matyukhina>new vulnerabilities to be able to improve
the whole protection level of the product.

280
00:18:27.640 --> 00:18:31.400
<v Jon Lester>OK, so when we find a problem, a way to
fix it.

281
00:18:31.640 --> 00:18:37.839
<v Jon Lester>So whether it's software or firmware or
whatever it might be to, to, to close that

282
00:18:37.839 --> 00:18:39.880
<v Jon Lester>door to, to bridge the gap.

283
00:18:40.300 --> 00:18:40.449
<v Alina Matyukhina>Yes,

284
00:18:41.000 --> 00:18:41.369
<v Jon Lester>perfect.

285
00:18:41.859 --> 00:18:46.500
<v Jon Lester>Um, I like all of these have been in a
little bit of an order, which is nice.

286
00:18:46.790 --> 00:18:49.430
<v Jon Lester>The next one is incident handling process.

287
00:18:49.540 --> 00:18:52.089
<v Jon Lester>How does this fit together with some of
the previous buzzwords?

288
00:18:52.430 --> 00:18:57.890
<v Alina Matyukhina>OK, in incident handling, you actually
have a notification of the incident.

289
00:18:58.430 --> 00:19:05.140
<v Alina Matyukhina>For example, customers, they can reach to
manufacturers and say that the OK, we

290
00:19:05.140 --> 00:19:09.780
<v Alina Matyukhina>think that there is a vulnerability, you
know, or incident in the product, or, for

291
00:19:09.780 --> 00:19:15.530
<v Alina Matyukhina>example, security research researchers,
they can find something sensitive, and then,

292
00:19:15.540 --> 00:19:19.979
<v Alina Matyukhina>uh, uh, after manufacturers they receive
this notification, they of course analyze

293
00:19:19.979 --> 00:19:26.579
<v Alina Matyukhina>it with security experts involved and, uh,
then, uh, um, they are, uh.

294
00:19:26.880 --> 00:19:33.790
<v Alina Matyukhina>Again, they are producing these fixes
security patches, so

295
00:19:33.790 --> 00:19:39.800
<v Alina Matyukhina>it's called mitigation, mitigation, and of
course you need to have a disclosure, so

296
00:19:39.800 --> 00:19:46.520
<v Alina Matyukhina>you need to manufacturers they are oblique
obliged to

297
00:19:46.520 --> 00:19:47.270
<v Alina Matyukhina>notify us.

298
00:19:47.530 --> 00:19:54.079
<v Alina Matyukhina>Customers of the potential incident
vulnerability and also provide a fix which

299
00:19:54.079 --> 00:19:55.310
<v Alina Matyukhina>is patch

300
00:19:56.569 --> 00:20:02.089
<v Jon Lester>this fits nicely into that communication
box from the holistic approach when there's

301
00:20:02.089 --> 00:20:06.849
<v Jon Lester>an issue, you react to that issue, you fix
it with the patch, but you also have to

302
00:20:06.849 --> 00:20:08.089
<v Jon Lester>tell all the people.

303
00:20:08.260 --> 00:20:11.579
<v Jon Lester>There that may use a product or work with
the product that there is a patch that

304
00:20:11.579 --> 00:20:15.880
<v Jon Lester>they should do, how urgent it is, what the
risks it would bring with it, etc.

305
00:20:15.900 --> 00:20:16.380
<v Jon Lester>etc.

306
00:20:16.780 --> 00:20:21.689
<v Alina Matyukhina>Yes, so you see, like there is a really
high dependence on people, technology,

307
00:20:21.780 --> 00:20:25.900
<v Alina Matyukhina>communication processes to keep it all
secure.

308
00:20:26.079 --> 00:20:27.459
<v Jon Lester>It's all tying together nicely.

309
00:20:27.540 --> 00:20:28.150
<v Jon Lester>It works well.

310
00:20:28.380 --> 00:20:28.760
<v Jon Lester>Perfect.

311
00:20:29.459 --> 00:20:33.579
<v Jon Lester>Now the next 3, you know, we dive into a
little bit of industry standards and things

312
00:20:33.579 --> 00:20:34.530
<v Jon Lester>like this, so.

313
00:20:36.150 --> 00:20:39.560
<v Jon Lester>Let's start with the first one, IEC 62443.

314
00:20:39.670 --> 00:20:42.390
<v Jon Lester>What is IEC 62443?

315
00:20:42.989 --> 00:20:45.619
<v Alina Matyukhina>Yeah, this is a very important buzzword.

316
00:20:45.949 --> 00:20:49.890
<v Alina Matyukhina>You will maybe hear it everywhere from
every corner.

317
00:20:51.349 --> 00:20:57.550
<v Alina Matyukhina>So this is a series of the standard which
is specifically for industrial control

318
00:20:57.550 --> 00:21:01.050
<v Alina Matyukhina>systems, uh, for our building automation
controls.

319
00:21:01.439 --> 00:21:05.989
<v Alina Matyukhina>And there are kind of different sections
of the standard.

320
00:21:06.410 --> 00:21:13.109
<v Alina Matyukhina>So for example, Section 2, sorry, 42, it
provides the requirements

321
00:21:13.770 --> 00:21:16.109
<v Alina Matyukhina>for security of the product.

322
00:21:16.810 --> 00:21:22.890
<v Alina Matyukhina>So manufacturers, they are using it in the
daily like deployment, developing of the

323
00:21:22.890 --> 00:21:23.030
<v Alina Matyukhina>product.

324
00:21:23.750 --> 00:21:26.050
<v Alina Matyukhina>Uh, based on these requirements.

325
00:21:26.790 --> 00:21:32.989
<v Alina Matyukhina>Uh, also, for example, section 33 speaking
about uh how to secure actually the whole

326
00:21:32.989 --> 00:21:35.849
<v Alina Matyukhina>system, what kind of requirements you need
to fulfill.

327
00:21:36.750 --> 00:21:41.599
<v Alina Matyukhina>Uh, and, uh, based on the standards there
is a different, uh, certification

328
00:21:41.599 --> 00:21:46.760
<v Alina Matyukhina>available, so manufacturers, they are
actually uh certify their products based on

329
00:21:46.760 --> 00:21:53.160
<v Alina Matyukhina>the standard because, uh, how you can, uh,
show, uh, security, of course, uh, by

330
00:21:53.160 --> 00:21:57.359
<v Alina Matyukhina>using certification of security, um.

331
00:21:58.369 --> 00:22:01.670
<v Alina Matyukhina>Yeah, so this one, it's, I would say.

332
00:22:02.410 --> 00:22:09.040
<v Alina Matyukhina>Um, It's uh this standard is used mainly
in the Union and

333
00:22:09.040 --> 00:22:15.250
<v Alina Matyukhina>also Asia, but for example, for US there
is another standard which is the UL

334
00:22:15.250 --> 00:22:21.030
<v Alina Matyukhina>2900, and it's more popular in the US.

335
00:22:22.000 --> 00:22:27.630
<v Jon Lester>And, and is it a safe, or maybe the
question is, are there really significant

336
00:22:27.630 --> 00:22:34.239
<v Jon Lester>differences between between the US and the
IEC standard, or are they built on some

337
00:22:34.239 --> 00:22:35.689
<v Jon Lester>similar base?

338
00:22:36.630 --> 00:22:37.780
<v Alina Matyukhina>Yes, yes, yeah, exactly.

339
00:22:37.959 --> 00:22:44.780
<v Alina Matyukhina>They are built on a similar concept, maybe
a bit different is based on the market,

340
00:22:44.920 --> 00:22:50.849
<v Alina Matyukhina>of course, yes, but the concept of
cybersecurity of product system is similar.

341
00:22:51.390 --> 00:22:56.579
<v Jon Lester>Yeah, I think that that's a really
important one, as you mentioned, because, uh, as

342
00:22:56.579 --> 00:22:58.130
<v Jon Lester>you say, how do you measure cybersecurity?

343
00:22:58.180 --> 00:22:59.780
<v Jon Lester>You need something to measure against.

344
00:23:00.380 --> 00:23:05.859
<v Jon Lester>So you need, you need a standard and you
need the certification to approve compared

345
00:23:05.859 --> 00:23:06.369
<v Jon Lester>to how you do that.

346
00:23:06.459 --> 00:23:10.280
<v Jon Lester>So that's an important one, especially for
those out there listening that may.

347
00:23:10.680 --> 00:23:16.869
<v Jon Lester>You know, we may be comparing a product or
may be looking or they want to have a

348
00:23:16.869 --> 00:23:19.300
<v Jon Lester>better understanding about the approach
that's been taken.

349
00:23:19.640 --> 00:23:23.640
<v Jon Lester>Those standards are a good thing to
compare consistently across different systems

350
00:23:23.640 --> 00:23:24.479
<v Jon Lester>and whatever it might be.

351
00:23:25.199 --> 00:23:31.599
<v Alina Matyukhina>Yeah, and for, for example, people like
customers who really wants to

352
00:23:31.599 --> 00:23:37.619
<v Alina Matyukhina>know is like this product secure, they
really need to look on the security level.

353
00:23:38.359 --> 00:23:43.920
<v Alina Matyukhina>In the certification because there is for
example security level 1 which actually

354
00:23:43.920 --> 00:23:50.800
<v Alina Matyukhina>protection against like unintended misuse
or just errors and it doesn't have a

355
00:23:50.800 --> 00:23:52.040
<v Alina Matyukhina>very high level of security.

356
00:23:52.079 --> 00:23:58.880
<v Alina Matyukhina>I would say security level 2 already if
you see it in the product it means that this

357
00:23:58.880 --> 00:24:03.119
<v Alina Matyukhina>product can be used against the
intentional misuse.

358
00:24:03.280 --> 00:24:05.959
<v Alina Matyukhina>So for example this is.

359
00:24:07.380 --> 00:24:13.290
<v Alina Matyukhina>Low knowledge of the system and also low
level of motivation of the hacker.

360
00:24:13.739 --> 00:24:17.479
<v Alina Matyukhina>But if you see, for example, security
level 3, it means that it's already this

361
00:24:17.479 --> 00:24:22.550
<v Alina Matyukhina>product can be used and it's secure
against sophisticated attacks.

362
00:24:22.739 --> 00:24:25.640
<v Alina Matyukhina>And the last level, it's security.

363
00:24:25.744 --> 00:24:32.005
<v Alina Matyukhina>Level 4 and I would say this level it's
there are a lot of requirements to fulfill

364
00:24:32.505 --> 00:24:37.854
<v Alina Matyukhina>because this kind of products, the
security level 4, they can be actually installed

365
00:24:37.854 --> 00:24:43.385
<v Alina Matyukhina>in military for example projects or
government, so they have really, really very

366
00:24:43.385 --> 00:24:44.385
<v Alina Matyukhina>high security level.

367
00:24:44.770 --> 00:24:45.260
<v Jon Lester>OK, perfect.

368
00:24:45.359 --> 00:24:49.859
<v Jon Lester>No, that's a great addition because, you
know, that certification, it's nice that

369
00:24:49.859 --> 00:24:52.660
<v Jon Lester>the higher the number, the higher the
security, that makes it a little bit easier,

370
00:24:52.780 --> 00:24:57.380
<v Jon Lester>but, uh, but also to understand, you know,
the highest level at level 4, you know,

371
00:24:57.530 --> 00:25:02.020
<v Jon Lester>this is where you really start to look at
the application requirements, um, but 2

372
00:25:02.020 --> 00:25:05.660
<v Jon Lester>and 3 are kind of what you would expect
with there if you were trying to, trying to

373
00:25:05.660 --> 00:25:09.000
<v Jon Lester>have a secure system in a, in a space
where perhaps there is a risk.

374
00:25:10.380 --> 00:25:11.500
<v Jon Lester>Alright, perfect, thank you.

375
00:25:11.819 --> 00:25:17.339
<v Jon Lester>Uh, now the next one, we have another
standard here, uh, ISO 27001 or ISO

376
00:25:17.339 --> 00:25:18.859
<v Jon Lester>27001.

377
00:25:19.180 --> 00:25:20.479
<v Jon Lester>What is this?

378
00:25:21.869 --> 00:25:28.680
<v Alina Matyukhina>Uh, so this is also a standard, but the
standard you cannot apply for

379
00:25:28.680 --> 00:25:30.219
<v Alina Matyukhina>industrial control systems.

380
00:25:30.479 --> 00:25:37.020
<v Alina Matyukhina>It's more applicable for IT, IT systems,
and, uh, for example,

381
00:25:37.199 --> 00:25:42.979
<v Alina Matyukhina>cloud also cloud applications you can
certify by this standard, uh,

382
00:25:43.280 --> 00:25:45.719
<v Alina Matyukhina>but it's not about hardware.

383
00:25:45.800 --> 00:25:49.819
<v Alina Matyukhina>It's, uh, I would say the standard, it's
more about software, software security,

384
00:25:50.089 --> 00:25:50.380
<v Jon Lester>OK.

385
00:25:50.880 --> 00:25:56.040
<v Jon Lester>So it has a similar approach, has a
similar function within the industry of, of, of

386
00:25:56.040 --> 00:26:00.920
<v Jon Lester>setting, a measurement and expectation
that can then be certified against, but it's

387
00:26:00.920 --> 00:26:04.119
<v Jon Lester>focused on those software cloud
applications rather than than hardware.

388
00:26:04.239 --> 00:26:04.819
<v Jon Lester>Perfect.

389
00:26:05.280 --> 00:26:05.599
<v Jon Lester>Amazing.

390
00:26:05.680 --> 00:26:05.959
<v Jon Lester>Thank you.

391
00:26:06.099 --> 00:26:11.040
<v Jon Lester>Now, the next one I have is, I'm also
interested to understand better, um,

392
00:26:11.920 --> 00:26:13.439
<v Jon Lester>OWASP.

393
00:26:13.959 --> 00:26:16.900
<v Jon Lester>I'm not sure if how, how you would
normally refer to this.

394
00:26:19.170 --> 00:26:19.920
<v Jon Lester>Alright, perfect.

395
00:26:20.160 --> 00:26:20.520
<v Jon Lester>Let's do this.

396
00:26:20.810 --> 00:26:21.050
<v Jon Lester>What is what is

397
00:26:21.050 --> 00:26:21.489
<v Alina Matyukhina>OAS?

398
00:26:22.130 --> 00:26:28.880
<v Alina Matyukhina>So, um, you will hear a lot if you are,
for example, the

399
00:26:28.880 --> 00:26:34.189
<v Alina Matyukhina>clouds, uh, because it's an organization.

400
00:26:36.709 --> 00:26:41.829
<v Alina Matyukhina>Uh, which produces, uh, best practices,
norms, how to secure cloud applications, how

401
00:26:41.829 --> 00:26:42.989
<v Alina Matyukhina>to secure job applications.

402
00:26:43.000 --> 00:26:48.770
<v Alina Matyukhina>It's, uh, like very well known in this
cloud community, I would say, and you can

403
00:26:48.770 --> 00:26:50.969
<v Alina Matyukhina>also, for example, do pen test.

404
00:26:51.469 --> 00:26:55.619
<v Alina Matyukhina>Uh, of cloud application based on OAS, uh,
principles.

405
00:26:56.500 --> 00:27:02.979
<v Alina Matyukhina>Yep, so this is more, as you can see like,
uh, IEC 62443, it's more about hardware

406
00:27:02.979 --> 00:27:08.699
<v Alina Matyukhina>if you want to secure, uh, secure hardware
and, uh, make a certification for the

407
00:27:08.699 --> 00:27:15.699
<v Alina Matyukhina>hardware and, um, then, uh, another one
it's, uh, ISO 27,0001

408
00:27:15.699 --> 00:27:19.099
<v Alina Matyukhina>if you are dealing with IT security IT
system.

409
00:27:19.339 --> 00:27:21.560
<v Alina Matyukhina>And almost it's about cloud.

410
00:27:21.930 --> 00:27:22.140
<v Alina Matyukhina>OK,

411
00:27:22.569 --> 00:27:22.920
<v Jon Lester>beautiful.

412
00:27:23.069 --> 00:27:28.300
<v Jon Lester>So these three together, when we look at
our industry and if you look at maybe a

413
00:27:28.300 --> 00:27:33.459
<v Jon Lester>traditional view on, on a building
automation system as an example, an operational

414
00:27:33.459 --> 00:27:38.260
<v Jon Lester>technology where you have, you know, your
hardware layers of your system and your

415
00:27:38.260 --> 00:27:39.160
<v Jon Lester>field layers.

416
00:27:39.630 --> 00:27:43.160
<v Jon Lester>Uh, your software layer and now the cloud
layer becomes more and more important.

417
00:27:43.479 --> 00:27:48.349
<v Jon Lester>These are the three standards that cover
these three segments of, of the hardware,

418
00:27:48.400 --> 00:27:51.280
<v Jon Lester>the software, and the systems that we talk
about in this industry.

419
00:27:51.719 --> 00:27:58.239
<v Alina Matyukhina>Yes, and also variations possible based on
the market which you are dealing with,

420
00:27:58.250 --> 00:28:00.319
<v Alina Matyukhina>like is it US, is it Asia, you know.

421
00:28:02.089 --> 00:28:05.099
<v Jon Lester>Yeah, and maybe it's a good time as always
to comment when we talk about

422
00:28:05.099 --> 00:28:11.430
<v Jon Lester>cybersecurity, you know, there are very,
very often, um, you know,

423
00:28:11.699 --> 00:28:15.479
<v Jon Lester>local regulations on top of international
regulations.

424
00:28:15.569 --> 00:28:20.520
<v Jon Lester>There's expectations for manufacturers
globally, but also locally for installers,

425
00:28:20.640 --> 00:28:24.650
<v Jon Lester>for, for people who are, you know, owners
and operators who are responsible for the

426
00:28:24.650 --> 00:28:24.979
<v Jon Lester>system.

427
00:28:25.040 --> 00:28:29.680
<v Jon Lester>So it's always worthwhile noting and
always be sure to say.

428
00:28:30.000 --> 00:28:35.280
<v Jon Lester>To check what is your local requirements,
what are your responsibilities within that

429
00:28:35.280 --> 00:28:38.239
<v Jon Lester>requirement, depending on where you sit
within the value chain, let's call it,

430
00:28:39.000 --> 00:28:41.619
<v Jon Lester>depending on what your role is in a
particular project.

431
00:28:42.599 --> 00:28:46.800
<v Jon Lester>Always double check because they could be
different, they could change, they could

432
00:28:46.800 --> 00:28:47.550
<v Jon Lester>be updated.

433
00:28:48.089 --> 00:28:51.079
<v Jon Lester>It's a, it's a constantly changing
landscape, you know, whenever we talk about

434
00:28:51.079 --> 00:28:55.579
<v Jon Lester>cybersecurity, we talk about there is no
such thing as a as a silver bullet.

435
00:28:56.199 --> 00:29:00.229
<v Jon Lester>What is secure today may need an update
tomorrow to remain secure.

436
00:29:00.640 --> 00:29:06.160
<v Jon Lester>So a big, a big hand up for everyone
that's listening to make sure you know.

437
00:29:06.680 --> 00:29:11.079
<v Jon Lester>Um, what you need to adhere to, what your
responsibility is, and, and what the

438
00:29:11.079 --> 00:29:15.439
<v Jon Lester>process should and could be for you to
remain secure, or be secure today but remain

439
00:29:15.439 --> 00:29:16.979
<v Jon Lester>secure into the future as well.

440
00:29:18.469 --> 00:29:18.800
<v Jon Lester>Alina,

441
00:29:18.979 --> 00:29:19.000
<v Alina Matyukhina>thank you.

442
00:29:21.510 --> 00:29:22.599
<v Jon Lester>You see, I, I learned from the best.

443
00:29:22.680 --> 00:29:25.959
<v Jon Lester>This is the, this is the thing, I, I, I, I
always bring it back.

444
00:29:26.069 --> 00:29:27.599
<v Jon Lester>Um, Alina, thank you so much.

445
00:29:27.699 --> 00:29:33.310
<v Jon Lester>We just ran through 15, I think, 15
buzzwords, so thank you so much for your time.

446
00:29:33.680 --> 00:29:38.079
<v Jon Lester>Uh, I can imagine that there are more for
us to talk about, so I'm sure we'll see

447
00:29:38.079 --> 00:29:40.500
<v Jon Lester>another cybersecurity buzzword session at
some point.

448
00:29:40.979 --> 00:29:45.579
<v Jon Lester>Um, for anyone who is listening out there,
of course, always share, like, and

449
00:29:45.579 --> 00:29:49.859
<v Jon Lester>comment, and please on this episode,
comment for, for some of the other buzzwords

450
00:29:49.859 --> 00:29:53.540
<v Jon Lester>that you're interested in, whether you,
you found this via LinkedIn or other social

451
00:29:53.540 --> 00:29:58.540
<v Jon Lester>media, or you found this, uh, in one of
your blog posts or something like this, come

452
00:29:58.540 --> 00:30:02.300
<v Jon Lester>and find us, make contact and let us know
what are the other buzzwords that you hear

453
00:30:02.300 --> 00:30:05.900
<v Jon Lester>out there, that, uh, that you want to hear
a definition for or want to learn a

454
00:30:05.900 --> 00:30:10.910
<v Jon Lester>little bit more about, and, uh, I will,
I'll secure some time with Alina and we

455
00:30:10.910 --> 00:30:13.829
<v Jon Lester>can, we can have a bit of a chat about
those as well.

456
00:30:14.189 --> 00:30:16.030
<v Jon Lester>Uh, Alina, thank you so much for joining
us.

457
00:30:16.469 --> 00:30:17.469
<v Alina Matyukhina>Thank you so much, John.

458
00:30:17.630 --> 00:30:22.520
<v Alina Matyukhina>I had a great pleasure to speak with you
again and this buzzword buster.

459
00:30:23.229 --> 00:30:25.949
<v Alina Matyukhina>And looking forward for other buzzwords.

460
00:30:25.959 --> 00:30:27.380
<v Alina Matyukhina>I'm really interested in.

461
00:30:28.160 --> 00:30:31.479
<v Jon Lester>I'm excited as well, and you know, welcome
to the buzzword buster, you know,

462
00:30:31.800 --> 00:30:32.579
<v Jon Lester>fraternity.

463
00:30:33.640 --> 00:30:36.119
<v Jon Lester>You know, this, I'm sure that we'll be
back here again.

464
00:30:36.199 --> 00:30:36.949
<v Jon Lester>So thank you.

465
00:30:37.349 --> 00:30:40.859
<v Jon Lester>And again, thank you to everyone
listening, like, share, comment, subscribe to us,

466
00:30:41.199 --> 00:30:44.280
<v Jon Lester>check out some of the previous
conversations I've had with Alina around Backnet

467
00:30:44.280 --> 00:30:46.920
<v Jon Lester>Secure Connect and other cybersecurity
topics.

468
00:30:46.989 --> 00:30:48.140
<v Jon Lester>There will be more, absolutely.

469
00:30:48.750 --> 00:30:52.800
<v Jon Lester>Uh, as long as she continues to say yes,
we will continue to record, uh, and

470
00:30:52.800 --> 00:30:56.839
<v Jon Lester>otherwise, uh, you know, feel free to
reach out to us if you have any thoughts or

471
00:30:56.839 --> 00:30:57.920
<v Jon Lester>suggestions, and we'll go from there.

472
00:30:58.040 --> 00:31:01.239
<v Jon Lester>But until the next time, thank you, and
we'll talk to you soon.

473
00:31:01.880 --> 00:31:02.550
<v Alina Matyukhina>Bye-bye.
