สำเนาบทสนทนา 🔗
WEBVTT
00:00:03.759 --> 00:00:08.000
You are now listening to the Secure AF Podcast.
00:00:11.679 --> 00:00:13.679
Welcome to the Secure AF Podcast.
00:00:13.759 --> 00:00:16.800
I'm Jonathan Kemmet, and we've got a special guest today.
00:00:16.960 --> 00:00:18.960
We're going to be talking about AI.
00:00:19.120 --> 00:00:20.640
We're going to talk about data security.
00:00:21.120 --> 00:00:22.160
We've got a lot of topics.
00:00:22.239 --> 00:00:23.120
So I'm really excited.
00:00:23.199 --> 00:00:24.640
So thank you for joining us.
00:00:25.440 --> 00:00:27.839
Tim, please introduce yourself.
00:00:28.399 --> 00:00:28.960
Hey, yeah.
00:00:29.039 --> 00:00:31.600
Thanks, Jonathan, for having me on the podcast.
00:00:31.760 --> 00:00:34.399
I knew by the name I was this was one I wanted to be on.
00:00:34.560 --> 00:00:36.960
So good job on the marketing of that part.
00:00:38.479 --> 00:00:43.600
So yeah, I Tim Freestone, Chief Strategy Officer at a company called Kiteworks.
00:00:43.840 --> 00:00:47.679
I've been with this organization for about five years.
00:00:48.159 --> 00:00:53.200
For those that don't know Kiteworks, uh, we are a data security company.
00:00:53.280 --> 00:01:00.880
Uh, we focus on helping customers control data that gets exchanged between people and machines.
00:01:01.039 --> 00:01:14.079
Uh and um machines meant something totally different three years ago when we would talk about um managed file transfer and secure file transfer protocols, machine to machine, computer to computer.
00:01:14.239 --> 00:01:15.680
That was really where our narrative was.
00:01:15.840 --> 00:01:32.640
And obviously um that machine has taken on a different form uh and certainly driven um a lot of interest in in what Kiteworks does in the past couple of years uh due to our uh value proposition at both the machine and the the data layer.
00:01:32.799 --> 00:01:37.439
So excited to be on the program and I love waxing philosophic about this stuff.
00:01:37.599 --> 00:01:38.959
So fire away.
00:01:39.599 --> 00:01:40.719
Well, I love that.
00:01:40.799 --> 00:01:43.599
And you know, I'm a I'm a big data security person.
00:01:43.760 --> 00:01:52.319
Um I do a lot of privacy stuff, I do a lot of data uh security with my clients, and and so it's kind of close to my heart, you know.
00:01:52.400 --> 00:02:02.400
Uh a lot of times what I do is I start with data security and kind of work out from there on the cybersecurity side because I want to protect the data for protect people that protect the data as best I can.
00:02:02.640 --> 00:02:05.040
So um, well, let's go let's get started.
00:02:05.200 --> 00:02:27.039
I mean, you know, one of the biggest fears that that I have as a CISO, um, and then I I I know a lot of other people are having the same thing, is the the the extreme speed in which AI and or some of the these new technologies that we have is getting access to our data, um, needing data, training on data.
00:02:27.120 --> 00:02:28.800
I mean, there's a lot of pieces there.
00:02:28.960 --> 00:02:32.479
So what's you know, from a broad point of view, what's what's your thoughts?
00:02:32.639 --> 00:02:35.680
You know, you take it in the last two years, kind of what you said before.
00:02:35.919 --> 00:02:37.199
What what has changed?
00:02:37.280 --> 00:02:44.159
You know, what have you seen that has changed so drastically that it's really bringing that data security back to the forefront?
00:02:44.479 --> 00:02:52.560
Yeah, I I mean look, the it's the evolution of what the word machine means, I think, is is the big narrative here, the big story.
00:02:52.800 --> 00:02:58.240
Uh previously, machines had no intent of their own, or really any intent.
00:02:58.479 --> 00:03:03.360
They just had uh process function as programmed, right?
00:03:03.759 --> 00:03:12.879
Uh and what has happened is this concept of intent, which was solely owned by uh human beings, um, is now owned by machines.
00:03:13.039 --> 00:03:27.840
And so when something has intent, sort of foundational to the word intent is making decisions on your own and coming up with what you want to do next and creating that sort of end game uh process of getting there.
00:03:28.000 --> 00:03:29.439
Like that that's intent.
00:03:29.680 --> 00:03:54.879
And that for me, that's the biggest thing that has changed is that machines now have intent and they can uh determine their own intent, they can change intent, and that leads to a very non-deterministic way to control data, control cybersecurity, and understand what needs to happen next.
00:03:54.960 --> 00:04:01.919
It's since it's non-deterministic, it's you you can't quite track what's gonna happen and where it's gonna happen.
00:04:02.159 --> 00:04:09.280
And so, you know, the we we talked a lot for years and years about this concept of assume breach.
00:04:09.520 --> 00:04:14.000
Um, and what I like to do is drop the B now and just say assume reach.
00:04:14.400 --> 00:04:24.879
You you just have to assume that agents can reach anything and everything that you have connected to the internet or in you know, internal and external.
00:04:25.199 --> 00:04:34.720
And and you know, intent plus uh the fact that they can get to anything and this assume reach mentality is all new within the past couple years.
00:04:35.040 --> 00:04:35.680
Yeah.
00:04:36.240 --> 00:04:38.000
Well, and and I agree with you.
00:04:38.079 --> 00:04:46.959
I mean, I think our our mindsets have to change, you know, from a cybersecurity perspective or by an industry perspective because we have to think like that.
00:04:47.199 --> 00:04:57.120
Um, you know, I uh in my I was doing a class where we were doing a an AI incident, and you know, it was a tabletop.
00:04:57.360 --> 00:04:58.000
I mean, it was fun.
00:04:58.079 --> 00:05:21.199
You know, I had you know 40 or so people in the room, and we were working through there and working through the the scenario, and one of the problems was about half of the
Load full transcript
room was was thinking about the data side of what happened, and the other group was or the other half of the room was really thinking about the functional side of what happened.
00:05:21.839 --> 00:05:39.759
And I think that that's really that that's that's a change that you know, starting back when I started into privacy back years ago, that's what I was trying to get people to understand is we need to think about the data side first, then start tracking where where things were happening based off of that.
00:05:39.920 --> 00:05:42.160
And it's still really hard to get people to think about that.
00:05:42.399 --> 00:05:45.439
So to think about yeah, and why do you think that is?
00:05:45.600 --> 00:05:52.319
You know, is it because they don't want to, or because they don't, it doesn't occur to them that that's that's where we need to start.
00:05:52.639 --> 00:05:55.120
No, I think it's much simpler than that.
00:05:55.279 --> 00:06:09.360
The first of all, I agree with everything you say, and the fact that you open the podcast with you think about the data for like that's the point of cybersecurity, with the exception of sort of like sabotage basically.
00:06:09.759 --> 00:06:10.160
Yeah, yeah.
00:06:10.879 --> 00:06:12.560
Right, the point is the data.
00:06:12.800 --> 00:06:24.480
Yeah, um, and so to answer your question, I think it's much more basic than that, which is until recently solving the data layer problem was too hard.
00:06:25.279 --> 00:06:40.319
And the volume of what needs to be covered and how it needs to be covered was too hard, which is another way to say like most people in all things look for the easy button.
00:06:40.639 --> 00:06:45.120
Um and the easy button is okay, well, I have one network.
00:06:45.759 --> 00:06:46.800
You know, that's the start.
00:06:46.879 --> 00:06:50.000
Like, here's my network, I'm gonna easy button that with a firewall.
00:06:50.160 --> 00:06:52.240
And it's like, okay, now I have applications, okay.
00:06:52.319 --> 00:06:55.199
I'm gonna easy button that with a web application firewall.
00:06:55.360 --> 00:06:58.399
Yeah, um, now I have a cloud and I have SaaS.
00:06:58.560 --> 00:07:00.720
Okay, CASB, let's go.
00:07:00.879 --> 00:07:12.319
You know, it just it's sort of like big decisions, easy buttons um at the infrastructure and parameter layer because because it's so hard to do with the data layer.
00:07:12.480 --> 00:07:20.879
Now uh it was okay because of the speed at which you know humans could function, basically.
00:07:21.120 --> 00:07:22.399
It's not okay anymore.
00:07:22.639 --> 00:07:37.199
And you know, to some degree, I'm grateful of the the fact that AI has pressed on this and made people look at and and honestly tried to develop easy buttons for the data because there's still people don't want to work, it's too hard.
00:07:37.519 --> 00:07:56.240
So what what's great about AI is they you know it pressed focus on the point, which is data, and also along with that is that AI is enabling companies to build tooling and technology and uh value for customers in the cybersecurity space that can actually address it.
00:07:56.399 --> 00:08:03.040
So we have a huge vendor ecosystem exploding right now that wasn't possible three years ago because of AI.
00:08:03.199 --> 00:08:11.199
So it's it's one of those things where it's sort of like the cause and the solution, but it's great that everybody's starting to 50% of the room is great.
00:08:11.360 --> 00:08:13.360
Three years ago would have been five percent of the room.
00:08:13.519 --> 00:08:13.839
Oh, yeah.
00:08:14.480 --> 00:08:15.839
Yeah, no, I I agree with that.
00:08:16.000 --> 00:08:22.079
In fact, I was doing, you know, of course, we just came out of Cybersecurity Awareness Month, and I do a lot of presentations during that month.
00:08:22.160 --> 00:08:27.120
I mean, I think I did 30 or so um this month or last month.
00:08:27.360 --> 00:08:36.960
Anyway, so I was I was doing a presentation at a a large firm here in town, and it was their yearly cybersecurity awareness training type thing.
00:08:37.200 --> 00:08:42.399
Um, and so I went in and I was doing data security, um, doing a presentation on it.
00:08:42.480 --> 00:08:55.519
And and one of the things that I do in my data security presentations is I asked the room, do you think we have right now in our organizations all the controls we need to do to protect data?
00:08:56.320 --> 00:08:58.480
And of course, there was a room full of IT people.
00:08:58.639 --> 00:09:01.279
They're like, no, no, no, we don't have those controls, we're not doing it.
00:09:01.360 --> 00:09:02.960
And it's like, well, I disagree with you.
00:09:03.039 --> 00:09:10.000
And I pull out a stack of hundred dollar bills, ten thousand dollars worth of hundred dollar bills, and I lay it on the table.
00:09:10.159 --> 00:09:13.200
It's like, do we do we protect this?
00:09:13.360 --> 00:09:15.279
I mean, do we how how do we protect money?
00:09:15.360 --> 00:09:18.320
Do you let money sit out on someone's desk overnight?
00:09:18.480 --> 00:09:21.759
Do you let them take it home and work on it or count it at home?
00:09:21.919 --> 00:09:24.480
Do you let them put it in their personal bank account?
00:09:24.720 --> 00:09:26.399
And they're like, no, of course not.
00:09:26.480 --> 00:09:36.159
It's like, well, everything we do to protect money, we could use those same exact controls to protect data, data records or data fields.
00:09:36.559 --> 00:09:38.399
And the light bulb went off in their head.
00:09:38.480 --> 00:09:43.279
It's like, oh, you mean I need to treat data like it was money?
00:09:43.440 --> 00:09:44.159
It's like, yes.
00:09:44.559 --> 00:09:47.600
And there was just happened to be a controller in the room.
00:09:47.840 --> 00:09:52.240
And uh, so I asked them, I was like, Do you monitor where money goes?
00:09:52.639 --> 00:09:55.200
You know, what account it goes in, and and who has access?
00:09:55.279 --> 00:09:57.759
And they're like, absolutely, yeah.
00:09:58.000 --> 00:10:01.759
And it's like, well, do you tr only allow certain people to have access to it?
00:10:01.919 --> 00:10:02.720
Well, well, of course.
00:10:02.799 --> 00:10:11.840
That's like, okay, we have all the controls, and and of course they thought it was funny, and of course, everyone loves a stack of money, they think that's funny.
00:10:12.080 --> 00:10:17.440
Um, but it's one of those things that we could protect it better.
00:10:17.759 --> 00:10:20.320
And like you said earlier, it's just hard.
00:10:20.480 --> 00:10:27.440
It's it's not something they I think a lot of people like that easy button, like you said, but they like, oh, I'm gonna protect the network.
00:10:27.679 --> 00:10:40.720
Well, the network is really hard because I need to protect this piece of the network like this for PCI, and this piece of the network for this because of data and HIPAA and GOPA and FERPA and whatever.
00:10:41.039 --> 00:10:45.120
And that starts getting too granular, and it it's it's really difficult.
00:10:45.279 --> 00:10:53.360
I I like to years ago, I like saying that the CISO was the original data protection officer, chief information security officer.
00:10:53.519 --> 00:10:57.919
And I have a lot of CISOs that they're like, no, we don't do data, that's legal.
00:10:58.159 --> 00:10:59.200
I know it's crazy.
00:10:59.360 --> 00:11:01.840
Yeah, I just it's nuts, yeah.
00:11:02.080 --> 00:11:04.559
It it is, it's it it it boggles me.
00:11:04.720 --> 00:11:06.240
So it's changing though.
00:11:06.480 --> 00:11:17.600
Like I said, I I I see it, I don't do 30 a month, but I do enough speaking where the conversations are very, very different than they were uh even a couple years ago, to be honest.
00:11:17.759 --> 00:11:29.679
And um the other thing that I'm seeing is the the data governance team and professionals and the CISO and the cybersecurity making amends coming together.
00:11:30.480 --> 00:11:37.200
You know, well, and I think it's because the a lot of this you have more leadership level involved.
00:11:37.360 --> 00:11:39.519
I mean, they're they're thinking about this.
00:11:39.600 --> 00:11:46.320
I mean, you go to any cybersecurity insurance with an IR, and their first thing they're gonna ask you is like, how many records are we dealing with?
00:11:46.480 --> 00:11:49.120
You know, how many records were on that machine that was ransomware?
00:11:49.360 --> 00:11:51.519
So that's one of their first questions.
00:11:51.679 --> 00:11:56.960
So yeah, I think leadership is is is learning that hey, this is really important.
00:11:57.120 --> 00:12:05.519
Of course, we've been saying that in the privacy side for years, but they're starting to pick up on that because it's cost, it's it's money, it's you know, there's value to it.
00:12:05.840 --> 00:12:06.240
Yeah.
00:12:06.480 --> 00:12:13.039
And I, you know, I many years ago I worked for a company called NetApp, which probably everybody's heard of.
00:12:13.200 --> 00:12:23.919
Um and we uh we a lot of conversations at the time with data governance teams, and a lot of conversations around data lineage.
00:12:24.159 --> 00:12:25.919
Uh, but it was there.
00:12:26.080 --> 00:12:28.559
We not with the cybersecurity team.
00:12:28.639 --> 00:12:35.039
It was just sort of like here's where your data is, here's how you backup and recover your data, here's how you track the lineage of data.
00:12:35.279 --> 00:12:39.200
And now I'm having similar conversations in the site.
00:12:39.600 --> 00:12:42.159
Here's what data lineage is, here's why it's important.
00:12:42.399 --> 00:12:42.799
Right.
00:12:43.039 --> 00:12:51.600
And the data governance is, you know, you need audits and auditors, and with AI, there's gonna be more of that, and everybody's gonna want to know where your data is and where it lives and where it went.
00:12:51.679 --> 00:13:01.120
And um, so it's kind of cool seeing that stuff all blend together, which you know puts the question out there like, well, who's who's in charge then?
00:13:01.440 --> 00:13:04.000
Um, yeah, you know who's in charge?
00:13:04.080 --> 00:13:05.440
I maybe uh I'm interested.
00:13:05.519 --> 00:13:05.919
What do you think?
00:13:06.000 --> 00:13:14.879
Because I get the question a lot, and I always end up going to the safe answer, which is it's the first time the CEO can't be just an operator, they need to be an IT professional.
00:13:15.600 --> 00:13:32.240
Well, I I agree with that, and I think you know, that comes down a lot like my AI governance thing that I was doing, I was teaching that question of who is making decisions, who is the owner of this data, who's the owner of the AI, who is the stakeholder, that's a big issue.
00:13:32.399 --> 00:13:37.120
And it's not it's not something that we've ever been able to answer on other things.
00:13:37.279 --> 00:13:49.360
I mean, if you ask somebody in the organization who owns 365, everyone uses it, everyone uses the office tools or Teams or Word or or Gmail if you're on the Google Suite side, you know, whatever.
00:13:49.600 --> 00:13:50.799
But who owns it?
00:13:51.120 --> 00:13:56.240
And I think a lot of people default down well, IT owns it because they're the ones managing it.
00:13:56.480 --> 00:14:02.159
And I guess it's okay for some things, but there's a lot of things you can't say that on.
00:14:02.399 --> 00:14:04.159
So I think that's changing.
00:14:04.320 --> 00:14:13.840
I think people are realizing that the ownership, the the idea of ownership of a service, of the data, of a process is starting to become really, really important.
00:14:14.080 --> 00:14:16.799
And unfortunately, I think it's because of liability.
00:14:16.960 --> 00:14:22.799
I think it's who is making bad decisions, and therefore we have to fix it.
00:14:22.960 --> 00:14:27.279
Now, I hate it when we have to do that, when we have to go to the negative side of it.
00:14:27.360 --> 00:14:33.840
I would much
rather someone take ownership of it and you know, build it, you know, and grow it and do it safely.
00:14:34.080 --> 00:14:36.399
But you know, it's kind of the world we live in.
00:14:36.559 --> 00:14:41.679
Um, is you know who's going to take ownership of it really means who's going to be liable for it.
00:14:42.000 --> 00:14:42.399
Exactly.
00:14:42.559 --> 00:14:45.120
Who can you blame when something goes wrong?
00:14:45.279 --> 00:14:45.919
That's right.
00:14:47.200 --> 00:14:48.480
But but I agree with you.
00:14:48.559 --> 00:14:55.200
I think that you know, leadership is taking more and more of a role now because well, they kind of have to.
00:14:55.279 --> 00:14:56.960
I mean, they're the decision makers.
00:14:57.120 --> 00:15:31.759
Um, you know, I think it's you know, back a couple years ago, um, there was a uh well, it was 20 2016, 2017, but there was a a letter that came out from Sally Yates, uh, and it went to the DOJ, and it was a um it was a memo, and what it said was that the the DOJ in as it relates to investigations, that if there's harm involved in a in a corporation or uh a business, that they would look for who who was actually accountable for.
00:15:31.919 --> 00:15:35.840
So it's individual accountability for corporate wrongdoing was the name of the memo.
00:15:36.639 --> 00:15:53.440
Uh, but well, that hit the the the IT field pretty hard because now you had people who were in it, they were making decisions in IT that was not getting approved by leadership, therefore that individual accountability fell on their shoulders.
00:15:53.840 --> 00:15:56.960
Um, and you know, I remember presenting about this.
00:15:57.039 --> 00:15:59.600
I mean, I would I'd bring up the letter and I'd put it up on the screen.
00:15:59.679 --> 00:16:06.320
I was like, hey, you guys need to read this, and I'm not a lawyer, but I'm going to interpret it for me this way.
00:16:06.480 --> 00:16:08.559
You interpret it what how you need to.
00:16:08.799 --> 00:16:21.759
And uh, there's a lot of people that freaked out because you know, I mean, we all know those system administrators who, you know, they would say, I'm not deploying Windows patches every time I do it, breaks these servers, and I have to fix them.
00:16:21.840 --> 00:16:33.519
And and so they they get off on their their patches and their updates, and they're choosing to go against the manufacturer's recommended critical and high security updates.
00:16:33.759 --> 00:16:36.720
That's a lot of liability on your shoulders, sure.
00:16:36.799 --> 00:16:45.440
Yeah, and so now they're they're the the the lower level people lower level, the sysadmins are going, wait a minute, I don't want that liability.
00:16:45.679 --> 00:16:47.360
I want to involve leadership.
00:16:47.519 --> 00:16:55.279
So change management became a much bigger issue of going and getting approval from someone so that liability moves up the line.
00:16:55.440 --> 00:17:01.360
So I think that's what pushed a lot of that, or at least some of it, because there's real liability now.
00:17:01.519 --> 00:17:10.000
Um, and they thought they might be protected, but again, you make poor decisions and there's harm, then bad things happen.
00:17:10.319 --> 00:17:10.799
Yeah.
00:17:11.119 --> 00:17:19.519
And you know, to your point, I I wish it wasn't about liability um as the the driving force of answering the question who owns it.
00:17:19.839 --> 00:17:21.440
But also, what is it?
00:17:21.759 --> 00:17:24.480
You know, what what does owning it mean?
00:17:24.640 --> 00:17:33.519
So if you look at uh let's say you do a cloud enter enterprise cloud deployment, okay, that's the technical it.
00:17:33.920 --> 00:17:39.359
I suppose the enterprise cloud deployment deployment owned is owned by it.
00:17:40.160 --> 00:17:41.759
But there's a higher it.
00:17:42.319 --> 00:17:44.319
Well, what do people do with cloud?
00:17:44.640 --> 00:17:50.640
Who owns how how people use it and how safe they are and how effective two buggers.
00:17:50.799 --> 00:17:57.200
How effective they are, how productive they are, how are they managing what they do with cloud as it relates to tokenomics?
00:17:57.599 --> 00:17:58.559
How safe are they?
00:17:58.720 --> 00:18:01.519
So there's a whole it around people's use of AI.
00:18:01.680 --> 00:18:04.240
Well, IT's not gonna take responsibility for that.
00:18:04.880 --> 00:18:14.400
Then there's um you know, personal AI and shadow AI, and that's oh, you know, a whole nother so this it what is it?
00:18:14.720 --> 00:18:36.000
Uh and I think at the end of the day, it is a complete transformation of how we operate in society and at work, and you know, there isn't a higher being at that company, maybe the board, but they're not operating anything, they're just coming once a quarter and yelling at people.
00:18:36.319 --> 00:18:46.720
So the CEO, the CEO owns the transformation of how you operate in in business, and you gotta figure out your own life aside.
00:18:46.880 --> 00:18:48.000
That's a whole nother podcast.
00:18:48.240 --> 00:18:51.200
But yeah, yeah, that's why I keep coming back to that.
00:18:51.519 --> 00:19:18.400
Well, I agree, and I think I think the it does change depending on what you're talking about, because when I talk about ownership of an AI, um usually what I'm talking about is a particular AI that does a particular function for a particular department or a set of departments, and that person who is that stakeholder who is going to be the one out there telling people, hey, this is how we use it, this is what I use it for, this is why we use it.
00:19:18.559 --> 00:19:21.440
They they monitor it, they do access control, they do all these.
00:19:21.680 --> 00:19:26.079
Now, some of that may be IT, but they're the ones that approve it.
00:19:26.240 --> 00:19:31.920
You know, we go back to the kind of the stakeholder or the data steward from the data privacy side.
00:19:32.079 --> 00:19:45.920
You know, you might have
lots of people who use a particular set of data, let's say a HIPAA data uh or FERPA data or whatever, but the registrar is the owner of that data, they are the ones who approve the use of it and how people use it, where do they use it, and that final say.
00:19:46.160 --> 00:19:47.119
So I think you're right.
00:19:47.200 --> 00:19:54.000
I think it changes a little bit depending on the the topic um and why we're using the word it.
00:19:54.559 --> 00:20:02.079
But I I do believe that the level in which we talk about owning it is rising.
00:20:02.240 --> 00:20:18.160
It's you know, people aren't just doing hands off because I think they want it, they they need to have these services, and and that's one of the things I try not to do is you know, it's very easy to bash AI, you know, for lots of different reasons, but there's a lot of value in it, it's a good tool.
00:20:18.319 --> 00:20:27.039
Yeah, and if you use it correctly, you can get a huge amount of benefit from it, but it's that using correctly that's the problem.
00:20:27.200 --> 00:20:32.720
It's you know, organizations don't have policies and training because you got to have both.
00:20:32.960 --> 00:20:38.160
They don't have realistic ideas of how to use it, they're not helping people use it.
00:20:38.319 --> 00:20:41.519
I mean, we still have organizations, it's very weird.
00:20:41.759 --> 00:20:51.200
I I went to Security Congress here recently, and uh you you have people from all over the world coming in, and it's in the United States, it's very different.
00:20:51.440 --> 00:20:57.200
People working on the coasts um and how they use AI, and people who work in the middle of the country who use AI.
00:20:57.920 --> 00:21:04.400
And it's it's it's slow moving in, you know, it kind of goes from the coast in, and every technology is like that.
00:21:04.720 --> 00:21:09.279
But when we're talking about that, you know, how people are using area.
00:21:09.440 --> 00:21:26.480
There was this one company that they're not hiring qualified individuals for a particular job, they're hiring people in, you know, at a certain level, whatever it is, then they're giving them three agents and saying, okay, go figure it out.
00:21:26.880 --> 00:21:32.000
I don't necessarily agree with that, but I see why they're doing it.
00:21:32.319 --> 00:21:34.720
They're, I mean, I'll put I'll give you an example.
00:21:34.880 --> 00:21:48.240
They're not hiring security analysts, they're hiring three entry level people that have no security skills, giving them an agent and then turning them loose, saying, Go learn how to do the agent to go answer these questions.
00:21:48.960 --> 00:21:51.599
They're very forward thinking.
00:21:51.759 --> 00:21:55.920
And of course, I asked him, I was like, How many, how many people do you have on your security team?
00:21:56.000 --> 00:21:57.279
Oh, about 150.
00:21:57.440 --> 00:21:59.519
And I was like, Oh, well, all right.
00:22:00.240 --> 00:22:02.799
That's a little different scale than most organizations.
00:22:03.039 --> 00:22:03.279
Right.
00:22:03.359 --> 00:22:03.599
Yeah.
00:22:03.839 --> 00:22:05.920
Um, but again, it's very different.
00:22:06.079 --> 00:22:16.319
So, I mean, I think that that's the interesting thing is how are people using AI, whether it be uh agents or LLMs or public, you know, LLMs, you know, whatever we're doing.
00:22:16.640 --> 00:22:22.880
And that's actually a question I have for you is what are you seeing happening in the organizations right now?
00:22:23.200 --> 00:22:29.440
Because I mean, again, two years ago, we were talking about okay, how do we stop the use of AI in shadow AI?
00:22:29.680 --> 00:22:35.599
Now we're okay, how can we use it to our best advantage and how do we protect our data around it?
00:22:35.920 --> 00:22:36.319
Yeah.
00:22:36.559 --> 00:22:45.839
So, you know, two years ago, all of the boards, and maybe not that long ago, let's just say two for boards of directors, CEOs, all went, use AI.
00:22:46.319 --> 00:22:53.920
And the they pour in a bunch of money in it, co-pilot cloud deployments everywhere, some chat GPT.
00:22:54.480 --> 00:23:02.319
And everybody quickly realized that this maybe not so quickly, that this in and of itself is a new skill.
00:23:02.880 --> 00:23:13.039
Like you can't just use AI and then be better at your old way of working, like, oh, I'm just making my like that in and of itself is an old skill.
00:23:13.200 --> 00:23:31.519
So, what I've seen is quickly, um who understands and who thinks in systems versus who thinks in the sort of old way of the role and responsibility and functional aspects of the role and responsibility.
00:23:31.839 --> 00:23:42.799
And I think that that's starting to happen faster and faster now, where companies are starting to realize the whole entire organizational operation needs to be restructured.
00:23:43.039 --> 00:23:49.680
And kind of the way I see it is there's there's this layer of I'll take one step back.
00:23:49.839 --> 00:23:52.799
I think every department now needs an engineering department.
00:23:52.960 --> 00:23:59.359
Finance needs an engineering team, AI engineering team, HR needs an AI engineering, however, big, big it is.
00:23:59.519 --> 00:24:08.640
And there's this layer of AI operations and AI engineering and AI systems architect for digital outcomes that are specific to that domain.
00:24:08.880 --> 00:24:22.480
And then there are sort of wisdom holders uh that are overseeing this the operations and the output to make sure that it's um correct or that it delivers the value.
00:24:22.640 --> 00:24:31.200
And so there's like this like wisdom layer of what good looks like, and then there's an operational execution layer of engineers to make things go faster.
00:24:31.519 --> 00:24:35.039
And very few people I've met are both.
00:24:35.440 --> 00:24:38.240
And so it's just starting to separate.
00:24:38.400 --> 00:24:55.519
Um and when as these are starting to separate, and
then more and more AI engineers are being deployed in departments for the function of that department, access to data gets faster and faster, and use of data gets faster and faster.
00:24:55.759 --> 00:25:04.640
And all of the systems uh that are sitting in infrastructures right now are not ready for that type of uh governance.
00:25:04.880 --> 00:25:19.440
And so companies are re-re-architecting all of their, you know, their SAS apps and making sure that they have the most modern SaaS apps, and then privilege management for unstructured data sitting in all of these file repositories.
00:25:19.680 --> 00:25:21.440
They're just all over privileged.
00:25:21.519 --> 00:25:35.920
And so, you know, at human speed, you couldn't find that file with all of the uh payroll records you were accidentally um, you know, privileged to access that's 14 file full folders deep in this S3 bucket.
00:25:36.079 --> 00:25:38.480
Now they can't, right?
00:25:38.720 --> 00:25:46.240
And so all of this data is bubbling up for people who are like, Well, I shouldn't have access to that when they're using Clot or Copilot or something like that.
00:25:46.559 --> 00:25:51.680
So that's where uh you get into like, okay, what you really need to do is start with the data.
00:25:51.839 --> 00:25:53.039
Where's your data?
00:25:53.279 --> 00:25:53.599
Yep.
00:25:53.759 --> 00:25:56.240
What are the identities that have access to the data?
00:25:56.400 --> 00:26:05.759
Do an inventory, start mapping priorities, start putting policies and governance on every single individual asset, and so finally solve the hard problem.
00:26:05.839 --> 00:26:09.119
Luckily, there are companies like Kiteworks and others that can help you with that.
00:26:09.440 --> 00:26:10.640
Self with plug.
00:26:11.039 --> 00:26:11.920
Yeah, absolutely.
00:26:12.000 --> 00:26:14.799
But that's the thing, though, is it really is hard.
00:26:14.960 --> 00:26:23.279
You know, you think about trying to do data classifications and data inventory four years ago when GDPR really became a huge issue.
00:26:23.440 --> 00:26:25.119
Yeah, you you just can't do it.
00:26:25.200 --> 00:26:37.200
I mean, you we still have organizations that are on old-fashioned file server file shares, you know, they're still running local file shares, they can't really put any sort of data scanner on those.
00:26:37.279 --> 00:26:43.680
I mean, it's not like you're doing DLP on uh on 365, which you know, by default you have at least some.
00:26:44.319 --> 00:26:45.519
It's really hard.
00:26:45.680 --> 00:26:48.720
And and and okay, maybe that's a good question for you.
00:26:48.880 --> 00:26:54.720
So, you know, I see a divide, you know, I see the divide of organizations.
00:26:55.440 --> 00:26:58.079
Okay, let me stab it one more time.
00:26:58.240 --> 00:27:05.680
So I saw a divide four or five years ago of the people that did data privacy well and those who didn't.
00:27:05.920 --> 00:27:07.680
Now, those who did it well were small.
00:27:07.920 --> 00:27:12.000
I mean, they were smaller, it was a smaller part of the industry.
00:27:12.160 --> 00:27:16.400
Um, people had to do it for GDPR, CCPA, CPRA, things like that.
00:27:16.559 --> 00:27:18.319
But there was only a handful that did it well.
00:27:18.400 --> 00:27:23.920
They had good classifications, they knew their inventory, they knew where things at, they had the access controls.
00:27:24.240 --> 00:27:30.720
Well, now we have we still have those people that are on old technologies.
00:27:30.799 --> 00:27:39.119
I mean, I still find people once in a while that have old uh on-prem exchange servers, you know, because they don't want to move to the cloud or they don't want to do that transition.
00:27:39.359 --> 00:28:00.640
So we have these chunk of people that are still on old file shares, and we still have um older technologies that have a lot of data, and then we've got these other companies that are very quickly adapting and and they are doing good data classifications and they're they're move who they're moving that needle for themselves forward so they can get some of the benefits.
00:28:00.960 --> 00:28:07.039
Do you think that these older organizations, and when I say older, I'm just talking about they're using older technologies.
00:28:07.279 --> 00:28:26.880
Do you think they're gonna be able to catch up, or do you think they're going to fall down and kind of dissolve and go away because these other companies that are adopting these pro new processes with these new technologies are going to be to overtake the market, overtake the industry, overtake the the services that people are wanting?
00:28:27.200 --> 00:28:38.640
Yeah, I mean, there'll be some of that, but um the question is why wouldn't a company with older technology uh modernize?
00:28:38.880 --> 00:28:44.960
Um, and look, I've been in tech for 25 years almost now, which is crazy to say.
00:28:45.279 --> 00:28:51.440
Um and I 20 of that, all I heard was modernize your insert tech stack here.
00:28:51.599 --> 00:29:00.400
Um yeah, and it is just like the oldest play in the book, and a lot of it used to be around just digital transformation, which you know, that was a thing, obviously.
00:29:00.720 --> 00:29:06.079
Um, and then clo cloud um uh cloud migrations and modernization around that.
00:29:06.160 --> 00:29:11.519
So there's this in so the question is why didn't people do that stuff then?
00:29:11.839 --> 00:29:20.960
And I think again, it just gets back to it was it's too much work, it's too hard, too many you know, it things are okay.
00:29:21.599 --> 00:29:28.960
You know, it just the pain isn't enough to validate the amount of work and cost that's gonna go into it.
00:29:29.200 --> 00:29:56.160
Um I think that quickly the pain is becoming enough for literally every company, but the driver to solve for the pain and the sort of AI native um solutions to modernizing your organization are easier to transition to than technologies would have been
four or five years ago, again, because of AI.
00:29:56.400 --> 00:30:07.839
Now it's you know, you be weary the marketer because you're just gonna, you know, it's gonna sound all great, like, oh yeah, we can migrate all of your files and you know, one day and everything's fine.
00:30:08.000 --> 00:30:16.160
You know, no, it's gonna be more than that, depending on how complex systems are, but it is gonna be easier than it was four or five years ago.
00:30:16.559 --> 00:30:18.640
There will be some that just can't.
00:30:18.799 --> 00:30:20.640
That's the CEO's fault.
00:30:20.880 --> 00:30:31.839
But I think uh the there's a homogenization of access to value through technologies that wasn't in existence four or five years ago because of AI.
00:30:31.920 --> 00:30:45.680
So I think by and large, uh the that homogenization and normalization will be irrelevant of uh you know how big the company is, how much money they have, or what their journey is in that transition.
00:30:46.559 --> 00:30:48.240
Yeah, I'll I'll tell you a thing.
00:30:48.319 --> 00:31:08.160
Uh you know, back well, 20 years ago, um, I had just kind of gotten into security, computer security response team type stuff, and and we had this thing that we we needed to find social security numbers on old data share, and then it was probably, I don't know, at the time, four or five terabytes.
00:31:08.400 --> 00:31:28.640
And I remember downloading a tool, you know, I bought it, I paid for a tool, I downloaded it and I ran, and so many false positives, so many problems that I mean it it took me weeks, and I really think that now I could do that in a half a day, you know, yeah with some of our tools.
00:31:28.720 --> 00:31:39.680
I could do the exact same thing I wanted to do 20 years ago, and I can do it in hours, um, and have a higher confidence level in what was found and process it much faster.
00:31:39.839 --> 00:31:46.960
And so I think that that is really a uh a testament to what is possible, you know.
00:31:47.119 --> 00:31:53.279
Of course, only us old timers can really realize that difference, that change that's happened over the years.
00:31:53.599 --> 00:31:58.319
So okay, well, you know, we we we've got about 10 minutes left or so in the podcast.
00:31:58.480 --> 00:32:03.839
I this is a question that I'm really curious about.
00:32:04.000 --> 00:32:07.119
Where do you see us in two years or three years?
00:32:07.359 --> 00:32:09.119
You know, right now we're in transition.
00:32:09.279 --> 00:32:10.559
We know we're in transition.
00:32:10.640 --> 00:32:19.920
We're we're adopting AI, maybe not as fast as people would like, but the the organizations, the industries are adopting it, but it's gonna be very different.
00:32:20.000 --> 00:32:22.960
I feel like it's gonna be very different in let's say three years.
00:32:23.200 --> 00:32:25.119
Where do you see us in three years?
00:32:25.279 --> 00:32:31.039
Where where do you see people using what we call AI now and how do they function?
00:32:31.200 --> 00:32:36.240
What what put your put your future hat on and tell me kind of what you think?
00:32:36.640 --> 00:32:40.319
Yeah, I mean, that's the that's the big question, isn't it?
00:32:40.480 --> 00:32:46.559
Um one I probably ask myself daily, maybe I don't stretch it out to three years.
00:32:46.720 --> 00:32:53.279
Um I think there's there's two trajectories and then variants on the trajectories.
00:32:53.680 --> 00:32:55.119
One is very negative.
00:32:55.440 --> 00:33:03.839
Um I two years ago I sat with our CEO and I you know I I just I was obsessed with what was going on.
00:33:04.160 --> 00:33:04.960
Unhealthy.
00:33:05.119 --> 00:33:08.319
Like kids are like, what are can you join us in life?
00:33:08.559 --> 00:33:20.079
Um and I I basically said, Look, I think in two two years, this is a year and a half ago, that you and I are gonna be sitting in this conference conference room going sit looking at each other and going, WTF.
00:33:20.240 --> 00:33:28.559
I don't know what WTF what will inspire that, and I don't know the degree to which it will mean negative or positive, but I know you know in two years.
00:33:28.720 --> 00:33:29.839
So I got six months on that bed.
00:33:30.000 --> 00:33:31.359
It's a big bottle of wine with that.
00:33:31.920 --> 00:34:12.239
Um but the the dirt two pass, there's a possibility of uh you know I'm not a doomer, but it's possible that there's a and let's not take it to the human extinction level they do, but in business operations, there's a potential that the vulnerabilities and the security issues and the the there's a catastrophe that forces everything to shut down operationally and reswizzle and you know crushes the economy for six months and everybody has to figure something out.
00:34:12.320 --> 00:34:14.639
Like I think that's that's a real possibility.
00:34:14.800 --> 00:34:20.159
Um, in that case, I I I'm not sure where we come out on the other side uh in three years.
00:34:20.320 --> 00:34:29.280
So let's go down the the big the the more interesting path, which is uh what happens to uh how people operate at business and business.
00:34:29.760 --> 00:34:51.599
It I think that it becomes such a self-fulfilling machine that we can produce and drive economic uh gains at such a scale that the quality of life goes up and quality of people's experience at work goes up.
00:34:52.000 --> 00:35:19.440
And as I don't think we'll have job losses as job change, and I think the job change what's left is this entire um industry or this entire operating model in business where people get to think and strategize and operationalize and be creative and find new paths to revenue and value, and there's almost no grudge work.
00:35:19.599 --> 00:35:31.519
Like that's what I think will will happen in three years is that you you just because I see it in my own life, like my day-to-day, I have almost completely stripped out everything I hate about going to work.
00:35:32.239 -->
00:35:44.960
And the only the only thing that's left is stuff like this, um operating the team, um, and creating new solutions to to hard problems.
00:35:45.119 --> 00:35:52.800
And I think you know, I'm probably on the forefront of that, as you probably are, and it just people are going to to catch up to that.
00:35:52.880 --> 00:35:58.320
And so I think we're we're looking at a really positive future, assuming the bad part doesn't happen.
00:35:58.639 --> 00:35:59.280
Yeah, yeah.
00:35:59.519 --> 00:36:14.000
And I know a lot of people like talking about the bad part, and and I'm gonna say I do from a tabletop and a a uh a disaster recovery point of view for my clients, you know, I've I've got to make sure that they're ready for anything that happens.
00:36:14.079 --> 00:36:17.280
So we do talk about that, but I I like talking about the good side.
00:36:17.519 --> 00:36:27.360
Um, and I'll tell you, you know, that's one of those things that when we look back, you know, uh I don't know how old you are, but you know, I'm pretty old.
00:36:27.440 --> 00:36:30.320
But you know, it's you this summer and it hurts.
00:36:30.559 --> 00:36:34.880
No, I'm not very far after you, so I I get that.
00:36:35.199 --> 00:36:37.199
But you know, think about the what we grew up with.
00:36:37.280 --> 00:36:41.519
I mean, we had Terminator, we had Matrix, we had you know, all these things.
00:36:41.599 --> 00:36:45.440
That's the bad side, and we know it, but think about all the good stuff we saw.
00:36:45.679 --> 00:36:49.920
Star Trek, they had AI on their computers, Star Wars.
00:36:50.000 --> 00:36:54.400
We I I would love to have a fully functional R2D2 rolling around in my trailer.
00:36:54.639 --> 00:36:56.239
I would I would love that.
00:36:56.800 --> 00:37:00.800
Um, so I mean, I think we do have both sides.
00:37:00.880 --> 00:37:06.960
I I mean, and we may have some negative effects, and I think negative effects are actually just because people are going to be people, you know.
00:37:07.039 --> 00:37:09.199
I don't think it's necessarily about technology.
00:37:09.440 --> 00:37:20.800
Um, I I was telling my daughters, um, I've got I've got three kids, and my daughters are the oldest ones, and they I mean, uh someone called them iPad babies.
00:37:20.960 --> 00:37:26.559
Um they they have never not had, as far as they remember, a tablet of some kind.
00:37:26.639 --> 00:37:28.639
You know, I and they were very, very small.
00:37:28.719 --> 00:37:34.320
I got them a kid's Google tablet thing so they could learn and play games and learn to read and whatever.
00:37:34.559 --> 00:37:37.519
Um, so they've never not had that technology.
00:37:37.760 --> 00:37:50.639
Um, and I feel very um very fortunate that they can be without that technology because I randomly will turn the main power off to the house and we live for a couple of days because you know, disaster recovery and tabletops and whatever.
00:37:51.039 --> 00:37:51.840
And they're fine with it.
00:37:51.920 --> 00:37:55.519
They they it's like, oh, okay, you know, no internet, let's let's go do something else, you know.
00:37:55.599 --> 00:38:06.639
Let's so I think you know, we go two years from now, uh it kind of like you know, back when online cloud storage became a thing.
00:38:06.719 --> 00:38:11.519
We had box and dropbox and AWS and OneDrive and this.
00:38:11.760 --> 00:38:14.480
Now, honestly, we have the big names.
00:38:14.639 --> 00:38:18.159
We have AWS, we have Google, and we have OneDrive.
00:38:18.320 --> 00:38:20.880
You know, there are other ones out there, but no one ever talks about them.
00:38:20.960 --> 00:38:23.920
I don't ever hear people talking about, oh, we need to get Dropbox work in.
00:38:24.000 --> 00:38:26.159
They I think that's gonna be the same thing with AI.
00:38:26.320 --> 00:38:30.960
I think it's gonna be built into our large tools, it's just gonna be part of who we are and what we do.
00:38:31.199 --> 00:38:33.519
And I don't think people are gonna think about it anymore.
00:38:33.679 --> 00:38:38.719
Yeah, I mean, I think I think people yeah, it's just gonna be part of what we do.
00:38:38.800 --> 00:38:43.920
Now, I will think I you know, I I grew up in higher ed, you know, in terms of my IT side.
00:38:44.159 --> 00:38:47.440
I think that will absolutely change higher education.
00:38:47.599 --> 00:38:56.719
Um, because you know, the idea of having someone write a 30-page paper, and I wrote lots of them back whenever I was in the business school, that's not a thing anymore.
00:38:56.800 --> 00:39:00.480
I don't think that that's I don't think it's a value of any kind of writing a 30-page paper.
00:39:00.639 --> 00:39:04.800
Write content, and if you've got to hit a number, well, AI can help you do that.
00:39:04.880 --> 00:39:08.079
I mean, it's let's let's get more pure in what we do.
00:39:08.239 --> 00:39:12.159
So I I think it's just gonna become part of our existence.
00:39:12.320 --> 00:39:26.079
It's it's I'm we're old enough, I'm old enough to know the difference between people who used to read the newspaper every single day and the people who check the news online every single day, and that transition happened.
00:39:26.239 --> 00:39:26.960
Well, what do we have?
00:39:27.119 --> 00:39:28.639
Very few newspapers anymore.
00:39:28.800 --> 00:39:32.320
I think it's just going to evolve and and move into that.
00:39:32.559 --> 00:39:37.199
I tell my clients, uh, two years from now, we're not gonna be having these discussions.
00:39:37.440 --> 00:39:39.119
You know, we'll be past that.
00:39:39.199 --> 00:39:41.840
We'll we'll have already gotten those pieces in place.
00:39:42.079 --> 00:39:45.519
We will know how to use AI, people are going to be trained on it.
00:39:45.599 --> 00:39:54.480
We're not going to have to necessarily I mean, we'll have to do security for sure and data classifications, like you said, but we're not gonna have to do all this extra stuff that we're having to do
right now.
00:39:54.880 --> 00:39:55.920
You think two years?
00:39:56.000 --> 00:40:01.920
I I I think uh it's just so hard for people to who move my cheese.
00:40:02.159 --> 00:40:11.599
Like that book, yeah, is is it's so pro relevant into right now that I just don't know if it uh it too two years that's ambitious.
00:40:11.920 --> 00:40:12.559
I hope so.
00:40:13.199 --> 00:40:15.840
I think I think the technology will be there in two years.
00:40:16.159 --> 00:40:19.920
People, you're right, maybe the people won't be there, but I think the technology will be, yeah, yeah.
00:40:20.000 --> 00:40:20.639
I'll buy that.
00:40:21.039 --> 00:40:22.639
Um, I mean, look at it right now.
00:40:22.719 --> 00:40:26.000
You take Copilot, it's in everything in terms of Office 365.
00:40:26.079 --> 00:40:26.800
You can't get away with it.
00:40:26.960 --> 00:40:28.079
What if I never use it?
00:40:28.400 --> 00:40:30.320
It might not just be me, it just sits there.
00:40:30.400 --> 00:40:40.000
I'm like, I don't want to I I know, but it's there, and I think that that's the issue is it's just going to be that those tools are going to be there.
00:40:40.320 --> 00:40:46.000
I mean, I wait until the first time someone has uh AI interaction on a watch.
00:40:46.159 --> 00:40:49.840
So you always have AI to be able to ask a question, you know.
00:40:50.159 --> 00:40:56.480
You don't have to you don't even have to pull your phone out, you just you do you dick tracy it and you turn your wrist frost up and you ask a question.
00:40:56.559 --> 00:40:58.800
Well, you you probably already have that if you have an apple watch.
00:40:58.880 --> 00:41:02.960
I don't have an apple watch, but you know, you probably already have some of that functionality there.
00:41:03.119 --> 00:41:05.199
I think it's just gonna be there, you know.
00:41:05.360 --> 00:41:13.199
I think the other part of just be there is that it's you know, one of the things is uh why I don't use copy, you you have to go and use it.
00:41:13.440 --> 00:41:22.960
Yeah, that's very quickly, it's gonna be like you don't have to go and use it, it's just being used and it's telling you what you should be doing without you engaging.
00:41:23.039 --> 00:41:28.960
And I experienced that I have Muse on my, you know, the Muse had a Muse agent on my phone every morning.
00:41:29.039 --> 00:41:32.320
It's like, hey, I was thinking of this last night.
00:41:32.480 --> 00:41:35.760
You know, it proactively starts telling me about stuff.
00:41:35.840 --> 00:41:44.159
Um, and I think that's probably where you know it just becomes ambient and you're you're not really actioning anything, it just does it, you know.
00:41:44.639 --> 00:41:50.000
Well, and I think that as technology gets better and easier, I mean, I I do a lot of driving.
00:41:50.159 --> 00:41:56.239
Um, and when you know, when you start driving for a long time, you will get tired, just for sure.
00:41:56.480 --> 00:42:00.800
And I will regularly pull up Chat GPT on my phone and have an argument with it.
00:42:00.960 --> 00:42:04.639
You know, it I don't really care about what the topic, it's a topic I'm interested in.
00:42:04.880 --> 00:42:05.840
Sure, I do the same, yeah.
00:42:05.920 --> 00:42:06.400
I'm not sure.
00:42:06.719 --> 00:42:11.360
I I just I want to talk, I want to engage that part of the brain that's going to keep me awake to get me home.
00:42:11.440 --> 00:42:22.639
And and I've had some really uh the processes in my own brain I've been able to form because of those questions that I ask and the information I got back.
00:42:22.800 --> 00:42:31.039
Um so and I think that that's what's a lot of people are going to do is they're going to find that that niche where that tool can really help them.
00:42:31.199 --> 00:42:37.679
Again, I want that R2D to that I can ask questions and they can roll up and answer my questions and then roll back and go do other stuff.
00:42:37.840 --> 00:42:44.559
So um, but well, okay, so we're we're we're we're right on the edge of time.
00:42:44.719 --> 00:43:01.039
So tell me a little bit more about uh kiteworks, you know, just give me a a breakdown of, you know, we've got our you know, the the the people who watch the the the podcast or listen to the podcast, what what do they need to really think about in terms of kiteworks and helping them and their organization?
00:43:01.360 --> 00:43:06.719
Yeah, so we we position ourselves in market as the control plane for secure data exchange.
00:43:06.880 --> 00:43:14.480
So, you know, data sits there, that's one thing, but it becomes really uh vulnerable.
00:43:15.280 --> 00:43:24.079
And um there are opportunities for leakage during an exchange process, so from point A to point B.
00:43:24.400 --> 00:43:30.000
And it's the point A to point B, like I said, is human to human, machine to machine, and machines now AI.
00:43:30.239 --> 00:43:41.440
So so data is moving and being used constantly, and we sit as as the control plane between those two the the point A and point B of data being exchanged.
00:43:41.519 --> 00:43:48.480
We encrypt the data, we apply policy controls that are granular down to uh context.
00:43:48.639 --> 00:43:50.000
So, where's the data coming from?
00:43:50.079 --> 00:43:50.719
Where's it going?
00:43:50.800 --> 00:43:51.519
Who's sending it?
00:43:51.599 --> 00:43:52.639
Who's trying to access it?
00:43:52.800 --> 00:43:54.239
What system did it come from?
00:43:54.400 --> 00:43:55.840
What's in the context of the data?
00:43:56.000 --> 00:43:56.800
What's the metadata?
00:43:57.199 --> 00:43:59.760
Like correlating all of these different attributes.
00:44:00.079 --> 00:44:04.559
some attribute-based access control to the data in in exchange, right?
00:44:04.719 --> 00:44:14.960
And and to be able to put not just allow block like the old DLPs would do, but you know, allow allow but then we have different layers of security.
00:44:15.199 --> 00:44:23.599
View only, water market, um, we
can provide a streaming service where the application provides the file but the data never leaves the data center.
00:44:23.840 --> 00:44:29.360
So being allowing for productivity but also reducing risk and then of course block.
00:44:29.519 --> 00:44:44.880
And so having all of these different controls on that data as it moves to being used by humans or AI is really where where we sit and we focus on regulated industries and regulate regulated data, which is pretty much all industries now at some to some degree.
00:44:45.039 --> 00:44:45.519
Oh yeah.
00:44:46.480 --> 00:44:50.000
There's some regulation somewhere that's telling you to do something with data.
00:44:50.159 --> 00:44:50.400
Yeah.
00:44:50.639 --> 00:44:58.639
And so we're not the all data in your company, but we're the regulated data layer for uh and that's really what people care about.
00:44:58.800 --> 00:45:03.920
They don't want the back the the regulated info is the info that's important to secure.
00:45:04.079 --> 00:45:18.800
So that's where we say we give those controls to companies and enable them to understand how where data's moving allow them to block and control use of it and um essentially report up to the auditors and the board as to what's happening in this AI era.
00:45:19.119 --> 00:45:19.599
Right.
00:45:19.760 --> 00:45:20.960
Well that's fantastic.
00:45:21.039 --> 00:45:29.840
And and and kiteworks has been around for a while because I remember meeting people at conferences, you know, when of course I was doing a lot more data secure data privacy back then.
00:45:30.000 --> 00:45:32.400
But how long has Kiteworks been around?
00:45:32.719 --> 00:45:34.480
Yeah so it's a long story.
00:45:34.800 --> 00:45:50.800
The short version is the company has been around 24 years, I want to say but it was okay let's say 17 of it was under the name Excelion where at the time it was a secure file transfer company where it was just large files point A to point B.
00:45:51.039 --> 00:46:07.599
Yep move it uh securely and in the past nine years or so uh we've really transformed to being that governance layer on data exchange across not just file transfer but email and um managed file transfer and automated transfers and file sharing and collaboration.
00:46:07.760 --> 00:46:15.360
So we've I would say new Kiteworks nine years old full operating business 20 plus years.
00:46:15.599 --> 00:46:33.280
Okay well and that makes sense because I remember KiteWorks and nine years ago I was doing you know hard and heavy GDPR and and and and all the different data privacies that we were doing and back in my old job I was doing the data transfers you know to I wanted to do I wanted to do it because I knew I could secure it.
00:46:33.519 --> 00:46:38.719
So I let everyone else do the approvals it got to me and then I would move it around and do different things.
00:46:38.880 --> 00:46:39.760
So yeah.
00:46:40.079 --> 00:46:43.760
All right well Tim thank you so much for being on the podcast this has been great.
00:46:43.920 --> 00:46:55.760
I've really enjoyed talking with you um I uh I I I want to come back in in maybe a a a year or two and talk to you again because I'd like to I want to see where we're at in those two years.
00:46:55.920 --> 00:46:59.679
And I think that that's uh it's gonna be very telling for all of us.
00:46:59.840 --> 00:47:08.159
Um but I'm gonna remember this conversation and at some point I'll reach back out to you and see if I can get you back on the podcast so we can see kind of where we're at in two years.
00:47:08.400 --> 00:47:59.760
Yeah that'd be great and I I appreciate it Jonathan and just one uh you know again shameless plug obviously we're at kiteworks.com and I do invite people to uh actually subscribe to our Substack like we do a lot of thought leadership there it's called the control plane if you just go there kiteworks the control plane you'll find it a lot of interesting information there so appreciate the time Tim thank you so much I really appreciate it hope you have a wonderful rest of the week and for all of our listeners and all the people that's watching thanks for joining us at the Secure AF podcast we've got another great show coming I believe next week so tune in your favorite uh podcast uh tools and we'll see you next time thanks everybody the Secure AF Podcast is a production of alias cybersecurity visit us online at alias cybersecurity dot com all rights reserved