51 min

Application Security, Product Security, and what do we call this thing we do

With Chris Romeo, Izar Tarandach, and Matt Coles

Security strategy, risk & industry trends

The gang is back to debate and discuss the definition of application security. We start by figuring out what an application is and then layer security on top of it.

Episode title image: Application Security, Product Security, and what do we call this thing we do

Listen to the conversation

About this episode

The gang is back to debate and discuss the definition of application security. We start by figuring out what an application is and then layer security on top of it. We branched into how product security fits against application security and eventually concluded that system security is all-encompassing, but it's an old term. We also learn that Izar is uncomfortable speaking about cybersecurity at cocktail parties. Enjoy!

Follow AI Security Table:

➜ Home: https://securitytable.ai/

➜ X: https://x.com/AISecurityTable

➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/

➜ YouTube: https://www.youtube.com/@AISecurityTable

Transcript · 51 min conversation

0:00Chris Romeo Hey folks, welcome to another meeting of the minds around the security table. This is Chris Romeo. I'm also joined by Izar Tarandash, Matt Coles, Tanya Ward, and we're going to pick right up where we left off at the end of the last episode. Last episode, we were talking about acronyms and abbreviations and all the different things that we use in the world of security. And towards the end of that conversation, we started talking about what is application security. And after 15 minutes of scratching our heads, we really didn't reach any conclusions there. And so in this conversation, I want to define application security as a starting point because it is such a big part of the world now. We should really have a good idea what it means. So let's see. I'm looking to see who's looking away from me in the— oh, everybody is. Wow. Nobody wants to define application security. Okay, well, thanks for joining the Security Table. And look forward to another— no, I'm just kidding.

1:00Izar Tarandach There's the security under the table episode. Nobody wants to go there.

1:04Chris Romeo Yeah, that'll be our, you know, our, the CD under the table in the next special episode. Yeah. But so who's got a definition? Tanya, when you hear application security, what, how would you define it?

1:18Tanya Ward Right now, firmware security, application security, hardware security. I mean, In its grandest theme, I would imagine application is anything to do with web-based applications that are deployed potentially on your own infrastructure. But then it gets a bit confusing because then cybersecurity is kind of popping up in there. And then there's— actually, to be honest, I feel like it's almost next to impossible to have— a consistent definition that everyone would agree with?

1:55Matt Coles So let me take a crack at this, if I may. So I'm gonna refer to, actually I found a good article that I can refer to here from VMware, the folks at VMware who do some work in this space, have defined application security as the process of developing, adding, adding, and testing security features within applications. To prevent security vulnerabilities. Well, that's great. Except for now we have to define what an application is. So, so what is an application? Well, if we, in another article, I was looking at not from VMware, but from somebody else talking about application being that layer 7 thing. So something that operates at layer 7.

2:41Chris Romeo Yikes.

2:42Matt Coles Not necessarily strictly web, but obviously web applications fit there. And I guess they're in the name already, web applications. Things that process at that level, if we consider those things applications, then application security is dealing with those things. So we're talking about business systems, we're talking about software, we're talking about control dashboards and whatnot that expose information or bells and whistles or knobs.

3:10Chris Romeo Isn't that kind of a circular— It's a circular reference though to say that like an application is anything that's at layer 7. Which is called application. It's like, it's, it's like, it doesn't— it's something, it's, it's a circular reference. It doesn't, it doesn't really define it to say it's layer. Listen, I'm just a pundit here. I'm just, I'm just here to attack what everybody else said. I'm not here for original thought.

3:34Izar Tarandach I have a better idea.

3:36Chris Romeo Okay, so, okay, this is gonna—

3:42Izar Tarandach what is not an application?

3:44Chris Romeo There you go.

3:48Izar Tarandach The way that Matt started going in, and that I think Tanya was going in, was that an application should have some form of interface with a user, with people, with something. But then, is a server an application? Is a daemon an application? They live by themselves and they do their stuff, but they do get input sometimes. So, are those applications or not? So yeah, I would say that an application is probably something that runs by itself, gets input, processes it, and has some kind of output. And the reason why I say it works by itself is just to, for example, separate it from a library.

4:39Matt Coles Right?

4:42Tanya Ward Hello? So I just did a search, and I'm— good if you could find other definitions. So if we're talking about what the definition of an application is, what I find is a computer program designed to carry out a specific task other than one relating to the operation of the computer itself, typically to be Used by end users, word processors, media players, and accounting software examples. I don't know if I necessarily agree with that.

5:09Izar Tarandach It's too high level.

5:10Tanya Ward Yeah. No, they're desktop applications.

5:14Chris Romeo Yeah. Yeah, the first part of that definition sounded pretty good. I think it started to kind of fall off. It started to sound like a '90s definition when you get to like, oh, word processors and, you know. But they're not the focus. Like when I think of, like how much time have you spent securing your word processor in your—

5:35Matt Coles Why not? If people—

