(upbeat music) (logo shimmers) >> Good afternoon everyone, and welcome back to AWS re Invent 2022. We are live here from the show floor in Las Vegas, Nevada, we're theCUBE, my name is Savannah Peterson, joined by John Furrier, John, are you excited for the next segment? >> I love the innovation story, this next segment's going to be really interesting, an example of ecosystem innovation in action, it'll be great. >> Yeah, our next guests are actually award-winning, I am very excited about that, please welcome Alan and Becky from IBM. Thank you both so much for being here, how's the show going for ya? Becky you got a, just a platinum smile, I'm going to go to you first, how's the show so far? >> No, it's going great. There's lots of buzz, lots of excitement this year, of course, three times the number of people, but it's fantastic. >> Three times the number of people- >> (indistinct) for last year. >> That is so exciting, so what is that... Do you know what the total is then? >> I think it's over 55,000. >> Ooh, loving that. >> John: A lot. >> It's a lot, you can tell by the hallways- >> Becky: It's a lot. >> John: It's crowded, right. >> Yeah, you can tell by just the energy and the, honestly the heat in here right now is pretty good. Alan, how are you feeling on the show floor this year? >> Awesome, awesome, we're meeting a lot of partners, talking to a lot of clients. We're really kind of showing them what the new IBM, AWS relationship is all about, so, beautiful time to be here. >> Well Alan, why don't you tell us what that partnership is about, to start us off? >> Sure, sure. So the partnership started with the relationship in our consulting services, and Becky's going to talk more about that, right? And it grew, this year it grew into the IBM software realm where we signed an agreement with AWS around May timeframe this year. >> I love it, so, like you said, you're just getting started- >> Just getting started. >> This is the beginning of something magic. >> We're just scratching the surface with this right? >> Savannah: Yeah. >> But it represents a huge move for IBM to meet our clients where they are, right? Meet 'em where they are with IBM technology, enterprise technology they're used to, but with the look and feel and usage model that they're used to with AWS. >> Absolutely and so to build on that, you know, we're really excited to be an AWS Premier Consulting Partner. We've had this relationship for a little over five years with AWS, I'd say it's really gone up a notch over the last year or two as we've been working more and more closely, doubling down on our investments, doubling down on our certifications, we've got over 15,000 people certified now, almost 16,000 actually- >> Savannah: Wow. >> 14 competencies, 16 service deliveries and counting. We cover a mass of information and services from Data Analytics, IoT, AI, all the way to Modernization, SAP, Security Services, right. So it's pretty comprehensive relationship, but in addition to the fantastic clients that we both share, we're doing some really great things around joint industry solutions, which I'll talk about in a few minutes and some of those are being launched at the conference this year, so that's even better. But the most exciting thing to me right now is that we just found out that we won the Global Innovator Partner of the Year award, and a LATAM Partner of the Year award. >> Savannah: Wow. >> John: That's (indistinct) >> So, super excited for IBM Consulting to win this, we're honored and it's just a great, exciting part to the conference. >> The news coming out of this event, we know tomorrow's going to be the big keynote for the new Head of the ecosystem, Ruba. We're hearing that it's going to be all about the ecosystem, enabling value creation, enabling new kinds of solutions. We heard from the CEO of AWS, this nextGen environment's upon us, it's very solution-oriented- >> Becky: Absolutely. >> A lot of technology, it's not an either or, it's an and equation, this is a huge new shift, I won't say shift, a continuation for AWS, and you guys, we've been covering, so you got the and situation going on... Innovation solutions and innovation technology and customers can choose, build a foundation or have it out of the box. What's your reaction to that? Do you think it's going to go well for AWS and IBM? >> I think it fits well into our partnership, right? The the thing you mentioned that I gravitate to the most is the customer gets to choose and the thing that's been most amazing about the partnership, both of these companies are maniacally focused on the customer, right? And so we've seen that come about as we work on ways the customer to access our technology, consume the technology, right? We've sold software on-prem to customers before, right, now we're going to be selling SaaS on AWS because we had customers that were on AWS, we're making it so that they can more easily purchase it by being in the marketplace, making it so they can draw down their committed spin with AWS, their customers like that a lot- [John] Yeah. >> Right. We've even gone further to enable our distributor network and our resellers, 'cause a lot of our customers have those relationships, so they can buy through them. And recently we've enabled the customer to leverage their EDP, their committed spend with AWS against IBM's ELA and structure, right, so you kind of get a double commit value from a customer point of view, so the amazing part is just been all about the customers. >> Well, that's interesting, you got the technology relationship with AWS, you mentioned how they're engaging with the software consumption in marketplace, licensed deals, there's all kinds of new business model innovations on top of the consumption and building. Then you got the consulting piece, which is again, a big part of, Adam calls it "Business transformation," which is the result of digital transformation. So digital transformation is the process, the outcome is the business transformation, that's kind of where it all kind of connects. Becky, what's your thoughts on the Amazon consulting relationships? Obviously the awards are great but- >> They are, no- >> What's the next step? Where does it go from here? >> I think the best way for me to describe it is to give you some rapid flyer client examples, you know, real customer stories and I think that's where it really, rubber meets the road, right? So one of the most recent examples are IBM CEO Arvind Krishna, in his three key results actually mentioned one of our big clients with AWS which is the Department of Veterans Affairs in the US and is an AI solution that's helped automate claims processing. So the veterans are trying to get their benefits, they submit the claims, snail mail, phone calls, you know, some in person, some over email- >> Savannah: Oh, it gives me all the feels hearing you talk about this- >> It's a process that used to take 25 to 30 days depending on the complexity of the claims, we've gotten it down with AWS down to within 24 hours we can get the veterans what they need really quickly so, I mean, that's just huge. And it's an exciting story that includes data analytics, AI and automation, so that's just one example. You know, we've got examples around SAP where we've developed a next generation SAP for HANA Platform for Phillips Carbon Black hosted on AWS, right? For them, it created an integrated, scalable, digital business, that cut out a hundred percent the capital cost from on-prem solutions. We've got security solutions around architectures for telecommunications advisors and of course we have lots of examples of migration and modernization and moving workloads using Red Hat to do that. So there's a lot of great client examples, so to me, this is the heart of what we do, like you said, both companies are really focused on clients, Amazon's customer-obsessed, and doing what we can for our clients together is where we get the impact. >> Yeah, that's one of the things that, it sounds kind of cliche, "Oh we're going to work backwards from the customer," I know Amazon says that, they do, you guys are also very customer-focused but the customers are changing. So I'd love to get your reaction because we're now in that cloud 2.0, I call that 2.0 or you got the Amazon Classic, my word, and then Next Gen Cloud coming, the customers are different, they're transforming because IT's not a department anymore, it's in the DevOps pipeline. The developers are driving a lot of IT but security and on DataOps, it's the structural change happening at the customer, how do you guys see that at IBM? I know we cover a lot of Red Hat and Arvind talks to us all the time, meeting the customer where they are, where are they? Where are the customers? Can you share your perspective on where they are? >> It's an astute observation, right, the customer is changing. We have both of those sets of customers, right, we still have the traditional customer, our relationship with Central IT, right, and driving governance and all of those things. But the folks that are innovating many times they're in the line of business, they're discovering solutions, they're building new things. And so we need our offerings to be available to them. We need them to understand how to use them and be convenient for these guys and take them through that process. So that change in the customer is one that we are embracing by making our offerings easy to consume, easy to use, and easy to build into solutions and then easy to parlay into what central IT needs to do for governance, compliance, and these types of things, it's becoming our new bread and butter. >> And what's really cool is- >> Is that easy button- >> We've been talking about- >> It's the easy button. >> The easy button a lot on the show this week and if you just, you just described it it's exactly what people want, go on Becky. >> Sorry about that, I was going to say, the cool part is that we're co-creating these things with our clients. So we're using things like the Amazon Working Backward that you just mentioned.` We're using the IBM garage methodology to get innovative to do design working, design thinking workshops, and think about where is that end user?, Where is that stakeholder? Where are they, they thinking, feeling, doing, saying how do we make the easier? How do we get the easy button for them so that they can have the right solutions for their businesses. We work mostly with lines of business in my part of the organization, and they're hungry for that. >> You know, we had a quote on theCUBE yesterday, Savannah remember one of our guests said, you know, back in the, you know, 1990s or two 2000s, if you had four production apps, it was considered complex >> Savannah: Yeah. >> You know, now you got hundreds of workloads, thousands of workloads, so, you know, this end-to-end vision that we heard that's playing out is getting more complex, but the easy button is where these abstraction layers and technology could come in. So it's getting more complex because there's more stuff but it's getting easier because- >> Savannah: What is the magnitude? >> You can make it easier. This is a dynamic, share your thoughts on that. >> It's getting more complex because our clients need to move faster, right, they need to be more agile, right, so not only are there thousands of applications there are hundreds of thousands microservices that are composing those applications. So they need capabilities that help them not just build but govern that structure and put the right compliance over that structure. So this relationship- >> Savannah: Lines of governance, yeah- >> This relationship we built with AWS is in our key areas, it's a strategic move, not a small thing for us, it covers things like automation and integration where you need to build that way. It covers things like data and AI where you need to do the analytics, even things like sustainability where we're totally aligned with what AWS is talking about and trying to do, right, so it's really a good match made there. >> John: It really sounds awesome. >> Yeah, it's clear. I want to dig in a little bit, I love the term, and I saw it in my, it stuck out to me in the notes right away, getting ready for you all, "maniacal", maniacal about the customer, maniacal about the community, I think that's really clear when we're talking about 24 days to 24 hours, like the veteran example that you gave right there, which I genuinely felt in my heart. These are the types of collaborations that really impact people's lives, tell me about some of the other trends or maybe a couple other examples you might have because I think sometimes when our head's in the clouds, we talk a lot about the tech and the functionality, we forget it's touching every single person walking around us, probably in a different way right now than we may even be aware- >> I think one of the things that's been, and our clients have been asking us for, is to help coming into this new era, right, so we've come out of a pandemic where a lot of them had to do some really, really basic quick decisions. Okay, "Contact Center, everyone work from home now." Okay, how do we do that? Okay, so we cobbled something together, now we're back, so what do we do? How do we create digital transformation around that so that we are going forward in a really positive way that works for our clients or for our contact center reps who are maybe used to working from home now versus what our clients need, the response times they need, and AWS has all the technology that we're working with like Amazon Connect to be able to pull those things together with some of our software like Watson Assistant. So those types of solutions are coming together out of that need and now we're moving into the trend where economy's getting tougher, right? More cost cutting potentially is coming, right, better efficiencies, how do we leverage our solutions and help our clients and customers do that? So I think that's what the customer obsession's about, is making sure we really understand where their pain points are, and not just solve them but maybe get rid of 'em. >> John: Yeah, great one. >> Yeah. And not developing in a silo, I mean, it's a classic subway problem, you got to be communicating with your community if you want to continue to serve them. And IBM's been serving their community for a very long time, which is super impressive, do you think they're ready for the challenge? >> Let's do it. >> So we have a new thing on theCUBE. >> Becky: Oh boy. >> We didn't warn you about this, but here we go. Although you told, Alan, you've mentioned you're feeling very cool with the microphone on, so I feel like, I'm going to put you in the hot seat first on this one. Not that I don't think Becky's going to smash it, but I feel like you're channeling the power of the microphone. New challenges, treat it like a 32nd Instagram reel-style story, a hot take, your thought leadership, money clip, you know, this is your moment. What is the biggest takeaway, most important thing happening at the show this year? >> Most important thing happening at the show? Well, I'm glad you mentioned it that way, because earlier you said we may have to sing (presenters and guests all laughing) >> So this is much better than- >> That's actually part of the close. >> John: Hey, hey. >> Don't worry, don't worry, I haven't forgotten that, it's your Instagram reel, go. (Savannah laughs) >> Original audio happening here on theCUBE, courtesy of Alan and IBM, I am so here for it. >> So what my takeaway and what I would like for the audience to take away, out of this conversation especially, but even broadly, the IBM AWS relationship is really like a landmark type of relationship, right? It's one of the biggest that we've established on both sides, right- >> Savannah: It seems huge, okay you are too monolith in the world of companies, like, yeah- >> Becky: Totally. >> It's huge. And it represents a strategic change on both sides, right? With that customer- >> Savannah: Fundamentally- >> In the middle right? >> Savannah: Yeah. >> So we're seeing things like, you know, AWS is working with us to make sure we're building products the way that a AWS client likes to consume them, right, so that we have the right integration, so they get that right look and feel, but they still get the enterprise level capabilities they're used to from IBM, right? So the big takeaway I like for people to take, is this is a new IBM, it's a new AWS and IBM relationship, and so expect more of that goodness, more of those new things coming out of it. [John] Excellent, wow. >> That was great, well done, you nailed it. and you're going to finish with some acapella, right? (Alan laughs) >> You got a pitch pipe ready? (everyone laughs) >> All right Becky, what about you? Give us your hot take. >> Well, so for me, the biggest takeaway is just the way this relationship has grown so much, so, like you said, it's the new IBM it's the new AWS, we were here last year, we had some good things, this year we're back at the show with joint solutions, have been jointly funded and co-created by AWS and IBM. This is huge, this is a really big opportunity and a really big deal that these two companies have come together, identified joint customer needs and we're going after 'em together and we're putting 'em in the booth. >> Savannah: So cool. And there's things like smart edge for welding solutions that are out there. >> Savannah: Yes. >> You know, I talked about, and it's, you know you wouldn't think, "Okay, well what's that?" There's a lot to that, a lot of saving when you look at how you do welding and if you apply things like visual AI and auditory AI to make sure a weld is good. I mean, I think these are, these things are cool, I geek out on these things- >> John: Every vertical. >> I'm geeking out with you right now, just geeking- >> Yeah, yeah, yeah, so- >> Every vertical is infected. >> They are and it's so impactful to have AWS just in lockstep with us, doing these solutions, it's so different from, you know, you kind of create something that you think your customers like and then you put it out there. >> Yeah, versus this moment. >> Yeah, they're better together. >> It's strategic partnership- >> It's truly a strategic partnership. and we're really bringing that this year to reinvent and so I'm super excited about that. >> Congratulations. >> Wow, well, congratulations again on your awards, on your new partnership, I can't wait to hear, I mean, we're seven months in, eight months in to this this SaaS side of the partnership, can't wait to see what we're going to be talking about next year when we have you back on theCUBE. >> I know. >> and maybe again in between now and then. Alan, Becky, thank you both so much for being here, this was truly a joy and I'm sure you gave folks a taste of the new IBM, practicing what you preach. >> John: Great momentum. >> And I'm just, I'm so impressed with the two companies collaborating, for those of us OGs in tech, the big companies never collaborated before- >> Yeah. >> John: Yeah. Joint, co-created solutions. >> And you have friction between products and everything else. I mean's it's really, co-collaboration is, it's a big theme for us at all the shows we've been doing this year but it's just nice to see it in practice too, it's an entirely different thing, so well done. >> Well it's what gets me out of the bed in the morning. >> All right, congratulations. >> Very clearly, your energy is contagious and I love it and yeah, this has been great. Thank all of you at home or at work or on the International Space Station or wherever you might be tuning in from today for joining us, here in Las Vegas at AWS re Invent where we are live from the show floor, wall-to-wall coverage for three days with John Furrier. My name is Savannah Peterson, we're theCUBE, the source for high tech coverage. (cheerful upbeat music)

>>Hey everyone, and welcome back to Las Vegas. Viva Las Vegas, baby. This is the Cube live at AWS Reinvent 2022 with tens of thousands of people. Lisa Martin here with Dave Valante. Dave, we've had some great conversations. This is day one of four days of wall to wall coverage on the cube. We've been talking data. Every company is a data company. Data protection, data resiliency, absolutely table stakes for organizations to, >>And I think ecosystem is the other big theme. And that really came to life last year. You know, we came out of the pandemic and it was like, wow, we are entering a new era. People no longer was the ecosystem worried about it, AWS competing with them. They were more worried about innovating and building on top of AWS and building their own value. And that's really, I think, the theme of the 2020s within the ecosystem. >>And we're gonna be talking about building on top of aws. Two guests join us, two alumni join us. Stephen Manley is here, the CTO of Druva. Welcome back. Jason crat as well is here. CIO and CTO of Summit Carbon Solutions. Guys, great to have you back on the program. >>Thank you. >>Let's start with you giving the audience an understanding of the company. What do you guys do? What do you deliver value for customers? All that good >>Stuff. Yeah, no, for sure. So Summit Carbon is the world's largest carbon capture and sequestration company capturing close to 15 million tons of carbon every year. So it doesn't go into the atmosphere. >>Wow, fantastic. Steven, the, the risk landscape today is crazy, right? There's, there's been massive changes. We've talked about this many times. What are some of the things, you know, ransomware is a, is, I know as you say, this is a, it's not a, if it's gonna happen, it's when it's how frequent, it's what's gonna be the damage. What are some of the challenges and concerns that you're hearing from customers out there today? >>Yeah, you know, it really comes down to three things. And, and everybody is, is terrified of ransomware and justifiably so. So, so the first thing that comes up is, how do I keep up? Because I have so much data in so many places, and the threats are evolving so quickly. I don't have enough money, I don't have enough people, I don't have enough skilled resources to be able to keep up. The second thing, and this ties in with what Dave said, is, is ecosystem. You know, it used to be that your, your backup was siloed, right? They'd sit in the basement and, and you wouldn't see, see them. But now they're saying, I've gotta work with my security team. So rather than hoping the security team stays away from me, how do I integrate with them? How do I tie together? And then the third one, which is on everybody's mind, is when that attack happens, and like you said, it's win and, and the bell rings and they come to me and they say, all right, it's time for you to recover. It's time for, for all this investment we've put in. Am I gonna be ready? Am I going to be able to execute? Because a ransom or recovery is so different than any other recovery they've ever done. So it's those three things that really are top of mind for >>How, so what is the, what are the key differences, if you could summarize? I mean, I >>Know it's so, so the first one is you can't trust the environment you're restoring into. Even with a disaster, it would finish and you'd say, okay, I'm gonna get my data center set up again and I'm gonna get things working. You know, when I try to recover, I don't know if everything's clean yet. I'm trying to recover while I'm still going through incident response. So that's one big difference. A second big difference is I'm not sure if the thing I'm recovering is good, I've gotta scan it. I've gotta make sure what's inside it is, is, is alright. And then the third thing is what we're seeing is the targets are usually not necessarily the crown jewels because those tend to be more protected. And so they're running into this, I need to recover a massive amount of what we might call tier two, tier three apps that I wasn't ready for because I've always been prepared for that tier one disaster. And so, so those three things they go, it's stuff I'm not prepared or covering. It's a flow. I'm not used to having to check things and I'm not sure where I'm gonna recover too when the, when the time comes. >>Yeah, just go ahead. Yeah, that's right. I mean, I think for me, the biggest concern is the blind spots of where did I actually back it up or not. You know, what did I get it? Cuz you, we always protect our e r p, we always protect these sort of classes of tiers of systems, but then it's like, oh, that user's email box didn't get it. Oh, that, you know, that one drive didn't get it. You know, or, or, or whatever it is. You know, the infrastructure behind it all. I forgot to back that up. That to me the blind spots are the scariest part of a ransomware attack. >>And, and if you think about it, some of the most high profile attacks, you know, on the, on the colonial pipeline, they didn't go after the core assets. They went after billing. That's right. But billing brought everything down so they're smart enough to say, right, I'm not gonna take the, the castle head on. Is there is they're that. Exactly. >>And so how do you, I get, I mean you can air gap and do things like that in terms of protecting the, the, the data, the corrupt data. How do you protect the corrupt environment? Like that's, that's a really challenging issue. Is >>It? I don't know. I mean, I'll, I'll you can go second here. I think that what's interesting to me about is that's what cloud's for. You can build as many environments as you want. You only pay for what you use, right? And so you have an opportunity to just reconstruct it. That's why things, everything is code matters. That's why having a cloud partner like Druva matters. So you can just go restore wherever you need to in a totally clean environment. >>So the answer is you gotta do it in the cloud. Yeah. What if it's on prem? >>So if it's on prem, what we see people do is, and, and, and this is where testing and, and where cloud can still be an asset, is you can look and say a lot of those assets I'm running in the data center, I could still recover in the cloud. And so you can go through DR testing and you can start to define what's in your on-prem so that you could make it, you know, so you can make it cloud recoverable. Now, a lot of the people that do that then say, well actually why am I even running this on prem anymore in the first place? I should just move this to the cloud now. But, but, but there are people in that interim step. But, but, but it's really important because you, you're gonna need a clean environment to play in. And it's so hard to have a clean environment set up in a data center cuz it basically means I'm not touching this, I'm just paying for something to sit idle. Whereas cloud, I can spin that up, right? Get a, a cloud foundation suite and, and just again, infrastructures code, spin things up, test it, spin it down. It doesn't cost me money on a daily basis. >>Jason, talk a little bit about how you are using Druva. Why Druva and give us a kind of a landscape of your IT environment with Druva. >>Yeah. You know, so when we first started, you know, we did have a competitor solution and, and, and it was only backing up, you know, we were a startup. It was only backing up our email. And so as you pointed out, the ecosystem really matters because we grew out of email pretty quick as a startup. And we had to have real use cases to protect and the legacy product just wouldn't support us. And so our whole direction, or my direction to my team is back it up wherever it is, you know, go get it. And so we needed somebody in the field, literally in the middle of Nebraska or Iowa to have their laptop backed up. We needed our infrastructure, our data center backed up and we needed our, our SaaS solutions backed up. We needed it all. And so we needed a partner like Druva to help us go get it wherever it's at. >>Talk about the value in, with Druva being cloud native. >>Yeah. To us it's a big deal, right? There's all sorts of products you could go by to go just do endpoint laptop protection or just do SAS backups. For us, the value is in learning one tool and mastering it and then taking it to wherever the data is. To me, we see a lot of value for that because we can have one team focus on one product, get good at it, and drive the value. >>That consolidation theme is big right now, you know, the economic headwinds and so forth. What was the catalyst for you? Was it, is that something you started, you know, years ago? Just it's good practice to do that? What's, >>Well, no, I mean luckily I'm in a very good position as a startup to do define it, you know, but I've been in those legacy organizations where we've got a lot of tech debt and then how do you consolidate your portfolio so that you can gain more value, right? Cause you only get one budget a year, right? And so I'm lucky in, in the learnings I've had in other enterprises to deal with this head on right now as we grow, don't add tech debt, put it in right. Today. >>Talk to us a little bit about the SaaS applications that you're backing up. You know, we, we talk a lot with customers, the shared, the shared responsibility model that a lot of customers aren't aware of. Where are you using that competing solution to protect SaaS applications before driven and talk about Yeah. The, the value in that going, the data protection is our responsibility and not the SA vendor. >>No, absolutely. I mean, and it is funny to go to, you know, it's like Office 365 applications and go to our, our CFO and a leadership and be like, no, we really gotta back it up to a third party. And they're like, but why? >>It's >>In the cloud, right? And so there's a lot of instruction I have to provide to my peers and, and, and my users to help them understand why these things matter. And, and, and it works out really well because we can show value really quick when anything happens. And now we get, I mean, even in SharePoint, people will come to us to restore things when they're fully empowered to do it. But my team's faster. And so we can just get it done for them. And so it's an extra from me, it's an extra SLA or never service level I can provide to my internal customers that, that gives them more faith and trust in my organization. >>How, how are the SEC op teams and the data protection teams, the backup teams, how are they coming together? Is is, is data protection backup just morphing into security? Is it more of an adjacency? What's that dynamic like? >>So I'd say right now, and, and I'll be curious to hear Jason's organization, but certainly what we see broadly is, you know, the, the teams are starting to work together, but I wouldn't say they're merging, right? Because, you know, you think of it in a couple of ways. The first is you've got a production environment and that needs to be secured. And then you've got a protection environment. And that protection environment also has to be secured. So the first conversation for a lot of backup teams is, alright, I need to actually work with the security team to make sure that, that my, my my backup environment, it's air gapped, it's encrypted, it's secured. Then I think the, the then I think you start to see people come together, especially as they go through, say, tabletop exercises for ransomware recovery, where it's, alright, where, where can the backup team add value here? >>Because certainly recovery, that's the basics. But as there log information you can provide, are there detection pieces that you can offer? So, so I think, you know, you start to see a partnership, but, but the reality is, you know, the, the two are still separate, right? Because, you know, my job as a a protection resiliency company is I wanna make sure that when you need your data, it's gonna be there for you. And I certainly want to, to to follow best secure practices and I wanna offer value to the security team, but there's a whole lot of the security ecosystem that I want to plug into. I'm not trying to replace them again. I want to be part of that broader ecosystem. >>So how, how do you guys approach it? Yeah, >>That's interesting. Yeah. So in my organization, we, we are one team and, and not to be too cheesy or you know, whatever, but as Amazon would say, security is job one. And so we treat it as if this is it. And so we never push something into production until we are ready. And ready to us means it's got a security package on it, it's backed up, the users have tested it, we are ready to go. It's not that we're ready just be to provide the service or the thing. It's that we are actually ready to productionize this. And so it's ready for production data and that slows us down in some cases. But that's where DevOps and this idea of just merging everything together into a central, how do we get this done together, has worked out really well for us. So, >>So it's really the DevOps team's responsibility. It's not a separate data protection function. >>Nope. Nope. We have specialists of course, right? Yeah, yeah. Because you need the extra level, the CISSPs and those people Yeah, yeah. To really know what they're doing, but they're just part of the team. Yeah. >>Talk about some of the business outcomes that you're achieving with Druva so far. >>Yeah. The business outcomes for me are, you know, I meet my SLAs that's promising. I can communicate that I feel more secure in the cloud and, and all of my workloads because I can restore it. And, and that to me helps everybody in my organization sleep well, sleep better. We are, we transport a lot of the carbon in a pipeline like Colonial. And so to us, we are, we are potential victims of, of a pipe, a non pipeline group, right? Attacking us, but it's carbon, you know, we're trying to get it outta atmosphere. And so by protecting it, no matter where it is, as long as we've got internet access, we can back it up. That provides tons of value to my team because we have hundreds of people in the field working for us every day who collect data and generate it. >>What would you say to a customer who's maybe on the fence looking at different technologies, why dva? >>You know, I think, you know, do the research in my mind, it'll win if you just do the research, right? I mean, there might be vendors that'll buy you nice dinners or whatever, and those are, those are nice things, but the, the reality is you have to protect your data no matter where it is. If it's in a SaaS application, if it's in a cloud provider, if it's infrastructure, wherever it is, you need it. And if you just go look at the facts, there it is, right? And so I, I'd say be objective. Look at the facts, it'll prove itself. >>Look at the data. There you go. Steven Druva recently announced a data resiliency guarantee with a big whopping financial sum. Talk to us a little bit about that, the value in it for your customers and for prospects, >>Right? So, so basically there's, there's really two parts to this guarantee. The first is, you know, across five different SLAs, and I'll talk about those, you know, if we violate those, the customers can get a payout of up to 10 million, right? So again, putting, putting our money where our mouth is in a pretty large amount. But, but for me, the exciting part, and this is, this is where Jason went, is it's about the SLAs, right? You know, one of Drew's goals is to say, look, we do the job for you, we do the service for you so you can offer that service to your company. And so the SLAs aren't just about ransomware, some of them certainly are, you know, that, that you're going to be able to recover your data in the event of a ransomware attack, that your data won't get exfiltrated as part of a ransomware attack. >>But also things like backup success rates, because as much as recovery matters a lot more than backup, you do need a backup if you're gonna be able to get that recovery done. There's also an SLA to say that, you know, if 10 years down the road you need to recover your data, it's still recoverable, right? So, so that kind of durability piece. And then of course the availability of the service because what's the point of a service if it's not there for you when you need it? And so, so having that breadth of coverage, I think really reflects who Druva is, which is we're doing this job for you, right? We want to make this this service available so you can focus on offering other value inside your business. And >>The insurance underwriters, if they threw holy water on >>That, they, they, they were okay with it. The legal people blessed it, you know, it, you know, the CEO signed off on it, the board of directors. So, you know, it, and it, it's all there in print, it's all there on the web. If you wanna look, you know, make sure, one of the things we wanted to be very clear on is that this isn't just a marketing gimmick that we're, we're putting, that we're putting substance behind it because a lot of these were already in our contracts anyway, because as a SAS vendor, you're signing up for service level agreements anyway. >>Yeah. But most of the service level agreements and SaaS vendors are crap. They're like, you know, hey, you know, if something bad happens, you know, we'll, we'll give you a credit, >>Right? >>For, you know, for when you were down. I mean, it's not, you never get into business impact. I mean, even aws, sorry, I mean, it's true. We're a customer. I read define print, I know what I'm signing up for. But, so that's, >>We read it a lot and we will not, we don't really care about the credits at all. We care about is it their force? Is it a partner? We trust, we fight that every day in our SLAs with our vendors >>In the end, right? I mean this, we are the last line of defense. We are the thing that keeps the business up and running. So if your business, you know, can't get to his data and can't operate, me coming to you and saying, Dave, I've got some credits for you after you, you know, after you declare bankruptcy, it'll be great. Yeah, that's not a win. >>It's no value, >>Not helpful. The goal's gotta be, your business is up and running cuz that's when we're both successful. So, so, so, you know, we view this as we're in it together, right? We wanna make sure your business succeeds. Again, it's not about slight of hand, it's not about, you know, just, just putting fine print in the contract. It's about standing up and delivering. Because if you can't do that, why are we here? Right? The number one thing we hear from our customers is Dr. Just works. And that's the thing I think I'm most proud of is Druva just works. >>So, speaking of Juva, just working, if there's a billboard in Santa Clara near the new offices about Druva, what's, what's the bumper sticker? What's the tagline? >>I, I, I think, I think that's it. I think Druva just works. Keeps your data safe. Simple as that. Safe and secure. Druva works to keep your data safe and secure. >>Saved me. >>Yeah. >>Truva just works. Guys, thanks so much for joining. David, me on the program. Great to have you back on the cube. Thank you. Talking about how you're working together, what Druva is doing to really putting, its its best foot forward. We appreciate your insights and your time. Thank >>You. Thanks guys. It's great to see you guys. Likewise >>The show for our guests and Dave Ante. I'm Lisa Martin, you're watching the Cube, the leader in enterprise and emerging tech coverage.

