41 min

Acronyms, Abbreviations, and a slide into Application Security

With Chris Romeo, Izar Tarandach, and Matt Coles

Security strategy, risk & industry trends

Matt, Izar, and Chris started the conversation by discussing all the acronyms and abbreviations we use in security and then morphed into a discussion of what application security is. While they only scratched the surface of what application security is, this episode will make you think about all the acronyms we use in our industry and how they are received by those that are new and outsiders.

Episode title image: Acronyms, Abbreviations, and a slide into Application Security

Listen to the conversation

About this episode

Matt, Izar, and Chris started the conversation by discussing all the acronyms and abbreviations we use in security and then morphed into a discussion of what application security is. While they only scratched the surface of what application security is, this episode will make you think about all the acronyms we use in our industry and how they are received by those that are new and outsiders.

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 · 41 min conversation

0:00Chris Romeo Hey folks, welcome to another episode of The Security Table. This is Chris Romeo. I'm joined by Matt Coles and Aizar Terandash. I always get your name wrong. I say your name differently every time. Even I say your name wrong every time. Well, I've heard so many different people say your name different ways that I'm like, now I'm always like, I don't know what to call this guy. Mr. Terandash, I know the last name. I got that right. It's Terandash. I know that part.

0:24Izar Tarandach Let's go with that guy.

0:26Chris Romeo Okay. Or I'll just call you sir, maybe Mr. Taryn Das. I don't know.

0:30Matt Coles You could call him IT.

0:32Izar Tarandach Oh my God.

0:32Chris Romeo Hello? Hello, IT.

0:36Izar Tarandach It's in my name.

0:38Chris Romeo That's good. I'm gonna go with that now. How do you feel about that, IT? And then someone from the IT department will literally sit up and go, I don't— I need support.

0:48Izar Tarandach I can't comply with that kind of thing.

0:52Matt Coles I thought you were cute.

0:53Izar Tarandach Somebody just took me off the shelf.

0:56Chris Romeo He could do these all day, folks. Like it's nonstop. He can literally keep the puns flowing. He has ChatGPT piped into an earpiece and he has asked ChatGPT to give him all the possible terrible IT puns.

1:11Izar Tarandach Sydney, come again? Sydney.

1:16Matt Coles We do have him on a 5-second delay though, just in case.

1:19Chris Romeo Well, I mean, yeah, that's, we all know why. We know why that is. All right, now I think we're actually here to talk about something, not just goof around at lunchtime, which is what I originally wanted to do with this episode, but you guys said—

1:33Izar Tarandach Wait, isn't that the same? Anyway.

1:35Chris Romeo Yeah. All right, we're back. And so, the topic we wanted to chat about today is this whole idea of acronyms. It seems like in application security, you have to have a 4-letter acronym to describe anything you're doing. Or 2 letters, 3 letters, but most of them are 4 letters.

1:57Matt Coles Actually, we do have some 1-letter acronyms too, which is—

1:59Chris Romeo Wait, hold on. My mind is just blown. How can you have a 1-letter— I mean, like maybe if your name is Prince and you go by the letter P, you can have a 1-letter association with something. But what is a 1-letter algorithm?

2:13Matt Coles Hold on, where's my sign?

2:14Izar Tarandach I'm gonna— The language previously referred to as C. Yeah.

2:19Matt Coles There, there, quickly.

2:22Izar Tarandach Signs! CIA.

2:24Matt Coles There we go.

2:24Chris Romeo Yeah, but there's 3. Come on. That's 3 letters.

2:26Matt Coles But it's 3 different words. They're not meant to be used together.

2:30Chris Romeo Sure.

2:31Matt Coles It's not a 3-letter acronym. It is 3 1-letter acronyms.

2:34Chris Romeo And you know, in the Security Trainer's Handbook, I don't know if you guys have received the latest copy of the Security Trainer's Handbook, but it does say within the first 3 slides, you have to introduce CIA. In any security class, like it's, if you don't do that, you're out of the guild, you're out of the union, whatever, whatever, whatever we're under. We have, let's talk AppSec.

2:55Matt Coles We have failed our job is if we don't.