5:40Chris Romeo Notepad always seems like to be one of the— No, that's Calculate. Sorry, that's the thing that everybody always pops. Yeah. Yeah. So, yeah. Okay. So, I mean, I like— if we put these things together, I like where Uzair was going because I think the most basic definition is a pro— and maybe if we put these two things together, a program that isn't an operating service that takes some input and provides some output. And does some basic— and does some processing. Takes some input, does some processing, and provides some output. It's a pretty basic definition. Now, does anybody want to argue against that as an application?

6:25Tanya Ward I would then say, where does product fit into that? Because some people would classify sub-applications as being potential products.

6:33Matt Coles So I wanna, I wanna address that. I think products are, is a word for product security is a domain that encompasses application security, but encompasses other things as well. You mentioned it earlier around firmware and hardware and the operating system and other aspects. For things that are called products. Now, my definition of product are things we generally sell or make available to individuals or organizations or for use outside of the team or the org or the company that's building them. So for instance, if you're building a mobile application that you're going to deliver into an app store and people can download it, pay $0.99, that could be considered a product. It's an application. But it's also a product, things that you sell. I think that word product has become, has been used more generically for anything that you build and then make available to others, but that may be within your organization. So if you build a business application as an IT group, your product to the rest of the org is that business application. I don't know that that's true, what I would consider product, but that's up for debate, I suppose. But the product is the collection of things that make up that product.

7:53Chris Romeo So product sits above.

7:54Matt Coles That's it.

7:54Chris Romeo Product sits above application.

7:55Matt Coles Where an application may be a product.

7:56Izar Tarandach Just to reinforce.

7:59Chris Romeo A grouping of things that provide a service.

8:02Matt Coles It's a grouping of.

8:03Izar Tarandach Just to reinforce what Matthew said. Usually when you go in front of a VC with an idea and an MVP or something, you are showing something that's close to an application. It's, it's an app, it's, it's a service, but it's something that does something. And then the next question that I have is, okay, but how do you turn that into a product? So yeah, you, you do have the idea that the product is the envelope that takes that functionality and turns it into something that you can commercialize, right? But I would go back and say that in order to be able to commercialize that, then you need a whole set of infrastructure things. How are you going to take money from people? How are you going to serve that reliably? How are you going to all sorts of scaffold things that you have to put around that idea that you have that turn it into an actual thing that you can call a product. So in our terms, I think that, and already jumping ahead on the discussion, the differentiation between AppSec and prod security is that at prod security, we are looking way beyond that unit of processing that takes input and produces output. And we are looking at the things that make it live in the world and integrate with other things and do so reliably and do so in a scalable way. So it's going from your cloud provider to the way that you actually let people interact with it.

9:35Matt Coles I would be careful about saying that profits don't have to be things that—

9:38Izar Tarandach Zero money is due money.

9:43Tanya Ward Why do we care? Like, why do we care what the— like, let's kind of back up. Why do we actually care what the definition is? I mean, security regardless of where it is, like, and this is what I'm trying to think about in terms of what you're saying. We have this concept of what application is. Okay, you may have many applications in a product or whatever it may be. Security evolves and changes, I guess, based on these different stacks as you kind of talk about it, right? Like when you think about how you secure an application, there's going to be some level of foundations there, but all those things that go into a product becomes a lot more complex. So, I don't know. I'm still like, why do we care? About the definition?

10:30Matt Coles I think we care.

10:33Chris Romeo Okay.

10:34Matt Coles The scope, but there's also capability. And I say capability for the people who are responsible for the care and feeding of that thing and the security of it, right? There's a particular— I think we find in general that between cybersecurity and product security, that the things that we need to worry about differ, right? So if you're deploying something internally, you have certain aspects. You may be within a defined infrastructure environment that has certain capabilities. And so you're going to take that application and integrate it with, you know, your SIEM and your auth provider and your secret provider and et cetera. And it's— and you want it to all fit within that ecosystem. Whereas on the product side, it's generally something that somebody else is going to consume, somebody else is potentially going to manage, and therefore you need to design and implement it in a different way. It needs to be pluggable and maintainable and upgradable, or it needs to be able to fit within something else and not within your defined environment. And so I think that while it's all security, Some of the implications differ based on those two aspects.

11:52Chris Romeo I wanna come back around to, so you said a product is something that, it could be something that's free and it could be something that's for money. What's like, what do you think of as a product that's free? Is that a product though?

12:12Matt Coles Is that a product? Anything delivered as open source on GitHub.

12:15Chris Romeo I don't know.

12:16Izar Tarandach I think that it's, it's a Lego block that can be made into a product, but it lacks exactly all that scaffolding that we talked about. So it's a potential product.

12:26Chris Romeo Yeah, I'm struggling to think of a product that doesn't exist to make money.

12:32Matt Coles Well, uh, just be careful of doesn't exist to make money versus is made available for free, right? So open, you can have open source hardware and open source software that can be combined together. Maybe the product is a reference implementation, right? You may not make any money off of it and you may provide it as an offering to consumers.

