WEBVTT - Cyberattacks Are a Growing Restaurant Concern

0:00:20.079 --> 0:00:22.840
<v Speaker 1>Welcome to Chopping It Up. I'm your host, Mike Haleon,

0:00:22.880 --> 0:00:26.320
<v Speaker 1>the senior restaurant and food Service analyst at Bloomberg Intelligence.

0:00:27.000 --> 0:00:29.440
<v Speaker 1>I've got a great guest today. I'd like to introduce

0:00:29.480 --> 0:00:34.040
<v Speaker 1>Deborah Nika, Senior manager of Cybersecurity and Privacy. She's also

0:00:34.080 --> 0:00:37.720
<v Speaker 1>the privacy services leader at Cone Resnik and she's also

0:00:38.000 --> 0:00:41.720
<v Speaker 1>been named Top twenty five women in Food Service and Hospitality.

0:00:41.760 --> 0:00:42.600
<v Speaker 1>Thanks for doing this.

0:00:42.520 --> 0:00:45.040
<v Speaker 2>Deborah, Thank you so much for having me on. Excited.

0:00:45.240 --> 0:00:47.839
<v Speaker 1>Yeah, this is this is cool because this is a

0:00:47.960 --> 0:00:52.000
<v Speaker 1>topic that's, you know, become increasingly important. You know, I'm

0:00:52.040 --> 0:00:55.880
<v Speaker 1>old enough to remember when investors didn't really care so much.

0:00:57.800 --> 0:01:00.640
<v Speaker 1>You know, I remember trading stocks in the early two

0:01:00.640 --> 0:01:03.920
<v Speaker 1>thousands and Target or Walmart and somebody would have a

0:01:03.960 --> 0:01:07.440
<v Speaker 1>security breach and you know, the stock would trade down

0:01:07.480 --> 0:01:09.440
<v Speaker 1>for about five minutes and then I would go back

0:01:09.480 --> 0:01:12.560
<v Speaker 1>higher than when it was traded prior to the news,

0:01:13.080 --> 0:01:15.480
<v Speaker 1>and it was just kind of people thought it was

0:01:15.880 --> 0:01:18.080
<v Speaker 1>a cost of doing business. But things have changed a

0:01:18.120 --> 0:01:20.759
<v Speaker 1>lot over the last two decades.

0:01:21.600 --> 0:01:24.640
<v Speaker 2>Yeah, I mean, you know, it's we're not living in

0:01:24.640 --> 0:01:28.160
<v Speaker 2>that world anymore. Unfortunately, we live in in a economy

0:01:28.200 --> 0:01:31.040
<v Speaker 2>where a breach is no longer blip on the radar.

0:01:32.319 --> 0:01:36.240
<v Speaker 2>A cybersecurity or privacy incident is you know, tip of

0:01:36.280 --> 0:01:39.400
<v Speaker 2>the iceberg, and everything that comes, you know, under the

0:01:39.480 --> 0:01:42.720
<v Speaker 2>water that you don't see is you know, loss of

0:01:42.720 --> 0:01:46.400
<v Speaker 2>investor confidence, loss of consumer confidence. And it really is

0:01:47.240 --> 0:01:49.960
<v Speaker 2>not a fun place to be having to crawl back

0:01:50.080 --> 0:01:54.760
<v Speaker 2>up and refresh your brand image and capability.

0:01:55.760 --> 0:01:58.160
<v Speaker 1>Yeah that's great, and so can you I guess before

0:01:58.240 --> 0:02:00.800
<v Speaker 1>we really dig in here, can you please tell the

0:02:00.840 --> 0:02:03.880
<v Speaker 1>listeners a little bit about your background and the cybersecurity

0:02:03.920 --> 0:02:05.200
<v Speaker 1>practice at Cohen Resnik.

0:02:05.760 --> 0:02:09.760
<v Speaker 2>Yeah, so I am. I am a self you know,

0:02:09.919 --> 0:02:13.600
<v Speaker 2>I am a data geek. I am so excited about information,

0:02:14.040 --> 0:02:16.480
<v Speaker 2>and you know, spend the very early years of my

0:02:16.600 --> 0:02:21.360
<v Speaker 2>career decades ago, wanting to be an academic librarian. I was,

0:02:21.520 --> 0:02:24.280
<v Speaker 2>I was really going down the path of like I

0:02:24.320 --> 0:02:27.200
<v Speaker 2>want to sit in a crusty old library and just

0:02:27.440 --> 0:02:30.320
<v Speaker 2>like go through archives and books all day every day.

0:02:31.320 --> 0:02:33.560
<v Speaker 2>And living in New York City, you really quickly learn

0:02:33.760 --> 0:02:38.080
<v Speaker 2>like that's not sustainable. Like I could be a librarian

0:02:38.080 --> 0:02:41.079
<v Speaker 2>and eat beans, or I could like take this knowledge

0:02:41.480 --> 0:02:45.240
<v Speaker 2>that I've built up and figure out how to you know, pivot.

0:02:45.280 --> 0:02:49.120
<v Speaker 2>We love that word pivot right, pivot into the corporate space,

0:02:49.680 --> 0:02:52.519
<v Speaker 2>and it was the earlier days of what today we

0:02:52.639 --> 0:02:57.040
<v Speaker 2>known as big data and really the early start of

0:02:57.240 --> 0:03:01.520
<v Speaker 2>companies figuring out, hey, we have all this information and

0:03:01.680 --> 0:03:05.000
<v Speaker 2>how do we use that information to make data informed decisions? Right?

0:03:05.880 --> 0:03:08.120
<v Speaker 2>Gone are the days where an executive licked their finger

0:03:08.160 --> 0:03:09.679
<v Speaker 2>and like put it up in the air and to

0:03:09.720 --> 0:03:12.960
<v Speaker 2>figure out which way the wind was blowing on a deal. Right.

0:03:13.880 --> 0:03:16.880
<v Speaker 2>So my career has really followed that data life cycle, Right,

0:03:16.880 --> 0:03:19.440
<v Speaker 2>how do we collect information, how do we curate information,

0:03:19.720 --> 0:03:23.240
<v Speaker 2>how do we use information and flow it through our

0:03:23.280 --> 0:03:27.079
<v Speaker 2>technology systems? How do we use that information to make

0:03:27.200 --> 0:03:31.960
<v Speaker 2>data informed data informed decisions? And then, you know, ultimately,

0:03:32.000 --> 0:03:36.160
<v Speaker 2>after a what I'll call a big Brother moment mid career,

0:03:36.680 --> 0:03:38.440
<v Speaker 2>I was like, hey, we've got to really do more

0:03:38.480 --> 0:03:41.920
<v Speaker 2>about protecting the data, right and protecting the people that

0:03:42.000 --> 0:03:45.960
<v Speaker 2>are ultimately the ones that are impacted in that you know,

0:03:46.480 --> 0:03:49.160
<v Speaker 2>by that data. So four years ago, I mean it

0:03:49.280 --> 0:03:51.760
<v Speaker 2>started way earlier, but four years ago had the great

0:03:51.760 --> 0:03:55.760
<v Speaker 2>privilege of coming over to Cohen Resnik part of their cybersecurity, tech,

0:03:55.800 --> 0:03:59.960
<v Speaker 2>risk and privacy practice and our you know, our mission

0:04:00.080 --> 0:04:03.680
<v Speaker 2>in market if you will is to help companies understand

0:04:03.840 --> 0:04:07.240
<v Speaker 2>that cyber and privacy don't need to be scary, if

0:04:07.240 --> 0:04:11.720
<v Speaker 2>they don't need to be these unattainable only technology driven capabilities.

0:04:12.000 --> 0:04:15.080
<v Speaker 2>But how do you use cybersecurity programs? How do you

0:04:15.240 --> 0:04:19.520
<v Speaker 2>use competency around privacy, compliance and management to actually drive

0:04:19.680 --> 0:04:23.560
<v Speaker 2>value in your business? Right? So if it's a transaction, right,

0:04:23.600 --> 0:04:26.000
<v Speaker 2>how are you preparing your company to make sure you're

0:04:26.000 --> 0:04:29.120
<v Speaker 2>getting great valuation? How do you make sure that you're

0:04:29.160 --> 0:04:34.440
<v Speaker 2>prepared to answer the hard questions of the underwriters of

0:04:34.560 --> 0:04:37.000
<v Speaker 2>how are your systems and how are your data secure?

0:04:37.760 --> 0:04:39.880
<v Speaker 2>How are you running your business? How are you growing

0:04:39.920 --> 0:04:42.680
<v Speaker 2>your business? How are you sustaining that growth? Cyber and

0:04:42.720 --> 0:04:46.640
<v Speaker 2>privacy are front and center to that equation. But before

0:04:46.680 --> 0:04:49.359
<v Speaker 2>we go any further, I think it's one of the

0:04:49.360 --> 0:04:51.560
<v Speaker 2>places I really like to start and chatting about this

0:04:52.279 --> 0:04:57.080
<v Speaker 2>is what is cybersecurity? What is privacy? Because when we

0:04:57.120 --> 0:05:00.560
<v Speaker 2>say cybersecurity, I can guarantee you half more audience is

0:05:00.600 --> 0:05:03.000
<v Speaker 2>going to think of a hacker sitting in a room

0:05:03.080 --> 0:05:07.960
<v Speaker 2>somewhere at night, tugging red bulls in a dark hoodie, right,

0:05:08.960 --> 0:05:14.320
<v Speaker 2>trying to crack code. And it's not that cybersecurity. There

0:05:14.320 --> 0:05:17.120
<v Speaker 2>are three main tenants of cybersecurity that we call the

0:05:17.200 --> 0:05:22.719
<v Speaker 2>CIA triad. Confidentiality, so information in your ecosystem is being

0:05:22.760 --> 0:05:28.680
<v Speaker 2>maintained in a confidential manner. Integrity that the information in

0:05:28.720 --> 0:05:33.760
<v Speaker 2>your systems can be relied upon. This is extremely important

0:05:33.800 --> 0:05:36.679
<v Speaker 2>for public retreated companies, especially when you get into things

0:05:36.720 --> 0:05:40.560
<v Speaker 2>like Starbine z Oxley, compliance and availability that your systems

0:05:40.600 --> 0:05:44.000
<v Speaker 2>are available when you need them to be right. And

0:05:44.040 --> 0:05:48.160
<v Speaker 2>then we layer on this wrapper of privacy, which historically

0:05:48.320 --> 0:05:52.120
<v Speaker 2>legally has been defined as the right to be left alone. Right,

0:05:52.440 --> 0:05:55.840
<v Speaker 2>But for companies that means you know, when, how and

0:05:55.880 --> 0:05:58.719
<v Speaker 2>to what extent can you use the information that you've

0:05:58.760 --> 0:06:02.960
<v Speaker 2>collected about your customer, about your population, about your consumers.

0:06:03.839 --> 0:06:05.800
<v Speaker 2>So you know, love, I always love to lay that

0:06:05.839 --> 0:06:08.880
<v Speaker 2>out because it really helps contextualize when it means, when

0:06:08.920 --> 0:06:11.560
<v Speaker 2>it means bringing this into your business, How does this

0:06:11.600 --> 0:06:14.719
<v Speaker 2>actually impact the decisions that you might be making about

0:06:14.760 --> 0:06:16.960
<v Speaker 2>a new business line, a growth of business line, an

0:06:16.960 --> 0:06:22.040
<v Speaker 2>investment in the technology, an investment in a membership rewards program, right,

0:06:22.839 --> 0:06:25.480
<v Speaker 2>putting an app out there to let folks, you know,

