(gentle music) >> Good afternoon, cloud community and welcome back to fabulous Las Vegas, Nevada. We are at AWS re:Invent. It's our fourth day, it's in the afternoon. We've got two more segments left. This is a serious marathon, but it's so exciting, it's kept my brain super curious. I'm Savannah Peterson, joined by Paul Gillan today. Paul- >> Hello Savannah. >> Are you as excited about how much we've learned this week as I am? >> I am. It's just taking, my mind is just bursting with all the new information I've absorbed over the last three days. Amazing talking to all these smart people. >> It has really been so cool. >> And learning about all the permutations that we to think about cloud but there are so many businesses that have been built around the cloud, around making the cloud easier to use, supporting cloud as our next guest can talk about, that there's this whole ecosystem element that we don't hear about so much, but it's very much the foundation of the people who are here. >> Speaking of ecosystem, our next guest, please welcome Garrett to the show. Runs Ecosystem for Console Connect. How you doing Eric? >> I'm doing very well. >> Savannah: Garrett, sorry. Excuse me. >> No worries. >> Few names on the show today. >> Garrett: I'm sure. >> I do know your name, my mouth just doesn't want to, just doesn't want to participate today. Have you had a great show so far? >> It's been fantastic. You know, the AWS re:Invent show has always been a fantastic event, so. >> You're a veteran. You're also a CUBE alumni, which is great. >> Yes. Thank you for having me back. Thank you for your time. I most appreciated it. >> Yeah. We love having you. It's going to be great. We'll, we'll try and do even better each time we have you on the show. So just in case those listening are unfamiliar with Console Connect, give us the pitch. >> Okay, so Console Connect is our software defined interconnect platform. We also provide what we call network as a service. This allows our customers and partners to take advantage of our global private network on a pay as you go basis. Scalable and flexible. When you're not using the service, you can turn it off. So you only pay as you go. >> What a novel idea. >> Yes, yes. In the past you would have to have a year or multi-year contract. So we're making our services match cloud offerings around the world. The platform itself is in more than a thousand data centers all around the globe. >> Savannah: Just a couple. >> Yes, just a few. We have about 45 terabits of network behind it. It's all on our private network, so none of it's accessible via the public internet and we have a meeting place which allows our existing customers and partners to reach out across the platform and share services. So one customer needs to subscribe to another customer services, they can do so right across the platform on a pay as to go basis. So it's been very exciting for us. It's been very fast, it seems to me, for the past five or six years that we've had the service. >> At what point in their cloud journey do customers typically realize they need a service like yours? If the bandwidth they're getting, their native bandwidth they're getting is insufficient. >> Yeah, and I think that's a great question. I think the customers themselves have seen a serious disconnect between their direct connections to the cloud service providers where the cloud service providers are billing by the minute. And a traditional telecommunications connection is built by the year or multi years and then you really lose control over your cloud connection when you forget about it, right? Because service is always up. The connection's always up. >> Yeah. >> And a lot of individuals in a company may have access to the cloud, that cloud service, provider service. And next thing you know, you have a runaway group of services that are running that you're paying for and you don't really realize it 'cause the connection's up, you've already paid the connection the cloud service is up, you've already paid for it. >> So how do businesses get better control over that spend or how do you help them? >> Yeah, so how we help them is our service is able to be turned off when it's not in use. So in the event that you don't need the service over a weekend or over a month, you can just turn it off and you're not paying for that. >> It sounds so simple but it actually is kind of revolutionary in the industry which is why I keep coming back to it. It's great. So we've heard a lot about hybrid cloud, multicloud. How is this increasing the complexity for customers? >> Well I think the complexity for customers has increased due to the fact that you have a multicloud requirement or you have multiple teams accessing your cloud service provider and there's no one really managing it from a central perspective. >> Savannah: They can definitely get siloed really easy. >> Yeah, and then it runs away from you and the next thing you know, you start to look at the monthly bills. But generally that happens on an annual basis. If any companies like mine, you're doing your annual reconciliation of your bills and that's when you notice something's not right. >> Yeah, definitely. I can actually see a Slack message I got once, multiple times probably. Is anyone using this service? Why does it cost us that? That's exactly what you're talking about. >> Do you integrate with the Amazon Management Console or is it a separate service? >> It's, our service is a separate service. We are APId in with AWS. You do have a single console from our platform to manage your connections to the cloud. And then once you are connected in, you would still need to use the AWS console to manage your service. They're very, let's just say no one is offering a remote console third party console yet for AWS or any other cloud service for that matter. >> How about for hybrid cloud is obviously the way, you know, the way the industry is going. How do you enable companies to manage their hybrid cloud environments more intelligently? >> Yeah, and that's another great question. We allow that, you know, we're a global company. We have global access around the world. It includes not only traditional telecommunication services but also includes satellite service as well as 5G and LTE capability to the platform. So in the event that someone is in a hyper cloud situation, they have a lot of capability to enable their services. >> You talked about network as a service, and I, we haven't had a chance to dig into it. So tell me a little bit more. How does, how can this help reduce egress charges? How, are people excited when they hear network as a service? Where are we off at on that hype curve? >> Yeah, I think it's low on the excitement scale. >> Savannah: Yeah. >> You know, network has become somewhat of a commodity in the world, like electricity or water, you know, for the most of the world. And so network as a service, what it has enabled is it has enabled the customers more control over what they're doing. 'Cause in the past, you would need weeks, if not months to get services installed. And then if you needed to make a change to that service to increase it or decrease it in accordance to your requirements, that might take a couple of days at the soonest and you know, the Console Connect platform now changed that down to a few minutes. So within a few minutes, you can enable services, turn it up, turn it down, scale up, scale down. >> Savannah: Talk about time to value. >> There's no equipment installation required? >> No, it is our private network and so there must be a direct connection to it. It's not available over the public internet. Generally, a customer will connect to us via a cross connect at a data center or they can bring in a local loop. Or our existing customers, we just flip a little switch, so to speak, software wise, and we give them access to the platform from their existing services. >> Do you work with co-location interconnects as well? >> Exactly, yes. And in fact, you can purchase those services across our platform with a lot of the co-location service providers. >> So if I'm already using a co-lo, I can deploy your service directly from that co-lo. >> Yes. Yes. >> That's very convenient. >> That is very convenient. (laughs) >> You also mentioned the ability interconnect between customers. So your customers can actually connect to each other and conduct transactions or integrate their applications. Talk about how that works. >> Yeah, so for instance, let's say you are a customer that's taking advantage of our platform and you find your network is under a DDoS attack. You can go into our meeting place, connect to one of our cloud service providers who specializes in DDoS mitigation, spin up a connection to them within a few minutes, and immediately, you can start taking care of your DDoS problem. And once it's taken care of, you turn it down. Now those types of services that are subscription based are via API into our platform so we can settle the bill for our customer on behalf of that service provider or the service provider themselves can bill that customer depending on how they want to set it up. So it's very flexible. >> It's really clever, too. I mean, especially in an instance like you just mentioned in that example, that's a moment of panic and high stress and high tension. The last thing you want to be thinking about is what's the right service provider? How quickly can I get this up and running? If I can just couple clicks, couple lines of code perhaps, or even just through the portal, be able to do it, it's pretty powerful. You mentioned that Console Connect, and I want to talk about this 'cause it's clear you care about the user experience, the community and Console Connect came out of LinkedIn DNA and you mentioned there's a social component to the platform as well. Can you tell me a little bit more about that? >> Yes, thank you for that. Yeah, so you can, as a customer or a partner, you can market directly to others on the platform using our meeting place. And you have the ability to reach out directly to people across the platform, send them a message. You have the ability to post articles, blog in one of our sections. And then the other one, you can actually go in and see all the latest activity in the platform. You can see who's the newest companies to join Console Connect. >> Savannah: Oh wow, cool. >> How do I reach out to them? And then that gives you the ability to begin either marketing across the platform or direct marketing to someone or directly just reach out and connect with them and say hey, we want to set a bilateral partnership with you. You know, how do we do that? So it's very flexible. >> Savannah: Yeah. >> Can I connect my systems to others? So if I want to plug into their eCommerce system so I can fulfill orders taken through their eCommerce system, can I enable that kind of connection? >> Oh, we're not there yet. It is coming, but we're just not there yet. >> What are the complexities? >> A lot of that is a trust issue. >> Yeah. >> You know, when you're dealing with across the globe, there are regulations in every location that must be adhered to. A lot of that is security and privacy related. And we must make sure that we are adhering to all the local regulations wherever we are. >> So it's not the technology, it's a problem, really. It's the- >> It's a regulatory issue, yeah. So the technology is there and I would say that the rest is following, it's just, it's slow when you're dealing with permits and with compliance. >> I also want to ask you, our notes here mention egress charges, which are a niggling pain point for a lot of customers. They have to pay to get their data of the cloud. How do you help with that problem? >> So how we help with this is first, we get a discount from our partners, our cloud partners, including AWS, and we pass that on to the customers. The other way is you have a full visibility of which connections you have live into those partners and you can manage that much easier through the single, I would say view. Of all of your connections. >> Savannah: Yeah. >> You can see all of your cloud connections right in the one view. And then you can do a little more digging and say are we using these, you know? Because a lot of times, you have projects that spin up and then someone forgets to spin them back down. So this helps give you that single view. But again, we get the discount that we are happy to pass on as well. >> Which is a win-win for everyone. I've using a tab analogy all show, we all we want it in one place, one tab, not all the tabs. >> Yes. I think network management and service management in any enterprise or partnership company is a real drain on resources. >> Oh yeah. And it's a waste of money. >> Garrett: Yeah. And if you're not managing correctly, yeah, you get the thing on the money. >> Are you an alternative to the direct connect services from the major cloud providers or are you a compliment to them? >> We're not competing with them, we're partnered. And so we don't see ourselves as an alternative. A lot of times, our customers come to us and they want to direct connect in a location where perhaps AWS isn't. >> Paul: Doesn't have a point of presence. >> Exactly. Right. We give them that flexibility of, yes you can directly connect here. And then the other approach that we like to take is we like to give our customers the choice of not only data center, but also region. So a lot of times egress charges are can be calculated across regions as well and that can really add up for our customer. Whereas if you have multiple egress locations, you're not transferring data across a region on the AWS platform or another cloud service platform. You can egress at that location and then take it across your own network or take it across our network and then your egress charges will be more reasonable. >> That's, it's convenient. Smart! You're making people's jobs optimized and easier as well as their stack and all the tools that they're using. It's fantastic. All right Garrett, we've got a new challenge here on theCUBE at re:Invent. >> Garrett: All right. >> It's probably different from the last time you were on theCUBE. We're looking for your 30 second hot take, your thought leadership moment. What's the biggest theme coming out of the show or for you as we look into 2023? >> Well, for in 30 seconds- >> Savannah: Yeah, casual, right? >> No pressure. >> Savannah: No big deal. >> No, so with Console Connect, you know, we are around the globe. I know that a lot of companies at AWS are, some are regional, some are global. And we have the ability to cover both. We can do either regional or global or a hybrid of those. We also have a hybrid approach on different types of services. And so the flexibility, scalability, reliability, and the lowered cost of egress with Console Connect is a win all around. You can't lose with it. >> I love it. You're meeting customers where they are. Garrett, it was fantastic to have you back on theCUBE. We look forward to your third cameo. >> Thank you very much. I appreciate your time. Thank you for having Console Connect on. >> Hey, absolutely. We look forward to continuing to watch and hopefully tell that story as well. And thank all of you for tuning in to day four of AWS's re:Invent coverage in Las Vegas, Nevada. I'm starting to forget my own name. I am with Paul Gilland. I'm Savannah Peterson. This is theCUBE. We are the leading source for high tech coverage. (gentle music)

(bright music) >> Hello cloud computing friends and welcome back to theCUBE, where we are live from Las Vegas, Nevada, here at AWS re:Invent all week. My name is Savannah Peterson, very excited to be joined by Paul Gillan today. How are you doing? >> I'm doing great, Savannah. It's my first re:Invent. >> I was just going to ask you >> So it's quite an experience. >> If you've ever been to re:Invent. >> It's dazzling much like the sequins on your top. It's dazzling. >> Yes. >> It's a jam packed affair. I came to the COMDEX Conference for many years in Las Vegas, which was huge event and this really rivals it in terms of these crowd sizes. But I think there's more intensity here. There's more excitement. People are just jazzed about being here to the extent that I never saw at other computer conferences. >> I thought I would agree with you. It's my first re:Invent as well. I'm glad we could share this experience together. And the vibe, the pulse, I think being back in person is really contagious as well. Ooh, maybe the wrong word to use, but in a great way. The energy is definitely radiating between people here. I'll watch my words a little bit better. >> And in person we have with us Samuel Nicholls, the director of public cloud at Global Product Marketing at Veeam Software. Sam, is it Sam or Samuel? >> Depends if I'm in trouble, Paul. >> Savannah: But it depends on who's saying it out loud. >> Yeah, yeah. It's typically, Samuel is usually reserved for my mother, so- >> Yeah. >> (laughs) Well, Sam, thanks for joining us. >> We'll stick with Sam on the show. >> Yeah. >> So Veeam been a red hot company for several years. Really made its, uh, its reputation in the VMware world. Now you've got this whole-sail shift to the cloud, not that VMware is not important still, but how is that affecting, you're shifting with it, how is that affecting your role as a product manager and the business overall? >> Yeah, it's a fantastic question. Obviously Veeam was pioneered in terms of being the purpose-built backup and recovery company for VMware. And as these workloads are being transitioned from the data center into the cloud or just net new workloads being created in the cloud, there is that equal need for backup and recovery there. So it's incredibly important that we were able to provide a purpose-built backup and recovery solution for workloads that live in AWS as well. >> Paul: And how different is it backing up an AWS workload compared to a VMware workload? >> I think it depends on what kind of service a user is, is, is utilizing, right? There's infrastructure as a service, platform as a service, software as a service. And given the differences in what is exposed to that customer that can make backup and recovery quite challenging. So I would say that the primary thing that we want to look at is utilizing native snapshots is our first line of defense when it comes to backup and recovery, irrespective of what workload that right might be whether it's a virtual machine, Amazon EC2, some sort of database on Amazon RDS, a file share, so on. >> Savannah: I bet you're seeing a lot across verticals and across the industry given the support that you're giving customers. What are you seeing in the market and in customer environments? What are some of those trends? >> So I think the major trends that we highlight in our data protection trend support, which is a new update is coming very shortly in the new year, is- >> Savannah: We have to check that out. >> Yeah, absolutely. The physical server is on a decline within the data center. Virtualized workloads, namely VMware is relatively static, kind of flat. The real hockey stick is with the cloud workloads. And as I mentioned before, that is partially because workloads are being transitioned from physical to virtual machines to being cloud hosted but also we're creating more applications and the cloud has become lead de facto standard for new workloads. So you hear about cloud first initiatives, digital transformation, the cloud is central to that. >> You mentioned snapshotting, which is a relatively new phenomenon, although it's taken a hold rapidly, how does snapshotting work in the cloud versus in on your on-prem environment? >> Samuel: It's not wildly different at all. I think the snapshots is again, a great first line of defense for helping users achieve very low recovery point objectives. So the frequency that they can protect their data as well as very low recovery time objectives, how quickly that I can recover the data. Because that's why we're backing up, right? We need the ability to recover. However, snapshots certainly have their limitations as well. They are not independent of the workload that is being protected. So if there were to be some sort of cybersecurity event like ransomware that is prolific throughout pretty much every business, every vertical. When that snapshot is not independent, if the production system becomes compromised that snapshot's likely to be compromised as well. And then going back to the recovery piece, not going to have something to recover from. >> And it's not a one and done with ransomware. >> No. >> It's, yeah. So how, so what is the role that backup plays? I mean a lot of people, I feel like security is such a hot topic here in the show and just in general, attacks are coming in unique form factors for everyone. I mean, I feel like backup is, no pun intended, the backbone of a system here. How does that affect what you're creating, I mean? >> Yeah, absolutely. I think, like you say the backup is core to any comprehensive security strategy, right? I think when we talk about security, everyone tends to focus on the preventative, the proactive piece, stopping the bad guys from getting in. However, there is that remediative aspect as well because like you say, ransomware is relentless, right? You, you as a good guy have to pretty much fend off each and every single attack that comes your way. And that can be an infinite number of attacks. We're all human beings, we're fallible, right? And sometimes we can't defend against everything. So having a secure backup strategy is part of that remediative recovery component for a cybersecurity strategy is critical. And that includes things like encryption, immutability, logical separation of data and so forth. >> Paul: We know that ransomware is a scourge on-premises, typically begins with the end users, end user workstation. How does ransomware work in the cloud? And do the cloud providers have adequate protections against ransomware? Or can they? >> Samuel: Yeah, it's a, it's a fantastic question as well. I think when we look at the cloud, one of the common misconceptions is as we transition workloads to the cloud, we are transitioning responsibility to that cloud provider. And again, it's a misconception, right? It is a shared responsibility between the cloud provider in this case, AWS and the user. So as we transition these workloads across varying different services, infrastructure, platform, software as a service, we're always, always transitioning varying degrees of responsibility. But we always own our data and it is our responsibility to protect and secure that data, for the actual infrastructure components, the hardware that is on the onus of the cloud provider, so I'd say that's the major difference. >> Is ransomware as big a threat in the cloud as it is on-prem? >> Absolutely. There's no difference between a ransomware attack on-premises or in the cloud. Irrespective of where you are choosing to run your workloads, you need to have that comprehensive cybersecurity strategy in order to defend against that and ultimately recover as well if there's a successful attempt. >> Yeah, it's, ooh, okay. Let's get us out at the dark shadows real quick (laughs) and bring us back to a little bit of the business use case here. A lot of people using AWS. What do you think are some of the considerations, they should have when they're thinking about this, thinking about growing their (indistinct)? >> Well, if we're going to stick down the dark shadows, the cybersecurity piece. >> We can be the darkness. >> You and me kind of dark shadows business. >> Yeah, yeah. >> We can go rainbows and unicorns, nice and happy if you like. I think there's a number of considerations they need to keep up. Security is, is, is number one. The next piece is around the recovery as well. I think folks, when they, when we talk about backup and recovery, the focus is always on the backup piece of it. But again, we need to focus on why we're doing the backup. It's the recovery, it's the recovery component. So making sure that we have a clean verifiable backup that we're able to restore data from. Can we do that in a, in efficient and timely manner? And I think the other major consideration is looking at the entirety of our environments as well. Very few companies are a hundred percent sole sourced on a single cloud provider. It is typically hybrid cloud. It's around 80% of organizations are hybrid, right? So they have their on-premises data and they also have workloads running in one or multiple clouds. And when it comes to backup and recovery of all of these different infrastructures and environments, the way that we approach it is very different. And that often leads to multiple different point products from multiple different vendors. The average company utilizes three different backup products, sometimes as many as seven and that can introduce a management nightmare that's very complex, very resource intensive, expensive. So looking at the entirety of the environment and looking to utilize a backup provider that can cover the entirety of that environment while centralizing everything under a single management console helps folks be a lot more efficient, a lot more cost effective and ultimately better when it comes to data protection. >> Amazon and all cloud providers really are increasingly making regions transparent. Just at this conference, Amazon introduced failover controls from multiple multi-region access points. So you can, you can failover from one access from one region to another. What kind of challenges does that present to you as a backup provider? >> I don't think it represents any challenges. When we look at the native durability of the cloud, we look at availability zones, we look at multi-region failover. That is, that durability is ultimately founded on, on replication. And I wouldn't say that replication and backup, you would use one or the other. I would say that they are complimentary. So for replication, that is going to help with the failover scenario, that durability component. But then backup again is that independent copy. Because if we look at replication, if let's say the source data were to be compromised by ransomware or there was accidental deletion or corruption, that's simply going to be copied over to the target destination as well. Having that backup as an independent copy, again compliments that strategy as well. >> Paul: You need it in either, in any scenario. >> Samuel: In any scenario. >> I think the average person would probably say that backup is not the most exciting technology aspect of this industry. But, but you guys certainly made, build a great business on it. What excites you about what's coming in backup? What are the new technologies, new advancements that perhaps we haven't seen and productized yet that you think are going to change the game? >> I think actually what we offer right now is the most exciting piece which is just choice flexibility. So Veeam again is synonymous with VMware backup but we cover a multitude of environments including AWS, containerized workloads, Kubernetes physical systems and the mobility pieces is critical because as organizations look to act on their digital transformation, cloud first initiatives, they need to be able to mobilize their workloads across different infrastructures, maybe from on-premises into the cloud, one cloud to another, maybe it's cloud back to on-premises, 'cause we do also see that. That flexibility of choice is what excites me about Veeam because it's ultimately giving the users best in class data protection tool sets without any prescriptive approach from us in terms of where you should be running your workloads. That is the choice that you use. >> Yeah, Veeam is definitely more than VMware. We actually had a chance to chat with you all like KubeCon and CloudNativeCon in Detroit. So we, we've seen the multitude of things that you touch. I want to bring it back to something and something kind of fun because you talked a lot about the community and being able to serve them. It's very clear, actually I shouldn't say this, I shouldn't say it's very clear, but to me it appears clear that community is a big priority for Veeam. I just want to call this out 'cause this was one of the cooler pieces of swag. You all gave out a hundred massage guns. Okay, very hot topic. Hot Christmas gift for 2022. I feel like Vanna White right now. And, but I thought that I was actually really compelled by this because we do a swag segment on theCUBE but it's not just about the objects or getting stuff. It's really about who's looking out for their community and how are they saying thanks. I mean, swag is a brand activation but it's also a thank you and I loved that you were giving out massage guns to the AWS Heroes and Community Builders. >> Yep. >> What role does community play in the culture and the product development at Veeam? >> So community has always been at the heart of Veeam. If you have a look at pretty much every single development across all of our versions, across all of our products it's always did by the community, right? We have a wonderful Veeam forum where we got 400,000 plus users actively providing feedback on the product what they would like to see. And that is ultimately what steers the direction of the product. Of course market trends and technology chain. >> A couple other factors, I'm sure. >> A couple of other factors, but community is huge for us. And the same goes for AWS. So, you know, talking with the AWS Heroes, the Community Builders helps Veeam reach further into that, into that community and the AWS user base and empower those folks with data protection tools and massage guns, when your feet are tired from, you know, being standing on them all day in Vegas. >> (laughs) Yeah, well, I mean, everybody, everybody's working hard and it's nice to say, it's nice to say, thank you. So I love, I love to hear that and it's, it's clear from the breadth of products that you're creating, the ways that you're supporting your customers that you already, they care a lot about community. We have a new challenge on theCUBE this year at AWS re:Invent. Think of it as an Instagram reel of your thought leadership, your hot take on the show, key themes as we look into 2023. What do you think is the most important story or trend or thing going on here at the show? >> I think it's just the continuation of cybersecurity and the importance of backup as a comprehensive cybersecurity strategy. You know, some folks might say that secure backup is your last line of defense. Again, ransomware is relentless. These folks are going to keep coming and even if they're successful, it's not a one and done thing. It's going to happen again and again and again. So, you know, we have a look around the show floor, the presentations there is a huge cybersecurity focus and really just what folks should be doing as their best practice to secure their AWS environments. >> That's awesome. Well, Paul, any final, any final thoughts or questions? >> I just quickly, you've mentioned data security, you mentioned data protection and backup sort of interchangeably but they're not really the same thing, are they? I mean, what businesses do you see Veeam as being here? >> I would say that we are a data protection company because of, yes, there is backup, but there's also the replication component. There's the continuous data protection component where we've got, you know, near-zero RTOs and then we again look at the cybersecurity components of that. What can we do to really protect that data? So I would say that the two are different. Backup is a subset of data protection. >> Sam, thank you so much for being here with us on theCUBE. It's been a super insightful conversation. Hopefully we'll get you back soon and more of the teams, there seem to be celebrities here with us on theCUBE. Paul Gillan, thank you so much for being here with me. >> Pleasure Savannah. >> And I'm glad we get to celebrate our first re:Invent and most importantly, thank you to the audience for tuning in. Without you, we don't get to hang out here in fabulous Las Vegas, Nevada, where we're live from the show floor at AWS re:Invent. My name is Savannah Peterson with Paul Gillan. We're theCUBE and we are the leading source for high-tech coverage. (bright music)