foreign continued coverage of AWS re invent my name is Savannah Peterson and I am very excited to be joined by two brilliant blokes in the space of efficiency and performance whether you're on Prem or in the cloud today's discussion is going to be fascinating please welcome Brad and Simon to the show how are you Simon coming in from the UK how you feeling well thank you excellent and Brad we have you coming in from Seattle how are you this morning doing fine thank you excellent and feeling bookish given your background love that I know that you both really care about efficiency and performance it's a very hot topic both of the show and in the industry right now I'm curious I'm going to open it up with you Simon what challenges and I think you've actually continued to tackle these throughout the course of your career what challenges were you facing and wanting to solve when you started yellow dog um really we're just looking at cloud and coming from an on-premise environment really wanted to be able to make accessing Cloud particularly a volume to be simple and straightforward um if you look at today at the number of instance types available from the major Cloud providers there's more than seven thousand different instance types whereas on-prem you go along you select your processes you select your systems it's already be really easy when you hit the cloud you've just got this amazing amount of choice so really it was all about how can you make Intelligent Decisions for you know are you going to run your workload how to match it with what you've got on premise and that was really the inspiration for Rafael so staying there for just a second what does yellow dog provide customers is a SAS system so um you get to it by accessing through the yellow platform and what it allows people to do is to be able to make Intelligent Decisions about where to run their workload would that be on premise or in the cloud it has a wealth of information it understands the costs the performance the latency and the availability of every different instance type in all different clouds it really allows people to uh to be able to make use of that information provision exactly what they need and to be able to run their workloads yeah it also includes a provisioner and it also includes a scheduler as well which is a cloud native scheduler so it's designed to be able to cope with um with cloud in terms of things like spots and interruptions and be able to uh to reschedule and fail over between clouds if there's ever need to do so yeah that sounds incredible and I know this means a lot for partners like AMD Brad talk to me about the partnership and what this means for AMD for your customers yeah absolutely it you know we're excited to be aligned with the uh with a company like yellow dog it's it's um you know the the importance of compute is becoming more and more prevalent every day and it's it's always been top of mind but especially now when you think about what the uh what the economy and the rest of the world is kind of facing over the next you know probably a year or longer it's so important that um that you're able to maximize your dollars and your spend and doing away with uh with uh with absolute certainty that you've got the right type of people behind you uh ensuring that you're your dollars are being spent very wisely and the great thing about yell dogs that they have tremendous insight into uh into cost optimization computer optimization across the entire Globe their their indexes is quite remarkable and what it does is it allows uh customers to actually see just how performant and cost efficient AMD is so it allows us to really put our best foot forward and and gives customers a chance to understand something that they probably weren't uh more familiar with the fact that uh that AMD uh is a tremendous a tremendous value in the marketplace yeah and and uh Simon can you tell us a little bit more about the yellow dog index I'm glad you brought that up Brad yes the yellow index is uh is essentially it's live it's available for anyone to access you can just go to index.yam.tech and you'll be able to see pretty much every single instance type that's available from all the major Cloud providers and be able to make your selection are you looking for GPU type nodes are you looking for AMD processors are you looking just for performance essentially what you're able to do is create a live view of effectively what's available in different data centers around the world and the price at this moment in time also just uh as Brad mentioned in terms of you know cost efficiency and uh and being taking green values seriously as we should we should do the yellow index also has the ability to be able to see at that point in time where the best place to be at a runner job is based upon the lowest carbon impact of running at this moment in time and that for many organizations gives an amazing Insight in not just about being able to find the the understand fishing processes but being able to ensure the greenest energy possible is powering that process when you want to be able to run your workload it's so powerful what you just said and I think when we exactly it's not just about it's not just about power but it's about place when we are are looking at Global Computing at scale what I know that there's ESG advantages in and ESG being a very hot topic when we're talking about AMW on AWS and and and leveraging tools like yellow dog what other sorts of advantages Beyond being least carbon impactful can your Mutual customers benefit from so it's not like I say there's many other features you know a very important thing when you're running a high performance Computing workload is being able to match the instruction set that you're running on premise and then being able to use that in the cloud as well and also to be able to make Intelligent Decisions of where should something run should would something be more efficient um to build on premise should we always try and maximize our on-premise resources before going into the cloud there's a lot about being able to just be able to make decisions and yellow itself it makes thousands of decisions per second to be in a workout where the the best and most optimized places to to run your workload yeah so Brad you work with a lot of companies at scale what type of scale is possible when leveraging Technologies like AMD and yellow dog combined well you know I love the fact that you mentioned uh you know HPC and it's one of the areas that actually is most exciting for for me personally and for and for AMD with the combination of yellow dog and AWS and AWS launched the very first HPC uh instance type last year and you know we're we're we haven't even begun to answer a question we haven't gotten to see um the full-scale capability in the cloud when it comes to these uh these very coordinated and very refined workloads that are running at massive scale and and uh you know we've got some some products we'll be launched in the near future as well that are incredibly performant and you know to be honest I don't think I don't think we have even come close to seeing the scale relative to somebody's very optimized workloads in HPC uh that that we're capable of so um we're excited we're excited for the next few years to see how how we can wrap in um some of the tremendous success that AMD has had on-prem in these these these massive compute centers and replicating that same success inside AWS with companies like yellow dog it's uh it we're excited to see what uh what's what's going to come forward can you give us a preview of anything on the record that gets you really excited about the future I was going to ask you what what had you looking forward to 2023 and Beyond but nothing well not nothing official of course uh but um I will say this you know AMD has recently successful had the launch for Genoa uh it's our next next-gen release and it is um it is proving to be it absolutely is the dominant compute engine it at this point that exists and you know when you start to couple that with the the prowess of AWS you know you could see that over time becoming something potentially that um you know um can really start to change the compute landscape quite a bit so we're hopeful that you know in the future we'll have something along those lines uh with AWS and others and um we're very uh we're very bullish in that area love it uh Simon what about you you've been passionate about low carbon I.T for a long time is carbon neutral Tech in our future what I realize is a bold and lofty claim for you but feel free to give us any of your future predictions um yeah so well I started here trying to build solutions for you know many years ago so 2006 um I was part of a team that launched the the world's lowest powered Windows PC that was actually based on the AMD technology back then so uh you can tell that AMD have been working on a low power for us for a long time in terms of carbon neutral yes I think um certainly there's a there's a few data centers around the world now that are getting very close to uh to carbon neutral some of which may have already achieved it so that's really interesting but so you know the the second part of that is really the the manufacturer of everything that goes into those Services systems and being able to to get to uh you know a net zero on those over a period of time and when we do that which is yeah not without challenges but but certainly possible then we really will have carbon neutral I.T which will be uh a benefit to everyone you know mankind itself yeah casual statement and I have to say that I wholeheartedly agree I think that it's one of the greater challenges of Our Generation especially as what we're able to do in HPC in particular since we're talking about it is only going to grow and scale and magnitude and the amount of data that we have to organize certain process is is wild even today so I love that I'm curious is there anything that you can share with us that's in the pipeline for Yellow Dog anything coming up in the future that's very exciting um so we're coming up very soon um we're going to release something called um version 4 again log which contains um what we call a resource framework which is all about making sure you've got everything you need before you run a job either on-prem or in the cloud so that might be anything from making sure you've got the right licenses making sure that your data is all in the right location making sure you've got all aspects of your workflow ready before you start launching compute and start really but you know burning through dollars with computer could potentially sat there uh not not doing anything until other tasks keep catch up so we're really excited about this new V4 release which will uh which will come out very soon awesome we can't wait to learn more about that hopefully here again on the cube Brad what do Partnerships with companies like yellowdog meme for you and for the customers that you're able to serve yeah it's it's incredibly important I it's you know there's one of the difficulties in in compute that we have today especially in Cloud compute there's there's so much available at this point I mean there was a point in time it was very simple and straightforward it's not even close to being that anymore green so you know one of the things I love about yellow dog itself is actually it does a great they do a great job of making very complex situations and environments fairly simple to understand especially from a business perspective and so one of the things that we love about it is it actually helps our customers you know the AMD direct customers better understand how to properly use our technology and to get the most out of it and so it's difficult for us to articulate that message because you know we are a Semiconductor Company so sometimes it's a little tough to be able to articulate workloads and applications in the way that our customer base will be able to understand but you know it's it's so critical to have companies like yellow dog in the middle that can actually you know make that translation for us directly to the customer um you know and and especially too when you start thinking about ESG and environmental relationships and I'd like to make a comment and one of the things that is fantastic about AMD AWS and yellow we all share the same Mission and we're very public about those missions about just being better to the to the planet and um you know AMD has taken some very aggressive uh targets through 2025 much beyond anything that the industry has expected and you know because of that we are you know we are the most um we are the most power efficient xa6 product on the marketplace and it's not even close and you know I look forward to the day when uh you know you start looking at instance types inside these public Cloud providers in conjunction with the old dog and you can actually even start to see maybe potentially what that carbon footprint is based on those decisions you make on compute and um you know considering that more than half to spend for everybody is generally compute in these environments it's critical to really know what your true impact in the world is and um it's just one of the best parts about a partnership like this oh what a wonderful note to close on and I love both the Synergy between all the partners on a technology level but most importantly on a mission level because none of it matters if we don't have a planet that we can continue to innovate on so I'm I'm really grateful that you're both here fighting a good fight working together and also making a lot of information available for companies of all different sizes as they're navigating very complex decision trees in and operating their stack so thank you both Simon and Brad I really appreciate your time it's been incredibly insightful and thank you to our audience for tuning in to our continuing coverage of AWS re invent here on thecube my name is Savannah Peterson and I look forward to learning more with you soon foreign [Music]

>>Hey everyone. Welcome back to Miami, Miami Beach. Specifically, not a bad location to have a conference. Lisa Martin here with the Cube live at IFS Unleashed. We're gonna be having a great conversation next about Ization moments of Service Rules. Royces here, as is the C of IFS for aerospace and defense. Scott Camani. Nick Ward joins us as well, the VP of Digital Systems at Roll Royce. Guys, excited to have you on the program and welcome back. >>Thank you very much. Nice to be back. It's >>Been three years since the last IFS show. I love How's Scott? I was talking with Darren Roots earlier today and I said, Well, didn't it used to be IFS world? And he said, Yes. And I said, I love the name. I would love to, to unpack that with your cheek marketing officer because it, there's a lot of, of, of power behind Unleash. A lot of companies do such and such world or accelerate, but we're talking about unleashing the power of the technology to help customers deliver those moments of service. Yes. Love it. So Scott, start us off here. Talk about ization. That's a relatively new term to me. Sure. Help me understand what it means, because IFS is a pioneer in this sense. >>We are. So one of the things that IFS is always trying to do is to try to find a way to help our customers to realize a moment of service. And that moment of service is really when they found the ability to delight their customers. And when we look at the way in which we're trying to drive those business outcomes for our customers, ization seems to be at the core of it. So whether it's the ability for a company to use a product, a service, or an outcome, they're driving ization in a way where they're shaping their business. They're orchestrating their customers and their people and their assets behind a val value chain that helps them to provide a delightful experience for their customers. And with IFS being focused on Lifecycle asset management, we no longer have customers that have to choose from best of suite or best of breed. They can actually have both with ifs. And that's something we're really excited to provide to our customers and more excited for our customers to realize that value with their customers, their partners. Along the way. >>You, you mentioned customer delight and it's a term that we, we all use it, right? But there's so much power and, and capabilities and metrics behind that phrase, customer delight, which will unpack Nick bringing you into the conversation. Talk to us a little bit about what your role is at Rolls Royce. My first thought when I saw you was, oh, the fancy cars, but we're talking about aerospace and the fence, so give us a little bit of a history. >>Okay. So yes, we don't make cars is the first point. So we are, we are power, we do power as a service. So we are most well known, I guess for large aircraft airliners. You know, if you've, if you've flown here to Miami, there's probably a 50 50 chance you've flown on a Rod Roy powered aircraft. Our market segment is what we call wide bodied aircraft where you go on, there's two aisles. So the larger section of the market, and we, we provide power, so we provide the engines, but more importantly, we've been a ization company, a service company for at least two decades. We, we have a, a service relationship we call total care. And the whole idea of total care is, yes, I have my engine, it's on my aircraft, but I take care of it. I make sure it's available to fly when you need to fly it. And all of the things that have to come together to make that happen, it's a service company. >>Service company. Talk to me a little bit about, and I wanna get got your perspective as well, but the relationship that Roll Royce and IFS have this is a little bit unique. >>Well, I can start, but I I think Nick's gonna be better served to tell us about that as our customer. Nick and I actually started this journey about four years ago, and what we did was, is we were working closely with our perspective customer Rolls-Royce identified what they were looking for as a desired business outcome. And then we found a way through the technology and the software that we provide to all of our enterprise customers globally to find a solution that actually helped to provide a, an outcome not only to Rolls-Royce, but also to our collective downstream customers, commercial operators around the globe. So that's where we started the journey and we're continuing our discussions around other solutions, but that's how we started and it's been an incredible partnership. We're so happy and proud to have Nick as a customer and a advocate of all things ifs and I'll let him kind of continue from his point of view how he sees the partnership in the relationship. >>No, thank you Scott. I think we've, we've always, we've valued the kind of relationship that we have because I think IFS has always got Rolls Royce in terms of strategic direction. What do we try to do? I said, we're a service company. You know, we, we are, we have to have a service relationship with our, our customers, our airlines. To have a service relationship, you have to be able to connect to your service customer. And ifs is a big part of how we connect for data. That's how do we understand what the airline is doing with the engines, but it's also how we return data back into the airline. So we are, we're get a very close integrated relation between us, our airlines, through a bridge that, that ifs create through the maintenance product. Got it. So it works really well. >>I I think I'd make one other point. One of the things that we've always focused on is quantifiable business value. The only way a partnership like this could possibly work is if we have a desired business outcome, but if we're providing value, So the value work that we did in conjunction with Rolls Royce and really identifying that helped to support the business case that allowed this partnership to really begin and flourish. So I I, I'd be remiss if I didn't mention that business value element that's really core to everything we do and all the, the conversations that Nick and I have. >>Well, it's all about outcomes. Absolutely. It's all about outcomes. It >>Is, it has to be about, it's about moments of service, right? That's why we're here, right? So perhaps a moment of service for Robs Royce is every time you're a passenger, you're going through the terminal. You expect your aircraft to be there, ready, waiting for you to get on and depart on time. And our moment of service is every aircraft takes off on time, every time we live. When we die by the quality of that statement, how well we live up to that statement, I think I checked this morning, there's something alike, 600 aircraft in the sky right now with Rolls Royce power carrying passengers. All of those passengers have relied on that moment. Service happening regularly like clockwork. Every single time you don't get any forgiveness for a delay, you get very little forgiveness for a cancellation that has to happen. And then so many things have to come together for that to happen. >>Those 600 aircraft, that's maybe 200,000 people right now in the sky, Wow. Those 200,000 people are trying to connect, They're trying to connect with friends, they're trying to connect with loved ones, family, colleagues, whatever the purpose is of that trip. It's really important to them. And we just have to make sure that that happens for us. We've had something like a million flights so far this year, 300 million people relying on that moment of so is happening. So I really resonate with, with the language that Scott users about the importance of sort of that focal point on when does it all come together? It comes together when as a passenger, I get on the plane and it goes and I get no issues. >>Right. Well people don't tolerate fragmented experiences anymore. No, no. I think one of the things that was in short supply during the pandemic was patience and tolerance. Sure. Not sure how much of that's gonna come back, right? But those integrated connected experiences, as you described so eloquently, Nick, those are table stakes for the customers, but also the brands behind them because of customers are unhappy, the churn rates go way up. And you see that reflected in obviously the success of the business and what you guys are doing together is seems to be quite powerful. Now then when you were on the cube with us three years ago in Boston at IFS back then you first introduced the intelligent engine and the Blue Data thread. Let's talk about the intelligent engine. Just give our audience a refresher of what that actually entails. >>So perhaps if we just step one one step back for that, just to understand how this fits in. So Roro is a service organization. We talked about that. What that means is we take a lot of the, the risk and the uncertainty away from our airline customers on the availability, the costs and maintenance effort associated with having a, having a chat engine. These are incredibly complicated and complex and sophisticated pieces of equipment. The most expensive, most sophisticated pieces of an aircraft. Managing that is, is difficult. And every airline does not want to have to focus on that. They wanna focus on being able to get the passenger on the air after, fly it, look after the airframe. So our role in that is to take that risk away, is to manage those engines, look after their health, look after their life, make sure they're available to fly whenever they need to fly. >>So for us to understand that, we then have to have data, we have to understand the state of every engine, where it is, the health of the engine, the life of that engine, what do we need to do next to that engine? And we can't do that unless we have data and that data flows into a digital platform. The intelligent engine, which is our cloud based ai, big data, all of the iot, all of the big buzzwords are there, right? So the data flows into that, that lets us run the models. It lets us understand, I can see something maybe it's a, it's a small issue, but if I leave it alone, it become a bigger issue. And maybe that will cause disruption further down the line. So we need to understand that we need to preempt it. So preemptive predictive maintenance is a, is a big part of the intelligent engine, but it's more than just that. >>It's also, we can understand how that engine is being flown. We can understand is it having a really intense flight? Is it having a more benign, gentle flight? Wow. That change time after the flight, typically after the flight. But what that means is we can then understand, actually we can keep that engine on the wing longer then you might otherwise have to do, If you have no data, you have to be conservative, safety rules, everything. Sure. So data allows you to say, actually I'm being overly conservative in this space. I can get more flying bios, flying hours from my product by extending the interval between maintenance and the intelligent engine has a large part to play in us justifying that we're able to do that. And then the final part that it does is eventually the engine is gonna have to come off from maintenance. >>These things fly 5 million miles between overhauls. You imagine you try to do that in your family car. It's, it doesn't happen. It's incredibly sophisticated thing can fly 5 million miles and then we take it off for a major overhaul. But there are thousands of these engines in the fleet. We have to understand which engine is going to come off when for what reason, and prepare our maintenance network to then receive the engine and deal with it and get it back to the customer. So the intelligent engine has a massive part to play in understanding the maintenance demand that the flying fleet is then creating. >>Wow, that's fascinating. And so you talked about that three years ago. What's next for that? I imagine there's only more evolution that's gonna happen. >>It keeps growing. It keeps growing. It's driven by the data. The more data we have, the more that we can do with that. I think as well that, you know, one of the big places that we've we've gone is you can do as much predictive analytics as you, like, there's a lot of people we'll talk about doing predictive analytics, but if you don't do the hard yards of turning predictive analytics into outcome Yeah. Then what did you get? You, you got a bit of smart advice. So we, we take that maintenance demand, we then have to understand how that drives the orchestration and the management of all the parts, the people, the work scope definition, the allocating an engine into a maintenance slot, exactly when it's gonna go. And what are we gonna do to, how do we control and manage our inventory to make sure that engine is gonna go through. >>How do we then actually execute the work inside our, our our overall shops? How do we get that engine back and and integrate our logistics process. So the intelligent engine is, if you like, the shiny front end of a process, it's all the buzzwords, but actually the hard yards behind the scene is just as if not more important to get right. And again, this is why I really like the moment of service concept. Because without that, the moment of service doesn't happen. The engine's not there, the part wasn't there. The field service maintenance guy wasn't there to go fix it. >>And brands are affected >>An, an aircraft on the ground earns no revenue for anybody. No. It's, it's a cost. It's it's a big sink of cost. It >>Is, it is. Absolutely. >>And you're helping aircraft only earn engines only earn when they fly. Yeah, >>Yeah. Absolutely. And what a fascinating, the intelligent engine. Scott, talk a little bit about, we talking about power, we can't not talk about sustainability. Yes, I understand that IFS has a new inaugural awards program that Rolls Roys was a recipient of the Change for Good sustainability awards. Congratulations. Thank you very much. And to Scott, talk to me a little bit about the Change for Good program sustainability program. What types of organizations across the industries of expertise are you looking for and why does Rules ROY really highlight what a winner embodies? >>So since Darren has joined IFS as the ceo, he's had a lot of intentional areas that we focused on. And sustainability has been one that's at the top of the list. IFS has a US ambassador Lewis Pew, who's our Chief Sustainability officer, and he helps us to provide worldwide coverage of the efforts around sustainability. So it's not just about ifss ability to become a more sustainable organization, but it's the solutions that IFS is putting together in the five verticals that we focus on that can help those organizations achieve a level of sustainability for their, for their downstream customers, their partners, and for their enterprises themselves. So when we look at, you know, the social ability for us to be more conscientious about leaving the world a better place or trying to do our best to leave the world not as bad as we came into it, sustainability is a real focus for us. And, you know, the way in which we can support an organization like Rolls Royce and Nickel obviously share those areas of focus from Rolls Royce. It's a perfect fit. And congratulations again for the award. Thank you. We're, we're, we're so excited to, to have shared that with you. We have some other customers that have achieved it across different categories, but it's an area of current and continuous focus for ifs. >>Nick, talk to us, take us out here as our last question is the, the focus on sustainability at Rolls Royce. Talk to us a little bit about that and what some of the major efforts are that you've got underway. >>I think, you know, very similar as, as, as Scott taught there, the focus within Rolls Royce as a strategic group level is really high aviation particularly, I mean we're a, we're an engineering company. We're a power company. Power inherently consumes natural resources. It tends to generate climate affecting outcomes. But at the same time, we are an innovative organization and if anybody's gonna help solve climate challenges, it's gonna be organizations like Rolls Royce who are able to bring different technologies into the market. So we have a responsibility to manage and, and optimize the behavior of our, our existing product suite. But we also have a, a vested interest in trying to move aviation on into the next, the next phase. We talk about sustainable aviation. Aviation has to earn the right to exist. People have choices. We've come out of covid, people are used to doing zoom and not flying. >>People are used to doing things when they don't necessarily get on an aircraft and do something. The aviation business always has to earn the right from the public to exist. And increasingly people will make choices about how they fly when they fly, how far they fly based on the sustainability footprint. So it's really important to us to help both our customers operate the aircraft in as sustainable and climate friendly way as we can. It's really important to find those, those balance points between the cost of an operation and it's the impact of an operation. If you go all over and say, I am going to be net, well, not even net to, but zero carbon by almost inference, that means I'm not gonna operate. You have to operate to get to an outcome. But how do I do that? Why I manage my cost, I manage the, the profitability, the organization doing it, right? >>So it has to be financially sustainable, it has to be sustainable for the people operating within it. It has to be sustainable for the planet, right? So we do that in lots of different ways in small places and, and in big places. So small things we do is we help the operator understand if you change your flight profile, you'll generate fewer emissions. You may avoid controls if you flying a different way, maybe you create trails, you'll lose, you'll lose less fuel while you're doing that. So it's cost effective for you. There was always a balance point there between the wear and tear on the engine versus the, the, the environmental impact. And you find that optimum place. One of the first things we started doing with, with Scott is we have a, a way that we life our engine components. And one of the very simple outcomes of that is using that data, the blue data for connection to the customer. >>If we can see, effectively see inside the engine about how well it's wearing and we can extend those maintenance intervals as we talked about, what that eventually does is it reduces the need to take the engine off, ship it around the world. Probably on a great big 7, 4 7 or maybe year or two ago on an Anson off four big engines flying a long distance trek, shipping our engine to an overhaul facility. We're avoiding something like 200 of those shop visit overhauls a year. So every year that's 200 flights there and back again, which don't happen, right? Collectively that's around about 15,000 automobile equivalent emissions just don't happen. So simple things we can do just starts to have accumulative effect, >>Right? Simple things that you're doing that, that have a huge impact. We could talk for so much longer on stability, I'm sure we're out of time, but I can see why Roll Royce was, was the winner of the Inocular award. Congratulations. Well deserved. Well >>Deserved. I well >>Deserved. So interesting to hear about the intelligent engine. So you're gonna have to come back. Hopefully we'll be here next year and we can hear more of the evolution. Cuz I have a feeling there's never a dual moment in what you're doing. >>It's never a dull moment. There's never an end point. >>No. >>Okay, >>Going Scott, Nick, thank you so much for joining me on the program today. Thank you, Lisa. It's great to have you talk through what's going on at ifx and the partnership with Rolls Royce. We >>Appreciate, and again, Nick, Nick, thank you for your continued support in the partnership. >>I thank you, Scott. We appreciate it. Likewise, thank >>You. Kudos all around. All right, for my guests, I'm Lisa Martin, you're watching a Cube live from Miami. We're at IFS unleashed. We'll be back shortly after a break with our next guests. So stick around.

>>We're back with Jerome West, product management security lead at for HCI at Dell Technologies Hyper-converged infrastructure. Jerome, welcome. >>Thank you, David. >>Hey, Jerome, In this series, A blueprint for trusted infrastructure, we've been digging into the different parts of the infrastructure stack, including storage, servers and networking, and now we want to cover hyperconverged infrastructure. So my first question is, what's unique about HCI that presents specific security challenges? What do we need to know? >>So what's unique about Hyperconverge infrastructure is the breadth of the security challenge. We can't simply focus on a single type of IT system, so like a server or a storage system or a virtualization piece of software. I mean, HCI is all of those things. So luckily we have excellent partners like VMware, Microsoft, and internal partners like the Dell Power Edge team, the Dell storage team, the Dell networking team, and on and on. These partnerships, in these collaborations are what make us successful from a security standpoint. So let me give you an example to illustrate. In the recent past, we're seeing growing scope and sophistication in supply chain attacks. This mean an attacker is going to attack your software supply chain upstream so that hopefully a piece of code, malicious code that wasn't identified early in the software supply chain is distributed like a large player, like a VMware or Microsoft or a Dell. So to confront this kind of sophisticated hard to defeat problem, we need short term solutions and we need long term solutions as well. >>So for the short term solution, the obvious thing to do is to patch the vulnerability. The complexity is for our HCI portfolio. We build our software on VMware, so we would have to consume a patch that VMware would produce and provide it to our customers in a timely manner. Luckily, VX Rail's engineering team has co engineered a release process with VMware that significantly shortens our development life cycle so that VMware will produce a patch and within 14 days we will integrate our own code. With the VMware release, we will have tested and validated the update and we will give an update to our customers within 14 days of that VMware release. That as a result of this kind of rapid development process, Vxl had over 40 releases of software updates last year for a longer term solution. We're partnering with VMware and others to develop a software bill of materials. We work with VMware to consume their software manifest, including their upstream vendors and their open source providers to have a comprehensive list of software components. Then we aren't caught off guard by an unforeseen vulnerability and we're more able to easily detect where the software problem lies so that we can quickly address it. So these are the kind of relationships and solutions that we can co engineer with effective collaborations with our, with our partners. >>Great, Thank you for that. That description. So if I had to define what cybersecurity resilience means to HCI or converged infrastructure, and to me my takeaway was you gotta have a short term instant patch solution and then you gotta do an integration in a very short time, you know, two weeks to then have that integration done. And then longer term you have to have a software bill of materials so that you can ensure the providence of all the components help us. Is that a right way to think about cybersecurity resilience? Do you have, you know, a additives to that definition? >>I do. I really think that site cybersecurity and resilience for hci, because like I said, it has sort of unprecedented breadth across our portfolio. It's not a single thing, it's a bit of everything. So really the strength or the secret sauce is to combine all the solutions that our partner develops while integrating them with our own layer. So let me, let me give you an example. So hci, it's a, basically taking a software abstraction of hardware functionality and implementing it into something called the virtualized layer. It's basically the virtual virtualizing hardware functionality, like say a storage controller, you could implement it in a hardware, but for hci, for example, in our VX rail portfolio, we, or our vxl product, we integrate it into a product called vsan, which is provided by our partner VMware. So that portfolio strength is still, you know, through our, through our partnerships. >>So what we do, we integrate these, these security functionality and features in into our product. So our partnership grows to our ecosystem through products like VMware, products like nsx, Verizon, Carbon Black and Bsphere. All of them integrate seamlessly with VMware. And we also leverage VMware's software, par software partnerships on top of that. So for example, VX supports multifactor authentication through bsphere integration with something called Active Directory Federation services for adfs. So there is a lot of providers that support adfs, including Microsoft Azure. So now we can support a wide array of identity providers such as Off Zero or I mentioned Azure or Active Directory through that partnership. So we can leverage all of our partners partnerships as well. So there's sort of a second layer. So being able to secure all of that, that provides a lot of options and flexibility for our customers. So basically to summarize my my answer, we consume all of the security advantages of our partners, but we also expand on that to make a product that is comprehensively secured at multiple layers from the hardware layer that's provided by Dell through Power Edge to the hyper-converged software that we build ourselves to the virtualization layer that we get through our partnerships with Microsoft and VMware. >>Great. I mean that's super helpful. You've mentioned nsx, Horizon, Carbon Black, all the, you know, the VMware component OTH zero, which the developers are gonna love. You got Azure identity, so it's really an ecosystem. So you may have actually answered my next question, but I'm gonna ask it anyway cuz you've got this software defined environment and you're managing servers and networking and storage with this software led approach, how do you ensure that the entire system is secure end to end? >>That's a really great question. So the, the answer is we do testing and validation as part of the engineering process. It's not just bolted on at the end. So when we do, for example, the xra is the market's only co engineered solution with VMware, other vendors sell VMware as a hyperconverged solution, but we actually include security as part of the co-engineering process with VMware. So it's considered when VMware builds their code and their process dovetails with ours because we have a secure development life cycle, which other products might talk about in their discussions with you that we integrate into our engineering life cycle. So because we follow the same framework, all of the, all of the codes should interoperate from a security standpoint. And so when we do our final validation testing when we do a software release, we're already halfway there in ensuring that all these features will give the customers what we promised. >>That's great. All right, let's, let's close pitch me, what would you say is the strong suit summarize the, the strengths of the Dell hyperconverged infrastructure and converged infrastructure portfolio specifically from a security perspective? Jerome? >>So I talked about how hyper hyper-converged infrastructure simplifies security management because basically you're gonna take all of these features that are abstracted in in hardware, they're now abstracted in the virtualization layer. Now you can manage them from a single point of view, whether it would be, say, you know, in for VX rail would be b be center, for example. So by abstracting all this, you make it very easy to manage security and highly flexible because now you don't have limitations around a single vendor. You have a multiple array of choices and partnerships to select. So I would say that is the, the key to making it to hci. Now, what makes Dell the market leader in HCI is not only do we have that functionality, but we also make it exceptionally useful to you because it's co engineered, it's not bolted on. So I gave the example of, I gave the example of how we, we modify our software release process with VMware to make it very responsive. >>A couple of other features that we have specific just to HCI are digitally signed LCM updates. This is an example of a feature that we have that's only exclusive to Dell that's not done through a partnership. So we digitally sign our software updates so you, the user can be sure that the, the update that they're installing into their system is an authentic and unmodified product. So we give it a Dell signature that's invalidated prior to installation. So not only do we consume the features that others develop in a seamless and fully validated way, but we also bolt on our own specific HCI security features that work with all the other partnerships and give the user an exceptional security experience. So for, for example, the benefit to the customer is you don't have to create a complicated security framework that's hard for your users to use and it's hard for your system administrators to manage. It all comes in a package. So it, it can be all managed through vCenter, for example, or, and then the specific hyper, hyper-converged functions can be managed through VxRail manager or through STDC manager. So there's very few pains of glass that the, the administrator or user ever has to worry about. It's all self contained and manageable. >>That makes a lot of sense. So you got your own infrastructure, you're applying your best practices to that, like the digital signatures, you've got your ecosystem, you're doing co-engineering with the ecosystems, delivering security in a package, minimizing the complexity at the infrastructure level. The reason Jerome, this is so important is because SecOps teams, you know, they gotta deal with cloud security, they gotta deal with multiple clouds. Now they have their shared responsibility model going across multiple, They got all this other stuff that they have to worry, they gotta secure containers and the run time and, and, and, and, and the platform and so forth. So they're being asked to do other things. If they have to worry about all the things that you just mentioned, they'll never get, you know, the, the securities is gonna get worse. So what my takeaway is, you're removing that infrastructure piece and saying, Okay guys, you now can focus on those other things that is not necessarily Dell's, you know, domain, but you, you know, you can work with other partners to, and your own teams to really nail that. Is that a fair summary? >>I think that is a fair summary because absolutely the worst thing you can do from a security perspective is provide a feature that's so unusable that the administrator disables it or other key security features. So when I work with my partners to define, to define and develop a new security feature, the thing I keep foremost in mind is, will this be something our users want to use in our administrators want to administer? Because if it's not, if it's something that's too difficult or onerous or complex, then I try to find ways to make it more user friendly and practical. And this is a challenge sometimes because we are, our products operate in highly regulated environments and sometimes they have to have certain rules and certain configurations that aren't the most user friendly or management friendly. So I, I put a lot of effort into thinking about how can we make this feature useful while still complying with all the regulations that we have to comply with. And by the way, we're very successful in a highly regulated space. We sell a lot of VxRail, for example, into the Department of Defense and banks and, and other highly regulated environments, and we're very successful >>There. Excellent. Okay, Jerome, thanks. We're gonna leave it there for now. I'd love to have you back to talk about the progress that you're making down the road. Things always, you know, advance in the tech industry and so would appreciate that. >>I would look forward to it. Thank you very much, Dave. >>You're really welcome. In a moment I'll be back to summarize the program and offer some resources that can help you on your journey to secure your enterprise infrastructure. I wanna thank our guests for their contributions and helping us understand how investments by a company like Dell can both reduce the need for dev sec up teams to worry about some of the more fundamental security issues around infrastructure and have greater confidence in the quality providence and data protection designed in to core infrastructure like servers, storage, networking, and hyper-converged systems. You know, at the end of the day, whether your workloads are in the cloud, OnPrem or at the edge, you are responsible for your own security. But vendor r and d and vendor process must play an important role in easing the burden faced by security devs and operation teams. And on behalf of the cube production content and social teams as well as Dell Technologies, we want to thank you for watching a blueprint for trusted infrastructure. Remember part one of this series as well as all the videos associated with this program, and of course, today's program are available on demand@thecube.net with additional coverage@siliconangle.com. And you can go to dell.com/security solutions dell.com/security solutions to learn more about Dell's approach to securing infrastructure. And there's tons of additional resources that can help you on your journey. This is Dave Valante for the Cube, your leader in enterprise and emerging tech coverage. We'll see you next time.

