Leading the Cloud Security Pack with Yoav Alon

• Orca Security: https://orca.security
• Twitter: https://twitter.com/yoavalon

Transcript

Announcer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.

Corey: This episode is sponsored in part by our friends at Vultr. Optimized cloud compute plans have landed at Vultr to deliver lightning fast processing power, courtesy of third gen AMD EPYC processors without the IO, or hardware limitations, of a traditional multi-tenant cloud server. Starting at just 28 bucks a month, users can deploy general purpose, CPU, memory, or storage optimized cloud instances in more than 20 locations across five continents. Without looking, I know that once again, Antarctica has gotten the short end of the stick. Launch your Vultr optimized compute instance in 60 seconds or less on your choice of included operating systems, or bring your own. It's time to ditch convoluted and unpredictable giant tech company billing practices, and say goodbye to noisy neighbors and egregious egress forever. Vultr delivers the power of the cloud with none of the bloat. "Screaming in the Cloud" listeners can try Vultr for free today with a $150 in credit when they visit getvultr.com/screaming. That's G E T V U L T R.com/screaming. My thanks to them for sponsoring this ridiculous podcast.

Corey: Finding skilled DevOps engineers is a pain in the neck! And if you need to deploy a secure and compliant application to AWS, forgettaboutit! But that’s where DuploCloud can help. Their comprehensive no-code/low-code software platform guarantees a secure and compliant infrastructure in as little as two weeks, while automating the full DevSecOps lifestyle. Get started with DevOps-as-a-Service from DuploCloud so that your cloud configurations are done right the first time. Tell them I sent you and your first two months are free. To learn more visit: snark.cloud/duplo. Thats’s snark.cloud/D-U-P-L-O-C-L-O-U-D.

Corey: Welcome to Screaming in the Cloud. I’m Corey Quinn. Periodically, I would say that I enjoy dealing with cloud platform security issues, except I really don’t. It’s sort of forced upon me to deal with much like a dead dog is cast into their neighbor’s yard for someone else to have to worry about. Well, invariably, it seems like it’s my yard.

And I’m only on the periphery of these things. Someone who’s much more in the trenches in the wide world of cloud security is joining me today. Yoav Alon is the CTO at Orca Security. Yoav, thank you for taking the time to join me today and suffer the slings and arrows I’ll no doubt be hurling your way.

Yoav: Thank you, Corey, for having me. I've been a longtime listener, and it’s an honor to be here.

Corey: I still am periodically surprised that anyone listens to these things. Because it’s unlike a newsletter where everyone will hit reply and give me a piece of their mind. People generally don’t wind up sending me letters about things that they hear on the podcast, so whenever I talk to somebody listens to it as, “Oh. Oh, right, I did turn the microphone on. Awesome.” So, it’s always just a little on the surreal side.

But we’re not here to talk necessarily about podcasting, or the modern version of an AM radio show. Let’s start at the very beginning. What is Orca Security, and why would folks potentially care about what it is you do?

Yoav: So, Orca Security is a cloud security company, and our vision is very simple. Given a customer’s cloud environment, we want to detect all the risks in it and implement mechanisms to prevent it from occurring. And while it sounds trivial, before Orca, it wasn’t really possible. You will have to install multiple tools and aggregate them and do a lot of manual work, and it was messy. And we wanted to change that, so we had, like, three guiding principles.

We call it seamless, so I want to detect all the risks in your environment without friction, which is our speak for fighting with your peers. We also want to detect everything so you don’t have to install, like, a tool for each issue: A tool for vulnerabilities, a tool for misconfigurations, and for sensitive data, IAM roles, and such. And we put a very high priority on context, which means telling you what’s important, what’s not. So, for example, S3 bucket open to the internet is important if it has sensitive data, not if it’s a, I don’t know, static website.

Corey: Exactly. I have a few that I’d like to get screamed at in my AWS account, like, “This is an open S3 bucket and it’s terrible.” I look at it the name is assets.lastweekinaws.com. Gee, I wonder if that’s something that’s designed to be a static hosted website.

