>> Is and who we are today as as a country, as a universe. >> Narrator: Congratulations Reggie Jackson, (inspirational music) you are a CUBE alumni. (upbeat music) >> Announcer: Live from Las Vegas it's theCUBE covering Splunk.Conf19. Brought to you by Splunk. >> Okay, welcome back everyone it's theCUBE's live coverage here in Las Vegas for Splunk.Conf19. I am John Furrier host of theCUBE. It's the 10th Anniversary of Splunk's .Conf user conference. Our 7th year covering it. It's been quite a ride, what a wave. Splunk keeps getting stronger and better, adding more features, and has really become a powerhouse from a third party security standpoint. We got a C-SO in theCUBE on theCUBE today. Chief Information Security, John Frushour Deputy Chief (mumbles) New York-Presbyterian The Award Winner from the Data to Everywhere Award winner, welcome by theCube. >> Thank you, thank you. >> So first of all, what is the award that you won? I missed the keynotes, I was working on a story this morning. >> Frushour: Sure, sure. >> What's the award? >> Yeah, the Data Everything award is really celebrating using Splunk kind of outside its traditional use case, you know I'm a security professional. We use Splunk. We're a Splunk Enterprise Security customer. That's kind of our daily duty. That's our primary use case for Splunk, but you know, New York Presbyterian developed the system to track narcotic diversion. We call it our medication analytics platform and we're using Splunk to track opioid diversion, slash narcotic diversions, same term, across our enterprise. So, looking for improper prescription usage, over prescription, under prescription, prescribing for deceased patients, prescribing for patients that you've never seen before, superman problems like taking one pill out of the drawer every time for the last thirty times to build up a stash. You know, not resupplying a cabinet when you should have thirty pills and you only see fifteen. What happened there? Everything's data. It's data everything. And so we use this data to try to solve this problem. >> So that's (mumbles) that's great usage we'll find the drugs, I'm going to work hard for it. But that's just an insider threat kind of concept. >> Frushour: Absolutely. >> As a C-SO, you know, security's obviously paramount. What's changed the most? 'Cause look at, I mean, just looking at Splunk over the past seven years, log files, now you got cloud native tracing, all the KPI's, >> Frushour: Sure. >> You now have massive volumes of data coming in. You got core business operations with IOT things all instrumental. >> Sure, sure. >> As a security offer, that's a pretty big surface area. >> Yeah. >> How do you look at that? What's your philosophy on that? >> You know, a lot of what we do, and my boss, the C-SO (mumbles) we look at is endpoint protection and really driving down to that smaller element of what we complete and control. I mean, ten, fifteen years ago information security was all about perimeter control, so you've got firewalls, defense and depth models. I have a firewall, I have a proxy, I have an endpoint solution, I have an AV, I have some type of data redaction capability, data masking, data labeling capability, and I think we've seen.. I don't think security's changed. I hear a lot of people say, "Oh, well, information security's so much different nowadays." No, you know, I'm a military guy. I don't think anything's changed, I think the target changed. And I think the target moved from the perimeter to the endpoint. And so we're very focused on user behavior. We're very focused on endpoint agents and what people are doing on their individual machines that could cause a risk. We're entitling and providing privilege to end users today that twenty years ago we would've never granted. You know, there was a few people with the keys to the kingdom, and inside the castle keep. Nowadays everybody's got an admin account and everybody's got some level of privilege. And it's the endpoint, it's the individual that we're most focused on, making sure that they're safe and they can operate effectively in hospitals. >> Interviewer: What are some of the tactical things that have changed? Obviously, the endpoint obviously shifted, so some tactics have to change probably again. Operationally, you still got to solve the same problem: attacks, insider threats, etc. >> Frushour: Yeah. >> What are the tactics? What new tactics have emerged that are critical to you guys? >> Yeah, that's a tough question, I mean has really anything changed? Is the game really the game? Is the con really the same con? You look at, you know, titans of security and think about guys like Kevin Mitnick that pioneered, you know, social engineering and this sort of stuff, and really... It's really just convincing a human to do something that they shouldn't do, right? >> Interviewer: Yeah. >> I mean you can read all these books about phone freaking and going in and convincing the administrative assistant that you're just late for meeting and you need to get in through that special door to get in that special room, and bingo. Then you're in a Telco closet, and you know, you've got access. Nowadays, you don't have to walk into that same administrative assistant's desk and convince 'em that you're just late for the meeting. You can send a phishing email. So the tactics, I think, have changed to be more personal and more direct. The phishing emails, the spear phishing emails, I mean, we're a large healthcare institution. We get hit with those types of target attacks every day. They come via mobile device, They come via the phishing emails. Look at the Google Play store. Just, I think, in the last month has had two apps that have had some type of backdoor or malicious content in them that got through the app store and got onto people's phones. We had to pull that off people's phones, which wasn't pretty. >> Interviewer: Yeah. >> But I think it's the same game. It's the same kind to convince humans to do stuff that they're not supposed to do. But the delivery mechanism, the tactical delivery's changed. >> Interviewer: How is Splunk involved? Cause I've always been a big fan of Splunk. People who know me know that I've pretty much been a fan boy. The way they handle large amounts of data, log files, (mumbles) >> Frushour: Sure. >> and then expand out into other areas. People love to use Splunk to bring in their data, and to bring it into, I hate to use the word data leg but I mean, Just getting... >> Yeah >> the control of the data. How is data used now in your world? Because you got a lot of things going on. You got healthcare, IOT, people. >> Frushour: Sure, sure. >> I mean lives are on the line. >> Frushour: Lives are on the line, yeah. >> And there's things you got to be aware of and data's key. What is your approach? >> Well first I'm going to shamelessly plug a quote I heard from (mumbles) this week, who leads the security practice. She said that data is the oxygen of AI, and I just, I love that quote. I think that's just a fantastic line. Data's the oxygen of AI. I wish I'd come up with it myself, but now I owe her a royalty fee. I think you could probably extend that and say data is the lifeline of Splunk. So, if you think about a use case like our medication analytics platform, we're bringing in data sources from our time clock system, our multi-factor authentication system, our remote access desktop system. Logs from our electronic medical records system, Logs from the cabinets that hold the narcotics that every time you open the door, you know, a log then is created. So, we're bringing in kind of everything that you would need to see. Aside from doing something with actual video cameras and tracking people in some augmented reality matrix whatever, we've got all the data sources to really pin down all the data that we need to pin down, "Okay, Nurse Sally, you know, you opened that cabinet on that day on your shift after you authenticated and pulled out this much Oxy and distributed it to this patient." I mean, we have a full picture and chain of everything. >> Full supply chain of everything. >> We can see everything that happens and with every new data source that's out there, the beauty of Splunk is you just add it to Splunk. I mean, the Splunk handles structured and unstructured data. Splunk handles cis log fees and JSON fees, and there's, I mean there's just, it doesn't matter You can just add that stream to Splunk, enrich those events that were reported today. We have another solution which we call the privacy platform. Really built for our privacy team. And in that scenario, kind of the same data sets. We're looking at time cards, we're looking at authentication, we're looking at access and you visited this website via this proxy on this day, but the information from the EMR is very critical because we're watching for people that open patient records when they're not supposed to. We're the number five hospital in the country. We're the number one hospital in the state of New York. We have a large (mumbles) of very important people that are our patients and people want to see those records. And so the privacy platform is designed to get audit trails for looking at all that stuff and saying, "Hey, Nurse Sally, we just saw that you looked at patient Billy's record. That's not good. Let's investigate." We have about thirty use cases for privacy. >> Interviewer: So it's not in context of what she's doing, that's where the data come in? >> That's where the data come in, I mean, it's advanced. Nurse Sally opens up the EMR and looks at patient Billy's record, maybe patient Billy wasn't on the chart, or patient Billy is a VIP, or patient Billy is, for whatever reason, not supposed to be on that docket for that nurse, on that schedule for that nurse, we're going to get an alarm. The privacy team's going to go, "Oh, well, were they supposed to look at that record?" I'm just giving you, kind of, like two or three uses cases, but there's about thirty of them. >> Yeah, sure, I mean, celebrities whether it's Donald Trump who probably went there at some point. Everyone wants to get his taxes and records to just general patient care. >> Just general patient care. Yeah, exactly, and the privacy of our patients is paramount. I mean, especially in this digital age where, like we talked about earlier, everyone's going after making a human do something silly, right? We want to ensure that our humans, our nurses, our best in class patient care professionals are not doing something with your record that they're not supposed to. >> Interviewer: Well John, I want to hear your thoughts on this story I did a couple weeks ago called the Industrial IOT Apocalypse: Now or Later? And the provocative story was simply trying to raise awareness that malware and spear phishing is just tactics for that. Endpoint is critical, obviously. >> Sure. >> You pointed that out, everyone kind of knows that . >> Sure. >> But until someone dies, until there's a catastrophe where you can take over physical equipment, whether it's a self-driving bus, >> Frushour: Yeah. >> Or go into a hospital and not just do ransom ware, >> Frushour: Absolutely. >> Actually using industrial equipment to kill people. >> Sure. >> Interviewer: To cause a lot of harm. >> Right. >> This is an industrial, kind of the hacking kind of mindset. There's a lot of conversations going on, not enough mainstream conversations, but some of the top people are talking about this. This is kind of a concern. What's your view on this? Is it something that needs to be talked about more of? Is it just BS? Should it be... Is there any signal there that's worth talking about around protecting the physical things that are attached to them? >> Oh, absolutely, I mean this is a huge, huge area of interest for us. Medical device security at New York Presbyterian, we have anywhere from about eighty to ninety thousand endpoints across the enterprise. Every ICU room in our organization has about seven to ten connected devices in the ICU room. From infusion pumps to intubation machines to heart rate monitors and SPO2 monitors, all this stuff. >> Interviewer: All IP and connected. >> All connected, right. The policy or the medium in which they're connected changes. Some are ZP and Bluetooth and hard line and WiFi, and we've got all these different protocols that they use to connect. We buy biomedical devices at volume, right? And biomedical devices have a long path towards FDA certification, so a lot of the time they're designed years before they're fielded. And when they're fielded, they come out and the device manufacturer says, "Alright, we've got this new widget. It's going to, you know, save lives, it's a great widget. It uses this protocol called TLS 1.0." And as a security professional I'm sitting there going, "Really?" Like, I'm not buying that but that's kind of the only game, that's the only widget that I can buy because that's the only widget that does that particular function and, you know, it was made. So, this is a huge problem for us is endpoint device security, ensuring there's no vulnerabilities, ensuring we're not increasing our risk profile by adding these devices to our network and endangering our patients. So it's a huge area. >> And also compatible to what you guys are thinking. Like I could imagine, like, why would you want a multi-threaded processor on a light bulb? >> Frushour: Yeah. >> I mean, scope it down, turn it on, turn it off. >> Frushour: Scope it down for its intended purpose, yeah, I mean, FDA certification is all about if the device performs its intended function. But, so we've, you know, we really leaned forward, our CSO has really leaned forward with initiatives like the S bomb. He's working closely with the FDA to develop kind of a set of baseline standards. Ports and protocols, software and services. It uses these libraries, It talks to these servers in this country. And then we have this portfolio that a security professional would say, "Okay, I accept that risk. That's okay, I'll put that on my network moving on." But this is absolutely a huge area of concern for us, and as we get more connected we are very, very leaning forward on telehealth and delivering a great patient experience from a mobile device, a phone, a tablet. That type of delivery mechanism spawns all kinds of privacy concerns, and inter-operability concerns with protocol. >> What's protected. >> Exactly. >> That's good, I love to follow up with you on that. Something we can double down on. But while we're here this morning I want to get back to data. >> Frushour: Sure. >> Thank you, by the way, for sharing that insight. Something I think's really important, industrial IOT protection. Diverse data is really feeds a lot of great machine learning. You're only as good as your next blind spot, right? And when you're doing pattern recognition by using data. >> Frushour: Absolutely. >> So data is data, right? You know, telecraft, other data. Mixing data could actually be a good thing. >> Frushour: Sure, sure. >> Most professionals would agree to that. How do you look at diverse data? Because in healthcare there's two schools of thought. There's the old, HIPAA. "We don't share anything." That client privacy, you mentioned that, to full sharing to get the maximum out of the AI or machine learning. >> Sure. >> How are you guys looking at that data, diverse data, the sharing? Cause in security sharing's good too, right? >> Sure, sure, sure. >> What's your thoughts on sharing data? >> I mean sharing data across our institutions, which we have great relationships with, in New York is very fluid at New York Presbyterian. We're a large healthcare conglomerate with a lot of disparate hospitals that came as a result of partnership and acquisition. They don't all use the same electronic health record system. I think right now we have seven in play and we're converging down to one. But that's a lot of data sharing that we have to focus on between seven different HR's. A patient could move from one institution to the next for a specialty procedure, and you got to make sure that their data goes with them. >> Yeah. >> So I think we're pretty, we're pretty decent at sharing the data when it needs to be shared. It's the other part of your question about artificial intelligence, really I go back to like dedication analytics. A large part of the medication analytics platform that we designed does a lot of anomaly detections, anomaly detection on diversion. So if we see that, let's say you're, you know, a physician and you do knee surgeries. I'm just making this up. I am not a clinician, so we're going to hear a lot of stupidity here, but bare with me. So you do knee surgeries, and you do knee surgeries once a day, every day, Monday through Friday, right? And after that knee surgery, which you do every day in cyclical form, you prescribe two thousand milligrams of Vicodin. That's your standard. And doctors, you know, they're humans. Humans are built on patterns. That's your pattern. Two thousand milligrams. That's worked for you; that's what you prescribe. But all of the sudden on Saturday, a day that you've never done a knee surgery in your life for the last twenty years, you all of a sudden perform a very invasive knee surgery procedure that apparently had a lot of complications because the duration of the procedure was way outside the bounds of all the other procedures. And if you're kind of a math geek right now you're probably thinking, "I see where he's going with this." >> Interviewer: Yeah. >> Because you just become an anomaly. And then maybe you prescribe ten thousand milligrams of Vicodin on that day. A procedure outside of your schedule with a prescription history that we've never seen before, that's the beauty of funneling this data into Splunk's ML Toolkit. And then visualizing that. I love the 3D visualization, right? Because anybody can see like, "Okay, all this stuff, the school of phish here is safe, but these I've got to focus on." >> Interviewer: Yeah. >> Right? And so we put that into the ML Toolkit and then we can see, "Okay, Dr. X.." We have ten thousand, a little over ten thousand physicians across New York Presbyterian. Doctor X right over here, that does not look like a normal prescriptive scenario as the rest of their baseline. And we can tweak this and we can change precision and we can change accuracy. We can move all this stuff around and say, "Well, let's just look on medical record number, Let's just focus on procedure type, Let's focus on campus location. What did they prescribe from a different campus?" That's anomalous. So that is huge for us, using the ML Toolkit to look at those anomalies and then drive the privacy team, the risk teams, the pharmacy analytics teams to say, "Oh, I need to go investigate." >> So, that's a lot of heavy lifting for ya? Let you guys look at data that you need to look at. >> Absolutely. >> Give ya a (mumbles). Final question, Splunk, in general, you're happy with these guys? Obviously, they do a big part of your data. What should people know about Splunk 2019, this year? And are you happy with them? >> Oh, I mean Splunk has been a great partner to New York Presbyterian. We've done so much incredible development work with them, and really, what I like to talk about is Splunk for healthcare. You know, we've created, we saw some really important problems in our space, in this article. But, we're looking, we're leaning really far forward into things like risk based analysis, peri-op services. We've got a microbial stewardship program, that we're looking at developing into Splunk, so we can watch that. That's a huge, I wouldn't say as big of a crisis as the opioid epidemic, but an equally important crisis to medical professionals across this country. And, these are all solvable problems, this is just data. Right? These are just events that happen in different systems. If we can get that into Splunk, we can cease the archaic practice of looking at spreadsheets, and look up tables and people spending days to find one thing to investigate. Splunk's been a great partner to us. The tool it has been fantastic in helping us in our journey to provide best in-class patient care. >> Well, congratulations, John Frushour, Deputy Chief Information Security Officer, New York Presbyterian. Thanks for that insight. >> You're welcome. >> Great (mumbles) healthcare and your challenge and your opportunity. >> Congratulations for the award winner Data to Everything award winner, got to get that slogan. Get used to that, it's two everything. Getting things done, he's a doer. I'm John Furrier, here on theCube doing the Cube action all day for three days. We're on day two, we'll be back with more coverage, after this short break. (upbeat music)