>>The cybersecurity landscape continues to be one characterized by a series of point tools designed to do a very specific job, often pretty well, but the mosaic of tooling is grown over the years causing complexity in driving up costs and increasing exposures. So the game of Whackamole continues. Moreover, the way organizations approach security is changing quite dramatically. The cloud, while offering so many advantages, has also created new complexities. The shared responsibility model redefines what the cloud provider secures, for example, the S three bucket and what the customer is responsible for eg properly configuring the bucket. You know, this is all well and good, but because virtually no organization of any size can go all in on a single cloud, that shared responsibility model now spans multiple clouds and with different protocols. Now that of course includes on-prem and edge deployments, making things even more complex. Moreover, the DevOps team is being asked to be the point of execution to implement many aspects of an organization's security strategy. >>This extends to securing the runtime, the platform, and even now containers which can end up anywhere. There's a real need for consolidation in the security industry, and that's part of the answer. We've seen this both in terms of mergers and acquisitions as well as platform plays that cover more and more ground. But the diversity of alternatives and infrastructure implementations continues to boggle the mind with more and more entry points for the attackers. This includes sophisticated supply chain attacks that make it even more difficult to understand how to secure components of a system and how secure those components actually are. The number one challenge CISOs face in today's complex world is lack of talent to address these challenges. And I'm not saying that SecOps pros are not talented, They are. There just aren't enough of them to go around and the adversary is also talented and very creative, and there are more and more of them every day. >>Now, one of the very important roles that a technology vendor can play is to take mundane infrastructure security tasks off the plates of SEC off teams. Specifically we're talking about shifting much of the heavy lifting around securing servers, storage, networking, and other infrastructure and their components onto the technology vendor via r and d and other best practices like supply chain management. And that's what we're here to talk about. Welcome to the second part in our series, A Blueprint for Trusted Infrastructure Made Possible by Dell Technologies and produced by the Cube. My name is Dave Ante and I'm your host now. Previously we looked at what trusted infrastructure means and the role that storage and data protection play in the equation. In this part two of the series, we explore the changing nature of technology infrastructure, how the industry generally in Dell specifically, are adapting to these changes and what is being done to proactively address threats that are increasingly stressing security teams. >>Now today, we continue the discussion and look more deeply into servers networking and hyper-converged infrastructure to better understand the critical aspects of how one company Dell is securing these elements so that dev sec op teams can focus on the myriad new attack vectors and challenges that they faced. First up is Deepak rang Garage Power Edge security product manager at Dell Technologies. And after that we're gonna bring on Mahesh Nagar oim, who was consultant in the networking product management area at Dell. And finally, we're close with Jerome West, who is the product management security lead for HCI hyperconverged infrastructure and converged infrastructure at Dell. Thanks for joining us today. We're thrilled to have you here and hope you enjoy the program. Deepak Arage shoes powered security product manager at Dell Technologies. Deepak, great to have you on the program. Thank you. >>Thank you for having me. >>So we're going through the infrastructure stack and in part one of this series we looked at the landscape overall and how cyber has changed and specifically how Dell thinks about data protection in, in security in a manner that both secures infrastructure and minimizes organizational friction. We also hit on the storage part of the portfolio. So now we want to dig into servers. So my first question is, what are the critical aspects of securing server infrastructure that our audience should be aware of? >>Sure. So if you look at compute in general, right, it has rapidly evolved over the past couple of years, especially with trends toward software defined data centers and with also organizations having to deal with hybrid environments where they have private clouds, public cloud locations, remote offices, and also remote workers. So on top of this, there's also an increase in the complexity of the supply chain itself, right? There are companies who are dealing with hundreds of suppliers as part of their supply chain. So all of this complexity provides a lot of opportunity for attackers because it's expanding the threat surface of what can be attacked, and attacks are becoming more frequent, more severe and more sophisticated. And this has also triggered around in the regulatory and mandates around the security needs. >>And these regulations are not just in the government sector, right? So it extends to critical infrastructure and eventually it also get into the private sector. In addition to this, organizations are also looking at their own internal compliance mandates. And this could be based on the industry in which they're operating in, or it could be their own security postures. And this is the landscape in which servers they're operating today. And given that servers are the foundational blocks of the data center, it becomes extremely important to protect them. And given how complex the modern server platforms are, it's also extremely difficult and it takes a lot of effort. And this means protecting everything from the supply chain to the manufacturing and then eventually the assuring the hardware and software integrity of the platforms and also the operations. And there are very few companies that go to the lens that Dell does in order to secure the server. We truly believe in the notion and the security mentality that, you know, security should enable our customers to go focus on their business and proactively innovate on their business and it should not be a burden to them. And we heavily invest to make that possible for our customers. >>So this is really important because the premise that I set up at the beginning of this was really that I, as of security pro, I'm not a security pro, but if I were, I wouldn't want to be doing all this infrastructure stuff because I now have all these new things I gotta deal with. I want a company like Dell who has the resources to build that security in to deal with the supply chain to ensure the providence, et cetera. So I'm glad you you, you hit on that, but so given what you just said, what does cybersecurity resilience mean from a server perspective? For example, are there specific principles that Dell adheres to that are non-negotiable? Let's say, how does Dell ensure that its customers can trust your server infrastructure? >>Yeah, like when, when it comes to security at Dell, right? It's ingrained in our product, so that's the best way to put it. And security is nonnegotiable, right? It's never an afterthought where we come up with a design and then later on figure out how to go make it secure, right? Our security development life cycle, the products are being designed to counter these threats right from the big. And in addition to that, we are also testing and evaluating these products continuously to identify vulnerabilities. We also have external third party audits which supplement this process. And in addition to this, Dell makes the commitment that we will rapidly respond to any mitigations and vulnerability, any vulnerabilities and exposures found out in the field and provide mitigations and patches for in attacking manner. So this security principle is also built into our server life cycle, right? Every phase of it. >>So we want our products to provide cutting edge capabilities when it comes to security. So as part of that, we are constantly evaluating what our security model is done. We are building on it and continuously improving it. So till a few years ago, our model was primarily based on the N framework of protect, detect and rigor. And it's still aligns really well to that framework, but over the past couple of years, we have seen how computers evolved, how the threads have evolved, and we have also seen the regulatory trends and we recognize the fact that the best security strategy for the modern world is a zero trust approach. And so now when we are building our infrastructure and tools and offerings for customers, first and foremost, they're cyber resilient, right? What we mean by that is they're capable of anticipating threats, withstanding attacks and rapidly recurring from attacks and also adapting to the adverse conditions in which they're deployed. The process of designing these capabilities and identifying these capabilities however, is done through the zero press framework. And that's very important because now we are also anticipating how our customers will end up using these capabilities at there and to enable their own zero trust IT environments and IT zero trusts deployments. We have completely adapted our security approach to make it easier for customers to work with us no matter where they are in their journey towards zero trust option. >>So thank you for that. You mentioned the, this framework, you talked about zero trust. When I think about n I think as well about layered approaches. And when I think about zero trust, I think about if you, if you don't have access to it, you're not getting access, you've gotta earn that, that access and you've got layers and then you still assume that bad guys are gonna get in. So you've gotta detect that and you've gotta response. So server infrastructure security is so fundamental. So my question is, what is Dell providing specifically to, for example, detect anomalies and breaches from unauthorized activity? How do you enable fast and easy or facile recovery from malicious incidents, >>Right? What is that is exactly right, right? Breachers are bound to happen and given how complex our current environment is, it's extremely distributed and extremely connected, right? Data and users are no longer contained with an offices where we can set up a perimeter firewall and say, Yeah, everything within that is good. We can trust everything within it. That's no longer true. The best approach to protect data and infrastructure in the current world is to use a zero trust approach, which uses the principles. Nothing is ever trusted, right? Nothing is trusted implicitly. You're constantly verifying every single user, every single device, and every single access in your system at every single level of your ID environment. And this is the principles that we use on power Edge, right? But with an increased focus on providing granular controls and checks based on the principles of these privileged access. >>So the idea is that service first and foremost need to make sure that the threats never enter and they're rejected at the point of entry, but we recognize breaches are going to occur and if they do, they need to be minimized such that the sphere of damage cost by attacker is minimized so they're not able to move from one part of the network to something else laterally or escalate their privileges and cause more damage, right? So the impact radius for instance, has to be radius. And this is done through features like automated detection capabilities and automation, automated remediation capabilities. So some examples are as part of our end to end boot resilience process, we have what they call a system lockdown, right? We can lock down the configuration of the system and lock on the form versions and all changes to the system. And we have capabilities which automatically detect any drift from that lockdown configuration and we can figure out if the drift was caused to authorized changes or unauthorized changes. >>And if it is an unauthorize change can log it, generate security alerts, and we even have capabilities to automatically roll the firm where, and always versions back to a known good version and also the configurations, right? And this becomes extremely important because as part of zero trust, we need to respond to these things at machine speed and we cannot do it at a human speed. And having these automated capabilities is a big deal when achieving that zero trust strategy. And in addition to this, we also have chassis inclusion detection where if the chassis, the box, the several box is opened up, it logs alerts, and you can figure out even later if there's an AC power cycle, you can go look at the logs to see that the box is opened up and figure out if there was a, like a known authorized access or some malicious actor opening and chain something in your system. >>Great, thank you for that lot. Lot of detail and and appreciate that. I want to go somewhere else now cuz Dell has a renowned supply chain reputation. So what about securing the, the supply chain and the server bill of materials? What does Dell specifically do to track the providence of components it uses in its systems so that when the systems arrive, a customer can be a hundred percent certain that that system hasn't been compromised, >>Right? And we've talked about how complex the modern supply chain is, right? And that's no different for service. We have hundreds of confidence on the server and a lot of these form where in order to be configured and run and this former competence could be coming from third parties suppliers. So now the complexity that we are dealing with like was the end to end approach and that's where Dell pays a lot of attention into assuring the security approach approaching and it starts all the way from sourcing competence, right? And then through the design and then even the manufacturing process where we are wetting the personnel leather factories and wetting the factories itself. And the factories also have physical controls, physical security controls built into them and even shipping, right? We have GPS tagging of packages. So all of this is built to ensure supply chain security. >>But a critical aspect of this is also making sure that the systems which are built in the factories are delivered to the customers without any changes or any tapper. And we have a feature called the secure component verification, which is capable of doing this. What the feature does this, when the system gets built in a factory, it generates an inventory of all the competence in the system and it creates a cryptographic certificate based on the signatures presented to this by the competence. And this certificate is stored separately and sent to the customers separately from the system itself. So once the customers receive the system at their end, they can run out to, it generates an inventory of the competence on the system at their end and then compare it to the golden certificate to make sure nothing was changed. And if any changes are detected, we can figure out if there's an authorized change or unauthorize change. >>Again, authorized changes could be like, you know, upgrades to the drives or memory and ized changes could be any sort of temper. So that's the supply chain aspect of it and bill of metal use is also an important aspect to galing security, right? And we provide a software bill of materials, which is basically a list of ingredients of all the software pieces in the platform. So what it allows our customers to do is quickly take a look at all the different pieces and compare it to the vulnerability database and see if any of the vulner which have been discovered out in the wild affected platform. So that's a quick way of figuring out if the platform has any known vulnerabilities and it has not been patched. >>Excellent. That's really good. My last question is, I wonder if you, you know, give us the sort of summary from your perspective, what are the key strengths of Dell server portfolio from a security standpoint? I'm really interested in, you know, the uniqueness and the strong suit that Dell brings to the table, >>Right? Yeah. We have talked enough about the complexity of the environment and how zero risk is necessary for the modern ID environment, right? And this is integral to Dell powered service. And as part of that like you know, security starts with the supply chain. We already talked about the second component verification, which is a beneath feature that Dell platforms have. And on top of it we also have a silicon place platform mode of trust. So this is a key which is programmed into the silicon on the black service during manufacturing and can never be changed after. And this immutable key is what forms the anchor for creating the chain of trust that is used to verify everything in the platform from the hardware and software integrity to the boot, all pieces of it, right? In addition to that, we also have a host of data protection features. >>Whether it is protecting data at risk in news or inflight, we have self encrypting drives which provides scalable and flexible encryption options. And this couple with external key management provides really good protection for your data address. External key management is important because you know, somebody could physically steam the server walk away, but then the keys are not stored on the server, it stood separately. So that provides your action layer of security. And we also have dual layer encryption where you can compliment the hardware encryption on the secure encrypted drives with software level encryption. Inion to this we have identity and access management features like multifactor authentication, single sign on roles, scope and time based access controls, all of which are critical to enable that granular control and checks for zero trust approach. So I would say like, you know, if you look at the Dell feature set, it's pretty comprehensive and we also have the flexibility built in to meet the needs of all customers no matter where they fall in the spectrum of, you know, risk tolerance and security sensitivity. And we also have the capabilities to meet all the regulatory requirements and compliance requirements. So in a nutshell, I would say that you know, Dell Power Service cyber resident infrastructure helps accelerate zero tested option for customers. >>Got it. So you've really thought this through all the various things that that you would do to sort of make sure that your server infrastructure is secure, not compromised, that your supply chain is secure so that your customers can focus on some of the other things that they have to worry about, which are numerous. Thanks Deepak, appreciate you coming on the cube and participating in the program. >>Thank you for having >>You're welcome. In a moment I'll be back to dig into the networking portion of the infrastructure. Stay with us for more coverage of a blueprint for trusted infrastructure and collaboration with Dell Technologies on the cube, your leader in enterprise and emerging tech coverage. We're back with a blueprint for trusted infrastructure and partnership with Dell Technologies in the cube. And we're here with Mahesh Nager, who is a consultant in the area of networking product management at Dell Technologies. Mahesh, welcome, good to see you. >>Hey, good morning Dell's, nice to meet, meet to you as well. >>Hey, so we've been digging into all the parts of the infrastructure stack and now we're gonna look at the all important networking components. Mahesh, when we think about networking in today's environment, we think about the core data center and we're connecting out to various locations including the cloud and both the near and the far edge. So the question is from Dell's perspective, what's unique and challenging about securing network infrastructure that we should know about? >>Yeah, so few years ago IT security and an enterprise was primarily putting a wrapper around data center out because it was constrained to an infrastructure owned and operated by the enterprise for the most part. So putting a rapid around it like a parameter or a firewall was a sufficient response because you could basically control the environment and data small enough control today with the distributed data, intelligent software, different systems, multi-cloud environment and asset service delivery, you know, the infrastructure for the modern era changes the way to secure the network infrastructure In today's, you know, data driven world, it operates everywhere and data has created and accessed everywhere so far from, you know, the centralized monolithic data centers of the past. The biggest challenge is how do we build the network infrastructure of the modern era that are intelligent with automation enabling maximum flexibility and business agility without any compromise on the security. We believe that in this data era, the security transformation must accompany digital transformation. >>Yeah, that's very good. You talked about a couple of things there. Data by its very nature is distributed. There is no perimeter anymore, so you can't just, as you say, put a rapper around it. I like the way you phrase that. So when you think about cyber security resilience from a networking perspective, how do you define that? In other words, what are the basic principles that you adhere to when thinking about securing network infrastructure for your customers? >>So our belief is that cybersecurity and cybersecurity resilience, they need to be holistic, they need to be integrated, scalable, one that span the entire enterprise and with a co and objective and policy implementation. So cybersecurity needs to span across all the devices and running across any application, whether the application resets on the cloud or anywhere else in the infrastructure. From a networking standpoint, what does it mean? It's again, the same principles, right? You know, in order to prevent the threat actors from accessing changing best destroy or stealing sensitive data, this definition holds good for networking as well. So if you look at it from a networking perspective, it's the ability to protect from and withstand attacks on the networking systems as we continue to evolve. This will also include the ability to adapt and recover from these attacks, which is what cyber resilience aspect is all about. So cybersecurity best practices, as you know, is continuously changing the landscape primarily because the cyber threats also continue to evolve. >>Yeah, got it. So I like that. So it's gotta be integrated, it's gotta be scalable, it's gotta be comprehensive, comprehensive and adaptable. You're saying it can't be static, >>Right? Right. So I think, you know, you had a second part of a question, you know, that says what do we, you know, what are the basic principles? You know, when you think about securing network infrastructure, when you're looking at securing the network infrastructure, it revolves around core security capability of the devices that form the network. And what are these security capabilities? These are access control, software integrity and vulnerability response. When you look at access control, it's to ensure that only the authenticated users are able to access the platform and they're able to access only the kind of the assets that they're authorized to based on their user level. Now accessing a network platform like a switch or a rotor for example, is typically used for say, configuration and management of the networking switch. So user access is based on say roles for that matter in a role based access control, whether you are a security admin or a network admin or a storage admin. >>And it's imperative that logging is enable because any of the change to the configuration is actually logged and monitored as that. Talking about software's integrity, it's the ability to ensure that the software that's running on the system has not been compromised. And, and you know, this is important because it could actually, you know, get hold of the system and you know, you could get UND desire results in terms of say validation of the images. It's, it needs to be done through say digital signature. So, so it's important that when you're talking about say, software integrity, a, you are ensuring that the platform is not compromised, you know, is not compromised and be that any upgrades, you know, that happens to the platform is happening through say validated signature. >>Okay. And now, now you've now, so there's access control, software integrity, and I think you, you've got a third element which is i I think response, but please continue. >>Yeah, so you know, the third one is about civil notability. So we follow the same process that's been followed by the rest of the products within the Dell product family. That's to report or identify, you know, any kind of a vulnerability that's being addressed by the Dell product security incident response team. So the networking portfolio is no different, you know, it follows the same process for identification for tri and for resolution of these vulnerabilities. And these are addressed either through patches or through new reasons via networking software. >>Yeah, got it. Okay. So I mean, you didn't say zero trust, but when you were talking about access control, you're really talking about access to only those assets that people are authorized to access. I know zero trust sometimes is a buzzword, but, but you I think gave it, you know, some clarity there. Software integrity, it's about assurance validation, your digital signature you mentioned and, and that there's been no compromise. And then how you respond to incidents in a standard way that can fit into a security framework. So outstanding description, thank you for that. But then the next question is, how does Dell networking fit into the construct of what we've been talking about Dell trusted infrastructure? >>Okay, so networking is the key element in the Dell trusted infrastructure. It provides the interconnect between the service and the storage world. And you know, it's part of any data center configuration for a trusted infrastructure. The network needs to have access control in place where only the authorized nels are able to make change to the network configuration and logging off any of those changes is also done through the logging capabilities. Additionally, we should also ensure that the configuration should provide network isolation between say the management network and the data traffic network because they need to be separate and distinct from each other. And furthermore, even if you look at the data traffic network and now you have things like segmentation isolated segments and via VRF or, or some micro segmentation via partners, this allows various level of security for each of those segments. So it's important you know, that, that the network infrastructure has the ability, you know, to provide all this, this services from a Dell networking security perspective, right? >>You know, there are multiple layer of defense, you know, both at the edge and in the network in this hardware and in the software and essentially, you know, a set of rules and a configuration that's designed to sort of protect the integrity, confidentiality, and accessibility of the network assets. So each network security layer, it implements policies and controls as I said, you know, including send network segmentation. We do have capabilities sources, centralized management automation and capability and scalability for that matter. Now you add all of these things, you know, with the open networking standards or software, different principles and you essentially, you know, reach to the point where you know, you're looking at zero trust network access, which is essentially sort of a building block for increased cloud adoption. If you look at say that you know the different pillars of a zero trust architecture, you know, if you look at the device aspect, you know, we do have support for security for example, we do have say trust platform in a trusted platform models tpms on certain offer products and you know, the physical security know plain, simple old one love port enable from a user trust perspective, we know it's all done via access control days via role based access control and say capability in order to provide say remote authentication or things like say sticky Mac or Mac learning limit and so on. >>If you look at say a transport and decision trust layer, these are essentially, you know, how do you access, you know, this switch, you know, is it by plain hotel net or is it like secure ssh, right? And you know, when a host communicates, you know, to the switch, we do have things like self-signed or is certificate authority based certification. And one of the important aspect is, you know, in terms of, you know, the routing protocol, the routing protocol, say for example BGP for example, we do have the capability to support MD five authentication between the b g peers so that there is no, you know, manages attack, you know, to the network where the routing table is compromised. And the other aspect is about second control plane is here, you know, you know, it's, it's typical that if you don't have a control plane here, you know, it could be flooded and you know, you know, the switch could be compromised by city denial service attacks. >>From an application test perspective, as I mentioned, you know, we do have, you know, the application specific security rules where you could actually define, you know, the specific security rules based on the specific applications, you know, that are running within the system. And I did talk about, say the digital signature and the cryptographic check that we do for authentication and for, I mean rather for the authenticity and the validation of, you know, of the image and the BS and so on and so forth. Finally, you know, the data trust, we are looking at, you know, the network separation, you know, the network separation could happen or VRF plain old wheel Ls, you know, which can bring about sales multi 10 aspects. We talk about some microsegmentation as it applies to nsx for example. The other aspect is, you know, we do have, with our own smart fabric services that's enabled in a fabric, we have a concept of c cluster security. So all of this, you know, the different pillars, they sort of make up for the zero trust infrastructure for the networking assets of an infrastructure. >>Yeah. So thank you for that. There's a, there's a lot to unpack there. You know, one of the premise, the premise really of this, this, this, this segment that we're setting up in this series is really that everything you just mentioned, or a lot of things you just mentioned used to be the responsibility of the security team. And, and the premise that we're putting forth is that because security teams are so stretched thin, you, you gotta shift the vendor community. Dell specifically is shifting a lot of those tasks to their own r and d and taking care of a lot of that. So, cuz scop teams got a lot of other stuff to, to worry about. So my question relates to things like automation, which can help and scalability, what about those topics as it relates to networking infrastructure? >>Okay, our >>Portfolio, it enables state of the automation software, you know, that enables simplifying of the design. So for example, we do have, you know, you know the fabric design center, you know, a tool that automates the design of the fabric and you know, from a deployment and you know, the management of the network infrastructure that are simplicities, you know, using like Ansible s for Sonic for example are, you know, for a better sit and tell story. You know, we do have smart fabric services that can automate the entire fabric, you know, for a storage solution or for, you know, for one of the workloads for example. Now we do help reduce the complexity by closely integrating the management of the physical and the virtual networking infrastructure. And again, you know, we have those capabilities using Sonic or Smart Traffic services. If you look at Sonic for example, right? >>It delivers automated intent based secure containerized network and it has the ability to provide some network visibility and Avan has and, and all of these things are actually valid, you know, for a modern networking infrastructure. So now if you look at Sonic, you know, it's, you know, the usage of those tools, you know, that are available, you know, within the Sonic no is not restricted, you know, just to the data center infrastructure is, it's a unified no, you know, that's well applicable beyond the data center, you know, right up to the edge. Now if you look at our north from a smart traffic OS 10 perspective, you know, as I mentioned, we do have smart traffic services which essentially, you know, simplifies the deployment day zero, I mean rather day one, day two deployment expansion plans and the lifecycle management of our conversion infrastructure and hyper and hyper conversion infrastructure solutions. And finally, in order to enable say, zero touch deployment, we do have, you know, a VP solution with our SD van capability. So these are, you know, ways by which we bring down the complexity by, you know, enhancing the automation capability using, you know, a singular loss that can expand from a data center now right to the edge. >>Great, thank you for that. Last question real quick, just pitch me, what can you summarize from your point of view, what's the strength of the Dell networking portfolio? >>Okay, so from a Dell networking portfolio, we support capabilities at multiple layers. As I mentioned, we're talking about the physical security for examples, say disabling of the unused interface. Sticky Mac and trusted platform modules are the things that to go after. And when you're talking about say secure boot for example, it delivers the authenticity and the integrity of the OS 10 images at the startup. And Secure Boot also protects the startup configuration so that, you know, the startup configuration file is not compromised. And Secure port also enables the workload of prediction, for example, that is at another aspect of software image integrity validation, you know, wherein the image is data for the digital signature, you know, prior to any upgrade process. And if you are looking at secure access control, we do have things like role based access control, SSH to the switches, control plane access control that pre do tags and say access control from multifactor authentication. >>We do have various tech ads for entry control to the network and things like CSE and PRV support, you know, from a federal perspective we do have say logging wherein, you know, any event, any auditing capabilities can be possible by say looking at the clog service, you know, which are pretty much in our transmitter from the devices overts for example, and last we talked about say network segment, you know, say network separation and you know, these, you know, separation, you know, ensures that are, that is, you know, a contained say segment, you know, for a specific purpose or for the specific zone and, you know, just can be implemented by a, a micro segmentation, you know, just a plain old wheel or using virtual route of framework VR for example. >>A lot there. I mean I think frankly, you know, my takeaway is you guys do the heavy lifting in a very complicated topic. So thank you so much for, for coming on the cube and explaining that in in quite some depth. Really appreciate it. >>Thank you indeed. >>Oh, you're very welcome. Okay, in a moment I'll be back to dig into the hyper-converged infrastructure part of the portfolio and look at how when you enter the world of software defined where you're controlling servers and storage and networks via software led system, you could be sure that your infrastructure is trusted and secure. You're watching a blueprint for trusted infrastructure made possible by Dell Technologies and collaboration with the cube, your leader in enterprise and emerging tech coverage, your own west product management security lead at for HCI at Dell Technologies hyper-converged infrastructure. Jerome, welcome. >>Thank you Dave. >>Hey Jerome, in this series of blueprint for trusted infrastructure, we've been digging into the different parts of the infrastructure stack, including storage servers and networking, and now we want to cover hyperconverged infrastructure. So my first question is, what's unique about HCI that presents specific security challenges? What do we need to know? >>So what's unique about hyper-converge infrastructure is the breadth of the security challenge. We can't simply focus on a single type of IT system. So like a server or storage system or a virtualization piece of software, software. I mean HCI is all of those things. So luckily we have excellent partners like VMware, Microsoft, and internal partners like the Dell Power Edge team, the Dell storage team, the Dell networking team, and on and on. These partnerships in these collaborations are what make us successful from a security standpoint. So let me give you an example to illustrate. In the recent past we're seeing growing scope and sophistication in supply chain attacks. This mean an attacker is going to attack your software supply chain upstream so that hopefully a piece of code, malicious code that wasn't identified early in the software supply chain is distributed like a large player, like a VMware or Microsoft or a Dell. So to confront this kind of sophisticated hard to defeat problem, we need short term solutions and we need long term solutions as well. >>So for the short term solution, the obvious thing to do is to patch the vulnerability. The complexity is for our HCI portfolio. We build our software on VMware, so we would have to consume a patch that VMware would produce and provide it to our customers in a timely manner. Luckily VX rail's engineering team has co engineered a release process with VMware that significantly shortens our development life cycle so that VMware would produce a patch and within 14 days we will integrate our own code with the VMware release we will have tested and validated the update and we will give an update to our customers within 14 days of that VMware release. That as a result of this kind of rapid development process, VHA had over 40 releases of software updates last year for a longer term solution. We're partnering with VMware and others to develop a software bill of materials. We work with VMware to consume their software manifest, including their upstream vendors and their open source providers to have a comprehensive list of software components. Then we aren't caught off guard by an unforeseen vulnerability and we're more able to easily detect where the software problem lies so that we can quickly address it. So these are the kind of relationships and solutions that we can co engineer with effective collaborations with our, with our partners. >>Great, thank you for that. That description. So if I had to define what cybersecurity resilience means to HCI or converged infrastructure, and to me my takeaway was you gotta have a short term instant patch solution and then you gotta do an integration in a very short time, you know, two weeks to then have that integration done. And then longer term you have to have a software bill of materials so that you can ensure the providence of all the components help us. Is that a right way to think about cybersecurity resilience? Do you have, you know, a additives to that definition? >>I do. I really think that's site cybersecurity and resilience for hci because like I said, it has sort of unprecedented breadth across our portfolio. It's not a single thing, it's a bit of everything. So really the strength or the secret sauce is to combine all the solutions that our partner develops while integrating them with our own layer. So let me, let me give you an example. So hci, it's a, basically taking a software abstraction of hardware functionality and implementing it into something called the virtualized layer. It's basically the virtual virtualizing hardware functionality, like say a storage controller, you could implement it in hardware, but for hci, for example, in our VX rail portfolio, we, our Vxl product, we integrated it into a product called vsan, which is provided by our partner VMware. So that portfolio of strength is still, you know, through our, through our partnerships. >>So what we do, we integrate these, these security functionality and features in into our product. So our partnership grows to our ecosystem through products like VMware, products like nsx, Horizon, Carbon Black and vSphere. All of them integrate seamlessly with VMware and we also leverage VMware's software, part software partnerships on top of that. So for example, VX supports multifactor authentication through vSphere integration with something called Active Directory Federation services for adfs. So there's a lot of providers that support adfs including Microsoft Azure. So now we can support a wide array of identity providers such as Off Zero or I mentioned Azure or Active Directory through that partnership. So we can leverage all of our partners partnerships as well. So there's sort of a second layer. So being able to secure all of that, that provides a lot of options and flexibility for our customers. So basically to summarize my my answer, we consume all of the security advantages of our partners, but we also expand on them to make a product that is comprehensively secured at multiple layers from the hardware layer that's provided by Dell through Power Edge to the hyper-converged software that we build ourselves to the virtualization layer that we get through our partnerships with Microsoft and VMware. >>Great, I mean that's super helpful. You've mentioned nsx, Horizon, Carbon Black, all the, you know, the VMware component OTH zero, which the developers are gonna love. You got Azure identity, so it's really an ecosystem. So you may have actually answered my next question, but I'm gonna ask it anyway cuz you've got this software defined environment and you're managing servers and networking and storage with this software led approach, how do you ensure that the entire system is secure end to end? >>That's a really great question. So the, the answer is we do testing and validation as part of the engineering process. It's not just bolted on at the end. So when we do, for example, VxRail is the market's only co engineered solution with VMware, other vendors sell VMware as a hyper converged solution, but we actually include security as part of the co-engineering process with VMware. So it's considered when VMware builds their code and their process dovetails with ours because we have a secure development life cycle, which other products might talk about in their discussions with you that we integrate into our engineering life cycle. So because we follow the same framework, all of the, all of the codes should interoperate from a security standpoint. And so when we do our final validation testing when we do a software release, we're already halfway there in ensuring that all these features will give the customers what we promised. >>That's great. All right, let's, let's close pitch me, what would you say is the strong suit summarize the, the strengths of the Dell hyper-converged infrastructure and converged infrastructure portfolio specifically from a security perspective? Jerome? >>So I talked about how hyper hyper-converged infrastructure simplifies security management because basically you're gonna take all of these features that are abstracted in in hardware, they're now abstracted in the virtualization layer. Now you can manage them from a single point of view, whether it would be, say, you know, in for VX rail would be b be center, for example. So by abstracting all this, you make it very easy to manage security and highly flexible because now you don't have limitations around a single vendor. You have a multiple array of choices and partnerships to select. So I would say that is the, the key to making it to hci. Now, what makes Dell the market leader in HCI is not only do we have that functionality, but we also make it exceptionally useful to you because it's co engineered, it's not bolted on. So I gave the example of spo, I gave the example of how we, we modify our software release process with VMware to make it very responsive. >>A couple of other features that we have specific just to HCI are digitally signed LCM updates. This is an example of a feature that we have that's only exclusive to Dell that's not done through a partnership. So we digitally signed our software updates so the user can be sure that the, the update that they're installing into their system is an authentic and unmodified product. So we give it a Dell signature that's invalidated prior to installation. So not only do we consume the features that others develop in a seamless and fully validated way, but we also bolt on our own a specific HCI security features that work with all the other partnerships and give the user an exceptional security experience. So for, for example, the benefit to the customer is you don't have to create a complicated security framework that's hard for your users to use and it's hard for your system administrators to manage it all comes in a package. So it, it can be all managed through vCenter, for example, or, and then the specific hyper, hyper-converged functions can be managed through VxRail manager or through STDC manager. So there's very few pains of glass that the, the administrator or user ever has to worry about. It's all self contained and manageable. >>That makes a lot of sense. So you've got your own infrastructure, you're applying your best practices to that, like the digital signatures, you've got your ecosystem, you're doing co-engineering with the ecosystems, delivering security in a package, minimizing the complexity at the infrastructure level. The reason Jerome, this is so important is because SecOps teams, you know, they gotta deal with cloud security, they gotta deal with multiple clouds. Now they have their shared responsibility model going across multiple cl. They got all this other stuff that they have to worry, they gotta secure the containers and the run time and and, and, and, and the platform and so forth. So they're being asked to do other things. If they have to worry about all the things that you just mentioned, they'll never get, you know, the, the securities is gonna get worse. So what my takeaway is, you're removing that infrastructure piece and saying, Okay guys, you now can focus on those other things that is not necessarily Dell's, you know, domain, but you, you know, you can work with other partners to and your own teams to really nail that. Is that a fair summary? >>I think that is a fair summary because absolutely the worst thing you can do from a security perspective is provide a feature that's so unusable that the administrator disables it or other key security features. So when I work with my partners to define, to define and develop a new security feature, the thing I keep foremost in mind is, will this be something our users want to use and our administrators want to administer? Because if it's not, if it's something that's too difficult or onerous or complex, then I try to find ways to make it more user friendly and practical. And this is a challenge sometimes because we are, our products operate in highly regulated environments and sometimes they have to have certain rules and certain configurations that aren't the most user friendly or management friendly. So I, I put a lot of effort into thinking about how can we make this feature useful while still complying with all the regulations that we have to comply with. And by the way, we're very successful in a highly regulated space. We sell a lot of VxRail, for example, into the Department of Defense and banks and, and other highly regulated environments and we're very successful there. >>Excellent. Okay, Jerome, thanks. We're gonna leave it there for now. I'd love to have you back to talk about the progress that you're making down the road. Things always, you know, advance in the tech industry and so would appreciate that. >>I would look forward to it. Thank you very much, Dave. >>You're really welcome. In a moment I'll be back to summarize the program and offer some resources that can help you on your journey to secure your enterprise infrastructure. I wanna thank our guests for their contributions in helping us understand how investments by a company like Dell can both reduce the need for dev sec up teams to worry about some of the more fundamental security issues around infrastructure and have greater confidence in the quality providence and data protection designed in to core infrastructure like servers, storage, networking, and hyper-converged systems. You know, at the end of the day, whether your workloads are in the cloud, on prem or at the edge, you are responsible for your own security. But vendor r and d and vendor process must play an important role in easing the burden faced by security devs and operation teams. And on behalf of the cube production content and social teams as well as Dell Technologies, we want to thank you for watching a blueprint for trusted infrastructure. Remember part one of this series as well as all the videos associated with this program and of course today's program are available on demand@thecube.net with additional coverage@siliconangle.com. And you can go to dell.com/security solutions dell.com/security solutions to learn more about Dell's approach to securing infrastructure. And there's tons of additional resources that can help you on your journey. This is Dave Valante for the Cube, your leader in enterprise and emerging tech coverage. We'll see you next time.

