# Philosophizing Cloud Security

URL: https://securitytable.ai/philosophizing-cloud-security/
Published: 2024-09-11
Duration: 1720 seconds
Season: 2
Episode: 26
Hosts: Chris Romeo, Izar Tarandach, Matt Coles

## Show notes and chapters

In this episode of the Security Table, our hosts discuss the concept of the 'Shared Fate Model' in cloud security. The conversation explores how this model builds on the shared responsibility model and the implications for cloud service providers and consumers. From robust default security measures to the historical evolution of ISPs, the discussion covers technical and philosophical aspects of cloud infrastructure security. Join us for an informative and engaging session filled with the past and present of internet connectivity and cloud service security.

  
  

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

**Izar Tarandach (0:09)**: And I think the verdict is we may actually be recording.

**Chris Romeo (0:14)**: Stand by.

**Izar Tarandach (0:16)**: I told you to reboot your router.

**Chris Romeo (0:20)**: So actually, I just want to let everybody know that this is the Security Table and we just rebooted the internet. So you may have noticed an outage for a short little period of time, but, uh, we are back now and, uh, ready to discuss many things, even though I feel like we've already discussed many things as we were trying to figure out how to get this thing to record. Okay. The first item on the agenda slash docket is an article that is entitled, What Is the Shared Fate? Model.

**Matt Coles (0:55)**: And in this article, in this article, Matt Koltz is our Chandash and Chris Romeo.

**Izar Tarandach (1:01)**: Oh, thank you for how everybody knows us by now.

**Matt Coles (1:04)**: Come on.

**Chris Romeo (1:05)**: Yeah, we're, we're, we're, we're huge in Australia too, by the way. Uh, Matt, this was your, your, I think you're, you found this article here. Why don't you set it up for us? I mean, shared fate. What are we even talking about here?

**Matt Coles (1:18)**: Uh, it's a good question. What are we really talking about here? So as everyone knows, there's a shared responsibility model, supposedly for cloud, right? Cloud services, you're borrowing somebody else's computer and using it for your stuff. And apparently people who, people who post those sort of things don't want to do everything themselves. So they implemented a shared responsibility model. You have a responsibility when using cloud services. to do certain things because they can't control everything. And that makes sense. You don't want them to control everything. If they did, you'd never have access to encryption keys and they'd have the ability to, you know, take your data away. Who knows what else? But I think that there's an understanding now that the cloud is hard and expensive and it's Well, okay, things, maybe there's some ice in there. I don't know. Maybe there's a lot of hail. And so, uh, it's really, it isn't just responsibility anymore, but now you also share the same fate as, as a cloud service provider. So if, for instance, if you're relying on the cloud to manage, uh, uh, file streaming or video or audio streaming or something like that to remote participants. If a cloud goes down, so do you.

**Chris Romeo (2:41)**: It is.

**Matt Coles (2:43)**: And so you're in the same, you have the same fate as the cloud provider. You can't escape it. You're relying on their services.

**Izar Tarandach (2:52)**: Okay, how's that different from an ISP?

**Matt Coles (2:56)**: Good question.

**Izar Tarandach (2:57)**: I'm always dependent on whatever is beyond my router, right? My modem, I don't know what it's called this week.

**Chris Romeo (3:03)**: I miss ISPs, right?

**Izar Tarandach (3:06)**: They were cool.

**Chris Romeo (3:06)**: Remember ISP used to be such a big part of our lives.

**Matt Coles (3:10)**: We all have ISPs here, right?

**Chris Romeo (3:11)**: You don't have any relationship with them anymore. Like in the '90s, you know, their names in the '90s, you like, we used to have one in my hometown that, uh, the building is still there where they, where they were set up. Uh, the name is slipping me at the moment, but it was a dial-up provider. And they literally had a tech support in like a, in a building. So you could actually drive to their building or, or stop by or whatever to see what was going on. Hey, what's happening with the internet today? It was just a kinder, gentler world back then.