Increasingly, I’ve been slapping CloudFront in front of those things just to make the broken warning light go away. I feel like it’s an underhanded way of driving CloudFront adoption some days, but not may not be the most charitable interpretation thereof. Orca has been top-of-mind for a lot of folks in the security community lately because let’s be clear here, dealing with security problems in cloud providers from a vendor perspective is an increasingly crowded—and clouded—space. Just because there’s so much—there’s investment pouring into it, everyone has a slightly different take on the problem, and it becomes somewhat challenging to stand out from the pack. You didn’t really stand out from the pack so much as leaped to the front of it and more or less have become the de facto name in a very short period of time, specifically—at least from my world—when you wound up having some very interesting announcements about vulnerabilities within AWS itself. You will almost certainly do a better job of relating the story, so please, what did you folks find?

Yoav: So, back in September of 2021, two of my researchers, Yanir Tsarimi and Tzah Pahima, each one of them within a relatively short span of time from each other, found a vulnerability in AWS. Tzah found a vulnerability in CloudFormation which we named BreakingFormation and Yanir found a vulnerability in AWS Glue, which we named SuperGlue. We’re not the best copywriters, but anyway—

Corey: No naming things is hard. Ask any Amazonian.

Yoav: Yes. [laugh]. So, I’ll start with BreakingFormation which caught the eyes of many. It was an XXE SSRF, which is jargon to say that we were able to read files and execute HTTP requests and read potentially sensitive data from CloudFormation servers. This one was mitigated within 26 hours by AWS, so—

Corey: That was mitigated globally.

Yoav: Yes, globally, which I’ve never seen such quick turnaround anywhere. It was an amazing security feat to see.

Corey: Particularly in light of the fact that AWS does a lot of things very right when it comes to, you know, designing cloud infrastructure. Imagine that, they’ve had 15 years of experience and basically built the idea of cloud, in some respects, at the scale that hyperscalers operate at. And one of their core tenets has always been that there’s a hard separation between regions. There are remarkably few global services, and those are treated with the utmost of care and delicacy. To the point where when something like that breaks as an issue that spans more than one region, it is headline-making news in many cases.

So it’s, they almost never wind up deploying things to all regions at the same time. That can be irksome when we’re talking about things like I want a feature that solves a problem that I have, and I have to wait months for it to hit a region that I have resources living within, but for security, stuff like this, I am surprised that going from, “This is the problem,” to, “It has been mitigated,” took place within 26 hours. I know it sounds like a long time to folks who are not deep in the space, but that is superhero speed.

Yoav: A small correction, it’s 26 hours for, like, the main regions. And it took three to four days to propagate to all regions. But still, it’s speed of lighting in for security space.

Corey: When this came out, I was speaking to a number of journalists on background about trying to wrap their head around this, and they said that, “Oh yeah, and security is always, like, the top priority for AWS, second only to uptime and reliability.” And… and I understand the perception, but I disagree with it in the sense of the nightmare scenario—that every time I mention to a security person watching the blood drain from their face is awesome—but the idea that take IAM, which as Werner said in his keynote, processes—was it 500 million or was it 500 billion requests a second, some ludicrous number—imagine fails open where everything suddenly becomes permitted. I have to imagine in that scenario, they would physically rip the power cables out of the data centers in order to stop things from going out. And that is the right move. Fortunately, I am extremely optimistic that will remain a hypothetical because that is nightmare fuel right there.

But Amazon says that security is job zero. And my cynical interpretation is that well, it wasn’t, but they forgot security, decided to bolt it on to the end, like everyone else does, and they just didn’t want to renumber all their slides, so instead of making it point one, they just put another slide in front of it and called the job zero. I’m sure that isn’t how it worked, but for those of us who procrastinate and building slide decks for talks, it has a certain resonance to it. That was one issue. The other seemed a little bit more pernicious focusing on Glue, which is their ETL-as-a-Service… service. One of them I suppose. Tell me more about it.

Yoav: So, one of the things that we found when we found the BreakingFormation when we reported the vulnerability, it led us to do a quick Google search, which led us back to the Glue service. It had references to Glue, and we started looking around it. And what we were able to do with the vulnerability is given a specific feature in Glue, which we don’t disclose at the moment, we were able to effectively take control over the account which hosts the Glue service in us-east-1. And having this control allowed us to essentially be able to impersonate the Glue service. So, every role in AWS that has a trust to the Glue service, we were able to effectively assume a role into it in any account in AWS. So, this was more critical a vulnerability in its effect.