(upbeat music) >> Hey, everyone. Welcome to this CUBE Conversation that's part of the AWS startup showcase Season Two, Episode Four. I'm your host Lisa Martin. Chase Doelling joins me, the principles strategist at JumpCloud. Chase, welcome to theCUBE. It's great to have you. >> Chase: Perfect. Well, thank you so much, Lisa. I really appreciate the opportunity to come and hang out. >> Let's talk about JumpCloud. First of all, love the name. This is an open directory platform. Talk to the audience about what the platform is, obviously, the evolution of the domain controller. But give us that backstory? >> Yeah, absolutely. And so, company was started, and I think, from serial entrepreneurs, and after kind of last exit, taking a look around and saying, "Why is this piece of hardware still the dominant force when you're thinking about identities, especially when the world is moving to cloud, and all the different pieces that have been around it?" And so, over the years, we've evolved JumpCloud into an open directory platform. And what that is, is we're managing your identities, the devices that are associated to that, all the access points that employees need just to get their job done. And the best part is, is we're able to do that no matter where they are within the world. >> It seems like kind of a reinvention of how modern IT teams are getting worked done, especially in these days of remote work. Talk to me a little bit about the last couple of years particularly as remote work exploded, and here we are still probably, permanently, in that situation? >> Yeah, absolutely. And I think it's probably going to be one of those situations where we stick with it for quite a while. We had a very abrupt force in making sure that essentially every IT and security team could grapple with the fact of their users are no longer coming into the office. You know, how do we VPN into all of our different resources? Those are very common and unfortunate pain points that we've had over the last couple years. And so, now, people have starting to kind of get into the motion of it, working from home, having background and setups and other pieces. But one of the main areas of concern, especially as you're thinking about that, is how does it relate to my security infrastructure, or kind of my approach to my organization. And making sure that too, on the tail end, that a user's access and making sure that they can get into everything that they need to do in order to get work done, is still happening? And so, what we've done, is we've really taken, evolving and really kind of ripping apart this notion of what a directory was. 'Cause originally, it was just like, great, almost like a phone directory. It's where people lived they're going into all those different pieces. But it wasn't set up for the modern world, and kind of how we're approaching it, and how organizations now are started with a credit card and have all of their infrastructure. And essentially, all of their IP, is now hosted somewhere else. And so, we wanted to take a different approach where we're thinking about, not only managing that identity, but taking an open approach. So, matter where the identity's coming from, we can integrate that into the platform but then we're also managing and securing those devices, which is often the most important piece that we have sitting right in front of us in order to get into that. But then, also that final question, of when you're accessing networks applications, can you create the conditions for trust, right? And so, if you're looking at zero trust, or kind of going after different levels of compliance, ISO, SOC2, whatever that might be, making sure that you have all that put in place no matter where your employees are. So, in that way, as we kind of moved into this remote, now hybrid world, it wasn't the office as the gating point anymore, right? So, key cards, as much as we love 'em, final part, whereas the new perimeter, the kind of the new barrier for organizations especially how they're thinking about security, is the people's identities behind that. And so, that's the approach that we really wanted to take as we continue to evolve and really open up what a directory platform can do. >> Yeah. Zero trust security, remote work. Two things that have exploded in the last couple of years. But as employees, we expected to be able to still have the access that we needed to apps, to the network, to WiFi, et cetera. And, of course, on the security side, we saw massive changes in the threat landscape that really, obviously, security elevates to a board level conversation. So, I imagine zero trust security, remote work, probably compliance, you mentioned SOC2, are some of the the key use cases that you're helping organizations with? >> Those are a lot of the drivers. And what we do, is we're able to combine a lot of different aspects that you need for each one of those. And so, now you're thinking about essentially, the use case of someone joins an organization, they need access to all these different things. But behind the scenes, it's a combination of identity access management, device management, applications, networks, everything else, and creating those conditions for them to do their roles. But the other piece of that, is you also don't want to be overly cumbersome. I think a lot of us think about security as like great biometrics, so I'm going to add in these keys, I'm going to do everything else to kind of get into these secured resources. But the reality of it now, is those secure resources might be AWS infrastructure. It might be other Salesforce reporting tools. It might be other pieces, or kind of IP within the organization. And those are now your crown jewel. And so, if you're not thinking about the identities behind them and the security that you have in order to facilitate that transaction, it becomes a board level conversation very quickly. But you want to do it in a way that people can move forward with their lives, and they're not spending a ton of time battling the systems and procedures you put in place to protect it, but that it's working together seamlessly. And so, that's where, kind of this notion for us of bringing all these different technologies into one platform. You're able to consolidate a lot of those and remove a lot of the friction while maintaining the visibility, and answering the question, of who has access to what? And when did they do that? Those are the most critical pieces that IT and security teams are asking themselves when something happens. And hopefully, on the preventative side and not so much on the redacted side. >> Have you seen the escalation up the C-Suite change of the board in terms of really focusing on how do we do identity management? How do we do single sign on? How do we do device management and network access? Is that all the way up to the C-Suite board level as well? >> It certainly can be. And we've seen it in a lot of different conversations, because now you are thinking about all different portions of the organization. And then, two, as we're thinking about times we're currently in, there's also a cost associated to that. And so, when you start to consolidate all of those technologies into one area, now it becomes much more of total cost optimization types of story while you're still maintaining a lot of the security and basic blocking and tackling that you need for most organizations. So, everything you just mentioned, those are now table stakes for a lot of small, medium, startups to be at the table. So, how do you have access to enterprise level, essentially technology, without the cost that's associated to it. And that's a lot of the trade offs that organizations are facing and having those types of conversations as it relates to business preparedness and how we're making sure that we are putting our best foot forward, and we're able to be resilient in no matter what type, of either economic or security threat that the organization might be looking at. >> So, let's talk about the go-to market, the strategy from a sales and marketing perspective. Where are the customer conversations happening? Are they at the IT level? Are they higher up the stack? >> It's really at, I'd say the IT level. And so, by that, I mean the builders, the implementers, everyone that's responsible for putting devices in people's hands, and making sure that they can do their job effectively. And so, those are their, I'd say the IT admins the world as well as the managed service providers who support those organizations, making sure that we can enable them to making sure that their organizations or their client organizations have all the tools that their disposable to make sure that they have the security or the policies, and the technology behind them to enable all those different practices. >> Let's unpack the benefits from an IT perspective? Obviously, they're getting one console that they can manage at all. One user identity for email, and devices, and apps, and things. You mentioned regardless of location, but this is also regardless of operating system, correct? >> That's correct. And so, part of taking an open approach, is also the devices that you're running on. And so, we take a cross OS approach. So, Mac, Windows, Linux, iPhone, whatever it might be, we can make sure that, that device is secure. And so, it does a couple different things. So, one, is the employees have device choice, right? So, I'm a Mac person coming in. If forced into a Windows, it'd be an interesting experience. But then, also too, from the back end, now you have essentially one platform to manage your entire fleet. And also give visibility and data behind what's happening behind those. And then, from the end user perspective as well, everything's tied together. And so, instead of having, what we'll call user ID schizophrenia, it might be one employee, but hundreds of different identities and logins just to get their work done. We can now centralize that into one person, making sure you have one password to get into your advice, get into the network, to get into your single sign on. We also have push MFA associated with that. So, you can actually create the conditions for your most secured access, or you understand, say, "Hey, I'm actually in the office. I'm going to be a hybrid employee. Maybe I can actually relax some of those security concerns I might have for people outside of the network." And all we do, is making sure that we give all that optionality to our IT admins, manage service providers of the world to enable that type of work for their employees to happen. >> So, they have the ability to toggle that, is critically important in this day and age of the hybrid work model, that's probably here to stay? >> It is, yeah. And it's something that organizations change, right? Our own organizations, they grow, they change different. New threats might emerge, or same old existing threats continue to come back. And we need to just have better processes and automations put within that. And it's when you start to consolidate all of those technologies, not only are you thinking about the visibility behind that, but then you're automating a lot of those different pieces that are already tightly coupled together. And that actually is truly powerful for a lot of the IT admins of the world, because that's where they spend a lot of time, and they're able to spend more time helping users tackling big projects instead of run rate security, and blocking, and tackling. That should be enabled from the organization from the get go. >> You mentioned automation. And I think that there's got to be a TCO reduction aspect here with respect to security and IT practices. Can you talk about that a little bit? >> Yeah, absolutely. Let's think about the opposite of that. Let's say we have a laundry list of technology that we need to go out and source. One is, great, where the identity is, so we have an identity provider. Now, we need to make sure that we have application access that might look like single sign on. Now, we need to make sure, you are who you are no matter where you are in the world. Well, now we need multifactor authentication and that might involve either a push button, or biometrics. And then, well, great the device's in front of us, that's a huge component, making sure that I can understand, not only who's on the device, but that the device is secure, that there's certificates there, that there's policies that ensure the proper use of that wherever it might be. Especially, if I'm an employee, either, it used to be on the the jet center going between flying anywhere you need. Now, it's kind of cross country, cross domain, all those different areas. And when you start to have that, it really unlocks, essentially IT sprawl. You have a lot of different pieces, a lot of different contracts, trying to figure out one technology works, but the other might not. And you're now you're creating workarounds for all these different pieces. So, the opposite of that, is essentially, let's take all those technologies and consolidate that into one platform. So, not only is it cheaper essentially, looking after that and understanding all the different technologies, but now it's all the other soft costs around it that many people don't think about. It's all the other automations. It's all the workarounds that you didn't have to do in the first place. It's all the other pieces that you'd spend a lot of time trying to wire it together. Into the hopes of that, it creates some security model. But then again, you lose a lot of the visibility. So, you might have an incident happen over here, or a trigger, or alert, but it's not tied to the rest of the stack. And so, now you're spending a lot of time, especially, either trying to understand. And worse timing, is if you have an incident and you're trying to understand what's happening? Unraveling all of that as it happens, becomes impossible, especially if it's not consolidated with one platform. So, there's not only the hard cost aspect of bringing all that together, but also the soft costs of thinking about how your business can perform, or at least optimize for a lot of those different standard processes, including onboarding, offboarding, and everything else in between. >> Yeah. On the soft cost side, I can imagine. I can see huge benefits for HR onboarding, offboarding. I can see benefits for the employee experience period, which directly relates to the customer experience. So, in terms of the business impact that JumpCloud can make, it seems to be pretty horizontal across any type of organization? >> It is, and especially as you mentioned HR. Because when you think about, where does the origin of someone's identity start? Well, typically, it starts with a resume and that might be in applicant tracking software. Now, we're going to get hired, so we're going to move into HR, because, well, everyone likes payroll, and we need that in our lives, right? But now you get into the second phase, of great, now I've joined the organization. Now, I need access to all of these different pieces. But when you look at it, essentially horizontally, from HR, all the way into the employee experience, and their whole life cycle within the organization, now you're touching multiple different teams And that's one of the other, I'd say benefits of that, is now you're actually bringing in HR, and IT, and security, and everyone else that might be related within these kind of larger use cases of making work happen all coming under. And when they're tightly integrated, it's also a lot more secure, right? So, you're not passing notes along. You're not having a checklist of other stuff, especially when it relates to something as important as someone's identity, which is more often than not, the most common attack vector for people to go after. Because they know it's the keys to the kingdom. There's going to be a lot of different attempts, maybe malware and other pieces, but a lot of it comes back into, can I impersonate, or become the person that I want within the organization, because it's the identity allows you to access all those different pieces. And so, if it's coming from a disjointed process or something that's not as tightly as it could be, that's where it really opens up a lot of different vectors that organizations don't think about. >> Right, and those vectors are only growing and multiplying as we know, and here to stay. When you're in customer conversations what do you describe as maybe the top three differentiators of JumpCloud compared to the competition? >> Well, I think a lot of it is we take an open approach. And so, by that, I mean, it's one we're not locking into, I'd say different vendors or other areas. We're really looking into making sure that we can work within your environment as it stands today, or where you want to migrate in the future. And so, this could be a combination of on-prem resources, cloud resources, or nothing if you're starting a company from today. And the second, is again, coming back into how we're looking at devices. So, we take a cross OS approach that way, no matter what you're operating on, it all comes back from the same dashboard. But then, finally, we leverage a ton of different protocols to make sure it works with everything within your current technology stack, as well as it continues to elevate and evolve over time. So, it could be LD app and Radius, and Sam, and skim, and open ID Connect, and open APIs. And whatever that might be, we are able to tie in all those different pieces. So, now, all of a sudden, it's not just one platform, but you have your whole business tied into as that gives you some flexibility too, to evolve. Because even during the pandemic and the shift for remote, there's a lot of technology choices that shifted. A lot of people are like, "Okay, now's the time to go to the cloud." There might be other events that organizations change. There's other things that might happen. So, creating that flexibility for organizations to move and make those calls, is essentially how we're differentiating ourselves. And we're not locking you into this, walled garden of technology that's just our own. We really want to make sure that we can operate, and be that glue, so that way, no matter what you're trying to do and making sure that your work is being done, we can help facilitate that. >> Nice. No matter what happens. Because boy, at this day, anything's possible. One more question for you about your AWS partnership. Talk to me a little bit about that? >> Yeah, absolutely. So, we are preferred ADP identity provider and SSO provider for AWS. And so, now rebranded under their identity center. But it's crucial for a lot of our organizations and joint customers because again, when we think about a lot of organization IP and how they operate as a business, is tied into AWS. And so, really understanding, who has the right level of access? Who should be in there or not? And when too, you should challenge in making sure that actually there's something fishy there. Like let's make sure that they're not just traveling to Europe on a sabbatical, and it's really who they are instead of a threat actor. Those are some of the pieces when we're thinking about creating that authentication, but then also, the right authorization into those AWS resources. And so, that's actually something that we've been very close to, especially, I'd say that the origins of a company. Because a lot of startups, that's where they go. That's where they begin their journey. And so, we meet them where they are, and making sure that we're protecting not only everything else within their organization, but also what they're trying to get into, which is typically AWS >> Meeting customers where they are. It's all about that. Chase, thank you so much for joining me on the program talking about JumpCloud, it's open directory platform. The benefits, the capabilities, what's in it for IT, HR, security, et cetera. We appreciate all of your insights and time. Where do you want to point folks to go to learn more? >> Well, absolutely. Well, thank you so much for having us. And I'd say, if you're curious about any and all these different technologies, the best part is everything I talked about is free up to 10 users, 10 devices. So, just go to jumpcloud.com. You can create an organization, and it's great for startups, people at home. Any size company that you're at, we can help support all of those different facets in bringing in those different types of technologies all into one roof. >> Awesome. Chase, thank you so much. This is awesome, go to jumpcloud.com. For Chase Doelling, I'm Lisa Martin. We want to thank you so much for giving us some of your time and watching this CUBE Conversation. (upbeat music)

>>The >>Cube presents HPE discover 2022 brought to you by >>HPE. Hi everybody. Welcome back to day three, the Cube's continuous coverage wall to wall coverage of HPE. Discover 2022. My name is Dave Lanta. I'm here with John furrier. Dave McGraw is here. He's the vice president in the office of the CTO at VMware. And he's joined by Scott. We, the vice president and CTO of global sales for Hewlett Packard enterprise. And we're gonna talk tech, we're gonna talk integration. Co-creation gens. Welcome to the cube. >>Thank you so much, >>Scott, let me, let me ask you a question on the Scott side on the HP, we had the sales executives on the leaders on the sales side. You're on the CTO side with customers. You're in the front lines with customers green. Lake's got traction. I got this 1600 plus customers, 70 services we heard. And just the beginning, when you're out front of customers, you've got the old HPE now the new HPE kind of developing, what are they talking to you guys about? Cause now you have this cloud layer. I call it cloud operations, architecture shift. Yeah. What is the main conversation that you're involved in? >>I think it's driven by fundamentally that customers want to consume differently, right there workloads are ever evolving. You guys have evolved to meet those and since their consumption methods have changed on how they want and right. A lot of it's agility and, and speed of business right. Has, has dramatically shifted. So I think you'll see HPE GreenLake, you know, obviously as the cloud that comes to you, try to meet the problem where the cloud experience is needed. And I think that's the fundamental shift we've seen. I spent a lot of time with customers here at this conference. And as we've moved from cloud first to cloud smart to cloud everywhere, we're sitting in the intersection of cloud ever and delivering the experience together. And I think that's the heart of most of the conversations that are going on. >>Well, VMware, you guys are on, on a cloud. You guys shifted up with the cloud play. That's accelerated the VMware proposition. Now we have yesterday, we were talking to the city, the storage folks, they're provisioning single pane of glass or storage to customers. And whether they wanna pipe it to S3 or develop at the edge, doesn't matter. It's one console. Yeah. That's brand new. That's shipping. >>Yeah. And you know, a lot of it's driven too. I think the days of trap silos of resources that support one line of business are over. So we're talking about cloud agility everywhere, right. And to be able to embrace the cloud in all the locations. Right. And you kind of see folks move beyond just like there's the cloud, it's everywhere. It's the cloud. And so things like storage and fundamental compute and fundamental network operations that we're working on together, I think are where the customers expect us to be. We no longer can just show up. We have to show up and solve and solve before their needs. And I think that's a unique shift in the experience that's going >>On. So when you go back to, you know, Antonio four years ago now said, okay, we're all in. Yeah. On as a service. And so when you do that, you say, okay, we're gonna, we have services. They're gonna help do that. We have financial models that we can take to market immediately. So let's start there. And I would imagine take, so take us back. That's the point at which, you know, you're, you got email, phone ring, whatever let's integrate from an engineering standpoint go yeah. You know, as fast as you can. So what did that mean in terms of an engineer from an engineering perspective between HPE and, and VMware take us through that progression. >>Yeah. No, thanks for the question in your spot on it started with flexible financing models around metered usage. That was sort of the need at the time to now the expectation of engineered integrated solutions where customers don't wanna be in the system integration business anymore. And that requires engineering right. Requires deep innovation partnership to evolve to where the customer's headed, like before they've thought about it. And you'll see, you know, what we've done with vCloud foundation together and the integration within the HP GreenLake ecosystem, what we're doing with unified hybrid cloud views of what's going on, I think requires deep innovation things we're doing with other projects that we're gonna talk about today. Like Monterey capital thunder, our deep integrative innovation projects, where we've got together to try to solve a big problem cross industry that our customers are expecting us to do. And I think that speaks to the spirit of our long partnership together too. It's a business partnership. Of course it's a customer partnership to solve, but it's an innovation partnership. >>I gotta, I gotta ask about the, um, hybrid, obviously hybrids, the steady state. We're all seeing that now multi-cloud is being kicked around, but it's not, multi-cloud in the sense of workload portability so much. It's more of hybrid stitched together. Um, but it's coming fast with a data plane and yeah. The fabric and control planes. Uh, VMware, you guys are talking heavy about cross cloud or multicloud. Absolutely. So this is now brings up the old school interoperability question, right? So GreenLake sits here on premise. You guys have the edge, you get public cloud together. Where's the cross cloud come in. Where are customers doing when they think about cross cloud or, or multicloud? What is that conversation? Is it, Hey, I got Azure cause I got office and teams and I got Amazon over here and I got my on premise edge. Are they moving towards just being agnostic on cloud or is what's the environment? What, what are you crossing in the cloud? What does that mean across the cloud? Can >>You, I mean, from, from our perspective at VMware on premises, it's VMware cloud foundation, having that available, it's a VMware cloud instance, full STD STDC stack, uh, that is interoperable with our VMware cloud instances at the hyperscalers. And so for us, it's really about putting the management and control planes around that so that customers can easily determine where they wanna place workloads and when they need to burst, they need to scale up scale down. They have the flexibility and we wanna make sure all of these capabilities are available with HPE >>Going forward. What's interesting is that, you know, with, with GreenLake, what I like about what I'm seeing is is that, um, the leveling up of the cloud operation model, it's always been DevOps. We've always saw dev stack ops, clearly being operationally with cloud now on premise and edge with public cloud, it's full end to end operational cloud. If you wanna call it that, what is a key technical issue the customers need to do to get that in place? Is it to be DevOps, is that have cloud native applications, um, what kind of managed services, what's the makeup of that operating model for cloud look like? >>Yeah. I think if you talk to any enterprise commercial account, a top account, they'll they'll, if you, they think about how they run their functions, right. And you got, and you spoke to one of them, you have it ops at the bottom, it's a layer cake, right? You have it ops, everybody's deeply looking for AI ops that can remediate and orchestrate and you guys are on that journey as we are, as you move up to devs and dev SecOps, cuz security's critical, you got financial ops cuz we know economic value matters all the way clear up to cloud ops and Mo ops. What we're talking about is building hybrid operating model cause hybrid, it is simplified it where you're out of the stack, we're doing that together as partners and hybrid cloud is multiple consumption methods, but an operating model is encompass encompassing, cyber resiliency, compliance, economic, operational control. >>That's what we're built and edges in there as well. Right? Folks is, and it's not OT and it touching that's happening too, as we build edge tax, but folks need a simplified way. And as you saw in a lot of announcements here, our job was to bridge the cloud locations, right? So the customer didn't have to back to the portability statement you made, we announced a lot here that will allow you to float back and forth. So you have choice, choice and control control is the me is what every customer wants and they want the right workload at the right place at the right time at the right economic with the right capability. So I think that's in our mission together. Right? So, and >>A big part of engineering obviously is, is futures and roadmap. Yeah. Thought you mentioned Monterey cap thunder, you know, Monterey's kind of the smart Nick. One of the mega trends in the industry is Silicon diversity that handle all these new workloads to help with the edge. You know, capital is like the VSAN of memory as I, I would describe it. It obviously fits in there as well. So talk a little bit about the engineering roadmap, whatever you can share with us and how you guys are working together on that. Yeah. >>Yeah. I mean, those are three key projects for us. So there's constant interaction and integration with the HPE engineering team and the VMware team to make sure we bring those solutions to market with full capability. And for us, ultimately it's taking that technology and having it available in a VMware cloud context so that customers can have a, a consistent experience on premises running VMware cloud running with HPE GreenLake and then two are various VMware cloud suppliers around the world. And it's not just the hyperscalers, right? There's thousands of VMware cloud, uh, you know, partners that we work with manage service providers across the board. So it's, it's a very significant network of cloud. And you know, being consistent allows for mobility of workloads allows for consistency and skill sets for it operators as well. Mm-hmm >><affirmative> yeah. I wanna get into that, um, manage service trend around skill sets, but yeah, I have a, the number one thing that we've got in our, my notes here on multi-cloud challenges and I wanna get your reaction to it real quick, inconsistent infrastructure, API database network, and security constructs are different by cloud. How do you guys view that? And when you go to customers and they say, well, I got APIs that are different. I got different security constructs. What do I do? What does that, how do you answer that, that, that, that objection. >>Well, it's, it's a great call out cuz it is still the ongoing challenge, right? To gets to some of the portability, some of unified model and how they treat resources and consumption. Right? And so we're, we've all gotten together as an industry. You'll see purposely that the hyperscalers are all here at, at the conference, right? We're working on deep integration with all of our partners to make sure the customer doesn't have to. And I think it does extend to the different security models are troubling for customers. We're all working hard on unified security models as well. It's not just a developer saying, I like this set of APIs anymore, right? Or this framework customers need to run tier zero tier one, tier three applications when it really comes down to it and we need to create that unified model together. So, and I think that's really what the, the spirit or the embodiment of hybrid really is. >>When you talk to any customer, who's running a big operation, they're running in that model, right? They're not just doing cool. They want operationally simplicity. And I think you'll see these, these things we're engineering together are going after some of the hard problems, applications are hungry or all the time customers need more and more resources. And I think we would all agree. We've spent a lot of time in industry together when we're all working on sort of systems of record. What I call the shift ride effect is happening. Now we're in systems of interaction and systems of engagement out at the edge. That's the creation point of data. We need to be able to have that unified model all the way through the data path for the customer so they can monetize business value. >>And the data model is coming together. That's right. Where all three of those types of work that's right. There's two iconic names. And the other thing is that their trusted names and you're right, you're solving some of those hard problems making it simpler, but also you people trust that if something goes wrong, you're gonna be able to recover. So guys. >>Yeah. And I, and I'll tell you on the security front, you know, we've worked closely together here. If you look at, you know, VMware strategy of intrinsic security, it's really around going back to the development of our products, making sure there's a secure bill of materials, working with these guys on route of trust. Right? Making sure there's a full stack, uh, solution for our customers. Ultimately >>That's a whole nother cube segment that's bombs and shifting left and supply chain. Absolutely >>Shifting game. Absolutely. Right. Shifting >>Lift we're >>Shifting. Right guys. Awesome story. Congrats on the collaboration. Really appreciate your time in the cube. Thank you so >>Much. Thank you so >>Much. All right. You're very welcome. Okay, John and I will be back right after this short break. You're watching the Cube's coverage of HPE discover 2022 from Las Vegas, right back.