13:07Tanya Ward I actually I agree with Chris. I don't know any product out there. You may get a free product, but there may be a subscription associated with it to upsell into something. I would challenge us to think, is there any—

13:20Izar Tarandach Mastodon?

13:21Tanya Ward Is there actually, to your point, Chris, is there anything free out there? Because you have to pay for people to do this work.

13:31Matt Coles Yeah, ad revenue. I mean, if you're going to do that, then anything that's supported by ads. Could be potentially—

13:36Chris Romeo I mean, I was thinking like social media, like Facebook for example. Facebook is technically free but is it really? No, no, no, no, no, not because they're selling my views of ads and everything. Right? Like so yes. Okay. I'm the product in that one.

13:59Izar Tarandach So what about Mastodon?

14:01Matt Coles You're the product in Facebook, right?

14:03Chris Romeo Yeah. So there is no way to pay for Mastodon, right? It's an open source.

14:08Izar Tarandach You can donate to those people who maintain and keep nodes. You don't have to, you may, because it's the right thing to do. By the way, donate to your Mastodon node maintainer.

14:22Chris Romeo So is it, is Mastodon a product then? I have no, I have no guarantee. There's no contractual language or anything. Oh, like Oh, oh, oh, but do you need that for a product? I'm, I'm, I'm spitballing here. Like, do, do I, do I need it for a product? That's what I'm, I'm kind of spitballing out loud almost like, is, is it a product or is it just a free service for communication?

14:49Izar Tarandach Wait, wait, wait, wait, wait. Let's go back to definitions. Is a service different from a product? But that I think, yes, because you can't offer a— no, you can. No, you can't. No, no, no, no, no, you can't.

15:11Matt Coles The application talks to a service.

15:14Tanya Ward I've never heard of an application. I've heard of product managers. I don't know if I've ever really heard of an application.

15:21Chris Romeo That'd be more of an ops function. An application manager would be somebody running and scaling the execution of an application.

15:30Tanya Ward So, yeah.

15:33Chris Romeo So, where does this leave us?

15:35Izar Tarandach So, service.

15:36Chris Romeo Yeah.

15:40Matt Coles Well, so, yeah, so I'd like to offer, you know, I have, in my career, I have been always, I always pitch myself as a product security person. Yeah. That, and, and, and I do that to differentiate myself from IT and cybersecurity traditionally. Now those lines are being very much blurred with, you know, cloud containers and, and, you know, these and eco and having an ecosystem that goes from device to cloud and, and, and everything in between. And so it's a lot harder now to say product security. It's amorphous.

16:15Izar Tarandach He's going to say, I know that he's going to say, it's hard to pin down what that means.

16:17Matt Coles It also potentially is very limiting.

16:19Izar Tarandach No. He's going to say we are DevSecOps consultants now.

16:22Matt Coles System security.

16:25Chris Romeo Hey, there's no swearing on this podcast, okay?

16:27Matt Coles Absolutely.

16:28Chris Romeo You cannot use that word. Absolutely not.

16:30Matt Coles That's why I paused. Yeah, absolutely not. So yeah, so system security is, or ecosystem security, it is not a good, not universally recognized, I think, but And it maybe is a cop-out to some extent, but it's hard to say product security nowadays because when I say product security, that gets misinterpreted also sometimes as, well, I'm building a— if you're building a financial application, you know, that you then make available like Fidelity or whoever, they make their platform available to customers. Is that a product? I wouldn't traditionally consider that a product. I would consider an appliance, you know, a piece of hardware that has a software.

17:18Chris Romeo Well, the Fidelity example customers and they deploy in their environment is a product.

17:23Matt Coles I mean, that's a hardware product.

17:25Chris Romeo But to complicate this even more, the Fidelity example you just used, I'm not paying the, the software and the infrastructure is enabling me to use the service. Like what I buy from Fidelity is a, an investment account, a window into being able to take my dollars and turn them into a share of Berkshire Hathaway. It's the applications and the systems support that, but Fidelity is more of a service in the way that I'm buying it. I mean, it's through the systems and applications.

18:02Matt Coles And how do you access that service?

18:06Chris Romeo At least I don't think so. When I open an account at Fidelity, I'm not buying access to their— they're giving me access to their infrastructure in exchange for making a commission on every time I buy a share of Google or whatever. We're all looking more confused than we actually started this conversation.

18:29Matt Coles Are we any closer? Security. Well, then you completely eliminate hardware.

18:47Tanya Ward Well, then you could have hardware security. I mean, it's like taking application, all these other compliance. Well, then you have infrastructure security as well. I just think it's so confusing.

18:56Chris Romeo We need a new term for what we do. We gotta, we gotta come up with a new term.

19:00Tanya Ward It's confusing.

19:01Chris Romeo I mean, it's not AppSec, it's, it's not software security, it's not hardware security, it's not product security. It's all of these things. It's what we do.

