전사 🔗
WEBVTT
00:00:05.679 --> 00:00:06.559
Welcome back everybody.
00:00:06.639 --> 00:00:08.960
I'm Tommy McCarthy and this is Let's Talk Cyber.
00:00:09.039 --> 00:00:10.640
No stranger to Let's Talk Cyber.
00:00:10.720 --> 00:00:12.080
Now he's almost part of the furniture.
00:00:12.160 --> 00:00:14.480
James Mullins, welcome back to Let's Talk Cyber.
00:00:14.800 --> 00:00:15.839
Hey Tommy, how are you?
00:00:16.079 --> 00:00:16.879
Very good, James.
00:00:16.960 --> 00:00:19.760
Um very envious of the fact that you're just back from a week's holiday.
00:00:19.839 --> 00:00:21.519
Well, holiday, what were those things again?
00:00:21.839 --> 00:00:22.800
I'll have to remind myself.
00:00:24.239 --> 00:00:29.440
So, James, uh vice president of uh Mattermost right across uh Asia and Emir.
00:00:29.679 --> 00:00:31.600
So um very busy man, that's for sure.
00:00:31.760 --> 00:00:36.000
Um James was delighted to spend time with you back in April at Cyber UK.
00:00:36.079 --> 00:00:38.560
And it's really because of what happened at Cyber UK, James.
00:00:38.640 --> 00:00:50.799
I want to talk a little bit more and expand on the whole out of band communication piece because you hosted a tremendous, very successful workshop there, educating executives about the challenges when it all goes wrong, when the cyber attack happens.
00:00:50.960 --> 00:00:59.119
But I really do want to take a bit of time with you, if you don't mind, just to expand that whole concept around out of band, none more so when a major cyber attack hits.
00:00:59.280 --> 00:01:03.759
You know, um, what exactly does that out of band mean um to the organization?
00:01:04.000 --> 00:01:10.640
Because we're looking at one, when it all goes wrong, your communications fail, but more importantly, what exactly does that mean to an organization, James?
00:01:10.799 --> 00:01:11.680
Can we expand on that?
00:01:11.760 --> 00:01:18.319
Because you guys touched on it really well at the workshop, and I really want to get a better understanding for the challenges around that attack.
00:01:18.560 --> 00:01:18.799
Brilliant.
00:01:18.879 --> 00:01:19.920
Yeah, no, thank you, Tommy.
00:01:20.000 --> 00:01:21.439
Um, very happy to expand on that.
00:01:21.519 --> 00:01:24.719
And as you know, at Cyber UK, it was a big theme, right?
00:01:24.879 --> 00:01:30.799
You know, everyone was really talking about how do you deal, you know, when you have been attacked, because everyone will be at some stage.
00:01:31.040 --> 00:01:35.120
So um, I think the first thing to do is actually look at the attacker strategy.
00:01:35.280 --> 00:01:42.719
So most you know, criminals, when they're going in, they're not just there to encrypt the data, they're actually going to make it challenging for you to actually work things out once that's been done.
00:01:42.879 --> 00:01:47.439
So, what it'll actually do, they will target things that stop you from communicating.
00:01:47.519 --> 00:01:55.040
They will attack your kind of active directory, they'll go after Teams, Slack, or any other communication kind of network that you'll use there.
00:01:55.120 --> 00:01:57.599
So, really cutting off your ability to respond.
00:01:57.840 --> 00:02:07.760
And actually, what we're seeing then is because these things are actually happening, you're actually getting the uh the IT teams then kicking in and actually doing essentially a self-inflicted blackout, right?
00:02:07.840 --> 00:02:15.840
Because as soon as they see something happen, they're trying to shut it down to stop that dissemination and that kind of you know, kind of infiltration of capability.
00:02:16.159 --> 00:02:26.240
So they pulled a plug to actually contain the breach, and then what you see is that kind of those isolation networks, they're all shutting down communications to try and stop that kind of further issue moving forward.
00:02:26.479 --> 00:02:41.680
So, what we kind of look at, and what kind of you know most organizations are actually now looking at is that outer band kind of communications, and that's completely independent, it's pre-configured communication network that the event that something like this does happen, that you're actually kind of still staying active.
00:02:41.840 --> 00:02:47.360
So, if you can imagine that your main company network is actually going dark, your outer band is keeping you in the bright.
00:02:47.520 --> 00:02:51.280
Okay, so you're still seeing, you can still communicate, and you can do things in that way.
00:02:51.439 --> 00:03:00.159
So, if you've ever watched the films and you see those kind of secure red phones that you see kind of going on with people, once everything else goes dark and they're in a crisis situation, look at it in that way, right?
00:03:00.240 --> 00:03:02.479
You've still got the ability to communicate.
00:03:02.719 --> 00:03:11.599
And you know, when we meet again in a few weeks' time, um at the OTO Cyber event in Aberdeen, we're going to be really kind of looking at a real use case.
00:03:11.759 --> 00:03:12.879
So, what have we seen happen?
00:03:12.960 --> 00:03:15.280
And there's many of them about as you know right now, Tommy.
00:03:15.360 --> 00:03:20.879
But we'll go for a real kind of example, what happened, and actually kind of how they would have been better to react without a band.
00:03:20.960 --> 00:03:22.479
But yeah, really much looking forward to that.
00:03:22.639 --> 00:03:34.080
Yeah, well, James, it's interesting actually because we heard we've heard of a multitude of horror stories when these cyber attacks do happen because everybody assumed it's never going to happen to them, as we all know.
00:03:34.240 --> 00:03:42.639
Uh a very well-known and very well-established car retailer based in Scotland experienced a catastrophic cyber attack some years ago on Christmas Eve.
00:03:42.719 --> 00:03:48.000
And can you imagine having to resort to nothing better than WhatsApp to keep the business afloat?
00:03:48.240 -->
Load full transcript
00:03:50.159
The the sleepless nights these guys had.
00:03:50.240 --> 00:03:55.039
I've spoken to De Ciso and he says it was one of the worst experiences of his entire life.
00:03:55.199 --> 00:03:58.159
So, non no better timing, James, and you're absolutely right.
00:03:58.400 --> 00:04:11.599
Delighted that you're gonna come and extend your partnership with uh with the team here and and host one of these executive challenge workshops um, you know, for the up-and-coming workshop, James, you know, testing board-level decisions on the degraded communications.
00:04:11.759 --> 00:04:18.399
And this is the real important thing for me is for decision makers to realise the challenges they're gonna experience if it all goes wrong.
00:04:18.560 --> 00:04:24.399
So what does what what does that uh the pressure actually look like, James, in practice?
00:04:24.639 --> 00:04:25.199
Yeah.
00:04:25.439 --> 00:04:27.759
And and why do executives struggle with it, James?
00:04:27.839 --> 00:04:30.079
Because I think that's the important thing we've got to understand.
00:04:30.319 --> 00:04:32.639
Yeah, I think again, great question, Tommy.
00:04:32.720 --> 00:04:34.319
Um, it's always interesting, right?
00:04:34.480 --> 00:04:46.319
So when you look at any kind of attack, it doesn't matter whether it's kind of, you know, Russia going into Ukraine or this kind of this kind of retailer on Christmas Eve, it's typically done at a time where you're actually least expecting it.
00:04:46.399 --> 00:04:50.240
Okay, you know, that's the time where you're actually going to be at your your most challenged, etc.
00:04:50.480 --> 00:04:54.480
So again, kind of using like military around this, you know, it's that fog of war, right?
00:04:54.560 --> 00:04:55.839
You don't really know what's going on.
00:04:56.000 --> 00:05:06.639
So if you think of it from a normal crisis, whatever that may be, you know, what define normal, you know, executives will typically always have a way of receiving clean, very structured information, what's going on.
00:05:06.720 --> 00:05:11.360
And so you could all come together and actually make a decision about what to do to actually resolve that.
00:05:11.600 --> 00:05:15.040
In a real cyber attack, that's very different, right?
00:05:15.199 --> 00:05:20.000
If your communication is gone, your updates are gone, that's all disappeared, you've no longer got that.
00:05:20.079 --> 00:05:27.519
You know, you don't have that reliable communication, you've got the executives struggling to, you know, just even answer basic questions, right?
00:05:27.600 --> 00:05:31.279
About what are they, where are they doing it, what's happening, etc., etc.
00:05:31.439 --> 00:05:32.800
So all of that is now gone.
00:05:32.959 --> 00:05:43.120
So what you then see is essentially a kind of a lot of people then kind of kicking in those knee-jerk reactions, you know, and they start doing things in a way that they wouldn't normally do, and you get different behaviour patterns.
00:05:43.279 --> 00:05:47.759
And actually, what is worse is you actually get leaders kind of doing a you know, decision paralysis.
00:05:47.920 --> 00:05:51.519
You know, they won't make a decision, they can't do things because they can't get all the information.
00:05:51.600 --> 00:05:57.040
And then you're actually kind of you know, you're accelerating the problem because you're not reacting to it in the way that you should do.
00:05:57.199 --> 00:06:05.279
So again, you know, kind of if you think back to Cyber UK, you know, we worked the kind of workshop along with Richard Pierce, who was phenomenal in that event.
00:06:05.439 --> 00:06:10.079
We should be doing the same again then at the kind of OT kind of you know cyber event in Aberdeen.
00:06:10.160 --> 00:06:15.680
And really, you know, what we'll be doing there in a very similar way is it's not a lecture, it's an interactive workshop, right?
00:06:15.759 --> 00:06:25.759
How do we actually kind of work with the people who are at the event to actually understand what it looks like and put them under the pressure that they should expect to see in that type of kind of you know, in that type of environment, right?
00:06:25.839 --> 00:06:34.000
But but really, you know, if if if you can think of it now, if you were to go kind of one hour kind of Tommy without your internet, what would that do to your life, right?
00:06:34.639 --> 00:06:37.040
James, don't do that, don't do that to me.
00:06:37.279 --> 00:06:42.800
You know, the interesting thing, James, and you've just triggered a light bulb moment there, you might have seen it come on, actually.
00:06:43.040 --> 00:06:55.519
It's okay, you know, panicking and and worrying about the important thing, surviving the cyber attack, you know, making sure that your clients are made aware of it, that you've still got communications with everybody in your network.
00:06:55.680 --> 00:06:59.759
You've got a massive obligation from a compliance and regulatory perspective.
00:06:59.920 --> 00:07:02.399
You know, ultimately you're gonna have to report this.
00:07:02.560 --> 00:07:05.040
Ultimately, you're gonna have to understand what went wrong.
00:07:05.120 --> 00:07:06.319
You know, was it your network?
00:07:06.480 --> 00:07:08.720
Was it was was were you at fault somewhere?
00:07:08.800 --> 00:07:11.839
But you've got a compliance obligation if you're a major organization.
00:07:12.240 --> 00:07:19.920
So when an organization's primary channels go offline during an incident, how do they maintain that legal and regulatory compliance to whilst trying to recover?
00:07:20.079 --> 00:07:25.839
Because, you know, hopefully the dust will settle and then you'll have to do a full post-mortem of what went wrong.
00:07:26.000 --> 00:07:29.360
So that regulatory and compliance piece, James, how important is that?
00:07:29.759 --> 00:07:30.720
Amazingly important.
00:07:30.800 --> 00:07:31.920
And it doesn't stop, right?
00:07:32.000 --> 00:07:38.240
You know, once you're actually kind of dealing with this, the regulatory clock is still ticking and it will continue to tick all the way through, right?
00:07:38.319 --> 00:07:41.680
So in reality, the regulators don't care if your email's down, right?
00:07:41.759 --> 00:07:44.000
They don't care if you don't have that communication channel.
00:07:44.079 --> 00:07:47.120
They're expecting you to have things in the background to work, right?
00:07:47.199 --> 00:07:50.399
You know, we're all dealing now with very strict frameworks like NIST too.
00:07:50.639 --> 00:07:55.839
You know, they're kind of you know requiring organizations to report these incidents within a very tight window, right?
00:07:55.920 --> 00:07:58.079
And it's often within 24 to 72 hours.
00:07:58.160 --> 00:08:02.319
So, so how do you do that if you can't communicate internally and actually have an update on where you are?
00:08:02.480 --> 00:08:16.160
So, so really, you know, you need to be able to have that communication, you need to be able to kind of gather the facts, you need to be able to understand and then disseminate that information out, whether that be to you know parties inside your organization or external parties like the regulator.
00:08:16.240 --> 00:08:18.160
So all of that needs to be done.
00:08:18.399 --> 00:08:29.360
And as you kind of mentioned, you know, what we do see, unfortunately, if you get a lot of organizations because they haven't prepared in that way, they'll actually kind of fall into the trap of the consumer messaging application, right?
00:08:29.439 --> 00:08:40.399
Now that's great, and you've got a little bit of communication going, but what you've also done is actually kind of you know, you're now potentially exposing corporate information, sensitive corporate information that you shouldn't be doing.
00:08:40.559 --> 00:08:44.720
You know, you are kind of opening up a real compliance nightmare at this point, right?
00:08:44.799 --> 00:08:49.679
There's no chain of custody, you haven't got your secure kind of you know auditable logs, etc.
00:08:49.919 --> 00:08:50.159
etc.
00:08:50.480 --> 00:08:54.080
So I kind of you know tell everyone right now, don't go that way.
00:08:54.159 --> 00:08:57.120
It is a temporary fix, but it's not the right fix, okay?
00:08:57.200 --> 00:08:58.080
So really don't do that.
00:08:58.240 --> 00:09:07.679
So everything you've got to do in terms of being in that dodgy, challenging situation, being under fire, as it were, from those cyber criminals you have to maintain compliance.
00:09:07.840 --> 00:09:22.799
So the kind of best way of doing that is to kind of have ready an out-of-band solution that kind of protects your legal position, allows you to communicate securely, and hopefully remain in control and actually come to the shortest possible resolution of the thing of which you're you're trying to deal with.
00:09:22.960 --> 00:09:24.879
But those compliance won't go away.
00:09:25.200 --> 00:09:28.960
Seriously, it's such a massive important part of the jigsaw puzzle.
00:09:29.120 --> 00:09:35.360
Your organizations spend multi-millions on network security, on recovery data systems.
00:09:35.519 --> 00:09:43.279
Well, that's okay after the incident, you know, to consider how you get through that incident really needs to be paid a lot more attention to.
00:09:43.360 --> 00:09:48.320
So I guess what I'm gonna leave with is when a major cyber attack hits, how do we communicate?
00:09:48.480 --> 00:09:49.840
Don't answer that question, James.
00:09:50.000 --> 00:09:54.879
That's the question that I'm gonna pose in less than four weeks' time at the Scottish O2 Cybers Comment.
00:09:54.960 --> 00:09:56.320
We're delighted to have Mattermost there.
00:09:56.480 --> 00:10:08.159
There's the principal partner leading the way forward, sharing your experiences, especially the um, you know, the real life example that you're gonna talk about in the morning, and then the great workshop that you're gonna host, James.
00:10:08.320 --> 00:10:12.879
Thank you so much for spending time with me today to give me a better understanding of out and band communications.
00:10:13.039 --> 00:10:17.360
We'll be seeing you at the Scottish OT Cyber Summit in less than four weeks in Aberdeen.
00:10:17.519 --> 00:10:18.720
Thanks for joining me for now, James.
00:10:18.799 --> 00:10:19.440
Thank you, Tommy.