2:56Chris Romeo Yeah. Yeah. So let's, let's, once you guys, these are, give us a couple of, summarize a couple of these acronyms. Let's get 'em on the table first when we're, we're talking about AppSec acronyms.

3:08Izar Tarandach So I, as many of you know, my, my start in this whole thing was a system programmer. In a university department, a university CS department. And I think that the first acronym that I ever heard, that I ever learned was RTFM, which of course then became the mantra.

3:24Matt Coles Not a security term.

3:26Izar Tarandach Definitely. If you don't want to be whacked across the head with a manual, it's very, very much a security term.

3:36Chris Romeo I think, and yeah, so is that, do people even use that anymore? I do. Other than in joke?

3:40Matt Coles I do, yep.

3:41Izar Tarandach I do.

3:41Chris Romeo Yeah. Yeah. You literally tell people to read the bleeping manual. Manual.

3:46Izar Tarandach Look, it's, it's, it's better than saying it's not bleeping, it's read the forgotten manual.

3:52Chris Romeo Mm-hmm.

3:53Izar Tarandach But it's better than telling someone, let me Google that for you.

3:58Chris Romeo Which is what we're all doing behind the scenes anyway.

4:00Matt Coles Well, and, and of course we're not talking physical manuals anymore, but, uh, you know, that could be documentation on GitHub or, yeah.

4:06Izar Tarandach Uh, or wherever.

4:07Chris Romeo So that, that's like a cultural abbreviation, right? Like RTFM.

4:12Izar Tarandach But it opens up for so much of security because at the end of the day, what we want is for people to first of all read the documentation, understand it, and most times do what it says. But, um, no, but going back to the thing then, um, let's see, my first security acronym, what was it? It might have been, as Matt said, CIA, although I don't think so.

4:42Matt Coles I can tell you one of the earlier acronyms I recall from college was actually all the acronyms used around crypto algorithms like CBC and AES and MD, right? Where, you know, they're, they're used, they're shortened for convenience because obviously they're, they're potentially very long or very complex words to say. Although I don't know how complex Advanced Encryption Standard is to speak for most people, but we concatenate or we abbreviate those things all over the place, right? And for documentation purposes, for ease of use, and then we say these words, well, we say these acronyms as words. you know, and sometimes actually make pronunciations with the letters even if they don't form words, uh, to, um, to try and make it, you know, as a form of language in some cases.

5:44Izar Tarandach Yeah, but you know, I keep thinking about like after that RTFM where things started going wrong with acronyms, and I think that I just started reading the, uh, The Letter Soup later on when I started creating, selling, and buying stuff. But in the middle, there was that one that all of us once met and I particularly love— Pooh Bar, which participates in so many different contexts of what we do around here.

6:19Chris Romeo Yeah, I mean, you're going back to like early internet culture here. Like, that's the—

6:24Izar Tarandach What can I do? Not early, early '90s something. But FUBAR, FUBAR was a great one because not only it explains what is happening, it explains how it's happening, and it explains why it happened.

6:42Chris Romeo Yeah. Let's think about some things that are more on the AppSec side. Now, we've had a little bit of a walk down memory lane, but when I—

6:51Matt Coles Memory lane.

6:52Chris Romeo Memory lane, maybe. But I mean, when I think AppSec, Tech acronyms, right? Let's go through the list. SAST, Static Application Security Testing. DAST, Dynamic Application Security Testing. IAST, Interactive. If static and dynamic weren't enough, now we have Interactive Application Security Testing. RASP, Runtime Application Self-Protection. CBA. Give me one, give me another one, hit me.

7:16Matt Coles SCA.

7:17Izar Tarandach Oh, remember?

7:17Chris Romeo SCA?

7:18Izar Tarandach It meant something else.

7:19Matt Coles It meant something else and now it means something different.

7:21Chris Romeo Yes.

7:22Matt Coles Okay.

7:22Chris Romeo Software Composition Analysis is what people refer to it now as.

7:25Izar Tarandach What was the previous?

7:27Matt Coles Analysis.

7:28Chris Romeo Yes, static code analysis. Okay. What else do we have? We got CVA, we got container vulnerability analysis. I've seen that one used. There's some new cloud-native ones. There's, I mean, of course, the best one of all time, TM, and it doesn't mean trademark.

