TRANSCRIPCIÓN 🔗
WEBVTT
00:00:06.799 --> 00:00:07.839
Welcome back everybody.
00:00:07.919 --> 00:00:10.240
I'm Tommy McCarthy and this is Let's Talk Cyber.
00:00:10.320 --> 00:00:15.039
Well, I am delighted to say, Stephanie Calder, welcome to Let's Talk Cyber.
00:00:15.359 --> 00:00:16.320
Thanks, Tommy.
00:00:16.640 --> 00:00:21.039
Wonderful to have you, Stephanie, and thank you so much for your support recently at the OT Summit.
00:00:21.120 --> 00:00:22.399
We were delighted to have you there.
00:00:22.559 --> 00:00:28.320
Now, Stephanie, we are going to talk about how people need to stop overcomplicating OT cybersecurity.
00:00:28.399 --> 00:00:34.320
But before we do, how on earth is Stephanie Calder working in OT Cyber?
00:00:34.479 --> 00:00:42.079
Tell us a little bit about yourself, Stephanie, who you are, where you've come from, and how on earth did you get into this male-dominated industry right now?
00:00:42.719 --> 00:00:44.560
So my name's Stephanie Calder.
00:00:44.640 --> 00:00:46.960
I'm the CEO at Asset Guardian.
00:00:47.119 --> 00:00:58.880
So we provide a software platform that allows people to manage their OT risk across their change management processes, their cybersecurity, and their obsolescence.
00:00:59.039 --> 00:01:01.200
And I started with them four years ago.
00:01:01.359 --> 00:01:06.400
I think this is a really interesting area, and I have learnt a lot in the last four years.
00:01:06.560 --> 00:01:12.000
I'm by no means an expert, but I have some thoughts on this particular matter.
00:01:12.400 --> 00:01:17.120
Yeah, well, Stephanie, uh, we don't all have to be experts to understand what's going on.
00:01:17.200 --> 00:01:27.359
And it's and actually it's a good place to start because who really owns OT cybersecurity stuff and why does it need greater visibility and accountability at board level?
00:01:27.439 --> 00:01:35.599
Because I think sometimes, you know, the boardroom are quite happy just to shut the door and say, oh, that's IT or that's OT, it's not our domain.
00:01:35.760 --> 00:01:38.560
So who owns it and why does it need more visibility?
00:01:38.719 --> 00:01:40.400
Give us your own opinion on that.
00:01:40.640 --> 00:01:44.000
Um, so I think the board question is a really interesting one.
00:01:44.079 --> 00:01:53.920
I think it's always been seen that it's IT or it's an engineering problem, but there needs to be that board-level visibility.
00:01:54.400 --> 00:01:59.760
This risk is not going away, it's ever increasing, and it is a business risk.
00:01:59.920 --> 00:02:03.920
It affects the revenue of your business.
00:02:04.159 --> 00:02:08.000
So, why isn't that a board priority, in my opinion?
00:02:08.319 --> 00:02:18.719
Cyber incidents in operational technology can affect production, interrupt operations, maybe create some safety concerns, affect critical infrastructure.
00:02:19.120 --> 00:02:22.719
They need to be aware of what's going on at that level.
00:02:22.960 --> 00:02:33.360
Now, I'm not suggesting that they need to have the technical detail of that, but they need to know what's critical, where their gaps are, and who's responsible.
00:02:34.560 --> 00:02:40.080
The who's responsible conversation is really difficult at the moment for us.
00:02:40.319 --> 00:02:53.360
I think there's many parties involved, like board, IT, engineering, operations, but nobody seems to be really taking ownership of this, in my opinion, in the main.
00:02:54.000 --> 00:03:17.439
There obviously will be uh companies that um do have this under control, but it makes it really difficult for anybody to make any uh actual decisions and make any real change into how they they decrease this risk in their organization because everybody's sat in their silos and nobody is taking ownership and saying, right, this is what needs to change.
00:03:17.599 --> 00:03:21.039
This is our risk just now, but this is what it needs to be.
00:03:21.360 --> 00:03:30.879
Yeah, it's interesting, Steph, because you touched on a couple of things there that I'm gonna come back to, none more so than the adverse the adversaries and you know the threats and the risks that we're all exposed to.
00:03:30.960 --> 00:03:36.960
But before we do, we often quite we quite often hear you can't protect what you don't know you have.
00:03:37.280 --> 00:03:39.599
That's quite an interesting statement, normally.
00:03:39.759 --> 00:03:44.400
Why is asset visibility such a fundamental first step in OT cybersecurity?
00:03:44.479 --> 00:03:46.400
So you can't protect what you don't know you have.
00:03:46.560 --> 00:03:49.280
So visibility clearly has to be critical there.
00:03:49.919 --> 00:03:50.960
It's the foundation.
00:03:52.159 --> 00:03:58.000
Because you know, you can get a list from CSAR of thousands and thousands and thousands of vulnerabilities.
00:03:58.240 --> 00:04:03.199
If you can't match it to your ass asset inventory, where do you even start?
00:04:03.439 --> 00:04:04.319
Yeah, for sure.
00:04:04.639 --> 00:04:06.800
Well, it needs to be people's first step.
00:04:06.879 --> 00:04:15.199
And it it's amazed me the amount of people when we approach them to deploy our solution that they don't know what they're running.
00:04:15.360 --> 00:04:28.480
And a lot of um companies have spent lots of money on sophisticated cyber tools, but if they don't have the basic clear view of their operational environment, how can they protect it?
00:04:28.720 --> 00:04:30.879
Yeah, yeah, you know, you're absolutely right, Stefan.
00:04:31.040 --> 00:04:36.639
I guess, you know, a lot of organizations I believe are over overcomplicating cybersecurity.
00:04:36.959 --> 00:04:44.319
What would you say to businesses that are so worried about doing it perfectly that well, you know, that they struggle at the first step?
00:04:44.399 --> 00:04:51.199
I mean, because obviously it's a huge complex domain, you know, and yeah, it's so easy to over overcomplicate things.
00:04:51.279 --> 00:04:54.000
What what's
Load full transcript
your advice here, Stefan, in respect of that?
00:04:54.319 --> 00:04:55.759
It is a complex subject.
00:04:56.000 --> 00:05:07.040
I'm not trying to detract from that, but I think all too often people are looking for perfection rather than actually just making that first leap.
00:05:07.439 --> 00:05:14.879
And for me, you have to identify what you've got, you have to assess the risk of that, and then you have to do something about it.
00:05:15.040 --> 00:05:20.480
And at the moment, that we've got so many companies out there that don't even know what they're running.
00:05:20.720 --> 00:05:21.680
Take that first step.
00:05:21.839 --> 00:05:35.120
We've got customers that, you know, they they look at the minute detail rather than, you know, the 50,000 vulnerabilities that they do need to take care of, the one that maybe isn't exactly where they think it should be.
00:05:35.279 --> 00:05:44.480
I think what we're trying to do, people are trying to push this back because it is a complex subject and it's almost like they don't want to start it because they don't know what it's going to look like.
00:05:44.800 --> 00:06:01.600
And I think in order to be able to do that, they just need to make that first step rather than trying to run before they can walk, trying to deploy really sophisticated tools that give them huge overviews and see when um they have network intrusion, for example.
00:06:01.839 --> 00:06:02.560
That's great.
00:06:02.639 --> 00:06:07.519
But how do you know what that is actually going to affect on your network if you don't know what you're running?
00:06:07.839 --> 00:06:11.360
It's interesting, Steph, actually, because you touched on two things earlier on.
00:06:11.519 --> 00:06:13.040
I'm going to go right off piece here.
00:06:13.519 --> 00:06:21.839
Um, you talked about asset visibility, and I guess it couldn't be more serious or more considered now than ever.
00:06:22.079 --> 00:06:29.199
We recently experienced in the UK an attack on an OT um capability at a power station.
00:06:29.439 --> 00:06:36.480
Some of the reports are that it was state sponsored, but obviously we don't have the facts, so we can't name the organization or the country.
00:06:36.720 --> 00:06:49.839
I guess more now than ever, having an understanding of what your assets look like could not be more absolutely um serious than right now, considering we are now experiencing these uh OT attacks.
00:06:50.000 --> 00:06:52.480
What are your views on on what recently happened?
00:06:52.639 --> 00:06:59.279
Do you think is this is this an opportunity for people to say, oh, we need to stop and think about what we've got in place?
00:07:00.240 --> 00:07:05.360
Well, I think there's a few things I've got on in response to that.
00:07:05.600 --> 00:07:11.279
Um obviously it was a a small power uh plant, so nobody's safe.
00:07:11.600 --> 00:07:17.199
Just because you're small or it doesn't affect the grid doesn't mean that you're not a target.
00:07:17.439 --> 00:07:20.160
You need to start at the very beginning.
00:07:20.399 --> 00:07:28.560
Um the response that we've had for the government and National Cybersecurity Centre shows how seriously they're taking this.
00:07:28.720 --> 00:07:28.959
Yeah.
00:07:29.439 --> 00:07:33.360
There's advice gone out, um, you know, we need to be aware.
00:07:33.519 --> 00:07:42.800
This is a test, in my opinion, to see how easy it has been and then how much more disruption they can make the next time.
00:07:43.680 --> 00:07:53.600
For me, that small organization, now it hasn't been named, um, but four days to get a small power plant back up and running is crazy.
00:07:53.839 --> 00:07:58.959
So if you've got a large process-driven organization, how long is that going to take you?
00:07:59.120 --> 00:08:07.839
If you don't have a disaster recovery plan or business continuity plan that's robust and is fully tested, where are you getting all of those software backups?
00:08:08.000 --> 00:08:09.120
Where's your repository?
00:08:09.199 --> 00:08:11.920
Has it gone through proper change management controls?
00:08:12.079 --> 00:08:20.800
Because if it hasn't, you're scrambling about in files, in safes, you've got systems that are running that you're not even aware are doing what they're doing.
00:08:21.279 --> 00:08:22.720
How do you get it back online?
00:08:23.360 --> 00:08:28.560
There's a reason why I thought asking you this question and going off piste would definitely be valuable, Steph.
00:08:28.720 --> 00:08:36.399
I know uh there's no question that there's a multitude of things that I'm sure you, an asset guardian, but could consider with an incident just like this.
00:08:36.480 --> 00:08:39.840
And there's a reason why they call this critical national infrastructure.
00:08:40.000 --> 00:08:47.120
And I think it is a sign of what's yet to come, you know, and that's not scare monitoring, that's just the fact of the world that we live in.
00:08:47.279 --> 00:08:51.519
Steph, I'd love to speak more in more detail about this, but as you know, time is limited today.
00:08:51.600 --> 00:08:58.480
What I would like to say is thank you so much for joining me today and sharing a little bit of an insight as to OT cybersecurity.
00:08:58.639 --> 00:09:00.320
And are we overcomplicating it?
00:09:00.399 --> 00:09:01.440
Well, only time will tell.
00:09:01.600 --> 00:09:04.720
But for now, Stephanie Calder, CEO at Asset Gaudio.
00:09:04.960 --> 00:09:06.320
Thank you so much for joining me.
00:09:06.559 --> 00:09:07.759
Thanks, Tommy.