**Matt Coles (3:41)**: Yeah, we had, uh, we had, we had EarthLink and they provided, you know, all, all basic services and everything like that. I mean, so it was like, it was a lot like Google, uh, in that regard, except for they, they also provided internet access, you know. Dial-up and then DSL and finally, oh man, DSL. I still have all those little, little phone adapters and what's to get for DSL lines.

**Chris Romeo (4:05)**: Okay. So what was your, so everybody here started with dial-up, right? Yeah. What was, what was your first modem? What speed was your first modem?

**Izar Tarandach (4:12)**: Uh, 1200.

**Matt Coles (4:14)**: 300.

**Chris Romeo (4:15)**: 300, Matt, old school.

**Matt Coles (4:17)**: Well, well, so my first computer was, my first computer was not mine. It was my, my My dad's here, used to work at Digital Equipment Corporation and he had a VT-100. So he had a dial-up modem.

**Chris Romeo (4:32)**: So you, yeah, okay, we're not even going to go there with what you were connecting to and what computer you were actually using.

**Matt Coles (4:38)**: Yeah, well, yeah, we're terminal services, right?

**Chris Romeo (4:40)**: So 300 baud, I think.

**Matt Coles (4:44)**: You can walk to the data center faster than connecting with 300 baud., and it was, and it was a green, it was a green screen terminal, you know, the clicky keyboard. Yeah, it was awesome.

**Izar Tarandach (4:54)**: But what, at one point I upgraded to a VT220, which was already orange.

**Chris Romeo (5:00)**: Ooh, fancy.

**Matt Coles (5:01)**: You could get simulators now for you so you could reproduce that behavior in your, your—

**Izar Tarandach (5:05)**: you never seen my terminal, right?

**Chris Romeo (5:07)**: All right. So dial up. All right. Did either of you have ISDN?

**Matt Coles (5:13)**: No. Okay.

**Izar Tarandach (5:14)**: I was trying to remember the, the 4 letters. I did.

**Matt Coles (5:16)**: At, at school, yes, but never—

**Chris Romeo (5:17)**: do you remember, remember ISDN? You could have, it was basically basically two phone lines. And so you could, you could literally pick up the phone and talk to somebody and your, and your, your connection would drop down to, I don't remember what the speed was at this point.

**Matt Coles (5:32)**: Was it even 100? Remember that time people would get two phone lines in their house so that one person could be on the computer?

**Chris Romeo (5:38)**: Oh, I had, actually, I had two phone lines. I had a, I ran a BBS, uh, in my house. So I did not have two lines.

**Izar Tarandach (5:47)**: I did not have two lines. I had a very pissed off girlfriend.

**Chris Romeo (5:52)**: She couldn't get in touch with you. But look, but look what it did for your career.

**Matt Coles (5:58)**: True.

**Chris Romeo (5:59)**: See, if you hadn't been a nerd that was playing on the computer, dialed into things all the time, you wouldn't be, uh, outfitting. Product placement is a— we're big on product placement here on the Security Table. Okay.

**Izar Tarandach (6:13)**: But maybe I'll do some cool equipment.

**Matt Coles (6:15)**: Okay.

**Chris Romeo (6:15)**: So. And then from ISDN, so two of us had ISDN and then DSL was next. Uh, yep. Before cable, I think DSL. I had DSL before cable.

**Matt Coles (6:24)**: DSL and cable. Yeah.

**Chris Romeo (6:26)**: Because cable wasn't a thing yet when DSL first came out, at least in the Northern Virginia area.

**Matt Coles (6:30)**: Yeah. Never, never got, never got cable. Had fi— had, uh, fiber up there.

**Chris Romeo (6:36)**: So you went for right from DSL to fiber. Nice. Wow. Fancy. Okay. So we're all up with all, so that's the history of our ISP and internet access.

**Matt Coles (6:48)**: Went from 56K to 10, 10 meg.

**Chris Romeo (6:52)**: 10 meg. And I mean, remember T1s? 1.5 megabits per second. Like we all wanted it. I remember we, we got a T1 at the, at the college I worked at back in '92, I think is when we went live with it. And it was like, I met like imagining, oh, what if I could have this at home? Imagine the bandwidth, but oh, it's like $25,000 a month in 1992 for 1.5 megabit per second.