7:46Izar Tarandach Oh yeah, definitely that one.

7:48Matt Coles Yeah. IAVS.

7:52Chris Romeo Oh, what's that one?

7:54Matt Coles Information Assurance— sorry, is that Information Assurance Vulnerability? It's a set of acronyms.

8:01Izar Tarandach Information—

8:01Matt Coles I'll have to look it up. I know it exists.

8:03Chris Romeo I don't know. Okay. So it is literally a grouping of another set of acronyms. So we have two levels of acronyms. Like, we use this one to describe all of it. Now, don't even get me started about EDR, MDR, XDR, ZDR. I know, I know. Have you guys seen ZDR? It's the Zebra Detection and Response. It's this new thing I'm trying to get going.

8:21Matt Coles I don't know what that is.

8:23Chris Romeo I just think Z sounds better. Like everybody's got a DR solution. So like I just threw one out there, you know?

8:28Izar Tarandach And I'm loving all the cloud ones, CPM, CSPM, C— there's a couple more that start with C and end with M.

8:37Matt Coles So here's IAVS. I remember seeing the term, but it is very confusing. It's Intelligent Active Network Vulnerability Scanner. The N is silent.

8:49Chris Romeo That's like the S in IoT or the security in IoT is silent. The S in the IoT is silent. But yeah, I mean, and I think, you know, when we think about all these different algorithms, I keep calling them algorithms, they're abbreviations. Like one of the challenges is that AppSec people, we tend to use these things and we don't always stop and security people, I think we're all, this is a bigger than AppSec, this is a security people thing. We tend to use these little abbreviations that we have and not always stopping to ensure that everybody in the conversation understands.

9:26Matt Coles Yeah.

9:27Chris Romeo All these different things. And so that's one of the challenges that we have with, with using all these shortcuts is stopping to explain what they are. And it makes me think, are you guys ever watched The Office?

9:40Matt Coles I haven't.

9:40Chris Romeo Okay. We have Office fans out there somewhere. There's an episode where Kevin Malone takes out, starts taking out letters of words because he wants to talk faster. But then at the end they're like, but wait, you had to stop and explain all this to us. So it actually took longer.

9:57Izar Tarandach But wait, you say that as if it's a bad thing. Like, don't forget that the overuse of acronyms is one form of jargon that people use many times to fence their little kingdoms. If I speak fast enough in a language that you don't understand, it means that A, you're not going to bother me. B, you're going to think that I am really, really smart and and see, you're going to think that I really know what I'm talking about.

10:26Matt Coles And all of those are bad reasons to use acronyms.

10:29Izar Tarandach And to go back again to why people use acronyms, I think that one of the— and Matt alluded to that in the beginning, I think, before we started recording— one of the areas where people use acronyms the most is the military, right? And in there, the idea is that you want to convey a fact or an idea extremely fast, extremely clearly in a way that cannot be misconstrued. So in, in radio messages, they found this, this way of passing whole ideas in very short acronyms. And then that gets moved to the other side of the, of the operation where they have all the acronyms to describe all the different pieces of equipment and material and whatnot that they use. So, in the military, basically everything is an acronym.

11:24Matt Coles Yep. But that makes sense if all of those acronyms have a consistent, clear meaning that everyone who is using that language understands and knows. Let's use the SCA example. Use SCA as an example. You know, it has multiple expansions, right? Static code analysis, software composition analysis. And so just using that in conversation, even among two security people, may get different interpretation about what's being meant.

11:59Izar Tarandach That one, I felt that in one week everybody decided to change the meaning and nobody called me. And I had meetings the next week and people are going, SCA this, SCA that, SCA the other one. And I'm listening to it and like, that's not what SCA does.

12:16Matt Coles It doesn't work that way.

12:19Izar Tarandach Led to some very, very interesting exchanges. But my feeling was that one given week, everybody just decided to change the meaning.

12:26Chris Romeo Think about where these things come from though. You guys know where a lot of these acronyms actually come from? Especially the ones in the marketing people, but even better, they come from— there's a particular organization that likes to create acronyms and then drop them on the industry by creating Let's see, 4. I'm not going to, you know, I don't want to be specific, but they create 4 charts, you know, charts with 4 quadrants in them. Oh my goodness.