19:14Tanya Ward Exactly. But how do we, how do we secure all of those?

19:16Izar Tarandach So say it's all of those things and none, please, please. Can also be, okay, I'll do it. It's not all of those things and none, and none of them.

19:27Chris Romeo Non-security. So I was thinking security unicorn.

19:29Tanya Ward What about non-security?

19:31Chris Romeo As a potential, uh, oh yeah.

19:36Izar Tarandach Yep.

19:37Matt Coles That, that, that, uh, that has connotations though.

19:40Tanya Ward Okay.

19:40Chris Romeo So let's, let's try to come back around to where we started and because we did, we, we really wanted to define application security and product security. That was our goal. We kind of got off on a tangent trying to unravel what those individual terms mean. But I think we came up with a definition for application in that it was a program that takes some type of input, does some type of process, and puts some type of output out. I think Matt gave us a good definition for product security as being, you know, kind of an almost an umbrella of other disciplines of security, but applied to a given product. So let's come back around to, if we put application and security together, Now what are we talking about? Because we kind of started trying to define it and then we went off on what is an application. Let's come back around. So what is application security then?

20:38Izar Tarandach No, no, no, go, go.

20:40Matt Coles Yeah, well, so it's— I think now if we— sorry, sir— if we just— if we, if we now have a definition of what an application is, and by the way, I think we've just decided the application is software primarily, or strictly software.

20:55Tanya Ward Yeah.

20:55Matt Coles That operates at a particular level. Well, security, application security then is securing that thing, right? So securing its data, its function, the things that we know how to talk about because we do threat modeling, we do code analysis, et cetera, right? And so all of the techniques and all of the capabilities and all of the skillset and whatnot that that comes with how do you protect code from being compromised and how to protect data from being exposed.

21:23Izar Tarandach Sorry, Daniel, and that may involve both software disciplines, but at some point in some way, a bit of hardware where things start hitting the wire and getting lower level. Things, for example, okay, would you say the things like, uh, uh, all the, the, the, yeah, side channel attacks with memory and on processor pipelines and all this.

21:51Chris Romeo Well, that's not application security though.

21:53Izar Tarandach Yeah, that's my question.

21:55Chris Romeo Is it? That's hardware.

21:58Izar Tarandach But it involves firmware.

22:00Chris Romeo That's firmware is hardware. Firmware is software that runs on hardware.

22:05Tanya Ward Firmware.

22:08Matt Coles Uh, but you have to But you have to keep those things in mind if you're going to—

22:12Tanya Ward I'm a programmer.

22:13Matt Coles Yeah, exactly. If you're going to threat model an application, you don't ignore the network. In fact, you have to know the properties of the network. And so if you're going to build an application that lives on a cloud service somewhere—

22:25Chris Romeo Yeah, but isn't that what the cloud does for us though? The cloud gives us the ability to not care about what sits underneath the application. That's why I use— Oh, please.

22:35Tanya Ward I didn't say trust.

22:36Chris Romeo I didn't say trust. I didn't say trust. You never heard me say that word. I didn't say I trust it. I said it gives me the ubiquitous ability to throw an application onto the cloud and poof, it starts, it starts serving up, uh, it starts processing requests without me worrying about things like the, uh, having to, I don't have to do anything. I have to worry about the underlying hardware, the underlying network, but I don't have to do anything to make it work.

23:04Izar Tarandach You do realize that this is how we got to this point in life, right? Because somebody back there said, I'm just going to write this code and I don't have to worry about it because somebody else is going to take care. Like, the cloud is just somebody else's computer.

23:18Chris Romeo Of course.

23:19Izar Tarandach It's a bumper sticker, but it's true. So yeah, you should care. The fact that you're not directly responsible or that you can't be responsible for those processes doesn't take the responsibility of caring away from you.

23:31Chris Romeo Sure. You still have to trust. You still have to investigate to ensure that— Don't trust, verify. Trust but verify. It's a little bit of both, right? But I guess let me ask you this question just to go completely off on a tangent that we never even imagined.

23:46Izar Tarandach Wait, wait, wait. Tanya was going to say something.

23:48Chris Romeo Okay, go ahead.

23:50Matt Coles Well, before you do that, Tanya's—

23:53Tanya Ward No, I was just— I mean, I'm hearing you all talk and I'm just scratching my head here, right? All these separate sections, right? We're talking about, yeah, we have, you know, we have the cloud and we have applications that sit on top of the cloud. And then we have, yeah, we have products, but they have firmware as well. And I think that's one of the fundamental problems is all of these things, they're like little security limpets in each of these different sections. And it maybe comes back to your point, Matt, is how do you, I mean, you have to look at a system at a whole, right? So even if you have an application that you're deploying on a cloud, You as that person need to make sure that all the kind of like little wires are being plugged in like in the most secure way possible and not just go, I'm just application security. You cloud, you figure it out. Because that's where a lot of the problems pop up. It's that lack of, I shouldn't say lack of, but it's maybe the misunderstanding that somebody else is taking care of something. When it's kind of a case where there needs to be some overlap. Like, you have to understand where things are going as you're building things for that particular—