>> From theCUBE studios in Palo Alto in Boston bringing you data driven insights from theCUBE and ETR. This is "Breaking Analysis" with Dave Vellante. >> In just over 10 years, CrowdStrike has become a leading independent security firm with more than 2 billion in annual recurring revenue, nearly 60% ARR growth, and approximate $40 billion market capitalization, very high retention rates, low churn, and a path to 5 billion in revenue by mid decade. The company has joined Palo Alto Networks as a gold standard pure play cyber security firm. It has achieved this lofty status with an architecture that goes beyond a point product. With outstanding go to market and financial execution, some sharp acquisitions and an ever increasing total available market. Hello, and welcome to this week's Wikibon Cube Insights powered by ETR. In this "Breaking Analysis" and ahead of Falcon, Fal.Con, CrowdStrike's user conference, we take a deeper look into CrowdStrike, its performance, its platform, and survey data from our partner ETR. Now, the general consensus is that spending on Cyber is non-discretionary and is held up better than other technology sectors. While this is generally true, as this data shows, it's nuanced. Let's explore this a bit. First, this is a year-to-date chart of the stock performance of CrowdStrike relative to Palo Alto, the BUG ETF, which is a Cyber index, the NASDAQ and SentinelOne, a relatively new entrant to the IPO public markets. Now, as you can see the security sector as evidenced by the orange line, that Cyber ETF, is holding up better than the overall NASDAQ which is off 28% year-to-date. Palo Alto has held up incredibly well, the best, being off only around 4% year-to-date. Whereas CrowdStrike is off in the double digits this year. But up as we talked about in one of our last "Breaking Analysis" on Cyber, up from its lows this past May. Now, CrowdStrike had a very nice beat and raise on August 30th. But the stop didn't respond well initially. We asked "Breaking Analysis" contributor, Chip Simonton for his technical take and he stated that CrowdStrike has bounced around for the last three months in its current range. He said that Cyber stocks have held up better than the rest of the market, as we're showing. And now might be a good time to take a shot but he is cautious. FedEx had a warning today of a global recession and that's obvious case for a concern. You know, maybe some of these quality Cyber stocks like Palo Alto and CrowdStrike and Zscaler will outperform in a recession, but that play is not for the faint of heart. In fact, it's feeling like a longer, more drawn out tech lash than many had hoped. Perhaps as much as 12 to 18 months of bouncing around with sellers still in control, is generally the sentiment from Simonton. So in terms of Cyber spending being non-discretionary, we'd say it's less discretionary than other it sectors but the CISO still does not have an open wallet, as we've reported before. We've seen that spending momentum has decelerated in all sectors throughout the year. This is an across the board trend. Now, independent of the stock price, George Kurtz, CEO of CrowdStrike, he's running a marathon, not a sprint. And this company is running at a nice pace despite tough macro headwinds. The company is free cash flow positive and is in the black, or a non-GAAP operating profit basis and yet it's growing ARR at nearly 60%. Frank Slootman uses the term inherent profitability, meaning that the company could drive more profits if it wanted to dial down expenses especially in go to market costs. But that would be a mistake for a company like CrowdStrike, in our opinion. While it has an impressive nearly 20,000 customers, there are hundreds of thousands of customers that CrowdStrike could penetrate. So like Snowflake and Slootman, Kurtz is not taking its foot off the gas. Now, the fundamental strength of CrowdStrike and its secret sauce is its architecture and platform, in our view, so let's take a deeper look. CrowdStrike believes that the unstoppable breach is a myth. Now, CISOs don't agree with that because they assume they're going to get breached, but that's CrowdStrike's point of view, so lofty vision. CrowdStrike's mission is to consolidate the patchwork of solutions by introducing modules that go beyond point products. CrowdStrike has more than 20 modules, I think 22, that span a range of capabilities as shown in this table. Now, there are a few critical aspects of the CrowdStrike architecture that bear mentioning. First is the lightweight agent, that is fundamental. You know, we're used to thinking that agentless is good and agent is bad, but in this case, a powerful but small, slim and easy to install but unobtrusive agent has its advantages because it supports multiple CrowdStrike modules. The second point is CrowdStrike from the beginning has been dogmatic about getting all the telemetry data into the cloud. It sort of shunned doing bespoke on prem so that all the data could be analyzed. So the more agents that CrowdStrike installs around the world, the more data it has access to and the better its intelligence. Few companies have access to more data, perhaps Microsoft given it scale and size is an exception in that endpoint space. CrowdStrike has developed a purpose-built threat graph and analytics platform that allows it to quickly ingest in near real time key telemetry data and detect not only known malware, that's pretty straightforward, pretty much anybody could do that. But using machine intelligence, it can also detect unknown malware and other potentially malicious behavior using indicators of attack, IOC, or IOAs. Humio is shown here as a company that CrowdStrike bought for around 400 million in early 2020, early 2021. It's the company's Splunk killer and will serve as an observability platform. It's really starting to take off, that's a great market for them to go after. CrowdStrike, to try to put it into sort of a summary, uses a three pronged approach. First is it's next generation anti-virus, meaning it's SaaS base. SAS based solution that can do fast lookups to telemetry data and that data lives in the cloud. And this leverages cloud strikes proprietary threat graph. Now, the second is endpoint detection and response. CrowdStrike sends all endpoint activity to the cloud and can process the data in real time. CrowdStrike EDR allows you to search data history and its partners with threat intelligent platforms who push the data into CrowdStrike, the CrowdStrike cloud. This increases CloudStrike's observation space. It also has containment capabilities in EDR to fence off compromised system. Now, the third leg of the stool is CrowdStrike's world class manage hunting approach. Like many firms, CrowdStrike has a crack team of experts that is looking at the data, but CrowdStrike's advantage is the amount of data, that observation space that we just talked about, and near real time capabilities of the architecture thanks to that proprietary database that they've developed. And all this is built in the cloud and so it enables global scale. And of course, agility. Now, let's dig into some of the survey data and take a look at what ETR respondents are saying about the spending momentum for CrowdStrike in context with its peers. Here's a very recent dataset, the October preliminary data from the October dataset in ETR's survey. Eric Bradley shared with us, ETR's head of strategy, and he runs the round tables, he's a frequent "Breaking Analysis" contributor. This is an XY graph with Netcore or spending momentum on the vertical axis and the overlap or pervasiveness in the survey on the horizontal axis. That dotted red line at 40% indicates an elevated level of spending velocity. Anything above that, we consider really impressive. Note the CrowdStrike progression since the pandemic started. The two notable points are one, that CrowdStrike has remained consistently above that 40% mark and two, it has made notable progress to the right. You can see that sort of squiggly line consistently increasing its share with one little anomaly there in the early days of over a two-year period. The other call out here is Microsoft in the upper-right. We circled Microsoft as usual. Microsoft messes up the data because it's such a dominant player and has referenced earlier as a massive scale and very quality telemetry from its endpoints. Unlike AWS, Microsoft is a direct competitor of CrowdStrike's. Nonetheless, the sector remains very strong with lots of players. Cyber is a large and expanding TAM with too many point tools that CrowdStrike is well positioned to consolidate, in our view. Now, here's a more narrow view of that same XY graph. What it does is it takes out Microsoft to kind of normalize the data a bit and it compares a number of firms that specialize in endpoint, along with CrowdStrike such as Tanium which also has a lightweight agent, by the way, and appears to be doing pretty well. SentinelOne did a relatively recent IPO, took off, stock hasn't done as well since, as you saw earlier. Carbon Black which VMware bought for around $2 billion and Cylance which is the Blackberry pivot. Now, we've also for context included Palo Alto and Cisco because they are major players with the big presence in security and they've got solutions that compete with CrowdStrike. But you can see how CrowdStrike looms large with a higher net score than these others. Although Palo Alto is very impressive, as is Cisco, steady. But Palo Alto also, sorry, CrowdStrike also has a very steady posture instead of just looming on that X axis. Let's now take a look at XDR, extended detection and response. XDR is kind of this bit of a buzzword but CrowdStrike seems to be taking the mantle and trying to sort of own the category and define it, in our view. It's a natural evolution of endpoint detection and response, EDR. In a recent ETR Roundtable hosted by our colleague, Eric Bradley, the sentiment among several CIOs is that existing SIEM, security information and event management platforms are inadequate and some see XDR as a replacement for, or at least a strong compliment to SIEM. CISOs want a single view of their data. Hmm, you haven't heard that before. They want help prioritizing potentially high impact breaches and they want to automate the low level stuff because the problem is sometimes too much information becomes information overload and you can't prioritize. So they want to consolidate platforms. They want better co consistency. They have too many dashboards, too many stove pipes. They have difficulty scaling and they have inconsistent telemetry data. As one CISO said, it's a call out here. "If the regulatory requirement isn't there, I absolutely would get rid of my SIEM." So CrowdStrike, we feel, is in a good position to continue to gain, share and disrupt this space. And that's what Dave Nicholson and I will be looking for next week when theCUBE is at Fal.Con, CrowdStrike's user conference. We'll be there for two days at the area in Vegas. In addition to CrowdStrike CEO, we'll hear from government cyber experts. We always hear that at security conferences and the CEO of Mandiant. Google just the other day closed its $5 billion plus acquisition of Mandiant, which is a threat intelligence expert and MSSP. I'm going to hear a lot about MSSPs by the way. CrowdStrike is a growing MSSP base. We think that's a really interesting sector because many companies don't have a SOC. As many as 50% of companies in the United States don't have a security operations center. So they need help, that's where MSPs come in. At the conference, there'll be a real focus on the Falcon platform. And we expect CrowdStrike to educate the audience on its multiple modules and how to take advantage of the capabilities beyond endpoint. And we'll also be watching for the ecosystem conversations. We saw this at reinforced, for example, where CrowdStrike and Okta were presenting together to show how these companies products compliment each other in the marketplace. Sometimes it gets confusing when you hear that CrowdStrike has an identity product. Okta, of course, is the identity specialist. So we'll be helping extract that signal from the noise. Because a generational company must have a strong ecosystem. CrowdStrike is evolving and our belief is that it has some work to do to create a stronger partner flywheel, and we're eager to dig into that next week. So if you're at the event, please do stop by theCUBE, say hello to Dave Nicholson and myself. Okay, we're going to leave it there today. Many thanks to Chip Simonton and Eric Bradley for their input and contributions to today's episode. Thanks to Alex Myerson, who does production, he also manages our podcast, Ken Schiffman as well, in our Boston studios, Kristen Martin and Cheryl Knight help get the word out on social media and our newsletters, and Rob Hof is our editor in chief over at siliconangle.com. He does some wonderful editing and I really appreciate that. Remember, all these episodes are available as podcasts wherever you listen, just search "Breaking Analysis" Podcast. I publish each week on wikibon.com and siliconangle.com and you can email me at david.vellante@siliconangle.com or DM me @DVellante or comment on our LinkedIn post. And please do check out etr.ai for the best survey data in the enterprise tech business. This is Dave Vellante for theCUBE Insights powered by ETR. Thanks for watching, and we'll see you next time on "Breaking Analysis". (upbeat music)

(upbeat music) >> We're back with Jerome West, the Product Management Security Lead for HCI at Dell Technologies Hyper-Converged Infrastructure. Jerome, welcome. >> Thank you, Dave. >> Hey, Jerome, in this series "A Blueprint for Trusted Infrastructure," we've been digging into the different parts of the infrastructure stack, including storage servers and networking, and now we want to cover hyper-converged infrastructure. So my first question is what's unique about HCI that presents specific security challenges? What do we need to know? >> So what's unique about hyper-converged infrastructure is the breadth of the security challenge. We can't simply focus on a single type of IT system, so like a server or a storage system or a virtualization piece of software. I mean, HCI is all of those things. So luckily we have excellent partners like VMware, Microsoft and internal partners, like the Dell Power Edge Team, the Dell Storage Team, the Dell Networking Team, and on and on. These partnerships and these collaborations are what make us successful from a security standpoint. So let me give you an example to illustrate. In the recent past, we're seeing growing scope and sophistication in supply chain attacks. This means an attacker is going to attack your software supply chain upstream, so that hopefully a piece of code, malicious code that wasn't identified early in the software supply chain is distributed like a large player, like a VMware or a Microsoft or a Dell. So to confront this kind of sophisticated hard to defeat problem, we need short-term solutions and we need long-term solutions as well. So for the short-term solution, the obvious thing to do is to patch the vulnerability. The complexity is for our HCI portfolio, we build our software on VMware. So we would have to consume a patch that VMware would produce and provide it to our customers in a timely manner. Luckily, VxRail's engineering team has co engineered a release process with VMware that significantly shortens our development life cycle, so that VMware will produce a patch, and within 14 days we will integrate our own code with the VMware release. We will have tested and validated the update, and we will give an update to our customers within 14 days of that VMware release. That as a result of this kind of rapid development process, VxRail had over 40 releases of software updates last year. For a longer term solution, we're partnering with VMware and others to develop a software bill of materials. We work with VMware to consume their software manifest including their upstream vendors and their open source providers to have a comprehensive list of software components. Then we aren't caught off guard by an unforeseen vulnerability, and we're more able to easily detect where the software problem lies so that we can quickly address it. So these are the kind of relationships and solutions that we can co-engineer with effective collaborations with our partners. >> Great, thank you for that description. So if I had to define what cybersecurity resilience means to HCI or converged infrastructure, to me, my takeaway was you got to have a short-term instant patch solution and then you got to do an integration in a very short time, you know, two weeks to then have that integration done. And then longer-term, you have to have a software bill of materials so that you can ensure the provenance of all the components. Help us, is that a right way to think about cybersecurity resilience? Do you have, you know, additives to that definition? >> I do. I really think that cybersecurity and resilience for HCI, because like I said it has sort of unprecedented breadth across our portfolio. It's not a single thing. It's a bit of everything. So really the strength or the secret sauce is to combine all the solutions that our partner develops while integrating them with our own layer. So let me give you an example. So HCI, it's a basically taking a software abstraction of hardware functionality and implementing it into something called the virtualized layer. It's basically the virtualizing hardware functionality, like say a storage controller. You could implement it in the hardware, but for HCI, for example, in our VxRail portfolio, our VxRail product, we integrated it into a product called vSan which is provided by our partner VMware. So that portfolio strength is still, you know, through our partnerships. So what we do, we integrate these security functionality and features into our product. So our partnership grows through our ecosystem through products like VMware products, like NSX, Horizon, Carbon Black and vSphere. All of them integrate seamlessly with VMware. And we also leverage VMware's software partnerships on top of that. So for example, VxRail supports multifactor authentication through vSphere's integration with something called Active Directory Federation Services or ADFS. So there is a lot of providers that support ADFS, including Microsoft Azure. So now we can support a wide array of identity providers such as Auth0, or I mentioned Azure or Active Directory through that partnership. So we can leverage all of our partners' partnerships as well. So there's sort of a second layer. So being able to secure all of that, that provides a lot of options and flexibility for our customers. So basically to summarize my answer, we consume all of the security advantages of our partners, but we also expand on them to make a product that is comprehensively secured at multiple layers from the hardware layer that's provided by Dell through Power Edge to the hyper-converged software that we build ourselves to the virtualization layer that we get through our partnerships with Microsoft and VMware. >> Great, I mean, that's super helpful. You've mentioned NSX, Horizon, Carbon Black, all the you know, the VMware component, Auth0, which the developers are going to love. You got Azure Identity. So it's really an ecosystem. So you may have actually answered my next question, but I'm going to ask it anyway cause you've got this software-defined environment, and you're managing servers and networking and storage with this software-led approach. How do you ensure that the entire system is secure end to end? >> That's a really great question. So the answer is we do testing and validation as part of the engineering process. It's not just bolted on at the end. So when we do, for example VxRail is the market's only co-engineered solution with VMware. Other vendors sell VMware as a hyper-converged solution, but we actually include security as part of the co-engineering process with VMware. So it's considered when VMware builds their code, and their process dovetails with ours because we have a secure development lifecycle which other products might talk about in their discussions with you, that we integrate into our engineering lifecycle. So because we follow the same framework, all of the code should inter-operate from a security standpoint. And so when we do our final validation testing, when we do a software release, we're already halfway there in ensuring that all these features will give the customers what we promised. >> That's great. All right, let's close. Pitch me. What would you say is the strong suit, summarize the the strengths of the Dell hyper-converged infrastructure and converged infrastructure portfolio, specifically from a security perspective, Jerome? >> So I talked about how hyper-converged infrastructure simplifies security management because basically you're going to take all of these features that are abstracted in hardware. They're not abstracted in the virtualization layer. Now you can manage them from a single point of view, whether it would be say, you know, for VxRail it would be vCenter, for example. So by abstracting all this, you make it very easy to manage security and highly flexible because now you don't have limitations around a single vendor. You have a multiple array of choices and partnerships to select. So I would say that is the key to making, to HCI. Now what makes Dell the market leader in HCI is not only do we have that functionality, but we also make it exceptionally useful to you because it's co-engineered. It's not bolted on. So I gave the example of SBOM. I gave the example of how we modify our software release process with VMware to make it very responsive. A couple of other features that we have specific just to HCI are digitally signed LCM updates. This is an example of a feature that we have that's only exclusive to Dell. It's not done through a partnership. So we digitally sign our software updates. So the user can be sure that the update that they're installing into their system is an authentic and unmodified product. So we give it a Dell signature that's invalidated prior to installation. So not only do we consume the features that others develop in a seamless and fully validated way, but we also bolt on our own specific HCI security features that work with all the other partnerships and give the user an exceptional security experience. So for example, the benefit to the customer is you don't have to create a complicated security framework. That's hard for your users to use, and it's hard for your system administrators to manage. It all comes in a package, so it can be all managed through vCenter, for example. And then the specific hyper-converged functions can be managed through VxRail manager or through STDC manager. So there's very few panes of glass that the administrator or user ever has to worry about. It's all self-contained and manageable. >> That makes a lot of sense. So you've got your own infrastructure. You're applying your best practices to that like the digital signatures. You've got your ecosystem. You're doing co-engineering with the ecosystems, delivering security in a package, minimizing the complexity at the infrastructure level. The reason, Jerome, this is so important is because SecOps teams, you know, they got to deal with Cloud security. They got to deal with multiple Clouds. Now they have their shared responsibility model going across multiple. They got all this other stuff that they have to worry. They got to secure the containers and the run time and the platform and so forth. So they're being asked to do other things. If they have to worry about all the things that you just mentioned, they'll never get, you know, the security is just going to get worse. So my takeaway is you're removing that infrastructure piece and saying, okay, guys, you now can focus on those other things that is not necessarily Dell's, you know, domain, but you, you know, you can work with other partners and your own teams to really nail that. Is that a fair summary? >> I think that is a fair summary because absolutely the worst thing you can do from a security perspective is provide a feature that's so unusable that the administrator disables it or other key security features. So when I work with my partners to define and develop a new security feature, the thing I keep foremost in mind is will this be something our users want to use and our administrators want to administer? Because if it's not, if it's something that's too difficult or onerous or complex, then I try to find ways to make it more user-friendly and practical. And this is a challenge sometimes because our products operate in highly regulated environments, and sometimes they have to have certain rules and certain configurations that aren't the most user friendly or management friendly. So I put a lot of effort into thinking about how can we make this feature useful while still complying with all the regulations that we have to comply with. And by the way, we're very successful in a highly regulated space. We sell a lot of VxRail, for example, into the Department of Defense and banks and other highly regulated environments. And we're very successful there. >> Excellent, okay, Jerome, thanks. We're going to leave it there for now. I'd love to have you back to talk about the progress that you're making down the road. Things always, you know, advance in the tech industry, and so would appreciate that >> I would look forward to it. Thank you very much, Dave. >> You're really welcome. In a moment, I'll be back to summarize the program and offer some resources that can help you on your journey to secure your enterprise infrastructure. (upbeat music)