>> Announcer: "theCUBE" presents HPE Discover 2022. Brought to you by HPE. >> Welcome back to HPE Discover 2022. You're watching "theCUBE's" coverage. This is Day 2, Dave Vellante with John Furrier. Sheila Rohra is here. She's the Senior Vice President and GM of the Data Infrastructure Business at Hewlett Packard Enterprise, and of course, the storage division. And Omer Asad. Welcome back to "theCUBE", Omer. Senior Vice President and General Manager for Cloud Data Services, Hewlett Packard Enterprise storage. Guys, thanks for coming on. Good to see you. >> Thank you. Always a pleasure, man. >> Thank you. >> So Sheila, I'll start with you. Explain the difference. The Data Infrastructure Business and then Omer's Cloud Data Services. You first. >> Okay. So Data Infrastructure Business. So I'm responsible for the primary secondary storage. Basically, what you physically store, the data in a box, I actually own that. So I'm going to have Omer explain his business because he can explain it better than me. (laughing) Go ahead. >> So 100% right. So first, data infrastructure platforms, primary secondary storage. And then what I do from a cloud perspective is wrap up those things into offerings, block storage offerings, data protection offerings, and then put them on top of the GreenLake platform, which is the platform that Antonio and Fidelma talked about on main Keynote stage yesterday. That includes multi-tenancy, customer subscription management, sign on management, and then on top of that we build services. Services are cloud-like services, storage services or block service, data protection service, disaster recovery services. Those services are then launched on top of the platform. Some services like data protection services are software only. Some services are software plus hardware. And the hardware on the platform comes along from the primary storage business and we run the control plane for that block service on the GreenLake platform and that's the cloud service. >> So, I just want to clarify. So what we maybe used to know as 3PAR and Nimble and StoreOnce. Those are the products that you're responsible for? >> That is the primary storage part, right? And just to kind of show that, he and I, we do indeed work together. Right. So if you think about the 3PAR, the primary... Sorry, the Primera, the Alletras, the Nimble, right? All that, right? That's the technology that, you know, my team builds. And what Omer does with his magic is that he turns it into HPE GreenLake for storage, right? And to deliver as a service, right? And basically to create a self-service agility for the customer and also to get a very Cloud operational experience for them. >> So if I'm a customer, just so I get this right, if I'm a customer and I want Hybrid, that's what you're delivering as a Cloud service? >> Yes. >> And I don't care where the data is on-premises, in storage, or on Cloud. >> 100%. >> Is that right? >> So the way that would work is, as a customer, you would come along with the partner, because we're 100% partner-led. You'll come to the GreenLake Console. On the GreenLake Console, you will pick one of our services. Could be a data protection service, could be the block storage service. All services are hybrid in nature. Public Cloud is 100% participant in the ecosystem. You'll choose a service. Once you choose a service, you like the rate card for that service. That rate card is just like a hyperscaler rate card. IOPS, Commitment, MINCOMMIT's, whatever. Once you procure that at the price that you like with a partner, you buy the subscription. Then you go to console.greenLake.com, activate your subscription. Once the subscription is activated, if it's a service like block storage, which we talked about yesterday, service will be activated, and our supply chain will send you our platform gear, and that will get activated in your site. Two things, network cable, power cable, dial into the cloud, service gets activated, and you have a cloud control plane. The key difference to remember is that it is cloud-consumption model and cloud-operation model built in together. It is not your traditional as a service, which is just like hardware leasing. >> Yeah, yeah, yeah. >> That's a thing of the past. >> But this answers a question that I had, is how do you transfer or transform from a company that is, you know, selling boxes, of course, most of you are engineers are software engineers, I get that, to one that is selling services. And it sounds like the answer is you've organized, I know it's inside baseball here, but you organize so that you still have, you can build best of breed products and then you can package them into services. >> Omer: 100%. 100%. >> It's separate but complementary organization. >> So the simplest way to look at it would be, we have a platform side at the house that builds the persistence layers, the innovation, the file systems, the speeds and feeds, and then building on top of that, really, really resilient storage services. Then how the customer consumes those storage services, we've got tremendous feedback from our customers, is that the cloud-operational model has won. It's just a very, very simple way to operate it, right? So from a customer's perspective, we have completely abstracted away out hardware, which is in the back. It could be at their own data center, it could be at an MSP, or they could be using a public cloud region. But from an operational perspective, the customer gets a single pane of glass through our service console, whether they're operating stuff on-prem, or they're operating stuff in the public cloud. >> So they get storage no matter what? They want it in the cloud, they got it that way, and if they want it as a service, it just gets shipped. >> 100%. >> They plug it in and it auto configures. >> Omer: It's ready to go. >> That's right. And the key thing is simplicity. We want to take the headache away from our customers, we want our customers to focus on their business outcomes, and their projects, and we're simplifying it through analytics and through this unified cloud platform, right? On like how their data is managed, how they're stored, how they're secured, that's all taken care of in this operational model. >> Okay, so I have a question. So just now the edge, like take me through this. Say I'm a customer, okay I got the data saved on-premise action, cloud, love that. Great, sir. That's a value proposition. Come to HPE because we provide this easily. Yeah. But now at the edge, I want to deploy it out to some edge node. Could be a tower with Telecom, 5G or whatever, I want to box this out there, I want storage. What happens there? Just ship it out there and connects up? Does it work the same way? >> 100%. So from our infrastructure team, you'll consume one or two platforms. You'll consume either the Hyperconverged form factor, SimpliVity, or you might convert, the Converged form factor, which is proliant servers powered by Alletras. Alletra 6Ks. Either of those... But it's very different the way you would procure it. What you would procure from us is an edge service. That edge service will come configured with certain amount of compute, certain amount of storage, and a certain amount of data protection. Once you buy that on a dollars per gig per month basis, whichever rate card you prefer, storage rate card or a VMware rate card, that's all you buy. From that point on, the platform team automatically configures the back-end hardware from that attribute-based ordering and that is shipped out to your edge. Dial in the network cable, dial in the power cable, GreenLake cloud discovers it, and then you start running the- >> Self-service, configure it, it just shows up, plug it in, done. >> Omer: Self-service but partner-led. >> Yeah. >> Because we have preferred pricing for our partners. Our partners would come in, they will configure the subscriptions, and then we activate those customers, and then send out the hardware. So it's like a hyperscaler on-prem at-scale kind of a model. >> Yeah, I like it a lot. >> So you guys are in the data business. You run the data portion of Hewlett Packard Enterprise. I used to call it storage, even if we still call it storage but really, it's evolving into data. So what's your vision for the data business and your customer's data vision, if you will? How are you supporting that? >> Well, I want to kick it off, and then I'm going to have my friend, Omer, chime in. But the key thing is that what the first step is is that we have to create a unified platform, and in this case we're creating a unified cloud platform, right? Where there's a single pane of glass to manage all that data, right? And also leveraging lots of analytics and telemetry data that actually comes from our infosite, right? We use all that, we make it easy for the customer, and all they have to say, and they're basically given the answers to the test. "Hey, you know, you may want to increase your capacity. You may want to tweak your performance here." And all the customers are like, "Yes. No. Yes, no." Basically it, right? Accept and not accept, right? That's actually the easiest way. And again, as I said earlier, this frees up the bandwidth for the IT teams so then they actually focus more on the business side of the house, rather than figuring out how to actually manage every single step of the way of the data. >> Got it. >> So it's exactly what Sheila described, right? The way this strategy manifests itself across an operational roadmap for us is the ability to change from a storage vendor to a data services vendor, right? >> Sheila: Right. >> And then once we start monetizing these data services to our customers through the GreenLake platform, which gives us cloud consumption model and a cloud operational model, and then certain data services come with the platform layer, certain data services are software only. But all the services, all the data services that we provide are hybrid in nature, where we say, when you provision storage, you could provision it on-prem, or you can provision it in a hyperscaler environment. The challenge that most of our customers have come back and told us, is like, data center control planes are getting fragmented. On-premises, I mean there's no secrecy about it, right? VMware is the predominant hypervisor, and as a result of that, vCenter is the predominant configuration layer. Then there is the public cloud side, which is through either Ajour, or GCP, or AWS, being one of the largest ones out there. But when the customer is dealing with data assets, the persistence layer could be anywhere, it could be in AWS region, it could be your own data center, or it could be your MSP. But what this does is it creates an immense amount of fragmentation in the context in which the customers understand the data. Essentially, John, the customers are just trying to answer three questions: What is it that I store? How much of it do I store? Should I even be storing it in the first place? And surprisingly, those three questions just haven't been answered. And we've gotten more and more fragmented. So what we are trying to produce for our customers, is a context to ware data view, which allows the customer to understand structured and unstructured data, and the lineage of how it is stored in the organization. And essentially, the vision is around simplification and context to ware data management. One of the key things that makes that possible, is again, the age old infosite capability that we have continued to hone and develop over time, which is now up to the stage of like 12 trillion data points that are coming into the system that are not corroborated to give that back. >> And of course cost-optimizing it as well. We're up against the clock, but take us through the announcements, what's new from when we sort of last talked? I guess it was in September. >> Omer: Right. >> Right. What's new that's being announced here and, or, you know, GA? >> Right. So three major announcements that came out, because to keep on establishing the context when we were with you last time. So last time we announced GreenLake backup and recovery service. >> John: Right. >> That was VMware backup and recovery as a complete cloud, sort of SaaS control plane. No backup target management, no BDS server management, no catalog management, it's completely a SaaS service. Provide your vCenter address, boom, off you go. We do the backups, agentless, 100% dedup enabled. We have extended that into the public cloud domain. So now, we can back up AWS, EC2, and EBS instances within the same constructs. So a single catalog, single backup policy, single protection framework that protects you both in the cloud and on-prem, no fragmentation, no multiple solutions to deploy. And the second one is we've extended our Hyperconverged service to now be what we call the Hybrid Cloud On-Demand. So basically, you go to GreenLake Console control plane, and from there, you basically just start configuring virtual machines. It supports VMware and AWS at the same time. So you can provision a virtual machine on-prem, or you can provision a virtual machine in the public cloud. >> Got it. >> And, it's the same framework, the same catalog, the same inventory management system across the board. And then, lastly, we extended our block storage service to also become hybrid in nature. >> Got it. >> So you can manage on-prem and AWS, EBS assets as well. >> And Sheila, do you still make product announcements, or does Antonio not allow that? (Omer laughing) >> Well, we make product announcements, and you're going to see our product announcements actually done through the HPE GreenLake for block storage. >> Dave: Oh, okay. >> So our announcements will be coming through that, because we do want to make it as a service. Again, we want to take all of that headache of "What configuration should I buy? How do I actually deploy it? How do I...?" We really want to take that headache away. So you're going to see more feature announcements that's going to come through this. >> So feature acceleration through GreenLake will be exposed? >> Absolutely. >> This is some cool stuff going on behind the scenes. >> Oh, there's a lot good stuff. >> Hardware still matters, you know. >> Hardware still matters. >> Does it still matter? Does hardware matter? >> Hardware still matters, but what matters more is the experience, and that's actually what we want to bring to the customer. (laughing) >> John: That's good. >> Good answer. >> Omer: 100%. (laughing) >> Guys, thanks so much- >> John: Hardware matters. >> For coming on "theCUBE". Good to see you again. >> John: We got it. >> Thanks. >> And hope the experience was good for you Sheila. >> I know, I know. Thank you. >> Omer: Pleasure as always. >> All right, keep it right there. Dave Vellante and John Furrier will be back from HPE Discover 2022. You're watching "theCUBE". (soft music)

(upbeat music) >> Hello everyone, welcome back to the manager risk across the extended attack surface with Armis. I'm John Furrier, your host of theCUBE. Got the demo. Got here, Bryan Inman sales engineer at Armis. Bryan, thanks for coming on. We're looking forward to the demo. How you doing? >> I'm doing well, John, thanks for having me. >> We heard from Nadir describing Armis' platform, lot of intelligence. It's like a search engine meets data at scale, intelligent platform around laying out the asset map, if you will, the new vulnerability module among other things that really solves CISCO's problems. A lot of great customer testimonials and we got the demo here that you're going to give us. What's the demo about? What are we going to see? >> Well, John, thanks. Great question. And truthfully, I think as Nadir has pointed out what Armis as a baseline is giving you is great visibility into every asset that's communicating within your environment. And from there, what we've done is we've layered on known vulnerabilities associated with not just the device, but also what else is on the device. Is there certain applications running on that device, the versions of those applications, and what are the vulnerabilities known with that? So that's really gives you great visibility in terms of the devices that folks aren't necessarily have visibility into now, unmanaged devices, IoT devices, OT, and critical infrastructure, medical devices things that you're not necessarily able to actively scan or put an agent on. So not only is Armis telling you about these devices but we're also layering on those vulnerabilities all passively and in real time. >> A lot of great feedback we've heard and I've talked to some of your customers. Rhe agentless is a huge deal. The discoveries are awesome. You can see everything and just getting real time information. It's really, really cool. So I'm looking forward to the demo for our guests. Take us on that tour. Let's go with the demo for the guests today. >> All right. Sounds good. So what we're looking at here is within the Armis console is just a clean representation of the passive reporting of what Armis has discovered. So we see a lot of different types of devices from your virtual machines and personal computers, things that are relatively easy to manage. But working our way down, you're able to see a lot of different types of devices that are not necessarily easy to get visibility into, things like your up systems, IT cameras, dash cams, et cetera, lighting systems. And today's day and age where everything is moving to that smart feature, it's great to have that visibility into what's communicating on my network and getting that, being able to layer on the risk factors associated with it as well as the vulnerabilities. So let's pivot over to our vulnerabilities tab and talk about the the AVM portion, the asset vulnerability management. So what we're looking at is the dashboard where we're reporting another clean representation with customizable dashlets that gives you visuals and reporting and things like new vulnerabilities as they come in. What are the most critical vulnerabilities, the newest as they roll in the vulnerabilities by type? We have hardware. We have application. We have operating systems. As we scroll down, we can see things to break it down by vulnerabilities, by the operating system, Windows, Linux, et cetera. We can create dashlets that show you views of the number of devices that are impacted by these CVEs. And scrolling down, we can see how long have these vulnerabilities been sitting within my environment? So what are the oldest vulnerabilities we have here? And then also of course, vulnerabilities by applications. So things like Google Chrome, Microsoft Office. So we're able to give a good representation of the amount of vulnerabilities as they're associated to the hardware and applications as well. So we're going to dig in and take a a deeper look at one of these vulnerabilities here. So I'm excited to talk today about of where Armis AVM is, but also where it's going as well. So we're not just reporting on things like the CVSS score from NIST NVD. We're also able to report on things like the exploitability of that. How actively is this CVE being exploited in the wild? We're reporting EPSS scores. For example, we're able to take open source information as well as a lot of our partnerships that we have with other vendors that are giving us a lot of great value of known vulnerabilities associated with the applications and with hardware, et cetera. But where we're going with this is in very near future releases, we're going to be able to take an algorithm approach of, what are the most critical CVSS that we see? How exploitable are those? What are common threat actors doing with these CVEs? Have they weaponized these CVEs? Are they actively using those weaponized tools to exploit these within other folks' environments? And who's reporting on these? So we're going to take all of these and then really add that Armis flavor of we already know what that device is and we can explain and so can the users of it, the business criticality of that device. So we're able to pivot over to the matches as we see the CVEs. We're able to very cleanly view, what exactly are the devices that the CVE resides on. And as you can see, we're giving you more than just an IP address or a lot more context and we're able to click in and dive into what exactly are these devices. And more importantly, how critical are these devices to my environment? If one of these devices were to go down if it were to be a server, whatever it may be, I would want to focus on those particular devices and ensuring that that CVE, especially if it's an exploitable CVE were to be addressed earlier than say the others and really be able to manage and prioritize these. Another great feature about it is, for example, we're looking at a particular CVE in terms of its patch and build number from Windows 10. So the auto result feature that we have, for example, we've passively detected what this particular personal computer is running Windows 10 and the build and revision numbers on it. And then once Armis passively discovers an update to that firmware and patch level, we can automatically resolve that, giving you a confidence that that has been addressed from that particular device. We're also able to customize and look through and potentially select a few of these, say, these particular devices reside on your guest network or an employee wifi network where we don't necessarily, I don't want to say care, but we don't necessarily value that as much as something internally that holds significantly, more business criticality. So we can select some of these and potentially ignore or resolve for determining reasons as you see here. Be able to really truly manage and prioritize these CVEs. As I scroll up, I can pivot over to the remediation tab and open up each one of these. So what this is doing is essentially Armis says, through our knowledge base been able to work with the vendors and pull down the patches associated with these. And within the remediation portion, we're able to view, for example, if we were to pull down the patch from this particular vendor and apply it to these 60 devices that you see here, right now we're able to view which patches are going to gimme the most impact as I prioritize these and take care of these affected devices. And lastly, as I pivot back over. Again, where we're at now is we're able to allow the users to customize the organizational priority of this particular CVE to where in terms of, this has given us a high CVSS score but maybe for whatever reasons it may be, maybe this CVE in terms of this particular logical segment of my network, I'm going to give it a low priority for whatever the use case may be. We have compensating controls set in place that render this CVE not impactful to this particular segment of my environment. So we're able to add that organizational priority to that CVE and where we're going as you can see that popped up here but where we're going is we're going to start to be able to apply the organizational priority in terms of the actual device level. So what we'll see is we'll see a column added to here to where we'll see the the business impact of that device based on the importance of that particular segment of your environment or the device type, be it critical networking device or maybe a critical infrastructure device, PLCs, controllers, et cetera, but really giving you that passive reporting on the CVEs in terms of what the device is within your network. And then finally, we do integrate with your vulnerability management and scanners as well. So if you have a scanner actively scanning these, but potentially they're missing segments of your net network, or they're not able to actively scan certain devices on your network, that's the power of Armis being able to come back in and give you that visibility of not only what those devices are for visibility into them, but also what vulnerabilities are associated with those passive devices that aren't being scanned by your network today. So with that, that concludes my demo. So I'll kick it back over to you, John. >> Awesome. Great walk through there. Take me through what you think the most important part of that. Is it the discovery piece? Is it the interaction? What's your favorite? >> Honestly, I think my favorite part about that is in terms of being able to have the visibility into the devices that a lot of folks don't see currently. So those IoT devices, those OT devices, things that you're not able to run a scan on or put an agent on. Armis is not only giving you visibility into them, but also layering in, as I said before, those vulnerabilities on top of that, that's just visibility that a lot of folks today don't have. So Armis does a great job of giving you visibility and vulnerabilities and risks associated with those devices. >> So I have to ask you, when you give this demo to customers and prospects, what's the reaction? Falling out of their chair moment? Are they more skeptical? It's almost too good to be true and end to end vulnerability management is a tough nut to crack in terms of solution. >> Honestly, a lot of clients that we've had, especially within the OT and the medical side, they're blown away because at the end of the day when we can give them that visibility, as I've said, Hey, I didn't even know that those devices resided in that portion, but not only we showing them what they are and where they are and enrichment on risk factors, et cetera, but then we show them, Hey, we've worked with that vendor, whatever it may be and Rockwell, et cetera, and we know that there's vulnerabilities associated with those devices. So they just seem to be blown away by the fact that we can show them so much about those devices from behind one single console. >> It reminds me of the old days. I'm going to date myself here. Remember the old Google Maps mashup days. Customers talk about this as the Google Maps for their assets. And when you have the Google Maps and you have the Ubers out there, you can look at the trails, you can look at what's happening inside the enterprise. So there's got to be a lot of interest in once you get the assets, what's going on those networks or those roads, if you will, 'cause you got in packet movement. You got things happening. You got upgrades. You got changing devices. It's always on kind of living thing. >> Absolutely. Yeah, it's what's on my network. And more importantly at times, what's on those devices? What are the risks associated with the the applications running on those? How are those devices communicating? And then as we've seen here, what are the vulnerabilities associated with those and how can I take action with them? >> Real quick, put a plug in for where I can find the demo. Is it online? Is it on YouTube? On the website? Where does someone see this demo? >> Yeah, the Armis website has a lot of demo content loaded. Get you in touch with folks like engineers like myself to provide demos whenever needed. >> All right, Bryan, thanks for coming on this show. Appreciate, Sales Engineer at Armis, Bryan Inman. Given the demo God award out to him. Good job. Thanks for the demo. >> Thanks, thanks for having me. >> Okay. In a moment, we're going to have my closing thoughts on this event and really the impact to the business operations side, in a moment. I'm John Furrier of theCUBE. Thanks for watching. (upbeat music)

