สำเนาบทสนทนา 🔗
WEBVTT
00:00:10.099 --> 00:00:10.808
That's true.
00:00:10.819 --> 00:00:11.358
That's true.
00:00:11.358 --> 00:00:15.249
Hey, folks, welcome to another episode of the Security Table.
00:00:15.519 --> 00:00:16.829
My name's Chris Romeo.
00:00:16.849 --> 00:00:20.989
I'm joined by Matt Coles and Izar Tarandach.
00:00:20.989 --> 00:00:25.239
And if you remember the 1990s, by any chance, you remember the show Seinfeld.
00:00:25.638 --> 00:00:27.388
Seinfeld was the show about nothing.
00:00:27.699 --> 00:00:29.399
This is kind of the podcast about nothing.
00:00:30.689 --> 00:00:31.018
Right?
00:00:31.088 --> 00:00:31.798
No, come on.
00:00:31.798 --> 00:00:32.969
We're talking about lots of things.
00:00:32.969 --> 00:00:42.698
We have, we have, uh, serious conversations about with us sitting around a Chinese restaurant for the entire podcast episode and nothing really happened.
00:00:42.719 --> 00:00:44.319
No, that's a, a Seinfeld
00:00:44.459 --> 00:00:45.109
we can still say,
00:00:46.209 --> 00:00:46.459
hello.
00:00:47.749 --> 00:00:47.988
And if you
00:00:48.219 --> 00:00:49.668
No No security for you.
00:00:50.408 --> 00:00:51.499
If you know, yeah, that's
00:00:51.789 --> 00:00:51.798
HELLOOOOOO!
00:00:51.829 --> 00:00:53.728
No security, no security for you.
00:00:54.168 --> 00:00:54.429
All right.
00:00:54.429 --> 00:00:58.978
What other Seinfeld reference can we make a security analysis of here?
00:00:59.238 --> 00:01:00.478
I mean, there was the double dip.
00:01:00.859 --> 00:01:07.899
Double dip was invented in that episode where George Costanza is at the, I don't remember what he was doing.
00:01:07.899 --> 00:01:12.168
He's at that party and he dips his chip in the second time and the kid is across the room.
00:01:12.168 --> 00:01:13.478
He's like, what are you doing?
00:01:14.418 --> 00:01:15.239
You double dipped.
00:01:15.239 --> 00:01:17.938
I don't know what the double dip analogy is in security, but.
00:01:18.938 --> 00:01:19.899
I don't know, it's somewhere.
00:01:20.739 --> 00:01:21.739
I'm sure it exists.
00:01:22.108 --> 00:01:24.228
One year! It's when you have two formats of the same SBOM.
00:01:26.289 --> 00:01:30.489
Okay, that was, uh, that was good.
00:01:30.528 --> 00:01:31.218
That was good.
00:01:31.328 --> 00:01:32.489
I, uh, that's, that is
00:01:32.698 --> 00:01:35.528
HAHAHAHAHA! These vulnerabilities are making me thirsty! Yeah.
00:01:35.664 --> 00:01:41.153
I was, I was going to say, I was going to say something like you're, you're, you're streaming your lugs to SysLug and Splunk at the same time.
00:01:41.183 --> 00:01:41.573
I mean,
00:01:41.629 --> 00:01:42.459
Oh, there you go.
00:01:43.069 --> 00:01:43.679
Now here's one.
00:01:43.688 --> 00:01:44.748
Here's one for you though.
00:01:45.019 --> 00:01:46.718
I bet you, there's a lot of.
00:01:46.944 --> 00:01:51.224
CISOs that are standing before the board and would like to say the following.
00:01:51.634 --> 00:01:56.614
So we started building our security program, yadda, yadda, yadda, and then the FBI showed up.
00:02:00.664 --> 00:02:02.793
Imagine that as a board presentation, so.
00:02:02.804 --> 00:02:07.233
Okay, we gotta talk about s we gotta this is the this now concludes our Seinfeld.
00:02:07.659 --> 00:02:10.628
Uh, memorabilia section of the security table.
00:02:10.628 --> 00:02:14.399
Let's talk about AppSec versus product security.
00:02:14.968 --> 00:02:30.008
There's been a number of different articles written over the last couple of months that we've, we've taken a look at and let's, we want to, we want to set the record straight from our perspective, as far as what we think of as the differences between these things and similarities.
00:02:30.468 --> 00:02:36.109
And so, shall we start with a definition of AppSec?
00:02:36.399 --> 00:02:38.449
What the heck is AppSec?
00:02:42.033 --> 00:02:43.864
Izar, do you want to go first?
00:02:44.438 --> 00:02:46.068
Ah, you know how I'm with definitions.
00:02:46.088 --> 00:02:46.959
You go for it.
00:02:47.554 --> 00:02:49.394
You know how I am with this topic.
00:02:49.463 --> 00:02:53.133
So, uh, since we've had a low back conversation prior to joining on the
00:02:53.139 --> 00:02:53.459
Cool.
00:02:53.549 --> 00:02:53.919
Cool.
00:02:54.364 --> 00:03:04.993
Well, actually no, so when we actually, Chris, if you could start, cause this ultimately this episode really is to, to, to give our perception of what AppSec and ProdSec are.
00:03:05.033 --> 00:03:22.493
Given, and the, the statements being made in these articles, uh, you know, from, from various sources, um, either some of these things are brand new to people, um, or, and, or certainly there is confusion in the industry about what these things mean.
00:03:23.033 --> 00:03:26.883
So, what do you think application security is?
00:03:28.449 --> 00:03:32.778
Yeah, let's uh, let's work our way through kind of a definition.
00:03:33.038 --> 00:03:43.389
Now I just happen to have done my own definition in a talk I did this previous year, the Application Security State of the Union, so I'll give you the definition that I put together for that perspective.
00:03:44.919 --> 00:03:54.179
So I think of application security as the people, process, tools, and governance that are required to properly secure applications.
00:03:55.008 --> 00:04:06.498
So for me, I go back to, I I'm always more, I'm always a bit of a programmatic thinker, like that's just tend to be how I approach the world is how do we programmatize this thing that we're trying to do?
00:04:06.498 --> 00:04:12.489
And so for me, application security is what we need to do for the people, the process.
00:04:13.399 --> 00:04:18.269
Processes, the tools, and the governance to properly secure our applications.
00:04:18.399 --> 00:04:18.678
So,
00:04:18.994 --> 00:04:21.084
so, yeah, so really briefly.
00:04:21.709 --> 00:04:23.178
What do you define as an application?
00:04:24.718 --> 00:04:31.579
An application is anything
Load full transcript
that has, anything that is made up of software.
00:04:33.319 --> 00:04:34.269
Oh, that's interesting.
00:04:34.749 --> 00:04:37.418
So let's introduce product security now.
00:04:37.899 --> 00:04:39.019
So what's a product?
00:04:39.119 --> 00:04:44.798
Yeah, so, but see, I tend to think of product security.
00:04:45.894 --> 00:04:50.994
Hardware and software application security software, and some of that is just where I grew up.
00:04:50.994 --> 00:04:56.634
As we were talking about before we, before we hit record on this episode, I was at Cisco for 10 years.
00:04:56.639 --> 00:05:02.093
Cisco has 27,000 products that are Not really, not quite that many, but they have a lot.
00:05:02.274 --> 00:05:07.103
They have, and in those days they had metal boxes that were routers and switchers.
00:05:07.223 --> 00:05:07.764
Switchers.
00:05:07.793 --> 00:05:09.913
What's a switcher, a new word here.
00:05:10.153 --> 00:05:14.324
Routers and switches that were, and I used to think of them, there was the metal box component.
00:05:14.548 --> 00:05:18.769
And then there was the the bits that were going into it to drive that metal box.
00:05:19.108 --> 00:05:34.733
And so I tend to, in my own mind, based on my experience, I tend to attribute product security as the things that I have to do to secure these metal boxes running the software or You know, you can extend it to cloud services and everything else that's a product.
00:05:35.093 --> 00:05:41.283
But I think of AppSec and applications as more of a general, general thing.
00:05:41.574 --> 00:05:44.314
Like, I don't think of applications as something that you sell.
00:05:44.814 --> 00:05:48.524
Like, you don't sell, like, I can't go, I'm going to go sign up for this new application.
00:05:49.204 --> 00:05:53.223
Nobody says that anymore, other than maybe in the context of mobile apps.
00:05:53.634 --> 00:05:56.483
That's what an application is in the use of that term.
00:05:56.803 --> 00:05:57.884
So I've talked enough.
00:05:57.913 --> 00:06:02.853
You guys tell me what your, what your, uh, how you break it down, how you separate it.
00:06:03.649 --> 00:06:08.858
So generally I look at products, products as things that a company sells.
00:06:09.803 --> 00:06:20.153
So they deliver to customers versus the things that they deploy themselves, either internally or for their customers, you know, exposed to their customers like a cloud or SaaS service.
00:06:20.733 --> 00:06:28.108
Um, but the product security would be securing the things, whether those are physical or, or non physical.
00:06:28.439 --> 00:06:35.809
Things that gets, that gets shipped externally and sold, you know, and, and either sold or given or used by customers.
00:06:35.819 --> 00:06:41.788
So, uh, potentially, or most likely, mobile applications, because those obviously go.
00:06:42.384 --> 00:06:46.374
That's software only that goes, that gets delivered outside of the company.
00:06:47.053 --> 00:06:52.163
Uh, certainly the bits that
run on the product, on the physical device and the physical device itself.
00:06:52.504 --> 00:06:55.343
So the people process, processes, etc.
00:06:55.403 --> 00:06:57.483
Uh, you know, infrastructure, networking, etc.
00:06:57.533 --> 00:07:03.564
That might get delivered with that, that physical box, uh, and the firmware and software that it runs.
00:07:04.124 --> 00:07:08.754
Uh, and any operating software, you know, if, if we don't.
00:07:10.139 --> 00:07:21.119
Thick clients are not as prevalent today, I think, but, uh, you know, when we used to have desktop software that controls, you know, the boxes, um, the, those are products too.
00:07:21.939 --> 00:07:55.069
Applications being things, business applications, especially being things that the business uses to, to Do all of that work as well as the things that they may then expose to to customers like, you know, License management and support systems and things like that And and so product security is is making sure that from a physical physical up Right, in the stack, security wise, and then applications, of course, would be anything that sits on top of the, on top of the infrastructure.
00:07:55.418 --> 00:08:07.038
If we think of the cloud model of, you know, SaaS, IaaS, PaaS, um, right, anything that sits on top of the, the infrastructure, at least, is the application, right, the software portion.
00:08:07.968 --> 00:08:10.538
Izar, do you, how do you feel about, about that?
00:08:11.384 --> 00:08:16.144
Well, so you guys know me, I like to think in terms of analogies, right?
00:08:16.324 --> 00:08:19.134
And when I went looking for one that could cover this.
00:08:20.093 --> 00:08:26.043
Luckily, my wife was watching one of those, uh, home improvement things on TV.
00:08:26.869 --> 00:08:48.649
And I think, and I know there are holes in the analogy here, but I think that what came to my mind was the difference between the interior designer that's turning a room in a building into something functional and that works for its purposes and that explores well the space.
00:08:49.629 --> 00:08:51.119
And that for me is an application.
00:08:51.884 --> 00:09:05.504
And the prod security is the architect or engineer that comes and builds the whole building around that thing, including all the plumbing and all the codes and all the safety and all the, all that kind of stuff.
00:09:06.333 --> 00:09:17.153
So, first of all, I was very, I don't know, very, uh, uh, I don't know if surprised is the term by the question itself.
00:09:17.994 --> 00:09:22.984
And especially when I read that some people think that Prod Security is an emerging new thing.
00:09:23.524 --> 00:09:29.264
Because, to the best of my recollection, we have been doing Prod Security for, Matt, how much is it now?
00:09:29.948 --> 00:09:30.599
It's been a long time.
00:09:30.599 --> 00:09:31.099
Long, long, long I mean,
00:09:31.288 --> 00:09:34.119
mean my, my, my title, my title and your title.
00:09:34.139 --> 00:09:37.519
Actually, we were both product security engineers for a
00:09:37.754 --> 00:09:38.264
We
00:09:38.308 --> 00:09:38.389
of
00:09:38.614 --> 00:09:41.543
came to work in the Prod Security office,
00:09:41.634 --> 00:09:43.379
in, in the mid, in the mid 2000s.
00:09:43.399 --> 00:09:46.899
I mean, so this is not a new, the term is not new.
00:09:46.908 --> 00:09:49.119
Maybe the scope has changed.
00:09:49.854 --> 00:09:51.933
I think it's exposure to the market too.
00:09:51.943 --> 00:09:59.153
It's exposure to specific companies because product companies tended to be the leading.
00:09:59.943 --> 00:10:04.183
Organizations that were deploying product security offices and product security engineers.
00:10:04.193 --> 00:10:05.563
I mean, we had it at Cisco.
00:10:05.563 --> 00:10:15.764
We were product security at Cisco Um, and that's, but that's because we had a company that was driven by a lot of different products that required That level of thing.
00:10:15.764 --> 00:10:26.894
And it was funny at Cisco, Application security became synonymous with what InfoSec was doing Securing the business applications and the internal applications.
00:10:27.214 --> 00:10:33.693
And product security was what we were doing as we were serving the business units and technology groups to help them build secure products.
00:10:36.903 --> 00:10:45.984
So, another thing that I saw in those, in those articles was that there was a tendency to go for the cardinality of the thing.
00:10:46.014 --> 00:10:52.293
AppSec is one, PodSecurity is many, or PodSecurity is one and AppSec is many, that kind of thing.
00:10:52.903 --> 00:11:04.639
And I think that I prefer best Chris' approached to defining AppSec and he went straight where I wanted to go, the PPT, the people, processes, and tools.
00:11:05.249 --> 00:11:15.759
And I think that I would extend that and say that to me, product security, application security is one of the tools and processes that goes into product security.
00:11:17.009 --> 00:11:28.808
So if I'm looking at some kind of relationship between them, some kind of Venn diagram between them, I would say that to me, AppSec falls.
00:11:29.163 --> 00:11:38.244
in the middle of the, the, the ProdSec bubble, but it goes a bit outside because it can exist as its own thing, right?
00:11:39.224 --> 00:11:42.394
What would make it exist as its own thing, I'm not so sure.
00:11:43.264 --> 00:11:45.033
Is it a size thing?
00:11:45.043 --> 00:11:46.583
Is it a focus thing?
00:11:46.594 --> 00:11:46.913
Is it a...
00:11:48.193 --> 00:11:50.903
Like, if somebody comes and says, oh, what about internal applications?
00:11:50.903 --> 00:11:52.464
Yeah, what about internal applications?
00:11:52.683 --> 00:11:58.844
They don't need the same standards and, and scrutiny that a product would need.
00:11:58.903 --> 00:11:59.403
Why not?
00:12:00.413 --> 00:12:01.683
Why have two processes?
00:12:01.903 --> 00:12:07.083
Why can't you treat your internal stuff as a product,
right?
00:12:07.874 --> 00:12:09.644
You probably gain a lot of stuff in there.
00:12:09.653 --> 00:12:21.119
I guess that you would probably not lose, but you would have a, a, a bit of, uh, Waste in there, as Jim liked to put it, but uh, I don't see why not.
00:12:22.899 --> 00:12:25.908
So I'm still a bit murky here on the,
00:12:26.509 --> 00:12:27.788
I think there's a lot of overlap.
00:12:28.538 --> 00:12:30.418
I think there's definitely a lot of overlap.
00:12:30.418 --> 00:12:35.489
I think what you're highlighting is there's inefficiencies if you separate the two, right?
00:12:35.548 --> 00:12:37.078
But I think that they are different.
00:12:37.278 --> 00:12:50.089
If we look at business systems, you know, things that a company deploys versus things that they sell, especially if it's associated with hardware, especially, right, the rules are different.
00:12:51.188 --> 00:13:06.058
Uh, and so while there's, there's some inefficiencies if you separate them, because things like the same vulnerability scanners that we use to look at the firmware on a box, uh, you know, can target a, a dust, I mean, a business application, right?
00:13:06.058 --> 00:13:08.178
A cloud, a cloud application or web application.
00:13:08.528 --> 00:13:18.678
The same, whether that web application is running, you know, in a, You know, a private cloud versus a, uh, on, on the box or on, on somebody's desk.
00:13:19.239 --> 00:13:22.438
Uh, so there, there's no reason to separate those, right?
00:13:22.438 --> 00:13:25.589
Those are dual purpose, uh, tools, for instance.
00:13:26.438 --> 00:13:26.769
But...
00:13:27.274 --> 00:13:35.484
The rules that govern what you sell and ship, right, need to follow a different set of rules than, than how you deploy, right?
00:13:35.524 --> 00:13:39.264
Let's take about, think about like, uh, connectivity, right?
00:13:39.394 --> 00:13:42.293
In the business environment, you own the, you own the network.
00:13:42.769 --> 00:13:42.938
Right.
00:13:42.938 --> 00:13:43.958
The company owns the network.
00:13:43.958 --> 00:13:45.928
When you deploy it, you're going to have certain requirements.
00:13:45.928 --> 00:13:58.308
You have a known infrastructure that you're, that you're deploying into, you know, say they're on Azure or AWS, or they have their own internal, you know, network and infrastructure and, and, you know, log infrastructure and whatnot.
00:13:58.649 --> 00:14:02.229
And those are the rules that govern that application deployment.
00:14:02.599 --> 00:14:06.793
When you're selling something, You're deploying that into a customer's environment.
00:14:06.813 --> 00:14:09.864
They're going to run their own firewalls, their own network infrastructure.
00:14:09.894 --> 00:14:14.413
They may or may not be in a cloud, a public cloud or a private cloud or a hybrid cloud.
00:14:15.144 --> 00:14:17.134
New concept, multi cloud these days.
00:14:17.183 --> 00:14:20.813
Uh, you know, these are, it's a lot more.
00:14:21.149 -->
00:14:28.808
Open, but you also have to be careful of things like, uh, inbound, inbound network requests and poking holes in the firewall.
00:14:29.528 --> 00:14:32.839
Um, or what regulations you have to, uh, have to apply.
00:14:33.408 --> 00:14:47.139
So the design requirements and standards and patterns that you use and some of the, um, some of the, the constructs and systems that might get deployed and how you secure them and your threats that you're looking for.
00:14:48.663 --> 00:14:57.254
will differ, I think, and you'll have a broader, a broader set of things to look at if you're talking about the thing that you deliver versus the thing that you deploy.
00:14:58.423 --> 00:15:13.313
However, I can see where you think that if you wrap this, a set of things, even if you deploy it locally, you wrap a set of things as a product, especially if it has a customer facing aspect, like a business application that may like a support system, right?
00:15:13.344 --> 00:15:20.469
If that's your, if that's your business, That is your product or, and, and they're like Twitter, right?
00:15:20.519 --> 00:15:22.499
Uh, or X or whatever it's called these days.
00:15:22.989 --> 00:15:28.408
Um, you know, that is a, that's a business application that's deployed for customer use.
00:15:28.408 --> 00:15:30.859
That's, that's obviously it's product.
00:15:31.308 --> 00:15:35.729
Although some people, I guess say we're, we're the product, not the business system.
00:15:35.729 --> 00:15:39.139
But so is that an application or is that a product?
00:15:40.188 --> 00:15:41.869
It's not something they sell.
00:15:41.899 --> 00:15:43.749
It's something they sell, but it's not something they deliver.
00:15:45.423 --> 00:15:47.724
Yeah, and they deliver it via mobile app and...
00:15:47.870 --> 00:15:51.479
API endpoints and, and other things.
00:15:52.099 --> 00:15:57.349
Okay, so I got a different, a different way to, I've just been thinking about a different way to frame the question.
00:16:00.009 --> 00:16:03.519
That may, maybe this will, maybe this will unlock something for us, maybe not.
00:16:04.578 --> 00:16:07.658
Why is there an application security industry?
00:16:07.839 --> 00:16:14.019
Meaning there's a whole cottage industry of tooling and consulting and everything else, but there's not a product security industry.
00:16:17.668 --> 00:16:26.729
A, perhaps because there isn't a need for one, because we all understand that a big technical part is being covered by the AppSec one.
00:16:28.408 --> 00:16:39.288
B, perhaps there is, we just don't take the steps to call it such, because, sure, you are a VP of Prod Security.
00:16:40.318 --> 00:16:44.859
That means that you have a certain number of, uh, almost preordained functions under you.
00:16:45.778 --> 00:16:53.538
And that makes you fraud security, because as, as Matthew said, that there are, there's a number of things that need to be, to be covered.
00:16:54.259 --> 00:16:58.649
Do you use the same tools in product security as you do in application security?
00:16:59.028 --> 00:17:00.479
Or are there other tools?
00:17:00.489 --> 00:17:12.608
I can't, like the way we approached it when I was in product security, we didn't do anything differently than, you could have called us, you could have swapped out AppSec for product security in the core set of services that we delivered.
00:17:12.969 --> 00:17:13.229
Right.
00:17:13.239 --> 00:17:14.778
In our secure development life cycle.
00:17:15.648 --> 00:17:18.759
If you, uh, if you introduce hardware, there's a difference, I
00:17:19.028 --> 00:17:24.509
that's, that, I was, yeah, that is where things got different or, or there were additional things that had to be considered.
00:17:24.759 --> 00:17:31.618
I mean, we were dealing with, um, Root of Trust and I can't remember what the, what's the thing called?
00:17:31.618 --> 00:17:37.858
The Hardware, um, Trusted TPM, the Trusted, yeah, TPMs.
00:17:38.098 --> 00:17:38.368
Like,
00:17:38.519 --> 00:17:45.048
So applications don't generally deal with TPMs because that's all virtualized or, or, you know, abstracted away from the application developer.
00:17:45.638 --> 00:17:50.679
But when you're delivering a product that has physical components, you obviously need to understand that.
00:17:50.903 --> 00:17:55.409
concepts
00:17:55.528 --> 00:17:55.999
there...
00:17:57.709 --> 00:18:00.368
Is there a product security industry and I'm just not aware of it?
00:18:00.759 --> 00:18:03.898
Are there tools that are targeting the product security industry?
00:18:04.328 --> 00:18:06.519
Or is this like a dead end?
00:18:06.999 --> 00:18:10.318
Well, so I, I think it, I think there, it is.
00:18:11.124 --> 00:18:20.824
There is, but not by that name, there are security tools targeted at product developers
00:18:21.308 --> 00:18:21.648
Okay,
00:18:22.413 --> 00:18:25.013
as opposed to security teams.
00:18:25.953 --> 00:18:31.483
So I think, uh, obviously we're going to debate here a little bit, but, right?
00:18:32.618 --> 00:18:50.719
We, as I mentioned earlier, we, we, the, a lot of the tools are dual purpose or rather have, you know, they have no specific purpose other than looking at software, you know, looking at web applications or looking at third party components in, you know, inventories or, or now analyzing for vulnerabilities or code analysis.
00:18:50.729 --> 00:18:55.398
All these tools will work whether you're doing application development or firmware development.
00:18:57.429 --> 00:18:58.578
So in terms of.
00:19:00.449 --> 00:19:27.489
And I guess, I guess this is the, I guess maybe this is the interesting part about why people see product security as new, even though it's not new, is product security was very much, I think, has always been and really is associated with, uh, I consider myself part of, or more closely related to an engineering or engineering function than a security function, especially if you look at security being IT
security or cybersecurity versus product engineering.
00:19:28.044 --> 00:19:29.564
Adding security to product engineering.
00:19:29.564 --> 00:19:32.183
And in fact, that's, I mean, that's a lot of how we approach things, right?
00:19:32.183 --> 00:19:34.403
Is we want to focus threat modeling at developers.
00:19:34.403 --> 00:19:42.003
Well, that's product, that's developers doing product work, adding security into their role, into their day to day lives.
00:19:42.403 --> 00:19:44.564
Uh, for, as an example.
00:19:44.574 --> 00:19:53.134
So, I think there has always been a strong engineering tool focus with security and AppSec.
00:19:53.839 --> 00:19:54.537
Good
00:19:54.959 --> 00:19:59.769
at security, at security teams doing application security.
00:20:00.419 --> 00:20:02.479
By and large, I think many of the tools are going to be the same though.
00:20:02.969 --> 00:20:14.769
Again, unless we're talking about hardware, you know, if we're looking at ChipSec or any of the glitching tools or things like that, most IT teams probably don't have a purpose for that unless they're attacking network switches.
00:20:15.519 --> 00:20:20.328
Um, whereas, you know, product developers have a need for that and maybe even a dual purpose need.
00:20:20.753 --> 00:20:26.334
You know, logic analyzers can, can look at hardware, not, not just from a security standpoint.
00:20:26.344 --> 00:20:30.513
They also may use it for quality and support purposes and test engineering and whatnot.
00:20:30.993 --> 00:20:33.223
And so I think that it's maybe it's been always there.
00:20:33.743 --> 00:20:46.973
Um, or it's always been available without maybe that label on it, which is actually starting to open up my mind as to why there's a, this, this thought that it's, that's a new thing, even though it's not really new.
00:20:49.523 --> 00:20:50.094
Izar, I know.
00:20:50.094 --> 00:20:50.564
you're.
00:20:51.338 --> 00:20:51.669
I don't know.
00:20:51.669 --> 00:20:55.088
The, the, the more we, yeah, the, the more we talk about it.
00:20:55.088 --> 00:20:59.588
I'm, I'm asking myself if this is not one of those cases of, uh, Uh, what's it?
00:20:59.588 --> 00:21:00.858
A difference without a distinction?
00:21:01.298 --> 00:21:02.878
Or a distinction without a difference?
00:21:04.128 --> 00:21:31.453
Because, yeah, I, I agree that the tooling and the processes are probably similar, but again, that Venn diagram, the, the part of it, of AppSec that, that slips out of ProdSec to me is so small, so, so edge case that I ask myself if it's not just Too much of an edge case to actually say these things are different.
00:21:32.574 --> 00:21:45.794
Or on the other hand, you could put on top of prod security, a number of things, people and processes that really don't belong in AppSec,
00:21:46.118 --> 00:21:47.449
Let me give you another example.
00:21:48.239 --> 00:21:49.229
Let me give you another example.
00:21:49.229 --> 00:21:54.388
that I think could be, could be an ill,
could be illustrative for us.
00:21:54.519 --> 00:21:55.898
I like how I worked that word in there.
00:21:56.209 --> 00:21:57.628
Illustrative, that's a big word.
00:21:58.489 --> 00:22:01.259
PSIRT, Product Security Incident Response Team.
00:22:02.199 --> 00:22:02.338
We
00:22:02.388 --> 00:22:03.469
Versus CSIRT.
00:22:03.749 --> 00:22:12.368
CSIRT, but now see, now there's another, see, for me, CSIRT defends the network, PSIRT defends the products that we build.
00:22:13.378 --> 00:22:13.669
Yep.
00:22:13.979 --> 00:22:17.868
That's, again, so, but in AppSec, we don't have a PSIRT.
00:22:17.888 --> 00:22:18.919
There is no such thing.
00:22:18.929 --> 00:22:23.669
Have you asked a, someone in AppSec, the AppSec program leaders?
00:22:24.439 --> 00:22:27.048
Uh, who, who runs your PSIRT?
00:22:27.189 --> 00:22:30.499
Most times a director of AppSec does not have a PSIRT function.
00:22:31.358 --> 00:22:37.628
So is this something that we can unlock that is a difference between AppSec and ProdSec?
00:22:39.763 --> 00:22:43.104
Again, I don't think that it's a matter of a difference, I think that it's complementary.
00:22:43.263 --> 00:22:55.344
If we already agreed, and I think we agreed, correct me if I'm wrong, that AppSec is part of ProdSec, then that would just be another bubble on the side of AppSec, just as you
00:22:55.368 --> 00:22:57.189
going to, I'm going to, flip it back on you the other way.
00:22:57.229 --> 00:23:05.558
ProdSec is a part of AppSec because AppSec is, when you think about the, I'm just talking about from a public perception, like you ask 10 people.
00:23:06.634 --> 00:23:11.084
What AppSec is and what ProdSec is that probably nobody can probably give a great definition.
00:23:11.324 --> 00:23:12.344
But AppSec is
00:23:12.364 --> 00:23:14.503
who should know, or just any 10 people.
00:23:14.854 --> 00:23:18.413
any 10 people, I'm just gonna go to the Walmart here in my town and ask people.
00:23:18.763 --> 00:23:19.104
But,
00:23:19.578 --> 00:23:21.659
And by the way, sorry, sorry to interrupt, Chris.
00:23:21.709 --> 00:23:23.878
By the way, I, we've had these conversations.
00:23:23.898 --> 00:23:28.669
I don't mean just the three of us, but other folks in the security space have had these conversations.
00:23:28.699 --> 00:23:30.558
I've been part of, of some of these.
00:23:32.038 --> 00:23:36.878
None of us have a good understanding, I think, even within the security space of what this stuff means, right?
00:23:36.919 --> 00:23:38.159
Are we cybersecurity?
00:23:38.169 --> 00:23:39.108
Are we InfoSec?
00:23:39.108 --> 00:23:40.028
Are we AppSec?
00:23:40.028 --> 00:23:40.808
Are we ProdSec?
00:23:41.364 --> 00:23:43.314
We are too busy securing stuff.
00:23:43.314 --> 00:23:43.423
I don't care what's
00:23:44.413 --> 00:23:44.624
ha,
00:23:45.124 --> 00:23:45.933
the color of the t
00:23:46.003 --> 00:23:48.993
me whatever you want, I will just show up and secure your
00:23:49.284 --> 00:23:52.634
But, but I think it's important that the way you're asking the question is interesting.
00:23:52.663 --> 00:24:12.094
And the way that we're responding, I think is, is doubly, uh, not adding, maybe not clearing up the confusion for folks if they're listening to this now, um, you know, the, the processes that a PSIRT or that a CSIRT follow are probably 90 percent the same.
00:24:13.284 --> 00:24:14.104
Where it gets...
00:24:14.679 --> 00:24:22.489
Where you have differences, again, is PSIRT deals with, potentially deals with hardware, right, because you have physical devices.
00:24:23.019 --> 00:24:31.519
Although, CSIRT may deal with physical devices in terms of network infrastructure, especially, you know, access points, but also other things.
00:24:32.088 --> 00:24:33.519
People security, potentially.
00:24:35.219 --> 00:24:45.298
And so you have, you have a Venn diagram of a lot of overlap and then some, some pieces outside of each of them that are unique, I think So there's a lot of overlap.
00:24:45.584 --> 00:24:47.874
making it, I don't think it's 90 percent the same.
00:24:48.314 --> 00:24:51.003
I think it might be 50, 50, 50 percent the same.
00:24:51.453 --> 00:24:53.584
And I've, I mean, I've, I've had a chance to work.
00:24:53.584 --> 00:24:58.354
I didn't work for PSIRT at Cisco, but I worked closely beside a lot of people from PSIRT.
00:24:58.763 --> 00:25:08.179
And, um, you know, having done incident response in the past, like, And like I said, CSIRT is about the network, PSIRT is about the product.
00:25:08.538 --> 00:25:19.048
Yes, there's going to be some overlap, but that focus really changes the core of what you're doing as an incident response team.
00:25:19.308 --> 00:25:19.558
Right?
00:25:19.558 --> 00:25:25.368
Because the PSIRT team is responsible for most of the time being notified about a problem.
00:25:26.088 --> 00:25:39.679
Out from an inbound source, going to the product team, testing, helping the product team through the process of fixing the issue, and then running the communication process to ensure we tell the people at the right time.
00:25:39.919 --> 00:25:45.298
Now, when I think about CSIRT, CSIRT is, um, has no real outbound.
00:25:45.848 --> 00:25:50.259
They don't report to the, to the public as far as what happened, what's happening, what they're doing.
00:25:50.648 --> 00:25:53.439
They may, they may receive an inbound.
00:25:53.618 --> 00:25:57.148
If they get an inbound notification, then things are really bad.
00:25:57.269 --> 00:25:57.499
Like
00:25:57.628 --> 00:26:00.398
Well, or, well, or they're running a bug or they're running a bug bounty.
00:26:01.578 --> 00:26:02.028
bounties
00:26:02.074 --> 00:26:04.094
Yeah, that's exactly what I was going to ask.
00:26:04.138 --> 00:26:07.479
bug bounties is another, but CSIRTs don't run bug bounties, right?
00:26:07.528 --> 00:26:07.949
Like,
00:26:08.483 --> 00:26:08.943
No, no, no.
00:26:08.993 --> 00:26:09.854
SIRTs don't run
00:26:09.854 --> 00:26:11.939
product, is a product related thing.
00:26:13.473 --> 00:26:14.023
Exactly.
00:26:14.144 --> 00:26:15.703
So, let's look at that for a second.
00:26:16.653 --> 00:26:18.193
Products run bug bounties.
00:26:18.743 --> 00:26:21.983
Applications, sort of not.
00:26:22.723 --> 00:26:23.723
Oh, they run bug bounties.
00:26:23.983 --> 00:26:24.884
Can we agree with that?
00:26:25.683 --> 00:26:33.324
lots of application providers run, lots of SAST tools, and like people that are building applications, they're running, everybody's running bug bounties these days.
00:26:34.013 --> 00:26:35.243
So, those are not products?
00:26:36.574 --> 00:26:37.763
I mean, they are products.
00:26:38.538 --> 00:26:38.898
Oh
00:26:39.153 --> 00:26:40.644
to Matt's definition, that we're selling.
00:26:41.824 --> 00:26:43.334
If you're selling them, it's a product.
00:26:45.134 --> 00:26:45.743
If I'm a
00:26:45.939 --> 00:26:46.148
them,
00:26:46.199 --> 00:26:51.433
SAST tool provider, And my tool just happens to be SAST.
00:26:52.074 --> 00:26:53.013
I'm selling you something.
00:26:53.013 --> 00:26:53.834
I'm giving you a service.
00:26:53.834 --> 00:26:54.673
You're giving me money.
00:26:56.114 --> 00:26:57.604
How is that not a product?
00:26:58.203 --> 00:26:59.013
No, I'm saying it is.
00:26:59.013 --> 00:26:59.874
I'm agreeing it is.
00:26:59.903 --> 00:27:01.753
Because there's money being, changing hands.
00:27:01.963 --> 00:27:03.144
But it's also an application.
00:27:03.144 --> 00:27:03.713
It's both.
00:27:05.874 --> 00:27:09.644
It's a product that's made of an application, which we agreed already.
00:27:10.038 --> 00:27:12.068
it's a product made up of an application.
00:27:12.808 --> 00:27:18.548
Products that have hardware, right, but products that have hardware also have applications as building blocks.
00:27:19.189 --> 00:27:20.138
So are we suggesting
00:27:20.163 --> 00:27:21.453
you the truth, I don't see the,
00:27:22.308 --> 00:27:24.118
is product security the superset?
00:27:24.699 --> 00:27:26.739
Because it includes applications and other things?
00:27:27.483 --> 00:27:29.703
I don't see the hardware as such a differentiator here.
00:27:30.729 --> 00:27:33.578
If I think about something that I'm selling
00:27:33.669 --> 00:27:34.848
not dealt with hardware before?
00:27:36.469 --> 00:27:45.769
yeah, but you know, it's, it's like it has some stuff that's different, but there isn't enough stuff in there to put in a class by its own.
00:27:47.753 --> 00:27:49.963
know a bunch of hardware engineers would say otherwise.
00:27:50.074 --> 00:27:50.644
I do too.
00:27:51.648 --> 00:27:57.128
Dude, I, I, I know a lot of people who think that what they do is the most important thing in the world we included, so,
00:27:57.364 --> 00:27:59.874
Well, okay, so hold on, so hold on, so hold on.
00:28:00.003 --> 00:28:04.273
Let's talk about, let's talk about the, let's talk about the real elephant in the room on that.
00:28:04.294 --> 00:28:06.574
That's the difference between hardware and non hardware.
00:28:07.223 --> 00:28:12.644
You actually have to build something and ship them somewhere so you have all the supply chain stuff that you have to
00:28:12.703 --> 00:28:13.993
that, but that doesn't
00:28:13.993 --> 00:28:15.963
I deployed through CICD and it's present.
00:28:17.074 --> 00:28:18.673
Okay, let me give you an example, okay?
00:28:19.104 --> 00:28:21.584
I have this amazing thing here on my wrist.
00:28:22.334 --> 00:28:24.173
Yeah, it's a product.
00:28:24.263 --> 00:28:26.253
and a product.
00:28:26.433 --> 00:28:29.663
And they decided, it's a hardware product, great, great.
00:28:29.683 --> 00:28:32.153
And it runs a specific version of an operating system.
00:28:32.534 --> 00:28:33.314
Yeah, same here.
00:28:33.413 --> 00:28:37.114
now they decided, no, now they decided that they're not going to give me more upgrades.
00:28:37.604 --> 00:28:42.564
And half of the functionality is dying because Google on the other side decided that I have to have the newest version
00:28:42.894 --> 00:28:43.223
Oh, sure.
00:28:43.253 --> 00:28:43.923
No names, huh?
00:28:43.953 --> 00:28:44.304
to run.
00:28:44.884 --> 00:28:49.663
Okay, now note that Google, the Google app, app ecosystem is a completely different word.
00:28:50.044 --> 00:28:51.844
You just know now that it's an Android thing.
00:28:51.844 --> 00:28:52.773
It's not an Apple thing.
00:28:52.804 --> 00:28:54.523
So, but that you knew from the shape.
00:28:55.044 --> 00:29:01.854
But anyway, so my point is, if I can remember it is, okay, this, this thing is hardware.
00:29:01.903 --> 00:29:02.213
Great.
00:29:02.213 --> 00:29:05.023
So according to your definition, it makes it more of a product.
00:29:06.108 --> 00:29:06.659
But you know what?
00:29:06.669 --> 00:29:08.959
It could not be hardware.
00:29:08.989 --> 00:29:14.848
It could be an app that lives in my Windows machine, as if I had one.
00:29:15.384 --> 00:29:15.834
That would
00:29:16.098 --> 00:29:16.838
No, not sure.
00:29:16.838 --> 00:29:17.548
I have one.
00:29:17.558 --> 00:29:18.398
It's my game box.
00:29:18.778 --> 00:29:24.108
Anyway, so it's running into a Windows machine, and what all it does is run exactly the same apps.
00:29:24.719 --> 00:29:27.729
Is that thing less of a product just because it doesn't live in a
00:29:28.574 --> 00:29:29.834
I'm not saying it's less,
00:29:29.933 --> 00:29:30.653
doesn't have hardware
00:29:31.054 --> 00:29:32.044
well, I'm not
00:29:32.084 --> 00:29:32.794
it on your wrist.
00:29:32.814 --> 00:29:32.983
That
00:29:33.003 --> 00:29:34.284
I'm not saying it's less of a product.
00:29:35.074 --> 00:29:36.344
I'm not saying it's less of a product.
00:29:36.584 --> 00:29:38.894
I'm saying that it's a different product.
00:29:38.913 --> 00:29:42.604
It's a product that has different, it's a product that has different aspects.
00:29:42.834 --> 00:29:43.473
Software.
00:29:43.864 --> 00:29:48.433
alone has different criteria
for security than hardware and software.
00:29:48.778 --> 00:29:49.949
Okay, okay, okay, okay, okay.
00:29:50.449 --> 00:29:54.739
Another example, you have this firewall box, wonderful firewall box, right?
00:29:54.759 --> 00:29:59.909
You can get it as a 1U, you stick it in your, in your stack, everything is beautiful and great.
00:30:00.719 --> 00:30:09.318
It just so happens that you can also get exactly the same functionality in the form of a virtual machine that you stick in your network, okay?
00:30:09.759 --> 00:30:11.709
on a virtual machine, on a VM server
00:30:11.759 --> 00:30:12.989
On a virtual machine, yeah,
00:30:13.048 --> 00:30:13.798
that you deploy?
00:30:14.548 --> 00:30:15.058
Yeah, yeah.
00:30:15.749 --> 00:30:18.263
Is one of them less of a product than the other?
00:30:18.959 --> 00:30:19.719
It's different.
00:30:20.054 --> 00:30:22.663
There's still hardware underneath in the cloud environment.
00:30:22.898 --> 00:30:24.828
yeah, but you're not, but you as,
00:30:25.054 --> 00:30:26.263
I can't do ones and zeros in my
00:30:26.419 --> 00:30:38.558
but as the, but as a supplier of, as a supplier of the product of the supplier, the product, the software only product, you're not governing the heart of the hardware runs, nor do you necessarily care how the hardware runs.
00:30:38.973 --> 00:30:41.493
But does that make my product less of a product?
00:30:42.308 --> 00:30:46.368
Oh my god, we're not talking about making it less of a product! We're
00:30:46.394 --> 00:30:46.753
Then why are
00:30:46.864 --> 00:30:47.763
caress about pro,
00:30:47.933 --> 00:30:49.574
why are you sticking to the hardware?
00:30:50.074 --> 00:30:53.403
what is it a one to five scale of how much of a product you are?
00:30:53.403 --> 00:30:54.634
Well, you're about a four.
00:30:54.723 --> 00:30:56.913
I mean, you're, you're almost the, the most
00:30:57.144 --> 00:30:58.923
But if you had hardware,
00:31:00.193 --> 00:31:00.433
Yeah,
00:31:00.608 --> 00:31:10.969
mean, if we really want to go that route, we could talk about wireless sensor networks that, you know, run, you know, environments, you know, smart fields and things where you have thousands of wireless devices out in the field talking to it.
00:31:11.459 --> 00:31:13.989
EdgeGateway, how much of a product is that?
00:31:14.193 --> 00:31:17.773
My primary question is why am I more confused now than when we started this
00:31:17.814 --> 00:31:19.183
I'm totally confused.
00:31:19.183 --> 00:31:20.473
I have no idea where I went.
00:31:20.614 --> 00:31:24.344
I've got to go read the articles again and try to see if I can find some wisdom
00:31:24.374 --> 00:31:25.124
no, no, seriously.
00:31:25.193 --> 00:31:26.203
Let's bring it back then.
00:31:26.243 --> 00:31:26.784
Let's bring it back.
00:31:26.963 --> 00:31:27.953
We're almost at time.
00:31:27.953 --> 00:31:28.804
So let's bring it back.
00:31:29.193 --> 00:31:31.673
Okay, so, who...
00:31:33.088 --> 00:31:33.989
Contains whom?
00:31:37.159 --> 00:31:40.969
I'm going to go with product security includes application security.
00:31:41.778 --> 00:31:42.269
Great.
00:31:42.409 --> 00:31:42.749
Okay.
00:31:43.134 --> 00:31:43.473
Hold on.
00:31:43.544 --> 00:31:44.963
I'm going to go on the, I'm on the other side.
00:31:45.249 --> 00:31:47.338
in part, and I have to say in
00:31:47.338 --> 00:31:47.868
to go there.
00:31:48.078 --> 00:31:48.348
Now we
00:31:48.449 --> 00:32:00.449
have to say in part, we do need to, we have to have, we have to further this conversation somewhere, but product security has parts that, actually, let me, let me take a really brief step back.
00:32:02.138 --> 00:32:12.743
If we look at product, if we look at application security, securing applications, and we've defined web applications and desktop software and mobile applications as applications.
00:32:13.763 --> 00:32:18.074
And those can be part of the things that you sell, like that watch that you were showing earlier.
00:32:19.084 --> 00:32:21.923
Then products must contain applications.
00:32:21.983 --> 00:32:24.344
Product security must contain application security.
00:32:24.824 --> 00:32:28.773
However, applications can be on their own and not be part of products.
00:32:31.429 --> 00:32:35.409
Yes, but then, but then that application becomes a product.
00:32:35.953 --> 00:32:36.153
Yeah.
00:32:36.153 --> 00:32:40.673
And I'm going to, I'm going to come at this from a different direction and I'm just going to go purely based on market share.
00:32:41.634 --> 00:32:45.963
And I'm going to say application security eats product security.
00:32:46.544 --> 00:32:50.104
Just because application security is the thing that exists in the market.
00:32:50.354 --> 00:32:51.144
There isn't a product.
00:32:51.153 --> 00:32:53.054
I mean, that was a, that was a trick question.
00:32:53.054 --> 00:32:54.594
There is no product security space.
00:32:55.114 --> 00:33:02.723
There is no, it is, there is an AppSec space of products that are built, that are used in, in product security programs.
00:33:03.213 --> 00:33:07.753
Um, but there is, I mean, there is not a, there is a...
00:33:08.409 --> 00:33:12.959
appSec is really what everybody refers to what all of us do at this point.
00:33:12.969 --> 00:33:18.358
I mean, for example, hold on, I have to go check, um, on the open worldwide product security.
00:33:19.429 --> 00:33:21.088
Program, uh, website.
00:33:21.578 --> 00:33:28.739
The OWP, no wait, there is no OWP, there's no OWPSP.
00:33:29.229 --> 00:33:30.449
There is, is that right?
00:33:31.229 --> 00:33:31.548
Okay.
00:33:31.818 --> 00:33:35.749
There is OWASP, which is the Open Worldwide Application Security Project.
00:33:35.749 --> 00:33:41.064
Uh, what was it called before they had a name change to try and bring a bigger tent?
00:33:41.148 --> 00:33:42.409
it's just web applications,
00:33:42.419 --> 00:33:43.308
Web application.
00:33:43.308 --> 00:33:43.719
Yes.
00:33:43.858 --> 00:33:46.689
point is, application security is at the core of that.
00:33:47.098 --> 00:33:49.648
And, I mean, at the end of the day, I don't really care what we call it.
00:33:49.669 --> 00:33:52.759
We're still going to do the right things to secure the hardware.
00:33:53.038 --> 00:33:57.128
and the software that, that go into products and applications both.
00:33:57.409 --> 00:34:02.499
My point is I think AppSec has just become, it's just the same way AppSec replaced SoftwareSec.
00:34:02.989 --> 00:34:13.018
We used to call software security, was used to be the thing, and then AppSec kind of took it away and squashed it, and now people, nobody really uses software security anymore.
00:34:13.048 --> 00:34:17.818
We don't really, we don't really say that or use it as a term as much as we used to 10 years ago.
00:34:18.259 --> 00:34:20.338
That's an interesting, that's an interesting statement.
00:34:20.369 --> 00:34:21.539
I agree with you.
00:34:22.199 --> 00:34:26.969
It's interesting because maybe that's where the problem lies, right?
00:34:27.079 --> 00:34:32.489
That within product security, you have software and you do software security of products...
00:34:32.958 --> 00:34:34.458
Or you do software security...
00:34:34.668 --> 00:34:37.309
Products that are either software or that contain software.
00:34:37.509 --> 00:34:38.688
You do software security.
00:34:39.353 --> 00:34:43.043
Applications can be something different then, right?
00:34:43.043 --> 00:34:47.753
But that, that's, those terms are now sort of munched together, as you, as you described.
00:34:47.849 --> 00:34:50.728
I'm just approaching it from how the industry sees it, like how...
00:34:51.903 --> 00:34:53.643
The external view of this.
00:34:54.568 --> 00:35:03.168
But now, now, just to put it in there, um, as you guys were, were talking, I was looking into the inside tomes of wisdom and experience.
00:35:03.639 --> 00:35:06.728
And I remember one place where it worked, where.
00:35:07.498 --> 00:35:10.679
There was a distinction between product security and application security.
00:35:11.389 --> 00:35:16.398
And the distinction was that prod security could stop releases, application security couldn't.
00:35:17.809 --> 00:35:30.389
Because prod security was much more enmeshed with the product side of the thing with the, we have to push stuff out because we have consumers waiting for and paying for stuff than AppSec.
00:35:31.568 --> 00:35:34.639
So the escalation of risk was AppSec, ProdSec.
00:35:34.699 --> 00:35:37.309
ProdSec makes a decision, go, no go.
00:35:38.423 --> 00:35:39.034
Interesting.
00:35:39.893 --> 00:35:52.023
The, the other aspect, and I know we're getting close to the end of this episode, but the, the other aspect is, would you consider, if you, if AppSec, is AppSec closely tied to cyber or IT security?
00:35:53.173 --> 00:35:56.043
And if so, are products, is product security,
00:35:56.054 --> 00:35:57.574
you're not gonna take us there, are ya?
00:35:57.588 --> 00:35:59.139
I, I, you have to.
00:36:00.518 --> 00:36:00.708
can
00:36:00.728 --> 00:36:01.048
not
00:36:01.048 --> 00:36:02.739
go with asterisk security?
00:36:04.309 --> 00:36:05.548
well, they're just security then.
00:36:05.559 --> 00:36:06.068
That's awesome.
00:36:06.108 --> 00:36:06.628
We can do that.
00:36:06.728 --> 00:36:07.168
Asterisk.
00:36:07.168 --> 00:36:10.719
Can we just go asterisk security and that's what we do?
00:36:10.914 --> 00:36:11.094
with it.
00:36:11.094 --> 00:36:11.824
Well, you know what?
00:36:11.884 --> 00:36:12.653
We're out of time.
00:36:13.074 --> 00:36:15.083
So we're gonna have to come back and revisit this again.
00:36:15.554 --> 00:36:18.494
Um, we were hoping for some clarity by the end.
00:36:18.514 --> 00:36:22.313
I think we just, we just threw some more mud in the water and stirred it up.
00:36:22.313 --> 00:36:26.443
And, um, made some, some security soup.
00:36:26.623 --> 00:36:28.023
I think is what we did at the end of the day.
00:36:28.023 --> 00:36:29.653
But we'll continue this conversation.
00:36:29.653 --> 00:36:31.653
We'll find, uh, we'll try to find clarity.
00:36:32.043 --> 00:36:32.943
That'll be our goal
00:36:33.248 --> 00:36:35.949
and maybe we'll get some guests on to, uh, to help us answer
00:36:36.018 --> 00:36:38.418
Yeah, perhaps we can bring someone who,
00:36:38.994 --> 00:36:41.264
Smarter than us that can come and just tell us what it is.
00:36:41.273 --> 00:36:42.173
That's what we're going to aim for.
00:36:42.289 --> 00:36:43.768
Yep, that would help.
00:36:43.768 --> 00:36:45.563
We'll debate, you know, we'll debate with them.
00:36:45.704 --> 00:36:48.623
No matter who we bring on, we're going to debate with them about what it means.
00:36:48.623 --> 00:36:51.193
But folks, thanks for listening to The Security Table.
00:36:51.204 --> 00:36:55.204
Stay tuned for a future episode where we will provide clarity.