(soft music) >> Welcome back, everyone. theCube's live coverage. Day two here at VMware Explore. Our 12th year covering VMware's annual conference formally called Vmworld, now it's VMware Explore. Exploring new frontiers multi-cloud and also bearing some of the fruit from all the investments in cloud native Tanzu and others. I'm John Furrier with Dave Vellante. We have the man who's in charge of a lot of that business and a lot of stuff coming out of the oven and hitting the market. Ajay Patel, senior vice president and general manager of the modern applications and management group at VMware, basically the modern apps. >> Absolutely. >> That's Tanzu. All the good stuff. >> And Aria now. >> And Aria, the management platform, which got social graph and all kinds of graph databases. Welcome back. >> Oh, thank you so much. Thanks for having me. >> Great to see you in person, been since 2019 when you were on. So, a lot's happened since 2019 in your area. Again, things get, the way VMware does it as we all know, they announce something and then you build it and then you ship it and then you announce it. >> I don't think that's true, but okay. (laughs) >> You guys had announced a lot of cool stuff. You bought Heptio, we saw that Kubernetes investment and all the cloud native goodness around it. Bearing fruit now, what's the status? Give us the update on the modern applications of the management, obviously the areas, the big announcement here on the management side, but in general holistically, what's the update? >> I think the first update is just the speed and momentum that containers and Kubernetes are getting in the marketplace. So if you take the market context, over 70% of organizations now have Kubernetes in production, not one or two clusters, but hundreds of clusters, sometimes tens of clusters. So, to me, that is a market opportunity that's coming to fruition. Sometimes people will come and say, Ajay, aren't you late to the market? I say, no, I'm just perfectly timing it. 'Cause where does our value come in? It's enterprise readiness. We're the company that people look to when you have complexity, you have scale, you need performance, you need security, you need the robustness. And so, Tanzu is really about making modern applications real, helping you design, develop, build and run these applications. And with Aria, we're fundamentally changing the game around multicloud management. So the one-two punch of Tanzu and Aria is I'm most excited about. >> Isn't it true that most of the Kubernetes, you know, today is people pulling down open source and banging away. And now, they're looking for, you know, like you say, more of a robust management capability. >> You know, last two years when I would go to many of the largest customers, like, you know, we're doing good. We've got a DIY platform, we're building this. And then you go to the customer a year later, he's got knocked 30, 40 teams and he has Log4j happen. And all of a sudden he is like, oh, I don't want to be in the business of patching this thing or updating it. And, you know, when's the next shoe going to fall? So, that maturity curve is what I was talking about. >> Yeah. Free like a puppy. >> Ajay, you know, mentioned readiness, enterprise readiness and the timing's perfect. You kind of included, not your exact words, but I'm paraphrasing. That's a lot to do with what's going on. I mean, I'll say Cloud Native, IWS, think of the hyper scale partner, big partner and Google and even Google said it today. You know, the market world's spinning in their direction. Especially with respect to VMware. You get the relationship with the hyperscalers. Cloud's been on everyone's agenda for a long time. So, it's always been ready. But enterprise, you are customer base at VMware, very cloud savvy in the sense they know it's there, there's some dabbling, there's some endeavors in the cloud, no problem. But from a business perspective and truly transforming the VMware value proposition, is already, they're ready and it's already time now for them, like, you can see the movement. And so, can you explain the timing of that? I mean, I get enterprise readiness, so we're ready to scale all that good stuff. But the timing of product market fit is important here. >> I think when Raghu talks about that cloud first to cloud chaos, to cloud smart, that's the transition we're seeing. And what I mean by that is, they're hitting that inflection point where it's not just about a single team. One of the guys, basically I talked to the CIO, he was like, look, let's assume hypothetically I have thousand developers. Hundred can talk about microservices, maybe 50 has built a microservice and three are really good at it. So how do I get my thousand developers productive? Right? And the other CIO says, this team comes to me and says, I should be able develop directly to the public cloud. And he goes, absolutely you can do that. You don't have to come through IT. But here's the book of security and compliance that you need to enforce to get that thing in production. >> Go for it. >> Go for it. >> Good luck with that. >> So that reality of how do I scale my dev developers is turning into a developer experience problem. We now have titles which says, head of developer experience. Imagine that two years ago. We didn't talk about it. People start, hey, containers Kubernetes. I'm good to go. I can go get all the open source technology you talked about. And now they're saying no. >> And also software supply chains, another board that you're think. This is a symptom of the growth. I mean, open source is the software industry. That is, I don't think debatable. >> Right. >> Okay. That's cool. But now integration becomes vetting, trust, trusting codes. It's very interesting software time right now. >> That's right. >> And how is that impacting the cloud native momentum in your mind? Accelerating it? What inning are we in? How would you peg the progress? >> You know, on that scale of 1 to 10, I think we're halfway marked now. And that moved pretty quickly. >> It really did. >> And if you sit back today, the kinds of applications we're involved in, I have a Chicago wealth management company. We're building the next generation wealth management application. It's a fundamental refactoring of the legacy application. If you go to a prescription company, they're building a brand new prescription platform. These are not just trivial. What they're learning is the lift and shift. Doesn't work for these major applications. They're having to refactor them which is the modernization. >> So how specifically, are they putting some kind of abstraction layer on that? Are they actually gutting it and rewriting it? >> There's always going to be brownfield. Remember the old days of SOA? >> Yeah, yeah. >> They are putting APIs in front of their main systems. They're not rewriting the core banking or the core platform, but the user experience, the business logic, the AIML capability to bring intelligence in the platform. It's surrounding the capability to make it much more intuitive, much more usable, much more declarative. That's where things are going. And so I'm seeing this mix of integration all over again. Showing my age now. But, you know, the new EAI so is now microservices and messaging and events with the same patterns. But again, being much more accelerated with cloud native services. >> And it is to the point, it's accelerated today. They're not having to freeze the code for six months or nine months and that which would kill the whole recipe for failure. So they're able to now to fast track their modernization. They have to prioritize 'cause they got limited resources. But how are you guys coming up to that? >> But the practice is changing as well, right? Well, the old days, it was 12, 18 months cycle or anything software. If you heard the CVS CIO, Rohan. >> Yeah. >> Three months where they started to engage with us in getting an app in production, right? If you look at the COVID, 10 days to get kind of a new application for getting small loans going with Pfizer, right? These are dramatically short term, but it's not rewriting the entire app. It's just putting these newer experiences, newer capability in front with newer modern developer practices. And they're saying, I need to do it not just once, but for 100, 200, 5,000 members. JPMC has 50,000 developers. Fifty thousand. They're not a bank anymore. >> We just have thousands of apps. >> Exactly. >> Ajay, I want to get your thoughts on something that we've been talking about on our super cloud event. I know we had an event a couple weeks ago, you guys were one of our sponsors, VMware was. It was called super cloud where we're defining that this next gen environment's a super cloud and every company will have a super cloud capability. And underneath that is cross cloud capabilities. So, super cloud is like a super set on top of a multi-cloud. And little word play or play on words is, ecosystem partners versus partners in the ecosystem. Because if you're coming down to the integration side of things, it's about knowing what goes what, it's almost like building an OS if you're a coder or an operating systems person. You got to put the pieces together right, not just go to the directory and say, okay, who's got the cheapest price in DR or air gaping or something or some solution. So ecosystem partners are truly partners. Partners in the ecosystem are a bunch of people out on a list. How do you see that? Because the trend we're seeing is, the development process includes partners at day one. >> That's right. Not bolt-on. >> Completely agree. >> Share your thoughts on that. >> So let's look at that. The first thing I'm hearing from my customers is, they're trying to use all the public clouds as a new IS. That's the first API or contract infrastructures code IS. From then on they're saying, I want more and more portable services. And if you see the success of some of the data vendors and the messaging vendors, you're starting to see best of breed becoming part of the platform. So you are to identify which of these are truly, you know, getting market momentum and are becoming kind of defacto leaders. So, Kafka goes hand in hand with streaming. RabbitMQ from my portfolio goes with messaging. Postgres for database. So these are the, in your definition, ecosystem partners, they're foundational. In the security space, you know, Snyk is a common player in terms of scanning or Aqua and Prisma even though we have Carbon Black. Those become partners from a container security perspective. So, what's happening is the industry stabilizing a handful of critical players that are becoming multi-cloud preference of choice in this. And our job is to bring it all together in a all coordinated, orchestrated manner to give them a platform. >> I mean, you guys always had ecosystem, but I think that priority more than ever. It wasn't really your job at VMware, even, Dave, 10 years ago to say, hey, this is the strategic role that you might play one partner. It was pretty much the partners all kind of fed off the momentum of VMware. Virtualization. And there's not a lot of nuance there. There's pretty much they plug in and you got. >> So what we're doing here is, since we're not the center of the universe, unfortunately, for the application world, things like Backstage is a developer portal from Spotify that became open source. That's becoming the place where everyone wants to provide a plugin. And so we took Backstage, we said, let's provide enterprise support for Backstage. If you take a technology like, you know, what we have with Spring. Every job where developer uses Spring, how do we make it modern with Spring cloud. We work with Microsoft to launch a service with Azure Spring Enterprise for Spring. So you're starting to see us taking communities where they have momentum and bringing the ecosystem around those technologies. Cluster API for Kubernetes, for have you managed stuff. >> Yeah. >> So it's about standard. >> Because the developers are voting with their clicks and their code repos. And so you're identifying the patterns that they like. >> That's right. >> And aligning with them and connecting with them rather than trying to sell against it. >> Exactly. It's the end story with everyone. I say stop competing. So people used to think Tanzu is Kubernetes. It's really Tanzu is the modern application platform that runs on any Kubernetes. So I've changed the narrative. When Heptio was here, we were trying to be a Kubernetes player. I'm like, Kubernetes is just another dial tone. You can use mine, you can use OpenShift. So this week we announced support for OpenShift by Tanzu application platform. The values moving up, it's around outcomes. So industry standards, taking lead and solving the problem. >> You know, we had a panel at super cloud. Dave, I know you got a question. I'll get to you in a second. But the panel was the innovator's dilemma. And then during the event, one of the panelists, Chris Hoff knows VMware very well, Beaker on Twitter, said it should be called the integrators dilemma. Because the innovations here, >> How do you put it all together? >> But the integration of the, putting the piece parts together, building the thing is the innovation. >> And we come back and say, it's a secure software supply chain. It starts with great content. Did you know, I published most of the open source content on every hyperscaler through my Bitnami acquisition. So I start with great content that's curated. Then I allow you to create your own golden images. Then I have a build service that secures and so on and so forth and we bring the part. So, that opinionated solution, but batteries included but you can change it is been one of our key differentiator. We recognize the roles is going to be modular, come back and solve for it. >> So I want to understand sort of relationship Tanzu and Aria, John was talking about, you know, super cloud before we had our event. We had an earlier session where we help people understand that Aria was not, you know, vRealize renamed. >> It's rebranded. >> And reason I bring that up is because we had said it around super cloud, that one of the defining characteristics was, sorry, super PaaS, which is a specific purpose built PaaS layer designed to support your objective for multi-cloud. And speaking to a lot of people this week, there's a federated architecture, there's graph relationships, there's real time ability to ingest and analyze. That's unique. And that's IP that is purpose built for what you're doing. >> Absolutely. When I think what came out of all that learning is after 20 years of Pivotal and BA and what we learned that you still need some abstraction layer. Kubernetes is too low level. So what are the developer problems? What are the delivery problems? What are the operations and management problems? Aria solves all the operations and management problem. Tanzu solves a super PaaS problems. >> Yes. Right. >> Of providing a consistent way to build great software and the secure software supply chain to run on any infrastructure. So the combination of Tanzu and Aria complete the value chain. >> And it's different. Again, we get a lot of heat for this, but we're saying, look, we're trying to describe, it's not just IAS, PaaS, and SaaS of last decade. There's something new that's happening. And we chose the name super cloud. >> And what's the difference? It's modular. It's pluggable. It fits into the way you operate. >> Whereas PaaS was very prescriptive. If you couldn't fit, you couldn't jump down to the next level. This is very much, you can stay at the abstraction level or go lower level. >> Oh, we got to add that to the attribute. >> We're recruiting him right now. (laughs) >> We'll give you credit. >> I mean, funny all the web service's background. Look at an app server. You well knew all about app servers. Basically the company is an app. So, if you believe that, say, Capital One is an application as a company and Amazon's providing all the CapEx, >> That's it. >> Okay. And they run all their quote, old IT spend millions, billions of dollars on operating expenses that's going to translate to the top line called the income statement. So, Dave always says, oh, it's on the balance sheet, but now they're going to go to the top line. So we're seeing dynamic. Ajay, I want to get your reaction to this where the business model shift if everything's tech enabled, the company is like an app server. >> Correct. >> So therefore, the revenue that's generated from the technology, making the app work has to get recognized in the income. Okay. But Amazon's doing all, or the cloud hyperscale is doing all the heavy lifting on the CapEx. So technically it's the cloud on top of a cloud. >> Yes and no. The way I look at it, >> I call that a super cloud. >> So I like the idea of super cloud, but I think we're mixing two different constructs. One is, the cloud is a new hardware, right? In terms of dynamic, elastic, always available, et cetera. And I believe when more and more customer I talk about, there's a service catalog of infrastructure services. That's emerging. This super cloud is the next set of PaaS super PaaS services. And the management service is to use the cloud. We spend so much time as VMware building clouds, the problem seems, how do you effectively use the cloud? What problems do we solve around digital where every company is a digital company and the product is this application, as you said. So everything starts with an application. And you look at from the lens of how you run the application, what it costs the application, what impact it's driving. And I think that's the change. So I agree with you in some way. That is a digital strategy. >> And that's the company. >> That's the company. The application is the company. >> That's the t-shirt. >> And API is the currency. >> So, Ajay, first of all, we love having you in theCube 'cause you're like a masterclass in multiple dimensions. So, I want to get your thoughts on the abstraction layer. 'Cause we were also talking earlier in theCube here as well as before. But abstraction layers happen when you have major movements in markets that are game changing or major inflection points because you've reached a complexity point where it's working so great, this new thing, that's too complex to reign it in. And we were quoting Andy Grove by saying, "let chaos reign then reign in the chaos". So, all major industry moments go back 30, 40 years happen with abstractions. So the question is is that, you can't be a vendor, we've observed you can't be a vendor and be the abstraction. Like, if Cisco's running routers, they can't be the abstraction layer. They have to be the benefit of the abstraction layer. And if you're on the other side of the abstraction layer, you can't be running that either. >> I like the way you're thinking about it. Yeah. Do you agree? >> I completely agree. And, you know, I'm an old middleware guy. And when I used to say this to my CEO, he's like, no, it's not middleware, it's just a new middleware. And what's middleware, right? It's a thing between app and infrastructure. You could define it whatever we want, right? And so this is the new distributed middleware. >> It's a metaphor and it's a good one because it does a purpose. >> It's a purpose. >> It creates a separation but then you have, it's like a DMZ zone or whatever you want to call it. It's an area that things happen. >> But the difference before last time was, you could always deploy it to a thing. The thing is now the cloud. The thing is a set of services. So now it's as much of a networking problem at the application layer is as much as security problem. It's how you build software, how we design. So APIs, become part of your development. You can't think of APIs after the fact, right? When you build an API, you got to publish API because the minute you publish it and if you change it, the API's out of. So you can't have it as a documentation process. So, the way you build software, you use software consume is all about it. So to me, digital product with an API as a currency is where we're headed towards. >> Yeah, that's a great observation. Want to make a mental note of that and make that a clip. I want to get your thoughts on software development. You mentioned that, obviously software development life cycles are changing. I'll say open sources now. I mean, it's unlimited codes, supply chain issue. What's in the code, I get that verified codes going to happen. Is software development coding as much or is coding changing the notion of writing code? Or is it more glue layer you're writing. >> I think you're onto something. I call software developments composition now. My son's at Facebook or Google. They have so many libraries. So you don't no longer start with the very similar primitive, you start with building blocks, components, services, libraries, open source technology. What are you really doing? You're composing these things from multiple artifacts. And how do you make sure those artifacts are good artifacts? So someone's not sticking in security in a vulnerability into it. So, the world is moving towards composition and there are few experts who build the core components. Most of the time we're just using those to build solutions. And so, the art here is, how do you provide that set of best practices? We call them patterns or building blocks or services that you can compose to build these next generation (indistinct) >> It's interesting. >> Cooking meals. >> I agree with you a hundred percent what you're thinking. I agree about that worldview. Here's a dilemma that I'm seeing. In the security world, you've got zero trust. You know, Which is, I don't know you, I don't trust you at all. And if you're going to go down this composed, we're going to have an orchestra of players with instruments, say to speak, Dave, metaphor. That's trust involved. >> Yes. >> So you have two spectrums of issues. >> Yes. >> If software's going trust and you're seeing Docker containers getting more verifications, software supply chain, and then you got hardware I call network guys, love zero trust. Where's the balance? How do you reconcile that? Is it just decoupled? Nuance? I mean, what's the point? >> No, no. I think it all comes together. And what I mean by that is, it starts with left shifting it all the way to hands of the developers, right? So, are you starting with good content? You have providence of the stuff you're using. Are you building it correctly? So you're not introducing bad things like solar winds along the process. Are you testing it along the way of the development process? And then once in production, do you know, half the time it's configurations of where you're running the stuff versus the software itself. So you can think of the two coming together. And the network security is protecting people from going laterally once they've got in there. So, a whole security solution requires all of the above, a secure software supply chain, the way to kind of monitor and look at configuration, we call posture management or workload management and the network security of SaaS-e for zero trust. That's a hard thing. And the boundary is the application. >> All right. >> So is it earned trust model sort of over time? >> No, it's designed in, it's been a thing. >> Okay. So it's not a, >> Because it developed. >> You can bolt in afterwards. >> Because the developers are driving it. They got to know what they're doing. >> And it's changing every week. If I'm putting a new code out every week. You can't, it can be changed to something else. >> Well, you guys got guardrails. The guardrails constant is a good example. >> It stops on the configuration side, but I also need the software. So, Tanzu is all about, the secure chain is about the development side of the house. Guardrails are on the operational side of the house. >> To make sure the developers don't stop. >> That's right. >> Things will always get out there. And I find out there's a CV that I use a library, I found after the fact. >> Okay. So again, while I got here again, this is great. I want to get test this thesis. So, we've been saying on theCube, talking about the new ops, the new kind of ops that emerging. DevOps, which we believe is cloud native. So DevOps moving infrastructure's code, that's happened, it's all good. Open source is growing. DevOps is done deal. It's done deal. Developers are doing that. That ops was IT. Then don't need the server, clouds my hardware. Check. That balances. The new ops is data and security which has to match up to the velocity of the developers. Do you believe that? >> Completely. That's why we call it DevSecOps. And the Sec is where all the action is. >> And data. And data too. >> And data is about making the data available where the app meets. So the problem was, you know, we had to move the logic to where the data is or you're going to move the data where the logic is. So data fabrics are going to become more and more interesting. I'll give you a simple example. I publish content today in a service catalog. My customer's saying, but my content catalog needs to be in 300 locations. How do I get the content to each of the repos that are running in 300 location? So I have a content distribution problem. So you call it a data problem. Yes, it's about getting the right data. Whether it's simple as even content, images available for use for deployment. >> So you think when I think about the application development stack and the analytics stack, the data stack, if I can call it that, they're separate, right? Are those worlds, I mean, people say, I want to inject data and AI intelligence into apps. Those worlds have deployment? I think about the insight from the historical being projected in the operational versus they all coming together. I have a Greenplum platform, it's a great analytics platform. I have a transactional platform. Do my customers buy the same? No, they're different buyers, they're different users. But the insight from that is being now plugged in so that at real time I can ask the question. So even this information is being made available on demand. So that's where I see it. And that's most coming together, but the insight is being incorporated in the operational use. So I can say, do I give the risk score? Do I give you credit? It's based on a whole bunch of historical analytics done. And at the real time, processing is happening, but the intelligence is behind it. >> It's a mind shift for sure because the old model was, I have a database, we're good. Now you have time series database, you got graphs. Each one has a role in the overall construct of the new thing. >> But it's about at the end. How do I make use of it? Someone built a smart AI model. I don't know how it was built, but I want to apply it for that particular purpose. >> Okay. So the final question for you, at least from my standpoint is, here at VMware Explore, you have a lot of the customers and so new people coming in that we've heard about, what's their core order of operations right now? Get on the bandwagon for modern apps. How do you see their world unfolding as they go back to the ranch, their places, and go back to their boss? Okay. We got the modern application. We're on the right track boss, full steam ahead. Or what change do they make? >> I think the biggest thing I saw was with some of the branding changes well and some of the new offerings. The same leader had two teams, the VMware team and the public cloud team. And they're saying, hey, maybe VMware's going to be the answer for both. And that's the world model. That's the biggest change I'm seeing. They were only thinking of us on the left column. Now they see us as a unifying player to play across cloud native and VMware, the uniquely set up to bring it all together. That's been really exciting this week. >> All right, Ajay, great to have you on. Great perspective. Worthy of great stuff. Congratulations on the success of all that investment coming to bear. >> Thank you. >> And on the new management platform. >> Yeah. Thank you. And thanks always for giving us all the support we need. It's always great. >> All right Cube coverage here. Getting all the data, getting inside the heads, getting all the specifics and all the new trends and actually connecting the dots here on theCube. I'm John Furrier with Dave Vellante. Stay tuned for more coverage from day two. Two sets, three days, Cube at VMware Explore. We'll be right back. (gentle music)

(upbeat music) >> We're here on theCube covering AWS Storage Day 2022. Kevin Miller joins us. He's the vice president and general manager of Amazon S3. Hello, Kevin, good to see you again. >> Hey Dave, it's great to see you as always. >> It seems like just yesterday we were celebrating the 15th anniversary of S3, and of course the launch of the modern public cloud, which started there. You know, when you think back Kevin, over the past year, what are some of the trends that you're seeing and hearing from customers? What do they want to see AWS focus more on? What's the direction that you're setting? >> Yeah, well Dave, really I think there's probably three trends that we're seeing really pop this year. I think one just given the kind of macroeconomic situation right now is cost optimization. That's not a surprise. Everyone's just taking a closer look at what they're using, and where they might be able to pair back. And you know, I think that's a place that obviously S3 has a long history of helping customers save money. Whether it's through our new storage classes, things like our Glacier Instant Retrieval, storage class that we launched to reinvent last year. Or things like our S3 storage lens capability to really dig in and help customers identify where their costs are are being spent. But so certainly every, you know, a lot of customers are focused on that right now, and for obvious reasons. I think the second thing that we're seeing is, just a real focus on simplicity. And it kind of goes hand in hand with cost optimization, because what a lot of customers are looking for is, how do I take the staff that I have, and do more this year. Right, continue to innovate, continue to bring new applications or top line generating revenue applications to the market, but not have to add a lot of extra headcount to do that. And so, what they're looking for is management and simplicity. How do I have all of this IT infrastructure, and not have to have people spending a lot of their time going into kind of routine maintenance and operations. And so that's an area that we're spending a lot of time. We think we have a lot of capability today, but looking at ways that we can continue to simplify, make it easier for customers to manage their infrastructure. Things like our S3 intelligent tiering storage class, which just automatically gives cost savings for data that's not routinely accessed. And so that's a big focus for us this year as well. And then I think the last and probably third thing I would highlight is an emerging theme or it's been a theme, but really continuing to increase in volume, is all around sustainability. And you know, our customers are looking for us to give them the data and the assurances for them, for their own reports and their own understanding of how sustainable is my infrastructure. And so within AWS, of course, you know we're on a path towards operating with 100% renewable energy by 2025. As well as helping the overall Amazon goal of achieving net zero carbon by 2040. So those are some big lofty goals. We've been giving customers greater insights with our carbon footprint tool. And we think that, you know the cloud continues to be just a great place to run and reduce customer's carbon footprint for the similar you know, storage capacity or similar compute capacity. But that's just going to continue to be a trend and a theme that we're looking at ways that we can continue to help customers do more to aggressively drive down their carbon footprint. >> I mean, it makes sense. It's like you're partnering up with the cloud, you know, you did same thing on security, you know, there's that shared responsibility model, same thing now with ESG. And on the macro it's interesting Kevin, this is the first time I can remember where, you know it used to be, if there's a downturn it's cost optimization, you go to simplicity. But at the same time with digital, you know, the rush to digital, people still are thinking about, okay how do I invest in the future? So but let's focus on cost for a moment then we'll come back to sort of the data value. Can you tell us how AWS helps customers save on storage, you know, beyond just the price per terabyte actions that you could take. I mean I love that, you guys should keep doing that. >> Absolutely. >> But what other knobs are you turning? >> Yeah, right and we've had obviously something like 15 cost reductions or price reductions over the years, and we're just going to continue to use that lever where we can, but it's things like the launch of our Glacier Instant Retrieval storage class that we did last year at Reinvent, where that's now you know, 4/10ths of a cent per gigabyte month. For data that customers access pretty infrequently maybe a few times a year, but they can now access that data immediately and just pay a small retrieval fee when they access that data. And so that's an example of a new capability that reduces customer's total cost of ownership, but is not just a straight up price reduction. I mentioned S3 Intelligent-Tiering, that's another case where, you know, when we launch Glacier Instant Retrieval, we integrated that with Intelligent-Tiering as well. So we have the archive instant access tier within Intelligent-Tiering. And so now data that's not accessed for 90 days is just automatically put into AIA and and then results in a reduced storage cost to customers. So again, leaning into this idea that customers are telling us, "Just do, you know what should be done "for my data to help me reduce cost, can you just do it, "and sort of give me the right defaults." And that's what we're trying to do with things like Intelligent-Tiering. We've also, you know, outside of the S3 part of our portfolio, we've been adding similar kinds of capabilities within some of our file services. So things like our, you know elastic file service launched a one zone storage class as well as an intelligent tiering capability to just automatically help customers save money. I think in some cases up to 92% on their their EFS storage costs with this automatic intelligent tiering capability. And then the last thing I would say is that we also are just continuing to help customers in other ways, like I said, our storage lens is a great way for customers to really dig in and figure out. 'Cause you know, often customers will find that they may have, you know, certain data sets that someone's forgotten about or, they're capturing more data than they expected perhaps in a logging application or something that ends up generating a lot more data than they expected. And so storage lens helps them really zoom in very quickly on, you know this is the data, here's how frequently it's being accessed and then they can make decisions about use that data I keep, how long do I keep it? Maybe that's good candidates to move down into one of our very cold storage classes like Glacier Deep Archive, where they they still have the data, but they don't expect to need to actively retrieve it on a regular basis. >> SDL bromide, if you can measure it, you can manage it. So if I can see it, visualize it, that I can take actions. When you think about S3- >> That's right. it's always been great for archival workloads but you made some updates to Glacier that changed the way that we maybe think about archive data. Can you talk about those changes specifically, what it means for how customers should leverage AWS services going forward? >> Yeah, and actually, you know, Glacier's coming up on its 10 year anniversary in August, so we're pretty excited about that. And you know, but there's just been a real increase in the pace of innovation, I think over the last three or four years there. So we launched the Glacier Deep Archive capability in 2019, 2018, I guess it was. And then we launched Glacier Instant Retrieval of course last year. So really what we're seeing is we now have three storage classes that cover are part of the Glacier family. So everything from millisecond retrieval for that data, that needs to be accessed quickly when it is accessed, but isn't being accessed, you know, regularly. So maybe a few times a year. And there's a lot of use cases that we're seeing really quickly emerge for that. Everything from, you know, user generated content like photos and videos, to big broadcaster archives and particularly in media and entertainment segment. Seeing a lot of interest in Glaciers Instant Retrieval because that data is pretty cold on a regular basis. But when they want to access it, they want a huge amount of data, petabytes of data potentially back within seconds, and that's the capability we can provide with Glacier Instant Retrieval. And then on the other end of the spectrum, with Glacier Deep Archive, again we have customers that have huge archives of data that they be looking to have that 3-AZ durability that we provide with Glacier, and make sure that data is protected. But really, you know expect to access it once a year if ever. Now it could be a backup copy of data or secondary or tertiary copy of data, could be data that they just don't have an active use for it. And I think that's one of the things we're starting to see grow a lot, is customers that have shared data sets where they may not need that data right now but they do want to keep it because as they think about, again these like new applications that can drive top line growth, they're finding that they may go back to that data six months or nine months from now and start to really actively use it. So if they want that option value to keep that data so they can use it down the road, Glacier Deep Archive, or Glacier Flexible Retrieval, which is kind of our storage class right in the middle of the road. Those are great options for customers to keep the data, keep it safe and secure, but then have it, you know pretty accessible when they're ready to get it back. >> Got it, thank you for that. So, okay, so customers have choices. I want to get into some of the competitive differentiators. And of course we were talking earlier about cost optimization, which is obviously an important topic given the macro environment you know, but there's more. And so help us understand what's different about AWS in terms of helping customers get value from their data, cost reduction as a component of value, part of the TCO, for sure. But just beyond being a cloud bit bucket, you know just a storage container in the cloud, what are some of the differentiators that you can talk to? >> Yeah, well Dave, I mean, I think that when it comes to value, I think there's tremendous benefits in AWS, well beyond just cost reduction. I think, you know, part of it is S3 now has built, I think, an earned reputation for being resilient, for storing, you know, at massive scale giving customers that confidence that they will be able to scale up. You know, we store more than 200 trillion objects. We regularly peak at over 100 million requests per second. So customers can build on S3 and Glacier with the confidence that we're going to be there to help their applications grow and scale over time. And then I think that in all of the applications both first party and third party, the customers can use, and services that they can use to build modern applications is an incredible benefit. So whether it's all of our serverless offerings, things like Lambda or containers and everything we have to manage that. Or whether it's the deep analytics and machine learning capabilities we have to help really extract, you know value and insight from data in near real time. You know, we're just seeing an incredible number of customers build those kinds of applications where they're processing data and feeding their results right back into their business right away. So I'm just going to briefly mention a couple, like, you know one example is ADP that really helps their customers measure, compare and sort of analyze their workforce. They have a couple petabytes of data, something like 25 billion individual data points and they're just processing that data continuously through their analytics and machine learning applications to then again, give those insights back to their customers. Another good example is AstraZeneca. You know, they are processing petabytes and petabytes of genomic sequencing data. And they have a goal to analyze 2 million genomes over the next four years. And so they're just really scaling up on AWS, both from a pure storage point of view, but more importantly, from all of the compute and analytics capability on top that is really critical to achieving that goal. And then, you know, beyond the first party services we have as I mentioned, it's really our third party, right? The AWS partner network provides customers an incredible range of choice in off the shelf applications that they can quickly provision and make use of the data to drive those business insights. And I think today the APN has something like 100,000 partners over in 150 countries. And we specifically have a storage competency partner where customers can go to get those applications that directly work, you know, on top of their data. And really, like I said, drive some of that insight. So, you know, I think it's that overall benefit of being able to really do a lot more with their data than just have it sit idle. You know, that's where I think we see a lot of customers interested in driving additional value. >> I'm glad you mentioned the ecosystem, and I'm glad you mentioned the storage competency as well. So there are other storage partners that you have, even though you're a head of a big storage division. And then I think there's some other under the cover things too. I've recently wrote, actually have written about this a lot. Things like nitro and rethinking virtualization and how to do, you know offloads. The security that comes, you know fundamentally as part of the platform is, I think architecturally is something that leads the way in the industry for sure. So there's a lot we could unpack, but you've fundamentally changed the storage market over the last 16 years. And again, I've written about this extensively. We used to think about storage in blocks or you got, you know, somebody who's really good in files, there were companies that dominated each space with legacy on-prem storage. You know, when you think about object storage Kevin, it was a niche, right? It was something used for archival, it was known for its simple, get put syntax, great for cheap and deep storage, and S3 changed that. Why do you think that's happened and S3 has evolved, the object has evolved the way it has, and what's the future hold for S3? >> Yeah I mean, you know, Dave, I think that probably the biggest overall trend there is that customers are looking to build cloud native applications. Where as much of that application is managed as they can have. They don't want to have to spend time managing the underlying infrastructure, the compute and storage and everything that goes around it. And so a fully managed service like S3, where there's no provisioning storage capacity, there's, you know we provide the resiliency and the durability that just really resonates with customers. And I think that increasingly, customers are seeing that they want to innovate across the entire range of business. So it's not about a central IT team anymore, it's about engineers that are embedded within lines of business, innovating around what is critical to achieve their business results. So, you know, if they're in a manufacturing segment, how can we pull data from sensors and other instrumentation off of our equipment and then make better decisions about when we need to do predictive maintenance, how quickly we can run our manufacturing line, looking for inefficiencies. And so we've developed around our managed offerings like S3, we've just developed, you know, customers who are investing and executing on plans and you know transformations. That really give them, you know put digital technology directly into the line of business that they're looking for. And I think that trend is just going to continue. People sometimes ask me, well "I mean, 16 years, you know, isn't S3 done?" And I would say, "By no stretcher are we done." We have plenty of feedback from customers on ways that we can continue to simplify, reduce the kinds of things they need to do, when they're looking for example and rolling out new security policies and parameters across their entire organization. So raising the bar there, finding, you know, raising the bar on how they can efficiently manage their storage and reduce costs. So I think we have plenty of innovation ahead of us to continue to help customers provide that fully managed capability. >> Yeah I often say Kevin, the next 10 years ain't going to be like the last in cloud. So I really thank you for coming on theCube and sharing your insights, really appreciate it. >> Absolutely Dave, thanks for having me. >> You're welcome. Okay keep it right there for more coverage of AWS Storage Day 2022 in theCube. (calm bright music)