>>Hello, welcome back to the manager risk across the extended attack surface with Armas I'm John fair host of the cube. Got the demo. God here, Brian Inman sales engineer at Armit. Brian. Thanks for coming on. We're looking forward to the demo, how you doing? >>I'm doing well, John, thanks for having me, >>You know, we heard from Nair, you know, describing arm's platform, a lot of intelligence. It's like a search engine meets data at scale intelligent platform around laying out the asset map. If you will, the new vulnerability module among other things that really solves CISO's problems, a lot of great customer testimonials. And we, we got the demo here that you're gonna give us, what's the demo about what are we, what are we gonna see? >>Well, John, thanks. Great question. And truthfully, I think as NAIA has pointed out what AIS as a baseline is giving you is, is great visibility into every asset on your that's communicating within your, within your environment. And from there, what we've done is we've layered on known vulnerabilities associated with not just the device, but also what else is on the device. What's is there certain applications running on that device, the versions of those applications and what are the vulnerabilities known with that? So that's really gives you great visibility in, in terms of the devices that folks aren't necessarily have visibility into now, unmanaged devices, OT devices, OT, and critical infrastructure, medical devices, things that you're not necessarily able to actively scan or put an agent on. So not only is Armas telling you about these devices, but we're also layer layering on those vulnerabilities all passively and in real time, >>A lot of great feedback we've heard and I've talked to some of your customers, the agent list is a huge deal. The Discover's at awesome. You can see everything and, and just getting real time information. It's really, really cool. So I'm looking forward to, for the demo for our guests, take us on that tour. Let's go with the demo for the guests today. >>All right. Sounds good. So what we're looking at here is within the Armas console is just a clean representation of the passive reporting of what Armas has discovered. So we see a lot of different types of devices, you know, from your virtual machines and personal computers, things that are relatively easy to manage, but working our way down, you're able to see a lot of different of the different types of devices that are not necessarily easy to, to get visibility into things like your up systems, IP cameras, dash cams, et cetera, lighting systems, and, and today's day and age, where everything is moving to the, that smart feature. You know, it's, it's great to have that visibility into, you know, what's communicating on my network and getting that, being able to layer on the risk factors associated with it, as well as the vulnerabilities. So let's pivot over to our vulnerabilities tab and talk about the, the ADM portion, the asset vulnerability management. >>So what we're looking at is the dashboard where we're reporting a, a, another clean representation with customizable dashboards that gives you visuals and reporting and things like new vulnerabilities as they come in, you know, what are the most critical vulnerabilities that are the, the newest as they roll in the vulnerabilities by type, we have hardware, we have application, we have operating systems. As we scroll down, we can see things to break it down by vulnerabilities, by the operating system, windows, Linux, et cetera. We can take, you know, create dashes that show you views of the, the number of, of devices that are impacted by these CVEs and scrolling down. We can see, you know, what, how long have these vulnerabilities been sitting within my environment? So how, what are the oldest vulnerabilities we have here? And then also of course, vulnerabilities by applications. So things like Google Chrome, Microsoft office. >>So we're able to give a, a good representation of the amount of vulnerabilities as they're associated to the hardware and applications as well. So we're gonna dig in and take a, a deeper look at one of these vulnerabilities here. So I'm excited to talk today about where Armas ABM is, but also where it's going as well. So we're not just reporting on things like the CVSs score from, from N N VD. We're also able to report on things like the exploitability of that, right? How, how actively is this, this CVE being exploited in the wild, right? We're reporting E EPSS scores. For example, we're able to take open source information as well as a lot of our partnerships that we have with other vendors that are giving us a lot of great value of known vulnerabilities associated with the applications and with hardware, et cetera. >>But we're where we're going with. This is we're in Fu very near future releases. We're gonna be able to, to take sort of an algorithm approach of what are the most critical CVSs that we see, how exploitable are those, what are common threat actors doing with these, these CVEs have they weaponized these CVS? Are they actively using those weaponized tools to exploit these within, within other folks' environments? And who's reporting on these. So we're gonna take all of these and then really add that Armas flavor of we already know what that device is, and we can explain. And, and so can the users of it, the business criticality of that device, right? So we're able to pivot over to the matches as we see the CVEs, we're able to very cleanly view, what are, what exactly are the devices that the CVE resides on, right? >>And as you can see, we're giving you more than just an IP address or more, you know, a lot more context, and we're able to click in and dive into what exactly are these devices and how, and more importantly, how critical are these devices to, to my, my environment, if one of these devices were to go down, if it were to be a server, if you know, whatever it may be, I would wanna focus on those particular devices and ensuring that that CVE, especially if it's an exploitable CVE were to be addressed or early, earlier than, than say the others, and really be able to manage and prioritize these another great feature about it is, you know, for example, we're looking at a, a particular CVE in terms of its its patch and build number from windows 10. So the AutoSol feature that we have, for example, we've passively detected what this particular personal computer is running windows 10 and the build and revision numbers on it. >>And then once Armas passively discovers an update to that firmware and patch level, we can automatically resolve that, giving you a, a confidence that that has been addressed from that particular device. We're also able to customize and look through and potentially select a few of these, say, you know, these particular devices reside on your guest network or an employee wifi network where we don't necessarily, I don't wanna say care, but we don't necessarily value that as much as something in, you know, internally that has holds significantly more business criticality. So we can select some of these and potentially ignore or resolve for determining reasons. As you see here, be able to really truly manage and prioritize these, these CVEs. As I scroll up, I can pivot over to the remediation tab and open up each one of these. So what this is doing is essentially Arma says, you know, through our knowledge base, been able to work with the vendors and, and pull down the patches associated with these. >>And within the remediation portion, we're able to view, for example, if we were to pull down the patch from this particular vendor and apply it to these 60 devices that you see here, right now, we're able to F to view, you know, which patches are gonna gimme the most impact as I prioritize these and take care of these affected devices. And lastly, as I pivot back, go again, where we're at now is we're able to allow the, the users to customize the organizational priority of this particular CVE, to where in terms of, you know, this has, has given us a high CVSs score, but maybe for whatever reasons it may be maybe this CVE in terms of this particular logical segment of my network, I'm gonna give it a low priority for whatever the use case may be. We have compensating controls set in place that, that render this CVE, not impactful to this particular segment of my environment. >>So we're able to add that organizational priority to that CVE and where we're going, as you can see that that popped up here, but where we're going is we're gonna start to be able to apply the, the organizational priority in terms of the actual device level. Right? So what we'll see is we'll see a, a column added to here to where we'll see the, the business impact of that device, based on the importance of that particular segment of your environment or the device type, be it, you know, critical networking device, or maybe a, a critical infrastructure device, PLCs controllers, et cetera, but really giving you that passive reporting on the CVEs in terms of what the device is within your network. And then finally we do integrate with your vulnerability, vulnerability management, and scanners as well. So if you have a scanner actively scanning these, but potentially they're missing segments of your net network, or they're not able to actively scan certain devices on your network, that's the power of Armas being able to come back in and give you that visibility of not only what those devices are for visibility into them, but also what vulnerabilities are associated with those passive devices that aren't being scanned by your network today. >>So with that that's, that concludes my demo. So I'll kick it back over to you, John. >>Awesome. Great, great walk through there. Take me through what you think the most important part of that. Is it the discovery piece? Is it the interaction what's your favorite? >>Honestly, I think my favorite part about that is, you know, in terms of being able to have the visibility into the devices, that a lot of folks don't see currently. So those OT devices, those OT devices, things that you're not able to, to run a scan on or put an agent on Armas is not only giving you visibility into them, but also layering in, as I said before, those vulnerabilities on top of that, that's just visibility that a lot of folks today don't have. So Armas does a great job of giving you visibility and vulnerabilities and risks associated with those devices. >>So I have to ask you, when you give this demo to customers and prospects, what's the reaction falling outta their chair moment? Are they more skeptical? It's almost too good to be true. And the end to end vulnerability management's is a tough nut to crack in terms of solution. >>Well, honestly, a lot of clients that we've had, you know, especially within the OT and the medical side, they're, they're blown away because at the end of the day, when we can give them that visibility, as I've said, you know, Hey, I, I didn't even know that those devices resided in that, that portion, but not only are we showing them what they are and where they are and enrichment on risk factors, et cetera. But then we show them, Hey, there's a known, you know, we've worked with that vendor, whatever it may be and, you know, Rockwell, et cetera. And we know that there's vulnerabilities associated with those devices. So they just seem to be blown away by the fact that we can show them so much about those devices from behind one single console. >>You know, it reminds me of the old days. I'm gonna date myself here. Remember the old Google maps, mashup days. This is customers. Talk about this as the Google maps for their assets. And when you have the Google maps and you have the Ubers out there, you can look at the trails, you can look at what's happening inside the, inside the enterprise. So there's gotta be a lot of interest in once you get the assets what's going on, on those, on, in those, on those networks or those roads, if you will, cuz you got in packet movement, you got things happening, you got upgrades, you got changing devices. It's always on kind of living thing. >>Absolutely. Yeah. It's what's on my network. And more importantly at times what's on those devices, right? Are the, what are the risks associated with the, the applications running on those? How are those devices communicating? And then as we've seen here, what are the vulnerabilities associated with those and how can I take action with them? >>All right. Real quick, put a plug in for where I can find the demo. Is it online is on YouTube, on the website. Where does someone see this demo? >>Yeah, the Amis website has a lot of demo content loaded. Get you in touch with folks like engineers like myself to, to provide demos whenever, whenever needed. >>All right, Brian, thanks for coming on this show. Appreciate sales engineer, Armas Brian Inman, given the demo God award out to him. Good job. Thanks for the demo. >>Thanks. Thanks for having me. >>Okay. You know, in a moment we're gonna have my closing thoughts on this event and really the impact to the business operation side. In a moment I'm John fur the cube. Thanks for watching.

(upbeat ambient music) >> Hey everyone, welcome to this CUBE Conversation. I'm your host, Lisa Martin. I've got NETSCOUT guests here with me today. Eileen Haggerty joins us, the AVP of product and solutions marketing and Jason Chaffee as well, senior product manager. We're going to be talking about gaps in edge visibility. Guys, great to have you on theCube. >> Yeah, thanks Lisa, I really appreciate it. I appreciate the time to be able to talk with everyone. >> Good to be here. >> Yeah. All right, Eileen, we're going to start with you. Oh, what a last two years we have had, COVID, digital transformation massively accelerated, it also both changed networking dynamics over the last couple of years. How has that changed? >> Yeah, and that's the absolute truth. I think we've really seen it in the huge swings where people are performing their jobs right now. You know, I think when people went home two years ago to do their jobs, no one ever expected we where we would be two years later, right? There's really been a variety of different stages from totally working at home to now where you see an awful lot of hybrid work. People splitting their time between the offices and home. That's really where we're at right now. And in fact, some of the studies that we've been reading up on and seeing, majority of workers actually really prefer a hybrid work model, I can understand that. (chuckles) As well the managers believe they are going to have some of their employees that work from a remote location on a regular basis going forward too. So that becomes one of the biggest issues that we have to support them from an IT perspective and a corporate of going forward. One aspect was interesting, two thirds of high revenue growth companies are really embracing hybrid work. This is going to require a couple of things though. Business continuity has depended on this model now, remote workers have been a part of it and we need applications in the network to support that as well as it used to when they were all based in one set of buildings, right? So one of the things that we find IT executives lamenting, some think that they have a lot of confidence in being able to troubleshoot problems when employees are having them remotely, others are actually not quite so confident. So we're going to have to look at this as an industry and help them assure IT infrastructure and services are performing flawlessly so that the hybrid workforce can be successful. >> Yeah, that hybrid environment, it's kind of like must embrace at this point. But Jason, there brings some network complexity to this. The digital transformation was absolutely essential, right, the last couple of years for businesses to first survive and then to thrive, but network complexity has increased. Jason, walk us through what the communications path looks like in today's hybrid environment. >> Yeah, Lisa, it really has. It's just become more complex, you know, in today's hybrid environment and the whole digital transformation, there's really three areas of visibility or three location types if you will that they really need to have to focus on. And one is sort of that data center, cloud services edge and then there's the network edge. And now the ever expanding and growing client edge and really what's common about all of these different edges is this is where the traffic gets altered and crosses across those two domains or those multiple domains really. And so what happens there is those are areas where problems can occur and these are possibly, if not probably blind spots for IT. So when you think about these different edges, like the service edge, just as your private data center or the cloud where applications that are actually hosted or the network edge are going through colocations and WANs and through the internet and your typical kind of network throughout the whole organization. And then lastly is the client edge. And the client edge is again, just continues to grow. And this, people now working from home as Eileen was just talking about and remote offices or their home one day and a remote office the next day and whatever that might be and heck, they might be working in coffee shops or in the corporate headquarters. So it's just really added complexity. And as we get further away from the data center, we start to lose all of that infrastructure that we own and can control. And so it makes it difficult to really manage and understand that. In fact, I think that's probably one of the biggest consequences or challenges of this whole digital transformation. You know, it's made it real easy for those of us to work from home and all these new systems, and it's real simple to work from literally anywhere, but it's just made it that much more complex and challenging for the IT organization to really be able to manage and kind of provide that ubiquitous end user experience regardless of where the users are. You know, kind of last point, I was just thinking about this is, when you think about an organization that maybe has 30,000 employees and if 80,000 of those sudden, or 80% of those suddenly got sent home and had to work during COVID and the whole pandemic, and maybe they're hybrid now, well, that's 24 to 25,000 employees that are really key to your revenue and customer satisfaction. So IT organizations just simply can't afford not to invest in all of this and really try and to understand these complexities and make sure that everything's working the way it should for productivity for the company. >> That's a great point, Jason, as consumers, we are so demanding. That's I think one of the things in COVID that went away was patients and maybe it's slowly coming back but the customer satisfaction, the brand reputation, those are all things that are dependent on solid networking. And of course IT challenges, IT is challenged to to really smooth out those challenges. But Eileen, as employees and end users, we've faced a lot of challenges. I know I have in the last couple of years. Walk us through some of those main pain points that the employees and the end users have been through in the last two years. >> You couldn't be more on spot there. So we really haven't. The irony is all of us on this call have been amongst the ones who have probably suffered from some of these issues as well. You know, one of the things that we found during this period is all of us were coming in over VPN or on video desktop interfaces like Citrix and others. And we were connecting to data center applications and software as service apps for everything. You know, it could be customer order processing, customer records, emails, and in any time or place that we were accessing, we could have slow responsiveness, we could have log issues, we had timeouts. I think one of the interesting ones was communications apps that became huge overnight, Teams, Zoom, WebEx, and those have had issues for us too. They had connection issues, poor quality voice, terrible video. So it became a very frustrating period of time in many cases for employees, they're there to deliver customer care, protect the corporate revenue. But networks and application disruptions counter that. So leading to productivity loss, that's a big issue and a concern. And certainly one of the bigger worries is customer dissatisfaction. But I'd say, you know what's fascinating here too is IT staffs were equally frustrated but for different reasons during this period. They were combating network and application issues for these employees. And usually, they were used to everybody being in one location or to a few buildings and they had total control if you will. Now they're managing 100s and sometimes 1000s of locations known as homes and those staff members we've heard them say things like, they felt like they were losing sight of the remote workforce or simply losing control. And hybrid work models, as they become the norm for many of these organizations, groups of IT professionals still have to ensure the quality of service performance for those employees wherever they do their jobs, home, remote offices or headquarters, and for any application wherever it happens to be hosted. So this is a big challenge. >> Big challenge for IT. You talked about that customer satisfaction. Reminded me of one time I was on the phone with a contact center and I heard a dog barking in the background and I first I thought was that my dog and I thought, no, that customer contact center person is also stuck working from home. Talk about losing control of your environment. But Jason, next question is actually for both of you and Jason, I'll start with you, how does IT assure performance? I mean, it's hard to manage, talk to us about that. >> Well, yeah, Lisa, really kind of as Eileen just said, we used to all sort of be in the same common area in the headquarters. And so people, you know, the IT organization was looking at things like the data center or server farms or internet links just going into and out of the headquarters or off to the data center itself. And so, but that's just not really the case anymore. And as people continue again, as I said before, work from literally anywhere, it's just made the ecosystem that much more challenging and much more complex and bigger frankly to try to manage. And so I think what you really need to do is you see something where it's challenging because the old adage is you just can't manage what you can't see. And so that's become that challenge. And I think what you need is visibility at every edge including up to the client edge that we've been talking about so that you can do things like track and trend volumes and bandwidth and capacity and application utilization and all the different things that make up that end user experience. You need that visibility from all of those locations to really understand and see what's going on from there. >> Eileen, what's your take? >> Well, Jason makes a bunch of valid points. I think what triggers in my mind as he was speaking was that there are other enterprises that have very specific remote locations which present themselves a very different kind of importance for value of the performance assurance. There's banks. They have financial transactions that are going on there, which are instantaneous in nature or need to be for a variety of different reasons, right? Factory plants they've been now wirelessly or WiFi driven production lines. And as a result, any disruption in that production line could have it turned off for 20 minutes an hour. And that has a deep impact to the business as well. Retail stores and distribution centers. This one rings probably for everybody, 'cause during this period of time, we were all online and we were ordering things, right? And so any issues with disruptions, slow downs from those types of remote locations for touchless pickup for the ability to go to a store or get something picked up that day, this was critical. And we all know those services broke down for one reason or another and it created a bit of a problem if you didn't have the right snack for the four year old today. >> Right, definitely the four year old losing control or losing patients, the poor parent. Jason, you talked about visibility and you said something really poignant, you can't manage what you can't see, what is needed for IT to have that visibility as this environment just scattered, what's needed to effectively manage it? >> Yeah. Lisa, you know I think as you just said, and as I said earlier, I think the real key is visibility at every edge and all of the different edges that we've talked about including the home user and it's really been impractical and expensive to instrument at every one of those, especially at all the home locations which are now everybody's home work office. And you just really can't get a view into it. And of course there's some solutions out there that sort of gives you a view of what's going on, what's that end user experience. And, but it doesn't really tell you why. And I think that's one of the key components of that. So as I think about this large new hybrid ecosystem, I think there's really three main things that you need in order to do that. And the first of all, again, is that complete visibility at every edge. And to me that means a combination of both passive and active synthetic based monitoring. So you're passive monitoring where you're actually looking at the real user traffic, and detecting trends and being able to understand what's going on there. But then you also do need, there's a time and a place for that synthetic active testing where we're getting an understanding and a baseline where we're testing continuously and automatically to understand what that end user experience is and understand what performance should look like. But as I mentioned, I think that's just not necessarily enough to do just do synthetics from those synthetic locations. I think it's really key to be able to get deep down into the wire day or the packets of that to really understand why something is happening. You know, for instance, today there might be an issue and you can say, well, I see it's a DNS issue. Hey, DNS guy, go off and try to fix this and figure out what's going on. Well, again, I think you need that visibility, you need a solution that can pull the packets back and give you that combination of both of those things. The next thing I think. >> So. >> Oh, sorry, go ahead. >> Go ahead. >> Well, the next thing I was going to say that I think that's really critical and key is tools that can manage the complexity as you go across all of these. I mean, there's just so many tools out there that are, SaaS and Ucast, your WebEx, Zoom teams, all of those. And it's just frankly, almost impossible to be an expert on all of those different solutions that you might have. And of course they have their own management platform forms that make it, so you can kind of see what's going on but being able to understand and see how to fix WebEx for instance, doesn't really help you when one of your users happens to be having a problem with teams. And so I think again, you need a solution that can go across all of those different applications to be able to see what's going on. And then thirdly, I think is the key, one of the key components is service and application collaboration. And what I mean by this is you need a tool that can give you the ability to have proof and evidence that you can share with your service providers, your application providers because they're very complex, right? They all have dozens of servers in different parts of the world, in different parts of the country. And frankly, they're going to probably blame you first, they're going to say, no, this is something on your end. And it really adds to the time of troubleshooting and get resolution. But if you can actually have that data to say, hey, I can see exactly what's going on. And it's this server at this data center and it's causing high retransmissions or latency. That just makes again more of a collaborative effort but allows you to sort of put all of those things together and stop the finger pointing and blame game and be able to solve those solutions much more quickly. So again, I think it's really a combination of active and passive together all in one console or one solution that really gives you that visibility across all of the different environments that we might have today. >> All those different environments, and there still are so many. Eileen, how have you seen this? How has NETSCOUT seen this actually in practice and how have the tool that you and talked about, how is it actually helping to give the visibility, to reduce the complexity and to ensure that ultimately the end users and the employees are productive so that the customers can be happy? >> Yeah, and you know, it's interesting as he was talking, I was thinking one of the accounts that I've talked to, an organization that's based in software development and they literally have offices all over the world. The hybrid workforce model is their choice going forward. And most of those worldwide employees are part of the sales and support organization for local prospects and customers. So one of the biggest things that's critical to them is communications. And that has to be top of their concerns for quality. The other business related applications are equally important because as you're talking to them, you're pulling those services up and they are in fact using solutions for looking at those edges, the WAN links are key for visibility. They're able to look at the inbound and outbound traffic at those locations. And then what they're able to do is to do two things, one, like Jason was talking about, collaborate, work with those local WAN providers. They're all different over the world. So you really need to build a relationship with them, you have to have some evidence and they're able to do that now. It helps them cost effectively and proactively plan bandwidth changes, and that's really important too. They're also using the synthetic testing that Jason referred to. These locations have the buildings able to test for different applications that are going to be important to the business that's at that location. They do it over ethernet, so for the people with hardwired desks, they can see what the traffic experience is. And then for those that are in open spaces or conference rooms on using WiFi, they're measuring there as well. They want to make sure that no matter where you sit in the office and how you connect, the quality is the same and that's important. Bottom line, they're being able to reduce dramatically the time it's taken to troubleshoot and resolve issues as they emerge. It's great. >> That is great. And of course, as we all have that patience limitation, that speed is key there. Guys, thank you so much for joining me talking about not just the gaps in edge visibility but the ways that they can be remedied and fixed so that ultimately customer satisfaction, employee productivity, all things are harmonious. We appreciate your insights. >> Absolutely, thank you. >> Thank you. >> For Eileen Haggerty and Jason Chaffee I'm Lisa Martin, you're watching a CUBE Conversation. (upbeat ambient music)