Corey: I think on some level, the game of security has changed because for a lot of us who basically don’t have much in the way of sensitive data living in AWS—and let’s be clear, I take confidentiality extremely seriously. Our clients on the consulting side view their AWS bills themselves as extremely confidential information that Amazon stuffs into a PDF and emails every month. But still. If there’s going to be a leak, we absolutely do not want it to come from us, and that is something that we take extraordinarily seriously. But compared to other jobs I’ve had in the past, no one will die if that information gets out.

It is not the sort of thing that is going to ruin people’s lives, which is very often something that can happen in some data breaches. But in my world, one of the bad cases of a breach of someone getting access to my account is they could spin up a bunch of containers on the 17 different services that AWS offers that can run containers and mine cryptocurrency with it. And the damage to me then becomes a surprise bill. Okay, great. I can live with that.

Something that’s a lot scarier to a lot of companies with, you know, serious problems is, yep, fine, cost us money, whatever, but our access to our data is the one thing that is going to absolutely be the thing that cannot happen. So, from that perspective alone, something like Glue being able to do that is a lot more terrifying than subverting CloudFormation and being able to spin up additional resources or potentially take resources down. Is that how you folks see it too, or is—I’m sure there’s nuance I’m missing.

Yoav: So yeah, the access to data is top-of-mind for everyone. It’s a bit scary to think about it. I have to mention, again, the quick turnaround time for AWS, which almost immediately issued a patch. It was a very fast one and they mitigated, again, the issue completely within days. About your comment about data.

Data is king these days, there is nothing like data, and it has all the properties of everything that we care about. It’s expensive to store, it’s expensive to move, and it’s very expensive if it leaks. So, I think a lot of people were more alarmed about the Glue vulnerability than the CloudFormation vulnerability. And they’re right in doing so.

Corey: I do want to call out that AWS did a lot of things right in this area. Their security posture is very clearly built around defense-in-depth. The fact that they were able to disclose—after some prodding—that they checked the CloudTrail logs for the service itself, dating back to the time the service launched, and verified that there had never been an exploit of this, that is phenomenal, as opposed to the usual milquetoast statements that companies have. We have no evidence of it, which can mean that we did the same thing and we looked through all the logs in it’s great, but it can also mean that, “Oh, yeah, we probably should have logs, shouldn’t we? But let’s take a backlog item for that.” And that’s just terrifying on some level.

It becomes a clear example—a shining beacon for some of us in some cases—of doing things right from that perspective. There are other sides to it, though. As a customer, it was frustrating in the extreme to—and I mean, no offense by this—to learn about this from you rather than from the provider themselves. They wound up putting up a security notification many hours after your blog post went up, which I would also just like to point out—and we spoke about it at the time and it was a pure coincidence—but there was something that was just chef’s-kiss perfect about you announcing this on Andy Jassy’s birthday. That was just very well done.

Yoav: So, we didn’t know about Andy’s birthday. And it was—

Corey: Well, I see only one of us has a company calendar with notable executive birthdays splattered all over it.

Yoav: Yes. And it was also published around the time that AWS CISO was announced, which was also a coincidence because the date was chosen a lot of time in advance. So, we genuinely didn’t know.

Corey: Communicating around these things is always challenging because on the one hand, I can absolutely understand the cloud providers’ position on this. We had a vulnerability disclosed to us. We did our diligence and our research because we do an awful lot of things correctly and everyone is going to have vulnerabilities, let’s be serious here. I’m not sitting here shaking my fist, angry at AWS’s security model. It works, and I am very much a fan of what they do.

And I can definitely understand then, going through all of that there was no customer impact, they’ve proven it. What value is there to them telling anyone about it, I get that. Conversely, you’re a security company attempting to stand out in a very crowded market, and it is very clear that announcing things like this demonstrates a familiarity with cloud that goes beyond the common. I radically changed my position on how I thought about Orca based upon these discoveries. It went from, “Orca who,” other than the fact that you folks have sponsored various publications in the past—thanks for that—but okay, a security company. Great to, “Oh, that’s Orca. We should absolutely talk to them about a thing that we’re seeing.” It has been transformative for what I perceive to be your public reputation in the cloud security space.

So, those two things are at odds: The cloud provider doesn’t want to talk about anything and the security company absolutely wants to demonstrate a conversational fluency with what is going on in the world of cloud. And that feels like it’s got to be a very delicate balancing act to wind up coming up with answers that satisfy all parties.

Yoav: So, I just want to underline something. We don’t do what we do in order to make a marketing stand. It’s a byproduct of our work, but it’s not the goal. For the Orca Security Research Pod, which it’s the team at Orca which does this kind of research, our mission statement is to make cloud security better for everyone. Not just Orca customers; for everyone.