(light music) >> Hello, welcome back everybody to theCUBE's coverage in New York City of AWS Summit 2022. I'm John Furrier, host of theCUBE. We had Dave Vellante, Lisa Martin here earlier. I'm going to wrap it up here with James Forrester, last interview of the day here in New York. Wish we would have had another day. It's a packed house, 10,000 people. James Forrester's the VP Worldwide Technical Leader for VMware's Cloud on AWS. On AWS is a big distinction. James, welcome to theCube. Thanks for coming on. >> Thank you so much, John. It's great to be here. >> So I think it's been like six years since the announcement of VMware's Cloud on AWS, which is a separate instance, separate hardware, but it's changed the game for VMware. You guys have done a lot of work, successful traction with customers. Clarified, I remember at that time, it really clarified VMware's Cloud play. Which then gave VMware more time to work on what it's doing now, which is, you know, using all their assets and their operations with Tanzu, Monterey, Cloud Native, Cross Cloud. What they call you guys call Cross Cloud, I call Super Cloud, action, a lot of stuff happening. So thanks for coming on. Okay. So first question is, what's the future look like for VMware's Cloud on AWS? >> Super bright, super bright. And there's a couple of great reasons for that. I think firstly, what we're seeing is that customers have now made enough progress in their cloud journeys. Many of them have chosen AWS and they're going full force. We're going to help them go faster. We're going to help them get there and get native to those adjacent services much quicker with more confidence and more resiliency. So it's a super exciting time to be doing what we do. >> You know, VMware has had a steady install base, okay. I mean basically it's like almost ingrained in the operations. What do you guys see as that next level step up function? Because you know, obviously Broadcom is buying VMware. Obviously that utility will be in place, but there's more. There's more there that customers can tap into. This is the promise of the cross-cloud. How do you talk about that when you got the AWS action? How does that all integrate? >> Yeah, absolutely. And of course, because so many customers are going to AWS on their own cloud journeys right now, what we get to have the conversation about is how they can get there more confidently. And so for customers who are just starting out, who are looking at their application portfolios, who have a ton of skilled IT professionals who they want to bring into that cloud journey, they can use the skills they already have. For those folks who are a little bit further along but they may be finding that refactoring their applications is more complex, more difficult that they anticipated, we give them a way of moving with confidence and with much less risk so they can do those cloud journeys that they anticipated. >> You know, James, I want to get your thoughts on what the state of the current situation is, vis-à-vis, your customers and your customers' appetite for AWS services. 'Cause one of the promises of the original deal was clarifying messaging but more importantly, customers can get the VMware Cloud and take advantage of the higher level services on AWS. What's the update there? What's the current state of the art? What's some of the patterns that you're seeing on the uptake of services and how they're working together? >> Yeah, it's a great call out. And honestly, one of the misconceptions that I address right out of the gate is that somehow going VMware Cloud takes you away from those services. It doesn't, it gets you closer to them. Full, direct, native access to all of those hundreds of great AWS services. So what we often find is that customers have their enterprise data, inside data workloads in their data centers. But what they want to do is get that up next to the AWS services that can use it, like Redshift and Athena and Glue. They can move those workloads right adjacent to those services to start using them right away. So it's a great way to look at the platform. >> So one of the observations that's pretty well understood right now by most people, I'd say 90%, if not more, not a hundred percent 'cause I've heard people like not get it, but it's pretty clear that the operating model for the the enterprise will be hybrid as a steady state. I don't think there's any debate on that unless you think there is. >> Do you feel the same- >> No debate. No debate. >> Okay. Hybrid's a steady state. What does that mean as clients start to think about edge and their data centers. 'Cause now the private cloud is back in the game. So I've heard people talk about private cloud, which we, I think we coined the term with Dave, Wikibon years ago, but it kind of went away because that was not the public cloud. So public cloud won, on premise didn't go away. We saw Amazon with Outpost. So now they're like, I can still have stuff on prem and run it in a cloud operations. So they're calling that private cloud, I think. So you're starting to hear the same things. What it means basically is that hybrid is winning. It's the standard. What does the hybrid environment look like from a VMware perspective as you guys look at that and have been building that out 'cause you have customers that are on premises. >> Yeah. >> Is it just to the cloud and back? Is it, is there any changes? Is there new connective tissue? Is there a glue layer? What's the operating model for VMware customers? >> Well, customers wanted those same benefits from public cloud agility, cost benefits, elasticity, innovation, sovereignty, sustainability, but they wanted to be able to do that everywhere. They wanted it in their data centers. They wanted it at the edge. And as you've pointed out public cloud delivered that for customers. AWS first out there delivering that for customers. Now with innovations like VMware Cloud and AWS outpost, we're able to bring that back into the data center. We're able to bring those same benefits of public cloud into the customers on-prem environment. And you're right. We see hybrid just rolling and rolling and being able to offer our solution across all of it. >> Yeah, we're big fans of VMware because theCube's 12 years old, we've been at every VMworld. Now they're calling it VMware Explorer, the events coming up. So the folks watching, plug for VMware Explorer, formerly VMworld, it's on the schedule. Content catalog just came out last week. It's looking pretty good. So put a plug out there. We'll be there with theCube, two sets. So you know, if you're going to VMworld, now Explorer go register, get up there. It's in San Francisco, always a great event. vSphere and vSAN, always great products. But you got Carbon Black, you got Security. So these things have all been working kind of pistons for VMware. Tanzu, I know Raghu and those guys are doing it. Craig McLuckie and team, they're working on that. You got Tanzu, you got Monterey. That's the new cloud native thing. How is that tracking vis-à-vis, the operating model of the the core engine, vSphere, vSAN and others. And then with the native services of Cloud. So you got AWS Cloud with VMware Cloud, vSphere, vSAN, Carbon Black, and Security. And then you got the Tanzu over here. How are those three things coming together? >> Well, the services that customers know and love first and foremost that they've been running the mission critical workloads on, vSphere, vSAN, NSX. What VMware cloud and AWS is, is a packaging together of those services. So customers don't have to configure it all themselves and do the heavy lifting. We manage and run it on their behalf. What we are adding to that most recently with Tanzu is now the ability to run containers within the same environment. 'Cause customers tell us they've got parts of their organization that are very much on vSphere VMs. Parts of their organization are moving to containers. We want be able to provide a single operating model, a single layer, a single way of managing all of that. No matter where it's deployed. >> You know, remember back in the day, when Raghu wasn't the CEO, Carl Eschenbach was there, Sanjay Poonen was there. Carl's now at Sequoia Capital, Raghu's a CEO. Sanjay's kind of looking for a next gig. I always said, why doesn't vSphere and NSX become that abstraction layer and commoditize the network so that white boxes and Dell and HP could all play in that layer? It just never happened yet. Is that something you guys talk about at all? Like, I mean in the, in the smokey room, in the execs, is that happening? What's the vision? >> Well, we always work backwards- from customers, right? (John laughing) And what customers are telling us is they want us to help them with that undifferentiated heavy lifting. So who knows where that could take us, but right now we're very focused on helping those customers move with confidence to the cloud. >> You didn't take the bait on that one. I appreciate that. (James laughing) Okay. So let's get some perspective. You're out with customers. What are the big things that you're seeing right now from your customers right now? 'Cause you look behind us here, 10,000 people at this event. This is not a no-show. This is not a throwaway event in, you know, somewhere in the corner of the world. This is New York City, only one summit. This is bigger than Snowflake Summit and that was packed. So from an event standpoint, this is pretty a big game statement here for AWS. These companies are not experiencing headwinds, they're changing. So what are your customers telling you around what they're looking at for the cloud native architecture? I mean obviously the digital transformation is continuing, obviously clouds here. And again, we were saying earlier, this is the first time in history that the cloud hyperscalers have been in market during a so-called downturn. So there's no other data. 2008, I wouldn't call 'em up and running. They were building, but AWS, Azure, others, these cloud players they're in market. And so you're starting to see kind of some data coming out saying, Hey, this thing's still working, the engine of innovation is cranking out and it's not slowing down the digital transformation. It might change the capital markets and valuations but it's not changing customers. That's what I'm hearing. Now, you probably would agree with that, right? >> James: I think that's exactly right. >> Okay. So let's stay with that. If you believe that, then it's like, okay, what are they doing? So what are customers doubling down on? What are some of the patterns you're seeing in the environment today that you could share with the audience? >> Yeah, so I think first and foremost is that steady transition to the cloud to deliver all of those benefits, agility, cost, elasticity, innovation, sovereignty, sustainability that hasn't gone away at all. In fact, it's only accelerated. With workloads like virtual desktops, which became so critical during COVID the need to be able to provide that kind of scalable elastic capacity has only increased. Now, coupled with that, most of these customers are already on a cloud journey. And while some folks may have had the luxury of letting that go a little bit more slowly, nowadays the urgency is pervasive across all of the industries that we get to talk to in New York. Everyone needs to go faster. Everybody's not seeing the progress that they expected that we think we can help them deliver. So the opportunity I think that's come out of COVID is more workloads, different use cases, disaster recovery, ransomware- >> Is that more of an awareness or reality or both? >> Both. Absolutely. >> Okay. So let me ask the next question. 'Cause this is a good conversation, I think. I agree a hundred percent. We're seeing the same exact thing. Now let's talk about how companies are thinking about the real opportunity that's emerged, which is refactoring the business model without actually changing the makeup of the organization per se, to take on new territories and potentially take over categories. >> James: Mm hmm. >> So I mean a data warehouse and a data cloud's kind of the same thing. Snowflake probably wouldn't like me saying that they're a data warehouse because they call themselves a data cloud, but it's kind of the same thing, just refactored on AWS. >> James: Yep. >> That's a super cloud. So that's an opportunity for everyone to do that in every vertical. How many customers are actually thinking that way and actually taking steps to pursue that, capture that opportunity? Or do you agree it's the opportunity? >> No, I think that that is an opportunity and I love that idea of super cloud in that what I think customers have started to realize, over the last couple of years in particular, is it's very difficult to take advantage of all of those great cloud services if your applications are still behind a whole lot of different layers of firewalls and so forth. So getting the application close to those services, in proximity to those services is that first step in modernization. Then it doesn't have to be a change the wings on the plane while it's flying conversation, which- >> John: Yeah. >> You know, is very risky for a lot of organizations. >> John: Exactly. >> It's a let's get the plane going a little bit faster. Let's get the plane going a little bit smoother, and let's get the plane to its destination with less risk. >> You know, James, that reminds me of the old school conversations of non disruptive operations. Remember those days? >> James: I do, yeah. >> Mostly around storage and, and servers. But that's what basically what you're saying. Transform while operating, right? >> James: Exactly. >> So this is, you can do both. You got to make time and it's a talent question too. I'd love to get your thoughts on how customers are thinking about who do you put on which task. 'Cause you want your A players on both areas. You don't want all your A players, what I hear, CSOs and CIOs telling me is that, I put all my A players on transformation, I got no one running the business. >> James: Mm hmm. >> So you got to kind of balance. That's a cultural team decision. >> It's a cultural team decision. It's also a skills marketplace decision. >> John: Yeah. >> And there's a practical reality to the skills that are available and how fast you can hire them. So a big part of the conversation that we have is when customers have existing skills sets, plug those into their transformation, plug those into their business outcomes. I like to use the phrase, "Let's make heroes out of IT" because they can be a much more critical player than they think they can be. Yeah, IT basically is not even around anymore. It's part of the organization. And then you have data science and data engineering coming in. So it's, you know, IT is not a department anymore, it's the company >> Exactly right. >> If you're kind of going down that road, yeah. >> Yeah. Alright, so final question. What's the biggest change you've seen and observed in your current year and a half? You know, we're coming out of COVID, knowing what was before, what sea change, what inflection point are we in now? How would you describe this current market? 'Cause again, we're kind of in a unique market. You know, you got crypto around the corner, people getting attracted to that, little bubbly obviously, reality of cloud and 2.0 or super cloud emerging. On premise is not going away. Edge exploding on the industrial side, especially with machine learning coming along. So this operating model is clearly in sight. What's the biggest observation you've noticed. >> I think it's the sense of urgency over the last couple of years in that most customers I talked to are no longer relaxed about the timing of delivering cloud capabilities to their organizations. Most customers are on sort of a transformation journey of their own and digital transformation and cloud transformation are absolutely fundamental to that. >> One more real quick follow up question if you don't mind, 'cause I appreciate your time. One of the things that's come up a lot in our conversations is the role of the ecosystem. Not only as a part of the business model but also validation of the enablement that cloud offers companies. You have an enabling platform, your ecosystem is well known. And so your customers are starting to develop ecosystems. So if the cloud model kind of trickles like downstream, ecosystem is kind of a proof of something. >> James: Mm hmm. >> What's your view of all this ecosystem discussion as we transform this next generation? >> Yeah, I think it touches on a couple of things. So obviously there is a technology ecosystem, which is evolving very rapidly in support of cloud and cloud transformation. But what's interesting, I think is the business ecosystem that's evolving around it. We're seeing our customers evolve their own businesses to assume that those cloud capabilities will be available to them. And if the cloud capabilities are not available to them in a timely fashion, then the ecosystem starts to have a domino effect. So the ecosystems are interdependent between business, and technology, and skills, and talent. And I think that's a great to be >> James Forrester, they're going to shut us down. The speakers are on, they're going to pull the plug. Thanks for being our last interview here in New York City and bringing us home. Really appreciate you taking the time to come on theCube. >> John, thanks so much. Great to be here, really enjoyed it. Okay. We are wrapping it up here in New York City. I'm John Ford with theCube, great day. For Lisa Martin, Dave Vellante, and the entire crew of theCube here on the ground. Live in person events are back. theCube hybrid, get online, check out our coverage there. The SiliconANGLE and thecube.net. I'm John Furrier signing off from New York City. See you next time. (light music)

>> Announcer: theCUBE presents HPE Discover 2022. Brought to you by HPE. >> Okay, we're back here at HPE Discover 2022, theCUBE's continuous coverage. This is day two, Dave Vellante with John Furrier. John Frey's here. He is the chief technologist for sustainable transformation at Hewlett Packard Enterprise and Justin Murrill who's the director of corporate responsibility for AMD. Guys, welcome to theCUBE. Good to see you. >> Thank you. >> Thank you. It's great to be here. >> So again, I remember the days where, you know, CIOs didn't really care about the power budget. They didn't pay the power budget. You had, you know, facilities over here, IT over here and they didn't talk to each other. That's changed. Why is there so much discussion around sustainable IT today? >> It's exciting to see how much it's up leveled, as you say. I think there are a couple different trends happening but mainly, you know, the IT teams and IT leaders that are making decisions are seeing to your point how their decisions are affecting enterprise level, greenhouse gas emission reduction goals. So that connection is becoming very clear. Everything from the server processor to beyond it, those decisions have a key role. And importantly we're seeing, you know, 60% of the Fortune 500 now have climate or energy efficiency related goals. So there's a perfect storm of sorts happening where more companies setting goals, IT decision makers looking particularly at the data center because as the computational heart of an organization, it has a wealth of opportunity from an energy and a mission savings perspective. >> I'm surprised it's only 60%. I mean, that number really shocked me. So it's got to be a 100% within the next couple of years here. I would think, I mean, it's not trivial, right? You've got responsibilities in terms of reporting and you can't just mail it in, right? >> Yeah, absolutely. So there's a lot more disclosure happening but the goal setting is really upleveling as well. >> And the metrics involved too. Can you just scope the scale and challenge of like getting the right metrics, not when you have the goals. Does that factor in, how do you see there? What's your commentary on that? >> Yeah, I think there's, the aperture is continuing to open as metrics go, so to speak. So from an operations perspective, companies are reporting on what's referred to as scope one and scope two. And scope two is the big one from electricity, right? And then scope three is everything else. That's the supply chain and the outside of that. So a lot of implications there as well from IT decision making. >> Is there a business case for sustainable IT? I mean, you're probably not going to lower the power budget, right? But is it just, hey, it's the right thing to do. We have to do it, it's good for the brand. It'll allow us to attract people or is there a a more of a rich business case? >> So there really is a business case even just within inside the data center walls, for example. There's inefficiencies that are inherent in many of these data centers. There's really low utilization levels as well. And by reducing over provisioning and increasing utilization, there's real money to be saved in terms of equipment costs, maintenance agreement costs, software licensing costs. So actually the power consumption and the environmental piece is an added benefit but it's not the main reason. So we actually had IDC do a survey for us last year and we asked IT executives, 500 senior IT executives, were you implementing sustainable IT programs and why? My guess initially was about 40% of them would say yes. Actually the number was 96% of them. And when we asked them why they fell into three categories. The digital leaders, those that are the early adopters moving the quickest. They said we do it to attract and retain institutional investors. They've been hearing from their boards. They've been hearing from their investor relations teams and investors are starting to ask and even in a couple cases board seats are becoming contentious based on the environmental perspective of the person being nominated. This digital mainstream, the folks in the middle about 80% of the total pie, they're doing it to attract and retain customers because customers are asking them about their sustainable IT programs. If they're a non-manufacturing customer, their data center consumption is probably the largest part of their company. It's also by the way usually the most expensive real estate the company owns. So customers are asking and customers are not only asking, do you have basic programs in place? But they're asking, what are your goals to Justin's point? The customers are starting to realize that carbon goals have been vaguely defined historically. So they're asking for specificity, they're asking for transparency and by the way the science-based target initiative recently released their requirements for net zero science-based targets. And that requires significant reduction to your point before you start considering renewable energy in that balance. The third reason those digital followers, that slowest group or folks that are in industries that move the slowest, they said they were doing this to attract and retain employees. Because they recognize the data scientists, the computer science, computer engineering students that they're trying to attract want to work at a company where they can see how what they do directly contributes to purpose. And they vote with their feet. If they come on and they can't make that connection pretty quickly or if they spend a lot of their time chasing down inefficiencies in a technology infrastructure, they're not going to stay there very long. >> I mean, the mission-driven organization is definitely an employee factor. People are interested in that. The work for company is responsible, doing the right thing but that business case is interesting because I think there's recognition now more than ever before. You think you're right on. It used to be kind of like mailed it in before. Okay, we're doing some stuff. Now it's like, we all have to do it. And it's a board issue. It's a financing issue. It might be a filing issue as you guys mentioned. So that's all great. So I got to ask how you guys specifically are working together, AMD and HPE. What are you guys doing to make it more efficient? And then I'll see with Cloud and Cloud scale, there's more servers being shipped now than ever before. And more devices at the edge. What are you guys doing together specifically? >> Yeah, we've been working together, AMD and HPE on advancing sustainability for many years. I've had the opportunity to working directly with John for many years and I've learned a lot from him and your team. It's fantastic to see all the developments here. I mean, so most recently the top 500 and the green 500 list of supercomputers came out. And at the top of that list is AMD HPE systems. And it shows kind of the pinnacle of what can be possible for other data centers looking to modernize and scale. So the number one system, the fastest system in the world and the most energy efficient system in the world, the Frontier supercomputer has AMD HPE technology in it. And it just passed the exit scale barrier. I mean, I'm still just blown away by this. A billion, billion calculations per second. It's just amazing. And the research is doing around clean energy, alternative energy sources, scientific research is really exciting. So there's that. The other system that really jumps out is the LUMI system, the number three system because it's a 100% powered by renewable energy. So not only that, it takes the heat and it channels it to a nearby town and covers 20% of that town's heating needs thereby avoiding 12,400 metric tons of carbon emissions. So this system is carbon negative, right? And you just go down the list. I mean, AMD is in the top eight out of 10 most green... >> Rewind that second. So you have the heat and the power shifting to a town? >> Yes, the LUMI supercomputer has the heat from the system to an nearby town. It's like a closed loop, the idea of circular economy but with energy. And it takes that waste and it makes it an input, a resource. >> But this is the kind of innovation that's going on, right? This is the scale, this is where scale and efficiency kind of come together. That's huge. Where's that going to go? What's your perspective on where that goes next because that's a blueprint that could be replicated. >> You bet. So I think we're going to continue to see overall power consumption go up at the system level. But performance per wat is climbing much more dramatically. So I think that's going to continue to scale. It's going to require a new cooling technology. So direct liquid cooling is becoming more and more in use and customers really interested in that. There's shifting from industry standard architectures to lower end high performance computer architectures to get direct liquid cooling, higher core processors and get the performance they want in a smaller footprint. And at the same time, they're really thinking about how do we operate the infrastructure as a system not as individual piece parts. And one of the things that Frontier and LUMI do so well is they were designed from the start as a system, not as piece parts making up the system. So I think that happens. The other thing that's really critical is no one company is going to solve these challenges ourself. So one of the things I love about our partnership with AMD is we look at each other's sustainability goals before we launch 'em. We say, well, how can we help? One of AMD's goals that I'll let Justin talk about came about because HPE at the time of separation laid a really aggressive product, energy efficiency goal out, said but we're not sure how we're going to make this. And AMD said we can help. So that collaboration, we critique each other's programs, we push each other, but we work together. I like to say partnership is leadership in this. >> Well, that's a nuance point. Before you get to that solution there Justin, this system's thinking is really important. You're seeing that now with Cloud. Some of the things that GreenLake and the systems are pointing out, this holistic systems' thinking is applied to partnerships, not just the company. >> Yep. >> This is a really nuanced point but we're seeing that more and more. >> Yeah, absolutely. In fact, Justin mentioned the heat reuse, same way with the national renewable energy lab. They actually did snow removal and building heating with the heat reuse. So if you're designing for example, a liquid cold system from the start, how do you make it a symbiotic relationship? There's more and more interest in co-locating data centers and greenhouses in colder environments for example. Because the principle of the circular economy is nothing is waste. So if you think it's waste or you think it's a byproduct, think about how can that be an input to something else. >> Right, so you might put a data center so you can use ambient cooling or in somewhere in the Columbia River so you can, you know, take advantage of, you know, renewable energy. What are some goals that you guys can share with us? >> So we've got some great momentum and a track record coming off of, going back to 2014, we set a 25 by 20 goal to improve the energy efficiency for our mobile processors and mobile devices, right? So laptops. And we were able to achieve a 31.7x in that timeframe. So which was twice the industry trend to that. And then moving on, we've doubled down on data center and we've set a new goal of a 30x increase in energy efficiency for our server processors and accelerators to really focused on HPC and AI training. So that's a 30x goal over 2020 to 2025 focused on these really important workloads 'cause they're fast growing. We heard yesterday 150 billion devices connected by 2025 generating a lot of data, right? So that's one of the reasons why we focused on that. 'Cause these are demanding workloads. And this represents a 2.5x increase over the historical trend, right? And fundamentally speaking, that's a 97% reduction in energy use per computation in five years. So we're very pleased. We announced an update recently. We're at 6.8x. We're on track for this goal and making great progress and showing how these, you know, solutions at a processor level and an accelerator level can be amplified, taken into HPE technology. >> Generally tech companies, you know, that compete want to rip each other's faces off. And is that the case in this space or do you guys collaborate with your competitors to share best practice? Is that beginning? Is it already there? >> There's much more collaboration in this space. This is one of the safe places I think where collaboration does occur more. >> Yeah. And we've all got to work together. A great example that was in the supply chain. When HPE first set our supply chain expectations for our suppliers around things like worker rights and environment and worker protection from a health and safety perspective. We initially had our code of conduct asked their suppliers to comply with it. Started auditing in event. And we quickly got into the factories and saw they were doing it for our workloads. But if you looked around the factory, they weren't doing in other places. And we took a step back and said, well, wait a minute. Why is that? And they said that vendor doesn't require it. So we took a step back and said let's get the industry together. We share a common supply chain. How do we have a common set of expectations and push them out to our supply chain? How to now do third party audits so the same supplier doesn't get audited by each of the major vendors and then share those audit results. And what we found was that really had a large lever effect of moving the electronic supply chain much more rapidly towards our expectations in all those areas. Well then other industries looked and said, well, wait a minute, if that worked for electronics, it'll probably work broader. And so now, the output of that is what's called the responsible business alliance across many industries taking that same approach. So that's a pre-competitive. We all have the same challenge. In many cases we share a common supply chain. So that's a great example of electronic companies coming together, design standards for things. There's a green grid group at the moment looking at liquid cooling connects. You know, we don't want every vendor to have a different connection point for liquid cooling for example. So how do we standardize that to make our customers have a easier time about looking at the technologies they want from any vendor and having common connection points. >> Right. Okay. So a lot of collaboration. Last question. How much of a difference do you think it can make? In other words, what percent of the blame pie goes to information technology? And I think regardless, you got to do your part. Will it make a dent? >> I think the sector has done a really good job of keeping that increase from going up while exponentially increasing performance. So it's been a really amazing industry effort. And moving forward, I think this is more important than ever, right? And with the slowdown of Moore's law we're seeing more gains that need to come from beyond process architecture to include packaging innovations, to power management, to just the architecture here. So the challenge of mitigating and minimizing energy growth is important. And we believe like with that 30x energy efficiency goal that it is doable but it does take a lot of collaboration and focus. >> That's a great point. I mean, if you didn't pay attention to this, IT could really become a big piece of the pie. Guys thanks so much for coming on theCUBE. Really appreciate. >> People are watching. They're paying attention at all levels. Congratulations. >> Absolutely. >> All right, Dave Vellante, John Furrier and our guests. Don't forget to go to SiliconANGLE.com for all the news. Our YouTube channel, actually go to CUBE.net. You'll get all these videos in our YouTube channel, youtube.com/SiliconANGLE. You can check out everything on demand. Keep it right there. We'll be right back. HPE Discover 2022 from Las Vegas. You're watching theCUBE. (soft music)

