전사 🔗
WEBVTT
00:00:08.080 --> 00:00:09.599
Welcome back everybody.
00:00:09.759 --> 00:00:12.880
My name's Tommy McCarthy and this is Let's Talk Cyber.
00:00:13.039 --> 00:00:14.240
Well, there we have it.
00:00:14.480 --> 00:00:22.320
No stranger to us at Let's Talk Cyber, our one and only Irene Coyle, Chief Operating Officer at OSP Cyber Academy.
00:00:22.480 --> 00:00:24.239
Now, I'll be careful what I say here.
00:00:24.320 --> 00:00:26.000
She's not going to be talking about boring stuff.
00:00:26.160 --> 00:00:31.120
She's going to be talking about the stuff that we all need to know more about and what we should be doing in our businesses.
00:00:31.199 --> 00:00:34.719
But before we get into that, Irene, welcome to Let's Talk Cyber.
00:00:34.799 --> 00:00:39.520
Tell us all a little bit about what you've done in your whole life professionally and where you are right now.
00:00:39.840 --> 00:00:41.759
We don't have time for that, Thomas.
00:00:45.200 --> 00:00:46.159
Give us a snapshot.
00:00:46.240 --> 00:00:46.560
Come on.
00:00:46.719 --> 00:00:52.880
Um so, in terms of career-wise, I was 30 years in the police in Scotland and Police Scotland.
00:00:52.960 --> 00:00:59.920
Uh I retired in 2018 after having a really fantastic career, actually, very varied.
00:01:00.159 --> 00:01:20.400
Worked in uh a number of different departments, had some great projects developing a vulnerable person's database or managing the development of a vulnerable person's database, um, investigations, professional standards, um vulnerable adults, uh you know, a whole raft of different things.
00:01:20.480 --> 00:01:33.439
But latterly, and it's relevant for for this particular podcast, latterly I was um chief inspector at the recruitment and I had to implement GDPR in 2017.
00:01:33.519 --> 00:01:49.439
And I like a lot of organisations, I suppose, when you're asked to do that and you have no knowledge of GDPR or how to implement it or how to demonstrate compliance, um, I I had to do that right across the entire recruitment function for the whole of police Scotland.
00:01:49.519 --> 00:01:56.480
So it was a learning curve for me, but it also gravitated me towards doing that when I retired in 2018.
00:01:56.560 --> 00:01:58.239
So it was nicely timed.
00:01:58.400 --> 00:02:06.480
Um, and with that experience, I then became a data protection officer and do that still currently to today.
00:02:06.560 --> 00:02:15.439
So that's from 2018, where I'm outsourced into different organisations of different sizes and help them do their GDPR compliance journeys.
00:02:15.599 --> 00:02:16.719
Um, and that's me.
00:02:16.960 --> 00:02:17.360
That's it.
00:02:17.520 --> 00:02:29.280
But there's a lot more to that than just being a compliance officer and a data protection officer because we know you're heavily involved in data protection training and cybersecurity training, which we'll we'll we'll cover in another podcast.
00:02:29.520 --> 00:02:36.400
What I really want to touch on
Load full transcript
just now and what's relevant for this podcast uh is regulation compliance and that whole piece.
00:02:36.479 --> 00:02:47.120
But funny enough, some of the podcasts that we've done over the last few weeks, what keeps come coming up is this gold standard recognition that GDPR seems to have globally.
00:02:47.280 --> 00:02:48.560
Why do you suppose that is?
00:02:48.719 --> 00:02:53.759
Tell us what your views are on why people think GDPR is the gold standard in data protection.
00:02:54.000 --> 00:02:58.479
Yes, um, it's definitely considered the gold standard, uh, Thomas.
00:02:58.639 --> 00:03:13.439
It's you know, having just finished a six-month project with one of the uh UK oil refineries, that's exactly the message that I was getting across because they work globally with um suppliers and vendors, etc.
00:03:13.840 --> 00:03:25.680
And it is definitely um viewed as the gold standard, and it's probably because it's the first major regulation that's taken what I would describe as a rights-based approach to data protection.
00:03:26.000 --> 00:03:41.759
So when it first came into effect in 2018, it marked this huge shift from treating personal data as a business asset to then recognising that that's actually an extension of that person because it's their data.
00:03:42.000 --> 00:03:54.719
And I quite often say when I'm working with organisations that GDPR makes you consider the person at the centre of what you're doing with their data, and that's a really important point to hang on to.
00:03:55.039 --> 00:04:03.039
And then previous data privacy laws, well, they focused a lot more on what your organization's responsibilities were.
00:04:03.199 --> 00:04:10.000
But the essence of GDPR, and this is what makes it the gold standard, is how it then centres the individual.
00:04:10.159 --> 00:04:17.920
Um, so it gives them control over how their data is used, how it's stored, how it's shared, and that's only right, isn't it?
00:04:18.079 --> 00:04:30.399
If it was your data, you would want to have that control or at least knowledge about what the data was being used for, where it was being stored, and who you're actually sharing it with out with that organisation.
00:04:30.639 --> 00:04:43.279
So I think what makes it stand out globally, in addition to the centred part of GDPR about an individual, is that this GDPR, so UK and EU GDPR, has got real teeth.
00:04:43.439 --> 00:04:45.600
And that's what makes it more effective.
00:04:45.759 --> 00:04:58.000
So, for example, if you look at Meta, it was fined 1.2 billion euros back in 2023, and that was for breaching cross-border data transfer rules under GDPR.
00:04:58.160 --> 00:05:05.920
So that just demonstrates and gives you some evidence that this regulation isn't just symbolic, it's got real power behind it.
00:05:06.160 --> 00:05:16.399
And that's the type of privacy law which other countries should really be aspiring to have, and a lot of them are making real inroads into doing just that.
00:05:16.720 --> 00:05:17.600
It's interesting actually.
00:05:17.759 --> 00:05:19.040
I knew you bring it to life.
00:05:19.120 --> 00:05:24.720
I knew you get all passionate about GDPR and data protection, calling me Thomas.
00:05:24.800 --> 00:05:27.199
I'm not sure how I feel about that, but that's a whole different thing.
00:05:27.600 --> 00:05:28.639
That's your Sunday name.
00:05:28.959 --> 00:05:29.920
That's it, yeah.
00:05:30.160 --> 00:05:35.120
What what role does GDPR play in shaping the global privacy regulations?
00:05:35.279 --> 00:05:37.839
I mean, what what role do you think it it has out there?
00:05:38.160 --> 00:06:03.600
I think essentially it's like the blueprint because it's working to make data privacy better, not just in the EU and the UK, where it's obviously um enforceable, but countries like if you look at Brazil with the LGPD, if you look at South Korea and even some of the regions within America, like Colorado and Virginia, they've started to follow GDPR's lead basically.
00:06:03.839 --> 00:06:18.240
So if you if you look at other countries that are now taking on board the same aspects of GDPR, that's because they they see that this is the shape and the way that they should be shaping their own data privacy laws.
00:06:18.480 --> 00:06:20.160
So I always think of it like this.
00:06:20.319 --> 00:06:25.680
If you think about our digital landscape and how it's changed over the last decade.
00:06:25.759 --> 00:06:39.759
So just look 10 years ago, and then you look at AI and you look at the technology, and then you compare that to where we are when we had the last UK Data Protection Act, and that was in 1998.
00:06:40.079 --> 00:06:53.279
So just thinking about the changes in the digital landscape and technology since then, it makes sense that those laws were fragmented, they were outdated, and they were also quite industry-specific.
00:06:53.519 --> 00:07:03.279
What GDPR has done, it's now created this unified model that even governments can localize but still align to GDPR.
00:07:03.600 --> 00:07:10.959
So that makes, I suppose, more countries adopt this kind of international standard.
00:07:11.120 --> 00:07:21.600
Um, as I say, if you think about the technology and think about the digital landscape, you need to make sure that the laws are keeping up to date with those changes in that.
00:07:21.680 --> 00:07:23.600
And that's what GDPR is doing.
00:07:24.079 --> 00:07:28.000
And I think GDPR fits nicely into that journey of technology.
00:07:28.399 --> 00:07:45.519
Well, it's interesting you should say that because I had a just a previous podcast there with uh with a very um successful vendor in the UAE that talked about how important compliance and regulation was in establishing a good foundation for how they approach businesses and companies and clients.
00:07:45.680 --> 00:07:53.199
Well, why is it then that GDPR's emphasis is so heavily um focused on consent and on transparency?
00:07:53.360 --> 00:07:57.040
Why is it so significant that that's the areas they focus on within GDPR?
00:07:57.360 --> 00:08:14.240
Yeah, it's a really good question, and it's an important question actually, because the consent aspect and in particular the transparency aspect is something that, you know, you know, when you're trying to look at GDPR compliance, that's too just two of the aspects that you should be focusing on.
00:08:14.399 --> 00:08:31.199
But in particular, previously um companies or organizations were getting buried in the consent aspect in terms of they were burying the consent request in amongst all this different text and and and legal jargon.
00:08:31.360 --> 00:08:37.919
And actually, you as a user, as an individual, you had no real idea what you were agreeing to or consenting to.
00:08:38.080 --> 00:08:53.679
And I'm sure you can relate to that yourself, um, Tommy, when you're when you're thinking about when you're going on to websites and you're actually reading things, if you're asking for your consent, sometimes you get screams and screeds of pages, and I describe that as the gobbledygoo.
00:08:53.840 --> 00:08:56.639
So it doesn't make sense to anybody.
00:08:56.799 --> 00:09:05.600
So what happens is people switch off and they just click agree without actually knowing what they're agreeing to, and that's not really giving consent.
00:09:05.840 --> 00:09:18.000
So, what GDPR changed for consent was that it now has to be really clear, has to be informed, and it has to be an affirmative action taken by the individual.
00:09:18.159 --> 00:09:23.360
So you can't have these pretty ticked boxes anymore or all of this legal jargon.
00:09:23.519 --> 00:09:27.200
It's got to be nice, clear, and simple and really easy to understand.
00:09:27.360 --> 00:09:34.960
So you as an individual and and and I as an individual are actually consenting to what they know they're consenting to.
00:09:35.120 --> 00:09:48.159
And what consent is done, not just consent, but what GDPR has done, is also introduced, and this is the transparency aspect, that all of your company's data practices now need to be much more transparent.
00:09:48.320 --> 00:09:53.919
So it's made every organisation who's complying with GDPR much more accountable.
00:09:54.080 --> 00:09:58.000
So being transparent also helps with the accountability principle.
00:09:58.159 --> 00:10:18.720
So a good example is that is we spoke about websites a second ago, but if you look at the shift now for your cookie banners across your websites, annoying as they may be to some people, but they're now much clearer and they're more user-controlled because GDPR requires that, or PECAR actually, but it's all it's all linked into GDPR.
00:10:18.879 --> 00:10:24.399
And it's part of a broader cultural shift towards digital ethics, I would describe it as.
00:10:24.639 --> 00:10:33.039
So, Tommy, I know when you go onto websites and the cookie banner comes up, I'm absolutely sure you'll not just click accept all.
00:10:33.120 --> 00:10:34.000
Am I correct?
00:10:34.399 --> 00:10:34.799
Correct.
00:10:35.360 --> 00:10:38.559
It's been drilled into me by somebody not too far away.
00:10:39.120 --> 00:10:47.919
You're in control, you should be in control, and that's what GDPR is actually helping make organisations give back that control to the user.
00:10:48.240 --> 00:10:53.679
It's interesting that you should say that actually, because it moves me really, really well into my next question.
00:10:53.840 --> 00:10:57.919
How has GDPR changed the way organizations approach data governance?
00:10:58.080 --> 00:11:03.440
I mean, what what has made a difference by the implementation of GDPR when it comes to data governance for companies?
00:11:03.759 --> 00:11:11.919
Yeah, so uh well, I certainly believe that one of the most significant shifts is that data privacy is now recognised as a business risk.
00:11:12.080 --> 00:11:14.559
So it's not just viewed as an IT issue.
00:11:14.639 --> 00:11:26.559
And I think for many, many years, and even when GDPR first came into play, uh when I went into organisation, you could hear the different departments saying, but that's not our issue, that's that's an IT issue.
00:11:26.720 --> 00:11:30.240
And it's absolutely not, it's definitely a business risk.
00:11:30.480 --> 00:11:38.080
So because it's now being viewed as a business risk, that's then shifting the organization's approach towards data governance.
00:11:38.240 --> 00:11:44.320
So it forces you, GDPR forces organisations to map their data flows.
00:11:44.399 --> 00:11:45.679
So, where is their data?
00:11:45.759 --> 00:11:46.799
How is it coming in?
00:11:46.960 --> 00:11:48.320
Where's the source of it?
00:11:48.480 --> 00:11:53.600
Um, what's the internal process from getting that data?
00:11:53.759 --> 00:11:54.960
Who do we share it with?
00:11:55.039 --> 00:11:56.720
How is it being stored?
00:11:56.879 --> 00:12:04.879
Um, all the kind of touch points of that of that data's journey within the organisation and externally out of the organisation.
00:12:05.120 --> 00:12:28.399
And that, by able to map your data flows, by documenting your processing activities and considering data protection at every stage of a product or a service lifestyle lifecycle, not lifestyle, but life cycle, well, that's what you're supposed to be doing, and that helps your data governance approach basically for GDPR.
00:12:28.639 --> 00:12:41.200
Now, what what what I have noticed, um Tommy, is whilst being a data protection officer, um, is that you have responsibilities if you're a DPO, basically.
00:12:41.440 --> 00:12:48.000
So you've got responsibilities under GDPR, and that makes sure that your organisation is demonstrating accountability.
00:12:48.240 --> 00:13:14.240
However, if it's left with someone within the organisation who's not a data protection officer, but they've had data protection role lobbed into their existing um day job, then that makes it very difficult to take
that same structured and compliance-evidenced um approach to data governance, is what I'm trying to say there.
00:13:14.399 --> 00:13:20.080
Because it's very difficult to speak your truth if you've not got that role of a data protection officer.
00:13:20.159 --> 00:13:26.159
So going to the board, going to the senior execs, and actually identifying where the risks are from GDPR.
00:13:26.320 --> 00:13:30.159
So it actually makes your data governance role probably more difficult.
00:13:30.399 --> 00:13:36.879
GDPR helps definitely make you accountable and it's definitely improved, I would say, the data governance.
00:13:37.039 --> 00:13:44.159
I mean, you think about there's there's probably some brands out there that are that are demonstrating it really clearly, like Apple, for instance.
00:13:44.320 --> 00:13:49.440
Um so they've leaned very heavily into privacy as being their brand value.
00:13:49.759 --> 00:13:58.080
Um, and that's great because they're then showcasing how GDPR-inspired principles can then give you that competitive edge.
00:13:58.159 --> 00:14:12.960
And that's always a good thing to say to your board and your executive that if your GDPR um journey is leading towards your compliance journey, then you're actually going to have a competitive edge over your um out there in the marketplace.
00:14:13.279 --> 00:14:28.720
And again, really, really relevant because obviously uh you made reference to Apple and uh, you know, an international organization, but predominantly an American organization, interesting that they would take data governance to heart in the way that they have for a month uh a number of reasons why.
00:14:28.879 --> 00:14:37.600
What I want to finish off with is um your views on uh on how does GDPR differ in comparison to uh other data protection laws?
00:14:37.679 --> 00:14:43.440
And let's use the CCPA as an example, comparable data protection standard or regulation.
00:14:43.600 --> 00:14:51.919
First of all, just give us a brief about the CCPA, who what what is that standard, and then give us a comparison as to how GDPR differs from CCPA.
00:14:52.159 --> 00:15:12.720
Well, so I think if it's the questions about what differs, how GDPR differs from like severe CCPA, or you know, you can there's other um regulations out there um similar in different countries, but one major difference is how deeply GDPR integrates data protection into all the business operations.
00:15:12.799 --> 00:15:23.200
So where CCPA allows users to opt out of data sales, for example, GDPR goes much, much further and requires opting in consent.
00:15:23.360 --> 00:15:28.320
And that's a significant difference between GDPR and CCPA.
00:15:28.559 --> 00:15:36.240
Um what also GDPR goes further to that CCPA doesn't do is about privacy by default.
00:15:36.399 --> 00:15:39.440
So privacy by default by design basically.
00:15:39.600 --> 00:15:52.639
So even when you're looking at new projects, you've got to look at developing privacy inbuilt at
the start rather than trying to introduce something and then frantically thinking, oh, we didn't think about GDPR compliance.
00:15:52.720 --> 00:16:06.720
So it so it's different, it differs from the privacy by default aspect, the opting in aspect for consents, and the data protection impact assessments that are required before you launch any high-risk project.
00:16:06.960 --> 00:16:17.679
So these aren't get-out clauses, these are must-do elements of GDPR, which which is a significant difference between CCPA and California.
00:16:17.919 --> 00:16:32.559
But I suppose what GDPR doesn't, it's easy to remember this for me, but for for everybody else, GDPR doesn't just apply within the EU for EU GDPR and UK for UK GDPR.
00:16:32.720 --> 00:16:43.600
If you're a company, for example, in Singapore and you're processing either EU or UK citizens' data, then you've still got to comply with GDPR.
00:16:43.679 --> 00:16:56.159
So I think I like this aspect of it so that you've got this extraterritorial scope, which is quite unique from other um regulations like the ones um that you've mentioned, Dea.
00:16:56.320 --> 00:17:06.000
So it's so it's pushing companies worldwide to adopt this GDPR level of standard, um, even if it's not legally required to do that.
00:17:06.079 --> 00:17:08.000
And that's got to be a good thing.
00:17:08.319 --> 00:17:15.119
Whoever said that data protection was boring, honestly, and you said that the entire time with a big smile on your face.
00:17:15.200 --> 00:17:26.880
Now, it's interesting you said, you know, as a global impact and as a as a you know as a significant reach globally, because I believe very shortly you're heading off to Dubai to attend the GISEC um conference once again this year.
00:17:28.960 --> 00:17:33.920
Great, and and you're gonna be OSP Cyber Academy, you are gonna be based at the UK Pavilion in Hall 5.
00:17:34.000 --> 00:17:46.799
So if anybody has got any questions, about data protection, about GDPR, any of the other compliance standards that they need to ask, they can come and they can come and find you out at Hall 5 uh at the UK pavilion.
00:17:46.880 --> 00:17:47.440
Would that be right?
00:17:47.759 --> 00:17:48.640
Yes, please do.
00:17:48.720 --> 00:17:50.640
Please come come and speak to me anyway.
00:17:50.720 --> 00:17:54.480
But yeah, I love to chat about data protection and GDPR.
00:17:54.559 --> 00:17:59.519
You know me well, so I'd be delighted to speak to anybody and to help everybody, you know.
00:17:59.680 --> 00:18:07.119
I I just love that um approach where organizations and individuals within organisations want to do things better.
00:18:07.200 --> 00:18:09.200
So, yeah, please seek me out at GISEC.
00:18:09.440 --> 00:18:18.559
Eileen, I hate to cut it short, but all that remains for me to say is Eileen Coyle, Chief Operating Officer, no longer chief inspector at OSP Cyber Academy.
00:18:18.720 --> 00:18:19.759
Thank you so much for joining.
00:18:19.839 --> 00:18:20.559
Let's talk cyber.
00:18:20.799 --> 00:18:21.519
Thanks, Chloe.