And you get to hear about the more shiny things like big headline vulnerabilities, but we also have very sensible blog posts explaining how to do things, how to configure things and give you more in-depth understanding into security features that the cloud providers themselves provide, which are great, and advance the state of the cloud security. I would say that having a cloud vulnerability is sort of one of those things, which makes me happy to be a cloud customer. On the one side, we had a very big vulnerability with very big impact, and the ability to access a lot of customers' data is conceptually terrifying. The flip side is that everything was mitigated by the cloud providers in warp speed compared to everything else we’ve seen in all other elements of security. And you get to sleep better knowing that it happened—so no platform is infallible—but still the cloud provider do work for you, and you’ll get a lot of added value from that.

Corey: You’ve made a few points when this first came out, and I want to address them. The first is, when I reached out to you with a, “Wow, great work.” You effectively instantly came back with, “Oh, it wasn’t me. It was members of my team.” So, let’s start there. Who was it that found these things? I’m a huge believer giving people credit for the things that they do.

The joy of being in a leadership position is if the company screws up, yeah, you take responsibility for that, whether the company does something great, yeah, you want to pass praise onto the people who actually—please don’t take this the wrong way—did the work. And not that leadership is not work, it absolutely is, but it’s a different kind of work.

Yoav: So, I am a security researcher, and I am very mindful for the effort and skill it requires to find vulnerabilities and actually do a full circle on them. And the first thing I’ll mention is Tzah Pahima, which found the BreakingFormation vulnerability and the vulnerability in CloudFormation, and Yanir Tsarimi, which found the AutoWarp vulnerability, which is the Azure vulnerability that we have not mentioned, and the Glue vulnerability, dubbed SuperGlue. Both of them are phenomenal researcher, world-class, and I’m very honored to work with them every day. It’s one of my joys.

Corey: Couchbase Capella Database-as-a-Service is flexible, full-featured and fully managed with built in access via key-value, SQL, and full-text search. Flexible JSON documents aligned to your applications and workloads. Build faster with blazing fast in-memory performance and automated replication and scaling while reducing cost. Capella has the best price performance of any fully managed document database. Visit couchbase.com/screaminginthecloud to try Capella today for free and be up and running in three minutes with no credit card required. Couchbase Capella: make your data sing.

Corey: It’s very clear that you have built an extraordinary team for people who are able to focus on vulnerability research. Which, on some level, is very interesting because you are not branded as it were as a vulnerability research company. This is not something that is your core competency; it’s not a thing that you wind up selling directly that I’m aware of. You are selling a security platform offering. So, on the one hand, it makes perfect sense that you would have a division internally that works on this, but it’s also very noteworthy, I think, that is not the core description of what it is that you do.

It is a means by which you get to the outcome you deliver for customers, not the thing that you are selling directly to them. I just find that an interesting nuance.

Yoav: Yes, it is. And I would elaborate and say that research informs the product, and the product informs research. And we get to have this fun dance where we learn new things by doing research. We [unintelligible 00:18:08] the product, and we use the customers to teach us things that we didn’t know. So, it’s one of those happy synergies.

Corey: I want to also highlight a second thing that you have mentioned and been very, I guess, on message about since news of this stuff first broke. And because it’s easy to look at this and sensationalize aspects of it, where, “See? The cloud providers security model is terrible. You shouldn’t use them. Back to data centers we go.” Is basically the line taken by an awful lot of folks trying to sell data center things.

That is not particularly helpful for the way that the world is going. And you’ve said, “Yeah, you should absolutely continue to be in cloud. Do not disrupt your cloud plan as a result.” And let’s be clear, none of the rest of us are going to find and mitigate these things with anything near the rigor or rapidity that the cloud providers can and do demonstrate.

Yoav: I totally agree. And I would say that the AWS security folks are doing a phenomenal job. I can name a few, but they’re all great. And I think that the cloud is by far a much safer alternative than on-prem. I’ve never seen issues in my on-prem environment which were critical and fixed in such a high velocity and such a massive scale.

And you always get the incremental improvements of someone really thinking about all the ins and outs of how to do security, how to do security in the cloud, how to make it faster, more reliable, without a business interruptions. It’s just phenomenal to see and phenomenal to witness how far we’ve come in such a relatively short time as an industry.