**Matt Coles (7:21)**: So, so I was in, I was in college. We had a T1, we had an Odyssey T1, you know, to the college, must've been more than a T1 because I'm sure they were like a hub, you know, one of those research centers and but in the dorms we'd get fractional T1 speeds. I remember playing a text-based mod, remember playing a text-based mod with like 1,000 other people around the world and you'd still get lag. You type, you type on the keyboard and you'd be like, hey, shit, shit, shit, shit, shit, shit, can't wait. Of course, if everyone ever, if anyone has ever played a text-based mod, especially one that is, uh, is more of like, you know, you go into a room and there's fight, you know, it's like a little dungeon kind of thing. You're fighting a monster and the screen stops scrolling and you don't know if your character's still alive or dead.

**Izar Tarandach (8:11)**: So I had the T1 on my first startup and I wanted a piece of that, especially in the evenings. And because there was a, uh, uh, the phone was behind the central, I couldn't like put a modem and call the mo— the, the phone and use it. So I actually had the modem program to call my home at a certain time. So I had to run home to pick up the phone to connect back up with him to make the connection for the night.

**Chris Romeo (8:36)**: I love it.

**Matt Coles (8:37)**: Wait, that's the first callback. Is that the first callback system?

**Izar Tarandach (8:40)**: That's, that's basically, yeah. I love it. And, and I won't even tell you what I had to do to be able to watch the games in the 1998 World Cup. I actually had to get, uh, uh, a graphics card that could get the signal from the cable company in my house. And then I would call back, connect to the computer there, sit in the office, open a window in my Linux box that had the graphics card, and watch the game there play.

**Matt Coles (9:09)**: Oh, that's right. Graphics cards at that time had, had great, had, uh, TV interfaces. They had coax cable, uh, interfaces or, um, yeah.

**Izar Tarandach (9:17)**: It was a, a Voodoo 2, if I remember correctly.

**Chris Romeo (9:19)**: Oh, I remember those.

**Matt Coles (9:20)**: Did you JCC? You had, you could get 2 cards in the same, in the same system. With a printer, I think.

**Izar Tarandach (9:25)**: You could, uh, bend them together.

**Matt Coles (9:27)**: Yeah. Yep.

**Chris Romeo (9:28)**: This is, this is the Wayback Machine. It's making me remember.

**Izar Tarandach (9:32)**: So back to Shared Fate.

**Chris Romeo (9:34)**: Okay, here's a quote. Here's a quote from the Shared Fate article that I wanted to kind of tee up here. Uh, the Shared Fate model is centered on the customer's needs, where the cloud service provider leverages its expertise to play an active role in the customer's security. This model provides enhanced support for organizations in 3 key ways: enhanced collaboration, actionable steps and guidance and robust defaults for cloud services. So is this really different?

**Izar Tarandach (10:04)**: I don't think so. More to the point, shared fate to me sounds like commiseration time. Let's just sit all around the modem and say how bad things are and how worse they're going to get.

**Chris Romeo (10:18)**: Yeah, like we're all screwed. We're all screwed together.

**Matt Coles (10:21)**: Actually, as you just read that, and as I look at the article again, I wonder, I wonder if the shared fate is not from the perspective of the consumer, but of the cloud service provider. In other words, they want a more active role because in the shared responsibility model, they provide the service and you do everything else, right? You're responsible for making sure that your account is secure. You're responsible for making sure the services you serve are stitched together correctly and that your figure them out really, right? They're just providing you the infrastructure, you know, shared responsibility model. But in the shared fate model, their security depends on you. And in the shared fate model, if they take on more of that partnership, they can steer you in the right direction or give you better defaults. One might argue they should have maybe done that the start with.

**Izar Tarandach (11:09)**: But here comes the question. When you say their security depends on you, Which company in the right frame of mind or in the same frame of mind would ever do that? I mean, it's not like everybody knows how to do security. I don't put my security depending on somebody else that the only relationship that I have is that they pay me.