24:57Izar Tarandach Well, and this is—

24:59Matt Coles and if you're doing system development or you're doing things that we learned in computer science class, right, this is what protocols and interfaces are for, right? Your system has connections to the outside world, and you have to understand what those connections are, understand how things interoperate. You don't necessarily— aren't responsible for what's on the other side of that interface, but you have to understand what's coming to you and how you're operating with it. It's no different if you're building an application to deploy into somebody else's cloud.

25:33Izar Tarandach You don't own it. Yes. And how they interact with each other. Just to illustrate that, my last job jump, I sort of did a pivot, a 180. I went from product security to security products. And now, and now I'm looking from the inside at the amount of data that we have out there, both about how our applications run, where they run, and how those things where they run run. So I went meta twice. The amount of information that we have out there about all these things, and if we can bring them together into, uh, this thing, for the lack of a better expression, called observability and security, security observability, whatever way we put that We got just this huge amount of data out there telling us about this universe where all our apps talk to each other and become products and interact with the outside universe, right? And I, every day, I get more and more surprised by how rich this data is. And by the uses that we could or will be making of them, right? And my point is that today, on the past experiences that I have had of product security, we have gotten used to certain looks at how these things work and how we scan them and how we interpret the results. I don't want to use the word siloed, but pretty separated from each one and from the layers. We tend to see these things as layers and we lose the, we lose seeing them more as a jigsaw where one piece goes into the other so that they can join, right? So I think that I look at prod security more like this jigsaw where these separate pieces and AppSec is one of them. Join each other and are part of each other and trade data at different levels and give us different ways of looking at that, uh, at that puzzle.

28:03Chris Romeo So are we jigsaw security specialists now?

28:06Izar Tarandach I think so. And it's just—

28:09Chris Romeo puzzle security specialists.

28:12Izar Tarandach We have always been, because keyword threat modeling, the modeling part is very much putting the puzzle together, right? And then the threat elicitation is figuring out what pieces are missing. Damn.

28:28Chris Romeo Yeah, that was good. So, yeah. Everyone's a threat modeler. That's what we just— there's no longer a need for AppSec, ProdSec, any of these things. Just call yourself a threat modeler?

28:48Izar Tarandach No! There is a need but what you do is— You recognize that you should start as a threat modeler and then you hang all those other pieces on what you just did on the threat model.

28:59Chris Romeo So let me come back to something Matt said though I've been waiting for it. Matt uses the term system security. He uses the term "system" all the time. And effectively that's what we do now to Izar's point here about AppSec, ProdSec, hardware, firmware, everything is bubbling up. The challenge is we used to call it system security like back in the late '90s. Like system security is just not that, it feels like something that we've gone past. And can we circle back around? Is that really what we do right now? Is system security?

29:32Izar Tarandach The system is the problem.

29:38Matt Coles Well, and I think the reason why we no longer do that, by and large, uh, is if one considers themselves a specialist or not. So for instance, in my personal path, I guess I look at myself as having very broad but not necessarily very— not, not necessarily very deep in one area experience, right? So when I look— when I say system security, I'm looking at hardware, software, firmware, application, everything in between, and some other stuff, right? And so I'm looking at the system as a whole. I look at that— that's the view that I bring to the table. I'm not an expert in one of those things. I may have some deep experience in some of them, but I don't— I'm not considered like a specialist in one of them. Whereas I think today we have a lot of there's a big emphasis on specialization. And so somebody may be an application security specialist and that's really what they focus on. They know how to, and potentially around even a subspecialty of that, like web applications, right? Somebody may know everything about web application security and very little about everything else. In fact, we know the network may be foreign to them, in fact, right? Even though they, a web application has to deal with the network, right? They may not understand all of the ins and outs of how networking works. To be able to make that web application work. And so, I think we've gone past the term system security because we are tending to put people in boxes around—

31:10Chris Romeo What do we call the generals? Sorry, Tanya's been waiting. No, no, Tanya's been waiting for a long time. Tanya, go.

31:19Tanya Ward Go ahead. I'm just translating what you're saying into very simple terms. It's like I'm building a house and I have this big picture of everything that I need. I may need a plumber to come in and do all the piping. I may need an electrician. I need all these different pieces. And what you're saying, at a time and a place, it was very simple. I may not have needed electricity, but now I do. And but there isn't really a term for that, to your point. There's no coin—

31:48Matt Coles General contractor.

31:49Tanya Ward No, but I'm saying—

31:50Matt Coles That's a general contractor.

31:51Tanya Ward If you translate it back into security, right?

31:53Chris Romeo What about the architect?

31:55Tanya Ward There isn't really. A term for that person that puts everything together.