0:06:25.680 --> 0:06:29.360
<v Speaker 2>order ahead, So it makes an impact.

0:06:30.080 --> 0:06:33.400
<v Speaker 1>Cool, and so you know, there's there's a few different

0:06:33.400 --> 0:06:35.840
<v Speaker 1>types of cyber attacks. You know, I guess if you

0:06:35.839 --> 0:06:39.760
<v Speaker 1>could talk about them a little bit and maybe what

0:06:39.760 --> 0:06:43.080
<v Speaker 1>what customers should be particularly worried about right now. You know,

0:06:43.120 --> 0:06:46.240
<v Speaker 1>I think I've read something recently about ransomware attacks being

0:06:46.360 --> 0:06:49.320
<v Speaker 1>up over one hundred percent year over year, uh, and

0:06:49.360 --> 0:06:52.800
<v Speaker 1>things of that nature. So I guess maybe the the

0:06:53.960 --> 0:06:56.760
<v Speaker 1>you know, biggest issues are may depend on the size

0:06:56.800 --> 0:06:58.320
<v Speaker 1>of the company, But if you can kind of give

0:06:58.400 --> 0:07:00.040
<v Speaker 1>us some color on that would be.

0:07:01.680 --> 0:07:04.440
<v Speaker 2>So. So ransom I would definitely say ransomware is what

0:07:04.480 --> 0:07:07.800
<v Speaker 2>we're seeing get the most, the most news coverage, if

0:07:07.800 --> 0:07:11.760
<v Speaker 2>you will. Right, So, ransomware in simplest terms, is your

0:07:11.800 --> 0:07:15.480
<v Speaker 2>systems have become unavailable a threat actor. Right. It can

0:07:15.560 --> 0:07:18.600
<v Speaker 2>be somebody who is out there for monetary you know,

0:07:19.120 --> 0:07:21.480
<v Speaker 2>monetary gains. They just want to access your system to

0:07:21.560 --> 0:07:27.280
<v Speaker 2>be able to get paid. That that that that ransom, Right.

0:07:27.320 --> 0:07:30.920
<v Speaker 2>It could be political, right, It could be a activist

0:07:31.000 --> 0:07:34.520
<v Speaker 2>that is not in agreement with something that you've said

0:07:34.600 --> 0:07:37.600
<v Speaker 2>or put out there in the marketplace, which we see

0:07:37.640 --> 0:07:42.240
<v Speaker 2>impacting right our our industry today. So somebody comes in

0:07:42.400 --> 0:07:45.920
<v Speaker 2>takes over all of your systems, a system, a critical

0:07:45.960 --> 0:07:50.600
<v Speaker 2>financial system. The point of access into your environment and

0:07:50.720 --> 0:07:53.360
<v Speaker 2>doesn't let you doesn't let you back in until you've

0:07:53.400 --> 0:07:56.800
<v Speaker 2>agreed to pay a fine, right, or a fee or

0:07:58.560 --> 0:08:01.720
<v Speaker 2>some sort of cost value. The other thing we're seeing

0:08:01.760 --> 0:08:06.520
<v Speaker 2>a lot, interestingly enough, is the theft of intellectual property. Right.

0:08:06.600 --> 0:08:10.679
<v Speaker 2>So we live in a very fluid marketplace. Intellectual property

0:08:10.720 --> 0:08:15.280
<v Speaker 2>theft doesn't really get that much airtime, but it is.

0:08:16.040 --> 0:08:21.120
<v Speaker 2>It is especially especially important. I I worked with a

0:08:21.520 --> 0:08:25.120
<v Speaker 2>company a few years back, and this was a transaction.

0:08:25.360 --> 0:08:27.880
<v Speaker 2>So you know, we said, okay, what's your what's your

0:08:27.920 --> 0:08:30.240
<v Speaker 2>crown jewel? Right, what are you the most afraid of

0:08:30.320 --> 0:08:33.280
<v Speaker 2>would get exposed? And they're like, there's only one there's

0:08:33.280 --> 0:08:35.199
<v Speaker 2>only one thing that we're worried about. I said, okay,

0:08:35.840 --> 0:08:39.760
<v Speaker 2>what is it? And they go our recipes? Like, if

0:08:39.840 --> 0:08:44.640
<v Speaker 2>our recipes walked out the door, we're out of business.

0:08:45.080 --> 0:08:47.840
<v Speaker 2>There's absolutely no reason for us to continue getting up

0:08:47.840 --> 0:08:51.640
<v Speaker 2>in the morning. Right. So, where we normally think of hey,

0:08:52.040 --> 0:08:54.840
<v Speaker 2>hackers coming in, our threat threat actors coming in, they're

0:08:54.880 --> 0:08:58.640
<v Speaker 2>taking over our financial systems, they're taking over our employee data,

0:08:58.679 --> 0:09:03.320
<v Speaker 2>they're changing numbers in our finance system. So we're actually

0:09:03.360 --> 0:09:05.360
<v Speaker 2>paying them when we think we're paying a vendor or

0:09:05.400 --> 0:09:08.679
<v Speaker 2>our employee, right, this company was like, hey, if this

0:09:08.840 --> 0:09:10.760
<v Speaker 2>recipe gets out the door, we're done.

0:09:11.080 --> 0:09:11.280
<v Speaker 3>Yeah.

0:09:11.280 --> 0:09:13.400
<v Speaker 1>It's literally their secret sauce.

0:09:13.600 --> 0:09:16.000
<v Speaker 2>Literally, and you know, like I'm a native New Yorker,

0:09:16.120 --> 0:09:20.360
<v Speaker 2>we're very, very you know, proud of our pizza industry. Right,

0:09:20.559 --> 0:09:23.760
<v Speaker 2>generally speaking, can you imagine if your favorite pizza place

0:09:23.800 --> 0:09:26.080
<v Speaker 2>all of a sudden had like a new dough recipe,

0:09:26.160 --> 0:09:29.040
<v Speaker 2>new sauce recipe, like the whole nine yards, Like, I'm

0:09:29.080 --> 0:09:32.240
<v Speaker 2>not going back there, yeah, right, And you can say

0:09:32.280 --> 0:09:36.079
<v Speaker 2>the same thing up uphill right for larger industries, right,

0:09:36.120 --> 0:09:38.920
<v Speaker 2>if you're gonna change something and all of a sudden

0:09:38.960 --> 0:09:41.640
<v Speaker 2>you're like, hey, that's what we made money off of.

0:09:42.760 --> 0:09:44.400
<v Speaker 1>First thing that came to my mind was the Kernel

0:09:44.440 --> 0:09:49.280
<v Speaker 1>secret recipe. It's worth a lot, man, it's worth a lot.

0:09:50.080 --> 0:09:54.480
<v Speaker 1>Oh yeah. So, in addition to restaurant companies, what other

0:09:54.520 --> 0:09:58.719
<v Speaker 1>types of clients are seeking your help? Other industries, other

0:09:58.840 --> 0:10:01.079
<v Speaker 1>verticals who seeking your help?

0:10:01.200 --> 0:10:06.479
<v Speaker 2>Yep. So so where our team very proudly is industry agnostic.

0:10:06.960 --> 0:10:08.800
<v Speaker 2>What I focus on day and day out is what

0:10:08.840 --> 0:10:14.200
<v Speaker 2>I'll call the hospitality adjacent companies. Right, are manufacturing firms

0:10:14.200 --> 0:10:17.240
<v Speaker 2>that are coming in and maybe you know producing producing

0:10:17.280 --> 0:10:22.920
<v Speaker 2>items our consumer retail company. Real estate. Everybody always forgets

0:10:23.000 --> 0:10:27.040
<v Speaker 2>that that real estate is a bigger market than just

0:10:27.160 --> 0:10:30.559
<v Speaker 2>the you know, the industrial real estate side of things.

0:10:31.480 --> 0:10:34.160
<v Speaker 2>A lot of noise being made, especially in states like

0:10:34.200 --> 0:10:37.080
<v Speaker 2>Illinois on biometrics, Right, what does that mean for the

0:10:37.160 --> 0:10:40.760
<v Speaker 2>smart building space? What does that mean for real estate

0:10:40.800 --> 0:10:44.600
<v Speaker 2>companies that are putting technology in to help them manage

0:10:45.160 --> 0:10:49.400
<v Speaker 2>from afar technology companies a lot of noise today.

0:10:49.480 --> 0:10:49.640
<v Speaker 3>Right.

0:10:49.679 --> 0:10:54.280
<v Speaker 2>We saw Apple and the Google play Store start putting

0:10:54.800 --> 0:10:59.079
<v Speaker 2>controls in place around what kind of applications security posture, hygiene,

0:10:59.120 --> 0:11:03.280
<v Speaker 2>privacy posture and hygiene could be put out there. And

0:11:03.320 --> 0:11:05.920
<v Speaker 2>then of course, you know, we can't ever forget that

0:11:06.000 --> 0:11:11.080
<v Speaker 2>the financial services industry spend a good amount of time

0:11:11.120 --> 0:11:17.520
<v Speaker 2>they're doing cyber privacy diligence in support of transactions. Right,

0:11:17.559 --> 0:11:23.160
<v Speaker 2>So what is a potential company's potential acquisition look like

0:11:23.200 --> 0:11:25.960
<v Speaker 2>from a cyber security lens? Right? What kind of risk

0:11:26.440 --> 0:11:29.080
<v Speaker 2>is present in their environment? What does that look like

0:11:29.240 --> 0:11:33.439
<v Speaker 2>for uh, the the you know, let's call it private

0:11:33.480 --> 0:11:36.240
<v Speaker 2>equity company that that's that's going out and buying them, right,

0:11:36.280 --> 0:11:39.560
<v Speaker 2>that the risk comes with it? How does that impact

0:11:39.880 --> 0:11:43.600
<v Speaker 2>the reps and warranties insurance. How does that impact money

0:11:43.600 --> 0:11:45.800
<v Speaker 2>that that may be set aside an escrow uh to

0:11:45.920 --> 0:11:51.640
<v Speaker 2>cover potential potential liability obligations. Uh. You know, especially in

0:11:51.679 --> 0:11:57.400
<v Speaker 2>consumer and hospitality, they're very they're very people centric industries. Right.

0:11:58.960 --> 0:12:01.480
<v Speaker 2>Nobody wants to be the company that bought the other

0:12:01.559 --> 0:12:03.760
<v Speaker 2>company and all sudden to find out that, hey, there

0:12:03.840 --> 0:12:07.840
<v Speaker 2>was a breach of a million records of personal information

0:12:08.040 --> 0:12:11.600
<v Speaker 2>and we're doing business in California and all of a sudden,

0:12:11.679 --> 0:12:14.560
<v Speaker 2>you're you're running a foul of the AG's office in

0:12:14.600 --> 0:12:19.760
<v Speaker 2>California with CCPA and cpr A. Right, there's a lot,

0:12:19.960 --> 0:12:23.080
<v Speaker 2>there's a lot of contentious conversations that are happening of

0:12:23.120 --> 0:12:27.199
<v Speaker 2>what is the obligation of covering that risk in the transaction?

0:12:27.600 --> 0:12:27.960
<v Speaker 1>Okay?

0:12:27.960 --> 0:12:28.240
<v Speaker 2>Cool?

0:12:29.360 --> 0:12:32.160
<v Speaker 1>And so you know, are you seeing you know in

0:12:32.200 --> 0:12:36.000
<v Speaker 1>the research that consumers are significantly changing their behavior following

0:12:36.040 --> 0:12:38.319
<v Speaker 1>cyber attacks And I guess, hows how's that changed over