**Matt Coles (11:32)**: If you're, if you're, if you're a, if you're a small, if you're a small business and you want to, and you just want to get, uh, you know, a site up and running to do ordering and things. You don't want to actually own infrastructure. You want a service provider that provides a lot more, a lot more stuff than just simply a hosting location, right? Yeah.

**Izar Tarandach (11:53)**: But then what's my, what's my relationship with their security? You just gave me a good reason to put all the security stuff on them.

**Chris Romeo (12:01)**: Which is the shared responsibility model.

**Izar Tarandach (12:03)**: Yeah.

**Chris Romeo (12:03)**: Ultimately is what, even though it's called shared responsibility, it's really for a reason. I rely upon the cloud provider to solve my problems.

**Izar Tarandach (12:12)**: But if you think about it, at the different levels of service, you can get like hardware, you can get an OS, you can get an application, you can get a serverless Lambda, whatever. Different levels of interaction with the CSP and different levels of expectation in terms of the security that you are responsible for. That to me is the shared responsibility model.

**Matt Coles (12:32)**: But the shared thing— Well, so the shared fate thing seems like it's coming from the perspective that that's not already happening, meaning that the cloud provider is just providing a hosting solution and you're basically implementing your own security on top of it.

**Chris Romeo (12:44)**: Which is what that, that's what's happening today, at least in my experience. But I'm, I'm on this third bullet point, robust defaults for cloud services. And that one's, I'm starting to see the light a little bit on this, at least on the cloud service providers taking a different approach or strategy, like imagine a world where a cloud service provider forced you to use Secrets Manager and you couldn't, you couldn't generate or release a service that didn't use Secrets Manager to manage its credentials.

**Izar Tarandach (13:18)**: There's nothing stopping me from doing my own solution and using it and just like connecting to the provider's solution to, you know, just check a box or pass their audit or whatever.

**Matt Coles (13:33)**: So yeah, but you wouldn't—

**Izar Tarandach (13:35)**: the CFPB can't enforce that.

**Matt Coles (13:36)**: If, well, they can lock down the APIs that you use. Oh. Because they own them. They own the gateway.

**Izar Tarandach (13:47)**: Why, how could they not?

**Matt Coles (13:49)**: I mean, they—

**Izar Tarandach (13:49)**: I create my own encryption API. How do they know that?

**Matt Coles (13:55)**: Well, certainly if you encrypt the data that before it makes it to the cloud, that's, that's one thing, but within the cloud, or even my own authentication.

**Izar Tarandach (14:02)**: So what, how, what do they know? Now they're looking at my traffic. Now, even worse, now they are understanding my traffic. If they do understand my APIs, that's a great service. Let me know how this shit works because I don't know. But, you know, beyond that, how can you enforce that?

**Chris Romeo (14:18)**: That brings a good question. Can cloud providers see everything?

**Matt Coles (14:24)**: Why, why would you suggest they couldn't?

**Chris Romeo (14:27)**: Yeah, I don't think, that's what I was landing on that. I think, I think they can see everything.

**Izar Tarandach (14:30)**: Wait, wait, wait, wait, wait, wait. There's a difference between seeing and actually understanding and then being able to read or being able to interpret or whatever. They can see everything because it's their pipes, but the thing is going through. Oh, look, another packet. Oh, another, oh, another packet.

**Chris Romeo (14:44)**: But apart from that, but if you do all your, if you do all your certificate generation inside of their certificate authority, then technically they even have the ability to see unless, unless it's hardware backed, unless it's hardware backed.

**Matt Coles (15:02)**: Well, that's the thing.

**Chris Romeo (15:03)**: Why would you use their, their certificate authority?

**Matt Coles (15:06)**: If you're a small business and you don't have your own infrastructure. Of course you would.

**Chris Romeo (15:10)**: I mean, what else are you going to use? Verisign or—

**Izar Tarandach (15:13)**: The guy that wrote, the guy that wrote the application for me, he should be the one saying, no, let's not use the, the PSPs.

**Matt Coles (15:23)**: Because there's a small business. Have you, how many small business developers have you met? Because I'm, I'm pretty sure that they just want stuff to work. I mean, this is why, this is why Squarespace exists, right? This is why GoDaddy has, has website building services.