31:58Izar Tarandach I think that we solved one of the problems— okay, true, true, yeah— with the circular reference to the layer 7 and to the application, because Matt brought us to a much simpler time— simpler in double quotes. It's not that things were simpler then, it's just that our scope and our boundaries were smaller. My first, uh, official title was a system programmer. And that meant that basically I could do anything from taking a 5 1/4 floppy that somebody put in the wrong slot out of the computer to actually debugging how a Sun 3 station failed to, to go up. And those, those were the boundaries. So when you said, hey, I'm going to define one layer as the application It's because there was only one way of presenting that application. There was only one way of interacting with that application. It was you against the terminal, holding a mouse, clicking on something, and you were there in the application. The application was running in front of you, right? And then applications became bigger and bigger, and Mosaic came, and Netscape came, and all the good stuff came, and everything went out. But even then, those were not new things, because at the time, for example, uh, banks and airlines were already operating on time-sharing systems that had terminals remote and everything. So for them, that 7-layer definition perhaps didn't make much sense. But for us, because it was confined, it did. So it's not that we are circular referencing here. It's still the same thing. It's just opened up in scope so much that application became something so almost enlarged and distributed. That it went out of that definition. But to Matt's point, just second thing, to Matt's point, I think that the system that today we are responsible for is that jigsaw, is that product. So being, working in system security is the nitty-gritty way of saying I work in product security because the system is the product and the product is the system.

34:15Tanya Ward I would love to see a timeline of all these terms and when they started surfacing up, because I'm sure it would have probably been maybe application security, product security. Somewhere down the line, firmware security came in with Meltdown and Spectre, or if not, way before that. Cloud security. Like a timeline of all these.

34:35Izar Tarandach You do have that Google tool that shows you over time how words appear. You could—

34:42Chris Romeo yeah, Google Trends analysis would show us as people started searching for them, as to, you know, how they, you know, when they became available.

34:59Matt Coles I want to be careful though, Tanya. I think it will be interesting to see, but we need to separate words that have adjectives added to them, like firmware security versus, I guess, the proper nouns here of cybersecurity, application security. I think there's a difference between security of firmware and application security. For instance, right? There's a technology domain.

35:28Chris Romeo So, okay, these are— done some rapid research since ChatGPT telling him what products here.

35:37Izar Tarandach Spiked in 2004.

35:41Chris Romeo Interesting.

35:42Izar Tarandach Spiked and it went sharply down. It wasn't like 100, and then it went back to 50, and now it's like between 25 and 75. Ever since. Meanwhile, okay, application security, application security has always been significantly higher than— wait, which one is red? Yeah, application security has been always significantly higher than prod security, and it peaked in February 2014.

36:17Chris Romeo When did it begin? When did application security become Both of them begin on January 1st, 2004. I can't— Yeah, they start tracking the data.

36:29Matt Coles That's how far back the dataset goes.

36:32Tanya Ward Yeah.

36:33Izar Tarandach Do I have to?

36:35Chris Romeo I might break the cloud right there.

36:38Matt Coles Right? Cybersecurity. Oh my eyes, my eyes.

36:46Izar Tarandach Okay, no, this one works. This one works. Okay, wait, let me see if I can do— do I share here?

36:55Chris Romeo Hit the share button. Give it this way, the audience will be clued in here into Isar's live research capabilities.

37:03Izar Tarandach I can't, I can't, I just can't. Wait, uh, window.

37:09Chris Romeo We're live.

37:10Izar Tarandach But which one? Is this the right one? Is this the wrong one? Wait, before I share anything here, let me see what I have open. It's called ops.

37:24Chris Romeo Yes, operational security. Crucial.

37:27Tanya Ward We'll see.

37:27Chris Romeo Crucial for maintaining a job.

37:29Matt Coles We'll see security in the first house.

37:32Chris Romeo Says you need system permissions to share. So it's probably on your system letting your browser—

37:37Izar Tarandach you know what? Forget about it. I'll just tell you guys about it.

37:40Chris Romeo Okay, so—

37:41Izar Tarandach ah, actually, ah, I have visual aids. Wait, where did I put my—

37:49Matt Coles you can take a screenshot.

37:55Izar Tarandach Pin, very important.

38:00Chris Romeo That's a different show. It's called the Tech Show.

38:04Izar Tarandach This one down here is product security. This one up here, so this is—

38:14Chris Romeo yeah, for those, for those listening to the audio stream, he is literally writing on his tablet and live.

38:25Izar Tarandach And this one is cyber.

38:29Chris Romeo Okay, here we go. Yep, there it is. Okay, as we would expect, right? That's the— wow, that everybody is used.

38:44Matt Coles Damn, right?

38:46Izar Tarandach So this is from 2004 to today, and the differences here are, uh, if you consider app 25. Prod is 5, and here it is a 75 and then 100. So this is the distribution as well.

39:11Tanya Ward Wow.

39:13Izar Tarandach And I need, I need something for my handwriting.