(upbeat music) >> Welcome back to Las Vegas everybody. You're watching theCUBE coverage of AWS reinvent 2021. I tell you this place is packed. It's quite amazing here, over 20,000 people, I'd say it's closer to 25, maybe 27,000, and it's whole overflow, lots going on in the evenings. It's quite remarkable and we're really happy to be part of this. Jay Turner is here, he's the Vice President of Development and Operations, at PCCW Global. He's joined by Garrett Lowell, Vice President of Ecosystem Partnerships for the Americas at PCCW Global. Guys, welcome to theCUBE. Thanks for coming on. >> Thank you. >> Thank you so much. Jay, maybe you could take us through, for those people who aren't familiar with your company, what do you guys do, what are you all about? >> PCCW Global is the international operating wing of Hong Kong telecom. If it's outside of Hong Kong, it's our network. We've got about 695,000 kilometers of diverse cable, we've got about 43, 44 terabit of capacity came into business in 2005, if my brain is serving me correctly right now. We have a very diverse and vast portfolio ranging all the way from satellite teleports, all the way to IP transit. We're a Tier 1 service provider from that perspective as well. We do one of everything when it comes to networking and that's really, what was the basis of Console Connect, was inventing a platform to really enable our users to capitalize on our network and our assets. >> Okay. 2005, obviously you predated Cloud, you laid a bunch of fibers struck it in the ocean, I mean, global networks. There was a big trend to do that you had to think, you had to go bigger, go home in that business, (laughing) all right. Console Connect is your platform, is that right? >> Jay: Yes. >> So explain- >> Yeah, sorry, Console Connect is a software defined interconnection platform. We built a user self-service portal. Users can allocate ports, they get the LOAs issued to them directly from the platform. And then once they've got an active port or they've come in via one of our partnerships, they can then provision connectivity across our platform. That may be extending to their data centers or extending to their branch office, or it could be building a circuit into the Cloud via direct connect, could be building a circuit into an internet exchange. All of those circuits are going to be across that 685,000 kilometers of diverse fiber rather than going across the public internet. >> When you started, it took some time obviously to build out that infrastructure and then the Cloud came into play, but it was still early days, but it sounds like you're taking the AWS Cloud model and applying that to your business, eliminate all that undifferentiated heavy lifting, if you will, like the visioning in management. >> Yeah, we've heard many people, and that's kind of the impetus of this was, I want to be directly connected to my end point. And how do I do that? AWS, yes, they had direct connect, but figuring out how to do that as an enterprise was challenging. So we said, hey, we'll automate that for you. Just tell us what region you want to connect to. And we'll do all the heavy lifting and we'll just hand you back a villain tag. You're good to go. So it's a classic case, okay. AWS has direct connect. People will go, oh, that's directly competitive, but it's now you're adding value on top of that. Right? >> Yeah. >> Describe where you fit, Garrett, inside of the AWS ecosystem. You look around this hall and it's just a huge growing ecosystem, where you fit inside of that ecosystem and then your ecosystem. What's that like? >> Where we fit into the AWS ecosystem, as Jay alluded to, we're adding value to our partners and customers where they can come in, not only are they able to access the AWS platform as well as other Cloud platforms, but they're also able to access each other. We have a marketplace in our platform, which allows our customers and partners to put a description of their services on the marketplace and advertise their capabilities out to the rest of the ecosystem of PCCW Global and Console Connect. >> And you're doing that inside of AWS, is that right or at least in part? >> No, that's not inside of AWS. >> So your platform is your platform. >> Yes. >> Your relationship with AWS is to superpower direct connect. Is that right or? >> So we're directly connected to AWS throughout the globe. And this allows our customers and partners to be able to utilize not only the PCCW global network, but also to expand that capability to the AWS platform in Cloud. >> So wherever there's a Cloud, you plug into it, okay? >> Garrett: That's correct. >> Jay: Yeah. And then another advantage, the customer, obviously doesn't have to be directly co-located with AWS. They don't have to be in the same geographical region. If for some reason you need to be connected to U.S. west, but you're in Frankfurt, fine, we'll back all the traffic for you. >> Dave: Does that happen a lot? >> It actually does. >> How come? What's the use case there. >> Global diversity is certainly one of them just being able to have multiple footprints. But the other thing that we're seeing more of late is these Cloud-based companies are beginning to be attracted to where their customers are located. So they'll start seeing these packets of views and they'll go, well, we're going to go into that region as well, stand up a VPC there. We want our customers then being able to directly connect to that asset that's closest to them. And then still be able to back call that traffic if necessary or take it wherever. >> What's the big macro trends in your business? Broadly you see cost per bit coming down, you see data consumption and usage going through the roof. How does that affect you? What are some of the big trends that you see? >> I think one of the biggest ones and one that we targeted with Console Connect, we were hearing a lot of customers going, the world's changing so dynamically. We don't know how to do a one-year forecast of bandwidth, much less a three-year, which is what a lot of contracts are asking us for. So we said, hey, how about one day? Can you do one day? (Dave laughs) Because that's what our granularity is. We allow for anything from one day up to three years right now, and then even within that term, we're dynamic. If something happens, if suddenly some product goes through the roof and you've suddenly got a spike in traffic, if a ship drags its anchor through a sub sea cable, and suddenly you're having to pivot, you just come into the platform, you click a couple of buttons, 20 seconds later, we've modified your bandwidth for you or we've provisioned a new circuit for you, we've got your backup going, whatever. Really at the end of the day, it's the customer paying for their network, so the customer should be the one making those decisions. >> How's that affect pricing? I presume or so, I can have one day to a three-year term, for example if I commit to three years, I get a better deal. Is that right, or? >> You do, but at the end of the day, it's actually pretty much a moderate, a better deal. We don't want to force the hand of the customer. If you signed a 12 month contract with us, we're going to give you a 3% discount. >> So it's not really, that's not a motivation to do it. It's just (indistinct) reduce the transaction complexity. And that's why you will sign up for a longer term not to get the big discount. >> Correct. And then, like I said, even within a longer contract, we're still going to allow you to flex and flow and modify if you need to, because it's your network. >> What kind of constraints do you put on that? Do I have to commit to a flow? And then everything above that is, I can flex up. Is that how it works? >> Yeah. >> Okay. And then, the more I commit to, the better the deal is, or not necessarily? >> No, it's pretty much flat rate. >> Okay, I'm going to commit and I'm going to say, all right, I know I'm going to use X, or sign up for that and anything over it, you're pretty flexible, I might get a few points if I sign up for more, somebody might want to optimize that if they're big enough. >> And another really neat advantage, the other complaint we heard from customers, they go, I need three different direct connect, I need to be connected to three different parties, but I don't want to run three different cross-connects and I don't want to have three different ports. That's just an expense and I don't want. And we, fine, take your one gig port run one gig of services on it. If that's 20 different services, we're fine. We allow you to multiplex your port and provision as- >> So awesome. I love that model. I know some software companies who I would recommend to take a look at that pricing model. So Garrett, how do you segment the ecosystem? How do you look at that? Maybe you could draw and paint a picture of the idea of partners and what they look like. I know there's not just one category, but, >> Sure. Our ideal partners are internet exchangers, Cloud partners and SAS providers, because a big piece of our business is migration to the Cloud, and the flexibility of our platform allows and encourages our SAS providers and SI partners to perform migration to the Cloud much easier in a flexible format for their customers. >> What can you tell us, any kind of metrics you can give us around your business to give a sense of the scope, the scale? >> Well, of our business, (Dave laughs) one of the driving factors here, Gardner says that about 2023, I think, 40% of the enterprise workloads will be deployed in the Cloud, which is all fine and dandy, except in my head, you're just trading one set of complexities for another. Instead of having everything in a glass house and being able to understand that, now you're going, it's in the Cloud, now I need to manage my connectivity there. wait a minute, are my security policies still the same? Do they apply if I'm going across the public internet? What exposure have I just bought into myself to try to run this? The platform really aims at normalizing that as much as possible. If you're directly connected to AWS, at the end of the day, that's a really long ethernet cable. So your a glass house just got a lot bigger, but you're still able to maintain and use the exact same policies and procedures that you've been using. That's really one of our guiding principles, is to reduce that complexity and make it very simple for the user. >> I understand that, cause in the early days of Cloud, a lot of enterprises, the CIOs, they were concerned about security, then I think they realized, ah, AWS has pretty good security. CIA is using it. But still people would say to me, it's not that it's best security, it's just different. You know, we move slow, Dave. How do you accommodate, there's that diversity, I mean, AWS is obviously matured, but are you suggesting that you can take my security edicts in my glass house and bring those into your networks and ultimately into the Cloud? Is that how it works? >> That's the goal. It's not going to be a panacea more than likely, but the more edicts that we can allow you to bring across and not have to go back and revamp and, the better for you as a customer and the better really for us, because it normalizes things, it makes it much easier for us to accommodate more and more users. >> And is it such now in the eco, is all the diversity in the ecosystem, is it such that there's enough common patterns you guys can accommodate most of those use cases? >> Yeah, absolutely. One of the key components is the fact that the platform runs on our MPLS network, which is inherently secure. It's not on the public internet anywhere. We do have internet on demand capability. So in the event that a customer wants access to the internet, no problem. We can accommodate this. And we also have 5G capability built into the platform to allow flexibility of location and flexibility of, I would say, standing up new customer locations. And then the other component of the security is the fact that the customers can bring their own security and apply anywhere. We're not blocking, we don't have any port filters or anything of this nature. >> If would think 5G actually, I could see people arguing both sides, but my sense is 5G is going to be a huge driver for your business cause it's going to just create so much more demand for your services, I think. I can see somebody arguing the counter about it. What's your point of view on that? >> No, I think that's a fair assessment. I think it's going to drive business for everyone here on the show floor and it's pushing those workloads more toward the edge, which is not an area that people were typically concerned with. The edge was just the door that they walked through. That's becoming much different now. We're also going to start seeing, and we're already seeing it, huge trends of moving that data at the edge rather than bringing it all the way back to a central warehouse and help ending it. The ability to have a dynamic platform where you can see exactly what your network's doing and in the push of a button, modify that, or provision new connectivity in response to how your business is performing. >> Yeah, ultimately it's all about the applications that are going to be driving demand for more data. That's just a tailwind for you guys. >> Yeah. You look at, some of the car companies are coming on, Tesla, you're drive around with like eight CPUs and I think communicating back over the air. >> Dave: Yeah, right. >> You start scaling that and you start getting into some some real bottlenecks. >> Amazing business you guys having obviously capital intensive, but once you get in there, you got a big moat. That is a matter of getting on a flywheel and innovating. Guys, congratulations on all the progress and so much for coming on theCUBE. >> Thanks for the time. >> Thank you very much. >> Great to meet you guys. Good luck. All right, thank you for watching. This is Dave Vellante for theCUBE, the leader in High-Tech Coverage. We'll be right back. (upbeat music)

(upbeat music) >> Welcome back to Las Vegas everybody. You are watching theCube's coverage of AWS reinvent 2021. I'll tell you this place is packed. It's quite amazing here over 20,000 people, I'd say it's closer to 25, maybe 27,000. And there's a little overflow, lots going on in the evenings. It's quite remarkable. And we're really happy to be part of this. Jay Turner is here, he's the vice president of development and ops at PCCW Global. He's joined by Garrett Lowell, vice-president of ecosystem partnerships for the Americas at PCCW Global. Guys, welcome to theCube. Thanks for coming on. >> Thank you so much. >> So, Jay, maybe you could take us through for those people who aren't familiar with your company, what do you guys do? What do you all about? >> Yes, so PCCW Global is the international operating wing of Hong Kong Telecom. So if it's outside of Hong Kong, it's our network. We've got about 695,000 kilometers of diverse cable. We've got about 43, 44 terabit of capacity. Came into business in 2005 if my brain is serving me correctly right now. So we have a very diverse and vast portfolio ranging all the way from satellite teleports, all the way to IP transit. We're a tier one service provider from that perspective as well. So we do one of everything when it comes to networking and that's really what was the basis of Console Connect, was inventing a platform to really enable our users to capitalize on that our network and our assets. >> Okay, so 2005, obviously you predated cloud, you laid a bunch of fibers, it's getting in the ocean, I mean, global networks, I mean, there was a big trend to do that and you had to think, you had to go bigger or go home and that business. >> Jay: Yes you had to do. >> So and Console Connect is your platform, is that right? So explain. >> Yeah, sorry. Yeah, Console Connect is our software defined interconnection platform. So we built a user self-service portal. Users can allocate ports, they get the LOAs issue to them directly from the platform. And then once they've got an active port or they've come in via one of our partnerships, they can then provision connectivity across our platform. And that may be extending to their data centers or extending or their branch office, or it could be building a circuit into the cloud via direct connect, could be building a circuit into an internet exchange. And all of those circuits are going to be across that 685,000 kilometers of diverse fiber rather than going across the public internet. >> So, when you started, it took some time obviously to build out that infrastructure and then the cloud came into play, but it was still early days, but it sounds like you're taking the cloud model, AWS Cloud model and applying that to your business, eliminate all that undifferentiated, heavy lifting, if you will, the visioning and management. >> Yeah, we've heard many people and that's kind of the impetus of this was, I want to be directly connected to my end point. And how do I do that? And AWS, yes, they had direct connect, but figuring out how to do that as an enterprise was challenging. So we said, hey, we'll automate that for you. Just tell us what region you want to connect to. And we'll do all the heavy lifting, and we'll just hand you back a villain tag. You're good to go. >> So it's a classic case of, okay, AWS has direct connect, people they go, "Ah, that's directly competitive, but it's not, you're adding value on top of that." Right. So describe where you fit Garrett inside of the AWS ecosystem. You look around this hall and it's just a huge growing ecosystem, where you fit inside of that ecosystem and then your ecosystem, what's that like? >> Okay, so where we fit into the AWS ecosystem, as Jay alluded to, we're adding value to our partners and customers where they can come in, not only are they able to access the AWS platform as well as other cloud platforms, but they're also able to access each other. So we have a marketplace in our platform, which allows our customers and partners to put a description of their services on the marketplace and advertise their capabilities out to the rest of the ecosystem of PCCW Global and Console Connect. >> Okay, so and you're doing that inside of AWS? I that right? Or at least in part? >> No, that's not inside of AWS. >> Okay, so your platform is your platform. >> Yes. >> And then, so your relationship with AWS is to sort of superpower direct connect, is that right or? >> So we're directly connected to AWS throughout the globe. And this allows our customers and partners to be able to utilize not only the PCCW Global network, but also to expand that capability to the AWS platform in clouds. >> Wherever there's a cloud you plug into it? Okay. >> That's correct. >> And then another advantage there is the customer, obviously doesn't have to be directly co-located with AWS. They don't have to be in the same geographic region. If for some reason you need to be connected to US West, but you're in Frankfurt, fine, we'll back all the traffic for you. >> Does that happen a lot? >> It actually does. >> How come? Why, what's the use case there? >> Global diversity is certainly one of them, just being able to have multiple footprints. But the other thing that we're seeing more of late is these cloud-based companies are beginning to kind of be attracted to where their customers are located. So they'll start seeing these pockets of use and they'll go, well, okay, we're going to go into that region as well, stand up a VPC there. And so then we want to our customers then being able to directly connect to that asset, that's closest to them. And then still be able to back call that traffic if necessary or take it wherever. >> What are the big, sort of macro trends in your business? I mean, broadly you see cost per bit coming down, you see data consumption and usage going through the roof. How does that affect you? What are some of the big trends that you see? >> I think one of the biggest ones and one that we targeted with Console Connect, we were hearing a lot of customers going, the world's changing so dynamically. We don't know how to do a one-year forecast of bandwidth, much less a three-year, which is what a lot of contracts are asking us for. So we said, hey, how about one day? Can you do one day? (Dave laughing) Because that's what our granularity is. So we allow for anything from one day up to three years right now, and then even within that term, we're dynamic. So if something happens, suddenly some product goes through the roof and you've suddenly got a spike in traffic. If a ship drags its anchor through a sub sea cable, and suddenly you're having to pivot, you just come into the platform, you click a couple of buttons, 20 seconds later, we've modified your bandwidth for you, or we've provisioned a new circuit for you. We've got your backup going whatever. Really at the end of the day, it's the customer paying for their network, so the customer should be the one making those decisions. >> How's that affect pricing? I presume, so I can have one date or a three-year term. Presume if I commit to three years, I get a better deal, is that right or? >> You do, but I mean, at the end of the day, it's actually pretty much a moderate, a better deal. We don't want to force the hand of the customer. So yeah, if you signed a 12 month contract with us, we're going to give you a 3% discount. >> Yeah, so it's not really, that's not a motivation to do it. Is just you want to reduce the transaction complexity. And that's why you would sign up for a longer term not to get the big discount. >> Correct. And then, like I said, even within a longer contract, we're still going to allow you to flex and flow and modify if you need to because it's your network. >> What kind of constraints do you put on that? Do I have to commit to a floor and then everything above that is I can flex up? Is that how it works? Okay. And then the more I commit to the better the deal is, or not necessarily? >> No, it's pretty much flat, right. >> So, okay. So I'm going to come in and I'm going to say, all right, I know I'm going to use X, I'll sign up for that and anything over it. You're pretty flexible, I might get a few points if I sign up for more, somebody might want to optimize that if they're big enough. >> And another really neat advantage, and the other complaint we heard from customers, they go, I need three different direct connect, or I need to be connected to three different parties, but I don't want to run three different cross-connects and I don't want to have three different ports. That's just an expense I don't want. And we say, fine, take your one gig port, run one gig of services on it, if that's 20 different services, we're fine. So we allow you to multiplex your port and provision- >> It's awesome. I love that model. I know some software companies who I would recommend take a look at that pricing model. So, Garrett, how do you segment the ecosystem? How do you look at that way? Maybe you could draw paint a picture sort of the, the ideal partners and what they look like. I know there's not just one category, but. >> Sure, so our ideal partners are internet exchanges, cloud partners, and SAS providers, because a big piece of our business is migration to the cloud. And the flexibility of our platform allows and encourages our SAS providers and SI partners to perform migration to the cloud much easier and flexible in a flexible format for their customers. >> Yeah, so what can you tell us, any kind of metrics you can give us around your business to give a sense of the the scope, the scale. >> Well, of our business, kind of one of the driving factors here, Gardner says that about 2023, I think 40% of the enterprise workloads will be deployed in the cloud, which is all fine and dandy, except in my head, you're just trading one set of complexities for another. So now, instead of having everything in a glass house and being able to kind of understand that now you're going, well, okay, so it's in the cloud now I need to manage my connectivity there. And, oh, well, wait a minute, are my security policies still the same? Do they apply if I'm going across the public internet? What exposure have I just, bought into myself to try to run this? So the platform really aims at normalizing that as much as possible. If you're directly connected to AWS, at the end of the day, that's a really long ethernet cable. So you're a glass house just got a lot bigger, but you're still able to maintain and use the exact same policies and procedures that you've been using. So that's really one of our guiding principles is to reduce that complexity and make it very simple for the user. >> Well, I don't understand, 'cause in the early days of cloud, a lot of enterprises, CIO they were concerned about security. And I think they realized that AWS has pretty good security, well, CIA is using it. But still people would say to me, it's not that it's bad security, it's just different. We move slow, Dave. So how do you accommodate, now I don't know, does that diversity, I mean, AWS has obviously matured, but are you suggesting that you can take my security edicts in my glass house and bring those into your networks and ultimately into the cloud? Is that kind of how it works? >> That's the goal. It's not going to be a panacea more than likely, but the more edicts that we can allow you to bring across and not have to go back and revamp and the better for you as a customer and the better really for us, because it normalizes things, it makes it much easier for us to accommodate more and more users. >> It is such now in the eco, it was all the diversity in the ecosystem. Is it such that there's enough common patterns that you you guys can kind of accommodate most of those use cases? >> Yeah, absolutely. I think the, one of the key components is the fact that the platform runs on our MPLS network, which is inherently secure. It's not on the public internet anywhere. Now we do have internet on demand capability. So in the event that a customer wants access to the internet, no problem, we can accommodate this. And we also have 5G capability built into the platform to allow flexibility of location and flexibility of... I would say, standing up new customer locations. And then the other component of the security is the fact that the customers can bring their own security and apply anywhere. So we're not blocking, we don't have any port filters or anything of this nature. >> Well, I would think 5G actually, I mean, I could see people arguing both sides, but my sense is 5G is going to be a huge driver for your business, 'cause it's going to just create so much more demand for your services I think, I could see somebody arguing the counter, but what's your point of view on that? >> No. I think that's a fair assessment. I think it's going to drive business for everyone here on the show floor. And it's pushing those workloads more toward the edge, which is not an area that people were typically concerned with. The edge was just the door that they walked through. That's becoming much different now. And we're also going to start seeing, and we're already seeing it, huge trends of moving that data at the edge, rather than bringing it all the way back to a central warehouse in Hare pending it. So, again, the ability to have a dynamic platform where you can see exactly what your network's doing and in the push of a button, modify that, or provision new connectivity in response to how your business is performing. >> Yeah, and ultimately it's all about the applications that are going to be driving demand for more data. And that's just a tailwind for you guys. >> Yeah, yeah and then you look at some of the car companies are coming on, you know, Tesla, you're driving around with like eight CPU's in that thing, communicating back over the air. >> Dave: Yeah right. >> You start scaling that, and you start getting into some real bottleneck. >> Amazing business you guys having, obviously capital intensive, but once you get in there, you've got a big moat, and then it's a matter of getting on a flywheel and innovating. Guys, congratulations on all the progress and thanks so much for coming on theCube. >> Yeah. No, thanks for the time. >> Thank you very much. >> Yeah, great to meet you guys. Good luck. All right. Thank you for watching. This is Dave Vellante for theCube, the leader in high-tech coverage, right back. (upbeat music)