**Izar Tarandach (15:37)**: Yeah, but at the other side, okay, so, so take Squarespace for example. Great company, worked for it for 2 years, loved it every second. And yeah, you're right. People can go into GoDaddy and Squarespace, not to make it sound like a company thing, and just buy a service, build their site, and so on and so forth. But even given that, what I saw personally, and this is not backed by any kind of data, people will go in, buy the basic package, get their nephew pays the website up, and very quick they would need some other functionality, and very quick they would find somebody to provide that functionality, and very quick they would understand that they need a certain amount of other stuff and start putting that stuff up. So even a small business, they, I think that they feed the even smaller businesses of building those commerce sites for them. If you want to be actually successful in that thing, you have to invest something into it. So my point is that somebody building something like that, cool, let's use the CSP's people's framework or whatever, because it's easy. But if you want to do it right, then you may want to go somewhere else.

**Chris Romeo (16:48)**: I think we went on a tangent that the article didn't actually say here. So the shared fate model suggests the cloud service provider focus on delivering robust defaults for cloud services. This requires cloud providers to build products that are secure by design and by default, helping customers with the toil of securing their environment, not adding to it. So secure by default, cloud service provider providing great secure defaults results in like, I can still change it to an insecure approach if I want to, but the beauty that I've seen in secure by default is it's usually harder for me to have to go reverse engineer, just take away the security control they've applied to put some insecure option in. People are generally lazy. And so if the default is secure, they're not going to go spend and invest the time and money to say, how can I turn this thing back? How can I go from using HTTPS to HTTP? I just want plain HTTP. Nobody's going to do that.

**Izar Tarandach (17:51)**: But help me, help me here. To the way that I see what you just said is that I'm a small business thing or whatever, and I just want myself to work. So I go and I put HTTP here. So now I'm relying that what the CSP at the load balancer thing will say, no, no, no, no HTTP here, only HTTPS. And they'll deal with the whole certificate thing. And no, yeah.

**Chris Romeo (18:17)**: Yeah. So basically if you, so if you add an application load balancer, to a cloud instance, all this is saying is that it should come out of the box set up for HTTPS.

**Matt Coles (18:28)**: Basically, when you deploy a, when you deploy an application, it should come with all the structure in a pre, in a pre-secured state.

**Chris Romeo (18:35)**: And you made a bad decision in your building process to use HTTP. You're going to have to go modify the application load balancer's configuration to make HTTP work. That's all I'm saying.

**Izar Tarandach (18:46)**: Okay. But by necessity, that means that that load balancer will have to have some kind of, uh, way to stand up with already a valid certificate. So, who's going to own that certificate? The CSP or the business?

**Chris Romeo (19:01)**: By default, the CSP might. The CSP generates them and handles the certificate management for you.

**Izar Tarandach (19:09)**: So that's one more—

**Chris Romeo (19:09)**: just like LexiCrypt would.

**Izar Tarandach (19:11)**: That's one more line item for the CSP to take from you. $195 a month for your certificates that you could have done by yourself.

**Chris Romeo (19:20)**: They're pennies. They're pennies. Certificates are dirt cheap now from cloud service providers.

**Izar Tarandach (19:25)**: They are, but it's a chance for them not to be dirt cheap for the small business that's just trying. You see my point here? It's a great way of getting $194.

**Matt Coles (19:36)**: Yeah, but we are, you're a pessimist, obviously.

**Chris Romeo (19:38)**: Yeah, we have, there's so much competition. How many, how many primary cloud service providers are there right now? There's, there's Amazon, AWS, Google. And Microsoft, and then you could say there's some secondary tier, there's probably 100 secondary tier cloud service providers.

**Matt Coles (19:57)**: Rackspace and those things.

**Chris Romeo (19:58)**: Yeah, you could even argue Rackspace might be closer to the big folks than, than some of the other ones are. So I don't have, I don't have a concern that somebody's going to try to price inflate cloud services when certificates are a commodity at this point. Right, right. That's what AWS brought to the cloud environment in the early days is commoditizing all of these things and charging fractions of pennies for things.