Corey: AWS in particular, has a reputation for being very good at security. I would argue that, from my perspective, Google is almost certainly slightly better at their security approach than AWS is, but to be clear, both of them are significantly further along the path than I am going to be. So great, fantastic. You also have found something interesting over in the world of Azure, and that honestly feels like a different class of vulnerability. To my understanding, the Azure vulnerability that you recently found was you could get credential material for other customers simply by asking for it on a random high port. Which is one of those—I’m almost positive I’m misunderstanding something here. I hope. Please?

Yoav: I’m not sure you’re misunderstanding. So, I would just emphasize that the vulnerability again, was found by Yanir Tsarimi. And what he found was, he used a service called Azure Automation which enables you essentially to run a Python script on various events and schedules. And he opened the python script and he tried different ports. And one of the high ports he found, essentially gave him his credentials. And he said, “Oh, wait. That’s a really odd port for an HTTP server. Let’s try, I don’t know, a few ports on either way.” And he started getting credentials from other customers. Which was very surprising to us.

Corey: That is understating it by a couple orders of magnitude. Yes, like, “Huh. That seems sub-optimal,” is sort of like the corporate messaging approved thing. At the time you discover that—I’m certain it was a three-minute-long blistering string of profanity in no fewer than four languages.

Yoav: I said to him that this is, like, a dishonorable bug because he worked very little to find it. So it was, from start to finish, the entire research took less than two hours, which, in my mind, is not enough for this kind of vulnerability. You have to work a lot harder to get it. So.

Corey: Yeah, exactly. My perception is that when there are security issues that I have stumbled over—for example, I gave a talk at re:Invent about it in the before times, one of them was an overly broad permission in a managed IAM policy for SageMaker. Okay, great. That was something that obviously was not good, but it also was more of a privilege escalation style of approach. It wasn’t, “Oh, by the way, here’s the keys to everything.”

That is the type of vulnerability I have come to expect, by and large, from cloud providers. We’re just going to give you access credentials for other customers is one of those areas that… it bugs me on a visceral level, not because I’m necessarily exposed personally, but because it more or less shores up so many of the arguments that I have spent the last eight years having with folks are like, “Oh, you can’t go to cloud. Your data should live on your own stuff. It’s more secure that way.” And we were finally it feels like starting to turn a cultural corner on these things.

And then something like that happens, and it—almost have those naysayers become vindicated for it. And it’s… it almost feels, on some level, and I don’t mean to be overly unkind on this, but it’s like, you are absolutely going to be in a better security position with the cloud providers. Except to Azure. And perhaps that is unfair, but it seems like Azure’s level of security rigor is nowhere near that of the other two. Is that generally how you’re seeing things?

Yoav: I would say that they have seen more security issues than most other cloud providers. And they also have a very strong culture of report things to us, and we’re very streamlined into patching those and giving credit where credit’s due. And they give out bounties, which is an incentives for more research to happen on those platforms. So, I wouldn’t say this categorically, but I would say that the optics are not very good. Generally, the cloud providers are much safer than on-prem because you only hear very seldom on security issues in the cloud.

You hear literally every other day on issues happening to on-prem environments all over the place. And people just say they expect it to be this way. Most of the time, it’s not even a headline. Like, “Company X affected with cryptocurrency or whatever.” It happens every single day, and multiple times a day, breaches which are massively bigger. And people who don’t want to be in the cloud will find every reason not to be the cloud. Let us have fun.

Corey: One of the interesting parts about this is that so many breaches that are on-prem are just never discovered because no one knows what the heck’s running in an environment. And the breaches that we hear about are just the ones that someone had at least enough wherewithal to find out that, “Huh. That shouldn’t be the way that it is. Let’s dig deeper.” And that’s a bad day for everyone. I mean, no one enjoys those conversations and those moments.

And let’s be clear, I am surprisingly optimistic about the future of Azure Security. It’s like, “All right, you have a magic wand. What would you do to fix it?” It’s, “Well, I’d probably, you know, hire Charlie Bell and get out of his way,” is not a bad answer as far as how these things go. But it takes time to reform a culture, to wind up building in security as a foundational principle. It’s not something you can slap on after the fact.