>>live from Washington D. C. It's the Cube covering Bumi World 19 to Bide Movie. >>Hey, welcome back to the Cubes Coverage of Bumi World 19 from Washington D. C. I'm Lisa Martin with John Ferrier and John and I have a Cube alumni sitting with us. We have the chief product officer off. Del blew me. Steve would Steve, Welcome back. >>Thank you. It's great to be back. I could see again. John. Great must meet you >>back. Wise Enjoyed your keynote this morning, Man. There were so many nuggets and there I couldn't type faster. But one of my favorite things that you said is that no one is asking for less data. Slower? >>Yes, OK did I like kind of like saying because it frames things very clearly. It's just because it's clearly a prole. Every relates to him in the audience, but it was kind of amusing, so they've really got it immediately as I get that, that's a fair statement, so >>so like, and then you kind of took us the audience back. Thio 11 months ago at Bumi World 18. Some of the things that you guys said this is what we're going to be really focused on redefining the eye and I pass to be intelligent. Give her audience who wasn't able to see your keynote A little bit of that historical from 11 months ago. So what you guys are delivering today what the Bumi platform looks like today? >>Yeah, sure. So I mean, a lot of showed last Army, we kind of owe. Then we feel like we is like craters. The industry have to kind of try lead it. Where? Where is it going next? That's our big kind of duty, I guess. And so it's been taken over when we had the founder of booming attend, which was nice, but yes, so the big thing we should Last year was kind of the next generation, which is really a unified look and feel super easy to build applications that spend all of the portfolio and art in our that we offer our customers. We wanted to make it very collaborative, so users of business or business analysts or quick technical people can work together and use. Our platform is a collaboration space of the right controls in place. Eso stuff like that was really good to show that our new solutions. Overview. We've been definitely encouraging partners to put Maur intellectual property into our platform to excel, help accelerate their customers. Helping our customers just get people on board as quickly as possible. In fact, actually owned boarding employees on boarding was the solution we showed last year. >>That was fantastic. I couldn't believe how complex that was at Bumi. And when you guys said, We've got to change this huge improvements. >>Yeah, well, it was sort of a discovery that came up from one of our cells. Engineers got Andy Tiller did a fantastic job. He didn't enjoy his, um, his own boarding experience abuse me and then sort of building a solution. And we're like, we like we can actually do this way better on the platform. But what was amazing was that even for a company the size of Bumi, which is about 1000 people, we have, like, nearly 100 integration points and systems had to be coordinated to on board a single employee 100. Yeah, it's a lot, you know. So it became a really connectivity problem, actually, on >>boarding >>bits relatively easy. It's just, like connected all these systems. That's the hard bit. So yeah, we're excited to show that I think we got a kick out of seeing you together than we give progress on how we're moving that forward with various demos >>you don't want to ask you. Last year we asked the chief operating officer and the CEO Bumi what their investment priorities were going into the next year. And they said Number one was product. So that was a key thing. First and foremost go to market and then customer equation. But a product has been a big focus. That continues to be. What >>is >>the problem? Does it mean product when your chief product officer, what do you overseeing? Talk about What is the product? What is the platform And is there a difference? >>Yeah, I mean, so we we talk about the problem because we're in the product group, but we definitely see it as a platform. The investment in product is great. It means I get to spend lots of money like about my new converse. I won't try to show them, but way, but yeah, I mean, the investment partners being that we know that as we get Maur is this is this economy keeps building of integration and connective iti wanna continue to hold our leadership. We need to invest in product to make it easier. The expectations of our users is that they get a really premium experience when they're on board it onto the platform. We have to make sure we keep up to date with all of that effort. So a lot of what we talked about, it's how one is that we break our product up into discreet service is to allow us to move faster from an engineering perspective. And there's a lot of stuff that goes on there to think about ourselves as a platform to make sure we're fully extensible on. Then providing Maura Maura service is that people can build on our platform. So a lot of that investment just driving those >>activity. Rick was on yesterday talking about the big bets they made early on that are paying off. One of them was Aussie Cloud. On seeing that as you look at the architecture of this kind of new era of clobbering cloud to point, are we calling it? There's new requirements. It's the glue layers being built out. You need data to be accessible on addressable and available in real time, and you have multiple systems to talk to hence the integration you guys are doing. But this new mega trends happening is event driven architectures, which you guys talk about. There's a P I's just going from rest ful to state. And so you have micro service is here. So these air new dynamics Can >>you take >>a minute displaying like what all this means And what is event driven infrastructure? >>Yeah, a venture of architecture. But yeah, that's well, that's what we've been calling it. But yeah, I mean, it's basically that we're going to models where we're responding in real time to things that are happening out there on that revolt that involves a whole new level of scale. But, you know, we're also getting to things like streaming soas. Data come comes in, it's coming in, not in these packets, but it's constantly being fed to you, sir, constantly having to process it. You know, before in the integration space, it was like what? You'd set up a schedule you'd say, move that data at midnight from there to there and then it got faster and booming, provided real time, which was a request response that you send it personally, require a response back. But now it's like we're not going to just send it to you as a discreet thing. We're going to send it to you constantly, so event driven architectures. But how do you handle this continuous influx of data? And it's not getting any less. So how do you kind of manage this? We're being pulled in. Both ends were being pulled. There's never been more data that you never wanted to have faster. So it's like, How do you manage that? So for Bhumi, you know, that's why we're investing so heavily. >>Used to be in the old days when things were slower, events were like a trigger in a network management software alarm notification. Now they're happening. All the time is more and more events and paying attention to what events becomes a non human thing. Yeah, it's a software thing. Is that kind of where this is going? >>Yeah, well, I >>mean, we've been thinking >>a lot about that, like we sort of feel it. One is that we're gonna grow up from being on iPods to more of a data management vendor. We think that, like where the data manager in the future will come from an I pass, that we will be managing your data across like all of these systems from the catalogue and preparation to the, you know, actually integration and surfacing it up in real time and all that kind of streaming side. So I know it's Ah yeah, it's an evolving field for sure. >>One final point on this topic of product AP eyes have been great. They really made the market. Going back to the original Web service is in early two thousands to cloud. Where does a P I go? A A p I to dot or whatever you call it. What's the next Gen Place for AP? Eyes? >>Well, so it's interesting course. So we >>have >>a slightly different view of a pie management. That may be the typical AP management space, which is one thing to declare openly. But I think I >>want to >>go with that. Were right in the sense that cause I would think that because I'm a product, >>it's a good thing for a product. I don't think so Go >>and we're more than a little opinionated. So >>it is here, >>but yeah. Is that like sure. I mean, with a p I You need a gateway you need for the proxy ap eyes. Wherever they may be, wherever they may be developed. Other you build him and Bumi or you code them yourself when you told him, Manage those and throttle and scale and add policies and, you know, have developers registered to use them and monitor their usage and cut them off and have quotas. All that kind of that is old, fantastically good stuff. You know, there's lots of understeer doing a lot of that. We're adding Maur Mork capabilities there. But for us, a p I is really about AP enabling absolutely everything like we're in this world where you got refrigerators, two autonomous vehicles to cloud infrastructure to pivotal to all these different environments. And you have to have a tool that how do you How do you manage a P I across this incredibly disparate landscape of tools, technologies, things, infrastructure and it's one thing to say. OK, we could manage a P eyes and you install our software. Well, that's not good enough because, you know, with our customer like Jack in the box. They have 2200 plus retail locations. Nice have joked in my keynote that it's like painting Golden Gate Bridge. If you had to upgrade your gateway every time there was enough grade needed. It's like pain the Golden Gate Bridge to get to the end and you start all over again. That's 2200 plus retail locations. You know, I work for Dow. Ultimately is the holy owner of our business. He put five billion P seas on the planet. What if you had a gateway on five billion peces like, How do you manage that from a single control plane in the cloud? And that's what we're after. How do you do that huge scale AP enabling literally everything. >>And this was kind of under the concept of run anywhere that waas Yes, >>yes, yeah, and that was because we wanted to emphasize that it was about running Ap eyes and a pen, enabling things wherever they may be. That's why we put it under the run anywhere Banner. >>What's the biggest thing that you guys have done this year from last movie world that you're proud of? In terms of product or technology or something that could be of some obscure something prominent. What do you do? You proud of? What's the big thing? >>Yeah, well, for a point of perspective, it would be the AP I side for sure, because that was that was a big lift. There was a lot of work involved. We kind of moved ourselves forward very, very quickly in our capabilities on a p I with Gateway portal proxy, you know, literally within the span of just over a year. So that was Ah, big left. But I would, you know, because I also run engineering. So I feel like I need to, like, geek out a little bit. I mean, one of my proud things is, actually, we started wrestling and wrangling that 30 terabytes plus of metadata and starting to see what's in there. And like, anything in data science, you know, you're kind of like looking at weaken start. We started seeing all sorts of cool new things. Now I'm not gonna talk about it the inside side, But you start to see new things. We start to see ways that that meditated can be applied. So we built the infrastructure It's huge scale, massive scale they might have meditated, were ingesting and then analyzing eyes helping us, you know, improve productivity across the platforms. We talk a lot about being more efficient, more effective, so you'll see more of that in the pub. >>Can you clear up the just the commentary around the definition around single tenant instance? And when customers do multi tenant, because the benefit of the single tenants what the main core value proposition with the data, the unification of data? That's awesome. But there's also potential opportunities with customs. Might want have a roll run through things. So you have flexibility. Is that true? Is that the definite Take us through what the difference when, when multi tenant kicks in and what's >>well, so on our platform multi tendencies s. So if you think about the build experience when you're your dragon dropping, pointing, clicking, building your work flows or your processes for managing your data, you do that in the cloud, and then you can decide where you wanna put that. So where is that actually gonna be executed? And you can put it in our cloud, which is our multi tenant cloud, and then you. Could we manage it all for you? And that's fantastic. You can point or manage. Cloud service is if you have very specific requirements, usually around security, Sometimes around hyper scale. Well may put you in a manage cloud service environment. But then, if you have very sensitive data, you may want to run that workload and then stole our little run time. Adam, you know behind your firewall so we never see the data. So it's super sensitive. We don't see it. We >>see how >>it's running and we manage it. We have grade that that infrastructure for you, but we never see your data, so it kind of gives you the best of both worlds. You could be a cloud first, cloud only vendor, and you can be a traditional on perimeter. You could be a hybrid of both >>is not a requirement. The product. It's a customer choice. >>It's a total customer choice. I think that's pretty cool. Yeah, and I think actually we're one of the few that does it the way we've been doing for a long time. And it's hard, by the way, because it's like maintaining that compatibility For 10 plus years, is quite difficult to make sure everything works every time. We have, like 9000 >>customers and 80 plus countries. But on the the 30 plus terabytes of anonymous metadata, you are very clear this morning and saying that it's just the metadata that's not the actual have any any, you know, private information from any of our customers. But in terms of leveraging that data for those insights where some of the things that from last spoon me world to this one, that that access to all that data has what some are. Some of the announcements, maybe that came out today that you guys looked at saying, It's these are some of the nuggets that were able to pull out because we have the access to this musing. Maybe it's a I or what not gonna give you >>some examples in one was the the suggested filters. And it was a simple thing. I did sort of like that joke of It's one small step for Bhumi customers, but a giant leap for booming engineering. But because we rebuild a whole bunch of infrastructure to dio but suggested filters just making it easier to query information of various systems. And it is cool because it literally is looking your system, comparing it with other customers systems based on how you've configured in this case Attilio environment and then working out actually, based on what people are doing. This is kind of what the filter might look like for you, which is very, very personalized to the user. Based on intelligence. We have more That's on the bill tight. We have more on the deployment side because you can show you, actually hey, few of built in a p. I do want to deploy it out, too. A raspberry pie will. Actually, you probably want to configure the AP. I like this where you may find you see some issues here, and that's not static information that's evolving from the metadata. We can see the performance of your systems against the Oxy. All right, In that environment, I do it a bit like this. Or if you deploy to say, I Jules, we might make recommendations based on that process of that, a p I or that data quality hub that you wantto excess just make your systems run like this. So it's kind of predicting how you deployed >>I was about to say, Are you helping customers get predicted with us? >>Yes. And there's lots we can do there. I mean, like, so we'll do Maura. Maura. But we can automatically optimize your deployment. So if it's in our cloud, that that'll happens automatically. So helps us, too. But for customers, it's also making just go. Okay, we'll deploy it. And then the leverage that community to so see what works best. The most successful deployment, the most successful architecture and the way you've deployed it is was what you'll be matched with. And then the same with the run time. With monitoring, we can start to look at things and see will. Well, not slowing down a little bit. Actually, it's Linden the string error. A little bit, actually, based on what we've seen before, that system may be about to fall over, so you might want to get all not before completely does what it's gonna do. >>Well, we got you here. I want to get your definition of cloud two point. Oh, on We've been riffing on this. Been more of a takeoff on Web two point. Oh, because cloud one daughter was anything Amazon you know storage. Compute some networking, but it's Amazon that working. But you scale up start ups will go there. It's beautiful thing, but now it's enterprise. Start to embrace cloud with hybrid on premises and deal with all these hard problems and challenges. Crazy opportunity. An operating model for on premises Cloud Club one Dato Amazon. Really easy to work with. Scales are beautiful. Cloud to point is different. I got things to deal with. Observe, abilities, a hot thing you got kubernetes containers you got. How would you define what cloud? Two pointers for Enterprise? >>We'll think because we're all about the data cloud 2.0, is really like for us. Ah, data problem. I mean, it's just like E think before I mean, I was part of cells force for a while. Is this whole idea of like earlier data in the cloud will manageable for you. But when you're getting into the kind of environments were seeing, say, there's just too much data like you, it's not feasible. I mean, give you an example. Bumi itself. We moved our infrastructure customers was transplanted customers from Rackspace to eight of us Last year it was a big engineering lift to do. You can imagine moving 9000 plus customers over on our cloud Ah, design surface that but so we did that, but actually to move the data, it was so much it was actually faster to put the disk drives in the back of a van. No mobile moving over snowball using the wheel network, you know, the engine motor e one and then put the hard drives in. And then we did our sink to bring them back up so that we have the same data in both locations. And that's just an example of the kind of customer data that customers are routinely struggling with. And cloud wasn't set up for that. But that's becoming day to day now, so you need a highly distributed architecture. It was probably why we announced the Adam Fabric, which is really a fabric of connectivity, as much as is a fabric of data, so we don't need to move your data around. You can leave it where it is. We can do some analysis on it as part of an end to end >>Program Cube alumni that I was on the cube a couple weeks ago, he said. Data is the new software, data and software. What's your reaction to that when you hear that? >>To some extent, >>I think that's a CZ, A bit of a business process geek. I think you know this process around data for sure. But But I do think I've heard similar things with, like, actually, applications come and go. Business processes come and go, but the data remains so I think maybe in some respects, your date is the new software Could be a term I I could buy into a Well, >>Steve, it's been great having you on the Cube with John and me sharing all of the things that you guys have done in the last 11 months. I can't wait to see how everything becomes a P. I enabled. Still, next Bumi World, you gotta come back. Yeah, All right. Our pleasure for John Ferrier. I'm Lisa Martin. You're watching the Cube from Bhumi World 19. Thanks for watching