39:16Matt Coles I mean, well, well, so I guess when, I guess when When I say that, when I've talked to people and say product security is a niche, I'm not kidding. And so, so there's a difference between—

39:32Chris Romeo We don't have any other terms though. Like, I mean, I think—

39:35Matt Coles Nobody understands what it is.

39:37Chris Romeo That kind of way that you walked us into this, effectively system security is what we're talking about. But to your point about specialization, like there is no, we're missing a term. Somehow we've survived in this industry for 20 years and we're missing a term that defines someone who understands application security, understands the network, understands maybe hardware, enough hardware and firmware to be dangerous. And product security is not that term. At least it hasn't been used in what we're seeing in the data. So is there a term that we're just— are we missing a term or are we just forgetting about a term that somehow exists in our industry that we don't— plug into?

40:22Izar Tarandach That's up to Unicorn.

40:25Matt Coles So I think—

40:26Tanya Ward can I just— can I just spark a huge debate, right? I'm gonna, I'm gonna say, I'm gonna just kind of throw the definition out there, okay? So would cybersecurity not be that complete picture? I mean, here's me, because it talks about people like making sure it's clean. It talks about policies according to this definition, processes and technology to make sure that you're protecting this whole system. Now if we go back to your analogy of having, you know, you're trying to protect this stack.

41:04Izar Tarandach Can I sound like a PR hornet?

41:06Tanya Ward Maybe cybersecurity representatives talk about this stack.

41:07Izar Tarandach Can I?

41:08Chris Romeo Just, I mean, Tanya, the—

41:11Matt Coles yeah?

41:13Chris Romeo The look, did you see the look on, like, we were laughing at César's reaction.

41:16Tanya Ward I'm just throwing it out there.

41:18Chris Romeo As he slowly started to bite through his fist, he may have lost a finger in that process of trying to, trying to feel in his heart the pain of cybersecurity being everything that we do. Yeah.

41:32Izar Tarandach Look, I love marketing people. I really love, I have huge respect for what they do because—

41:37Matt Coles I mean, it is hard.

41:38Izar Tarandach Probably could never do it. But some things, after some time, they just become wrong, right? And these umbrella terms, and cyber among them, I think it's like the most overused, overhyped, overstressed, over-alarmed terms in history. Nowadays, you, you, you just tackle cyber in front of anything that you want money for. And, and the worst part is people give it to you.

42:06Chris Romeo I mean, in my experience, I see the only place I hear people using the term cyber anymore is more on the defense side. Like I don't, I don't in the circles and maybe I walk in, maybe I walk in very like-minded circles or something. I don't hear people use the term cyber anymore.

42:25Tanya Ward Do you guys?

42:26Izar Tarandach I walk in those circles too, please. Really?

42:32Matt Coles Yeah.

42:32Chris Romeo I mean, I live in much more of an absent world. What do you say is the primary term that the conversations I'm having with people, but anytime I hear cyber, it's normally somebody that's a defense sector focused people. Yeah. Like military or defense contractors and people like that. Oh, you mean like federal defense contractors? Still have that term. You know, everything is, it's all about cyber. That's where I hear that. Now, maybe other people, maybe, I mean, do y'all have other experiences? Are you hearing cyber thrown around all over the place still?

43:10Matt Coles Yeah, I hear cyber mostly for network and system defense, but specific to an organization. And that's the traditional way I think of cybersecurity, right? Is somebody who has responsibility for protecting a network environment, you know, either doing perimeter and firewall or making sure that applications or other things within that perimeter and that environment are protected and are secure and incident response and handling and disaster recovery and all that falls into cyber, which again, and maybe this is a bias, and this is certainly a bias that I have, right? In terms of, and maybe some others in the industry have, that cyber is defense of a network, defense of an environment, and not necessarily things that we don't own and control after we ship it, right? Which is where the cyber versus product discussion emanates from in part. But I hear it all the time and I think we see it all the time in whether it be presidential memorandums or executive orders, around cybersecurity, uh, or, um, ISE squared and the certifications, or even SANS and the certifications that they produce. They use cyber all over the place to be used outside of the defense contractor environment. So I, I would— and I was, uh, sorry, Tanya, I, I, I have a hard time thinking that what I do is cybersecurity. And I also have, we also have, you know, I've worked with companies in the past where cyber and non-cyber.

44:49Izar Tarandach Yeah, I'm just going to add to that, that a place where you firmly hear cyber and does have a meaning is in the military where you have the cyber domain of warfare. And that's dealing with a whole different set of things that we don't even go close. All the electromagnetic spectrum, all the information warfare. I mean, we can think that we are there, but we are so not there.

45:21Tanya Ward I'm going to say two things. I threw that out there just to see your reaction, but I think—

45:27Matt Coles Is that the reaction you wanted?