12:55Izar Tarandach Seriously? Oh yeah, right.

12:58Chris Romeo They create a lot of these. They make the market for a lot of these acronyms because marketing people can then say, we've got the best such and such, you know, because marketing people need to, they want to be able to fit what they're doing into a category. They want to be able to take advantage of the education of the market that's happened across everybody that's got a product in that space. And so how do you do that? You do that by buying into the acronyms and demonstrating that your product has that, is that thing that you already know, right? Like, do I, do any of us, we don't need a definition of what a SaaS is. So that, I would say.

13:37Izar Tarandach So that goes back to the military use of creating a clear language and maintaining an inventory, right? Because you have these products that are coming up all the time, filling niches that are being created all the time, and we still have to be able to talk about classes of things so that, especially them, so that they can compare everything under the same, uh, the same keys. So yeah, that makes sense.

14:04Matt Coles And that extends then into organizations that work with the military, it sounds like, like MITRE as an example.

14:10Chris Romeo Yeah.

14:11Matt Coles Which has an entire series of acronyms in their program, describing programs as opposed to describing technologies or types of systems, right?

14:25Chris Romeo Yeah, I mean, that's a whole other segment of acronyms we didn't even touch on yet, right? The CVE, CWE, CVSS.

14:33Matt Coles CWSS.

14:35Chris Romeo CWSS.

14:36Matt Coles CAPEC, which is Nobody knows what it means.

14:39Chris Romeo I use the alternative pronunciation, CAPEC, but that's just from the South.

14:43Matt Coles And then you have ATT&CK, and you have ATT&CK, which is an acronym, but modifies the middle letter.

14:51Izar Tarandach But yeah, Chris brings another great point. It's not only the acronyms, it's the pronunciations as well. Mm-hmm. Let's not go into the JIF GIF, but KPEGIF.

15:02Chris Romeo Now hold on, stop, stop, stop. There's only one correct answer.

15:08Izar Tarandach And it's not—

15:09Chris Romeo yeah, it's not—

15:10Matt Coles no, no, no, no, this is—

15:12Chris Romeo this is— it is a GIF.

15:16Matt Coles So it is the peanut butter.

15:17Chris Romeo Look up the— look up the file format. The file format— I swear this is true and I can't prove it. I swear that in the file format initially for GIF, it said JIF in the actual binary file. I'm probably completely making this up or I had a dream about it. But I feel like we can always ask ChatGPT to tell us the answer.

15:39Izar Tarandach EMA, VI, I don't care. But the truth is, back to the acronyms. So basically at this point, almost what we need is an LOA. Don't use the acronyms.

15:54Chris Romeo You got me there. I'm sitting there for a second going, wait, what the heck is an LOA? I don't know. I know LOI, letter of intent. What's an LOA?

16:05Matt Coles DMU.

16:07Chris Romeo That's right, another acronym.

16:10Izar Tarandach Because, uh, hey, we can't keep up not only with the, the new acronyms, but we can't even figure out the ongoing meaning of the old ones. Do we have another— any other acronym that changed under us apart from SCA?

16:29Chris Romeo Can't think of any off the top of my head. Yeah. I'm sure some have, but it's that maturation of the industry.

16:38Izar Tarandach I think I remember something with ZT that like, of course, became Zero Trust, but before that was something else.

16:43Chris Romeo Might've been something in the Zigbee space.

16:45Izar Tarandach Oh.

16:46Chris Romeo I think there was a ZT. Yeah, it was a crossover though, so between different areas and stuff. But I mean, I think, so what do we do with this though? Like what are we— Is it a good thing?

16:57Izar Tarandach We haven't decided that yet.

16:58Chris Romeo That's a good question.

17:01Matt Coles Well, it depends on what you— Contextual as to whether it's good or bad. I think you highlighted it earlier actually. We do a generally, and I say we collectively as a security industry and probably as a technology industry in general, not just security. But sticking to security for a moment, we do, I think we do use acronyms in common language and common discourse with clients, with customers, with ourselves or with engineers, developers, and fail to adequately expand the acronyms when we need to. Good writing style is you start, if you're going to use an acronym, you define it first and then you can make an acronym and then you can use it throughout because there's a reference, right? Well, when we're talking through it, right, if you start talking about, let's say, I want you to put an HTTPS interface on your web server and I want you to use CBC and AES, but you might have some PKI in there. Okay, great. What did you just say? And so, We do need to do a better job about that. And I think it's bad when we use them assuming that others know what we're talking about. And it's good because we can make clear, concise documentation and diagrams and other things as long as we provide the references to what those acronyms mean.