0:12:38.320 --> 0:12:39.280
<v Speaker 1>the last decade or so?

0:12:39.920 --> 0:12:43.040
<v Speaker 2>Yeah? Really, really good question. So the greatest shift that

0:12:43.080 --> 0:12:47.800
<v Speaker 2>we've seen is in upfront conscientiousness by the consumer. Who

0:12:47.880 --> 0:12:52.040
<v Speaker 2>am I getting into business with? You know? What are

0:12:52.080 --> 0:12:55.679
<v Speaker 2>they doing with my information? Is this brand doing right

0:12:55.760 --> 0:12:59.880
<v Speaker 2>by me as a consumer. A lot of we all

0:13:00.040 --> 0:13:04.319
<v Speaker 2>remember the days of the Target breach, right, and most

0:13:04.400 --> 0:13:08.439
<v Speaker 2>forget that Target was breached because of their HVAC system. Right.

0:13:08.520 --> 0:13:11.360
<v Speaker 2>It wasn't that Target went out and willingly did something

0:13:11.440 --> 0:13:15.040
<v Speaker 2>that was running a foul of their of their customers.

0:13:15.800 --> 0:13:17.640
<v Speaker 2>A big Target fan here, This is not this is

0:13:17.679 --> 0:13:19.640
<v Speaker 2>not a knock on Target, right, this is the reality

0:13:19.640 --> 0:13:22.199
<v Speaker 2>of the world that we live in. And you know

0:13:22.240 --> 0:13:25.960
<v Speaker 2>the response was okay, well, Target was required right to

0:13:26.040 --> 0:13:29.840
<v Speaker 2>go out and get credit monitoring service for their customers.

0:13:30.520 --> 0:13:32.960
<v Speaker 2>Most people still think that it was Target's goodwill. But

0:13:33.000 --> 0:13:35.840
<v Speaker 2>they went out, I got credit service monitoring for their customers.

0:13:35.880 --> 0:13:38.520
<v Speaker 2>That's not the case. They were required to do it, right.

0:13:39.000 --> 0:13:44.160
<v Speaker 2>But today we very much still see this conscientiousness by

0:13:44.559 --> 0:13:47.199
<v Speaker 2>consumers to say, you know what, I'm not going to

0:13:47.240 --> 0:13:51.440
<v Speaker 2>opt in. I'm not going to download an app that

0:13:51.720 --> 0:13:54.640
<v Speaker 2>is knowingly using my information. We're seeing a lot of

0:13:54.679 --> 0:13:58.360
<v Speaker 2>it now, right with the way that there's this conscientiousness

0:13:58.360 --> 0:14:01.040
<v Speaker 2>of how is big tech using our information? How are

0:14:01.600 --> 0:14:07.319
<v Speaker 2>they monetizing my information for their own their own purposes.

0:14:07.760 --> 0:14:11.199
<v Speaker 2>In a post ro v wead world, right, there was

0:14:11.280 --> 0:14:13.640
<v Speaker 2>a lot of a lot of light that was suddenly

0:14:13.679 --> 0:14:16.360
<v Speaker 2>shown on well, there are all these these apps that

0:14:16.440 --> 0:14:21.560
<v Speaker 2>help women, and what are their practices around cybersecurity? How

0:14:21.600 --> 0:14:26.400
<v Speaker 2>might my information be compromised there? So there's certainly this upfront,

0:14:26.480 --> 0:14:29.040
<v Speaker 2>you know, conscientiousness, and on the flip side, right, there's

0:14:29.080 --> 0:14:32.600
<v Speaker 2>a lot of brain reputation that that is impacted when

0:14:32.680 --> 0:14:35.000
<v Speaker 2>the own no moment happens, not if the owned no

0:14:35.040 --> 0:14:37.960
<v Speaker 2>moment happens, but truly when, right, what did the brand

0:14:38.080 --> 0:14:44.160
<v Speaker 2>do to protect my information? What was their social contract

0:14:44.160 --> 0:14:48.200
<v Speaker 2>that they had with me? What information did they give

0:14:48.240 --> 0:14:51.600
<v Speaker 2>me in their privacy policy, their terms and conditions upfront

0:14:51.640 --> 0:14:54.160
<v Speaker 2>about how that information they were collecting about me it

0:14:54.200 --> 0:14:57.280
<v Speaker 2>was going to be protected. So we are seeing a

0:14:57.320 --> 0:14:59.280
<v Speaker 2>little bit of a shift. We're seeing a lot more

0:14:59.320 --> 0:15:03.840
<v Speaker 2>noise come out when a brand is impacted. And the

0:15:03.880 --> 0:15:07.080
<v Speaker 2>reality is in the marketplace is that we're no longer

0:15:07.120 --> 0:15:09.560
<v Speaker 2>living in a marketplace where there's only one makeup store,

0:15:09.680 --> 0:15:11.960
<v Speaker 2>or there's only one retail shop, or there's only one

0:15:12.000 --> 0:15:14.080
<v Speaker 2>shoe store that you that you can shop in. Right,

0:15:14.160 --> 0:15:17.800
<v Speaker 2>so brands have to take that proactive stance of saying

0:15:18.280 --> 0:15:21.720
<v Speaker 2>we are in custodians of this information. We have built

0:15:21.720 --> 0:15:24.520
<v Speaker 2>this reputation in the market with our customers. We have

0:15:24.640 --> 0:15:28.200
<v Speaker 2>to do right by protecting this information, using it with fairness,

0:15:28.360 --> 0:15:31.600
<v Speaker 2>using it with transparency, because the reality is that if

0:15:31.600 --> 0:15:34.120
<v Speaker 2>our clients want it to walk away, it's going to

0:15:34.200 --> 0:15:37.080
<v Speaker 2>be that much harder for us to reacquire that client.

0:15:37.200 --> 0:15:40.320
<v Speaker 1>Yeah, more costly as well. Yeah for sure. Yeah, it's

0:15:40.320 --> 0:15:43.240
<v Speaker 1>really really interesting. You know, I think there's definitely been

0:15:43.280 --> 0:15:44.400
<v Speaker 1>more attention paid to it.

0:15:44.480 --> 0:15:44.640
<v Speaker 2>Right.

0:15:44.680 --> 0:15:48.360
<v Speaker 1>You have have people in the media, you know, looking

0:15:48.440 --> 0:15:51.240
<v Speaker 1>at you know, TikTok terms of service and things of

0:15:51.240 --> 0:15:54.520
<v Speaker 1>that nature, right, And so I think I don't know

0:15:54.520 --> 0:15:56.720
<v Speaker 1>if it's hurt their user base at all, but you know,

0:15:56.760 --> 0:16:00.440
<v Speaker 1>you have people definitely more cognizant of what's being cappedured, right,

0:16:00.480 --> 0:16:02.520
<v Speaker 1>and what's being used and how it's being used. So

0:16:03.480 --> 0:16:06.320
<v Speaker 1>I think that's a good thing. And when anytime, consumers

0:16:06.320 --> 0:16:10.280
<v Speaker 1>are willing to educate themselves, right, So, what are the

0:16:10.320 --> 0:16:13.920
<v Speaker 1>main vulnerability points both at the restaurant level and at

0:16:13.920 --> 0:16:14.640
<v Speaker 1>the corporate level.

0:16:14.880 --> 0:16:17.880
<v Speaker 2>Tough question, and I hate to sound like a consultant here,

0:16:17.920 --> 0:16:20.280
<v Speaker 2>but I'm going to give the first consultant answer, which

0:16:20.280 --> 0:16:24.000
<v Speaker 2>is it depends. It depends what the ecosystem looks like.

0:16:25.280 --> 0:16:28.320
<v Speaker 2>I'll say that, you know, even up to like four

0:16:28.400 --> 0:16:31.800
<v Speaker 2>or five, six years ago, when we had these types

0:16:31.800 --> 0:16:34.640
<v Speaker 2>of conversations with brands, it was like, oh, well, I'm

0:16:34.720 --> 0:16:38.320
<v Speaker 2>PCI compliant, my credit card data is safe, and you're like, okay,

0:16:38.360 --> 0:16:41.280
<v Speaker 2>that's fine, and I am so happy that you got

0:16:41.320 --> 0:16:49.920
<v Speaker 2>through the PCI questionnaire, which is like totally counterintuitive. Let's say,

0:16:51.360 --> 0:16:56.240
<v Speaker 2>but now we're beyond credit card information, right, and I

0:16:56.280 --> 0:16:59.840
<v Speaker 2>think that what the what the questions are now that

0:16:59.840 --> 0:17:03.160
<v Speaker 2>these companies should be asking themselves, especially in a post

0:17:03.200 --> 0:17:07.480
<v Speaker 2>COVID world, is what does your technology landscape look like? Right?

0:17:08.040 --> 0:17:13.920
<v Speaker 2>Are you using cloud based platforms to support your orders

0:17:14.000 --> 0:17:17.080
<v Speaker 2>your fulfillment? What does that look like? How are you

0:17:17.320 --> 0:17:19.959
<v Speaker 2>how are your restaurant locations or how you know, how

0:17:20.000 --> 0:17:23.600
<v Speaker 2>are your store locations interconnect one another? What does that

0:17:23.600 --> 0:17:27.840
<v Speaker 2>that mesh of network look like? How are you granting

0:17:27.920 --> 0:17:32.800
<v Speaker 2>access to your systems? How is your customer interacting? Right?

0:17:32.840 --> 0:17:35.080
<v Speaker 2>Are they coming in making a purchase and that purchase

0:17:35.119 --> 0:17:37.080
<v Speaker 2>is being shipped? Are they coming in making a purchase,

0:17:37.119 --> 0:17:39.200
<v Speaker 2>the purchase is going out the door with them? Are

0:17:39.200 --> 0:17:44.840
<v Speaker 2>they ordering ahead for pickup? Right? So this this you know,

0:17:45.040 --> 0:17:48.560
<v Speaker 2>night what we'll call ninety percent reliance on technology has

0:17:48.600 --> 0:17:50.760
<v Speaker 2>really changed the game of where you need to look

0:17:50.800 --> 0:17:55.719
<v Speaker 2>for the technology related risks. Your apps? Right, who's developing them?

0:17:55.760 --> 0:17:58.480
<v Speaker 2>Are they developing them in a secure manner? Are they

0:17:58.280 --> 0:18:01.680
<v Speaker 2>are they being updated? How is information that you're collecting

0:18:01.720 --> 0:18:06.600
<v Speaker 2>about your consumer being protected and used right through that app?

0:18:06.960 --> 0:18:10.640
<v Speaker 2>Again above and beyond just credit card information? Right? How

0:18:10.640 --> 0:18:14.760
<v Speaker 2>are you granting maintaining access to your point of sale systems?

0:18:14.800 --> 0:18:17.080
<v Speaker 2>What kind of point of sale systems are you using?

0:18:17.240 --> 0:18:20.159
<v Speaker 2>Are you are you pushing the you know, are you

0:18:20.240 --> 0:18:23.280
<v Speaker 2>pushing onus onto your vendors to make sure that they're

0:18:23.359 --> 0:18:26.240
<v Speaker 2>behaving and coding and developing their own software in a

0:18:26.280 --> 0:18:30.000
<v Speaker 2>secure manner? Right? How is it information going from store

0:18:30.040 --> 0:18:33.879
<v Speaker 2>location back to HQ? Right? What is your what is

0:18:33.920 --> 0:18:38.440
<v Speaker 2>your cyber hygiene, privacy hygiene and posture look like at headquarters? Right?

