Latest / Views and News with Clarence Ford / Data breaches due to 3rd party service providers.
Transcript
- 0:00Speaker 1: Alan, it's great to have you with us.
- 0:03Speaker 2: Thank you, Clarence. Pleasure to be here.
- 0:06Speaker 1: We're talking serious major institutions compromised, and often not through
- 0:11Speaker 1: their own primary firewalls, but through third-party vendors and shared
- 0:16Speaker 1: software infrastructure. Are financial institutions over-relying on vendor trust? Are
- 0:22Speaker 1: they not getting them to jump through the hoops that
- 0:25Speaker 1: is going to keep us safe? How should third-party risk
- 0:28Speaker 1: management change?
- 0:32Speaker 2: Very good questions.
- 0:33Speaker 3: And I would say it's a little bit of both
- 0:35Speaker 3: in that there's an over-reliance of trust and also lack
- 0:38Speaker 3: of due checks and due diligence. But it's very difficult,
- 0:42Speaker 3: especially in this increasingly interconnected world. In this particular case,
- 0:46Speaker 3: it was like you rightfully said, it was a third
- 0:48Speaker 3: party was compromised and which led to these particular organizations
- 0:53Speaker 3: being compromised. Now, like you said, the need to be
- 0:55Speaker 3: robust and third party compliance. Now, it's a whole, when
- 1:00Speaker 3: it comes to third party, basically, it's a whole matrix
- 1:03Speaker 3: where you need to go through and just check and
- 1:05Speaker 3: make sure that they're doing the right thing. Some of
- 1:07Speaker 3: these things, number one is the third party security assessment.
- 1:11Speaker 3: How secure are they? What technology are they using? Is
- 1:14Speaker 3: it the best in class technology? Then there's what we
- 1:16Speaker 3: call the compliance risk Are they complying, for example, with
- 1:19Speaker 3: the regulations of the industry that they are in? Then
- 1:22Speaker 3: also they need to look at also as far as
- 1:24Speaker 3: their operations are concerned. Are they carrying out the operations
- 1:27Speaker 3: in the best way possible? So those are some of
- 1:29Speaker 3: the things that you can try and minimize. But also
- 1:31Speaker 3: having said that, Clarence, we have seen a lot of
- 1:34Speaker 3: third parties being compromised.
- 1:36Speaker 2: And why are they being compromised?
- 1:37Speaker 3: Because they don't have as robust security as maybe the
- 1:41Speaker 3: big multinationals or the big organizations would have.
- 1:45Speaker 1: I mentioned some brands. They are trusted brands. We're talking
- 1:48Speaker 1: Easy Equities, Satrix, Budvest Bank, Peregrine Capital, Peach Payments this
- 1:53Speaker 1: past week as well. These are trusted brands. Are they
- 1:58Speaker 1: absolved from the responsibility that third parties should show ultimately
- 2:05Speaker 1: to the consumer?
- 2:07Speaker 3: No, they're not absolved because It is your responsibility, what
- 2:10Speaker 3: we call a data controller, whereby a data controller or
- 2:14Speaker 3: a data owner, it is your responsibility to make sure
- 2:16Speaker 3: that anything that is downstream of you has the best
- 2:19Speaker 3: class in security. That's why now there are things that
- 2:21Speaker 3: we call third-party assessment, third-party risk, third-party compliance, that it
- 2:25Speaker 3: is the responsibility of this organization to make sure that
- 2:28Speaker 3: anybody who is interacting with our data or our client's
- 2:31Speaker 3: data has better, if not equivalent, security. So it is
- 2:36Speaker 3: their responsibility to make sure that Anybody downstream dealing with
- 2:39Speaker 3: the data has the same security, if not better.
- 2:42Speaker 2: Yeah.
- 2:46Speaker 1: Okay. I also want to give you another one that
- 2:48Speaker 1: I shared, 45 insurers. 45 insurers, multiple investment platforms exposed
- 2:54Speaker 1: in a single incident. Does this maybe point to a
- 2:58Speaker 1: systemic design flaw, especially in how client data is centralized,
- 3:04Speaker 1: maybe shared across South African financial services?
- 3:08Speaker 3: I wouldn't say it's a systemic flaw. It's just that,
- 3:11Speaker 3: look at it from this perspective. It's a building block.
- 3:15Speaker 3: There are many people who have apartments there, but there's
- 3:18Speaker 3: the main door. And the main door maybe has enough security,
- 3:21Speaker 3: not so good security. If you get in through the
- 3:24Speaker 3: main door, you have access to all these apartments, even
- 3:26Speaker 3: if maybe they have locked their doors or whatnot. So
- 3:29Speaker 3: it's not a systemic flaw. It's just the magnitude or
- 3:32Speaker 3: the what? or the scope of this particular hack. Because
- 3:37Speaker 3: when you look at it from a bank perspective, if
- 3:39Speaker 3: a bank is breached, those are millions of customers.
- 3:42Speaker 2: So we won't say it's a systemic flaw, it's just
- 3:44Speaker 2: a failure.
- 3:45Speaker 3: And in this particular case, from what we've seen online,
- 3:48Speaker 3: it was not even an advanced level of attack. It
- 3:50Speaker 3: was basically compromised credentials. So it's not systemic, it's just
- 3:54Speaker 3: that we need to show up our defenses and do
- 3:57Speaker 3: the basics very, very.
- 3:58Speaker 2: Very well. I get you.
- 3:59Speaker 1: And you're talking about responsibility. The question is, is it...
- 4:03Speaker 1: Is it not paying due attention to the responsibility? Is
- 4:05Speaker 1: it shirking the responsibility? Why are they not doing what
- 4:08Speaker 1: they are required to do?
- 4:11Speaker 2: A little bit of both.
- 4:12Speaker 3: I mean, who did the audit? When was the last audit?
- 4:17Speaker 3: Who verified the audit? Did you go and actually check
- 4:20Speaker 3: what you have audited vis-a-vis what is on ground is
- 4:23Speaker 3: actually the same. So also on the third party's end,
- 4:27Speaker 3: Who is your IT security guy? Are you audited also
- 4:30Speaker 3: by a third party, not just the guys you're handling
- 4:32Speaker 3: their data? What are your internal processes? What are your
- 4:36Speaker 3: internal compliance? So it's failures on different ends. And now
- 4:39Speaker 3: when something like this happens, that's where now you see
- 4:42Speaker 3: it that this led to this, this other thing led
- 4:44Speaker 3: to that. So it's maybe a domino effect.
- 4:47Speaker 2: One failure leads to another failure to another failure.
- 4:49Speaker 3: And now you have it 45 companies affected just by
- 4:53Speaker 3: one single breach.
- 4:54Speaker 1: Yeah, you're actually giving me some peace of mind, not
- 4:57Speaker 1: all the peace of mind that I need. You are
- 5:00Speaker 1: saying still that the safety protocols are sufficient to keep
- 5:07Speaker 1: the mischief at bay.
- 5:11Speaker 3: Yeah, they should be there, but you may have a
- 5:15Speaker 3: secure Fort Knox.
- 5:17Speaker 2: That's okay.
- 5:17Speaker 3: Fort Knox, you have your wires, your whatnot, electric fences,
- 5:21Speaker 3: your guard dogs. But if the front door is not
- 5:23Speaker 3: securely locked, All that is rendered useless if the basics
- 5:27Speaker 3: are not taken care of.
- 5:28Speaker 2: And that's what I'm saying.
- 5:29Speaker 3: In this particular case, it's the basics that were slightly
- 5:32Speaker 3: overlooked or overlooked and led to the magnitude of this
- 5:35Speaker 3: particular breach.
- 5:35Speaker 2: Because, I mean, three.
- 5:37Speaker 3: Companies going public on the same weekend with almost near
- 5:40Speaker 3: identical messages, that's something that should make us now pay attention.
- 5:44Speaker 1: But they claim to client that they are a Fort
- 5:48Speaker 1: Knox company.
- 5:50Speaker 2: Sorry, please repeat that question.
- 5:51Speaker 1: They claim to client that they are a Fort Knox,
- 5:55Speaker 1: that their transactional modality or that your money is safe
- 5:59Speaker 1: with them. How should client be responding?
- 6:03Speaker 3: Now, it's very difficult for us as clients maybe to
- 6:07Speaker 3: respond or to hold them accountable. What needs to happen
- 6:11Speaker 3: is the regulator now needs to step in and put
- 6:13Speaker 3: in the bare minimums, which they have done. But now
- 6:16Speaker 3: in this case, after all the dust has settled, once
- 6:19Speaker 3: the investigations.
- 6:20Speaker 2: Are done, now we will see the light from the dark.
- 6:23Speaker 3: We'll see in plain terms what actually happened, who bears
- 6:26Speaker 3: the cost, who needs, for example, if there needs to
- 6:28Speaker 3: be compensation. Who bears the cost of compensation? Where did
- 6:32Speaker 3: the ball actually drop? We claim or they claim to
- 6:34Speaker 3: be Fort Knox. Was it actual an overstatement or was
- 6:39Speaker 3: it just on paper?
- 6:40Speaker 2: But in actuality, there were things that were missing. Okay.
- 6:43Speaker 1: Maybe some class action then. Is that what you're saying?
- 6:47Speaker 2: It might be.
- 6:48Speaker 3: I mean, if, Clarence, you get a couple of your
- 6:51Speaker 3: friends and you say, my data was breached and I've
- 6:54Speaker 3: received some unsolicited calls, or I don't have the peace
- 6:57Speaker 3: of mind that I was misled to believe that you
- 7:01Speaker 3: guys have the best security.
- 7:03Speaker 2: Now, I don't have that peace of mind. Yes, it
- 7:04Speaker 2: can happen.
- 7:05Speaker 3: You can check individual action against, in your case, the
- 7:10Speaker 3: one who informed you of the breach.
- 7:13Speaker 1: Okay, let's talk about where the buck stops, essentially. So, yeah,
- 7:21Speaker 1: who's to blame? Where does corporate liability end and where
- 7:24Speaker 1: does individual responsibility begin?
- 7:30Speaker 3: Individual responsibility in terms of the end clients, I would
- 7:35Speaker 3: say if, For them, it's now as far as maybe
- 7:38Speaker 3: not sharing the passwords, making sure they have multi-factor authentication.
- 7:42Speaker 3: But in this particular case, I would absolve the end user.
- 7:48Speaker 3: This issue needs to be between the owner of the information,
- 7:51Speaker 3: the data owner, and now the third party. Now, between
- 7:55Speaker 3: the two of them, they need to see where did
- 7:57Speaker 3: the actual mistake or issue happen. And in this particular case,
- 8:01Speaker 3: from what I've seen, it is now the third party.
- 8:03Speaker 3: Now there will be audited, there will be investigations, and
- 8:06Speaker 3: to see what they have improved.
- 8:09Speaker 2: And that's where now we'll start tightening.
- 8:10Speaker 3: But also, it should be a lesson to all organizations
- 8:14Speaker 3: in South Africa, whether they're big, they're small, whether they're
- 8:17Speaker 3: multi-million or just a few thousand runs, they need to
- 8:20Speaker 3: take cybersecurity very, very, very important. Because all it takes
- 8:24Speaker 3: is just one lapse, like what we've seen, and then
- 8:26Speaker 3: it will be a domino effect of consequences.
- 8:29Speaker 1: Alan Juma, our guest lead cybersecurity engineer at ESET accredited,
- 8:34Speaker 1: credible financial services providers have been hacked through third-party service providers.
- 8:40Speaker 1: We're trying to understand what that means. Maybe you have
- 8:43Speaker 1: insights as well. Maybe you have a vantage point that
- 8:46Speaker 1: is meaningful to this particular conversation. Please share your thoughts
- 8:51Speaker 1: because we're seeing an uptick in this kind of thing
- 8:56Speaker 1: via WhatsApp at 0725671567. I want to go back to
- 9:00Speaker 1: that last question, Alan. So essentially the context is the
- 9:05Speaker 1: breach occurs at an investment firm, maybe a bank, maybe
- 9:09Speaker 1: a fintech company. The consumer is left paying the price.
- 9:14Speaker 1: It's our identity theft. There's targeted phishing that could come
- 9:18Speaker 1: as a consequence. In that context, where does corporate liability end?
- 9:23Speaker 1: Where does that individual responsibility begin?
- 9:25Speaker 3: Individual responsibility begins Now, in your case, since you're affected
- 9:31Speaker 3: it will be prudent for you to actually go and
- 9:33Speaker 3: change your passwords. Just make sure that you leave nothing
- 9:36Speaker 3: to chance because identities have stolen, been stolen. Now for
- 9:39Speaker 3: the corporate responsibility, now as far as maybe just to
- 9:42Speaker 3: be a bit technical, they need to review their internal structures.
- 9:45Speaker 3: What APIs need to be changed? What passwords need to
- 9:48Speaker 3: be changed? What models of operandi need to be changed?
- 9:51Speaker 3: And also, you know, now for the third party, how
- 9:54Speaker 3: can they ascertain you as a client and also ascertain
- 9:58Speaker 3: their clients who are attacked, that is Bidvest and the likes,
- 10:02Speaker 3: how can they ascertain them that this is the genuine
- 10:05Speaker 3: data that was breached, this is the extent, and this
- 10:08Speaker 3: is what we are doing about it.
- 10:10Speaker 2: And why am I saying that?
- 10:10Speaker 3: Because earlier on, three months ago, no, not three months, actually,
- 10:13Speaker 3: I think in March, there was a bank that was
- 10:15Speaker 3: actually attacked in South Africa. And they say that, you
- 10:18Speaker 3: know what, the data that was actually taken over was
- 10:21Speaker 3: not that significant. Only later on to see on the
- 10:24Speaker 3: dark web that the data was being leaked and it
- 10:25Speaker 3: was far much more than what they claimed. So in
- 10:29Speaker 3: this case, both organizations, the ones that were attacked and
- 10:32Speaker 3: the ones whose data was attacked, they need to come
- 10:34Speaker 3: clean and just lay it clear. This is the extent
- 10:37Speaker 3: of the damage. This is what we are doing, changing
- 10:40Speaker 3: our systems, holding people responsible. And this is what our
- 10:43Speaker 3: clients need to do. They need to change their passwords.
- 10:45Speaker 3: They need maybe to... you know, implement two-factor authentication just
- 10:49Speaker 3: so that everybody along this particular chain can be protected.
- 10:54Speaker 1: And I think you've actually argued that there's a gap
- 10:57Speaker 1: between legally compliant, the tick box isn't actually secure. You've
- 11:04Speaker 1: argued compliance frameworks don't automatically mean security. Help us to
- 11:07Speaker 1: understand your mind.
- 11:10Speaker 2: Yeah, true, true.
- 11:11Speaker 3: I agree because, I mean, you work in an organization.
- 11:14Speaker 3: Of course, when the audit is coming, you make sure
- 11:17Speaker 3: that you are on your best behavior. You make sure
- 11:19Speaker 3: that all your I's are dotted and your T's are crossed.
- 11:22Speaker 3: But it should not be that just to pass an
- 11:27Speaker 3: audit because an audit can happen once a year or
- 11:30Speaker 3: twice a year at the maximum.
- 11:31Speaker 2: It should be a lifestyle. It should be the standard.
- 11:34Speaker 3: And that is where we are seeing a gap because
- 11:36Speaker 3: people pass security audits, but they don't actually understand implement
- 11:40Speaker 3: those changes and make it part and parcel of their
- 11:43Speaker 3: everyday activities. And that is why such breaches will always
- 11:46Speaker 3: keep on happening. Because it's culture and not just passing
- 11:51Speaker 3: the test.
- 11:52Speaker 1: My guest, Alan Juma, lead cybersecurity engineer at ESET. In
- 11:56Speaker 1: your recent work as well, you've highlighted how threat intelligence
- 11:59Speaker 1: bridges this gap. Now, your language is a language that
- 12:02Speaker 1: few understand. How should banks move away from, I think,
- 12:06Speaker 1: static annual audits towards the real-time threat intelligence that is
- 12:11Speaker 1: necessary to catch those emerging risks? Because they are innovating
- 12:15Speaker 1: all the time, aren't they?
- 12:17Speaker 2: Yeah, they're innovating.
- 12:18Speaker 3: Now, it depends on the size of the organization. For example,
- 12:20Speaker 3: like a big organization, what they should do, they should
- 12:22Speaker 3: look at it from this perspective. There should be external auditors,
- 12:25Speaker 3: external auditors to come and check the processes, the compliance
- 12:28Speaker 3: and whatnot from a regulatory perspective and also from a
- 12:31Speaker 3: security perspective. There's something we call pentesting, basically coming to
- 12:35Speaker 3: check the strengths of your system. That should be done
- 12:39Speaker 3: by an independent third party to come and ascertain that
- 12:41Speaker 3: you are actually as secure as you claim to be.
- 12:44Speaker 3: That is on the external end. Now, on the internal end,
- 12:47Speaker 3: the same processes should still be happening. Your internal audit,
- 12:49Speaker 3: because they have a better understanding of your systems, they
- 12:52Speaker 3: can actually do that maybe on a rolling basis. And
- 12:56Speaker 3: likewise for now for the internal security team. But what
- 12:59Speaker 3: will actually make a difference is if culture is changed.
- 13:03Speaker 3: Culture is changed whereby throughout the organization, there's a cultural shift, right,
- 13:07Speaker 3: from the CEO to the low-level organization. For mid-level organizations,
- 13:12Speaker 3: they may not have that budget to keep big teams
- 13:15Speaker 3: or hire, you know, expensive third-party auditors. What they can do,
- 13:18Speaker 3: they can outsource this particular functionality to individuals or organizations
- 13:22Speaker 3: that do this for a living, kind of like, you know,
- 13:25Speaker 3: Outsourcing a function that you're not really good at to
- 13:28Speaker 3: somebody who excels in that particular area. That's for middle-level
- 13:31Speaker 3: organizations in the form of maybe what you call MDR,
- 13:34Speaker 3: Managed Detection and Response Services. And also maybe for small
- 13:40Speaker 3: family-owned organizations, maybe 20 users, they can make sure that
- 13:43Speaker 3: they just occasionally get a third party to come and
- 13:47Speaker 3: help them. At the bare minimum, they should practice basic
- 13:51Speaker 3: cybersecurity hygiene.
- 13:53Speaker 1: I think you've also mentioned that financial institutions are rushing
- 13:56Speaker 1: to multi-cloud setups, maybe to stay agile, maybe to close any,
- 14:02Speaker 1: let's just call it compromised space kind of quickly. But
- 14:08Speaker 1: you also said that comes with greater management, managing security across,
- 14:13Speaker 1: I would imagine, complex environments. Are banks spreading their data
- 14:18Speaker 1: across too many cloud vendors, maybe, without the proper oversight
- 14:21Speaker 1: over multiple crowd vendors? Are they creating open doors for attackers?
- 14:28Speaker 2: I won't say that, but I will give this premise.
- 14:32Speaker 3: There's something we call an attack surface area. Let's say,
- 14:34Speaker 3: for example, your house is a four-bedroom house with two entrances.
- 14:38Speaker 3: it's very easy for you to man those two entries
- 14:40Speaker 3: because you know they're only two entries. Now if you
- 14:42Speaker 3: move to a bigger building complex whereby now there are
- 14:45Speaker 3: 15 doors, you're kind of stretched to make sure that
- 14:49Speaker 3: all these 15 entries are actually manned. Now take that
- 14:52Speaker 3: whereby you have all your data residing in one particular environment,
- 14:56Speaker 3: maybe on-prem. Now you're taking it to three service providers
- 15:00Speaker 3: on the cloud. How sure are you that you have
- 15:02Speaker 3: enough manpower, enough security to make sure that your security
- 15:05Speaker 3: mechanisms across the four different areas where your data is lying,
- 15:10Speaker 3: that is on-prem and the three data providers or the
- 15:12Speaker 3: three cloud service providers is the same. Now, that's the
- 15:15Speaker 3: complexity we're talking about. Are banks doing enough?
- 15:18Speaker 2: Yes, they're doing enough. Can they do more?
- 15:20Speaker 3: Definitely, they can only do more because all it takes
- 15:23Speaker 3: in this particular industry of ours is just one lapse.
- 15:26Speaker 3: So it needs to be a continuous process of making
- 15:29Speaker 3: sure that our defenses are up to speed and getting
- 15:33Speaker 3: people who are, you know, third party people to come
- 15:36Speaker 3: and look at it from a new perspective, a fresh
- 15:38Speaker 3: set of eyes, if I may say so.
- 15:40Speaker 1: Let's take a look at maybe a fresh response or
- 15:42Speaker 1: a fresh response that is required. We're talking about next
- 15:45Speaker 1: generation cyber attacks. We're talking about AI in the equation
- 15:49Speaker 1: as well. And the question must be, are our legacy,
- 15:53Speaker 1: maybe consumer, maybe even corporate defenses, are they obsolete against
- 15:58Speaker 1: new threats, especially the, Autonomous ones.
- 16:03Speaker 3: If they do not upgrade, they will be obsolete. The attackers,
- 16:08Speaker 3: the hackers are upgrading their tools. They're using AI to increase...
- 16:12Speaker 3: the veracity of the attack, the volumes of the attacks,
- 16:15Speaker 3: the complexity of the attacks, this AI-powered malware. Attackers are
- 16:19Speaker 3: using AI to automate these things. Now, if organizations are
- 16:23Speaker 3: still relying on the old methods whereby you're not using
- 16:26Speaker 3: next-generation firewall, your tools are not AI-powered, they're not upgraded
- 16:31Speaker 3: to be able to detect AI attacks that have been
- 16:36Speaker 3: leveraged through AI, then you will be, for lack of
- 16:39Speaker 3: a better term, a sitting duck because the attackers are
- 16:41Speaker 3: increasing their tools. They're upgrading their tools. What about the defenders?
- 16:46Speaker 3: Are you upgrading your defense mechanism? So if a company
- 16:49Speaker 3: chooses to morph and innovate, then there will be better
- 16:55Speaker 3: place to protect themselves from new age threats or AI
- 16:58Speaker 3: driven threats that we're seeing that are increasing in this
- 17:01Speaker 3: day and age.
- 17:02Speaker 1: I think a big question is, should a corporate be
- 17:07Speaker 1: hacked and paying a ransom means that their client's information
- 17:11Speaker 1: is safe? Should they pay that ransom?
- 17:16Speaker 3: That's an ethical question. There has been a debate. There
- 17:20Speaker 3: are people who say you need to pay. There are
- 17:21Speaker 3: those who say you do not need to pay. I'll
- 17:23Speaker 3: give an example. There was a company in the U.S.
- 17:25Speaker 3: called Colonial Pipeline. Now, Collodion and Palo Alto were in
- 17:29Speaker 3: charge of the oil in the U.S. Now, they were hacked, ransomware,
- 17:33Speaker 3: and the hackers were asking for a couple of Bitcoins,
- 17:35Speaker 3: translating to a number of U.S.
- 17:36Speaker 2: Dollars.
- 17:37Speaker 3: The CEO made a decision in saying, by us not
- 17:40Speaker 3: paying the ransom, we are incurring bigger losses. So he
- 17:44Speaker 3: paid from this perspective. It made business sense. Now, law
- 17:49Speaker 3: enforcers and, you know, the larger majority will say, by
- 17:53Speaker 3: you paying, you are funding an underground web of extortion.
- 17:58Speaker 3: You're funding an underground web of crime. And, you know,
- 18:02Speaker 3: God knows what other is. And also the argument against
- 18:06Speaker 3: pain would be, how sure are you that Paying out
- 18:10Speaker 3: the ransom will actually guarantee you getting your data because
- 18:14Speaker 3: it's what we call double extortion, whereby they ask you
- 18:16Speaker 3: to pay, but they still.
- 18:17Speaker 2: Leak your data on the dark web.
- 18:21Speaker 3: So I would say it depends on the moral obligation
- 18:24Speaker 3: of that particular organization. So from a professional perspective, I
- 18:28Speaker 3: will say do not pay because you're not too sure
- 18:30Speaker 3: whether you will get your data back. You don't know
- 18:33Speaker 3: the delivery process of the decryption keys, whether it will
- 18:35Speaker 3: work or not.
- 18:37Speaker 1: I get you. I started off this conversation by saying
- 18:40Speaker 1: I thought fiat was obsolete, but maybe cash in the
- 18:45Speaker 1: pocket and being able to run away from the robber
- 18:49Speaker 1: is a better kind of situation to be in.
- 18:55Speaker 2: Yeah, yeah, it might be.
- 18:56Speaker 3: I mean, although it's difficult because cash, like you're saying,
- 19:00Speaker 3: people are saying it's king, but it's becoming a bit
- 19:02Speaker 3: obsolete because of cashless payments. But the world we are
- 19:05Speaker 3: going to, we just have to improve our defenses. Just
- 19:08Speaker 3: have to improve our defenses.
- 19:09Speaker 1: And you're always playing catch up on that front, aren't you?
- 19:12Speaker 1: Because the innovation is coming from the other side.
- 19:15Speaker 3: Unfortunately, unfortunately, but it's a race that I am confident
- 19:19Speaker 3: that we will win eventually.
- 19:20Speaker 2: We will always come up.
- 19:21Speaker 1: But it's going to be at an expense if it's... Yeah,
- 19:24Speaker 1: if you're playing catch-up, if it's in response to if
- 19:26Speaker 1: you are reactive, there's always going to be a victim, unfortunately.
- 19:29Speaker 2: Actually, that's the thing, Karence. That's the thing. We should
- 19:32Speaker 2: not be reactive. We should be proactive, which is where
- 19:35Speaker 2: a majority of us find ourselves reactive, not proactive.
- 19:38Speaker 1: This has been an Insight of Note, and we appreciate
- 19:40Speaker 1: those insights. Alan Juma, Lead Cybersecurity Engineer at ESET.