>> From theCUBE studios in Palo Alto in Boston, bringing you data driven insights from theCUBE and ETR. This is Breaking Analysis with Dave Vellante. >> In the words of my colleague CTO David Nicholson, Broadcom buys old cars, not to restore them to their original luster and beauty. Nope. They buy classic cars to extract the platinum that's inside the catalytic converter and monetize that. Broadcom's planned 61 billion acquisition of VMware will mark yet another new era and chapter for the virtualization pioneer, a mere seven months after finally getting spun out as an independent company by Dell. For VMware, this means a dramatically different operating model with financial performance and shareholder value creation as the dominant and perhaps the sole agenda item. For customers, it will mean a more focused portfolio, less aspirational vision pitches, and most certainly higher prices. Hello and welcome to this week's Wikibon CUBE Insights powered by ETR. In this Breaking Analysis, we'll share data, opinions and customer insights about this blockbuster deal and forecast the future of VMware, Broadcom and the broader ecosystem. Let's first look at the key deal points, it's been well covered in the press. But just for the record, $61 billion in a 50/50 cash and stock deal, resulting in a blended price of $138 per share, which is a 44% premium to the unaffected price, i.e. prior to the news breaking. Broadcom will assume 8 billion of VMware debt and promises that the acquisition will be immediately accretive and will generate 8.5 billion in EBITDA by year three. That's more than 4 billion in EBITDA relative to VMware's current performance today. In a classic Broadcom M&A approach, the company promises to dilever debt and maintain investment grade ratings. They will rebrand their software business as VMware, which will now comprise about 50% of revenues. There's a 40 day go shop and importantly, Broadcom promises to continue to return 60% of its free cash flow to shareholders in the form of dividends and buybacks. Okay, with that out of the way, we're going to get to the money slide literally in a moment that Broadcom shared on its investor call. Broadcom has more than 20 business units. It's CEO Hock Tan makes it really easy for his business unit managers to understand. Rule number one, you agreed to an operating plan with targets for revenue, growth, EBITDA, et cetera, hit your numbers consistently and we're good. You'll be very well compensated and life will be wonderful for you and your family. Miss the number, and we're going to have a frank and uncomfortable bottom line discussion. You'll four, perhaps five quarters to turn your business around, if you don't, we'll kill it or sell it if we can. Rule number two, refer to rule number one. Hello, VMware, here's the money slide. I'll interpret the bullet points on the left for clarity. Your fiscal year 2022 EBITDA was 4.7 billion. By year three, it will be 8.5 billion. And we Broadcom have four knobs to turn with you, VMware to help you get there. First knob, if it ain't recurring revenue with rubber stamp renewals, we're going to convert that revenue or kill it. Knob number two, we're going to focus R&D in the most profitable areas of the business. AKA expect the R&D budget to be cut. Number three, we're going to spend less on sales and marketing by focusing on existing customers. We're not going to lose money today and try to make it up many years down the road. And number four, we run Broadcom with 1% GNA. You will too. Any questions? Good. Now, just to give you a little sense of how Broadcom runs its business and how well run a company it is, let's do a little simple comparison with this financial snapshot. All we're doing here is taking the most recent quarterly earnings reports from Broadcom and VMware respectively. We take the quarterly revenue and multiply by four X to get the revenue run rate and then we calculate the ratios off of the most recent quarters revenue. It's worth spending some time on this to get a sense of how profitable the Broadcom business actually is and what the spreadsheet gurus at Broadcom are seeing with respect to the possibilities for VMware. So combined, we're talking about a 40 plus billion dollar company. Broadcom is growing at more than 20% per year. Whereas VMware's latest quarter showed a very disappointing 3% growth. Broadcom is mostly a hardware company, but its gross margin is in the high seventies. As a software company of course VMware has higher gross margins, but FYI, Broadcom's software business, the remains of Symantec and what they purchased as CA has 90% gross margin. But the I popper is operating margin. This is all non gap. So it excludes things like stock based compensation, but Broadcom had 61% operating margin last quarter. This is insanely off the charts compared to VMware's 25%. Oracle's non gap operating margin is 47% and Oracle is an incredibly profitable company. Now the red box is where the cuts are going to take place. Broadcom doesn't spend much on marketing. It doesn't have to. It's SG&A is 3% of revenue versus 18% for VMware and R&D spend is almost certainly going to get cut. The other eye popper is free cash flow as a percentage of revenue at 51% for Broadcom and 29% for VMware. 51%. That's incredible. And that my dear friends is why Broadcom a company with just under 30 billion in revenue has a market cap of 230 billion. Let's dig into the VMware portfolio a bit more and identify the possible areas that will be placed under the microscope by Hock Tan and his managers. The data from ETR's latest survey shows the net score or spending momentum across VMware's portfolio in this chart, net score essentially measures the net percent of customers that are spending more on a specific product or vendor. The yellow bar is the most recent survey and compares the April 22 survey data to April 21 and January of 22. Everything is down in the yellow from January, not surprising given the economic outlook and the change in spending patterns that we've reported. VMware Cloud on AWS remains the product in the ETR survey with the most momentum. It's the only offering in the portfolio with spending momentum above the 40% line, a level that we consider highly elevated. Unified Endpoint Management looks more than respectable, but that business is a rock fight with Microsoft. VMware Cloud is things like VMware Cloud foundation, VCF and VMware's cross cloud offerings. NSX came from the Nicira acquisition. Tanzu is not yet pervasive and one wonders if VMware is making any money there. Server is ESX and vSphere and is the bread and butter. That is where Broadcom is going to focus. It's going to look at VSAN and NSX, which is software probably profitable. And of course the other products and see if the investments are paying off, if they are Broadcom will keep, if they are not, you can bet your socks, they will be sold off or killed. Carbon Black is at the far right. VMware paid $2.1 billion for Carbon Black. And it's the lowest performer on this list in terms of net score or spending momentum. And that doesn't mean it's not profitable. It just doesn't have the momentum you'd like to see, so you can bet that is going to get scrutiny. Remember VMware's growth has been under pressure for the last several years. So it's been buying companies, dozens of them. It bought AirWatch, bought Heptio, Carbon Black, Nicira, SaltStack, Datrium, Versedo, Bitnami, and on and on and on. Many of these were to pick up engineering teams. Some of them were to drive new revenue. Now this is definitely going to be scrutinized by Broadcom. So that helps explain why Michael Dell would sell VMware. And where does VMware go from here? It's got great core product. It's an iconic name. It's got an awesome ecosystem, fantastic distribution channel, but its growth is slowing. It's got limited developer chops in a world that developers and cloud native is all the rage. It's got a far flung R&D agenda going at war with a lot of different places. And it's increasingly fighting this multi front war with cloud companies, companies like Cisco, IBM Red Hat, et cetera. VMware's kind of becoming a heavy lift. It's a perfect acquisition target for Broadcom and why the street loves this deal. And we titled this Breaking Analysis taming the VMware beast because VMware is a beast. It's ubiquitous. It's an epic software platform. EMC couldn't control it. Dell used it as a piggy bank, but really didn't change its operating model. Broadcom 100% will. Now one of the things that we get excited about is the future of systems architectures. We published a breaking analysis about a year ago, talking about AWS's secret weapon with Nitro and it's Annapurna custom Silicon efforts. Remember it acquired Annapurna for a measly $350 million. And we talked about how there's a new architecture and a new price performance curve emerging in the enterprise, driven by AWS and being followed by Microsoft, Google, Alibaba, a trend toward custom Silicon with the arm based Nitro and which is AWS's hypervisor and Nick strategy, enabling processor diversity with things like Graviton and Trainium and other diverse processors, really diversifying away from x86 and how this leads to much faster product cycles, faster tape out, lower costs. And our premise was that everyone in the data center is going to competes, is going to need a Nitro to be competitive long term. And customers are going to gravitate toward the most economically favorable platform. And as we describe the landscape with this chart, we've updated this for this Breaking Analysis and we'll come back to nitro in a moment. This is a two dimensional graphic with net score or spending momentum on the vertical axis and overlap formally known as market share or presence within the survey, pervasiveness that's on the horizontal axis. And we plot various companies and products and we've inserted VMware's net score breakdown. The granularity in those colored bars on the bottom right. Net score is essentially the green minus the red and a couple points on that. VMware in the latest survey has 6% new adoption. That's that lime green. It's interesting. The question Broadcom is going to ask is, how much does it cost you to acquire that 6% new. 32% of VMware customers in the survey are increasing spending, meaning they're increasing spending by 6% or more. That's the forest green. And the question Broadcom will dig into is what percent of that increased spend (chuckles) you're capturing is profitable spend? Whatever isn't profitable is going to be cut. Now that 52% gray area flat spending that is ripe for the Broadcom picking, that is the fat middle, and those customers are locked and loaded for future rent extraction via perpetual renewals and price increases. Only 8% of customers are spending less, that's the pinkish color and only 3% are defecting, that's the bright red. So very, very sticky profile. Perfect for Broadcom. Now the rest of the chart lays out some of the other competitor names and we've plotted many of the VMware products so you can see where they fit. They're all pretty respectable on the vertical axis, that's spending momentum. But what Broadcom wants is that core ESX vSphere base where we've superimposed the Broadcom logo. Broadcom doesn't care so much about spending momentum. It cares about profitability potential and then momentum. AWS and Azure, they're setting the pace in this business, in the upper right corner. Cisco very huge presence in the data center, as does Intel, they're not in the ETR survey, but we've superimposed them. Now, Intel of course, is in a dog fight within Nvidia, the Arm ecosystem, AMD, don't forget China. You see a Google cloud platform is in there. Oracle is also on the chart as well, somewhat lower on the vertical axis, but it doesn't have that spending momentum, but it has a big presence. And it owns a cloud as we've talked about many times and it's highly differentiated. It's got a strategy that allows it to differentiate from the pack. It's very financially driven. It knows how to extract lifetime value. Safra Catz operates in many ways, similar to what we're seeing from Hock Tan and company, different from a portfolio standpoint. Oracle's got the full stack, et cetera. So it's a different strategy. But very, very financially savvy. You could see IBM and IBM Red Hat in the mix and then Dell and HP. I want to come back to that momentarily to talk about where value is flowing. And then we plotted Nutanix, which with Acropolis could suck up some V tax avoidance business. Now notice Symantec and CA, relatively speaking in the ETR survey, they have horrible spending momentum. As we said, Broadcom doesn't care. Hock Tan is not going for growth at the expense of profitability. So we fully expect VMware to come down on the vertical axis over time and go up on the profit scale. Of course, ETR doesn't measure the profitability here. Now back to Nitro, VMware has this thing called Project Monterey. It's essentially their version of Nitro and will serve as their future architecture diversifying off x86 and accommodating alternative processors. And a much more efficient performance, price in energy consumption curve. Now, one of the things that we've advocated for, we said this about Dell and others, including VMware to take a page out of AWS and start developing custom Silicon to better integrate hardware and software and accelerate multi-cloud or what we call supercloud. That layer above the cloud, not just running on individual clouds. So this is all about efficiency and simplicity to own this space. And we've challenged organizations to do that because otherwise we feel like the cloud guys are just going to have consistently better costs, not necessarily price, but better cost structures, but it begs the question. What happens to Project Monterey? Hock Tan and Broadcom, they don't invest in something that is unproven and doesn't throw off free cash flow. If it's not going to pay off for years to come, they're probably not going to invest in it. And yet Project Monterey could help secure VMware's future in not only the data center, but at the edge and compete more effectively with cloud economics. So we think either Project Monterey is toast or the VMware team will knock on the door of one of Broadcom's 20 plus business units and say, guys, what if we work together with you to develop a version of Monterey that we can use and sell to everyone, it'd be the arms dealer to everyone and be competitive with the cloud and other players out there and create the de facto standard for data center performance and supercloud. I mean, it's not outrageously expensive to develop custom Silicon. Tesla is doing it for example. And Broadcom obviously is capable of doing it. It's got good relationships with semiconductor fabs. But I think this is going to be a tough sell to Broadcom, unless VMware can hide this in plain site and make it profitable fast, like AWS most likely has with Nitro and Graviton. Then Project Monterey and our pipe dream of alternatives to Nitro in the data center could happen but if it can't, it's going to be toast. Or maybe Intel or Nvidia will take it over or maybe the Monterey team will spin out a VMware and do a Pensando like deal and demonstrate the viability of this concept and then Broadcom will buy it back in 10 years. Here's a double click on that previous data that we put in tabular form. It's how the data on that previous slide was plotted. I just want to give you the background data here. So net score spending momentum is the sorted on the left. So it's sorted by net score in the left hand chart, that was the y-axis in the previous data set and then shared and or presence in the data set is the right hand chart. In other words, it's sorted on the right hand chart, right hand table. That right most column is shared and you can see it's sorted top to bottom, and that was the x-axis on the previous chart. The point is not many on the left hand side are above the 40% line. VMware Cloud on AWS is, it's expensive, so it's probably profitable and it's probably a keeper. We'll see about the rest of VMware's portfolio. Like what happens to Tanzu for example. On the right, we drew a red line, just arbitrarily at those companies and products with more than a hundred mentions in the survey, everything but Tanzu from VMware makes that cut. Again, this is no indication of profitability here, and that's what's going to matter to Broadcom. Now let's take a moment to address the question of Broadcom as a software company. What the heck do they know about software, right. Well, they're not dumb over there and they know how to run a business, but there is a strategic rationale to this move beyond just doing portfolios and extracting rents and cutting R&D, et cetera, et cetera. Why, for example, isn't Broadcom going after coming back to Dell or HPE, it could pick up for a lot less than VMware, and they got way more revenue than VMware. Well, it's obvious, software's more profitable of course, and Broadcom wants to move up the stack, but there's a trend going on, which Broadcom is very much in touch with. First, it sells to Dell and HPE and Cisco and all the OEM. so it's not going to disrupt that. But this chart shows that the value is flowing away from traditional servers and storage and networking to two places, merchant Silicon, which itself is morphing. Broadcom... We focus on the left hand side of this chart. Broadcom correctly believes that the world is shifting from a CPU centric center of gravity to a connectivity centric world. We've talked about this on theCUBE a lot. You should listen to Broadcom COO Charlie Kawwas speak about this. It's all that supporting infrastructure around the CPU where value is flowing, including of course, alternative GPUs and XPUs, and NPUs et cetera, that are sucking the value out of the traditional x86 architecture, offloading some of the security and networking and storage functions that traditionally have been done in x86 which are part of the waste right now in the data center. This is that shifting dynamic of Moore's law. Moore's law, not keeping pace. It's slowing down. It's slower relative to some of the combinatorial factors. When you add up in all the CPU and GPU and NPU and accelerators, et cetera. So we've talked about this a lot in Breaking Analysis episodes. So the value is shifting left within that middle circle. And it's shifting left within that left circle toward components, other than CPU, many of which Broadcom supplies. And then you go back to the middle, value is shifting from that middle section, that traditional data center up into hyperscale clouds, and then to the right toward infrastructure software to manage all that equipment in the data center and across clouds. And look Broadcom is an arms dealer. They simply sell to everyone, locking up key vectors of the value chain, cutting costs and raising prices. It's a pretty straightforward strategy, but not for the fate of heart. And Broadcom has become pretty good at it. Let's close with the customer feedback. I spoke with ETRs Eric Bradley this morning. He and I both reached out to VMware customers that we know and got their input. And here's a little snapshot of what they said. I'll just read this. Broadcom will be looking to invest in the core and divest of any underperforming assets, right on. It's just what we were saying. This doesn't bode well for future innovation, this is a CTO at a large travel company. Next comment, we're a Carbon Black customer. VMware didn't seem to interfere with Carbon Black, but now that we're concerned about short term disruption to their tech roadmap and long term, are they going to split and be sold off like Symantec was, this is a CISO at a large hospitality organization. Third comment, I got directly from a VMware practitioner, an IT director at a manufacturing firm. This individual said, moving off VMware would be very difficult for us. We have over 500 applications running on VMware, and it's really easy to manage. We're not going to move those into the cloud and we're worried Broadcom will raise prices and just extract rents. Last comment, we'll share as, Broadcom sees the cloud data center and IoT is their next revenue source. The VMware acquisition provides them immediate virtualization capabilities to support a lightweight IoT offering. Big concern for customers is what technology they will invest in and innovate, and which will be stripped off and sold. Interesting. I asked David Floyer to give me a back of napkin estimate for the following question. I said, David, if you're running mission critical applications on VMware, how much would it increase your operating cost moving those applications into the cloud? Or how much would it save? And he said, Dave, VMware's really easy to run. It can run any application pretty much anywhere, and you don't need an army of people to manage it. All your processes are tied to VMware, you're locked and loaded. Move that into the cloud and your operating cost would double by his estimates. Well, there you have it. Broadcom will pinpoint the optimal profit maximization strategy and raise prices to the point where customers say, you know what, we're still better off staying with VMware. And sadly, for many practitioners there aren't a lot of choices. You could move to the cloud and increase your cost for a lot of your applications. You could do it yourself with say Zen or OpenStack. Good luck with that. You could tap Nutanix. That will definitely work for some applications, but are you going to move your entire estate, your application portfolio to Nutanix? It's not likely. So you're going to pay more for VMware and that's the price you're going to pay for two decades of better IT. So our advice is get out ahead of this, do an application portfolio assessment. If you can move apps to the cloud for less, and you haven't yet, do it, start immediately. Definitely give Nutanix a call, but going to have to be selective as to what you actually can move, forget porting to OpenStack, or do it yourself Hypervisor, don't even go there. And start building new cloud native apps where it makes sense and let the VMware stuff go into manage decline. Let certain apps just die through attrition, shift your development resources to innovation in the cloud and build a brick wall around the stable apps with VMware. As Paul Maritz, the former CEO of VMware said, "We are building the software mainframe". Now marketing guys got a hold of that and said, Paul, stop saying that, but it's true. And with Broadcom's help that day we'll soon be here. That's it for today. Thanks to Stephanie Chan who helps research our topics for Breaking Analysis. Alex Myerson does the production and he also manages the Breaking Analysis podcast. Kristen Martin and Cheryl Knight help get the word out on social and thanks to Rob Hof, who was our editor in chief at siliconangle.com. Remember, these episodes are all available as podcast, wherever you listen, just search Breaking Analysis podcast. Check out ETRs website at etr.ai for all the survey action. We publish a full report every week on wikibon.com and siliconangle.com. You can email me directly at david.vellante@siliconangle.com. You can DM me at DVellante or comment on our LinkedIn posts. This is Dave Vellante for theCUBE Insights powered by ETR. Have a great week, stay safe, be well. And we'll see you next time. (upbeat music)

(upbeat music) >> Hey, welcome back to Las Vegas. Lisa Martin here, covering Coupa Insp!re 2022. theCUBE is really happy to be here at this event. About 2,500 folks are here, which is great to see. I have two guests from Microsoft with me. Please, welcome Jonathan Allen, the director of global network modeling design and planning, and Cassie Wang, senior global network model and design engineer. Guys, thanks so much for joining me today. >> No problem. Thanks Lisa for having us. >> Thank you. >> So let's talk about what's going on at Microsoft, the Microsoft supply chain. Supply chain is a term that's on everyone's lips these days for some interesting reason, but talk to me a little bit about the Microsoft supply chain and how does it scale to meet the needs of business? >> Yeah, Lisa, it's really an interesting design at Microsoft. When you look at all the products we service, from Xbox consoles, controllers, Xbox games, Xbox Live cards, service devices for retail customers, for consumer customers and commercial customers. And then the way we go to market through distributors, retailers, and direct to consumer homes, we have to have a supply chain that actually executes across all the products and customer needs based on seasonality. When you think about our products, Xbox console heavy Christmas, heavy consumer, heavy retail commercial devices for service, heavy quarter ends, heavy periods of time back to school. So, we have to have a supply chain that effectively works across all of our products, all of our customers, and all the differences analogies that we have to manage. >> And do so globally? >> And do so globally. >> So talk to me about the transformation. That's a word that we talk a lot about digital transformation, right? >> Yes. >> Before COVID, now we've seen the acceleration of digital transformation during COVID, we've seen challenges with the supply chain. Talk to me about Microsoft supply chain journey from a digitalization perspective, what you guys have gone through. >> Yeah, absolutely. Data is the key. And I have a philosophy which is around managing a business by facts and figures. And so, when Cassie first came on about a year and a half ago, our focus was on digitizing our supply chain. So how do you take our physical supply chain, digitize it in a way that you have a digital mapping and a duplication of what's happening physically in a digital way across the supply chain. So about every single day, we're grabbing in about 500 gigabytes of data, that then allows us to understand the physical and the virtual world of our supply chain, to understand how it's moving, how it's executing and how it's delivering. As for example, we were able to, when the war began in Ukraine, to understand where our trains were, how they were moving, and if they were continuing to move versus stopping. On the second side, we're leveraging that data now to make decisions about where our supply chain is today, which is really focused in the changing environments that are real time occurring. That's driving opportunities, whether it's about reducing carbon, whether it's driving cost down or whether it's servicing the customers to make real time decisions, while at the same time planning for three to five years out based on our growth, our projections, and making sure we'll have the right infrastructure partner supply chain in place to service with those changes in growth. >> Basically you need a crystal ball? >> Basically. >> Essentially? >> Yes. >> And Cassie, it sounds like from what Jonathan just said, you joined the team during the pandemic? >> Yes. >> So, during a time of massive change? >> Fully remote, yeah. Talk to me a little bit about that and some of the opportunities that you saw in helping the supply chain modernization. >> Yeah, definitely. So when I joined Microsoft, it's great time. And it's all the risks and challenges and dynamic changing environment that's really involved. So we spent a long time, like from the time I joined Microsoft, we spent the time to set up this digital chain of our supply chain. So really to transform what is happening physically to how do we see it digitally. So just to bring the visibility of the supply chain. So the great thing is we are able to leverage the tool from Coupa, the digital transformation and also supply chain design optimization tool to help us really build the digital twin, and also the model for Microsoft device supply chain. >> Now, interesting comment. So when I met Casie, the first time I met her, was in person when I interviewed her. Second time I met her in person was here at Coupa, and I was afraid I wouldn't recognize her. (all laughing) >> Of course, challenges of last year. Talk to me about speaking of challenges, talk to me about some of the challenges that Microsoft saw and said, "We need a partner like Coupa to help us eliminate these challenges. We don't have time. Real time is no longer nice to have. We've got to be able to transform, so we have that visibility in real time." >> Absolutely. When you think about time, time and decisions, overnight, cities get locked down in China, cities get locked down in Europe. And if you wait days or wait hours, that could be the difference between product on a boat, product on a plane, or product not arriving to support your customer needs. >> Right. And then the question is knowing that with that real time, how are you making decisions real time to change, to alternate airports? Making changes on the products you're making to make sure that, I was making this but now I should make this, because I have a risk of getting product to show. >> And you've got to do all that with very limited amount of time. And of course, cause there's the consumer. I mean, we think about the Microsoft on the business side but the consumer side, you mentioned some of the consumer products you don't offend the Xbox, the service consumers. One of the things that was really in short supply during the pandemic and probably still is to some degree, is patience. >> Yes. >> The consumer experience is so critical for a brand. >> Correct. >> And as is the employee experience. >> Yes. >> Talk to me a little bit about, from a supply chain digitization perspective, what was some of the executive sponsorships? Who were some of those executive sponsors that were involved in going, "Yeah, we need to move in this direction with Coupa, and it's got to be now."? >> The real supporter behind that is, my manager, Jeff Davidson, and then his leader, which is Donna Wharton, where they are truly about what are we doing next? How are we going to leverage the tools and the capabilities that are provided by others that allow us to do our job? So let's be clear on, let's use those that are designed to do what they're supposed to do, and then build where we need to. And that was the big difference, the digitization of the data, create the data, create the information so that we could then leverage the tools to create the information, right? And that information is then about bringing the facts, the information and the data forward, to have very fact-based conversations, which is back to manage the business by facts and figures. >> Right. Well, Cassie, one of the things that we've also learned in the last couple years, is that every company is a data company. If they're not a data company they're probably not going to be around. I even think of my grocery store and all that data that they have on me to be able to surface up. What did I buy last time, and I want to buy that again? Talk to me a little bit about why was Coupa the right choice to help facilitate this data strategy so that the visibility and the supply chain and the ability to tweak things on demand is there? >> Yeah. So, the main stuff that we are leveraging from Coupa are the data group and also the supply chain group. So data group enable us to really, for the people who do not have a intensive data manipulation backgrounds, they can use data group very straightfowardly to work on the data so they can build, they can grab the data transactional level and aggregate to the leadership level to see data in different aspects, tell the trends to get the key information. So that's the power of getting the massive data on a level that's like everybody can say, "Oh, wow! This is what it means." And another is definitely leveraging the data to get into a model, which is what we just talked about, the digital twin of our physical supply chain. So, we are able to like make analysis based on very easy design, like sensitive analysis, what-if analysis, to test out what our future supply chain can be. And what is the cost benefits? What is all the impacts on the on the lead times? On the carbons? So, yeah. So that's the power of leveraging the data. >> Speaking of carbons, how is Microsoft working towards being carbon negative, zero waste? What's some of the things that are going on there from a corporate responsibility perspective? >> Yeah, that's a really important one. As known about two years ago, we came out with a pledge to be carbon neutral by 2030. >> 2030. >> And so, the company as a whole is doing massive initiatives from different groups, but specifically in supply chain, we're constantly focusing on cutting our carbon footprint, whether it's the way we're making the products and designing the products, whether it's the way that we're designing our warehouses. So for example, just recently, we launched a Carbon Neutral DC in Europe, which is all solar panel based. We're about to do that as well in one of our US operations. We're working on other things that allow us to think about alternative pallets that eliminate the weight of wood, to a much lighter pallet that has a huge carbon reduction when you think about shipping things via the air and the carbon impact there. So, everything that we work on is really around three things; service, cost and sustainability. And our biggest objective is really taking all three of those objectives and trying to bring them closer to each other so that the decisions aren't as large against each other when you make one versus the other. That's our objective. So, how do we continue to move that ball forward, challenge the paradigms of the old, that we're so accustomed to and really move forward to changing? >> How does Coupa help with that? >> Oh, I can't say that, yeah. >> Yeah, so one of the actual dimensions, Microsoft our goal is to achieve carbon neutral by 2030. So traditionally, the trade off might be between cost and service, right? >> Okay. And now, the carbon is the most important priority. So the trade off, the balance, are between cost, service, time and carbon. So one of the great thing that Coupa can help us is in the network modeling. There is actually objective for lowering the carbon emissions. So that can be the top priority that you wanted to solve through your network modeling like in parallel to cost, to service. So you can just like very straightforwardly put more weight into carbon when you're making your decisions, like that can be a higher penalty cost when you have more carbon emissions. It's like a very straightforward way to translate the carbon goal into some quantifiable goal into the modeling and data. >> Jonathan, I'm curious from a Microsoft strategic partnership perspective, how important is it from Microsoft to partner with companies that have that strong commitment to help facilitate being carbon neutral by 2030, having a strong ESG initiative? >> It's critical. Microsoft for the most part is an outsourced supply chain in which we measure partners across the network. We have our partners run our distribution and centers, we have outsource manufacturing, we have outsourced logistics. And it's important that we're working with them about what their plans are, because they're just simply an extension of the Microsoft supply chain. >> Right. >> Right. They're not not just companies we work with, they're companies we partner with, to think about how can we change the future? What are the alternatives that we can do? How do we think about alternative fuels? How do we think about alternative shipping ways? How do we think about creating density in the network? So one of the biggest things when you really think about optimization is really around creating deensity. How do I create more with less, and make sure I'm taking, for every dollar spent, for every shipment made, I maximize it to its fullest, and leave no waste behind it? That's the goal. And so, partners challenging us is probably the most important piece because they're on the front line. They actually see our shipments, they see our loads, they see the work we're doing and how it's translating to their environment. And it's important that they give us that hard feedback back that allows us know where we're not meeting the bar. >> Got it. Cassie, you guys are giving a presentation in about a couple of hours. Talk to me about some of the things that the audience, like if you had to summarize the top three takeaways that the audience is going to learn from the top, what would they be? >> I think the first is sustainability. So we want everybody to know that this is the key mission for Microsoft. That's one of the priorities for the next eight years for Microsoft to achieve. And the second is just how Coupa can help us achieve that goal. And how do we leverage the the applications, the tools, the cutting edge technologies for us to achieve a sweet balance between sustainability and technology supplychain? >> I think one of the greatest things about conferences like this, is that Coupa is great with that customer centricity, is it the opportunity to hear from the voice of the customer? What challenges you had? Why you chose Coupa? How you resolved them? And that crystal ball that you talked about in terms of where we're going from here. I think that there's so much value. I'm sure in what you're going to share today with the audience. Jonathan, last question for you, for other folks in any industry that are about to embark on, or are in the midst of a supply chain, digital transformation, what's your advice? What recommendations would you give? >> For me, it's really about two things. First and foremost is about creating data. Focus on data, not an answer, not a conversation. What is the information that you require? And then the second piece about that is then how do you make sure you stitch it together? And how you create, whether it's manufacturing data, whether it's purchase order data, whether it's sales order data, whether it's shipment data, whatever it is, making sure that you can stitch end-to-end together, because each individual decision by itself, may be right, but could be wrong, because ultimately, it's about the decision for the whole, not the decision for the one. And then making sure you focus on the cultural change, which is around, it's just not my area, it's just not my thing, it's about the end, it's about the planet, it's about Microsoft, it's about the customer, it's about the future, and making sure you're really really focused on making that change, right? Not my change. >> Right, and Rob Bernstein even alluded to that a little bit this morning in his keynote talking about one of the things that Coupa breaks is silos. >> Yes. >> Organizations that, cause to your point, something might be really good for sales or operations, but not good for marketing or logistics, for example, need to be able to have that visibility across, but also another thing that Coupa is famous for is collaboration. >> Correct. >> Being able to enable that collaboration across lines of business, across teams, across partners. >> Yep. And an important statement of that is, when you think about change, think of it like a stream, right? Streams, they create pathways with persistence. When you believe in something and you're truly behind it, just stay the path, right? There'll be a time and a place, cause sometimes the decisions just aren't now, but they will become. There's a lot of things that, for example, myself and Cassie are constantly working on, that might not be right now, but they will be right in the future. And it takes sometimes, just the right opportunity, the right situation, but the key is making ysure you understand those things so when those opportunities present themselves, you can just step in. >> Yep. Another thing we've learned, I think in the last two years, I'm losing count, is it's not a matter of if, but when. >> Correct. >> And you can apply that general statement to pretty much anything these days. >> Absolutely. >> Guys, thank you so much for joining me talking about Microsoft's transformation of the supply chain, the digital twin that you've created. Have a great time in your session. I'm sure folks are going to learn a lot from you. >> Thank you very much. >> Thank you so much. >> All right, my pleasure. For Jonathan Allen and Cassie Wang, I'm Lisa Martin. You're watching the the CUBE's coverage of Coupa Insp!re 2022 from Las Vegas. Stick around, be right back with my next guest. (upbeat msuic)