0:18:38.480 --> 0:18:41.760
<v Speaker 2>And that is logically right? How are folks get how

0:18:42.080 --> 0:18:44.760
<v Speaker 2>are folks interacting with your systems? How are they getting

0:18:44.800 --> 0:18:48.639
<v Speaker 2>into your buildings technologically? Right? What controls do you have

0:18:48.720 --> 0:18:51.600
<v Speaker 2>in place around your technology systems? Again? How are you

0:18:51.680 --> 0:18:54.760
<v Speaker 2>working in partnership with your vendors to make sure that

0:18:54.760 --> 0:18:57.119
<v Speaker 2>that if you're if you're using a cloud based system

0:18:57.119 --> 0:18:58.840
<v Speaker 2>and you're like, oh, yeah, you know so and so

0:18:59.000 --> 0:19:03.040
<v Speaker 2>companies responsible for security because they're providing me this platform.

0:19:03.720 --> 0:19:06.720
<v Speaker 2>Guess what, buddy, read the fine print because that risk

0:19:06.800 --> 0:19:09.720
<v Speaker 2>transfer that you think that you're making is not really there. Right.

0:19:09.720 --> 0:19:12.040
<v Speaker 2>There are obligations that you've got on your side to

0:19:12.080 --> 0:19:15.840
<v Speaker 2>make sure that you've got appropriate controls in place. How

0:19:15.880 --> 0:19:20.280
<v Speaker 2>are those systems interacting with one another? Right? What does

0:19:20.280 --> 0:19:23.639
<v Speaker 2>that interface look like between your systems? How are you

0:19:23.840 --> 0:19:28.639
<v Speaker 2>educating your people and your users to maintain a sense

0:19:28.720 --> 0:19:32.240
<v Speaker 2>of cybersecurity hygiene? Right? You know one of the latest

0:19:32.280 --> 0:19:36.960
<v Speaker 2>statistics out there is sixty five percent of cybersecurity incidents

0:19:37.000 --> 0:19:39.080
<v Speaker 2>start with your people. Somebody click the link that they

0:19:39.119 --> 0:19:44.000
<v Speaker 2>shouldn't have, right, and we're we're a click happy bunch humans. Right,

0:19:45.200 --> 0:19:47.760
<v Speaker 2>So are you educating your people on hey, don't click

0:19:47.760 --> 0:19:50.840
<v Speaker 2>the link. If your finance team is getting requests for wires,

0:19:50.840 --> 0:19:53.760
<v Speaker 2>are they calling the person to confirm that it's a

0:19:53.840 --> 0:19:57.239
<v Speaker 2>legitimate request? The account number has not been has not

0:19:57.280 --> 0:20:02.000
<v Speaker 2>been compromised in an email transit? Are you? Are you

0:20:02.160 --> 0:20:05.560
<v Speaker 2>doing technical testing of your boundaries? Right? Are you having

0:20:05.600 --> 0:20:08.320
<v Speaker 2>an objective third party come in and look at at

0:20:08.400 --> 0:20:10.800
<v Speaker 2>all of this And I think the other piece that

0:20:10.920 --> 0:20:12.880
<v Speaker 2>really really gets lost in all of this is are

0:20:12.920 --> 0:20:17.439
<v Speaker 2>you empowering your information security and your privacy teams to

0:20:17.600 --> 0:20:19.800
<v Speaker 2>do what they need to do? Are you giving them,

0:20:20.040 --> 0:20:22.359
<v Speaker 2>you know, the monetary support. Are you giving them the

0:20:22.480 --> 0:20:25.920
<v Speaker 2>right human capital to be able to do this? Are

0:20:25.920 --> 0:20:28.880
<v Speaker 2>you giving them a seat in the conversation to say, hey,

0:20:28.920 --> 0:20:31.679
<v Speaker 2>here's where we are today, Here's where we need to

0:20:31.720 --> 0:20:34.320
<v Speaker 2>be in the future to meet all the obligations that

0:20:34.320 --> 0:20:39.879
<v Speaker 2>we're putting out there. Right. Are you educating your board again?

0:20:40.359 --> 0:20:43.920
<v Speaker 2>You know, the SEC has proposed proposed rules out there

0:20:44.000 --> 0:20:47.600
<v Speaker 2>for publicly traded companies that you know, in the future,

0:20:47.640 --> 0:20:49.680
<v Speaker 2>should these rules pass, you're going to have to have

0:20:49.840 --> 0:20:53.720
<v Speaker 2>board educated members, right, really be aware of what what

0:20:53.760 --> 0:20:56.840
<v Speaker 2>does cybersecurity mean? Right? And and you've got to be

0:20:56.880 --> 0:21:00.119
<v Speaker 2>able to train your board on what cybersecurity risk look

0:21:00.320 --> 0:21:04.200
<v Speaker 2>like for the company. So I think where we talk about,

0:21:04.240 --> 0:21:06.960
<v Speaker 2>you know, what is the vulnerability to a brand? What

0:21:07.000 --> 0:21:08.720
<v Speaker 2>you know, you've also got to really weigh what the

0:21:08.800 --> 0:21:11.840
<v Speaker 2>impact is going to be. Right. You could have let's

0:21:11.880 --> 0:21:17.680
<v Speaker 2>say a single location Wi Fi go down, it sticks, right,

0:21:18.200 --> 0:21:20.560
<v Speaker 2>It could be malicious intent behind that, it could just

0:21:20.600 --> 0:21:23.639
<v Speaker 2>be the fact that it's Wi Fi and it's not

0:21:24.040 --> 0:21:27.600
<v Speaker 2>always going to be friendly, right, But what if your

0:21:27.640 --> 0:21:30.400
<v Speaker 2>critical application goes down? What if your CRM goes down?

0:21:30.480 --> 0:21:33.480
<v Speaker 2>What if your order payment system goes down? Right? And

0:21:33.520 --> 0:21:35.639
<v Speaker 2>it is a threat actor? You know, what does it

0:21:35.680 --> 0:21:38.679
<v Speaker 2>mean for your business to be out of you know,

0:21:38.800 --> 0:21:42.200
<v Speaker 2>out of technology service for four hours, for eight hours,

0:21:42.359 --> 0:21:45.479
<v Speaker 2>for three weeks? How many dollars are not coming in

0:21:45.520 --> 0:21:48.400
<v Speaker 2>the door because of that? Right? So you've really got

0:21:48.400 --> 0:21:51.159
<v Speaker 2>to understand what are your crown jewel systems, What technology

0:21:51.200 --> 0:21:55.520
<v Speaker 2>do you need to keep safe? And what what investment

0:21:55.640 --> 0:21:58.280
<v Speaker 2>are you willing to make as a company to make

0:21:58.320 --> 0:21:59.720
<v Speaker 2>sure they stay safe.

0:22:00.840 --> 0:22:04.160
<v Speaker 1>Yeah, that's great. And you know what I found when

0:22:04.160 --> 0:22:05.679
<v Speaker 1>I was doing a little bit of legwork before we

0:22:05.720 --> 0:22:08.840
<v Speaker 1>spoke that was interesting was like how much they spoke

0:22:08.840 --> 0:22:14.119
<v Speaker 1>about employees and protecting employee data, right, because I've just

0:22:14.160 --> 0:22:17.800
<v Speaker 1>been thinking about you thinking about it at the consumer level, right,

0:22:17.880 --> 0:22:20.359
<v Speaker 1>and the credit card data and the loyalty data and

0:22:21.080 --> 0:22:24.760
<v Speaker 1>all that kind of stuff, But obviously securing employee data

0:22:24.800 --> 0:22:25.359
<v Speaker 1>is important too.

0:22:25.480 --> 0:22:30.720
<v Speaker 2>Right. So without naming names of brands, because I feel

0:22:30.720 --> 0:22:33.359
<v Speaker 2>for the brands, irrelevant of size of these companies, I

0:22:33.400 --> 0:22:36.399
<v Speaker 2>feel for the brands that are dealing with this. The

0:22:36.440 --> 0:22:40.760
<v Speaker 2>state of Illinois gifted us some new laws around bio

0:22:41.400 --> 0:22:45.360
<v Speaker 2>biometric information. Right, So I think you're spot on. When

0:22:45.400 --> 0:22:48.600
<v Speaker 2>companies think about data, we're always thinking about consumer We

0:22:48.680 --> 0:22:51.720
<v Speaker 2>really also need to include employees in that. And the

0:22:51.760 --> 0:22:55.800
<v Speaker 2>reason I bring it up is because it is not unmanageable.

0:22:55.880 --> 0:22:57.960
<v Speaker 2>Again speaking in broad strokes here, I don't want to

0:22:57.960 --> 0:23:01.920
<v Speaker 2>throw any any companies under the US on this. Right.

0:23:03.800 --> 0:23:07.040
<v Speaker 2>When we think about employees, I'll give you this scenario.

0:23:07.119 --> 0:23:10.959
<v Speaker 2>An employee walks in the door. You're using, you know,

0:23:11.800 --> 0:23:17.800
<v Speaker 2>upper right quadrant technology for your employee timekeeping systems, and

0:23:17.840 --> 0:23:21.320
<v Speaker 2>your employee comes in, they scan their thumbprint, they've clocked in,

0:23:21.800 --> 0:23:26.160
<v Speaker 2>they work the shift, scan back out, end of day. Right,

0:23:27.240 --> 0:23:29.720
<v Speaker 2>How are you protecting that information? Are you? Did you

0:23:29.760 --> 0:23:32.280
<v Speaker 2>give disclosure to your employees that you're going to be

0:23:32.359 --> 0:23:36.480
<v Speaker 2>using your biometric information to do this? How are you

0:23:36.600 --> 0:23:40.960
<v Speaker 2>maintaining the security of that information that you're collecting. How

0:23:41.000 --> 0:23:46.840
<v Speaker 2>are you maintaining information that your employee and their health

0:23:46.840 --> 0:23:50.439
<v Speaker 2>care status? Right, especially if in the restaurant industry world, right,

0:23:50.480 --> 0:23:54.720
<v Speaker 2>if there's a health matter that's being investigated related to

0:23:54.760 --> 0:23:57.359
<v Speaker 2>an employee. So there are all these laws that are

0:23:57.480 --> 0:24:00.359
<v Speaker 2>very specific to employee data. I am not into I

0:24:00.400 --> 0:24:02.480
<v Speaker 2>don't want to ever be a labor attorney. I give that,

0:24:02.640 --> 0:24:05.880
<v Speaker 2>I give that that group of specialists great great respect. Right,

0:24:06.200 --> 0:24:08.240
<v Speaker 2>but what are you doing? And do you understand the

0:24:08.880 --> 0:24:14.560
<v Speaker 2>complex environment that you that you're operating in about that information? Right?

0:24:15.080 --> 0:24:18.679
<v Speaker 2>You know, Illinois, California. You know there are states that

0:24:18.920 --> 0:24:21.520
<v Speaker 2>are really making it easy for businesses to operate, and

0:24:21.560 --> 0:24:23.160
<v Speaker 2>there are states that make it a little bit tougher.

0:24:23.200 --> 0:24:26.200
<v Speaker 2>And you've got to really do the work to understand

0:24:26.720 --> 0:24:30.160
<v Speaker 2>what are our obligations And a lot of it really

0:24:30.200 --> 0:24:33.400
<v Speaker 2>comes down to how are you informing your employees about this? Right?

0:24:33.480 --> 0:24:36.640
<v Speaker 2>What does that look like to inform you employees? Here's

0:24:36.680 --> 0:24:38.919
<v Speaker 2>the information we've re collected about you. Here's how that

