# To SSH or Not?

URL: https://securitytable.ai/to-ssh-or-not/
Published: 2024-07-17
Duration: 1688 seconds
Season: 2
Episode: 20
Hosts: Chris Romeo, Izar Tarandach, Matt Coles

## Show notes and chapters

In this episode of 'The Security Table,' we are back from our midsummer break to discuss OpenSSH regression vulnerability. We dig into the nuances of this race condition leading to remote code execution, explore the chain of security updates, and the role of QA in preventing such regressions. We debate the necessity of SSH in modern cloud-native environments and its alternatives. Plus, we answer the critical question of who should catch these vulnerabilities first — QA teams, pentesters, or automated tools? 

  
  

Follow AI Security Table:

➜ Home: [https://securitytable.ai/](https://securitytable.ai/)

➜ X: [https://x.com/AISecurityTable](https://x.com/AISecurityTable)

➜ LinkedIn: [https://www.linkedin.com/company/ai-security-table/](https://www.linkedin.com/company/ai-security-table/)

➜ YouTube: [https://www.youtube.com/@AISecurityTable](https://www.youtube.com/@AISecurityTable)

## Transcript

**Chris Romeo (0:10)**: Hi. Hey folks, welcome to another episode of The Security Table. We're back after a midsummer break, kind of like Formula 1. We take a month off to retool the cars, to get the brains moving again, but We're back again to, uh, to enlighten you with, I don't know, something hopefully that's enlightening. And before we jump in too far, I want to give a quick shout out, not in a Casey Kasem top 40 kind of way, because, uh, that would be just weird. That'd be weird.

**Matt Coles (0:42)**: That'd be just weird.

**Chris Romeo (0:44)**: Some people, anybody under like 40 is like, what are they talking about? Google it. Look it up on Wikipedia. Now this is a, a quick shout out to Robbie and JD who are some of our avid fans. Here in the Raleigh-Durham metro area apparently like to get together and discuss the Security Table. So keep it up and, uh, give us some feedback and let us know, uh, let us know what else you want to hear us talk about. But, uh, Matt, you got an issue that you want to throw on the table here, and I have a simple answer, but I'm going to let you describe it first before I just completely wrap up the episode.

**Matt Coles (1:18)**: Okay, let's— this ought to be fun. So topic for today. Regression. Regression. Sorry, couldn't resist. Anyone under 40 has no idea what I just did. Regression. So regression is a word and it means something and it is also a vulnerability and it means something. So regression, for those who don't know, I forget what the CVE is actually, it's a uh, SSH, OpenSSH vulnerability, uh, race condition leading to a remote code execution in the OpenSSH server. The important part and the reason for the fancy vulnerability name that we all, you know, naming a vulnerability is always an art and a science in and of itself, uh, regression. So regression means found and fixed and reopened. And that's what's happening here as well. So not only is this an OpenSSH vulnerability, which is particularly bad, uh, but this is a fault somewhere in the, in the supply chain that resulted in a vulnerability being opened, introduced, opened, found, closed, and then reopened and rediscovered, uh, and recapped.

**Chris Romeo (2:42)**: Yeah.

**Matt Coles (2:42)**: So that in and of itself is interesting, but it brings up some interesting questions about the nature of security updates, applying updates, keeping on the latest and greatest, bleeding edge versus, you know, a known working configuration. And also, you know, who, who should have caught that, right? Is that QA's job? Is that pen tester's job? This was found rediscovered by two pen testing teams. Well, actually, I should say one, folks over at Qualys Research discovered it, but at the same time, there was a university, actually, which university was, also rediscovered it. The OpenSSH vulnerability notice does have, does credit both sets of researchers for finding or rediscovering this issue. But who should have found it first, right? That's really the, The big question.

**Chris Romeo (3:35)**: Well, and, and this isn't the first time that a bug has been, air quotes, fixed and then reappeared. Like, I mean, it's, it happens literally thousands and thousands of times inside of big companies where things come back around and it could be an integration problem where depending on how you're building software, You know, branches could be a branch overwrite, things like that happen all the time. Much more than gets advertised.

**Matt Coles (4:08)**: Merging is really challenging sometimes.

**Chris Romeo (4:11)**: Yeah, especially in non-DevOps-y kind of worlds where you're dealing in bigger changes. Like, it's one thing if you're changing 2 lines out of 2 million lines, there's unlikely you're going to get a hit, but when you're doing some type of a You're creating a new software version and you're releasing once a quarter and you have 5,000 developers all working in branches that are slowly getting merged up into trunk branches and the train, they start to consolidate in the station. There's invariably going to be some, something's going to get lost in that process and whatnot. So it does happen. We just don't, very seldom does it, is it in a magnitude vulnerability like this, which, what was the, what were the scores on this? Is this a 10.0?

**Matt Coles (4:59)**: No, it's an 8.1. It has some mitigations built in and it is a timing issue. It's a race condition.

**Izar Tarandach (5:05)**: It's a race condition. Race conditions are very, very hard to get all that.

**Chris Romeo (5:08)**: I mean, yeah.

**Izar Tarandach (5:10)**: Even reading the article, I get it.

**Matt Coles (5:12)**: Yeah. On the, on the plus side, it's all there. And then if you have ASLR enabled, you have some built-in defenses. I mean, for whatever that's worth.

**Chris Romeo (5:19)**: What is ASLR? I'm curious.

**Matt Coles (5:21)**: Uh, address space layout randomization, for those who don't know, uh, is a means for helping when, when you have a buffer overflow to help prevent remote code execution. Uh, it randomizes the addresses of your return pointers.

**Chris Romeo (5:33)**: Makes it much more difficult for an attacker to get a single exploit to work, uh, over—

**Matt Coles (5:40)**: Repeatedly.

**Chris Romeo (5:41)**: Yeah, repeatedly because things are always moving around. Okay. So do you want me to shut this whole thing down so we can just wrap up the episode? Let's try: The year is 2024. Why the heck does SSH still exist? Oh no, no, no, why? No, you are not going to give me a good reason in a cloud native world why I would ever need to start sshd on a machine and somehow give somebody access into it. In a cloud-native world?

**Izar Tarandach (6:15)**: I'm going to tell you that perhaps it's not the best thing today, but it is definitely something that you still need running around and having access to because when everything else fails, because your IDP failed, because something in the middle failed, some— there are the answers to SSH in my experience so far. Have too many moving parts that in the middle of an incident, when you absolutely need to get to a box, that's the time when they fail.

**Matt Coles (6:50)**: So, so help me understand what is, what are the alternatives? Because from what I, from what I can recall, we have VNC, Telnet, but neither of those are really good options. Big fan of Telnet and Telnet back. If not SSH, then what?

**Izar Tarandach (7:08)**: There's a bunch of—

**Chris Romeo (7:10)**: go ahead, go ahead.

**Izar Tarandach (7:10)**: No, no, you're going.

**Chris Romeo (7:11)**: Okay, cloud native, right? So we're thinking cloud native world here, right?

**Matt Coles (7:15)**: You are, you are.

**Chris Romeo (7:17)**: I have access to—

**Matt Coles (7:17)**: I'm thinking about the scope of all Linux machines.

**Chris Romeo (7:22)**: Okay, but in a, so let's, cloud native world in a modern application, you can access console services if you are still running in a console. Please don't tell me you SSH into your containers because then I will just have to, we'll have to, this will have to be called the insecurity table or the unsecurity table, right? I mean, people did that. Remember in the beginning of containers, people were like, we have to add SSHD so we can SSH into the container. Like, no, no, you don't understand. The essence of a container is if you don't need it, if it's broken, you just destroy it and make another one pop up. You don't ever try to fix it. But like in a, let's just talk containerization, orchestration, Kubernetes, containers running inside of an orchestrated environment through a, through a modern day cloud provider. If, even if I did have a box like an Amazon EC2 for some reason in my architecture, I still wouldn't SSH to it over the public internet. I would use the cloud provider's tooling. To be able to access the console of that device through a protected channel, which has been battle-tested and hardened and everything else. And so I don't see a world where I use SSH. I don't use SSH anymore.

**Izar Tarandach (8:38)**: So I see two problems with that.

**Chris Romeo (8:38)**: I used to, I've used it for decades, but I don't anymore because I just don't have any use cases for it.

**Izar Tarandach (8:43)**: I see two problems with what you just put on the table.

**Chris Romeo (8:46)**: Okay.

**Izar Tarandach (8:46)**: First, many of those still use SSH under the hood. And second, battle-tested, that's a, a, a, a appeal to authority fallacy. Just because it's Amazon doesn't mean that it was battle-tested. Amazon still has its problems.

**Chris Romeo (9:03)**: Of course, but it's been, but it's been used at scale by thousands and thousands of customers. And so it's been tested by attackers over and over again. And there is not an exploit available that I'm aware of today that gives me full access to an Amazon or I'm not even, we don't even have to say Amazon. It could be Google, it could be Microsoft. It doesn't matter. Large cloud provider has thousands of customers that have been running thousands of applications for thousands of years total.

**Izar Tarandach (9:36)**: It's a very strong probability, but let's turn the clock back a bit. Millions and millions of people use every day Windows 95. Therefore, Windows 95 is a secure operating system.

**Chris Romeo (9:52)**: Millions of people use Windows 95.

**Izar Tarandach (9:54)**: No, I'm bringing the clock back a couple of decades.

**Chris Romeo (9:57)**: Okay.

**Izar Tarandach (9:57)**: Okay. So that's basically saying the same thing.

**Chris Romeo (10:01)**: That was before Microsoft found security though.

**Izar Tarandach (10:05)**: Yeah. But again, what you say is a very, very, very strong probability of being right.

**Chris Romeo (10:10)**: The timeline.

**Izar Tarandach (10:11)**: But I don't accept it as an absolute.

**Chris Romeo (10:13)**: Okay. But the timeline. Of course, nothing, I mean, nothing is 100% secure. I'm just saying that it has been tested. And so I put more trust. Okay. I'll put, I'll, here's a, here's a premise for you. I put more trust in the large cloud providers console access than I do in SSHD today from OpenSSH, just based on track record and history.

**Matt Coles (10:40)**: Well, I will highlight that. So OpenBSD, the organization, if I remember correctly, the OpenBSD was the organization that produced OpenSSH, and they have an exceedingly great track record of security vulnerabilities, especially in remote security vulnerabilities. To have this show up in SSH multiple times is, uh, is really a black mark on them or the maintainers, and I hope they get their act together. I will give you that in a cloud-native world, You're probably right that SSH is less prevalent, uh, less important, and therefore not as, as impactful. But there's a ton of systems out there, legacy systems, non-cloud native systems, edge devices, consumer devices, other things that have a need for SSH to exist so that you can do remote access, so you can do remote management. Uh, where all of those things are going to be, are potentially impacted by this and hopefully they're getting patched. Let's hope that that's happening.

**Chris Romeo (11:46)**: So basically your premise is OpenSSH is important for legacy, for things that are important for anything that is not cloud native.

**Matt Coles (11:57)**: Certainly. If you're not in Kubernetes and, but if you are in Kubernetes, you're using, you're using SSH to manage your Kubernetes.

**Izar Tarandach (12:05)**: SSH is important as a common denominator.

**Matt Coles (12:07)**: It's a secure shell. That's it. That's the goal.

**Chris Romeo (12:12)**: But if it's a common denominator, then we should have invested more time and money into its overall security stance. Well, should we open— I mean, listen, do we want to open the can of worms of funding of open source projects? I started in security and system administration in the early '90s. I've used SSH since the very beginning. And it's, it has had a pathway of high, high severity, critical level remote code execution vulnerabilities. I can't remember the, I can't remember what they're all, the names of them all, but I just remember patching SSH a lot over its lifetime, over the lifetime of using it.

**Matt Coles (12:51)**: And so, because they made, because they've been maintaining it very well, right? Patches are not coming out reactively. They're coming out proactively.

**Izar Tarandach (12:57)**: And they are a big target because it is, I never get that word right, ubiqui—

**Matt Coles (13:02)**: ubiquitous.

**Izar Tarandach (13:04)**: It's everywhere. It's just everywhere.

**Matt Coles (13:06)**: Yes, it is. It's in every Linux distro. And many Windows systems have SSH installed.

**Chris Romeo (13:11)**: Isn't there something better? Isn't there something better that we could do that would take out—

**Matt Coles (13:17)**: Is there? That's the question.

**Chris Romeo (13:19)**: Yeah. I mean, but that's, if— There's gotta be something, there's gotta be a bit something better. There's gotta be a better way to do other than I get legacy, but legacy will go away eventually. Hopefully, never seems to though.

**Matt Coles (13:36)**: That's the problem.

**Izar Tarandach (13:37)**: Look, even if you look at the virtual KVMs and stuff like that, again, some of them use SSH. I won't say most of them, but some of them, they build their technology on top of SSH. Like they offer all the bells and whistles, but it's on top of SSH because everybody trusts SSH.

**Matt Coles (13:54)**: And SSH has a ton of capability with, with, if you add PAM to it, right? If you have pluggable authentication modules, although I don't think PAM is used anymore. Maybe it's systemd.

**Izar Tarandach (14:04)**: No, it is. It is.

**Matt Coles (14:06)**: Uh, but you have, you have the option of certificates and passwords if you want it. One-time passwords, multi-factor authentication, RADIUS.

**Chris Romeo (14:17)**: The only challenge is though, when there's a remote code in Poland. When there's a remote code execution, it never calls the PAM module or the certificate checker or anything else. It just goes right to the source and runs the code.

**Matt Coles (14:30)**: Well, that's because this is a pre-auth vulnerability. This is a pre-auth vulnerability. So it happens before the authentication flow happens.

**Izar Tarandach (14:35)**: So if we're going to throw away everything that has an RC, we're going to be standing with VI in our hands.

**Chris Romeo (14:41)**: Awesome. I love VI.

**Matt Coles (14:45)**: VI or life.

**Izar Tarandach (14:46)**: That's life. No, but seriously, so, okay, so now comes the question. Vulnerabilities are a fact of life. If you are a high-profile target and SSH is as high as they come, you will be scrutinized. There's been a history both of vulnerabilities and of fixing from SSH. Most people enjoy a certain level of trust and belief in SSH. What makes SSH different from all the rest of all the other stuff that keeps having even worse vulnerabilities coming out every day? Is it because, again, as we spoke so many times, SSH is a security utility in the sense of power and water, not utility as a tool?

**Chris Romeo (15:38)**: I think the challenge with it is it always leads to root access.

**Matt Coles (15:45)**: No, no.

**Chris Romeo (15:46)**: Well, can you, you can't run, but you can't run SSH. You can't run. Can you run SSHD as a non-privileged user? Like, could you run it in such a way that you, Matt, run a copy of SSHD that's tied to your, so you never need, uh, full system access or you never need root access. The shell.

**Matt Coles (16:06)**: So you, okay.

**Izar Tarandach (16:07)**: Wait, When we say SSHD, there's the official one, there are smaller versions that you can definitely run on a non-privileged port with your own UID, and those will connect only you. They are much more limited. They are not the official SSHD, so they don't come under the same scrutiny. So yes, it's possible to jail, I guess, an SSHD implementation.

**Matt Coles (16:32)**: And actually with— with SELinux and other, and, and jails on, on FreeBSD, for instance, you can restrict what resources SSHD has access to.

**Chris Romeo (16:41)**: Yeah. Yeah. But does anybody, has anybody successfully used SELinux? Well, in a commercial context.

**Izar Tarandach (16:46)**: Oh, wait, wait, wait, wait.

**Matt Coles (16:48)**: So you're opening, you're opening yet a different can of worms.

**Chris Romeo (16:51)**: Listen, we've been off for a couple of weeks. Okay. I've had a lot of thoughts.

**Matt Coles (16:55)**: And oh, by the way, Kubernetes, if I recall correctly, relies on SS, on, uh, SELinux and other, and other, um, Yeah, but you don't have to, you don't have to administer it.

**Chris Romeo (17:03)**: That's somebody else figured out. Well, you have to finally, you do have to administer it.

**Matt Coles (17:07)**: It is your responsibility.

**Chris Romeo (17:08)**: No, no, no, not, not anything Kubernetes is doing with SELinux. You're not, there's no way that the administrator for Kubernetes is changing SELinux parameters. You have to have a PhD just to even consider it.

**Izar Tarandach (17:21)**: No, SELinux in learning mode is one of the funniest things that you ever see going through your, uh, your system loves it.

**Matt Coles (17:30)**: The point was, can nothing end up putting the system into enforcing mode and have everything stop?

**Izar Tarandach (17:34)**: Oh yeah, yeah, yeah, no, I'm sure that I have had some Linux boxes in the past look at me and say, what do you want from me? Why, why, why are you doing this to me? Why? Why?

**Matt Coles (17:44)**: Why?

**Chris Romeo (17:44)**: That's been my experience whenever I tried to use SELinux. It's like you turn it on in that watching mode. You're like, ooh, look at all the cool things that it's going to do.

**Izar Tarandach (17:51)**: Yeah, look at all the pretty permissions.

**Chris Romeo (17:53)**: And you're like, oh, I can't even type on the keyboard anymore. This is cool.

**Izar Tarandach (17:58)**: It's like you put it in learning mode and you let it run. And then you look at the box and say, okay, you learned it, right? So now let's enforce.

**Matt Coles (18:06)**: So, so here's a perfect use case for AI. Is that what you're saying? Oh my God.

**Chris Romeo (18:11)**: Figure out the SELinux policy that doesn't lock me out of the machine every time.

**Izar Tarandach (18:19)**: So, okay. So we, we, we go back then to the thing that we were asking offline. Where's the QA in all this? Is it QA?

**Matt Coles (18:26)**: Is QA's responsibility to find regressions? So even take it, take it out of SSH's hands for a moment. Who should be finding regressions? How, how do regressions happen?

**Chris Romeo (18:38)**: What is this QA thing you talk about?

**Izar Tarandach (18:42)**: When a bug daddy and a bug mommy love each other very much, then they commit And it's the wrong commit and you get a regression.

**Chris Romeo (18:55)**: Uh, but no, I mean, honestly, what is the QA world look like these days? Like a lot of, a lot of people don't have QA anymore. QA has gone away in a DevOps-y kind of world where developers are supposed to be doing their own testing and automation testing is supposed to be ruling the way that we release software. And so QA seems like it is becoming a lost art.

**Izar Tarandach (19:26)**: Once upon a time, every developer had that Gandalf QA person that would not let them commit. Thou shalt not commit because they kept like bringing back edge cases and bits and corners that they forgot to code for.

**Matt Coles (19:42)**: There's a whole— there's a whole theory around QA testing, right? Positive cases, negative cases, boundary cases.

**Izar Tarandach (19:48)**: There's a whole basket of cases and, you know, it's—

**Matt Coles (19:52)**: That's what QA becomes when you end up over here.

**Izar Tarandach (19:55)**: So everybody loves to hate on QA, right? And yeah, I'll hand to the sky, I used to. I'll be the first one to say so. But at some point, I I started looking around and saying, wait, there was a function around here called QA. Where have those guys gone? And when you had a good QA person, they usually were very, very good. And they knew the system inside and out, every single bit, every single skeleton.

**Matt Coles (20:26)**: Where are those people? Well, I can tell you personally, as somebody who used to do QA, I joined the security team.

**Chris Romeo (20:35)**: That's where they all went. I was wondering.

**Matt Coles (20:40)**: Interesting.

**Chris Romeo (20:42)**: No, it's, uh, it's QA is definitely an art form and I've found QA people to be some of the best threat modeling people because they have a breaking and critical thinking mentality and they also tend to do their job well have to understand the system, what you just mentioned. They have to conceptualize how everything fits together, and then they can start to come up with scenarios that sometimes developers can't see because they're looking at this little piece and the QA person was looking at the whole, everything that was around it. So, I mean, I miss QA.

**Izar Tarandach (21:19)**: But, but, but they need to do a, a, a jump in the mindset there because apparently OpenSSH missed QA too. Apparently.

**Chris Romeo (21:26)**: Oh, that's the beauty.

**Matt Coles (21:30)**: But send hate mail too.

**Izar Tarandach (21:34)**: But QA people, some of them, any of them, used to test per spec, right? Okay, this is the spec, the thing is doing what the spec says, so the thing is good. I think that those that came to security and those that are good threat modelers were those that took the next step and said, Okay, outside the spec, if we turn on the gorilla and bang the keyboard many times repeatedly on a full moon, this thing breaks. Those are the ones that I really miss. Where have those people gone?

**Chris Romeo (22:08)**: All right, well, we have to reach some conclusions here. Like, what's our conclusion?

**Matt Coles (22:11)**: They were replaced by a very small shell script that runs a fuzzing utility.

**Izar Tarandach (22:15)**: Right? And no, and don't even get me started on, on developers and unit tests and how they like to write tests and then to code to tests and things like that.

**Matt Coles (22:28)**: And no, that's not—

**Chris Romeo (22:29)**: remember development?

**Matt Coles (22:30)**: I was going to say, yeah. Do you remember test-driven development?

**Chris Romeo (22:33)**: Still around?

**Izar Tarandach (22:34)**: Oh yeah.

**Chris Romeo (22:34)**: Still, it's still floating around in some languages. It's more prevalent than others.

**Izar Tarandach (22:38)**: Wasn't it part of XP? Uh, oh, do I express XP in the same?

**Chris Romeo (22:42)**: Yeah. Uh, Windows XP.

**Izar Tarandach (22:43)**: No, no, no, no. This time is extreme programming. Well, twice the same acronym, different meanings, same episode.

**Chris Romeo (22:49)**: Welcome to technology. So we got to draw some conclusions here. So, um, if I can conclude based on our discussion, we're just going to get rid of SSH.

**Matt Coles (22:59)**: Perfect.

**Chris Romeo (23:00)**: Good conclusion.

**Matt Coles (23:00)**: And all the world comes crashing down because everyone, because everyone needs shell access. So they go to Telnet.

**Chris Romeo (23:08)**: Wait, everyone needs shell access. Why does everyone need shell access?

**Matt Coles (23:12)**: I'm kidding. Not everyone needs shell access, but those who do need it. When you need it, you need it.

**Izar Tarandach (23:19)**: I wish everyone needed shell access. Back in those days, people knew what the system was doing. It wasn't just like a bunch of connect the dots programming APIs and libraries, and I have no idea what's going on under the hood. And if I need this thing to move faster, I'll just put bigger iron on it. I miss when people used to pay attention to what's happening in the shell.

**Matt Coles (23:47)**: So we need to get rid of SSH in cloud-native environments. We need to get QA back into their desk and their job functions.

**Izar Tarandach (23:59)**: Actually, question. There must be some obscure tool out there that's going to be SSH next generation and it's made of 1,000 modules written in Rust with a front in Go and something shiny on top of everything. Is there? Have you guys heard of anything like that?

**Matt Coles (24:20)**: If there is, that would be awesome. Let's, uh, let's, let's be on the search, be on the lookout for it. Anyone has any suggestions?

**Chris Romeo (24:26)**: I mean, I think it's an architecture solution is how we get to the next generation and it's an architecture that started back in the '90s of separating things and administering things in a controlled way versus an open way of saying, we're just going to use the internet as our, as our pathway to everything.

**Matt Coles (24:51)**: Well, OpenSSH doesn't require the internet. You're opening yet another can of worms about how exposed are these systems. It doesn't.

**Chris Romeo (24:59)**: What do you mean? It doesn't use IP? Like you can use something other than IP?

**Matt Coles (25:03)**: It uses IP, but it does not require you to be publicly facing on the internet.

**Chris Romeo (25:08)**: Sure. Yeah. Yeah. So just like any, any other service. Yeah. Yeah. No, I wasn't, but what I would—

**Matt Coles (25:12)**: And what I would say is, if you show up in Shodan, uh, you've done it wrong.

**Chris Romeo (25:17)**: Yeah. Yep.

**Izar Tarandach (25:18)**: Totally.

**Chris Romeo (25:18)**: Which, but that's the, it's, it's easy to show up in Shodan though, with SSH, the SSH default stance is people maybe that don't understand it as well as we do run it in a public way so that it's accessible on the public internet.

**Matt Coles (25:35)**: But it's not just SSH then. I mean, you're running SSH, you potentially have Telnet, you potentially have ICMP because you're not running a firewall and you're not blocking on the internet.

**Chris Romeo (25:45)**: Telnet doesn't exist anymore. Let's, let's, I mean, in, in the modern world, like, yeah, hopefully you don't, you don't scan for Telnet. ICMP is a debugging protocol at the end of the day, right? Like it doesn't give you any— Ping.

**Matt Coles (26:01)**: It's ping.

**Chris Romeo (26:02)**: Yeah, yeah, no, but I mean, it was created for debugging. It doesn't, I don't have access to some data.

**Matt Coles (26:08)**: I guess what I mean is, if you have a default configuration and you're not running a firewall and your network is internet-facing and you're allowing inbound connections, you probably have more than SSH on a server exposed.

**Chris Romeo (26:21)**: Yeah, I see.

**Matt Coles (26:22)**: You may have, you may have etcd and you may have, uh, the Kubernetes API exposed in fact, as we've seen in the past. Yeah. So it isn't just SSH that you have to worry about at that point.

**Izar Tarandach (26:34)**: Quick look at the alternatives to SSH. The only thing that's even remotely usable is that place that likes to divide everything into 4, they give us an alternative to SSH. They give you, what's it called? Privileged Access Management.

**Matt Coles (26:57)**: Oh, PAM.

**Izar Tarandach (26:58)**: Yeah.

**Matt Coles (26:58)**: But different PAM.

**Izar Tarandach (26:59)**: Oh, a different PAM. Oh, different PAM.

**Chris Romeo (27:01)**: Oh, two acronyms.

**Matt Coles (27:02)**: Yeah.

**Chris Romeo (27:02)**: Yay.

**Izar Tarandach (27:03)**: We're on a roll today.

**Chris Romeo (27:06)**: Yeah. All right.

**Matt Coles (27:06)**: We have to wrap it up.

**Izar Tarandach (27:07)**: All right.

**Chris Romeo (27:08)**: Well, we'll have to, we'll just have to, we'll have to continue to monitor the situation and and see what happens. Hopefully—

**Izar Tarandach (27:14)**: So bottom line, everybody keep using SSH, but patch it.

**Matt Coles (27:18)**: Patch it. Put a firewall. Don't make it internet-facing.

**Chris Romeo (27:23)**: Or, and look for an alternative. And someone invented an alternative that doesn't have the same legacy challenges that exist with SSH.

**Izar Tarandach (27:32)**: Interesting.

**Chris Romeo (27:33)**: Well, we got to wrap it up. So once again, thank you for joining us around the security table. Shout out to our friends in Australia. Can't remember if it's Northern or Southern Australia.

**Izar Tarandach (27:44)**: Treadmills.

**Chris Romeo (27:45)**: Keep on treadmill. People in Raleigh, everybody else out there. Uh, we'll see you again soon for another episode of Security Tales.

**Matt Coles (27:54)**: Security Tales.

**Izar Tarandach (27:55)**: Dun dun dun.