18:33Chris Romeo Yeah. Yeah, I mean, it does give people a framework, gives people a place to start. If you're new to the industry, because I like to think of these types of things from the people that are new to the industry. Like, we've all been around the block 7 times and, you know, we— I was just thinking about like if somebody like, how do I approach if there's an acronym somebody uses now versus 20 years ago? Now I just like, hey, stop, what does that mean? Because like, I've reached the point where I realize there's so much that I don't know. About security and about everything else that, and I just don't care if anybody like looks at me and goes, how do you not know? I don't like, I just want to know. Whereas 20 years ago I would've been like, you know, maybe being quiet for a while going, ooh, I should know this. Like, I don't know what that is. They're using this thing. So I think, you know, acronyms, it's as long as those of us that have been around for a while are ensuring that we're teaching the next generation and not using acronyms as a weapon, I think they're fine.

19:30Matt Coles Well, in addition, In addition to the acronym and its expansion, we also, I think, need to be careful about acronyms and their meaning. So we generally know when you say SAS, PAS, IAS, what those expand to. But it's not always clear, I think, what those scope to, right? What's the boundary of PAS or boundary of IAS? When we're talking about a system.

20:02Izar Tarandach Let's say we're doing prep, that's not the acronym anymore. I mean, it's, it's the overuse of the term.

20:09Matt Coles Well, can you explain that a bit? Because maybe your viewers aren't sure.

20:14Izar Tarandach Uh, if I understood what you're putting on the table, people are using something like SaaS for things that are way beyond the boundaries of SaaS. But then it's not really the acronym, it's, it's the use of the term itself. They could call it, uh, Mercedes and it would be the same problem.

20:35Matt Coles Nothing against Mercedes, which is not an acronym.

20:40Chris Romeo As far as we know, it's not an acronym. Maybe it's a really fancy acronym, but, but I—

20:46Izar Tarandach yeah, that's the thing. I'm sure that somebody has an acronym Mercedes somewhere because People are welcome to name anything.

20:54Chris Romeo True. Could be a new Stride-like categorization of threats. The Mercedes method of threats.

21:00Izar Tarandach Main event repository of chained execution data entered Sunday.

21:13Chris Romeo Solidarity. Solidarity.

21:15Izar Tarandach Entered Sunday.

21:18Chris Romeo Yeah. So I guess, you know, this acronym conversation is kind of, I guess we talked a bunch of, about a bunch of different AppSec acronyms and stuff. And, you know, this is kind of, has kind of been a warmup for the issue that I want to throw on the table right now, 'cause this one may end up being more controversial, more in-depth. But to me, we've got all these AppSec acronyms and I've seen a pattern where Some people think AppSec is just SAST and DAST and tooling. They think of AppSec as this is just a tooling thing. Like I'm an AppSec, I've seen a lot of people described as AppSec engineers. And when I look at what, like a job posting for AppSec engineer, and it will say you need proficiency in one of these types of SAST tools, one of these types of DAST tools, your job description is to ensure the tools are running and spitting out data. And for me, that's a component of AppSec, sure. That's not AppSec in its entirety. But I feel like that is a place where acronyms meld together with a misrepresentation perhaps of what all of AppSec entails versus just focused on the tooling. So what have you guys seen in your travels?

22:36Izar Tarandach I think that people like to chain acronyms the same way that they chain concepts. And, and that's where things break a bit for me, because they have a tool that does this and a tool that does that and a tool that does the other one, and each one of these is an acronym. And they say, my, my CI/CD is covered because I have these acronyms along it. Okay, but then you go and you look at our lovely acronym TM. And with all due respect to all the tools out there, right, you can go and press buttons as much as you want. What's going to come out is not a 100% correct model because there will always be the conceptual stuff that needs a person to actually look and ideate in there. So to just hide the, the completeness of the process behind the amount and the, um, connectiveness of those acronyms and build that, that huge string of acronyms that you hope somehow solidifies the security that you have in your processes, to me is, is just a bit more security theater, right? If you don't have the people glue in the middle, if you don't have the conceptual layer, if you don't have the, uh, what could go wrong and what are we gonna do about it, then you just got a bunch of robots talking to each other. And that's going to be— it's a lofty goal to get to. I don't think that we're there yet.