0:24:38.960 --> 0:24:41.719
<v Speaker 2>information is being used, Here's where that information is stored,

0:24:41.760 --> 0:24:44.960
<v Speaker 2>Here's how it might be shared. Because it's not just

0:24:45.280 --> 0:24:48.400
<v Speaker 2>you know, the yester year of Oh, we're collecting employee

0:24:48.440 --> 0:24:50.760
<v Speaker 2>information so we can send it to our our you know,

0:24:50.800 --> 0:24:53.520
<v Speaker 2>the company that does our health insurance. Right now, all

0:24:53.560 --> 0:24:56.600
<v Speaker 2>of a sudden, you're saying, Okay, we're collecting really sensitive

0:24:56.640 --> 0:25:02.720
<v Speaker 2>information about an employee, and maybe we're using AI to decide, Hey,

0:25:02.760 --> 0:25:05.480
<v Speaker 2>this person works this shift and that person works that

0:25:05.600 --> 0:25:09.000
<v Speaker 2>shift because of X y Z capability. But there are

0:25:09.040 --> 0:25:12.480
<v Speaker 2>inherent biases to a lot of this that I think

0:25:12.480 --> 0:25:15.240
<v Speaker 2>that our industry, well the technology industry least, is still

0:25:15.680 --> 0:25:19.920
<v Speaker 2>fleshing out. But I will say we're seeing a lot

0:25:20.080 --> 0:25:25.120
<v Speaker 2>creeping up, especially in Illinois. What does it mean to

0:25:25.240 --> 0:25:31.200
<v Speaker 2>use employee information appropriately even if it's for legitimate business practice?

0:25:32.600 --> 0:25:34.919
<v Speaker 2>And you know where can companies start getting in trouble?

0:25:34.960 --> 0:25:38.640
<v Speaker 1>And you mentioned the employee data being upper right quadrant data.

0:25:38.680 --> 0:25:40.760
<v Speaker 1>I'm not familiar with the quadrants. I can kind of

0:25:41.119 --> 0:25:43.560
<v Speaker 1>maybe back into a guest there, but if you can

0:25:43.640 --> 0:25:45.440
<v Speaker 1>kind of talk about the quadrants a little bit, talk

0:25:45.440 --> 0:25:48.800
<v Speaker 1>about what the upper right quadrant means for you know,

0:25:50.440 --> 0:25:51.280
<v Speaker 1>you know us layman.

0:25:53.520 --> 0:25:57.920
<v Speaker 2>So oftentimes when I talk with businesses and we start

0:25:57.960 --> 0:26:02.080
<v Speaker 2>having conversations of hey, we're finally out of COVID, right,

0:26:02.600 --> 0:26:05.400
<v Speaker 2>We're finally back to a world where we can make

0:26:05.480 --> 0:26:08.479
<v Speaker 2>technology investment. We're like, we're gonna go look at Gartner,

0:26:08.520 --> 0:26:10.800
<v Speaker 2>We're gonna go look at Forrester, and we're gonna pick

0:26:10.920 --> 0:26:14.479
<v Speaker 2>like the top leader, right. The leader of this is

0:26:14.600 --> 0:26:19.000
<v Speaker 2>like the best tool or application that we can get

0:26:19.000 --> 0:26:21.640
<v Speaker 2>in the space. And this is this you know, Gartner

0:26:21.760 --> 0:26:25.720
<v Speaker 2>leading or Forrester wave leading technology is going to solve

0:26:25.840 --> 0:26:29.119
<v Speaker 2>all of our problems. You know, I'll context I'll contextualize

0:26:29.160 --> 0:26:32.440
<v Speaker 2>them saying Gartner and Forrester are great resources for information. Right,

0:26:32.440 --> 0:26:36.320
<v Speaker 2>They're fantastic. I use them quite a bit. But you've

0:26:36.359 --> 0:26:38.919
<v Speaker 2>got to then say, Okay, we're making this investment technology

0:26:38.960 --> 0:26:44.760
<v Speaker 2>we're going with you know this this this hr information system, right,

0:26:45.080 --> 0:26:47.240
<v Speaker 2>but what does that mean for your business? You're making

0:26:47.280 --> 0:26:53.840
<v Speaker 2>this gigantic investment. These these tools, technologies, applications are not cheap, right,

0:26:54.320 --> 0:26:57.480
<v Speaker 2>How are you then deploying that in your environment? A?

0:26:57.840 --> 0:27:01.160
<v Speaker 2>What technology risk are you introducing to your environment by

0:27:01.200 --> 0:27:04.800
<v Speaker 2>doing this? B? How are you setting appropriate controls of

0:27:04.840 --> 0:27:07.880
<v Speaker 2>who's got access to what information is it? Is it?

0:27:08.040 --> 0:27:12.760
<v Speaker 2>Com measure it with the job that they were doing? Right? See?

0:27:12.800 --> 0:27:16.840
<v Speaker 2>How are you giving people appropriate disclosure about what information

0:27:16.960 --> 0:27:21.280
<v Speaker 2>you're storing about them? Right? How are you integrating these

0:27:21.280 --> 0:27:25.400
<v Speaker 2>systems with other technologies that are that are in your environment?

0:27:25.960 --> 0:27:27.800
<v Speaker 2>And I think the big one, which is which is

0:27:28.560 --> 0:27:32.840
<v Speaker 2>let's call it one of the largest emerging issues in

0:27:33.280 --> 0:27:36.840
<v Speaker 2>cyber and privacy is what kind of onus are you

0:27:36.920 --> 0:27:40.680
<v Speaker 2>taking on because of this third party? Right? You got

0:27:40.720 --> 0:27:43.560
<v Speaker 2>you went out, you spent half a million bucks on

0:27:43.840 --> 0:27:46.680
<v Speaker 2>a system that is, Oh, but it's great. It's SaaS

0:27:46.720 --> 0:27:48.920
<v Speaker 2>solution and we don't need to have a server form

0:27:49.000 --> 0:27:51.960
<v Speaker 2>anywhere supporting it. And this vendor is going to do

0:27:52.040 --> 0:27:54.399
<v Speaker 2>all this maintenance and they're going to support it for

0:27:54.480 --> 0:27:56.719
<v Speaker 2>us and we don't need to worry about like backing

0:27:56.720 --> 0:28:00.119
<v Speaker 2>it up or disaster recovery or you know, UX and

0:28:00.240 --> 0:28:03.879
<v Speaker 2>U I updates. It's fantastic. Right, But somewhere there's a

0:28:03.920 --> 0:28:07.600
<v Speaker 2>paragraph in your contract that could say, hey, we reserve

0:28:07.640 --> 0:28:10.040
<v Speaker 2>the right to use this data that you're uploading as

0:28:10.040 --> 0:28:14.879
<v Speaker 2>we see fit. Right, what kind of exposure did you

0:28:14.960 --> 0:28:19.880
<v Speaker 2>just introduce to your business because of this third party? Right? Alternatively,

0:28:20.280 --> 0:28:23.960
<v Speaker 2>right on the extreme opposite side of the example, we'll

0:28:24.080 --> 0:28:27.199
<v Speaker 2>get cases where the company is like, look, we just

0:28:27.280 --> 0:28:30.840
<v Speaker 2>need something. I googled first to ad that came up.

0:28:30.840 --> 0:28:34.119
<v Speaker 2>We went with them, and oh, by the way, we

0:28:34.200 --> 0:28:38.400
<v Speaker 2>got like the first year free for I guess right,

0:28:38.520 --> 0:28:43.720
<v Speaker 2>and it's great. Right, And then very similarly, like you know,

0:28:43.880 --> 0:28:46.840
<v Speaker 2>you're like, okay, we'll review the contract for you from

0:28:46.960 --> 0:28:50.920
<v Speaker 2>a cyber or privacy perspective, and the contracts two pages

0:28:52.240 --> 0:28:55.200
<v Speaker 2>right and a full page of it says, by the way,

0:28:55.280 --> 0:28:58.680
<v Speaker 2>you got this free year because you're giving us access

0:28:58.760 --> 0:29:01.200
<v Speaker 2>to use your information turn around and sell it to

0:29:01.240 --> 0:29:04.600
<v Speaker 2>another customer. And that's why you're not paying the ninety

0:29:04.640 --> 0:29:09.480
<v Speaker 2>nine ninety nine a month in twelve equal installments, right.

0:29:10.720 --> 0:29:12.640
<v Speaker 2>And what happens with those with those smaller mom and

0:29:12.680 --> 0:29:16.200
<v Speaker 2>pop companies that are that are out there is they're

0:29:16.240 --> 0:29:18.960
<v Speaker 2>not doing the due diligence to make sure that that tool,

0:29:19.000 --> 0:29:22.120
<v Speaker 2>application technology right and naven what you will is secure.

0:29:22.720 --> 0:29:26.640
<v Speaker 2>They're not helping you to shore up and mature your

0:29:26.680 --> 0:29:33.160
<v Speaker 2>own cybersecurity hygiene because they're introducing right a mode into

0:29:33.280 --> 0:29:37.960
<v Speaker 2>your environment where this is living. They are they may

0:29:38.120 --> 0:29:40.680
<v Speaker 2>or may not be acting above board in terms of

0:29:40.720 --> 0:29:46.280
<v Speaker 2>what the data sharing. The data sharing is behind, you know,

0:29:46.320 --> 0:29:48.640
<v Speaker 2>behind the scenes, and all of a sudden, right this

0:29:48.760 --> 0:29:50.280
<v Speaker 2>thing that you were like, oh this is great, we

0:29:50.560 --> 0:29:53.560
<v Speaker 2>got out of paying ninety nine ninety nine a month, Well, hey,

0:29:53.640 --> 0:29:56.960
<v Speaker 2>guess guess what you just took on from a risk perspective, right,

0:29:57.440 --> 0:30:00.680
<v Speaker 2>So there's there's a lot of the lot of you know,

0:30:00.800 --> 0:30:03.800
<v Speaker 2>obligation that companies have that doesn't always get seen of

0:30:03.880 --> 0:30:08.600
<v Speaker 2>What does there look like to manage proactively manage their

0:30:08.800 --> 0:30:13.080
<v Speaker 2>their third party risk? Right, and especially in hospitality and

0:30:13.200 --> 0:30:19.840
<v Speaker 2>especially in in in the food industry. Food companies should

0:30:19.840 --> 0:30:22.480
<v Speaker 2>be doing food, They're not. They're not technology companies, right,

0:30:22.600 --> 0:30:26.160
<v Speaker 2>So the likely, the high likelihood is there's a lot

0:30:26.200 --> 0:30:30.880
<v Speaker 2>of these tools in their ecosystem, right and likely not

0:30:30.960 --> 0:30:31.840
<v Speaker 2>getting looked at.

0:30:31.960 --> 0:30:34.480
<v Speaker 1>Is there a way for them to negotiate, to negotiate

0:30:34.520 --> 0:30:36.280
<v Speaker 1>out some of that that third party risk?

0:30:36.480 --> 0:30:42.160
<v Speaker 3>When when yeah, absolutely absolutely, Again, I'm not not attorney,

0:30:42.200 --> 0:30:46.760
<v Speaker 3>not legal advice, but consult your friendly neighborhood attorney in

0:30:46.800 --> 0:30:47.320
<v Speaker 3>a space.

0:30:48.040 --> 0:30:50.360
<v Speaker 2>The other thing that companies really should be considering is

0:30:50.400 --> 0:30:52.760
<v Speaker 2>what does their data sharing agreement look like with these

0:30:53.760 --> 0:30:57.240
<v Speaker 2>with these vendors, are they are you know, are companies