>> From the theCUBE Studios in Palo Alto in Boston, bringing you data-driven insights from theCUBE and ETR, this is Breaking Analysis with Dave Vellante. >> Well, it looks like hybrid cloud is finally here. We've seen a decade of posturing, marchitecture, slideware and narrow examples of hybrid cloud, but there's little question that the definition of cloud is expanding to include on-premises workloads in hybrid models. Now depending on which numbers you choose to represent IT spending, public cloud only accounts for actually less than 5% of the total pie. So the big question is, how will this now evolve? Customers want control, they want governance, they want security, flexibility and a feature-rich set of services to build their digital businesses. It's unlikely that they can buy all that, so they're going to have to build it with partners, specifically vendors, SI's, consultancies and their own developers. The tug of war to win the new cloud day has finally started in earnest between the hyperscalers and the largest enterprise tech companies in the world. Hello and welcome to this week's Wikibon CUBE insights, powered by ETR. In this Breaking Analysis, we'll walk you through how we see the battle for hybrid cloud, how we got here, where we are and where it's headed. First, I want to go back to 2009, in a blog post by a man named Chuck Hollis. Chuck Hollis, at the time, was a CTO and marketing guru inside of EMC who, remember, owned VMware. Chuck was kind of this hybrid, multi-tool player, pun intended. EMC at the time had a big stake, a lot at stake, as the ascendancy of AWS was threatening the historical models, which had defined enterprise IT. Now around that time, NIST published its first draft of a cloud computing definition which, as I recall, included language, something to the effect of accessing remote services over the public network, i.e., public IP networks. Now, NIST has essentially or since evolved that definition, but the original draft was very favorable to the public cloud. And the vendor community, the traditional vendor community, said hang on, we're in this game too. So that was 2009 when Chuck Hollis published this slide. He termed it Private Cloud, a term which he saw buried inside of a Gartner research post or research note that was not really fleshed out and defined. The idea was pretty compelling. The definition of cloud centered on control, where you, as the customer, had on-prem workloads that could span public and on-prem clouds, if you will, with federated security and a data plan that spanned the states. Essentially, you had an internal and an external cloud with a single point of control. This is basically what the hybrid cloud vision has become. An abstraction layer that spans on-prem and public clouds and we can extend that across clouds and out to the edge, where a customer has a single point of control and federated governance and security. Now we know this is still aspirational, but we're now seeing vendor offerings that put forth this promise and a roadmap to get there from different points of view, that we're going to talk about today. The NIST definition now reads cloud computing is a model for enabling ubiquitous, convenient on-demand network access to a shared pool of configurable computing resources, e.g., network server storage, applications and services, that can be rapidly provisioned and released with minimal management effort or service provider interaction. So there you have it, that is inclusive of on-prem, but it took the industry a decade plus to actually get where we are today. And they did so by essentially going to school with the public cloud offerings. Now in 2018, AWS announced Outposts and that was another wake up call to the on-prem community. Externally, they pointed to the validation that hybrid cloud was real. Hey, AWS is doing it so clearly they've capitulated, but most on-prem vendors at the time didn't have a coherent offering for hybrid, but the point is the on-prem vendors responded as they saw AWS moving past the demilitarized zone into enemy lines. And here's what the competitive landscape of hybrid offerings looks like today. All three US-based hyperscalers have an offering or multiple offerings in various forms, Outposts from Amazon and other services that they offer, Google Anthos and Azure Arc, they're all so prominent, but the real action today is coming from the on-prem vendors. Every major company has an offering. Now most of these stemmed from services-led and finance-led initiatives, but they're evolving to true Azure Service models. HPE GreenLake is prominent and the company's CEO, Antonio Neri, is putting the whole company behind Azure Service. HPE claims to be the first, it uses that in its marketing, with such an Azure Service offering, but actually Oracle was their first with Cloud@Customer. You know, possibly Microsoft could make a claim to being early as well, but it really doesn't matter. Let's see, Dell has responded with Apex and is going hard after this opportunity. Cisco has Cisco Plus and Lenovo has TruScale. IBM also has a long services and finance-led history and has announced pockets of Azure Service in areas like storage. And Pure Storage is an example that we chose of a segment player, of course within storage, that has a strong Azure Service offering, and there are others like that. So the landscape is getting very busy. And so, let's break this down a bit. AWS is bringing its programmable infrastructure model and its own hardware to what it calls the edge. And it looks at on-prem data centers as just another edge node. So that's how they're de-positioning the on-prem crowd, but the fact is, when you really look at what Outposts can do today, it's limited, but AWS will move quickly so expect a continued rapid evolution of their model and the services that are supported on Outposts. Azure gets its hardware from partners and has relationships with virtually everyone that matters. Anthos is, as well, a software layer and Google created Kubernetes as the great equalizer in cloud. And it was a nice open source gift to the industry and has obviously taken off. So the cloud guys have the advantage of owning a cloud. The pure on-prem players, they don't, but the on-prem crowd has rich stacks, much richer and more mature in a lot of areas, as it relates to supporting on-premises workloads and much more so than the cloud players, but they don't have mature cloud stacks. They're kind of just getting started with things like subscription billing and API-based microservices offerings. They got to figure out Salesforce compensation and just the overall Azure service mentality versus the historical product box mentality, and that takes time. And they're each coming at this from their respective different points of view and points of strength. HPE is doing a very good job of marketing and go-to market. It probably has the cleanest model, enabled by the company's split from HP, but it has some gaps that it's needed to fill and it's doing so through acquisitions. Ezmeral, for example, is it's new data play. It just bought Zerto to facilitate backup as a service. And it's expanded partnerships to fill gaps in the portfolio. Some partnerships, which they couldn't do before because it created conflicts inside of HPE or HP. Dell is all about the portfolio, the breadth of the portfolio, the go-to-market prowess and its supply chain advantage. It's very serious about Azure Service with Apex and it's driving hard to win that day. Cisco comes at this from a huge portfolio and of course, a point of strength and networking, which maybe is a bit tougher to offer as a service, but Cisco has a large and fast growing subscription business in collaborations, security and other areas, so it's cloud-like in that regard. And Oracle, of course, has the huge advantage of an extremely rich functional stack and it owns a cloud, which has dramatically improved in the past few years, but Oracle is narrow to the red stack, at least today. Oracle, if it wanted to, we think, could dominate the database cloud, it could be the database cloud, especially if it decided to open its cloud to competitive database offerings and run them in the Oracle cloud. Hmm. Wonder if Oracle will ever move in that direction. Now a big part of this shift is the appeal of OPEX versus CAPEX. Let's take a look at some ETR data that digs a bit deeper into this topic. This data is from an August ETR drill down, asking CIOs and IT buyers how their budgets are split between OPEX and CAPEX. The mid point of the yellow line shows where we are today, 57% OPEX, expecting to grow to 63% one year from now. That's not a huge difference, there's not a huge difference when you drill into global 2000, which kind of surprised me. I thought global 2000 would be heavier CAPEX, but they seem to be accelerating the shift to OPEX slightly faster than the overall base, but not really in a meaningful way. So I didn't really discern big differences there. Now, when you dig further into industries and look at subscription versus consumption models for OPEX, you see about 60/40 favoring subscription models, with most industry slowly moving toward consumption or usage based models over time. There are a couple of outliers, but generally speaking, that's the trend. What's perhaps more interesting is when you drill into subscription versus usage based models by product area, and that's what this chart shows. It shows by tech segment, the percent subscription, that's the blue, versus consumption or usage based, that's the gray bars, yellow being indifferent or maybe it's I don't know. What stands out are two areas that are more usage heavy, consumption heavy. That's database, data warehousing, and IS. So database is surely weighted by companies like Snowflake and offerings like Redshift and other cloud databases from Azure and Google and other managed services, but the IS piece, while not surprising, is, we think, relevant because most of the legacy vendor Azure Service offerings are borrowing from a SaaS-oriented subscription model with a hardware twist. In other words, as a customer, you're committing to a term and a minimum spend over the life of that term. You're locked in for a year or three years, whatever it is, to account for the hardware and headroom the vendor has to install because they want to allow you to increase your usage. So that's the usage based model. See, you're then paying by the drink for that consumption above that minimum threshold. So it's a hybrid subscription consumption model, which is actually quite interesting. And we've been saying, what would really be cool is if one of the on-prem penguins on the iceberg would actually jump in and offer a true consumption model right out of the box, as a disruptive move to the industry and to the cloud players, and take that risk. And I think that might happen once they feel comfortable with the financial model and they have nailed the product market fit, but right now, the model is what it is. And even AWS without post requires a threshold and a minimum commitment. So we'd love to see someone take that chance and offer true cloud consumption pricing to facilitate more experimentation and lower risk for the customer entry points. Now let's take a look at some of these players and see what kind of spending momentum they have. This is our popular XY chart-view that plots net score or spending velocity on the x-axis and market share or pervasiveness in the data set on the... Oh, sorry, net score or spending momentum on the y-axis and pervasiveness or market share on the x-axis. Now this is cut by cloud computing vendors, as defined by the customers responding. There were nearly 1500 respondents in the ETR survey, so a couple of points here. Note the red line is the elevated line. In other words, anything above that is considered really robust momentum. And no surprise, Azure, AWS and Google are above that line. Azure and AWS always battle it out for top share of voice in the x-axis in this survey. Now this, remember, is the July survey, but ETR, they gave me a sneak peek at the October results that they're going to be releasing in the coming week and Dell cloud and VMware cloud, which is VCF and maybe some other components, not VMware cloud and AWS, that's a separate beast, but those two are moving up in the y-axis. So they're demonstrating spending momentum. IBM is moving down and Oracle is at a respectable 20% on the y-axis. Now, interestingly, HPE and Lenovo don't show up in the cloud taxonomy, in that cloud cut, and neither does Cisco. I believe I'm correct in that this is an open-ended question, i.e., who are your cloud suppliers? So the customers are not resonating with that messaging yet, but I'm going to double check on that. Now to widen the aperture a bit, we said let's do a cut of the on-prem and cloud players within cloud accounts, so we can include HPE and Cisco and see how they're doing inside of cloud accounts. So that's what this chart does. It's a filter on 975 customers who identify themselves as cloud accounts. So here we were able to add in Cisco and HPE. Now, Lenovo still doesn't show up on the data. It shows up in laptops and desktops, but not as prominent in the enterprise, not prominent at all, but HPE Ezmeral did show up and it's moving forward in the October survey, again, part of the sneak peek. Ezmeral is HPE's data platform that they've introduced, combining the assets of MapR, BlueData and some other organic development. Now, as you can see, HPE and Cisco, they show up on the chart, as I said, and you can see the rope in the tug of war is starting to get a little bit more taut. The cloud guys have momentum and big account presence, but the on-prem folks also have big footprints, rich stacks and many have strong services arms, and a lot of customer affinity. So let's wrap with some comments about how this will shake out and what's some of the markers we can watch. Now, the first thing I'll say is we're starting to hear the right language come out of the vendor community. The idea that they're investing in a layer to abstract the underlying complexity of the clouds and on-prem infrastructure and turning the world into, essentially, a programmable interface to resources. The question is, what about giving access through that layer to underlying primitives in the public cloud? VMware has been very clear on this. They will facilitate that access. I believe Red Hat as well. So watch to the degree in which the large on-prem players are enabling that access for developers. We believe this is the right direction overall, but it's also very hard and it's going to require lots of resources and R & D. I would say at this point that each company has its respective strengths and weaknesses. I see HPE mostly focused today on making its on-prem offerings work like a cloud, whereas some of the others, VMware, Dell and Cisco, are stressing to a greater degree, in my view, enabling multi-cloud and edge connections, cross connections. Not that HPE isn't open to that when you ask them about it, but its marketing is more on-prem leaning, in my opinion. Now all of the traditional vendors, in my view, are still defensive about the cloud, although I would say much less so each day. Increasingly, they look at the public cloud as an opportunity to build value on top of that abstraction layer, if you will. As I said earlier, these on-prem guys, they all have ways to go. They're in the early stages of figuring out what a cloud operating model looks like, how it works, what services to offer, how to pay sellers and partners, but the public cloud vendors, they're miles ahead in that regard, but at the same time, they're navigating into on-prem territory. And they're very immature, in most cases. So how do they service all this stuff? How do they establish partnerships and so forth? And how do they build stacks on prem that are as rich as they are in the cloud? And what's their motivation to do that? Are they getting pulled, digging their heels in? Or are they really serious about it? Now, in some respects, Oracle is in the best position here in terms of hybrid maturity, but again, it's narrowly focused on the Red Stack. I would say the same for Pure Storage, more mature as a service, but narrowly focused, of course, on storage. Let's talk marketplace and ecosystems. One of the hallmarks of public clouds is optionality of tooling. Just all you do is go to the AWS Marketplace and you'll see what I mean. It's got this endless bevy of choices. It's got one of everything in there and you can buy directly from your AWS Console. So watch how the hybrid cloud plays out in terms of partner inclusion and ease of doing business, that's another sign of maturity. Let's talk developers and edge. This is by far the most important and biggest hole in the hybrid portfolios, outside the public cloud players. If you're going to build infrastructure as code, who do you expect to code it? How are the on-prem players cultivating developer communities? IBM paid 34 billion to buy its way in. Actually, in today's valuation terms, you might say that's looking like a good play, but still, that cash outlay is equal to one third of IBM's revenue. So big, big bet on OpenShift, but IBM's infrastructure strategy is fragmented and its cloud business, as IBM reports in its financial statements, is a services-heavy, kitchen sink set of offerings. It's very confusing. So they got to still do some clean up there, but they're serious about the architectural battle for hybrid cloud, as Arvind Krishna calls it. Now VMware, by cobbling together the misfit developer toys of the remnants from the EMC Federation, including Pivotal, is trying to get there. You know, but when you talk to customers, they're still not all in on VMware's developer affinity. Now Cisco has DevNet, but that's basically CCIE's and other trained networking engineers learning to code in languages like Python. It's not necessarily true devs, although they're upskilling. It's a start and they're investing, Cisco, that is, investing in the community, leveraging their champions, and I would say Dell could do the same with, for example, the numerous EMC storage admins that are out there. Now Oracle bought Sun to get Java, and that's a large community of developers, but even so, when you compare AWS and Microsoft ecosystems to the others, it's not even close in terms of developer affinity. So lots of work to be done there. One other point is Pure's acquisition of Portworx, again, while narrowly focused, is a good move and instructive of the changes going on in infrastructure. Now how does this all relate to the edge? Well, I'm not going to talk much about that today, but suffice to say, developers, in our view, will win the edge. And right now, they're coding in the cloud. Now they're often coding in the cloud and moving work on prem, wrapping them in containers, but watch how sticky that model is for the respective players. The other thing to watch is cadence of offerings. Another hallmark of cloud is a rapid expansion of features. The public cloud players don't appear to be slowing down and the on-prem folks seem to be accelerating. I've been watching HPE and GreenLake and their cadence of offerings, and watch how quickly the newbies of Azure Service can add functionality, I have no doubt Dell is going to be right there as well, as is Cisco and others. Also pay attention to financial metrics, watch how Azure Service impacts the income statements and how the companies deal with that because as you shift to deferred revenue models, it's going to hurt profitability. And I'm not worried about that at all because it won't hurt cashflow, or at least it shouldn't. As long as the companies communicate to Wall Street and they're transparent, i.e., they don't shift reporting definitions every year and a half or two years, but watch for metrics around retention and churn, RPO or Remaining Performance Obligations, billing versus bookings, increased average contract values, cohort selling, the impact on both gross margin and operating margin. These are the things you watch with SaaS companies and essentially, these big hardware players are becoming Azure Service slash SaaS companies. These are going to be the key indicators of success and the proof in the pudding of the transition to Azure Service. It should be positive for these companies, assuming they get the product market fit right, and can create a flywheel effect with their respective ecosystems and partner channels. Now I'm sure you can think of other important factors to watch, but I'm going to leave it here for now. Remember these episodes, they're all available as podcasts, wherever you listen. All you got to do is search Breaking Analysis podcast and please subscribe, check out ETR's website at etr.plus. We also publish a full report every week on wikibon.com and siliconangle.com. You can get in touch with me, email david.vellante@siliconangle.com or you can DM me @dvellante. You can comment on our LinkedIn posts. This is Dave Vellante for theCUBE Insights powered by ETR. Have a great week, everybody, stay safe, be well. And we'll see you next time. (soft music)

>>Okay, welcome back everyone. To the cubes coverage here, coop con cloud native con 2021 in person. The Cuba's here. I'm John farrier hosted the queue with Dave Nicholson, my cohost and cloud analyst, man. It's great to be back, uh, in person. We also have a hybrid event. We've got two great guests here, the founders of deep fence, sham, Krista Swami, C co-founder and CTO, and said deep line founder. It's great to have you on. This is a super important topic. As cloud native is crossed over. Everyone's talking about it mainstream, blah, blah, blah. But security is driving the agenda. You guys are in the middle of it. Cutting edge approach and news >>Like, like we were talking about John, we had operating at the intersection of the awesome desk, right? Open source security and cloud cloud native, essentially. Absolutely. And today's a super exciting day for us. We're launching something called track pepper, Apache V2, completely open source. Think of it as an x-ray or MRI scan for your cloud scan, you know, visualize this cloud at scale, all of the modalities, essentially, we look at cloud as a continuum. It's not a single modality it's containers. It's communities, it's William to settle we'll list all of them. Co-exist side by side. That's how we look at it and threat map. It essentially allows you to visualize all of this in real time, think of fed map, but as something that you, that, that takes over the Baton from the CIS unit, when the lift shift left gets over, that's when the threat pepper comes into picture. So yeah, super excited. >>It's like really gives that developer and the teams ops teams visibility into kind of health statistics of the cloud. But also, as you said, it's not just software mechanisms. The cloud is evolving, new sources being turned on and off. No one even knows what's going on. Sometimes this is a really hidden problem, right? Yeah, >>Absolutely. The basic problem is, I mean, I would just talk to, you know, a gentleman 70 of this morning is two 70 billion. Plus public cloud spent John two 70 billion plus even 3 billion, 30 billion they're saying right. Uh, projected revenue. And there is not even a single community tool to visualize all the clouds and all the cloud modalities at scale, let's start there. That's what we sort of decided, you know what, let's start with utilizing everything else there. And then look for known badness, which is the vulnerabilities, which still remains the biggest attack vector. >>Sure. Tell us about some of the hood. How does this all work cloud scale? Is it a cloud service managed service it's code? Take us out, take us through product. Absolutely. >>So, so, but before that, right, there's one small point that Sandeep mentioned. And Richard, I'd like to elaborate here, right? He spoke about the whole cloud spending such a large volume, right? If you look at the way people look at applications today, it's not just single clone anymore. It's multicloud multi regions across diverse plants, right? What does the solution to look at what my interests are to this point? That is a missing piece here. And that is what we're trying to tackle. And that is where we are going as open source. Coming back to your question, right? How does this whole thing work? So we have a completely on-prem model, right? Where customers can download the code today, install it. It can bill, we give binary stool and Shockley just as the exciting announcement that came out today, you're going to see somewhat exciting entrepreneurs. That's going to make a lot more easy for folks out there all day. Yeah, that's fine. >>So how does this, how does this all fit into security as a micro service and your, your vision of that? >>Absolutely. Absolutely. You know, I'll tell you, this has to do with the one of the continual conferences I would sort of when I was trying to get an idea, trying to shape the whole vision really? Right. Hey, what about syncretism? Microservice? I would go and ask people. They mentioned that sounds, that makes sense. Everything is becoming a microservice. Really. So what you're saying is you're going to deploy one more microservice, just like I deploy all of my other microservices. And that's going to look after my microservices. That compute back makes logical sense, essentially. That was the Genesis of that terminology. So defense essentially is deployed as a microservice. You go to scale, it's deployed, operated just like you to your microservices. So no code changes, no other tool chain changes. It just is yet another microservice. That's going to look after you talk about >>The, >>So there's one point I would like to add here, which is something very interesting, right? The whole concept of microservice came from, if you remember the memo from Jeff Bezos, that everybody's going to go, Microsoft would be fired. That gave rise to a very conventional unconditionally of thinking about their applications. Our deep friends, we believe that security should be. Now. You should bring the same unconventional way of thinking to security. Your security is all bottom up. No, it has to start popping up. So your applications on microservice, your security should also be a micro. >>So you need a microservice for a microservice security for the security. You're starting to get into a paradigm shift where you starting to see the API economy that bayzos and Amazon philosophy and their approach go Beanstream. So when I got to ask you, because this is a trend we've been watching and reporting on the actual application development processes, changing from the old school, you know, life cycle, software defined life cycle to now you've got machine learning and bots. You have AI. Now you have people are building apps differently. And the speed of which they want to code is high. And then other teams are slowing them down. So I've heard security teams just screw people over a couple of days. Oh my God, I can wait five days. No, it used to be five weeks. Now it's five days. They think that's progress. They want five minutes, the developers in real time. So this is a real deal optimum. >>Well, you know what? Shift left was a good thing. Instill a good thing. It helps you sort of figure out the issues early on in the development life cycle, essentially. Right? And so you started weaving in security early on and it stays with you. The problem is we are hydrating. So frequently you end up with a few hundred vulnerabilities every time you scan oftentimes few thousand and then you go to runtime and you can't really fix all these thousand one. You know? So this is where, so there is a little bit of a gap there. If you're saying, if look at the CIC cycle, the in financial cycle that they show you, right. You've got the far left, which is where you have the SAS tools, snake and all of that. And then you've got the center where, which is where you hand off this to ops. >>And then on the right side, you've got tech ops defense essentially starts in the middle and says, look, I know you've had thousand one abilities. Okay. But at run time, I see only one of those packages is loaded in memory. And only that is getting traffic. You go and fix that one because that's going to heart. You see what I'm saying? So that gap is what we're doing. So you start with the left, we come in in the middle and stay with you throughout, you know, till the whole, uh, she asks me. Yeah, well that >>Th that, that touches on a subject. What are the, what are the changes that we're seeing? What are the new threats that are associated with containerization and kind of coupled with that, look back on traditional security methods and how are our traditional security methods failing us with those new requirements that come out of the microservices and containerized world. And so, >>So having, having been at FireEye, I'll tell you I've worked on their windows products and Juniper, >>And very, very deeply involved in. >>And in fact, you know what I mean, at the company, we even sold a product to Palo Alto. So having been around the space, really, I think it's, it's, it's a, it's a foregone conclusion to say that attackers have become more sophisticated. Of course they have. Yeah. It's not a single attack vector, which gets you down anymore. It's not a script getting somewhere shooting who just sending one malicious HTP request exploiting, no, these are multi-vector multi-stage attacks. They, they evolve over time in space, you know? And then what happens is I could have shot a revolving with time and space, one notable cause of piling up. Right? And on the other side, you've got the infrastructure, which is getting fragmented. What I mean by fragmented is it's not one data center where everything would look and feel and smell similar it's containers and tuberosities and several lessons. All of that stuff is hackable, right? So you've got that big shift happening there. You've got attackers, how do you build visibility? So, in fact, initially we used to, we would go and speak with, uh, DevSecOps practitioner say, Hey, what is the coalition? Is it that you don't have enough scanners to scan? Is it that at runtime? What is the main problem? It's the lack of visibility, lack of observability throughout the life cycle, as well as through outage, it was an issue with allegation. >>And the fact that the attackers know that too, they're exploiting the fact that they can't see they're blind. And it's like, you know what? Trying to land a plane that flew yesterday and you think it's landing tomorrow. It's all like lagging. Right? Exactly. So I got to ask you, because this has comes up a lot, because remember when we're in our 11th season with the cube, and I remember conversations going back to 2010, a cloud's not secure. You know, this is before everyone realized shit, the club's better than on premises if you have it. Right. So a trend is emerged. I want to get your thoughts on this. What percentage of the hacks are because the attackers are lazier than the more sophisticated ones, because you see two buckets I'm going to get, I'm going to work hard to get this, or I'm going to go for the easy low-hanging fruit. Most people have just a setup that's just low hanging fruit for the hackers versus some sort of complex or thought through programmatic cloud system, because now is actually better if you do it. Right. So the more sophisticated the environment, the harder it is for the hackers, AK Bob wire, whatever you wanna call it, what level do we cross over? >>When does it go from the script periods to the, the, >>Katie's kind of like, okay, I want to go get the S3 bucket or whatever. There's like levels of like laziness. Yeah. Okay. I, yeah. Versus I'm really going to orchestrate Spearfish social engineer, the more sophisticated economy driven ones. Yeah. >>I think, you know what, this attackers, the hacks aren't being conducted the way they worked in the 10, five years ago, isn't saying that they been outsourced, there are sophisticated teams for building exploiters. This is the whole industry up there. Even the nation, it's an economy really. Right. So, um, the known badness or the known attacks, I think we have had tools. We have had their own tools, signature based tools, which would know, look for certain payloads and say, this is that I know it. Right. You get the stuff really starts sort of, uh, getting out of control when you have so many sort of different modalities running side by side. So much, so much moving attack surfaces, they will evolve. And you never know that you've scanned enough because you never happened because we just pushed the code. >>Yeah. So we've been covering the iron debt. Kim retired general, Keith Alexander, his company. They have this iron dome concept where there's more collective sharing. Um, how do you see that trend? Because I can almost imagine that the open-source man is going to love what you guys got. You're going to probably feed on it, like it's nobody's business, but then you start thinking, okay, we're going to be open. And you have a platform approach, not so much a tool based approach. So just give me tools. We all know that when does it, we cross over to the Nirvana of like real security sharing. Real-time telemetry data. >>And I want to answer this in two parts. The first part is really a lot of this wisdom is only in the community. It's a tribal knowledge. It's their informal feeds in from get up tickets. And you know, a lot of these things, what we're really doing with threat map, but as we are consolidating that and giving it out as a sort of platform that you can use, I like to go for free. This is the part you will never go to monetize this. And we are certain about disaster. What we are monetizing instead is you have, like I said, the x-ray or MRI scan of the cloud, which tells you what the pain points are. This is feel free. This is public collective good. This is a Patrick reader. This is for free. It's shocking. >>I took this long to get to that point, by the way, in this discussion. >>Yeah, >>This is this timing's perfect. >>Security is collective good. Right? And if you're doing open source, community-based, you know, programs like this is for the collector group. What we do look, this whole other set map is going to be open source. We going to make it a platform and our commercial version, which is called fetch Stryker, which is where we have our core IP, which is basically think about this way, right? If you figured out all the pain points and using tech map, or this was a free, and now you wanted the remedy for that pain feed to target a defense, we targeted quarantining of those statin workloads and all that stuff. And that's what our IP is. What we really do there is we said, look, you figured out the attack surface using tech fabric. Now I'm going to use threat Stryker to protect their attacks and stress >>Free. Not free to, or is that going to be Fort bang? >>Oh, that's for, okay. >>That's awesome. So you bring the goodness to the party, the goods to the party, again, share that collective, see where that goes. And the Stryker on top is how you guys monetize. >>And that's where we do some uniquely normal things. I would want to talk about that. If, if, if, if you know public probably for 30 seconds or so unique things we do in industry, which is basically being able to monitor what comes in, what goes out and what changes across time and space, because look, most of the modern attacks evolve over time and space, right? So you go to be able to see things like this. Here's a party structure, which has a vulnerability threats. Mapper told you that to strike. And what it does is it tells you a bunch of stress has a vulnerable again, know that somebody is sending a Melissa's HTP request, which has a malicious payload. And you know what, tomorrow there's a file system change. And there is outbound connection going to some funny place. That is the part that we're wanting this. >>Yeah. And you give away the tool to identify the threats and sell the hammer. >>That's giving you protection. >>Yeah. Yeah. Awesome. I love you guys love this product. I love how you're doing it. I got to ask you to define what is security as a microservice. >>So security is a microservice is a deployment modality for us. So defense, what defense has is one console. So defense is currently self posted by the customers within the infrastructure going forward. We'll also be launching a SAS version, the cloud version of it. But what happens as part of this deployment is they're running the management console, which is the gooey, and then a tiny sensor, which is collecting telemetric that is deployed as a microservice is what I'm saying. So you've got 10 containers running defenses level of container. That's, that's an eight or the Microsoft risk. And it utilizes, uh, EDP F you know, for tracing and all that stuff. Yeah. >>Awesome. Well, I think this is the beginning of a shift in the industry. You start to see dev ops and cloud native technologies become the operating model, not just dev dev ops are now in play and infrastructure as code, which is the ethos of a cloud generation is security is code. That's true. That's what you guys are doing. Thanks for coming on. Really appreciate it. Absolutely breaking news here in the queue, obviously great stuff. Open source continues to grow and win in the new model. Collaboration is the cube bringing you all the cover day one, the three days. I'm Jennifer, your host with Dave Nicholson. Thanks for watching.