45:29Tanya Ward I knew by the first reaction of the graph, you're like, oh my, help me. But going back to your point, Chris, I do think that there is in the industry some level of mistranslation in terms of what that means. Like, if you go back to the executive order, everything's about cybersecurity. You have the NIST framework, cybersecurity. So that word's being pushed a lot, even though we, you know, as AppSec or product security, have to meet some of those requirements, like the executive order. There's specific things that we have to meet. And so I think this word has just become now a very overall arching Like, I don't know if the definition will change. I don't know what's led, you know, us to this point in time, but I know that that word does affect us in all, like, in everything that we do when we think about integrating security into what we build.

46:19Matt Coles And actually, really important point about this, I think you're highlighting here, or maybe not highlighting directly, but maybe you're going to get there, is In terms of scope, right? There's security, cybersecurity that defends a network. And if you think about it, if you build something for internal consumption, for internal users, maybe you're building a product for internal consumption, your cyber, your cybersecurity team within your organization is going to be defending that. And you're going to have to build it to those specifications, to those requirements. But if you're building a product, and I'll say the product here in quotes of things that we ship outside the organization, it's somebody else's cybersecurity environment that you're shipping into, right? And so the scope changes. And it's an interesting way to think about it in terms of not necessarily just what cyber does, but sort of which cyber you're talking about. So, As you were talking, that's what it was, where my head went to.

47:25Tanya Ward And I would add onto that, if you look at the change in, you know, if you look at kind of how we respond to vulnerabilities and you look at the different practices out there, there used to always be certs, and now PCERTs started coming up. So, and that's kind of like almost a delineation, like most PCERTs are not always going to respond to potentially, they may or may not, like cloud vulnerabilities that would come up or, you know, applications. I think we're at an actually interesting point in time in terms of all of these different technologies and how we're really just handling them when it comes to responding to the issues.

48:05Matt Coles And I just wanna do a quick shout out, Chris, I think that there is somebody who can help us with this over at NIST. I'm gonna drop his name 'cause it'd be nice if he was listening to our podcast and maybe could respond if he hears it. Ron Ross over in this land is working on system security engineering and other standard development, and it'd be great to get some perspectives.

48:31Chris Romeo Yeah, please send us a signal of some form.

48:34Matt Coles If he's listening.

48:35Chris Romeo I don't know that we solved anything here.

48:38Izar Tarandach Did we try to?

48:40Chris Romeo That was my goal. I came here to try to solve something. That's always my goal.

48:45Izar Tarandach I don't think we can solve it. I think we we can shed some light on top of something like this. But it's, it's such a, a consensus-driven thing. I mean, how did cyber get so up there? Because people agreed that, yeah, it's an umbrella term that can be used, right?

49:00Chris Romeo I mean, let's be honest, we all, it's in certain social situations when someone says, what do you do? Come on, we've all done it. We're like, oh, well, I'm in cybersecurity. And they're like, ooh, wow, wow, cool. You know, He's lying. You do. You said you're in cybersecurity. Okay, here, let's pretend we're at a cocktail party. Um, hello, I'd like a martini. Okay. Um, sir, what, what do you do for a living?

49:23Izar Tarandach Why do you care? What's your problem?

49:27Chris Romeo Well, I'm trying to be friends. We're at a cocktail party. We have a shared friend here. What a jerk.

49:32Izar Tarandach I do computer stuff.

49:34Chris Romeo Really? Computer stuff? That's interesting. What type of computer stuff?

49:37Izar Tarandach Well, I do computer stuff and I am a jerk. I'm in data security.

49:44Chris Romeo Oh well, I think we tried. I'm gonna go be friends with the people over there.

49:52Izar Tarandach No, no, no, no, to be sure, to be sure, I'm gonna go, uh, particularly because of the distinction of, uh, where I think that the cyber label does apply, which is all that good stuff happening in the military domain. I think that I, I, I have too much respect for that part of the house to be able to point at myself and say I do cybersecurity. No, I don't. I, I secure products.

50:24Chris Romeo Okay. I can, we, we, we, we can take that. Well, I think we'll, we'll leave it there. So, uh, thank you Security Table folks for trying to wrestle through this. I think we— I think there were some moments of clarity, at least for me, I had some moments of clarity. I don't ever want to be at a cocktail party with Bizarre. I learned that as well as a takeaway from this.

50:48Tanya Ward But—

50:50Matt Coles And you know what? If this drives a conversation—

50:53Chris Romeo Yeah. And if somebody comes up with a term for what we do—

50:55Matt Coles People learn when they exchange ideas.

50:57Izar Tarandach So, A nice one.

51:00Chris Romeo Yeah, a nice term for what we do. That would be, you know, ping us on LinkedIn or Twitter or something. Give us your thoughts if you have a— if you somehow have an idea of what we can call this. And you're yelling, you've been yelling into your speakers, "No, you need to call it this!" Tell us, ping us, tell us. But that'll wrap up this episode of The Security Table, and tune in next week as we continue the conversation.

Transcript supplied by AssemblyAI. It may contain transcription errors.

Originally published as The Security Table. Part of the AI Security Table archive.