(bright upbeat music) >> Hello, and welcome back to theCUBE's continuous coverage of AWS re:Invent 2021. I'm John Furrier your host of theCUBE wall-to-wall coverage, Sumit Dhawan president of VMware is joining me today. Sumit, welcome to theCUBE. >> Great to be here, John, good to see you. >> You know, I remember Raghu when we were talking to him when the original AWS deal, we covered it many, many years ago. It seems like yesterday, but since then, again, it was a lot of people who were kind of like looking at that deal, not understanding. We were very clear that we thought that that was going to create clarity. If you look at the success of VMware's cloud strategy, since that moment in time, it really has been an amazing run for VMware. And so congratulations and looking at that trajectory, we're going into what even a bigger wave now we're seeing, coming out of the pandemic with Edge, 5g, Cloud Native going mainstream. This is like another tipping point, another inflection. Well, how are we want to look at it? This is really big. Can you share your thoughts on how you see your customers and AWS customers coming together with the VMware. >> Yeah, we are excited about sort of this phase, era or whatever you want to call it, where customers are looking at just the power of cloud for all of their applications. And in fact, what we call multicloud, where they are looking at private cloud, public cloud, sometimes even multiple public clouds and Edge and how they are going to leverage all of this power of cloud across all their applications. And we're excited about the partnership, like you said, John, we did with AWS, customers have last two years, have had a hard time modernizing their infrastructure. And now they're looking at their tier one applications, which are oftentimes the lifeline of their businesses and they have not been, the infrastructure has not been modernized. And our partnership with AWS brings to the customers a fully modernized infrastructure as a service, which is optimized for their tier one application. So they can embrace the power of cloud, not just for new modern applications that they have built for running their new digital services, but also all of their tier one enterprise applications instantly modernize their infrastructure, secure it run their tier one applications through the power and the scale of public cloud. And then gradually start modernizing, like you mentioned, modernization of application is a key element and we have provided a rich stack for customers to be able to build their new SRE and DevOps practices and enable developers to have a fast journey to build these modern applications, leveraging the power of public cloud and in fact multiple public clouds seamlessly, and we're extending the same thing to the Edge. So it's actually exciting times in the industry. We call it the multicloud era and VMware is enabling our customers what we call smartest path to cloud. >> Well, congratulations, first of all, on the new independent company, VMware, that's great news. You guys now are on your own very valuable company in and of itself, under Dell Technologies now out on the open and we've been covering VMware, theCube's been to VMware every year. And looking at this year's VMware and looking at VMware for the old folks, the veterans VMware has been synonymous with operations, IT operations, running workloads in data centers to power business, enterprise classic innovation for business value. Now with the cloud, you see operations DevOps being discussed in security. You're talking about, and you mentioned SRE the workloads. The game is still the same, but it is shifting landscape wise. You got cloud scale, you mentioned on premises and multi-cloud. So with operations going to full scale, your customers are building and running their businesses on VMware and AWS and other clouds. This is the same game, but different world. Can you just share what's the current similarities and differences from where operations used to be from a workload standpoint. >> John, you're a hundred percent, right. The need for operational scale and discipline is always, there has always been there and now it's extended to potentially lot more complex world of what we call multicloud. In this new world, the whole aspect of operations is no longer the world of system admins, where you would have people pushing buttons to control the infrastructure and it's lot more where infrastructure is now designed to be managed as a code. There is a lot more of what is considered shift left, where more and more of power of orchestrating the infrastructure as given to the developers because they're oftentimes the sort of ones who understand the business logic and understand how the infrastructure is required to scale up and down the applications. And so along those two key trends, there is still a critical element of how a platform is needed for customers to operate that environment okay. You can't sort of have operational discipline be lost just because you have the paradigm changed and that's what VMware is enabling now with VMware stack, you can manage your entire infrastructure, not just public cloud, but even private cloud as a code, you can create a platform where developers get this freedom and a great experience to leverage any public cloud, to build their services and work closely with DevOps and SRE functions, to make sure that the orchestration of all of their cloud environment in a multicloud environment is available and enabled seamlessly through Kubernetes. This doesn't have to be done through virtual machines anymore it could be virtual machines or Kubernetes orchestrated containers across all clouds. And so bottom line operations has always been critical, but it has been done in a certain way in the world of multicloud it's changed to where it's more and more of infrastructure as a service shift left to developers and cybersecurity is extremely important where it needs to be built into the platform. And that's what VMware solutions are now enabling for our customers. >> Yeah, and for all the young guns coming into the business that have developers, the DevOps is still the same game. You've got developers and you've got operations now at large scale. And I think this whole multi-cloud is really kind of the multi-vendor equation so I think clear synergies and congratulations on the trajectory. I think it's really relevant. Can you take us through on how this means for the businesses, because at VMWorld this year, you guys talked about cross-cloud services. Can you talk about what that is and what does it mean for the customers, and what's the focus at reInvent this year? >> Yeah, so VMware this year at VMworld announced our sort of portfolio for enabling customers to embrace the power of multicloud easily. We call it cross-cloud services and they fit into five major categories. First is our cloud infrastructure that is available through partnership with all major cloud providers. We started with AWS and we expanded with all major cloud providers, including Azure, Google, Ali in China, Oracle, IBM. Secondly, our cloud native platform, Cloud native platform is where it doesn't have to be traditional VM based applications, applications built using modern cloud native technologies container-based, or that can be orchestrated using Kubernetes that are operationalized using our platform where customers can get any Kubernetes on any public cloud and operate them in a consistent and scalable fashion and enable a great developer experience at the same time. Third is networking and security services, which are underlay across both the cloud infrastructure, as well as cloud native services for this cloud management, how infrastructure as a code and shift-left developer function can be enabled through our management technologies designed for both private and public cloud, both VM based or VMware based infrastructure, as well as native public cloud infrastructure. And then lastly, at workspace and Edge services, enabling customers to build today's requirements of people working from anywhere and anywhere workspace experience for a hybrid workforce. So these are our five cloud services, John, that we call collectively as cross-cloud services, which enable customers to embrace the power of multicloud easily. These are modular, easy to acquire services designed to run across all clouds. And obviously for customers looking at leveraging the power of AWS, these services enable you to embrace it AWS at the fastest speed. >> Yeah and I think anything cross-cloud, multi-cloud, the ease of use and choice is key, you have to have choice that's cool. Open source is driving a lot of that, which I want to get to with the Tanzu, but you guys have had a great partnership with AWS, both on a development level, as well as a business partnership. Take us through the evolution of the partnership between VMware and AWS, because I know Raghu was really into this with Pat Gelsinger and then Andy Jassy, we covered that. But if you look at what Amazon web services is doing under Adam's leadership now they're going to set the table for the next 15 years. And you've got Outpost is going to be a big part of that. You've got all of the cloud native high level services inside the cloud, inside AWS as well. So take us through your view of the evolution of the VMware AWS partnership. >> Yeah I mean, AWS and VMware started a partnership for those of you who don't know, we started our partnership about five years ago, where we announced the availability of VMware cloud on AWS, which is all of our fully sort of modernized software defined data centers infrastructure available for running tear one enterprise applications on top of AWS all of their data centers globally. So our software with AWS hardware together as a managed service means customers could get fully modern infrastructure without refactoring any of their applications. They can run on AWS. And that relationship has grown significantly. We have continued to enable more and more of sort of different sized sort of platform infrastructure that we have continually made available. And the business has led to great success. We have at this point in time thousands of customers, joint customers running all of their tier one business applications, whether it's banking to healthcare, to insurance on top of our infrastructure, and it's been great. We then gradually expanded that partnership to other industries. Now we have customers in telcos running major telco cloud on top of our platform, we've expanded our partnership to other solutions. We brought our Tanzu, which is our cloud native platform for managing native cloud services on AWS, in an enterprise fashion, connected to all of their enterprise requirements as well in the marketplace we have brought other offerings, including security services on AWS marketplace for customers to get so over time. >> Hold on Sumit if you don't mind me asking, so you saying that Tanzu Carbon Black and VMware cloud are all in AWS marketplace. >> They're all available in AWS marketplace and they're all available to be transacted through even just the AWS's EDP. So the commercial relationship with AWS has strengthened significantly over time. >> EDP is their sales channel that's their direct. >> EDP is their enterprise agreement that's right. >> So you go to market together with AWS under the marketplace. >> Joint support integration so their customers can get joint support with us. So over time, the technology integration that started has led to strong commercial integrations, helping making sure customers can get one commercial agreement and one support agreement with VMware and AWS together. And that's been great for customers, customers have loved it and we are continuing to build upon it. Your second question was, well, what happens when AWS has new modern native services? And what we have done is for example, at Tanzu Solution, it is integrated with AWS's EKS. So their Kubernetes distribution can be fully operationalized as well as a great developer experience can be created for AWS native services using VMware Tanzu solution. So we are embracing the power of more and more of AWS services for our enterprise solutions. >> You know I love following VMware, especially and AWS. I spoke to companies, both very technical, pragmatic, very smart companies So congratulations on success. I got to ask you from a customer perspective, as you look at the landscape of the commercial side, what are the customers saying? What's the big summary of where they're at? What's the vibe, where's their head, what are they thinking? Take us through some anecdotal customer sentiment or data. >> Yeah, our customers tell us three things consistently. Number one, they say that they have, at this point of time, just decided that they're going to have some kind of a black solution, which will span multiple clouds, which could have public cloud, private cloud and Edge or multiple public clouds. In fact, we just did a recent survey, John and we found that 74% of our customers are already using multiple clouds. And 90 plus percent said that they want that freedom and choice to be able to use cloud of their choice and not be encumbered by any particular sort of just choice that they make. So that's the first trend we see, secondly, customers want to modernize their infrastructure and modernize their applications. They haven't been able to do so over the course of last two years, and modernization is a key requirement and VMware and AWS gives them that ability to do so now at this point in time, very, very quickly. And then third thing we hear is that customers are looking for some solution where cybersecurity is built in it's something where they are standardizing their enterprise requirements via a platform, which has a great experience for the developers, great operational scale and cybersecurity. And these are the three trends John, that VMware is solely focused on as part of our services and solutions and our partnership with AWS. >> Sumit, always great to talk to you. One final point. I want to get your reaction to a VMware has made a couple of big bets in the past decade. One, the deal with Amazon, which opened the door for multicloud, that path is clear. Cloud-scale check the box well done. And the other one was cloud native technologies and Kubernetes specifically, two big bets that don't, that kind of no one kind of saw coming, turns out they turned out pretty well. What's your reaction to that? Would you agree? And how would you talk about those two events? >> Yeah, we at VMware always considered sort of how we are going to keep innovating and the way we see the world is follow where the applications are going. It's pretty simple. Okay we saw that a few years ago where cloud and container technologies are where the applications are going. And we innovated through both our organic investments, as well as inorganic investments to bring our VMware cloud Solutions and Tanzu Solutions. And similarly, John, we're looking at now the next generation of applications where we fast forward three years down the road, we envision a great degree of innovation is going to happen in the Edge. And that's the third sort of area of innovation for us. So that public cloud or multi-cloud cloud native applications, as well as Edge applications can all be orchestrated using VMware's cross-cloud services. >> Sumit Dhawan, president of VMware thanks for coming on theCUBE we appreciate it. Enjoy the rest of the event. I'm John Furrier host of theCUBE. Thanks for watching. (bright upbeat music)

(Music) >> Welcome to the AWS executive summit presented by Accenture at AWS reinvent 2021. I'm Lisa Martin, and I've got two Cube alum here with me, please welcome Merim Becirovic, Managing Director of Global IT Enterprise Architecture at Accenture and Chris Wegmann, Accenture, AWS Business Group technology and practices, Senior Managing Director, gentlemen, welcome back to the program. >> Thank you, Lisa, great to be back. >> Thank you, Lisa. Great to be here. >> It is nice to be back in a way right here we are at this hybrid event, but we want to talk about what Accenture is doing with its, with AWS to serving its clients. And then we're going to get into your own internal use case, drinking your own champagne. Chris go ahead and start with you, talk to us about what Accenture is doing with AWS to serve its clients. >> Yeah, Lisa, it's exciting, as you said to be back in this hybrid event and you know, for me, this will be my 10th re-invent and for Accenture we're in year 14 of our partnership with AWS and actually year six of our partnership called Accenture AWS business group. And you know, the focus over the last year has been helping our clients come out of the pandemic stronger than, than where they started. Right? And a lot of that has been around focusing our customers, getting past cloud migration, past cloud modernization, and getting further into what we now call the cloud continuum, starting to truly leverage all the AWS assets and capabilities and services to, to truly speed their transformation. You know, we work with a lot of our customers who are needing to transform even faster today than they were before the pandemic. And, you know, we're focused on helping those customers do that with AWS services. >> So Merim, let's bring you into the conversation. Now Accenture's internal IT organization has been leveraging AWS and public cloud for a while. Talk to me about that you completed the journey a couple of years ago, 95% in the cloud. Talk to me about what you're doing there. >> Sure. Lisa, so our, our journey into the public cloud is complete. As you said, we put a bow on that project a couple of years ago. We started in 2015 and we went all in on public cloud. So we, the number 95%, 95% represents a true measure of everything it takes to run Accenture. Everything addressable is in the public cloud today. So the 95% just represents a small component of things that have to live outside of the cloud. But other than that, our journey to the cloud is complete, and we are very happy being in the cloud because it has opened tremendous doors for us as a business. I'm sure we'll talk about here as we go, but it's fundamentally a different place we live in today and where we were before we were in the cloud. >> Merim, you said something really powerful there a second ago. The Accenture's journey to the cloud is complete. I don't think I'd ever heard anybody say that. Talk to me about the impact, especially during the last 18 months that that cloud journey is delivered. >> I mean, one of the things I am extremely proud of for our collective global teams around the world, when the, obviously the, you know, when COVID hit and the pandemic engulf the world, the only difference for us was that people just did not come into an office to work. Our capabilities in the cloud, our capabilities of having everything in the cloud really made it that much easier for our people to go to work. We weren't fighting over resources around infrastructure. People could just work from home directly. So I'm extremely proud of the collective global team that made all of that happen as part of that execution of all those things. So it was really a very proud moment, I would say for all of us running IT. >> As well, it should be. Chris, talk about that from your perspective of facilitating that massive pivot 18, 19 months ago, and what your group was responsible for doing to enable this cloud journey to be complete. >> Yeah. I always laughed at, you know, Merim and our internal CIO organizations, we call it was our first customer, right. You know, way back when I started working in this partnership, you know, we were already starting to leverage AWS, S3 and EC2, and that insight Accenture, and we took a lot of those best practices and started helping, our clients leverages best practices. So, you know, from an Accenture, we always kind of harvest from internally what we're doing, but, you know, over the last several years, we really are our focused with the CIO organization, Merim's organization has been, you know, expanding the usage of non, you know, I, as I call Maya services, right? So past EC2, you know, past S3. Obviously there's always storage. There's always compute, but you know, truly doing and building serverless applications, truly using, you know, services, fully managed services. So, you know, the CIO organization doesn't have to spend their time doing that. And, for our customers, that's while it's, they're still early on in a lot of their journeys, that's a novel idea is a truly try to sunset IS services or EC2 and things like that, you know, and whether that's, you know, fix some containerization or things like that, I think the other big part is, is the maturing security footprint, right? Obviously, as you use one or more of these AWS services, your security posture, your presence, how you think about security. We created an asset called secure cloud foundation, leveraging many of the AWS services in the security space that have come out like guard duty and others really to help make that security foundation stronger, make it easier for our customers, including CIO to leverage those services and truly enable that move further up the cloud or further down the continuum as we call it. >> Merim, I want to get your thoughts on security from in a, because we have seen such a dramatic change in the threat landscape in the last 18, 19 months. We've seen a huge spike in ransomware. It's getting much more personal. It's now a household word. We've got the executive order. We had this rapid pivot to and hundreds of thousands of Accenture employees working from home. Talk to me about, you feel very confident in the cloud during that you didn't word where's your competence from a security perspective. >> As you said, security is the fastest growth in our business. Collectively, like you said, the bad guys don't sleep. We don't sleep either when it comes to security. One of the things that we're constantly thinking about is how do we turn on a lot of our capabilities as an example. So even, I would say at an enterprise level, it's different when you're running a big multinational corporation, 650,000 people like we do. We can't just turn everything on and hope for the best. We are very scripted in terms of how we think about those services, how we think about the processes, how we work with our CSO organization, so that we're very meticulous and very thorough in terms of what services we turn on, how we turn them on, when we turn them on? How long we make them available, because this is, this is the new world, right? We have extended our corporate structure out into the cloud. That means we have to think of different ways for how we want to consume those capabilities and services. So like Chris said, you know, the, the journey to the cloud for us is complete. A lot of it was I, as I would tell you, a lot of it was lift and shift for less. And we can talk about that if we get time, but it was more about getting into the cloud and taking advantage of the cloud where we are today, because now that we're there, we get to take advantage of all those capabilities that are there. And I would say the best part of being with on, in, in the cloud is also having the, the providers like AWS they are with us, helping us with that security posture. So it's not just us doing this by ourselves. >> So Chris, I want to talk about that Merim just said, this was mostly lift and shift. Talk to us about that. Cause when we talk to organizations in every industry, the cloud transition, the cloud journey is extremely challenging. It's complex. How did you do this? How did you facilitate this and in a relatively short time period, Chris? >> Yeah. And, and you're right. Everyone has conversations I have with my clients. You know, there's a huge debate whether to lift and shift or modernize or build new build cloud native, right? So, you know, in Accenture's situation, you know, very early on, it was identified that we can, we can do a large savings by doing a lift and shift migration, right. We were not a big data center owner, right. That wasn't, we're not a big capital intense organization. So for us, that, that journey we had, you know, colos and that stuff coming up for renewal. And we knew that we could, you know, get some early savings there and really, you know, reduce our footprint and take that investment and then invest it into, you know, true modernization. So Merim and his organization worked very closely to build the factory, to do the migrations, get that done in a very short amount of time and then turn their attention on truly refactoring rebuilding the applications. I'm super proud of the number of applications that we've rebuilt. I'm super proud of the number of applications that, that now are cloud native. And we live in these applications every day. You know, they they're everything from our performance to how we do our payroll and do our time charging and things like that. But which, you know, it was a big reason why, you know, we can access our systems remotely and at home versus going into different systems to get to that stuff. So, you know, it was very much heavily lift and shift early, then really focusing on modernization. And as Merim said, getting, you know, now it's about living there and continuing, continuing to modernize, continuing to accelerate what we're doing in the cloud. >> Yeah. Lisa, its little bit like, so our journey lift and shift was a core component of it. But the minute we decided to go to the cloud, one of the things, the first things we did, as I said, no more vans. So any new capability that we were going to build, we were going to build a cloud native micro-services based, and that's been our standard for the last 3 or 4 years ago. So any new capability that comes along today that we must do custom, we build a cloud native microservices because one of the other things that I've got on my plate is I'm trying to reduce our overall technical debt. So all of these IS platforms, I still have to maintain them, patch them, support them, upgrade them. And I would rather be much more efficient at doing those things as, as I can and reinvest money into refactoring and modernizing the rest of the application, plead through containers through microservices, et cetera, which then gives me the agility right back to actually go even faster, to enable more services for the business. >> Speed is something that we've seen become even more critical in the last 18, 19 months where we needed to everybody pivot businesses multiple times over and over. But part of the challenge there Merim, I want to get your thoughts on this is they are something cultural shift. Talk to me about, you've been at Accenture for a long time. Talk to me about the cultural shift needed to facilitate this massive transformation to cloud and how Chris's team was a facilitator of that. >> So, you know, one of the things for us, I have probably in the last five years spoken to a thousand of our clients, around our cloud journey and this culture conversation always comes up and I will say, you know, the biggest thing for us was interesting. We had those same fears. We had some same in when we first talked about going to the cloud, you know, six years ago, it was very, not everything was there, that's there today. So the teams were extremely nervous and they were confident that we could never be as, as good in the cloud as we were on, on site. Yet here we are six years later and we're constantly finding ways to add value and take, bring value back. And though, it's so same teams. And one of the things is just, we gave them the challenge to say, Hey, this is the future. We're telling our clients, this is where we're going. We have an opportunity here to do something different and they took it and the team really took it on. And they said, okay, let's do it. And they act, and we looked at how we run into cloud the many different ways, whether we're using reserved instances, whether we're using containers, whether we're using, you know, different computer capabilities, we went through all of it and we're running such a highly efficient machine right now that it's like, we're still able to continue to eat out savings even five years after the program. Even two years after the program is complete, we're still able to get savings. >> That's outstanding. That's ROI that every business and every industry hopes to be able to achieve from this. I want to switch gears a little bit now because this is actually pretty cool. Accenture is really focused also on sustainability. You guys have signed onto the Amazon climate pledge, which if you don't know what the Amazon climate pledge, and this is back in 2019, Amazon, co-founded this a commitment to be net zero carbon across businesses by 2040, which is actually 10 years ahead of the Paris agreement. You're in talk to us about that. And from Accenture's perspective, why it was important to sign on to that. >> So on a, on a personal level, I love obviously sustainability as a whole, that I think about the world park for my children that are growing up. So it's very important to me on a personal level as well. But I would say at a company level, what I love about the cloud is I am there right there with them as they make investments. All of our enterprise capabilities are there. We are able to very quickly shift and use those capabilities. So as Amazon, for example, in this scenario creates new capabilities, new compute offerings, new, new storage offerings, whatever it may be. They're doing it with a sustainability lens and me by being in the cloud already, I can then turn to start using those things too. So as much as I can, on that perspective, I'm in a great place with, as Amazon puts these sustainability capabilities out there, I'm right there consuming and making them more efficient. And then the other one is obviously as much of our workloads, as we can get to a cloud native perspective, microservices perspective, then we keep reducing that compute consumption and everything else that goes along with it. And lastly, I would say, you know, the, the other thing is we're very aggressive in managing all of our systems in terms of uptime. So for example, in a data center, most, most organizations don't think about turning off their development environments and everything else. But for us, we're very rigid in this process. And we have a, we have a target of all of our development environments being down 55% of the time. And primarily that's also a sustainability play in addition to a financial savings plan. >> Awesome. Great stuff, Chris, last question for you, as we wrap up here, what are some of the things that you were excited about that's coming in cloud in the next few years? Obviously here we are at, re-invent going to be hearing a lot of news, a lot of announcements about cloud in the coming days. What excites you most, Chris? >> Yeah. You know, obviously the machine learning and AI stuff is, is always the most exciting things right now in cloud. And, you know, we've put a lot of those to use here inside of Accenture as well. And, and our, you know, in our synopsis platform, which we use with our customers to run in a more intelligent operations, we use that internally as well. But you know, one of the things that excites me the most is the continued innovation at the core. Right. And you know, whether that be, you know, chip sets, you know, Merim talked a little bit about, you know, improvement and performance improvement and power consumption, you know, grabbing time, those types of stuff that, that excites me every year, I look forward to seeing what, what they come out with and, and then how we're going to put that to use. >> Well, I look forward to talking to you guys next year, you've done such a tremendous job. You should be proud of the massive transformation that you've done. I imagine this is, would be a great case study. If it's not already written up, it should be. It's really impressive. Merim and Chris, thank you for joining me at the summit. Talking to me about what's going on with Accenture and AWS and some of the things that you are looking forward to, we appreciate your insights and your time. >> Thanks, Lisa. >> Thanks, Lisa. >> You're welcome for my guests. I'm Lisa Martin. This is the AWS executive summit presented by Accenture at AWS reinvent 2021. (Music)

(bright music) >> Welcome back to theCUBE's coverage of AWS re:Invent 2021. I'm John Furrier, your host of theCUBE. We have Michael D´aniello, platform architect at VMware's Carbon Black. Michael, great to see you. We're here at re-Invent virtual hybrid in person. Great to have you on theCUBE. Thanks for coming on. >> Yeah, thanks a lot. Glad to be here. >> So one of the big stories that we're tracking, obviously, is workloads. All cloud for all workloads. Obviously the data is a big part of things, but under the covers and optimizing cloud for the application developers, this modern application movement is more and more at the top of the stack. People just wanting to code. Infrastructure as code. You've seen DevSecOps is a big trend that's driving all new microservices, all new greatness for developers, but still, there's an optimization question. I want to get your thoughts on this, is what you do. Take a minute to explain what your role is at Carbon Black around this cloud optimization. >> Yeah, absolutely. Yeah, so my name is Michael D'aniello. I am a platform architect of VMware Carbon Black. I work across all the different engineering teams. And our main objective is to develop scalable platform tools and that includes, yeah, cloud security, automation pieces, pipelines, cost optimization, like we'll be talking about today, developer enablement tooling and observability tooling. >> One of the big things about instances is that, you know, do I have enough instances? 'Cause honestly, the elastic cloud is amazing, all kinds of new resources there, but talk about the AMD portion of the instances. How do we identify these instances? How to developers understand it, what's in them, and what's the selection criteria? Take us through that whole process of the Amazon web service and the AMD instances. >> Yeah, sure. So essentially, we're leveraging a lot of our instances to run our EKS clusters, which is a managed service for me and for us to run our Kubernetes clusters. And we identify that we can take a bunch of those instances and gain some cost optimization benefits by selecting from Intel to AMD processors. And, you know, initially, we had measured out to be roughly a 10% reduction in cost just for selecting that instance type. But yeah, we actually learned we gained quite a bit more, so. >> John: You know, developers are always like, I want more power, and this is what, you know, the whole idea of Cloud is. Cloud scale has been a big competitive advantage, but also the cost aspect of it. What's the balance between maximizing performance and cost optimization? Because now, you know, people don't want to, you know, they want more power. They also don't want to have a lot of extra spend. And this is kind of one of those things they talk about in Cloud where it's been so successful, cost is important. >> Yeah, yeah, for sure. And it's got to be easy, too, to get that cost optimization benefit. Otherwise, you're spending all your cycles and burning that money there in the human capital and the team and the engineering effort. So luckily, this change is a one-line change. We use Terraform for our automated provisioning, a layer, and we were able to make that one line change and then developers didn't have to make any application changes, which was great. So it was a no-brainer for us to pursue this. >> Talk about the EC2 instances that leverage AMD based process for the EKS, you mentioned that earlier, what is that all about? What's the benefits, what's in it for you guys? >> Yeah, for sure. So essentially, the workloads that are running on these instance types are actual Carbon Black Cloud application. So, all the backend systems that support our customers. And so in that use case, we're, you know, we're spinning up all of our containers that are running our applications and essentially, that's our use case for those instance types. >> How did you come to use the AWS EC2 instances on the AMD? Did you have an evaluation process? Did you just go select it? I mean, take us through that migration aspect of it. >> Yeah, sure, yeah. So originally, we're looking across the board. How can we do better cost optimization, right? And that goes across every different AWS resource, but we targeted this one specifically. We worked alongside with their AWS TAMs and representatives to basically find out, "Hey, is this financially worth the effort?" And we did reach that conclusion with some analysis, basically targeting these instance types and doing some analysis on that cost optimization specifically. And it ended up, you know, being the right thing to target. >> What was the ease of use of the switch? Take us through that. Was it a heavy lift? Was it seamless? Take us through the impact, there, on the move over and what were the results of that? >> Yeah, so I mean, that's the greatest thing. Like I said before, I mean, we had to make just a single line change just to change that instance type in our config and then roll that out across our regions. We did slow roll that in order to make sure that those changes in our development environments didn't make any, you know, performance hits or we didn't run into any snags with the applications themselves. But yeah, I mean, that's the greatest part about the story from my perspective is the ease to migrate over and to switch to these instance types, and then you just immediately gain that cost optimization benefit. >> You know what I love about what your job is, platform architect, that word kind of had a lot of meaning even 10, 15 years ago, but now with the Cloud, it's almost like you're always finagling and managing and massaging and nurturing the infrastructure to enable it. More new things are coming online as well, more high level services. So you've got a fun job and it's always evolving. How do you stay on top of it? What's the impact been for your customers, too, as you start deploying some of these new instance capabilities? Take us through kind of a day in the life of what you do and then what's the impact of customers? >> Yeah, sure. So, you know, like you said, there's quite a bit now to look at. You know, you got to stay on top of different blogs and keep connected with your network to see what your other colleagues are doing across different companies. You know, you can go into conferences like AWS re:Invent, right, to keep on the cutting edge here. But yeah, that's essentially, you know, one of the key aspects is just trying to look at all the different aspects, all the new technologies that are coming out, making sure you're making the right choices there and trying to get the most bang for your buck while you're at it. >> What are some of the big factors that you see in cloud native as you start to look at what customers are doing? Obviously with Kubernetes, you're starting to see that platform develop inside the industry as well as de facto, kind of orchestration layer. But now as customers start to look at it, they want to have more ease of use there, too. At the same time, they don't want to have to do a lot of front end work. They want to get instant benefits in the Cloud, obviously, whether it's from a security standpoint or just rolling out a modern application. Okay, so as having all this infrastructure under the covers, how do you look at that problem and how do you capture that opportunity? >> Yeah, and I think that's why we're seeing a movement here on platform teams. It's kind of a newer terminology, usually a band of developers and SREs come together and say, "Well, we've got a lot of different things to look at. We're onboarding applications to Kubernetes, and we need to make tools so that developers don't have to think much about the transition and the underlying platform." And so that's one of our success metrics on the platform engineering team is just to almost, you know, be non-existent, right? To just have everything flow through our systems and then have just a high ease of use to onboard the applications to the new platform. >> You know, it looks like you have some great success with the AMD based instances. Can I ask you a question? 'Cause I wanted figure this out. How do you identify an AMD based instance when you're making the selections? >> Yeah, sure. It's as easy as just the A after the name. So for us, it was the C5.4XL. And if you want the AMD one, it's just the C5A.4XL. So I guess technically, instead of a one line change, it's actually a one letter change. So, quite easy there. >> Yeah, it's almost like back in the old glory days of command line, one quick update. The customer aspect of this is also important, too. If you don't mind, while I got you here, what are some of the things that you're hearing from your customers, from a performance standpoint, that they're looking for? Obviously, the cost optimization is key, but as they look to deploy more power and more performance, what are some of the things that your customers are looking for from Carbon Black? >> Yeah, so I mean, we are a security company, but we're really a data company because we have, you know, 8,000 customers, we processed over a trillion events per day, we ingress over a hundred terabytes of data per day. And so, our customers need high level performance. And if we can't provide that with low latency, we're not successful. So that's why, you know, performance on the underlying systems that are running our applications is super critical. >> Yeah, you're looking at trailblazer over there. I mean, the work that you guys are doing with the data is amazing. And that's a big theme at re:Invent this year is that data is a huge part. We look at the success of the cloud growth on this, I call gen-two cloud, happening. This whole modern movement is all about how people handle the data at scale, 'cause cloud scales here and now you've got processing all that data, The trailblazing that's going on, there's like this new wave of, I almost called it first-generation trailblazers, but you guys are doing that. What advice would you have for other architects out there and kind of the mainstream enterprises who are like, "Hey, I want to take advantage of the path that you guys have plowed through." What's your advice? >> Yeah, I think one of the key things in a place where we've had a lot of success is creating standards, making sure that we're choosing technology wisely, and making sure that your company isn't building the same solution in silos. And you know, that's a huge pattern that I've seen in my career. And if you can negate that, you're going to be in a great place. So, you know, choose the right technology, container first, cloud native first, push forward, and then make sure that everybody's kind of on that same ship running in the same direction. >> Well, great case study on this AMD based instance migration. Was there any uplift and experience that you've seen on the switch and the performance? Can you just talk about that? What does it mean to upgrade? What benefits are you seeing on the performance you have? >> Yeah, so I didn't hit on this yet and I really wanted to. Yeah, so upfront, the instance itself is 10% cheaper. However, we found out that we had to run far less instances because of that performance increase. So we ended up saving roughly 30% and we've continued to scale out. So at first, it was a couple of hundred instances. Now we're in the thousands and we're going to keep ramping up to over 10 thousands, tens of that. >> John: Let me get this right. So single line change, letter change, instance change. So you get not as many instances, and you save money, so you get cost optimization and higher performance. >> Yep. They say, if it's too good to be true, it's not. But in this case, it actually is. >> So why is it so good in your opinion? What did you discover? What was the big revelation that went down this path? Because that's good value proposition. >> Yeah, for sure. I mean, so initially, we were just chasing that initial BC to 10% and then as we kind of push it forward, we're looking at the metrics, month to month costs and we're actually saying, well, as we kind of swap over from one instance type to another, we're actually paying less. And then once we fully swapped over, it took five or six months to get to the same amount of costs as we continued to scale upward. So it's been a great story. >> It is a great story. It's super nuanced, but it's super important to know these platform benefits. I got to ask you on a personal question, if you don't mind. We love covering Cloud. We've been covering Amazon, it's our ninth year at re:Invent. Just love covering all the action and tech as this just total awesomeness environment. Cloud scale, innovation, capabilities, it's like surfing a big wave. But there's a bigger wave coming and we're seeing it now. I want to get your thoughts on this. As you look to the next big wave, beyond Cloud now, Cloud scale, data, new architecture is rolling out with Edge, basically distributing computing at large scale, and tons of security challenges, right? How do you look at this next big wave coming? Are you staring at it saying, wow, this is going to be huge? And how do you ride that wave? What's your mindset and how do you look at that? >> Well first of all, I'm extremely excited about it. Just the further this thing grows out, there's definitely more complexity, but just a whole slew of fun problems to solve. But when we look at these different problems and solving them at scale across multiple regions, it gets pretty exciting, right? So I can say one example of this is our security of our Cloud, not the security product, and we've developed automation for prevention and auto-remediation in our pipelines. It's been such a success story. And these type of technologies did not exist even a couple of years ago and we've been able to take advantage of them. So, there's going to be a lot more of that where that came from. So, yeah. >> Michael, great work. And again, you're truly a trailblazer, and this is, again, you got to do it. You got to screw your own cloud and stay on the cutting edge and ride that wave. Congratulations on the CostOp cloud optimization and the success with AMD based instances. Congratulations. Thanks. >> Thanks. >> Okay, this is theCUBEs coverage of AWS's re:Invent 2021. I'm John Furrier, your host of theCUBE. Thanks for watching. (inspirational music)