>>Okay, okay, we're back, you're watching the cubes, continuous coverage of HBs Green Lake announcement. One of the things that we said on the Cuban. We first saw Green Lake was let's watch the pace at which H P E delivers new servants is what's that cadence like? Because that's a real signal as to the extent that the company's leading into the cloud and today we're covering that continued expansion. We're here with Tom Black, who was the general manager of HPC storage and Omar assad, who's the storage platform lead for cloud data services at Hewlett Packard Enterprise gentlemen welcome. It's good to see you. >>Thanks Dave. Thanks for having us today. Good to see you. >>Happy to be here. Dave. >>So obviously a lot has changed globally, but when you think of things like cyber threats, ransomware, uh, the acceleration of business transformation, uh, these are new things, a lot of it is unknown a lot of it was forced upon us tom what are you guys doing to address these trends? How are you helping customers? >>Sure, thanks for the question. So if you think back to what we launched in early May, kind of the initial cloud transformation of what was our traditional storage business. Um, we really focused on one key theme. Very customer and customer driven theme that the cloud operational model has one and that customers want that operational model, whether they're operating their workload in the cloud or whether they're operating that workload in their own facility or Nicolo kind of the same thing. So that was kind of our true north and that's what we launched out of the gate in May. But we did allude in May to the fact that we would have an ongoing series of new services coming out on the uh H B Green Lake edge to cloud platform. And just really excited today to be talking about somewhat that expansion looks like um we will continue uh through this month and through the quarters ahead to really add more and more services in that vein of focusing on bringing that true cloud services model to our customer. So we're really excited today to unveil kind of, we've entered the data protection as a service market with HP Green Lake. So this is really our expansion into a very top of mind topic and set of problems and solutions or headaches and aspirins, to quote an old friend um that Ceos faces, they think about how to manage data through its life cycle in their organization. >>When I talked to see IOS during the pandemic. Not that we're out yet, but really in the throes of it and asked them about things like business resilience that they said, you know, we really had to rethink our disaster recovery strategy. It was it was sort of geared toward a fire or a hurricane and we we just didn't even imagine this type of disaster if you will. So we really needed to rethink it. So when I, I see your disaster recovery as a service and capabilities like that. Is that the Xarelto acquisition? >>Yes. Dave thanks you. So we're super happy to have the Xarelto team now as part of our family. Um, just a brilliant team, a well respected technology, uh, kind of a blue chips at our customers and partners that really appreciate what zero has to offer. Um, as we looked at the data protection as a service market, one of the hardest problems is really in that disaster recovery space, I think Omar's gonna talk a little bit more about today. Um, but sort of really does bring the leading industry, what's called continuous data protection um, capability into our green lake platform. Um, we've just recently closed the acquisition and we're working on kind of integration plan as we speak now that we can actually talk to each other post close. Um, but you'll uh, you'll continue to see, you know, some really exciting milestones each and every quarter as we march forward with certain now as part of the family. >>So we all talk about how data is, is so important. We certainly learned during the pandemic that that if you weren't a digital business, you were out of business and a digital business is a data business. So things like backup data protection as a service become increasingly critical. I know you have some capabilities there maybe you could share with us. >>Absolutely. So you know, one of the things that we noticed was as we took the storage business through its transformation and we started can work you know, with the launch of the electron 90 and the six K platform. We really really brought the cloud operational model to our customers. So one of the things that you know, feedback that was coming loud and clear to us is that as we look at the storage portfolio where we look at file block and object, which are now being transformed into a cloud operational experience, data protection, disaster recovery coming back into business after a disaster snapshot management. All of those capabilities, we still have to rely on our partner technologies in order to do that now. It's not bad that we have great partners in the data protection world, but what we're really focused on is that cloud operational model and cloud operational experience and to and as tom mentioned through the data management life cycle. So as a result of that, we talked to a lot of our customers, we talked to a bunch of partners and one of the things that was coming back was that yes, there are many data protection backup offerings on the market. But that true as a service experience that is completely integrated to the services experience of the storage that the customers is experiencing that is not there. So what we looked at was especially to the largest ecosystem, which is the VM ware ecosystems. So we're launching data protection as a service or backup as a service for our VM ware customers offered from data services, cloud console as a SAAS portal. 100% SAs service, nothing to install. No media servers, no application servers, no catalog servers, no backup targets, no patching, no expansion, no capacity planning. None of that is needed. All that's needed is sign on click. Give your V center credentials and off you go, that's it. That is it three clicks and you're in business. So currently, you know, in our, in our analysis we offer five x faster recovery from any of the competitive offerings that there there there are 3.5 better de doop ratios. But for our customers is as simple as this. VM is protected as this many dollars per gig per month. That's it. No backup target, no media server, no catalogs are nothing nothing to manage total Turkey off of the portal. So that's the cadence of services that if you promise and this is one of the first ones when it comes to data management that is coming out into the open. >>So you may have just answered this question, but I want to pose it and get you maybe just summarize it because tom was talking earlier about the customer mandate for cloud in a cloud operational model. So I want you to explain to the audience how you're making that real >>actually can I start that one should be the test was monday morning. Getting ready for this chat with you Dave they got me on console and I'm not kidding three clicks, I got back up and running off the lab VM ware instance so I'll pass it off to you the real answer. But if I could do it three clicks >>as well as a convenience of this service, even tom can be your back, you might be able to do with this. Uh again, you know, a very important question the when you, when you look at the cloud operational model as you abstracts the hardware and and take the management model up into a SAS service, it gives our customers that access to that continuous delivery access that we have. We're going to continue to make the service medal better in the cloud model and automatically customers get the value of it without even reinstalling or going through a patch cycle or an upgrade cycle. But as we get into this cloud operational model, one of the things that was missing was uh if you if you if you if you start to talk about applications, how our application workloads going to be deployed, how are they going to be protected and how are they going to be expanded? So what we did was we, we expanded our info site offerings by merging them into the data services, cloud console and we're releasing a new service called app insects. It is going to be available to our customers at the end of the month. Uh It is, nothing has to change. They don't have to install any sort of agents or or host modifications, nothing like that. If their customers of electra nimble primary boxes and they're using info site and data services, cloud console, they will automatically get app insights. What Athens sites does is it really teases apart all that data that we have been collecting within foresight and now with the acquisition of HPV cloud physics, we're merging them together and relating the operational stacked top to bottom. So discovering all the way from your application usage, network usage, storage, use it. IOP usage VM values cross, collaborating them and presenting that to a customer from an app or an outcome perspective all in the data services, cloud console. So what this does for our customers is it really really transforms not only their operational experience but also buying experience. Because if you remember in one of the earlier releases of data services cloud console we released this application called, you know, intelligent intent based provisioning in which you just describe your workload and we go ahead and we provision that app insights and info site, feed that information directly into that and cloud physics generates and results and displays those analytics back to us to your partner of record and to the H. B. So we can all come together on a common data driven discussion point with our customers to continue to make their journey better >>tom where's all the boxes, traditional storage is changing. I've actually been waiting for this day for a long, long time. We've certainly seen glimpses of it from the cloud players, but they don't have, you know, super rich portfolio storage portfolio. They're growing now, but this is a really good strong example of a company with a large storage portfolio. That's, I mean I haven't heard the word three power once today. Right. And so what that says to me, that's an indication that you're thinking like a cloud player, can you maybe talk >>to that? Sure. Yeah, we're just tremendously excited about this transformation and really the reception we've got in the market from analysts, from partners, from customers because you're right, you haven't heard us talk about a box at all today. It's really about a block service, a file on the object service, a backup and recovery service, disaster recovery service. That that's that is the the language, if you will of the business problems of our customers not, do they need to pick this widget or that widget. And how many apps can I get here and there? And which did the h a cage protection scheme be that, is that, is our job to manage underneath are true North, which is the cloud operational model. And so that's going to be really how we we've set our course and how we will uh kind of deliver products solutions offers into the market underneath that umbrella, Ultimately, um getting our customers wherever their data is Dave to be able to interact at that service level instead of at that infrastructure box >>level, you've got my attention wherever the data. So that's the north star here is this is, you know, you're not done today obviously, but you've got a vision to bring that to the cloud across clouds on prem out to the edge. That's the abstraction layer that you're gonna build, your hiding all that complexity. That's correct. And that's cloud. The definition of cloud is changing. >>Yeah, >>it's no longer started, it's no longer a remote set of services. Somewhere up in the cloud. It's expanding on prem hybrid across clouds edge >>everywhere. You're exactly right. Dave it is, cloud is more about the experience and the outcome. It gives a customer than actually where the compute or storage is. We've chosen to take a very customer an agnostic position of whether it's, you know, data in your premise, data in your cloud. We're going to help you manage that data and deliver, you know, that data to workloads and analytics, uh, wherever the, wherever the compute needs to be, where the data needs to be. Again, technologies like Xarelto giving instability and move data across clouds from facilities and clouds back and forth. So it's a really exciting new day for HP. Green Lake were just so super happy to bring these technologies out and really continue to follow on the course of doing what we said, we would do >>the new mindset starts there, I guess it's obviously knew certainly new technologies, uh, you're talking about machine intelligence is a metadata challenge. Absolutely. Big time, you know, long term that North Star that we talked about and applying that machine intelligence, all the experience that you gather data that you're gathering is, I think ultimately how customers want you to solve this problem >>in the middle of info site data services, cloud console and the instrumentation that is already shipping on our appliances, both in edge appliances and the data center appliances were collecting more than a trillion data points over the period of a quarter. Right at the end of the day. So it's harnessing that at the back end to cross relate and then using the cloud physics accusation. What we're doing is we can now simulate these things on behalf of our customers into the future timeline. So at the end of the day, it's really about listening to the customer and what outcomes that they want to achieve with their data storage is there we provide excellent persistence layers where customers can store their data safely. But at the end of the day it's customers choice, They can store their data out of the edge in compute servers, commodity servers, X 86 servers, they can have their data in the data center which they are privately owned or their data can be in a service provider or it can be in a hyper secular. The infrastructure of the persistence layer is independent from the data services. Cloud console data services. Cloud console provides our customers with a SAS based industry leading metadata rich management experience, which then allows you to draw conclusions. So services like cloud physics services like uh enforce it, provide the analytics and richness of the metadata, backup and recovery service allows us to index our customers data and add a rich metadata to that and then combine that with xylitol, which is our disaster recovery as a service offering. Going to start over here. That gives the customer a very simple slider as to where they want their protection levels to be, they want their protection to be instant or they want their protection to be lazy eight hours window. But the thing is at the end of the day, it's about choice without managing the complexities of the hardware >>underneath because programmable completely right I come in, what I'm hearing is file object blocks of your multi protocol. I got a full stack so data data reduction, my snaps might replicate whatever whatever I need it in there as a service. I can I can access latency sensitive storage if I need to or I can push it out to cheaper stores. I could push it out to the cloud, presumably I could someday I air gap it uh and it's all done as infrastructure as code and then different protection levels where I see this going. It really gets exciting is you're now a data company and you're bringing ai machine intelligence and driving data products, data services for your customers who are going to monetize that at their end of the value >>chain. That's right. That's right. And safely insecurity. Keeping in mind that was their toes technology. We can give you, you know, small second recovery points to protect against ransomware. So all of that operational elegance, all those insights and intelligence to help you build a more agile, um you know, workloads centric organization, but then to do it safely and securely against ransomware, that's kind of the storm, if you will. That's brewing. And we're just really excited to be at the eye of it. >>I'm excited to. This is uh I've been waiting for this day for a long time and we're not talking about envy, Emmy and Atomic Rights and I love that stuff by the way and I'm sure it's all under the covers, but that's not what drives business value guys. Thanks so much for coming on the Cuban. David. >>Thanks for having us. It's been great. Thank you. >>All right. We're seeing a transformation all through the stack and keep it right there. This is Dave Volonte for the Cuban. Our coverage of HBs Green Lake announcements right back mm mhm