24:18Chris Romeo When you say security theater, you're referring to Schneier's— Bruce Schneier's definition or use of that term in that it is security that is done for people to feel like things are more secure when in fact it doesn't improve. It's not necessarily improving the overall security. Is that the definition or the way you're thinking of security theater?

24:39Izar Tarandach That is the primary definition that I know, and that's the one that I'm using here with the added meaning perhaps of a bit of a puppet theater. Where you are seeing the shadows moving and you think that there's a whole story and costumes and scenarios involved, but basically it's just a shadow.

25:08Matt Coles So I think, Chris, you're touching upon something. I mean, what you just said was you're touching upon the whole compliance versus security discussion, right? Which is doing things that you can demonstrate easily, that you can get metrics from, that you can check checkboxes from, but not necessarily that gives you assurance in the security posture of the system. When you proposed this, actually, I was kind of wondering where the acronym side fit in. I don't see the connection as well, although CI/CD was a good one that we should have, uh, there's CI/CD, um, uh, continuous delivery, continuous integration, continuous delivery, and there's one other one, but I don't see something that goes with that.

26:02Izar Tarandach Continuous script modeling? No.

26:05Matt Coles Well, there's that too, but that's 3 letters, not 2, uh, and not related to the that part of the pipeline. And so I want to be careful here that, you know, there is benefit, I think, to having people run these automated tools. But as Ozar said, there's parts that require human intervention in order to get full value out of it. And so I think we have done it. There has been something has happened. I don't know if it's specifically AppSec that's done it or marketers or business people or whoever. I believe it's probably business folks who drive rush, you know, drive to market as a goal. And so what happens is, well, how do you do all the things that security needs you to do in an efficient manner? Well, you run a tool. We know that tools enable productivity. The problem is tools are not 100% effective. They aren't necessarily effective at all against the technologies that we're working on. And I think we've either had an episode or we'll have an episode coming up about something like that, I'm sure, around effectiveness of tools. And so we have to recognize that though, that we, you're not gonna get full benefit out of just running a tool, right? And AppSec is not just, cannot be just running a tool. Because you'll miss a large portion of, or some portion of, of your security posture as a result.

27:44Chris Romeo So that leads me to ask the question, what is AppSec? Oh, what's the definition of AppSec? I have mine. I have my own definition, but I'm going to hold it until the end. I want to know, I want to know what you both think of when you say the def— if you had to answer this question, the definition of application security is So let me take a stab at that.

28:11Matt Coles And this is gonna be completely left outta my head 'cause obviously you've been thinking about it a lot longer than I have. I think if I were to define AppSec, application security, it is an area, say, I guess a knowledge domain or functional domain of system development that strives to reduce these, the, or improve the security posture and gain assurance and confidence about that posture to minimize the impact to a system. Very clinical definition there.

28:55Izar Tarandach And to my view, very correct. The one thing where I'm going to start asking questions is just one question. AppSec. What's an application? What's security? And when do you want to know? Because the thing is, AppSec, once upon a time— okay, let's go back, back, back, back, back, back, back, back. And once upon a time, there was Security. Actually, before that, I would say that before security, there was network security, right? Because this whole thing just started when we started connecting cables to cables.

29:37Chris Romeo Yeah. I mean, we called it security in those days, though.

29:39Izar Tarandach Yeah.

29:39Chris Romeo We didn't specifically call it network security. It was just security.

29:43Izar Tarandach But then when we started, like, putting all those Cisco boxes and blinking lights and things were talking to each other, all of a sudden it became network security because one of those pipes was going outside and talking to other people that we don't know. That was like the limit of our perimeter.

29:59Matt Coles So let's take a step. I need to— we just need to take a quick step back. Even before that, there was already physical security and personnel security, right?

30:10Izar Tarandach We don't care about those guys.