And perhaps this is unfair. But Microsoft has 30 years of history now of getting the world accustomed to oh, yeah, just periodically, terrible vulnerabilities are going to be discovered in your desktop software. And every once a month on Tuesdays, we’re going to roll out a whole bunch of patches, and here you go. Make sure you turn on security updates, yadda, yadda, yadda. That doesn’t fly in the cloud. It’s like, “Oh, yeah, here’s this month’s list of security problems on your cloud provider.” That’s one of those things that, like, the record-scratch, freeze-frame moment of wait, what are we doing here, exactly?

Yoav: So, I would say that they also have a very long history of making those turnarounds. Bill Gates famously did his speech where security comes first, and they have done a very, very long journey and turn around the company from doing things a lot quicker and a lot safer. It doesn’t mean they’re perfect; everyone will have bugs, and Azure will have more people finding bugs into it in the near future, but security is a journey, and they’ve not started from zero. They’re doing a lot of work. I would say it’s going to take time.

Corey: The last topic I want to explore a little bit is—and again, please don’t take this as anyway being insulting or disparaging to your company, but I am actively annoyed that you exist. By which I mean that if I go into my AWS account, and I want to configure it to be secure. Great. It’s not a matter of turning on the security service, it’s turning on the dozen or so security services that then round up to something like GuardDuty that then, in turn, rounds up to something like Security Hub. And you look at not only the sheer number of these services and the level of complexity inherent to them, but then the bill comes in and you do some quick math and realize that getting breached would have been less expensive than what you’re spending on all of these things.

And somehow—the fact that it’s complex, I understand; computers are like that. The fact that there is—[audio break 00:27:03] a great messaging story that's cohesive around this, I come to accept that because it’s AWS; talking is not their strong suit. Basically declining to comment is. But the thing that galls me is that they are selling these services and not inexpensively either, so it almost feels, on some level like, shouldn’t this on some of the built into the offerings that you folks are giving us?

And don’t get me wrong, I’m glad that you exist because bringing order to a lot of that chaos is incredibly important. But I can’t shake the feeling that this should be a foundational part of any cloud offering. I’m guessing you might have a slightly different opinion than mine. I don’t think you show up at the office every morning, “I hate that we exist.”

Yoav: No. And I’ll add a bit of context and nuance. So, for every other company than cloud providers, we expect them to be very good at most things, but not exceptional at everything. I’ll give the Redshift example. Redshift is a pretty good offering, but Snowflake is a much better offering for a much wider range of—

Corey: And there’s a reason we’re about to become Snowflake customers ourselves.

Yoav: So, yeah. And there are a few other examples of that. A security company, a company that is focused solely on your security will be much better suited to help you, in a lot of cases more than the platform. And we work actively with AWS, Azure, and GCP requesting new features, helping us find places where we can shed more light and be more proactive. And we help to advance the conversation and make it a lot more actionable and improve from year to year. It’s one of those collaborations. I think the cloud providers can do anything, but they can’t do everything. And they do a very good job at security; it doesn’t mean they’re perfect.

Corey: As you folks are doing an excellent job of demonstrating. Again, I’m glad you folks exist; I’m very glad that you are publishing the research that you are. It’s doing a lot to bring a lot I guess a lot of the undue credit that I was giving AWS for years of, “No, no, it’s not that they don’t have vulnerabilities like everyone else does. It just that they don’t ever talk about them.” And they’re operationalizing of security response is phenomenal to watch.

It’s one of those things where I think you’ve succeeded and what you said earlier that you were looking to achieve, which is elevating the state of cloud security for everyone, not just Orca customers.

Yoav: Thank you.

Corey: Thank you. I really appreciate your taking the time out of your day to speak with me. If people want to learn more, where’s the best place they can go to do that?

Yoav: So, we have our website at orca.security. And you can reach me out on Twitter. My handle is at @yoavalon, which is @-Y-O-A-V-A-L-O-N.

Corey: And we will of course put links to that in the [show notes 00:29:44]. Thanks so much for your time. I appreciate it.

Yoav: Thank you, Corey.

Corey: Yoav Alon, Chief Technology Officer at Orca Security. I’m Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you’ve enjoyed this podcast, please leave a five-star review on your podcast platform of choice, or of course on YouTube, smash the like and subscribe buttons because that’s what they do on that platform. Whereas if you’ve hated this podcast, please do the exact same thing, five-star review, smash the like and subscribe buttons on YouTube, but also leave an angry comment that includes a link that is both suspicious and frightening, and when we click on it, suddenly our phones will all begin mining cryptocurrency.

Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Announcer: This has been a HumblePod production. Stay humble.