0:30:57.280 --> 0:31:01.000
<v Speaker 2>setting out the appropriate rules of the road based on

0:31:01.240 --> 0:31:06.080
<v Speaker 2>their business there, the jurisdictions where they're, where they're conducting business,

0:31:06.160 --> 0:31:08.960
<v Speaker 2>their type of end consumer. Are they setting out the

0:31:09.000 --> 0:31:13.080
<v Speaker 2>right rules of the road with these vendors saying here's

0:31:13.120 --> 0:31:16.880
<v Speaker 2>how you may or may not use information, right, here's

0:31:16.960 --> 0:31:21.160
<v Speaker 2>how you here's how you are obligated to help us

0:31:21.280 --> 0:31:23.800
<v Speaker 2>in the case we have a need around this information,

0:31:24.560 --> 0:31:28.640
<v Speaker 2>especially for the companies that are required to be GDPR compliant,

0:31:28.720 --> 0:31:31.600
<v Speaker 2>especially for the companies that are required to comply with

0:31:31.680 --> 0:31:36.840
<v Speaker 2>CCPA CPR, companies that are operating states with emerging or

0:31:38.120 --> 0:31:43.440
<v Speaker 2>newly enacted privacy laws. This is going to become critically important.

0:31:44.840 --> 0:31:50.320
<v Speaker 2>Understand what your data sharing landscape looks like, and the

0:31:50.520 --> 0:31:53.960
<v Speaker 2>risk around third party is front and center and that conversation.

0:31:54.360 --> 0:31:58.520
<v Speaker 2>Understand Yes, you as a company, you're collecting information, you're

0:31:58.640 --> 0:32:03.040
<v Speaker 2>using it right for again fully legitimate business purpose, but

0:32:03.120 --> 0:32:06.080
<v Speaker 2>then you're sharing it right and you may not think

0:32:06.120 --> 0:32:10.560
<v Speaker 2>of sharing it in that way, but ultimately that that

0:32:10.680 --> 0:32:12.800
<v Speaker 2>is what it looks like. Right, you are sharing information

0:32:14.320 --> 0:32:19.440
<v Speaker 2>with your technology platform. What are the appropriate rules of

0:32:19.480 --> 0:32:21.920
<v Speaker 2>the road for that platform to be able to use

0:32:22.120 --> 0:32:22.640
<v Speaker 2>your data?

0:32:23.040 --> 0:32:26.880
<v Speaker 1>Okay? Cool? And you know, can companies also ensure some

0:32:27.040 --> 0:32:30.160
<v Speaker 1>of their risk against cyber attacks and third priority risk?

0:32:32.280 --> 0:32:36.120
<v Speaker 2>I love that question. I spend a lot of my

0:32:36.240 --> 0:32:43.160
<v Speaker 2>time talking about that question. So cyber insurance is incredibly expensive,

0:32:44.880 --> 0:32:48.440
<v Speaker 2>it is harder and harder to get. There are more

0:32:48.480 --> 0:32:53.000
<v Speaker 2>and more exclusions being put into policies. So yes, you

0:32:53.120 --> 0:32:55.479
<v Speaker 2>can go out and you can get it. It is

0:32:55.600 --> 0:32:59.720
<v Speaker 2>not a set it and forget it. Most cybersecurity insurance

0:32:59.720 --> 0:33:08.480
<v Speaker 2>pols today are very descriptive of what capabilities a company

0:33:08.560 --> 0:33:10.480
<v Speaker 2>has to have in place in order for the cyber

0:33:10.560 --> 0:33:15.920
<v Speaker 2>insurance policy to be effective and cover a potential breach loss,

0:33:15.960 --> 0:33:20.000
<v Speaker 2>whatever it is. So most of the time you speak

0:33:20.000 --> 0:33:21.440
<v Speaker 2>to folks and they're like, no, I don't need to

0:33:21.480 --> 0:33:23.880
<v Speaker 2>do anything. I have cyber insurance and it'll be great.

0:33:24.000 --> 0:33:26.440
<v Speaker 2>And then the oh no moment happens because again nobody

0:33:26.520 --> 0:33:29.880
<v Speaker 2>is immune from an oh no moment, and they go

0:33:29.960 --> 0:33:31.760
<v Speaker 2>to their cyber and share and they're like, hey, I

0:33:31.800 --> 0:33:35.760
<v Speaker 2>have to pay like two million dollars if ransom right

0:33:35.800 --> 0:33:38.560
<v Speaker 2>to get my finances the back. The cybernture is like, no,

0:33:38.560 --> 0:33:41.040
<v Speaker 2>I'm not covering that. It's like, what what do you mean? Like,

0:33:41.080 --> 0:33:44.280
<v Speaker 2>we've been paying you a hundred thousand dollars right for this,

0:33:46.040 --> 0:33:49.560
<v Speaker 2>and cybernture is like, well, you didn't have any proactive

0:33:50.440 --> 0:33:56.040
<v Speaker 2>controls in place. You weren't doing your job in making

0:33:56.080 --> 0:34:01.320
<v Speaker 2>sure that you're authenticating traffic that's crossing network. You weren't

0:34:01.360 --> 0:34:05.080
<v Speaker 2>doing annual risk assessments to understand where you might have

0:34:05.160 --> 0:34:09.040
<v Speaker 2>cybersecurity risk exposures. You weren't doing a good job at

0:34:09.080 --> 0:34:11.920
<v Speaker 2>managing your third party risk. And even though you had

0:34:11.960 --> 0:34:14.600
<v Speaker 2>a great CRM platform that you paid half a million

0:34:14.640 --> 0:34:17.120
<v Speaker 2>dollars for right two years ago and you finally got

0:34:17.120 --> 0:34:21.239
<v Speaker 2>the implementation, and that's where the vulnerability came from. You

0:34:21.320 --> 0:34:25.239
<v Speaker 2>didn't do enough to proactively understand what your cyber risk

0:34:25.320 --> 0:34:30.400
<v Speaker 2>landscape looks like internally and to mature your capabilities to

0:34:30.520 --> 0:34:35.719
<v Speaker 2>mitigate those risks. So, yeah, cyber insurance is available out there,

0:34:35.760 --> 0:34:38.080
<v Speaker 2>but there is a large obligation that's still put on

0:34:38.160 --> 0:34:42.719
<v Speaker 2>companies to have that oh no, right file ready if

0:34:42.760 --> 0:34:45.240
<v Speaker 2>you will. Hey, we've been doing every year, we've been doing,

0:34:45.480 --> 0:34:49.640
<v Speaker 2>you know, an objective you know, cybersecurity risk assessment. We

0:34:49.760 --> 0:34:52.480
<v Speaker 2>understand that we have areas that we can mature, but

0:34:52.560 --> 0:34:56.000
<v Speaker 2>we've got these baseline competencies in place. We're making sure

0:34:56.000 --> 0:34:59.080
<v Speaker 2>that folks are accessing our network in a secure manner.

0:34:59.120 --> 0:35:02.560
<v Speaker 2>We're using multi doctor authentication for people coming in. We're

0:35:02.600 --> 0:35:06.680
<v Speaker 2>doing proactive scanning of our network to detect any any

0:35:06.800 --> 0:35:11.040
<v Speaker 2>potentially malicious activity. You know, We're doing annual penetration testing

0:35:11.120 --> 0:35:14.040
<v Speaker 2>to make sure that that the walls around our castle

0:35:15.200 --> 0:35:19.160
<v Speaker 2>are intact. We're educating our users with security awareness training.

0:35:19.239 --> 0:35:23.879
<v Speaker 2>We're training our leadership to be able to identify spearfishing

0:35:23.920 --> 0:35:27.560
<v Speaker 2>and you know, whale fishing. And if you have those

0:35:27.600 --> 0:35:31.200
<v Speaker 2>in place, you're in a much better position to go

0:35:31.280 --> 0:35:34.320
<v Speaker 2>to your insure and say, look, the own no woman happens.

0:35:35.160 --> 0:35:37.840
<v Speaker 2>We need help, you know, we need hey, we ensure,

0:35:37.880 --> 0:35:40.279
<v Speaker 2>we need your help being able to engage a an

0:35:40.280 --> 0:35:44.640
<v Speaker 2>incident response team or a ransom you know, uh recovery

0:35:44.680 --> 0:35:46.680
<v Speaker 2>team and somebody's got to go figure out how to

0:35:46.680 --> 0:35:49.840
<v Speaker 2>buy bitcoin for me to pay this ransom. Right, But

0:35:49.920 --> 0:35:51.799
<v Speaker 2>we did everything that we were supposed to do, and

0:35:51.840 --> 0:35:55.400
<v Speaker 2>the own no, theman still happened. And in those cases,

0:35:56.120 --> 0:35:59.640
<v Speaker 2>the insurers are looking. You know, it's a more favorable

0:35:59.680 --> 0:36:02.920
<v Speaker 2>outcome for the most part. Now that's not written in stone.

0:36:03.800 --> 0:36:06.400
<v Speaker 2>There are some insurers that are better than others. I

0:36:06.920 --> 0:36:11.520
<v Speaker 2>will not name names here, right, but but that's really

0:36:11.560 --> 0:36:14.480
<v Speaker 2>where we try to help folks understand. You could have

0:36:14.640 --> 0:36:18.359
<v Speaker 2>a great cyber insurance policy. That doesn't mean that you're

0:36:18.400 --> 0:36:19.280
<v Speaker 2>fully protected.

0:36:20.200 --> 0:36:23.880
<v Speaker 1>Okay, cool, cool? Yeah, And I guess in terms of

0:36:23.920 --> 0:36:27.480
<v Speaker 1>the insurers you you recommend, I guess we have to

0:36:27.480 --> 0:36:27.920
<v Speaker 1>pay for that.

0:36:33.160 --> 0:36:35.160
<v Speaker 2>You can we could we could have a one on

0:36:35.160 --> 0:36:37.839
<v Speaker 2>one a lovely one on one chat on you know

0:36:38.000 --> 0:36:42.640
<v Speaker 2>what that space looks like. But I'll refrain from publicizing

0:36:42.800 --> 0:36:45.000
<v Speaker 2>too widely my my fearing.

0:36:45.320 --> 0:36:47.640
<v Speaker 1>So what should a restaurant chain do if they suffer

0:36:47.640 --> 0:36:48.440
<v Speaker 1>a cyber attack?

0:36:49.680 --> 0:36:54.239
<v Speaker 2>Engage a good attorney. I say that tongue in cheek,

0:36:54.280 --> 0:36:59.480
<v Speaker 2>but you know this is really where your service providers

0:36:59.600 --> 0:37:03.680
<v Speaker 2>that you have relationships with come into play. So most

0:37:03.719 --> 0:37:09.040
<v Speaker 2>of you know, very very you know openly your attorney

0:37:09.080 --> 0:37:10.600
<v Speaker 2>is going to be critical in a lot of this.

0:37:11.040 --> 0:37:13.160
<v Speaker 2>There's going to be a lot of conversations that happen

0:37:13.239 --> 0:37:19.280
<v Speaker 2>of what do we know, what don't we know? And frankly,

0:37:19.400 --> 0:37:24.040
<v Speaker 2>attorney client privilege is going to be very helpful right

0:37:24.200 --> 0:37:26.960
<v Speaker 2>until you get your feet under you. Obviously, there are

0:37:27.000 --> 0:37:31.200
<v Speaker 2>obligations in certain jurisdictions to let h you know, an

0:37:31.200 --> 0:37:34.560
<v Speaker 2>Attorney General's office know if you're if the cyber event