(upbeat intro music) >> More than a decade ago, the team at Wikibon coined the term Server SAN. We saw the opportunity to dramatically change the storage infrastructure layer and predicted a major change in technologies that would hit the market. Server SAN had three fundamental attributes. First of all, it was software led. So all the traditionally expensive controller functions like snapshots and clones and de-dupe and replication, compression, encryption, et cetera, they were done in software directly challenging a two to three decade long storage controller paradigm. The second principle was it leveraged and shared storage inside of servers. And the third it enabled any-to-any typology between servers and storage. Now, at the time we defined this coming trend in a relatively narrow sense inside of a data center location, for example, but in the past decade, two additional major trends have emerged. First the software defined data center became the dominant model, thanks to VMware and others. And while this eliminated a lot of overhead, it also exposed another problem. Specifically data centers today allocate probably we estimate around 35% of CPU cores and cycles to managing things like storage and network and security, offloading those functions. This is wasted cores and doing this with traditional general purpose x86 processors is expensive and it's not efficient. This is why we've been reporting so aggressively on ARM's ascendancy into the enterprise. It's not only coming it's here and we're going to talk about that today. The second mega trend is cloud computing. Hyperscale infrastructure has allowed technology companies to put a management and control plane into the cloud and expand beyond our narrow server SAN scope within a single data center and support the management of distributed data at massive scale. And today we're on the cusp of a new era of infrastructure. And one of the startups in this space is Nebulon. Hello everybody, this is Dave Vellante, and welcome to this Cube Conversation where we welcome in two great guests, Craig Nunes, Cube alum, co-founder and COO at Nebulon and Tobias Flitsch who's director of product management at Nebulon. Guys, welcome. Great to see you. >> So good to be here Dave. Feels awesome. >> Soon, face to face. Craig, I'm heading your way. >> I can't wait. >> Craig, you heard my narrative upfront and I'm wondering are those the trends that you guys saw when you, when you started the company, what are the major shifts in the world today that, that caused you and your co-founders to launch Nebulon? >> Yeah, I'll give you sort of the way we think about the world, which I think aligns super right with, with what you're talking about, you know, over the last several years, organizations have had a great deal of experience with public cloud data centers. And I think like any platform or technology that is, you know, gets its use in a variety of ways, you know, a bit of savvy is being developed by organizations on, you know, what do I put where, how do I manage things in the most efficient way possible? And there are, in terms of the types of folks we're focused on in Nebulon's business, we see now kind of three groups of people emerging, and, and we sort of simply coined three terms, the returners, the removers, and the remainers. I'll explain what I mean by each of those, the returners are folks who maybe early on, you know, hit the gas on cloud, moved, you know, everything in, a lot in, and realize that while it's awesome for some things, for other things, it was less optimal. Maybe cost became a factor or visibility into what was going on with their data was a factor, security, service levels, whatever. And they've decided to move some of those workloads back. Returners. There are what I call the removers that are taking workloads from, you know, born in the cloud. On-prem, you know, and this was talked a lot about in Martine's blog that, you know, talked about a lot of the growth companies that built up such a large footprint in the public cloud, that economics were kind of working against them. You can, depending on the knobs you turn, you know, you're probably spending two and a half X, two X, what you might spend if you own your own factory. And you can argue about, you know, where your leverage is in negotiating your pricing with the cloud vendors, but there's a big gap. The last one is, and I think probably the most significant in terms of who we've engaged with is the remainers. And the remainers are, you know, hybrid IT organizations. They've got assets in the cloud and on-prem, they aspire to an operational model that is consistent across everything and, you know, leveraging all the best stuff that they observed in their cloud-based assets. And it's kind of our view that frankly we take from, from this constituency that, when people talk about cloud or cloud first, they're moving to something that is really more an operating model versus a destination or data center choice. And so, we get people on the phone every day, talking about cloud first. And when you kind of dig into what they're after, it's operating model characteristics, not which data center do I put it in, and those, those decisions are separating. And so that, you know, it's really that focus for us is where, we believe we're doing something unique for that group of customers. >> Yeah. Cloud first doesn't doesn't mean cloud only. And of course followers of this program know, we talk a lot about this, this definition of cloud is changing, it's evolving, It's moving to the edge, it's moving to data centers, data centers are moving to the cloud. Cross-cloud, it's that big layer that's expanding. And so I think the definition of cloud, even particularly in customer's minds is evolving. There's no question about it. People, they'll look at what VMware is doing in AWS and say, okay, that's cloud, but they'll also look at things like VMware cloud foundation and say oh yeah, that's cloud too. So to me, the beauty of cloud is in the eye of the customer beholder. So I buy that. Tobias. I wonder if you could talk about how this all translates into product, because you guys start up, you got to sell stuff, you use this term smart infrastructure, what is that? How does this all turn into stuff you can sell? >> Right. Yeah. So let me back up a little bit and talk a little bit about, you know, what we at Nebulon do. So we are a cloud based software company, and we're delivering sort of a new category of smart infrastructure. And if you think about things that you would know from your everyday surroundings, smart infrastructure is really all around us. Think smart home technology like Google Nest as an example. And what this all has in common is that there's a cloud control plane that is managing some IOT end points and smart devices in various locations. And by doing that, customers gain benefits like easy remote management, right? You can manage your thermostat, your temperature from anywhere in the world basically. You don't have to worry about automated software updates anymore, and you can easily automate your home, your infrastructure, through this cloud control plane and translating this idea to the data center, right? This idea is not necessarily new, right? If you look into the networking space with Meraki networks, now Cisco or Mist Systems now Juniper, they've really pioneered efforts in cloud management. So smart network infrastructure, and the key problem that they solved there is, you know, managing these vast amount of access points and switches that are scattered across the data centers across campuses, and, you know, the data center. Now, if you translate that to what Nebulon does, it's really applying this smart infrastructure idea, this methodology to application infrastructure, specifically to compute and storage infrastructure. And that's essentially what we're doing. So with smart infrastructure, basically our offering it at Nebulon, the product, that comes with the benefits of this cloud experience, public cloud operating model, as we've talked about, some of our customers look at the cloud as an operating model rather than a destination, a physical location. And with that, we bring to us this model, this, this experience as operating a model to on-premises application infrastructure, and really what you get with this broad offering from Nebulon and the benefits are really circling it out, you know, four areas, first of all, rapid time to value, right? So application owners think people that are not specialists or experts when it comes to IT infrastructure, but more generalists, they can provision on-premise application infrastructure in less than 10 minutes, right? It can go from, from just bare metal physical racks to the full application stack in less than 10 minutes, so they're up and running a lot quicker. And they can immediately deliver services to their end customers, cloud-like operations, this, this notion of zero touch remote management, which now with the last couple of months with this strange time that we're with COVID is, you know, turnout is becoming more and more relevant really as in remotely administrating and management of infrastructure that scales from just hundreds of nodes to thousands of nodes. It doesn't really matter with behind the scenes software updates, with global AI analytics and insights, and basically overall combined reduce the operational overhead when it comes to on-premises infrastructure by up to 75%, right? The other thing is support for any application, whether it's containerized, virtualized, or even bare metal applications. And the idea here is really consistent leveraging server-based storage that doesn't require any Nebulon-specific software on the server. So you get the full power of your application servers for your applications. Again, as the servers intended. And then the fourth benefit when it comes to smart infrastructure is, is of course doing this all at a lower cost and with better data center density. And that is really comparing it to three-tier architectures where you have your server, your SAN fabric, and then you have an external storage, but also when you compare it with hyper-converged infrastructure software, right, that is consuming resources of the application servers, think CPU, think memory and networking. So basically you get a lot more density with that approach compared to those architectures. >> Okay, I want to dig into some of that differentiation too, but what exactly do I buy from you? Do I buy a software subscription? Is that right? Can you explain that a little bit? >> Right. So basically the way we do this is it's really leveraging two key new innovations, right? So, and you see why I made the bridge to smart home technology, because the approach is civil, right? The one is, you know, the introduction of a cloud control plane that basically manage this on-premise application infrastructure, of course, that is delivered to customers as a service. The second one is, you know, a new infrastructure model that uses IOT endpoint technology, and that is embedded into standard application servers and the storage within this application servers. Let me add a couple of words to that to explain a little bit more, so really at the heart of smart infrastructure, in order to deliver this public cloud experience for any on-prem application is this cloud-based control plane, right? So we've built this, how we recommend our customers to use a public cloud, and that is built, you know, building your software on modern technologies that are vendor-agnostic. So it could essentially run anywhere, whether it is, you know, any public cloud vendor, or if we want to run in our own data centers, when regulatory requirements change, it's massively scalable and responsive, no matter how large the managed infrastructure is. But really the interesting part here, Dave, is that the customer doesn't really have to worry about any of that, it's delivered as a service. So what a customer gets from this cloud control plane is a single API end point, how they get it with a public cloud. They get a web user interface, from which they can manage all of their infrastructure, no matter how many devices, no matter where it is, can be in the data center, can be in an edge location anywhere in the world, they get template-based provisioning much like a marketplace in a public cloud. They get analytics, predictive support services, and super easy automation capabilities. Now the second thing that I mentioned is this server embedded software, the server embedded infrastructure software, and that is running on a PCIE based offload engine. And that is really acting as this managed IOT endpoint within the application server that I managed that I mentioned earlier. And that approach really further converges modern application infrastructure. And it really replaces the software defined storage approach that you'll find in hyper-converged infrastructure software. And that is really by embedding the data services, the storage data service into silicon within the server. Now this offload engine, we call that a services processing unit or SPU in short. And that is really what differentiates us from hyper-converged infrastructure. And it's quite different than a regular accelerator card that you get with some of the hyper-converged infrastructure offerings. And it's different in the sense that the SPU runs basically all of the shared and local data services, and it's not just accelerating individual algorithms, individual functions. And it basically provides all of these services aside the CPU with the boot drive, with data drives. And in essence provides you with this a separate fall domain from the service, so for example, if you reboot your server, the data plan remains intact. You know, it's not impacted for that. >> Okay. So I want to stay on that for just a second, Craig, if I could, I get very clear how you're different from, as Tobias said, the three-tier server SAN fabric, external array, the HCI thing's interesting because in some respects, the HCI has, you know, guys take Nutanix, they talk about cloud and becoming more friendly with developers and API piece, but what's your point of view Craig on how you position relative to say HCI? >> Yeah, absolutely. So everyone gets what three-tier architecture is and was, and HCI software, you know, emerged as an alternative to the three-tier architectures. Everyone I think today understands that data services are, you know, SDS is software hosted in the operating system of each HCI device and consume some amount of CPU, memory, network, whatever. And it's typically constrained to a hypervisor environment, kind of where we're most of that stuff is done. And over time, these platforms have added some monitoring capabilities, predictive analytics, typically provided by the vendor's cloud, right? And as Tobias mentioned, some HCIS vendors have augmented this approach by adding an accelerator to make things like compression and dedupe go faster, right? Think SimpliVity or something like that. The difference that we're talking about here is, the infrastructure software that we deliver as a service is embedded right into server silicon. So it's not sitting in the operating system of choice. And what that means is you get the full power of the server you bought for your workloads. It's not constrained to a hypervisor-only environment, it's OS agnostic. And, you know, it's entirely controlled and administered by the cloud versus with, you know, most HCIS is an on-prem console that manages a cluster or two on-prem. And, you know, think of it from a automation perspective. When you automate something, you've got to set up your playbook kind of cluster by cluster. And depending what versions they're on, APIs are changing, behaviors are changing. So a very different approach at scale. And so again, for us, we're talking about something that gives you a much more efficient infrastructure that is then managed by the cloud and gives you this full kind of operational model you would expect for any kind of cloud-based deployment. >> You know, I got to go back, you guys obviously have some three-part DNA hanging around and you know, of course you remember well, the three-part ASIC, it was kind of famous at the time and it was unique. And I bring that up only because you've mentioned a couple of times the silicon and a lot of people yeah, whatever, but we have been on this, especially, particularly with ARM. And I want to share with the audience, if you follow my breaking analysis, you know this. If you look at the historical curve of Moore's law with x86, it's the doubling of performance every two years, roughly, that comes out to about 40% a year. That's moderated down to about 30% a year now, if you look at the ARM ecosystem and take for instance, apple A15, and the previous series, for example, over the last five years, the performance, when you combine the CPU, GPU, NPU, the accelerators, the DSPs, which by the way, are all customizable. That's growing at 110% a year, and the SOC costs 50 bucks. So my point is that you guys are riding perfect example of doing offloads with a way more efficient architecture. You're now on that curve, that's growing at 100% plus per year. Whereas a lot of the legacy storage is still on that 30% a year curve, and so cheaper, lower power. That's why I love to buy, as you were bringing in the IOT and the smart infrastructure, this is the future of storage and infrastructure. >> Absolutely. And the thing I would emphasize is it's not limited to storage, storage is a big issue, but we're talking about your application infrastructure and you brought up something interesting on the GPU, the SmartNIC of things, and just to kind of level set with everybody there, there's the HCI world, and then there's this SmartNIC DPU world, whatever you want to call it, where it's effectively a network card, it's got that specialized processing onboard and firmware to provide some network security storage services, and think of it as a PCIE card in your server. It connects to an external storage system, so think Nvidia Bluefield 2 connecting to an external NVME storage device. And the interesting thing about that is, you know, storage processing is offloaded from the server. So as we said earlier, good, right, you get the server back to your application, but storage moves out of the server. And it starts to look a little bit like an external storage approach versus a server based approach. And infrastructure management is done by, you know, the server SmartNIC with some monitoring and analytics coming from, you know, your supplier's cloud support service. So complexity creeps back in, if you start to lose that, you know, heavily converged approach. Again, we are taking advantage of storage within the server and, you know, keeping this a real server based approach, but distinguishing ourselves from the HCI approach. Cause there's a real ROI there. And when we talked to folks who are looking at new and different ways, we talk a lot about the cloud and I think we've done a bit of that already, but then at the end of the day, folks are trying to figure out well, okay, but then what do I buy to enable this? And what you buy is your standard server recipe. So think your favorite HPE, Lenovo, Supermicro, whatever, whatever your brand, and it's going to come enabled with this IOT end point within it, so it's really a smart server, if you will, that can then be controlled by our cloud. And so you're effectively buying, you know, from your favorite server vendor, a server option that is this endpoint and a subscription. You don't buy any of this from us, by the way, it's all coming from them. And that's the way we deliver this. >> You know, sorry to get into the plumbing, but this is something we've been on and a facet of it. Is that silicon custom designed or is it pretty much off the shelf, do you guys add any value to it? >> No, there are off the shelf options that can deliver tremendous horsepower on that form factor. And so we take advantage of that to, you know, do what we do in terms of, you know, creating these sort of smart servers with our end point. And so that's where we're at. >> Yeah. Awesome. So guys, what's your sweet spot, you know, why are customers, you know, what are you seeing customers adopting? Maybe some examples you guys can share? >> Yeah, absolutely. So I think Tobias mentioned that because of the architectural approach, there's a lot of flexibility there, you can run virtualized, containerized, bare metal applications. The question is where are folks choosing to get started? And those use cases with our existing customers revolved heavily around virtualization modernization. So they're going back in to their virtualized environment, whether their existing infrastructure is array-based or HCI-based. And they're looking to streamline that, save money, automate more, the usual things. The second area is the distributed edge. You know, the edge is going through tremendous transformation with IOT devices, 5g, and trying to get processing closer to where customers are doing work. And so that distributed edge is a real opportunity because again, it's a more cost-effective, more dense infrastructure. The cloud effectively can manage across all of these sites through a single API. And then the third area is cloud service provider transformation. We do a fair bit of business with, you know, cloud service providers, CTOs, who are looking at trying to build top line growth, trying to create new services and, and drive better bottom line. And so this is really, you know, as much as a revenue opportunity for them as cost saving opportunity. And then the last one is this notion of, you know, bringing the cloud on-prem, we've done a cloud repatriation deal. And I know you've seen a little of that, but maybe not a lot of it. And, you know, I can tell you in our first deals, we've already seen it, so it's out there. Those are the places where people are getting started with us today. >> It's just interesting, you're right. I don't see a ton of it, but if I'm going to repatriate, I don't want to go backwards. I don't want to repatriate to legacy. So it actually does kind of make sense that I repatriate to essentially a component of on-prem cloud that's managed in the cloud, that makes sense to me to buy. But today you're managing from the cloud, you're managing on-prem infrastructure. Maybe you could show us a little leg, share a little roadmap, I mean, where are you guys headed from a product standpoint? >> Right, so I'm not going to go too far on the limb there, but obviously, right. So one of the key benefits of a cloud managed platform is this notion of a single API, right. We talked about the distributed edge where, you know, think of retailer that has, you know, thousands of stores, each store having local infrastructure. And, you know, if you think about the challenges that come with, you know, just administrating those systems, rolling out firmware updates, rolling out updates in general, monitoring those systems, et cetera. So having a single console, a cloud console to administrate all of that infrastructure, obviously, you know, the benefits are easy now. If you think about, if you're thinking about that and spin it further, right? So from the use cases and the types of users that we've see, and Craig talked about them at the very beginning, you can think about this as this is a hybrid world, right. Customers will have data that they'll have in the public cloud. They will have data and applications in their data centers and at the edge, obviously it is our objective to deliver the same experience that they gained from the public cloud on-prem, and eventually, you know, those two things can come closer together. Apart from that, we're constantly improving the data services. And as you mentioned, ARM is, is on a path that is becoming stronger and faster. So obviously we're going to leverage on that and build out our data storage services and become faster. But really the key thing that I'd like to, to mention all the time, and this is related to roadmap, but rather feature delivery, right? So the majority of what we do is in the cloud, our business logic in the cloud, the capabilities, the things that make infrastructure work are delivered in the cloud. And, you know, it's provided as a service. So compared with your Gmail, you know, your cloud services, one day, you don't have a feature, the next day you have a feature, so we're continuously rolling out new capabilities through our cloud. >> And that's about feature acceleration as opposed to technical debt, which is what you get with legacy features, feature creep. >> Absolutely. The other thing I would say too, is a big focus for us now is to help our customers more easily consume this new concept. And we've already got, you know, SDKs for things like Python and PowerShell and some of those things, but we've got, I think, nearly ready, an Ansible SDK. We're trying to help folks better kind of use case by use case, spin this stuff up within their organization, their infrastructure. Because again, part of our objective, we know that IT professionals have, you know, a lot of inertia when they're, you know, moving stuff around in their own data center. And we're aiming to make this, you know, a much simpler, more agile experience to deploy and grow over time. >> We've got to go, but Craig, quick company stats. Am I correct, you've raised just under 20 million. Where are you on funding? What's your head count today? >> I am going to plead the fifth on all of that. >> Oh, okay. Keep it stealth. Staying a little stealthy, I love it. Really excited for you. I love what you're doing. It's really starting to come into focus. And so congratulations. You know, you got a ways to go, but Tobias and Craig, appreciate you coming on The Cube today. And thank you for watching this Cube Conversation. This is Dave Vellante. We'll see you next time. (upbeat outro music)

(bright music) >> Hello, and welcome to today's session of the 2021 AWS Global Public Sector Partner Awards. I'm your host, Natalie Erlich and today we'll highlight the best cybersecurity solution. I'm very pleased to welcome our next guests. They are Tina Thorstenson executive public sector strategist at CrowdStrike and Jennifer Dvorak information security architect for the State of Arizona. Thank you so much for being with me today. >> Thanks for having us. >> Yep, thank you. >> Perfect. Well you know obviously a really wild year with COVID and it certainly pushed a lot of boundaries. Cyber security resiliency also a hot topic as ransomware really spiked up. How have you addressed this concern and really accelerated this push with COVID-19 in the backdrop? I'd love it if either one of you would just like to jump in here. >> Well, CrowdStrike was one of our initiatives for 2020 and it was significantly increased, accelerated due to COVID. So we had to roll out in a matter of weeks when we had a matter of months previously and it really provided us the visibility that we needed for folks taking their computers home. We had no way of triaging any of our incidents when the computers were at home. So rolling out CrowdStrike as quickly as possible it gave us remote access, it gave us visibility and that was huge for our organization. >> Tina, if you could weigh in on this as well, that would be terrific. >> Sure absolutely. And you know, Jen with the State of Arizona is one of our premier customers but across the board with the 2021 global threat report that we issue each year, what we saw there was a fourfold increase in the number of intrusions. So to your point about the threat activity and it's not getting better. So what CrowdStrike is on a mission to do is stop regions and protect organizations against these bad actors so that they're, that we minimize disruptions. It's really been tremendous to see and build a ecosystem from a platform approach that started with visibility on the end point that Jen was just alluding to. >> And Jennifer, I'd love to get your insight how the public sector and the private sector can work better in tandem with each other in order to protect customers and also communities against ransomware attacks and other kinds of cybersecurity threats that we've seen coming from Russia for instance. >> Certainly so our state CISO Tim Roemer, he has definitely encouraged us to make partners with our private vendors. So that's one of his strategic initiatives and we really want partners in the private sector. We want folks that are going to come alongside us and help us with our security goals. And CrowdStrike has been one of those vendors. We don't want to just spend money and then the vendor runaway, we want somebody that's going to be with us every step of the way. We've had some incidents this past year and CrowdStrike was the first team to alert us because it was a different agency or a different part of our organization that we don't typically work with a lot. And that was really helpful because we were able to act quickly and address the issues that arose. So just having somebody that's looking out for your best interests and being a true partner is what we're really looking for. And that's the only way that we can circumvent these ransomware attacks. >> And Tina I'd love it if you'd weigh in as well. How do you see your role in this effort to protect the public evolving now in 2021? >> So I love that question and especially with the role of my role brand new in COVID interestingly enough, to create this bi-directional executive alignment with our customers and our internal teams and overall at CrowdStrike our goal, as I said is to stop breaches and it's really to bring, to minimize the frustration that comes sometimes with rolling out security tools. I've been at this a long time and tools like CrowdStrike are really game changers for security teams that are really about protecting organizations. And essentially what we do is we brought a single platform where when it, when the, when our software is deployed to an organization across their laptops, desktops, server and cloud infrastructure, we were born in the cloud kind of before it was cool and now we serve more than 11,000 customers. And that threat activity goes to a single AWS instance where we look across all of the threat activity. And then when we see activity in one area, we can protect all of our customers. That's the power of the cloud. >> Perfect and I'd love Jennifer's insights here too. What steps are you taking now to keep the public protected and the state cyber ready? >> And I like Tina's point about being born in the cloud. So State of Arizona is a cloud first state. We are also looking for solutions in the cloud, and I think by leveraging cloud solutions, we're able to be more nimble. We're able to pivot our approach to security and address anything that comes up more quickly. So being cloud first, even though it's, it wasn't embraced initially, I think that it's something that we've been driving towards and looking for more partners that support that cloud first initiative that we have. >> And Tina what's top of mind? What are some of the key initiatives that your team and teams are going to be focused on in the years ahead? What's the next phase for cybersecurity? >> Great question and we've talked quite a bit about the end point but where we're headed and really where we've invested heavily the last couple of years and we'll continue moving forward is now that we have, we've brought this game-changing visibility to our security teams on the end point of each one of the systems in their environment where we've expanded the platform to now include cloud services like I mentioned. Now include indicators of misconfigurations which are so detrimental to teams working in a hybrid cloud environment. And then we've also moved into the identity protection space. And essentially what we're doing there is the same thing we've been doing to protect workloads coming from desktops and laptops across the country and around the world and moved to a model where we're also in a zero trust principles way looking for threat activity coming in through identities, through people logging into these systems and doing the same real-time continuous monitoring and taking proactive action to protect organizations where we see malicious activity. >> Terrific, well, in light of COVID-19, we saw a big spike in ransomware and I'd love to hear specifically from Tina why do we need trusted partners rather than software vendors in this fight? >> You know, it's so important to get out in front of all of the adversaries and most recently that we've seen huge growth in the e-crime actors that are taking advantage of the tools that are unfortunately in the market today, sometimes even free that allow them to hold organizations hostage. And the reason that's so important to partner with organizations and companies like CrowdStrike, is that we've been thinking ahead and we are designed in a way to stop an individual, a breach or adversary attack from occurring but we've been watching how their adversary works and now we can see their activity very early on before they have a chance to gain a foothold in an organization's server or laptop or even a phone or a tablet. And really what we're doing is we're providing protection so that it doesn't even need to move to an analyst to do further review. We just stop it right at the gate before it causes harm. And the reason that this is so important probably is obvious, but we're about making sure that the organizations like the State of Arizona can continue on their business and without these kinds of disruptions. So we haven't designed against one particular adversary but we really designed an approach that works across them all because we've been watching so closely how they move through environments for years. And we use the power of artificial intelligence delivered from the cloud to protect against all things including ransomware. >> Right it's really an evolving process. You constantly have to be vigilant for the next threat. Now I'd love to hear how you see things change with your tech partners and providers at the moment. >> So from a CrowdStrike perspective, we aim to be absolutely the best in class for the products and services that we provide whether that's your products that you can purchase like our endpoint solutions or whether that's services like our 24/7 threat hunting teams or Falcon Complete Teams that basically serve as an extension of an organization's team. But it's absolutely critical that we move this direction and not try to be the best at everything and instead partner. So we have extensive partnerships with Zscaler and Proofpoint and so many others, Okta. I mean the list goes on and on with now hundreds. And we also have a CrowdStrike store. So once you're a customer we've reduced the friction to taking on and trying out new modules, either from us or new options that maybe you haven't considered before from our trusted partners, much like the AWS marketplace we've got the CrowdStrike store and it's a growing set of partnerships where we build those integrations. So, my prior life I was the CISO for Arizona State University most recently. And we spend an awful lot of time integrating these solutions in a CrowdStrike. We're about building those integrations so that the teams within the organizations that can get on to doing innovative things within their space, rather than having to spend all their time tying these technologies together. >> Yeah now shifting to Jennifer late last year we learned that suspected Russian hackers broke into the US government agencies including a county in Arizona. So what measures has the State of Arizona put in place now to ensure that something like that won't happen again or that at least the state is very vigilant and ready to protect citizens and the government against these threats? >> We're definitely partnering with products like or vendors like CrowdStrike. That's what we, we're looking to extend those partnerships. And not only that we're developing our information sharing program across state, local and territorial governments. So we're looking to partner with the cities, the counties. Cybersecurity is a team sport. Cybersecurity is, it takes everyone. It takes the whole state working together. And that's one of the things that we've been trying to build. So working in conjunction with the state fusion center, the Arizona Counter Terrorism Information Center, we've been working to do more indicators of compromise sharing, any intelligence that we've been gathering from these counties that maybe did have an incident or a breach. We want to make sure that the information is disseminated to everyone so that we can be stronger and protect against it. Additionally, we we're always looking for grants that we can extend so that we're able to extend our products that we use to some of the smaller cities and towns and counties so that they can leverage some of the same technologies like CrowdStrike in their environments at a fraction of the cost or paid for by a grant. >> Terrific, well, Tina how does your experience as a CrowdStrike customer now come into play in your current role? >> Well, how's it come into play? Well, I think that it makes it really easy for me to be a liaison internally and help internal teams understand what it's like to sit as a CISO or as a CIO or deputy CIO. And to understand the kinds of challenges that these teams are (indistinct) these leaders of these teams are facing as they're moving forward with their innovation agenda while making sure to make sure that they're gaining those operational efficiencies that are so important today and wowing their customers all the while, right? So I think really what I bring to it is that level of experience to make sure that the voices of our customers are heard internally and that we continue to build products and services that make sense for the needs of our customers additional capabilities. Like we just released Falcon X Recon is an example of one of our newer capabilities where we're basically looking at their deep and dark web activity and bringing that together in the single platform, single event console that we've leveraged for years now. And in highlighting that activity many, in many cases, pre breach. So before you'd ever see it hit your, in your organization's operational environment, we would detect it through that service. So, I think it's those, all those things combined. >> Terrific well, CrowdStrike won a number of key accolades this year, and I was curious, Tina what you attribute to this huge success. >> Well, I have to tell you that I've been in the security space for far too long. And what I can say is that until CrowdStrike came along, there wasn't a solution, a security solution that we could get software running on an end point that wasn't just frustrating across the board. There were conflicts with other software running or the software would work great for one platform but it wouldn't work for the other. So we really have this new approach. And I think that that's what's made us, in fact I'm sure it's certainly what made me a wildly happy customer is that staff, faculty, employees, if we hadn't told them the software was being rolled out, they wouldn't have even noticed. You know it doesn't impact the machines and it's really provided this amazing experience and bringing all that with 150 different adversary groups that we track and we take that on for the customers and just bring visibility for the immediate things they need to take action on. I think those are all of the things that got us to this point in building out this platform is going to be really amazing to see in the years to come as we expand across other areas within the security space, either developing our own or really driving partnerships to make it easier for our customers. >> Yeah, terrific. Well, I pulled up the stat here for us to examine because I think it's really important for our viewers to understand just how important cybersecurity is and how it's going to be even more important for customers and for the private citizens and public citizens. According to Cybersecurity Ventures, cyber crime costs will grow by 15% per year reaching 10.5 trillion by 2025. That's just in about four years. And not only that, cyber crime will become the third largest economy in the world after the United States and China. So, I mean, it's really terrific that you're stepping up. You know just if you could both, perhaps Jennifer can go first and then Tina, what are the key lessons that you have for even the federal government to take a more proactive stance against these threats? >> Well, I think it's clear that this is a very lucrative venture, business venture. It's treated like a business venture by these criminal actors and they have a formula and it works. So I don't see that it's going to be changing anytime soon. And it's also not something that is highly sophisticated, highly technical. It's very easy. It's very much phishing, you know, users clicking on emails and vulnerabilities and environments. It's really a very easy formula that they continue to repeat. So I think until the federal government has more ways to recoup some of these ransomware payments, or we're able to stop some of these ransomware as a service products from being used, I think it's going to continue. So we're defenders so we need to make sure that we're ready for anything that comes and using products that keep us safe is really the best way and training our users. >> Terrific and Tina? >> Thank you. So we are so passionate about making sure that our customers can sleep better at night. When it comes down to tips it really comes back to the basics in many regards but the basics are sometimes really hard to do. So they sound simple, but they aren't so easy to do. And it's basics like making sure your systems are patched. Every organization has just a growing number of devices and pieces of software and infrastructure and all of those things need to be patched nearly immediately to stay out in front of today's adversaries. And Jen's right, Some are sophisticated, some are not but the reality is if we leave those windows open, we will have adversaries, oh, you know walk into our house if you will. So the basics like that also making sure that you have great backups, right? So if you do run into an instance of a ransomware where your systems are locked that you have the ability to recover quickly, being proactive and making sure that you have the partnership arrangement ahead of time is a third really important thing to do. Many organizations now have IRR retainers that they, incident response retainers that you can use proactively in years where you don't find yourself on your heels in a reactive situation but then it's there when you need it. Sometimes it's hard to find great services when there are the flood of ransomware attacks like we've seen in recent months. And then lastly, and I should have started with this 'cause it's the most important part, train your people. It's so important to make sure that security is just a culture, a part of the culture, just like you lock your car and you lock your house. Making sure that you're thinking about those things that will help keep you safe and your organization safe. >> Really excellent points. Thank you both so much for your insights. That was Tina Thorstenson executive public sector strategist at CrowdStrike, as well as Jennifer Dvorak, information security architect for the State of Arizona. Again, really appreciate your insights. This was a fantastic conversation with you. And that's all for the 2021 AWS Global Public Sector Partner Awards or in this session of that. I'm your host Natalie Erlich and see you very soon. (bright music)