**Izar Tarandach (20:26)**: They are for the people who know what a certificate is. For the use case that Matt is, is, uh, describing, certificate schmurf schmurf certificate. They don't know what it is. They just want things to work. You want, you want to put that in.

**Matt Coles (20:40)**: If you get a, if you get a, if you get a site from, from Squarespace, doesn't it come with a TLS cert? As part of the subscription?

**Izar Tarandach (20:48)**: I am not equipped to answer that question.

**Matt Coles (20:53)**: I mean, I'm pretty sure it's at one— I'm pretty sure it's a one-click thing. I'm pretty sure it's a one-click thing. I need an application. I need it to be at this URL. Go do it. And it makes it happen.

**Izar Tarandach (21:02)**: Yes. But now transfer that to the CSP. Now you don't have that one-click anymore. The CSP is just saying, hey, as part of your service, as part of your By the way, here's $100 more on your, on your bill.

**Chris Romeo (21:13)**: But the, the people who want this just to work are not working with a cloud service provider directly. They're working with some third party, to your example, a GoDaddy, a Squarespace.

**Izar Tarandach (21:25)**: That's a good point.

**Chris Romeo (21:26)**: They're not in there trying to figure out certificates. They're just expecting to swipe their credit card for a website. And that's, that, and so that does play back into what this article's saying though. That shared, that website you get from a GoDaddy. Should have a secure default and that it should have a certificate that the, that user doesn't even need to know exists. All they know is the URL is HTTPS to get to it.

**Izar Tarandach (21:50)**: But now who's responsible for that certificate? GoDaddy or the, the, the CSP?

**Chris Romeo (21:54)**: In that point, it's—

**Izar Tarandach (21:55)**: GoDaddy decides who it is.

**Chris Romeo (21:56)**: GoDaddy is the CSP in that environment, right? GoDaddy is effectively running their own data centers, I think. I don't think—

**Matt Coles (22:04)**: Well, even if they're, even if they're leasing it from, from AWS, Right. Let's just say for a moment there's a, there's a relationship there of, of a frontend provider and a backend provider. The frontend provider should be, should be managing that relationship, right? With shared—

**Chris Romeo (22:19)**: transparent.

**Matt Coles (22:21)**: Yeah.

**Chris Romeo (22:22)**: There's no visibility into the backend for, like, if I buy a website on GoDaddy, I don't see AWS ever.

**Matt Coles (22:29)**: Right. And so what's the shared fate model of them? And so we come back to, whose fate is it? So the, the CSP, the CSP taking on more ownership means they have better control and ability to defend their infrastructure. You, you as the consumer, in theory, get some slight, some benefit from that because the more uptime they have, the more uptime you have. And they do more, they take on, they take on more of the responsibility, but it also becomes more of a collaboration. Right? They provide better, they provide more secure defaults out of the box. And if, and they want to collaborate with you to the first point, right? Better collaboration and better service delivery. Because if you don't know what you're doing and you say, oh, I don't need HTTPS, and I turn off the TLS certs, their systems are now at risk and their other customers are now at risk.

**Izar Tarandach (23:21)**: Their systems are at risk because I don't use HTTPS?

**Chris Romeo (23:26)**: Sure.

**Matt Coles (23:26)**: Because traffic can, you know, traffic can be intercepted or modified, right? You, they may, they may—

**Izar Tarandach (23:30)**: it's my traffic.

**Matt Coles (23:32)**: Well, hold on. It may be, though, let's just say for a moment you have a company that's full of lawyers and, and decide that, you know, I lose data. Guess who's getting the first call? The lawyer for this hosting provider that, you know, where your data is stored and has now been compromised. So there's other— there's non-technical reasons for, for this to be a positive for the cloud service provider. Right?

**Izar Tarandach (24:02)**: Yeah, let's put it like this. If it is the way that you guys describe it, then yeah, it's a net positive. I'm still struggling with the shared base here. Like, if I'm a user of the CSP, and my mistakes can bring down the CSP, I probably need a different CSP.