30:11Matt Coles Uh, but, but it matters.

30:16Izar Tarandach The, the thing is that at that point, I think that this thing that we called security was basically very analogous to what Matt just said— sitting in the tower, sitting in the fence, and making sure that nobody was coming in. And that was good. We knew the people who were inside. We trusted them to different values of trust. And anyway, the systems couldn't do too much stuff. Roll all the way back in. We passed the desktop age, we passed the new mainframe age, we passed the network is the computer, we passed, uh, what else have we got? To cloud, we got to hybrid clouds, we got to public clouds. Now we have serverless and things are just going ubiquitous computing and yeah.

31:09Chris Romeo Right?

31:09Izar Tarandach So they're getting more and more diffused. And now we have that, uh, that huge discussion between, uh, everybody wants to do DevOps, but we say they should be doing DevSecOps and the Sec is silent and sitting on the fence, looking outside with the rifle in your hands, shooting at whomever comes in doesn't work anymore because now you can't really say who you trust, who you don't, to which extent. Inside, you shouldn't and probably trust everybody to the same extent. So all that good stuff. What I'm trying to say is that application became not, not anymore just that binary running in one computer that you have to sort of do something so that most people can do anything with it. It became this much more amorphous thing that I am a developer, but I am also an infrastructure person, but I am also somebody that deals with the building pipe, but I am also the troubleshooter and I am support and I am the security guy. So that application acquired levels and levels and levels of things that need security. And now the other definition, security. What is it that we're trying to do? We're trying to keep anybody who's not wanted authorized, authenticated to interact with all these different layers that we have that make up our application, right? Which leads me to the question— what was the question again?

32:44Chris Romeo Definition of application security.

32:46Izar Tarandach Yeah, that. So my personal definition now is if you are involved in any part of the development of something that can be construed, compacted, limited as an application, then you need to some extent to have— you don't need, you have to some extent responsibility over its security. And that to me is what closes the whole DevOps, DevSecOps discussion. Like, it's not enough that I am writing the thing and I have to keep an eye on how it performs. I am also writing the thing, I have to keep an eye on How it gets deployed and what does that mean in terms of who can get to the thing.

33:34Matt Coles I want to counter, I think, I think I want to counter something you just said there. First off, or maybe I want to counter it in a different way. AppSec, can AppSec exist without DevSecOps as an operating model?

33:51Izar Tarandach Yes.

33:52Chris Romeo Yes.

33:54Matt Coles So in that case, we now use DevSecOps as the model by which we execute or perform a lot of the AppSec functions. But AppSec is not DevSecOps, right?

34:10Izar Tarandach Yes. But in the same vein, can a car exist without tires? Yes. But can it run? Not really. Nowadays, everybody's trying to get to the DevSecOps layer of things.

34:21Chris Romeo Yeah, but AppSec and DevSecOps are definitely different things. AppSec, and here's how I come to that conclusion, AppSec will still exist whenever the next thing after DevOps is created, right? We know we've been through a cycle of Waterfall, Agile, DevOps. There will be something else. Like, it's, it's, we know there'll be something else. I don't know. We don't know what it is, but there will be a newer methodology. And I would argue that AppSec will still apply to that next methodology.

34:52Izar Tarandach But wait, Matt was going somewhere and I cut with the cat, with the car.

34:57Matt Coles Sorry.

34:59Izar Tarandach Go back there.

35:01Matt Coles I wanted to separate the method by which we do application security from the thing that we're doing.

35:07Izar Tarandach But that's the thing. Go back to my timeline. Back then when it was network security, AppSec in double quotes, quadruple quotes was sitting on the perimeter, not letting anybody come in. And today AppSec is DevSecOps, right? And, and, and all that stuff. And, and as Chris points out, tomorrow it's gonna be something else. It's going to be us saying what ChatGPT said is just bullshit. Can I say bullshit? Well, it's like you did.

35:41Chris Romeo You just did.

35:41Matt Coles You can or not is a different question.

35:42Chris Romeo No, no, that's a totally different question. But I mean, DevSecOps is, there's so much more to AppSec than DevSecOps. Right? DevSecOps is not like— it is, you know, training, for example. Training sits at this— for me, training, I think of training as the secure development lifecycle, which wraps around my DevOps pipeline but also covers a lot of other things. And so I think of them as separate. I think of them as not the same thing. AppSec and DevSecOps are not, in my mind, not the same thing.