0:37:34.560 --> 0:37:37.120
<v Speaker 2>that happens is a data breach and there's a disclosure

0:37:37.200 --> 0:37:40.080
<v Speaker 2>of uh personally that the fiable information right, there are

0:37:40.120 --> 0:37:43.160
<v Speaker 2>obligations there. You know that is again, we're a really

0:37:43.160 --> 0:37:45.400
<v Speaker 2>good attorney in the space in the room is going

0:37:45.440 --> 0:37:48.839
<v Speaker 2>to help you through that process. Your cyber insure if

0:37:48.840 --> 0:37:52.440
<v Speaker 2>you've got cyber insurance in place will be dramatically and

0:37:52.520 --> 0:37:55.160
<v Speaker 2>drastically helpful in terms of getting boots on the ground

0:37:56.120 --> 0:37:58.560
<v Speaker 2>to help you get you know, systems back to help

0:37:58.560 --> 0:38:02.000
<v Speaker 2>you understand how how you know what is the breadth

0:38:02.040 --> 0:38:06.839
<v Speaker 2>and depth of this cybersecurity incident to your environment? You know,

0:38:06.920 --> 0:38:09.960
<v Speaker 2>if it's if it's an internal you know, insider threat,

0:38:10.000 --> 0:38:12.680
<v Speaker 2>it's a you know, totally different game. You're getting departments

0:38:12.680 --> 0:38:15.560
<v Speaker 2>like HR involved. But leading up to this, you know,

0:38:15.760 --> 0:38:18.480
<v Speaker 2>the cyber incident, the point of cyber incident is not

0:38:18.600 --> 0:38:20.920
<v Speaker 2>the time where you want to be figuring this out.

0:38:21.719 --> 0:38:24.279
<v Speaker 2>You want to do a lot of this planning for

0:38:24.360 --> 0:38:28.160
<v Speaker 2>the own no moment before it actually happens. So we

0:38:28.200 --> 0:38:32.000
<v Speaker 2>always make the recommendations that on a regular basis, you

0:38:32.040 --> 0:38:35.719
<v Speaker 2>should be simulating, right, even if it's a table top event,

0:38:35.760 --> 0:38:39.200
<v Speaker 2>you should be simulating these discussions. Sit folks in a

0:38:39.280 --> 0:38:43.160
<v Speaker 2>room and that includes your CEO, that includes your investor relations,

0:38:43.200 --> 0:38:46.360
<v Speaker 2>that includes your your legal team, that includes you know it,

0:38:46.960 --> 0:38:50.360
<v Speaker 2>if your insurer is proactive, your you know, your cyber

0:38:50.560 --> 0:38:54.680
<v Speaker 2>and ensure and talk through, Hey, here's a scenario, how

0:38:54.680 --> 0:38:57.920
<v Speaker 2>are we going to respond to this? How are we

0:38:57.960 --> 0:39:00.000
<v Speaker 2>going to get to the other side of this moment,

0:39:00.080 --> 0:39:02.040
<v Speaker 2>because there is light at the end of the tunnel.

0:39:02.200 --> 0:39:04.600
<v Speaker 2>At the end of the tunnel, a cyber event is

0:39:04.640 --> 0:39:09.279
<v Speaker 2>not the end of your company. Right, So you know,

0:39:09.360 --> 0:39:12.239
<v Speaker 2>if you feel that there's capabilities in house to lead

0:39:12.280 --> 0:39:15.160
<v Speaker 2>that in house, do it partner with a third party. Right,

0:39:15.200 --> 0:39:17.759
<v Speaker 2>and shameless plug for our team here, Right, We do

0:39:17.880 --> 0:39:20.840
<v Speaker 2>these regularly. Right, We're sitting down with with with the board,

0:39:20.840 --> 0:39:24.040
<v Speaker 2>We're sitting down with the incident response teams to say,

0:39:24.080 --> 0:39:26.080
<v Speaker 2>how are you actually going to respond to this? What

0:39:26.120 --> 0:39:28.000
<v Speaker 2>does this mean to be able to go out to

0:39:28.040 --> 0:39:31.040
<v Speaker 2>the market and say, yes, we brand ABC that is

0:39:31.080 --> 0:39:34.200
<v Speaker 2>a publicly traded company in this many states. Here's what

0:39:34.320 --> 0:39:36.640
<v Speaker 2>happened to us, Here's what we're doing to respond to it.

0:39:36.719 --> 0:39:39.880
<v Speaker 2>Here's how to you as a consumer. This may impact

0:39:40.000 --> 0:39:42.719
<v Speaker 2>you if there is a data breach. Here's how your

0:39:42.719 --> 0:39:46.239
<v Speaker 2>information what types into and how your information might have

0:39:46.360 --> 0:39:51.600
<v Speaker 2>been exposed. But look at your partner landscape to help

0:39:51.680 --> 0:39:56.319
<v Speaker 2>support that that response. It should not happen in a silo,

0:39:56.920 --> 0:39:59.560
<v Speaker 2>and it certainly should not be you know, that cyber

0:39:59.600 --> 0:40:02.560
<v Speaker 2>event or you know, the privacy beach event should not

0:40:02.640 --> 0:40:04.480
<v Speaker 2>be the point where you're figuring it out.

0:40:04.880 --> 0:40:05.960
<v Speaker 1>Yeah, by then it's too late.

0:40:06.040 --> 0:40:06.239
<v Speaker 3>Right.

0:40:06.800 --> 0:40:13.440
<v Speaker 1>Oh yeah, all right, So how is cybersecurity impacting loyalty programs?

0:40:13.680 --> 0:40:16.120
<v Speaker 1>And do you think privacy and data concerns are going

0:40:16.200 --> 0:40:18.240
<v Speaker 1>to slow down the shift to one to one marketing?

0:40:19.560 --> 0:40:25.719
<v Speaker 2>Yes? So here's here's kind of the you know what

0:40:25.760 --> 0:40:29.000
<v Speaker 2>we talk about when it comes to loyalty programs. Loyalty

0:40:29.040 --> 0:40:32.640
<v Speaker 2>programs are great. I and myself will say that I

0:40:32.680 --> 0:40:35.200
<v Speaker 2>love my loyalty programs. I love getting to know that

0:40:35.239 --> 0:40:37.480
<v Speaker 2>my tenth pizza is free. And I'm not going to

0:40:37.560 --> 0:40:40.080
<v Speaker 2>name the brand, but we all know, right, I love

0:40:40.120 --> 0:40:42.920
<v Speaker 2>my tenth pizzas free. Right. But the reality is, to

0:40:43.000 --> 0:40:45.799
<v Speaker 2>sign up for a loyalty program, you're giving them a

0:40:45.840 --> 0:40:49.000
<v Speaker 2>lot of information about yourself. So let's first talk about

0:40:49.040 --> 0:40:53.279
<v Speaker 2>from a consumer perspective, right way, whether or not the

0:40:53.360 --> 0:40:56.960
<v Speaker 2>loyalty programs really worth it. Right if this is an

0:40:57.000 --> 0:41:01.160
<v Speaker 2>ongoing brand that you have an ongoing relationship with, Yeah,

0:41:01.200 --> 0:41:03.040
<v Speaker 2>maybe you want to say, okay, look if I you know,

0:41:03.040 --> 0:41:05.960
<v Speaker 2>if I give my information, I get my tenth pizza free,

0:41:06.000 --> 0:41:08.640
<v Speaker 2>I get twenty percent off my my my purchase of

0:41:08.719 --> 0:41:12.200
<v Speaker 2>you know, linens and whatever. All right, totally at it.

0:41:13.440 --> 0:41:15.160
<v Speaker 2>Let's say this is a brand that it's a one

0:41:15.200 --> 0:41:17.320
<v Speaker 2>and done. You're on the road, you're grabbing a soda,

0:41:17.320 --> 0:41:20.000
<v Speaker 2>you're grabbing a coffee somewhere to rest stop. Right, what

0:41:20.040 --> 0:41:22.680
<v Speaker 2>does it look like for you to actually give that information? Right?

0:41:22.800 --> 0:41:26.279
<v Speaker 2>Is there an ROI for you for doing that? So

0:41:26.360 --> 0:41:30.560
<v Speaker 2>I don't wanna I don't want to ignore the fact

0:41:30.600 --> 0:41:32.960
<v Speaker 2>that a consumer plays a really big role in this

0:41:33.120 --> 0:41:36.719
<v Speaker 2>relationship right on the marketing front. Now, let's go to

0:41:36.960 --> 0:41:40.600
<v Speaker 2>the company side of this. Right, So companies are looking

0:41:40.640 --> 0:41:42.879
<v Speaker 2>to say, Okay, we want to understand better who our

0:41:42.880 --> 0:41:45.160
<v Speaker 2>consumer is. We want to figure out you know, we're

0:41:45.280 --> 0:41:48.560
<v Speaker 2>we're piloting products, let's see who buys my membership perspective,

0:41:49.000 --> 0:41:53.240
<v Speaker 2>We're using this to maintain customer loyalty, right, to increase

0:41:53.280 --> 0:41:56.520
<v Speaker 2>customer lifetime value for us. You know, gone other days

0:41:56.520 --> 0:41:59.320
<v Speaker 2>where we can just put cookies and pixels on our websites,

0:41:59.440 --> 0:42:03.680
<v Speaker 2>right and have at it. Because again, thanks thanks right

0:42:03.719 --> 0:42:08.919
<v Speaker 2>to the powers that be for disallowing us to do that. Right.

0:42:09.600 --> 0:42:12.840
<v Speaker 2>But you're collecting as a company, massive amounts of information

0:42:12.880 --> 0:42:15.680
<v Speaker 2>about people that they may or may not understand the

0:42:15.719 --> 0:42:19.160
<v Speaker 2>impact of. Right, So how are you going to collect

0:42:19.160 --> 0:42:21.400
<v Speaker 2>information about your user base? How are you going to

0:42:21.440 --> 0:42:24.880
<v Speaker 2>aggregate that information? How are you then going and buying

0:42:25.000 --> 0:42:29.279
<v Speaker 2>let's say consumer sentiment information to layer on top of this, right?

0:42:29.360 --> 0:42:32.520
<v Speaker 2>How are you potentially using deal location data as an

0:42:32.520 --> 0:42:35.399
<v Speaker 2>additional layer here? Right? And what does that mean now

0:42:35.440 --> 0:42:39.080
<v Speaker 2>to that massive data set and aggregate instead of just hey,

0:42:39.200 --> 0:42:41.919
<v Speaker 2>you know Debra Nica who lives in xity and meets

0:42:41.960 --> 0:42:45.480
<v Speaker 2>the demographic measurement, right now you're like, hey, Debra is

0:42:45.480 --> 0:42:48.640
<v Speaker 2>more likely to buy you know, shoes A versus shoes B,

0:42:48.960 --> 0:42:50.799
<v Speaker 2>and she's going to she's more likely to go to

0:42:50.880 --> 0:42:53.760
<v Speaker 2>store one versus store two. Right, So, now that data

0:42:53.760 --> 0:42:56.400
<v Speaker 2>set has become a lot larger and a lot more

0:42:56.520 --> 0:43:01.120
<v Speaker 2>risky for your company if a cyber event topic. Right, So,

0:43:01.800 --> 0:43:04.800
<v Speaker 2>I think a lot of what the what the loyalty

0:43:04.840 --> 0:43:07.799
<v Speaker 2>program you know, is showing us is yes you can

0:43:07.840 --> 0:43:09.919
<v Speaker 2>do it, Yes you can do it in a smart way.