**Matt Coles (24:22)**: Well, not necessarily bring down, let's be careful, right? Taking down a cloud service provider is a hard, is a hard problem just by design, right?

**Izar Tarandach (24:30)**: Then what are we sharing here? What's the fate?

**Chris Romeo (24:34)**: Shared fate is the outcome, right? It's not shared responsibility is more like, it's more like nothing's happened. Shared fate is like admitting something's going to happen here. And so whatever happens, happens to both of us. It happens to you as the provider. It happens to me as the person who's trying to deliver my application.

**Izar Tarandach (24:53)**: But it doesn't.

**Matt Coles (24:53)**: If you, well, to some extent, right? If you get breached, if you get breached, depending on how that breach happens, either your data is lost or the system that's hosted is corrupt.

**Izar Tarandach (25:06)**: And in a good design, that system should be isolated enough so that it doesn't interfere with anybody else's. So what's the threat model here?

**Chris Romeo (25:15)**: I mean, there's been, there's been escapes before. There's been VM escapes, for example.

**Izar Tarandach (25:20)**: And you escape to the host. Now what?

**Chris Romeo (25:23)**: If you're, but if you're on the host, if you escape, if you do a VM escape inside of a cloud provider, aren't you at the cloud provider's infrastructure? If you're at the host, don't we have that whole VPC thing and whatnot and It's still shared services. It's got to break down somewhere. If you can—

**Matt Coles (25:42)**: No, no, no, no.

**Izar Tarandach (25:44)**: And all that good stuff.

**Chris Romeo (25:46)**: I, I mean, if you break out the—

**Matt Coles (25:48)**: just depends on how the tenancy model is done, right? It depends on whether you're given, it depends on whether you're given exclusive access to a collection of CPUs.

**Izar Tarandach (25:58)**: So now I'm interfering with a different tenant, but still not the CSP, but that, that reflects badly on the CSP.

**Chris Romeo (26:07)**: But the CSP is still running a train. There's got to be a way to the CSP if you can escape the VM. If I'm at the host level of the provider, then there's got to be a way to get to the next. And I mean, I don't know that unless you were running in a shared C or in a dedicated CPU mode that you just, I think Matt mentioned, challenge with that is it's uber expensive.

**Matt Coles (26:30)**: Like it's, it might exactly.

**Chris Romeo (26:32)**: Most people don't use it because it's thousands and thousands of dollars per instance per month. But to have a dedicated instance.

**Izar Tarandach (26:39)**: Okay. So you're going to break out and you are now inside their network, but you are inside their operational network. You're not in the backline. You're not in the, at the service level thing. You're not getting ready, getting close to their authentication stuff. There are so many bumps in the road here that is this really a problem? And how is this different from what we have today? Like the shared responsibility model, you can still do all those things. So how is the CSP deciding that from now on everything's HTTPS going to save anybody from this? I'm having a problem with the whole threat model here.

**Chris Romeo (27:18)**: It's less interfaces. If you enforce secure defaults, it's less insecure, potential insecure interfaces for the attackers to have to work with.

**Izar Tarandach (27:28)**: Fair, but I would propose that on a good enough design to be a commercial CSP, he would have done that from the start, included it in your threat model, in your design, and actually have some mitigation and some controls against that kind of thing.

**Chris Romeo (27:44)**: I think you're, I think you're too pie in the sky here. I don't think you live in reality.

**Matt Coles (27:49)**: We're starting to circle here a bit.

**Izar Tarandach (27:51)**: Could be.

**Matt Coles (27:51)**: I need to run.

**Chris Romeo (27:52)**: So, okay. Well, let's, uh, yeah, I mean, we, we, we really, Took a, a, uh, pretty simple article and turned it into a 30-minute deep dive, but it was good. I think it's, it was, this is, this was fun to, to think about the philosophy of the cloud is really where we were here. So we are all officially philosophers now. So you will get a certificate in the mail. It says Cloud Philosopher. That's a, that'll be a picture of Izar doing that pose in the background and it'll go on —t-shirts, Cloud Philosopher. So folks, thanks for listening to another episode of the Security Table. We'll be back next week to talk about some other stuff.