36:11Izar Tarandach You know, in your presentation at the Global OSp last week, you, you said something like, uh, the infinite loop is not the best representation. And I think that sometimes we, we catch the, the SSDLC loop as our best representation for AppSec, and we don't recognize the fact that, as you just said, yeah, things, things change in the ways that they happen. So let me put this in a different way. Is AppSec something that is fully represented by the SSDLC loop? By the flowchart?

36:59Matt Coles Let's define that acronym first. Yeah, please. Well, so what acronym are you using? Because there are— Now here's another Here's another one. True, true. Similar to SCA that has multiple potential—

37:15Izar Tarandach Yeah, so the Secure Software Development Lifecycle.

37:17Matt Coles Right, and so that's, and actually that's the second S is the key part I want to ask there. So I think of SSDLC as a source.

37:28Izar Tarandach Oh, the source, yeah.

37:29Matt Coles Secure System Development Lifecycle.

37:31Izar Tarandach Yeah, yeah, yeah.

37:32Matt Coles And the discussion you had earlier about network security, right? When I think of network security and app security, Application security is two different domains of subdomains of security. Cybersecurity and network security is all about perimeter defense. Make sure that data center is secure. Make sure my network of laptops is secure. And then the applications sit on top of those things that are within the perimeter, traditional networking, obviously. And they are different domains. So the first question is, do you see that there's a domain separation? Second question is, AppSec software-focused?

38:15Chris Romeo We really opened a can of worms here, didn't we?

38:17Matt Coles And I'm going to bring that, you know, I, you know, for folks who have listened to this podcast series may have picked up, you know, I tend to look at the system and that includes physical systems. Often, right? And so hardware and firmware and the network, but also the processes, the people that are involved. And not all of that is within AppSec, I think. At least traditionally, people don't consider all of that within AppSec.

38:49Chris Romeo But we don't have boundaries. I've heard people not like— I've heard people hate on the AppSec term for that reason by saying, hey, the world is more than software. For example, in Dublin, we saw OWASP is no longer Open Web. OWASP is now Open Worldwide.

39:11Izar Tarandach Woo-hoo!

39:12Chris Romeo As in there's another acronym. We didn't even talk about OWASP. Open Worldwide Application Security Project. So, they're still using application security, but they've changed the focus, right, from web which we know the world is so much bigger than web, to worldwide.

39:31Izar Tarandach So while I completely support the change, I really, really support the change. Isn't it funny that we are talking on one side about security, on the other side something that's open worldwide?

39:42Chris Romeo Yeah.

39:43Izar Tarandach To me, it does have a thing of, anyway. But, oh, one thing, one very important thing. We haven't spoken about the most important acronym of all. W-I-T. Where is Tanya?

40:00Chris Romeo Where is Tanya?

40:01Izar Tarandach Sorry, we don't have Tanya today as well, but we hope that she's going to join us in the next one.

40:06Chris Romeo Yeah. So with that, I think we'll call this meeting of the Security Table to a close. I don't feel like we maybe came to any conclusions coming out of this. No. I think we just asked a lot of questions. Yep. And we went on this, We kind of went on this journey from acronyms all the way to what is application security. But I think we got to come back around and talk about this some more next time because there's more work to be done here.

40:30Izar Tarandach Yep.

40:30Chris Romeo Yeah.

40:31Izar Tarandach The, the, the what is AppSec is, is, is a nice one to go back to.

40:34Matt Coles Yeah.

40:35Izar Tarandach Yeah.

40:35Chris Romeo Yeah.

40:35Matt Coles But we also have lots of acronyms to work with. I mean, CAPTCHA, come on.

40:39Chris Romeo Oh, well, we at least we put some of those acronyms in the air now. So they're in the ether, they're floating around. We can use them at will. While we still try to define them. So folks, tune in for the next episode. We're going to continue this conversation about what is application security, is AppSec DevSecOps, and I'm sure a bunch of other things that'll come up. So tune in for the next episode.

Transcript supplied by AssemblyAI. It may contain transcription errors.

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