0:43:09.960 --> 0:43:13.279
<v Speaker 2>But you've got to be really really measured of what

0:43:13.400 --> 0:43:16.799
<v Speaker 2>is it that you're trying to push out there to

0:43:16.960 --> 0:43:20.040
<v Speaker 2>your customer and how much risk and you know, are

0:43:20.040 --> 0:43:22.479
<v Speaker 2>you taking on and is that ROI is still going

0:43:22.520 --> 0:43:25.400
<v Speaker 2>to be worth it at the end? I still am

0:43:25.440 --> 0:43:27.200
<v Speaker 2>I'm going to age myself for a second, But I

0:43:27.200 --> 0:43:29.440
<v Speaker 2>remember the really really early days of like the shop

0:43:29.480 --> 0:43:32.319
<v Speaker 2>right card and key card beef. Anybody they'll put on

0:43:33.160 --> 0:43:35.440
<v Speaker 2>the little key card right, and it was like, well,

0:43:35.440 --> 0:43:36.839
<v Speaker 2>like you want to the point you have to like

0:43:36.880 --> 0:43:41.160
<v Speaker 2>go into the store right to swipe your card, and

0:43:41.239 --> 0:43:45.720
<v Speaker 2>that is not the shopping experience reality. Right, I'm biased.

0:43:45.719 --> 0:43:47.799
<v Speaker 2>I'm in New York, right, and I'm not. There's there's

0:43:47.840 --> 0:43:50.479
<v Speaker 2>no shop right where I live. I missed my little

0:43:50.480 --> 0:43:52.920
<v Speaker 2>membership card, right. But now, what does it look like

0:43:52.960 --> 0:43:55.839
<v Speaker 2>for me to have a loyalty program for a supermarket

0:43:55.880 --> 0:43:59.000
<v Speaker 2>that I am going to right, or an online grocery

0:43:59.080 --> 0:44:01.879
<v Speaker 2>service that is kind of my way? So I think

0:44:01.880 --> 0:44:04.319
<v Speaker 2>that there's a great from business perspective, there's a great

0:44:04.440 --> 0:44:08.880
<v Speaker 2>utility for the loyalty program. It's also going to impact

0:44:08.960 --> 0:44:14.959
<v Speaker 2>the breadth of your security, right. So so we look

0:44:15.000 --> 0:44:17.720
<v Speaker 2>at this from the lens of you as a company,

0:44:18.680 --> 0:44:21.600
<v Speaker 2>have certain information assets that you're going to use to

0:44:21.680 --> 0:44:23.960
<v Speaker 2>drive value for your company. You're gonna support revenue, You're

0:44:23.960 --> 0:44:26.480
<v Speaker 2>gonna put the loyalty program out there the own no

0:44:26.560 --> 0:44:31.080
<v Speaker 2>moment happens or the own no moment is about to happen. Right,

0:44:31.239 --> 0:44:39.040
<v Speaker 2>you have one hundred million pieces of data in your ecosystem, right,

0:44:39.800 --> 0:44:42.800
<v Speaker 2>every every one of those, every piece of that of information,

0:44:42.920 --> 0:44:46.319
<v Speaker 2>there is an exposure point for you. So let's say

0:44:46.320 --> 0:44:50.480
<v Speaker 2>the own moment happens. We have fifty states in our

0:44:50.719 --> 0:44:53.319
<v Speaker 2>in our country, every single state has its own data

0:44:53.320 --> 0:44:57.560
<v Speaker 2>breach law, right, none of which are the state you're crazy, right,

0:44:57.600 --> 0:44:59.920
<v Speaker 2>we have great precedent here for why privacy laws are

0:45:00.080 --> 0:45:01.759
<v Speaker 2>day by state, right, because we couldn't get it right

0:45:01.760 --> 0:45:03.319
<v Speaker 2>with data breach, so why should we get it right

0:45:03.360 --> 0:45:10.359
<v Speaker 2>with privacy right. So there are thresholds of in each state,

0:45:10.360 --> 0:45:13.000
<v Speaker 2>because a threshold that says, you know, all it takes

0:45:13.080 --> 0:45:16.279
<v Speaker 2>is one person's record to be breached and that is

0:45:16.320 --> 0:45:19.320
<v Speaker 2>going to trigger you to have to inform your attorney

0:45:19.320 --> 0:45:21.360
<v Speaker 2>general's office, and it's going to trigger some sort of

0:45:21.400 --> 0:45:25.640
<v Speaker 2>requirement for you to respond to this bridge. Other states

0:45:25.640 --> 0:45:27.359
<v Speaker 2>are like, nope, it's got to be over you know,

0:45:27.800 --> 0:45:31.040
<v Speaker 2>five ten thousand whatever it is records for it to

0:45:31.080 --> 0:45:34.400
<v Speaker 2>actually trigger a response for you to need to do something. Now,

0:45:34.640 --> 0:45:37.840
<v Speaker 2>let's say you have a loyalty program and you've got

0:45:38.480 --> 0:45:41.160
<v Speaker 2>you know, you've got this hundred million data points, right,

0:45:41.160 --> 0:45:43.440
<v Speaker 2>and you've got all these records about people. What does

0:45:43.480 --> 0:45:45.400
<v Speaker 2>it mean in that Oh no, woman, how much of

0:45:45.440 --> 0:45:48.640
<v Speaker 2>that information is actually a value additive information that you

0:45:48.719 --> 0:45:52.719
<v Speaker 2>are utilizing to support business? And how much of that

0:45:52.840 --> 0:45:55.920
<v Speaker 2>is information that you were collecting because you could, because

0:45:55.960 --> 0:45:59.239
<v Speaker 2>you could take on that information? And what does that

0:45:59.360 --> 0:46:04.879
<v Speaker 2>mean in protecting it? Right? Are there appropriate controls around it?

0:46:04.920 --> 0:46:07.400
<v Speaker 2>Is there a locks on the treasure box of this

0:46:07.480 --> 0:46:11.520
<v Speaker 2>treasure trove of information? Right? Or it's information that ultimately

0:46:11.560 --> 0:46:15.200
<v Speaker 2>exposed you to requirements and to cost of responding to

0:46:15.239 --> 0:46:18.880
<v Speaker 2>a breach and you know, cost of responding to the

0:46:19.000 --> 0:46:23.720
<v Speaker 2>impact of you know, brand erosion in that own a moment.

0:46:24.760 --> 0:46:27.680
<v Speaker 1>That's great, thanks and you have time for one more.

0:46:28.080 --> 0:46:29.280
<v Speaker 2>I have time for one more?

0:46:29.400 --> 0:46:33.880
<v Speaker 1>All right, good stuff. So last question, are ESG investors

0:46:33.920 --> 0:46:39.000
<v Speaker 1>placing a focus on cybersecurity? Are they focusing enough on cybersecurity?

0:46:39.000 --> 0:46:42.000
<v Speaker 1>I'd imagine this is probably a big part of the

0:46:42.040 --> 0:46:43.640
<v Speaker 1>governance piece of ESG.

0:46:43.880 --> 0:46:46.560
<v Speaker 2>Oh yeah, So we're seeing a lot a lot of

0:46:46.600 --> 0:46:51.320
<v Speaker 2>conversations happening from an ESG lens on this. So cybersecurity

0:46:51.360 --> 0:46:53.799
<v Speaker 2>is certainly from a governance lens, and then privacy from

0:46:54.560 --> 0:46:59.400
<v Speaker 2>a social lens. Right. So I'll say that that for

0:46:59.480 --> 0:47:02.480
<v Speaker 2>the most part art right, unless a fund is purely

0:47:02.560 --> 0:47:07.000
<v Speaker 2>an es G play. Right. There are still i would say,

0:47:07.000 --> 0:47:10.319
<v Speaker 2>conversations that are emerging in this space, right, But there's

0:47:10.320 --> 0:47:13.799
<v Speaker 2>a lens that says we have to report out, we

0:47:13.840 --> 0:47:17.279
<v Speaker 2>are required to report at out on our ESG activities,

0:47:17.360 --> 0:47:21.319
<v Speaker 2>and we're going to use cybersecurity or privacy as a

0:47:21.560 --> 0:47:27.839
<v Speaker 2>means to quantify ESG for us. So what we see

0:47:27.880 --> 0:47:29.960
<v Speaker 2>a lot of the time is there's this focus on

0:47:30.200 --> 0:47:34.040
<v Speaker 2>what does cybersecurity mean and how can cybersecurity hygiene be

0:47:34.400 --> 0:47:38.920
<v Speaker 2>used to inform that governance metric? And from a privacy perspective,

0:47:39.400 --> 0:47:42.239
<v Speaker 2>how are companies you know, how are are let's say

0:47:42.280 --> 0:47:44.560
<v Speaker 2>called up a port code right in this example? How

0:47:44.600 --> 0:47:51.279
<v Speaker 2>is a portfolio company maintaining the privacy standards of you know,

0:47:51.440 --> 0:47:53.880
<v Speaker 2>of their their consumer base, of their of their data

0:47:54.840 --> 0:47:59.640
<v Speaker 2>in order to really understand this social social contract aspect

0:48:01.280 --> 0:48:03.080
<v Speaker 2>with their customers. So I think that there's a there's

0:48:03.280 --> 0:48:07.520
<v Speaker 2>a really I this is personal opinion, right, I think

0:48:07.520 --> 0:48:09.360
<v Speaker 2>that that we're going to see an increase in a

0:48:09.560 --> 0:48:11.919
<v Speaker 2>in a lot of these types of conversations. I think

0:48:11.920 --> 0:48:15.880
<v Speaker 2>that as we see more perforation of you know, e

0:48:16.080 --> 0:48:18.799
<v Speaker 2>s G based funds, we're going to see a lot

0:48:18.960 --> 0:48:24.680
<v Speaker 2>more traction in the conversation of you know, the seat

0:48:24.560 --> 0:48:27.360
<v Speaker 2>at the table that that cyber and privacy you know

0:48:28.280 --> 0:48:31.680
<v Speaker 2>have in that value edit creation.

0:48:32.760 --> 0:48:37.480
<v Speaker 1>Very cool. Uh, that was awesome. I learned a lot.

0:48:37.760 --> 0:48:40.400
<v Speaker 1>Is there is there a best way you know, in

0:48:40.560 --> 0:48:42.560
<v Speaker 1>an email you'd like to share something like that, best

0:48:42.560 --> 0:48:44.719
<v Speaker 1>way for our listeners to get in touch with you

0:48:44.760 --> 0:48:46.680
<v Speaker 1>if if they have any questions.

0:48:47.400 --> 0:48:50.680
<v Speaker 2>Yeah, absolutely so. Always happy to chat and geek out

0:48:50.760 --> 0:48:56.399
<v Speaker 2>about this, Debra cofres dot com. Happy to to chat

0:48:56.440 --> 0:48:59.239
<v Speaker 2>with you. Uh, I am going to say, feel free

0:48:59.280 --> 0:49:02.200
<v Speaker 2>to Google because Google is still very much one of

0:49:02.239 --> 0:49:06.560
<v Speaker 2>our best friends. Cohen Resnick Cybersecurity, tech risk and Privacy team,

0:49:06.640 --> 0:49:10.200
<v Speaker 2>and we're always happy to have a chat, have a thought,

0:49:10.840 --> 0:49:14.240
<v Speaker 2>you know, a moment of thinking and sharing and looking forward.

0:49:14.280 --> 0:49:17.480
<v Speaker 1>Awesome. Well, thanks for doing us, Thanks to our listeners

0:49:17.719 --> 0:49:30.600
<v Speaker 1>for listening it, and have a good day everybody,