>> Live from Washington, DC, it's theCUBE, covering AWS Public Sector Summit. Brought to you by Amazon Web Services. >> Welcome back everyone to theCUBE's live coverage of the AWS Public Sector Summit, here in our nation's capital. I'm your host, Rebecca Knight, co-hosting with John Furrier. We have two guests for this segment, we have George Gagne, he is the Chief Information Officer at Defense POW/MIA Accounting Agency. Welcome, George. And we have Christopher McDermott, who is the CDO of the POW/MIA Accounting Agency. Welcome, Chris. >> Thank you. >> Thank you both so much for coming on the show. >> Thank you. >> So, I want to start with you George, why don't you tell our viewers a little bit about the POW/MIA Accounting Agency. >> Sure, so the mission has been around for decades actually. In 2015, Secretary of Defense, Hagel, looked at the accounting community as a whole and for efficiency gains made decision to consolidate some of the accounting community into a single organization. And they took the former JPAC, which was a direct reporting unit to PACOM out of Hawaii, which was the operational arm of the accounting community, responsible for research, investigation, recovery and identification. They took that organization, they looked at the policy portion of the organization, which is here in Crystal City, DPMO and then they took another part of the organization, our Life Sciences Support Equipment laboratory in Dayton, Ohio, and consolidated that to make the defense POW/MIA Accounting Agency, Under the Office of Secretary Defense for Policy. So that was step one. Our mission is the fullest possible accounting of missing U.S. personnel to their families and to our nation. That's our mission, we have approximately 82,000 Americans missing from our past conflicts, our service members from World War II, Korea War, Korea, Vietnam and the Cold War. When you look at the demographics of that, we have approximately 1,600 still missing from the Vietnam conflict. We have just over a 100 still missing from the Cold War conflict. We have approximately 7,700 still missing from the Korean War and the remainder of are from World War II. So, you know, one of the challenges when our organization was first formed, was we had three different organizations all had different reporting chains, they had their own cultures, disparate cultures, disparate systems, disparate processes, and step one of that was to get everybody on the same backbone and the same network. Step two to that, was to look at all those on-prem legacy systems that we had across our environment and look at the consolidation of that. And because our organization is so geographically dispersed, I just mentioned three, we also have a laboratory in Offutt, Nebraska. We have detachments in Southeast Asia, Thailand, Vietnam, Laos, and we have a detachment in Germany. And we're highly mobile. We conduct about, this year we're planned to do 84 missions around the world, 34 countries. And those missions last 30 to 45 day increments. So highly mobile, very globally diverse organization. So when we looked at that environment obviously we knew the first step after we got everybody on one network was to look to cloud architectures and models in order to be able to communicate, coordinate, and collaborate, so we developed a case management system that consist of a business intelligence software along with some enterprise content software coupled with some forensics software for our laboratory staff that make up what we call our case management system that cloud hosted. >> So business challenges, the consolidation, the reset or set-up for the mission, but then the data types, it's a different kind of data problem to work, to achieve the outcomes you're looking for. Christopher, talk about that dynamic because, >> Sure. >> You know, there are historical different types of data. >> That's right. And a lot of our data started as IBM punchcards or it started from, you know, paper files. When I started the work, we were still looking things up on microfiche and microfilm, so we've been working on an aggressive program to get all that kind of data digitized, but then we have to make it accessible. And we had, you know as George was saying, multiple different organizations doing similar work. So you had a lot of duplication of the same information, but kept in different structures, searchable in different pathways. So we have to bring all of that together and make and make it accessible, so that the government can all be on the same page. Because again, as George said, there's a large number of cases that we potentially can work on, but we have to be able to triage that down to the ones that have the best opportunity for us to use our current methods to solve. So rather than look for all 82,000 at once, we want to be able to navigate through that data and find the cases that have the most likelihood of success. >> So where do you even begin? What's the data that you're looking at? What have you seen has had the best indicators for success, of finding those people who are prisoners of war or missing in action? >> Well, you know, for some degrees as George was saying, our missions has been going on for decades. So, you know, a lot of the files that we're working from today were created at the time of the incidents. For the Vietnam cases, we have a lot of continuity. So we're still working on the leads that the strongest out of that set. And we still send multiple teams a year into Vietnam and Laos, Cambodia. And that's where, you know, you try to build upon the previous investigations, but that's also where if those investigations were done in the '70s or the '80s we have to then surface what's actionable out of that information, which pathways have we trod that didn't pay off. So a lot of it is, What can we reanalyze today? What new techniques can we bring? Can we bring in, you know, remote sensing data? Can we bring GIS applications to analyze where's the best scenario for resolving these cases after all this time? >> I mean, it's interesting one of the things we hear from the Amazon, we've done so many interviews with Amazon executives, we've kind of know their messaging. So here's one of them, "Eliminate the undifferentiated heavy lifting." You hear that a lot right. So there might be a lot of that here and then Teresa had a slide up today talking about COBOL and mainframe, talk about punch cards >> Absolutely. >> So you have a lot of data that's different types older data. So it's a true digitization project that you got to enable as well as other complexity. >> Absolutely, when the agency was formed in 2015 we really begin the process of an information modernization effort across the organization. Because like I said, these were legacy on-prem systems that were their systems' of record that had specific ways and didn't really have the ability to share the data, collaborate, coordinate, and communicate. So, it was a heavy lift across the board getting everyone on one backbone. But then going through an agency information modernization evolution, if you will, that we're still working our way through, because we're so mobilely diversified as well, our field communications capability and reach back and into the cloud and being able to access that data from geographical locations around the world, whether it's in the Himalayas, whether it's in Vietnam, whether it's in Papua New Guinea, wherever we may be. Not just our fixed locations. >> George and Christopher, if you each could comment for our audience, I would love to get this on record as you guys are really doing a great modernization project. Talk about, if you each could talk about key learnings and it could be from scar tissue. It could be from pain and suffering to an epiphany or some breakthrough. What was some of the key learnings as you when through the modernization? Could you share some from a CIO perspective and from a CDO perspective? >> Well, I'll give you a couple takeaways of what I thought I think we did well and some areas I thought that we could have done better. And for us as we looked at building our case management system, I think step one of defining our problem statement, it was years in planning before we actually took steps to actually start building out our infrastructure in the Amazon Cloud, or our applications. But building and defining that problem statement, we took some time to really take a look at that, because of the different in cultures from the disparate organizations and our processes and so on and so forth. Defining that problem statement was critical to our success and moving forward. I'd say one of the areas that I say that we could have done better is probably associated with communication and stakeholder buy-in. Because we are so geographically dispersed and highly mobile, getting the word out to everybody and all those geographically locations and all those time zones with our workforce that's out in the field a lot at 30 to 45 days at a time, three or four missions a year, sometimes more. It certainly made it difficult to get part of that get that messaging out with some of that stakeholder buy-in. And I think probably moving forward and we still deal regarding challenges is data hygiene. And that's for us, something else we did really well was we established this CDO role within our organization, because it's no longer about the systems that are used to process and store the data. It's really about the data. And who better to know the data but our data owners, not custodians and our chief data officer and our data governance council that was established. >> Christopher you're learnings, takeaways? >> What we're trying to build upon is, you define your problem statement, but the pathway there is you have to get results in front of the end users. You have get them to the people who are doing the work, so you can keep guiding it toward the solution actually meets all the needs, as well as build something that can innovate continuously over time. Because the technology space is changing so quickly and dynamically that the more we can surface our problem set, the more help we can to help find ways to navigate through that. >> So one of the things you said is that you're using data to look at the past. Whereas, so many of the guests we're talking today and so many of the people here at this summit are talking about using data to predict the future. Are you able to look your data sets from the past and then also sort of say, And then this is how we can prevent more POW. Are you using, are you thinking at all, are you looking at the future at all with you data? >> I mean, certainly especially from our laboratory science perspective, we have have probably the most advanced human identification capability in the world. >> Right. >> And recovery. And so all of those lessons really go a long ways to what what information needs to be accessible and actionable for us to be able to, recover individuals in those circumstances and make those identifications as quickly as possible. At the same time the cases that we're working on are the hardest ones. >> Right. >> The ones that are still left. But each success that we have teaches us something that can then be applied going forward. >> What is the human side of your job? Because here you are, these two wonky data number crunchers and yet, you are these are people who died fighting for their country. How do you manage those two, really two important parts of your job and how do you think about that? >> Yeah, I will say that it does amp up the emotional quotient of our agency and everybody really feels passionately about all the work that they do. About 10 times a year our agency meets with family members of the missing at different locations around the country. And those are really powerful reminders of why we're doing this. And you do get a lot of gratitude, but at the same time each case that's waiting still that's the one that matters to them. And you see that in the passion our agency brings to the data questions and quickly they want us to progress. It's never fast enough. There's always another case to pursue. So that definitely adds a lot to it, but it is very meaningful when we can help tell that story. And even for a case where we may never have the answers, being able to say, "This is what the government knows about your case and these are efforts that have been undertaken to this point." >> The fact there's an effort going on is really a wonderful thing for everybody involved. Good outcomes coming out from that. But interesting angle as a techy, IT, former IT techy back in the day in the '80s, '90s, I can't help but marvel at your perspective on your project because you're historians in a way too. You've got type punch cards, you know you got, I never used punch cards. >> Put them in a museum. >> I was the first generation post punch cards, but you have a historical view of IT state of the art at the time of the data you're working with. You have to make that data actionable in an outcome scenario workload work-stream for today. >> Yeah, another example we have is we're reclaiming chest X-rays that they did for induction when guys were which would screen for tuberculosis when they came into service. We're able to use those X-rays now for comparison with the remains that are recovered from the field. >> So you guys are really digging into history of IT. >> Yeah. >> So I'd love to get your perspective. To me, I marvel and I've always been critical of Washington's slowness with respect to cloud, but seeing you catch up now with the tailwinds here with cloud and Amazon and now Microsoft coming in with AI. You kind of see the visibility that leads to value. As you look back at the industry of federal, state, and local governments in public over the years, what's your view of the current state of union of modernization, because it seems to be a renaissance? >> Yeah, I would say the analogy I would give you it's same as that of the industrial revolutions went through in the early 20th century, but it's more about the technology revolution that we're going through now. That's how I'd probably characterize it. If I were to look back and tell my children's children about, hey, the advent of technology and that progression of where we're at. Cloud architecture certainly take down geographical barriers that before were problems for us. Now we're able to overcome those. We can't overcome the timezone barriers, but certainly the geographical barriers of separation of an organization with cloud computing has certainly changed. >> Do you see your peers within the government sector, other agencies, kind of catching wind of this going, Wow, I could really change the game. And will it be a step function into your kind of mind as you kind of have to project kind of forward where we are. Is it going to a small improvement, a step function? What do you guys see? What's the sentiment around town? >> I'm from Hawaii, so Chris probably has a better perspective of that with some of our sister organizations here in town. But, I would say there's more and more organizations that are adopting cloud architectures. It's my understanding very few organizations now are co-located in one facility and one location, right. Take a look at telework today, cost of doing business, remote accessibility regardless of where you're at. So, I'd say it's a force multiplier by far for any line of business, whether it's public sector, federal government or whatever. It's certainly enhanced our capabilities and it's a force multiplier for us. >> And I think that's where the expectation increasingly is that the data should be available and I should be able to act on it wherever I am whenever the the opportunity arises. And that's where the more we can democratize our ability to get that data out to our partners to our teams in the field, the faster those answers can come through. And the faster we can make decisions based upon the information we have, not just the process that we follow. >> And it feeds the creativity and the work product of the actors involved. Getting the data out there versus hoarding it, wall guarding it, asylumming it. >> Right, yeah. You know, becoming the lone expert on this sack of paper in the filing cabinet, doesn't have as much power as getting that data accessible to a much broader squad and everyone can contribute. >> We're doing our part. >> That's right, it's open sourcing it right here. >> To your point, death by PowerPoint. I'm sure you've heard that before. Well business intelligence software now by the click of a button reduces the level of effort for man-power and resources to put together slide decks. Where in business intelligence software can reach out to those structured data platforms and pull out the data that you want at the click of a button and build those presentations for you on the fly. Think about, I mean, if that's our force multiplier in advances in technology of. I think the biggest thing is we understand as humans how to exploit and leverage the technologies and the capabilities. Because I still don't think we fully grasp the potential of technology and how it can be leveraged to empower us. >> That's great insight and really respect what you guys do. Love your mission. Thanks for sharing. >> Yeah, thanks so much for coming on the show. >> Thank you for having us. >> I'm Rebecca Knight for John Ferrer. We will have much more coming up tomorrow on the AWS Public Sector Summit here in Washington, DC. (upbeat music)

>>Hello, and welcome to the cubes presentation of the AWS startup showcase. This is season two, episode four, the ongoing series covering exciting startups from the AWS ecosystem to talk about cyber security. I'm your host, John feer. And today we're excited to join by a Mediatel Walker, CEO of Quin security and sub IER, vice president of product management of sequence security gentlemen, thanks for joining us today on this showcase. >>Thank you, John PRAs. >>So the title of this session is continuous API protection life cycle to discover, detect, and defend security. APIs are part of it. They're hardened, everyone's using them, but they're they're target for malicious behavior. This is the focus of this segment. You guys are in the leading edge of this. What are the biggest challenges for organizations right now in assessing their security risks? Because you're seeing APIs all over the place in the news, just even this week, Twitter had a whistleblower come out from the security group, talking about their security plans, misleading the FTC on the bots and some of the malicious behavior inside the API interface of Twitter. This is really a mainstream Washington post is reporting on it. New York times, all the global outlets are talking about this story. This is the risk. I mean, yeah, this is what you guys do protect against this. >>Yeah, this is absolutely top of mind for a lot of security folks today. So obviously in the media and the type of attack that that is being discussed with this whistleblower coming out is called reputation bombing. This is not new. This has been going on since I would say at least eight to 10 years where the, the bad actors are using bots or automation and ultimately using APIs on these large social media platforms, whether it's Facebook, whether it's Twitter or some other social media platform and messing with the reputation system of those large platforms. And what I mean by that is they will do fake likes, fake commenting, fake retweeting in the case of Twitter. And what that means is that things that are, should not be very popular, all of a sudden become popular. That that way they're able to influence things like elections, shopping habits, personnel. >>We, we work with similar profile companies and we see this all the time. We, we mostly work on some of the secondary platforms like dating and other sort of social media platforms around music sharing and things like video sharing. And we see this all the time. These, these bots are bad. Actors are using bots, but ultimately it's an API problem. It's not just a bot problem. And that's what we've been trying to sort of preach to the world, which is your bot problem is subset of your API security challenges that you deal as an organization. >>You know, IMIA, we talked about this in the past on a previous conversation, but this really is front and center mainstream for the whole world to see around the challenges. All companies face, every CSO, every CIO, every board member organizations out there looking at this security posture that spans not just information technology, but physical and now social engineering. You have all kinds of new payloads of malicious behavior that are being compromised through, through things like APIs. This is not just about CSO, chief information security officer. This is chief security officer issues. What's your reaction >>Very much so I think the, this is a security problem, but it's also a reputation problem. In some cases, it's a data governance problem. We work with several companies which have very restrictive data governance and data regulations or data residency regulations there to conform to those regulations. And they have to look at that. It's not just a CSO problem anymore. In case of the, the news of the day to day, this is a platform problem. This goes all the way to the, that time CTO of Twitter. And now the CEO of Twitter, who was in charge of dealing with these problems. We see as just to give you an example, we, we work, we work with a similar sort of social media platform that allows Oop based login to their platform that is using tokens. You can sort of sign in with Facebook, sign in with Twitter, sign in with Google. These are API keys that are generated and trusted by these social media platforms. When we saw that Facebook leaked about 50 million of these login credentials or API keys, this was about three, four years ago. I wrote a blog about it. We saw a huge spike in those API keys being used to log to other social media platforms. So although one social platform might be taking care of its, you know, API or what problem, if something else gets reached somewhere else, it has a cascading impact on a variety of platforms. >>You know, that's a really interesting dynamic. And if you think about just the token piece that you mentioned, that's kind of under the coverage, that's a technology challenge, but also you get in the business logic. So let's go back and, and unpack that, okay, they discontinue the tokens. Now they're being reused here. In the case of Twitter, I was talking to an executive here in Silicon valley and they said, yeah, it's a cautionary tale, for sure. Although Twitter's a unique situation, but they abstract out the business value and say, Hey, they had an M and a deal on the table. And so if someone wants to unwind that deal, all I gotta say is, Hey, there's a bot problem. And now you have essentially new kinds of risk in the business have nothing to do with some sign the technology, okay. They got a security breach, but here with Twitter, you have an, an, an M and a deal, an acquisition that's being contested because of the, the APIs. So, so if you're in business, you gotta think to yourself, what am I risking with my API? So every organization should be assessing their security risks, tied to their APIs. This is a huge awakening for them. Where should they start? And that's the, that's the core question. Okay. You got my attention risks with the API. What do I do? >>So when I talked to you in my previous interview, the start is basically knowing what to, in most cases, you see these that are hitting the wire much. Every now there is a major in cases you'll find these APIs are targeted, that are not poorly protected. They're absolutely just not protected at all, which means the security team or any sort of team that is responsible for protecting these APIs are just completely unaware of these APIs being there in the first place. And this is where we talk about the shadow it or shadow API problem. Large enterprises have teams that are geo distributed, and this problem is escalated after the pandemic even more because now you have teams that are completely distributed. They do M and a. So they acquire new companies and have no visibility into their API or security practices. And so there are a lot of driving factors why these APIs are just not protected and, and just unknown even more to the security team. So the first step has to be discover your API attack surface, and then prioritize which APIs you wanna target in terms of runtime protection. >>Yeah. I wanna dig into that API kind of attack surface area management, runtime monitoring capability in a second, but so I wanna get you in here too, because we're talking about APIs, we're talking about attacks. What does an API attack look like? >>Yeah, that's a very good question, John, there are really two different forms of attacks of APIs, one type of attack, exploits, APIs that have known vulnerabilities or some form of vulnerabilities. For instance, APIs that may use a weak form of authentication or are really built with no authentication at all, or have some sort of vulnerability that makes them very good targets for an attacker to target. And the second form of attack is a more subtle one. It's called business logic abuse. It's, it's utilizing APIs in completely legitimate manner manners, but exploiting those APIs to exfiltrate information or key sensitive information that was probably not thought through by the developer or the designers or those APIs. And really when we do API protection, we really need to be able to handle both of those scenarios, protect against abuse of APIs, such as broken authentication, or broken object level authorization APIs with that problem, as well as protecting APIs from business logic abuse. And that's really how we, you know, differentiate against other vendors in this >>Market. So just what are the, those key differentiated ways to identify the, in the malicious intents with APIs? Can you, can you just summarize that real quick, the three ways? >>Sure. Yeah, absolutely. There are three key ways that we differentiate against our competition. One is in the, we have built out a, in the ability to actually detect such traffic. We have built out a very sophisticated threat intelligence network built over the entire lifetime of the company where we have very well curated information about malicious infrastructures, malicious operators around the world, including not just it address ranges, but also which infrastructures do they operate on and stuff like that, which actually helps a lot in, in many environments in especially B2C environments, that alone accounts for a lot of efficacy for us in detecting our weed out bad traffic. The second aspect is in analyzing the request that are coming in the API traffic that is coming in and from the request itself, being able to tell if there is credential abuse going on or credential stuffing going on or known patterns that the traffic is exhibiting, that looks like it is clearly trying to attack the attack, the APM. >>And the third one is, is really more sophisticated as they go farther and farther. It gets more sophisticated where sequence actually has a lot of machine learning models built in which actually profile the traffic that is coming in and separate. So the legitimate or learns the legitimate traffic from the anomalous or suspicious traffic. So as the traffic, as the API requests are coming in, it automatically can tell that this traffic does not look like legitimate traffic does not look like the traffic that this API typically gets and automatically uses that to figure out, okay, where is this traffic coming from? And automatically takes action to prevent that attack? >>You know, it's interesting APIs have been part of the goodness of cloud and cloud scale. And it reminds me of the old Andy Grove quote, founder of, in one of the founders of Intel, you know, let chaos, let, let the chaos happen, then reign it in it's APIs. You know, a lot of people have been creating them and you've got a lot of different stakeholders involved in creating them. And so now securing them and now manage them. So a lot of creation now you're starting to secure them and now you gotta manage 'em. This all is now big focus. As you pointed out, what are some of the dynamics that customers who have to deal with on the product side and, and organization, let, let chaos rain, and then rain in the chaos, as, as the saying goes, what, what do companies do? >>Yeah. Typically companies start off with like, like a mayor talked about earlier. Discovery is really the key thing to start with, like figuring out what your API attack surfaces and really getting your arms around that problem. And typically we are finding customers start that off from the security organization, the CSO organization to really go after that problem. And in some cases, in some customers, we even find like dedicated centers of excellence that are created for API security, which go after that problem to be able to get their arms around the whole API attack surface and the API protection problem statement. So that's where usually that problem starts to get addressed. >>I mean, organizations and your customers have to stop the attacks. A lot of different techniques, you know, run time. You mentioned that earlier, the surface area monitoring, what's the choice. What's the, where are, where are, where is everybody? Is everyone in the, in the boiling water, like the frog and boiling water or they do, they know it's happening? Like what did they do? What's their opportunity to get in >>Position? Yeah. So I, I think let's take a step back a little bit, right? What has happened is if you draw the cloud security market, if you will, right. Which is the journey to the cloud, the security of these applications or APIs at a container level, in terms of vulnerabilities and, and other things that market grew with the journey to the cloud, pretty much locked in lockstep. What has happened in the API side is the API space has kind of lacked behind the growth and explosion in the API space. So what that means is APIs are getting published way faster than the security teams are able to sort of control and secure them. APIs are getting published in environments that the security completely unaware of. We talked about in the past about the parameter, the parameter, as we know, it doesn't exist anymore. It used to be the case that you hit a CDN, you terminate your SSL, you stop your layer three and four DDoS. >>And then you go into the application and do the business logic. That parameter is just gone because it's now could be living in multi-cloud environment. It could be living in the on-prem environment, which is PubNet is friendly. And so security teams that are used to protecting apps, using a perimeter defense plus changes, it's gone. You need to figure out where your perimeter is. And therefore we sort of recommend an approach, which is have a uniform view across all your APIs, wherever they could be distributed and have a single point of control across those with a solution like sequence. And there are others also in this space, which is giving you that uniform view, which is first giving you that, you know, outside and looking view of what APIs to protect. And then let's, you sort of take the journey of securing the API life cycle. >>So I would say that every company now hear me out on this indulges me for a second. Every company in the world will be non perimeter based, except for maybe 5% because of maybe unique reason, proprietary lockdown, information, whatever. But for most, most companies, everyone will be in the cloud or some cloud native, non perimeter based security posture. So the question is, how does your platform fit into that trajectory? And specifically, why are you guys in the position in your mind to help customers solve this API problem? Because again, APIs have been the greatest thing about the cloud, right? Yeah. So the goodness is there because of APS. Now you gotta reign it in reign in the chaos. Yeah. What, what about your platform share? What is it, why is it win? Why should customers care about this? >>Absolutely. So if you think about it, you're right, the parameter doesn't exist. People have APIs deployed in multiple environments, multicloud hybrid, you name it sequence is uniquely positioned in a way that we can work with your environment. No matter what that environment is. We're the only player in this space that can protect your APIs purely as a SA solution or purely as an on-prem deployment. And that could be a SaaS platform. It doesn't need to be RackN, but we also support that and we could be a hybrid deployment. We have some deployments which are on your prem and the rest of this solution is in our SA. If you think about it, customers have secured their APIs with sequence with 15 minutes, you know, going live from zero to life and getting that protection instantaneously. We have customers that are processing a billion API calls per day, across variety of different cloud environments in sort of six different brands. And so that scale, that flexibility of where we can plug into your infrastructure or be completely off of your infrastructure is something unique to sequence that we offer that nobody else is offering >>Today. Okay. So I'll be, I'll be a naysayer. Yeah, look, it, we are perfectly coded APIs. We are the best in the business. We're locked down. Our APIs are as tight as a drum. Why do I need you? >>So that goes back to who's answer. Of course, >>Everyone's say that that's, that's great, but that's my argument. >>There are two types of API attacks. One is a tactic problem, which is exploiting a vulnerability in an API, right? So what you're saying is my APIs are secure. It does not have any vulnerability I've taken care of all vulnerabilities. The second type of attack that targets APIs is the business logic. Use this stuff in the news this week, which is the whistleblower problem, which is, if you think APIs that Twitter is publishing for users are perfectly secure. They are taking care of all the vulnerabilities and patching them when they find new ones. But it's the business logic of, you know, REWE liking or commenting that the bots are targeting, which they have no against. Right. And then none of the other social networks too. Yeah. So there are many examples. Uber wrote a program to impersonate users in different geo locations to find lifts, pricing, and driver information and passenger information, completely legitimate use of APIs for illegitimate, illegitimate purpose using bots. So you don't need bots by the way, don't, don't make this about bot versus not. Yeah. You can use APIs sort of for the, the purpose that they're not designed for sort of exploiting their business logic, either using a human interacting, a human farm, interacting with those APIs or a bot form targeting those APIs, I think. But that's the problem when you have, even when you've secured all your problem, all your APIs, you still have to worry about these of challenges. >>I think that's the big one. I think the business logic one, certainly the Twitter highlights that the Uber example is a good one. That is basically almost the, the backlash of having a simplistic API, which people design to. Right. Yeah. You know, as you point out, Twitter is very simple API, hardened, very strong security, but they're using it to maliciously manipulate what's inside. So in a way that perimeter's dead too. Right. So how do you stop that business logic? What's the, what's the solution what's the customer do about that? Because their goal is to create simple, scalable APIs. >>Yeah. I'll, I'll give you a little bit, and then I think Subaru should maybe go into a little bit of the depth of the problem, but what I think that the answer lies in what Subaru spoke earlier, which is our ML. AI is, is good at profiling plus split between the API users, are these legitimate users, humans versus bots. That's the first split we do. The split second split we do is even when these, these are classified users as bots, we will say there are some good bots that are necessary for the business and bad bots. So we are able to split this across three types of users, legitimate humans, good bots and bad bots. And just to give you an example of good bots is there are in the financial work, there are aggregators that are scraping your data and aggregating for end users to consume, right? Your, your, and other type of financial aggregators FinTech companies like MX. These are good bots and you wanna allow them to, you know, use your APIs, whereas you wanna stop the bad bots from using your APIs super, if you wanna add so, >>So good bots versus bad bots, that's the focus. Go ahead. Weigh in, weigh in on your thought on this >>Really breaks down into three key areas that we talk about here, sequence, right? One is you start by discovering all your APIs. How many APIs do I have in my environment that ly immediately highlight and say, Hey, you have, you know, 10,000 APIs. And that usually is an eye opener to many customers where they go, wow. I thought we had a 10th of that number. That usually is an eyeopener for them to, to at least know where they're at. The second thing is to tell them detection information. So discover, detect, and defend detect will tell them, Hey, your APIs are getting traffic from. So and so it addresses so and so infrastructure. So and so countries and so on that usually is another eye opener for them. They then get to see where their API traffic is coming from. Let's say, if you are a, if you're running a pizza delivery service out of California and your traffic is coming from Eastern Europe to go, wait a minute, nobody's trying, I'm not, I'm not, I don't deliver pizzas in Eastern Europe. Why am I getting traffic from that part of the world? So that sort of traffic immediately comes up and it will tell you that it is hitting your unauthenticated API. It is hitting your API. That has, that is vulnerable to a broken object level, that authorization, vulnerable be and so on. >>Yeah, I think, and >>Then comes the different aspect. Yeah. The different aspect is where you can take action and say, I wanna block certain types of traffic, or I wanna rate limit certain types of traffic. If, if you're seeing spikes there or you could maybe insert header so that it passes on to the end application and the application team can use that bit to essentially take a, a conscious response. And so, so the platform is very flexible in allowing them to take an action that suits their needs. >>Yeah. And I think this is the big trend. This is why I like what you guys are doing. One APIs we're built for the goodness of cloud. They're now the plumbing, you know, anytime you see plumbing involved, connection points, you know, that's pretty important. People are building it out and it has made the cloud what it is. Now, you got a security challenge. You gotta add more intelligence, more smarts to it. This is where I think platform versus tools matter. Can you guys just quickly share your thoughts on that? Cuz a lot of your customers and, and future customers have dealt with the sprawls of all these different tools. Right? I got a tool for this. I got a tool for that, but people are gravitating towards platforms, but how many platforms can a customer have? So again, this brings up the point point around how you guys are engaging with customers. Can you share your thoughts on tooling platforms? Your customers are constantly inundated with the same tsunami. Isn't new thing. Why, what, how should they look at this? >>Yeah, I mean, we don't wanna be, we don't wanna add to that alert fatigue problem that affects much of the cybersecurity industry by generating a whole bunch of alerts and so on. So what we do is we actually integrate very well with S IEM systems or so systems and allow customers to integrate the information that we are detecting or mitigating and feed them onto enterprise systems like a Splunk or a Datadog where they may have sophisticated processes built in to monitor, you know, spikes in anomalous traffic or actions that are taken by sequence. And that can be their dashboard where a whole bunch of alerting and reporting actually happens. So we play in the security ecosystem very well by integrating with other products and integrate very tightly with them, right outta the box. >>Okay. Mia, this is a wrap up now for the showcase. Really appreciate you guys sharing your awesome technology and very relevant product for your customers and where we are right now in this we call Supercloud or now multi-cloud or hybrid world of cloud. Share a, a little bit about the company, how people can get involved in your solution, how they can consume it and things they should know about, about sequence security. >>Yeah, we've been on this journey, an exciting journey it's been for, for about eight years. We have very large fortune 100 global 500 customers that use our platform on a daily basis. We have some amazing logos, both in Europe and, and, and in us customers are, this is basically not the shelf product customers not only use it, but depend on sequence. Several retailers. We are sitting in front of them handling, you know, black Friday, cyber, Monday, Christmas shopping, or any sort of holiday seasonality shopping. And we have handled that the journey starts by, by just simply looking at your API attack surface, just to a discover call with sequence, figure out where your APIs are posted work with you to prioritize how to protect them in a sort of a particular order and take the whole life cycle with sequence. This is, this is an exciting phase exciting sort of stage in the company's life. We just raised a very sort of large CDC round of funding in December from Menlo ventures. And we are excited to see, you know, what's next in, in, in the next, you know, 12 to 18 months. It certainly is the, you know, one of the top two or three items on the CSOs, you know, budget list for next year. So we are extremely busy, but we are looking for, for what the next 12 to 18 months are, are in store for us. >>Well, congratulations to all the success. So will you run the roadmap? You know, APIs are the plumbing. If you will, you know, they connection points, you know, you want to kind of keep 'em simple, as they say, keep the pipes dumb and make the intelligence around it. You seem to see more and more intelligence coming around, not just securing it, but does, where does this go in your mind? Where, where do we go beyond once we secure everything and manage it properly, APRs, aren't going away, they're only gonna get better and smarter. Where's the intelligence coming share a little bit. >>Absolutely. Yeah. I mean, there's not a dull moment in the space. As digital transformation happens to most enterprise systems, many applications are getting transformed. We are seeing an absolute explosion in the volume of APIs and the types of APIs as well. So the applications that were predominantly limited to data centers sort of deployments are now splintered across multiple different cloud environments are completely microservices based APIs, deep inside a Kubernetes cluster, for instance, and so on. So very exciting stuff in terms of proliferation of volume of APIs, as well as types of APIs, there's nature of APIs. And we are building very sophisticated machine learning models that can analyze traffic patterns of such APIs and automatically tell legitimate behavior from anomalous or suspicious behavior and so on. So very exciting sort of breadth of capabilities that we are looking at. >>Okay. I mean, yeah. I'll give you the final words since you're the CEO for the CSOs out there, the chief information security officers and the chief security officers, what do you want to tell them? If you could give them a quick shout out? What would you say to them? >>My shout out is just do an assessment with sequence. I think this is a repeating thing here, but really get to know your APIs first, before you decide what and where to protect them. That's the one simple thing I can mention for thes >>Am. Thank you so much for, for joining me today. Really appreciate it. >>Thank you. >>Thank you. Okay. That is the end of this segment of the eight of his startup showcase. Season two, episode four, I'm John for your host and we're here with sequin security. Thanks for watching.

>>Hey, welcome back everyone to the cubes coverage of eaters reinvent 2021. So our third day wall-to-wall coverage. I'm my coach, Dave Alonzo. He we're getting all the action two sets in person. It's also a virtual hybrid events with a lot of great content online, bringing you all the fresh voices, all the knowledge, all the news and all the action and got great guests here today. As your renderer, managing director of AWS is Europe, middle east, and Africa also known as EMIA. Welcome to the cube. Welcome, >>Welcome. Thanks for coming on. Lovely to be here. >>So Europe is really hot. Middle east Africa. Great growth. The VC culture in Europe specifically has been booming this year. A lot of great action. We've done many cube gigs out there talking to folks, uh, entrepreneurship, cloud, native growth, and then for us it's global. It's awesome. So first question got to ask you is, is you're new to AWS? What brought you here? >>Yeah, no, John, thank you so much. I've been here about three and a half months now, actually. Um, so what brought me here? Um, I have been in and around the tech world since I was a baby. Um, my father was an entrepreneur. I sold fax machines and microfilm equipment in my early days. And then my career has spanned technology in some form or the other. I was at EMC when we bought VMware. Uh, I was a Colt when we did a FinTech startup joined Schneider in my background, which is industrial tech. So I guess I'm a bit of a tech nerd, although I'm not an engineer, that's for sure. The other thing is I've spent a huge part of my career advising clients. And so while I was at McKinsey on business transformation and cloud keeps coming up, especially post pandemic, huge, huge, huge enabler, right of transformation. So when I got the call from AWS, I thought here's my opportunity to finally take what companies are wrestling with, bring together a pioneer in cloud with our enterprise and start-up and SMB clients connect those dots between business and technology and make things happen. So it real magic. So that's what brought me here. And I guess the only other thing to say is I'd heard a lot of other culture, customer mash, obsession, and leadership principles. >>That's why I'm here. It's been a great success. I got to ask you too, now that your new ostium McKinsey, even seeing the front lines, all the transformation, the pandemic has really forced everybody globally to move faster. Uh, things like connect were popular in EMEA. How, how is that going out? There's at the same kind of global pressure on the digital transformation with cloud? What are you seeing out there? >>I've been traveling since I joined, uh, around 10 of the countries already. So Ben planes, trains, automobiles, and what you definitely see is massive acceleration. And I think it's around reinvention of the business. So people are adopting cloud because it's obviously there's cost reasons. There's MNA reasons. There's really increasingly more about innovating. How do I innovate my business? How do I reinvent my business? So you see that constantly. Um, and whether you're a enterprise company or you're a startup, they're all adopting cloud in different, different ways. Um, I mean, I want to tell a core to stack because it's really interesting. And Adam mentioned this in his keynote five to 15% only of workloads have moved to the cloud. So there's a tremendous runway ahead of us. Um, and the three big things on people's minds helped me become a tech company. So it doesn't matter who you are, you're retail, whether you're life sciences or healthcare. You've probably heard about the Roche, uh, work that we're doing with Roche around accelerating R and D with data, or if you're a shoes Addie desk, how do you accelerate again, your personalized experiences? So it doesn't matter who you have helped me become a tech company, give me skills, digital skills, and then help me become a more sustainable company. Those are the three big things I'm thinking of. >>So a couple of things to unpack there. So think about it. Transformation. We still have a long way to go to your point, whatever 10, 15%, depending on which numbers you look at. We've been talking a lot in the cube about the next decade around business transformation, deeper business integration, and the four smarts to digital. And the woke us up to that, accelerated that as you say, so as you travel around to customers in AMEA, what are you hearing with regard to that? I mean, many customers maybe didn't have time to plan. Now they can sit back and take what they've learned. What are you hearing? >>Yeah. And it's, it's a little bit different in different places, right? So, I mean, if you start, if you look at, uh, you know, our businesses, for example, in France, if you look at our businesses in Iberia or Italy, a lot of them are now starting they're on the, at least on the enterprise front, they are now starting to adopt cloud. So they stepping back and thinking about their overall strategy, right? And then the way that they're doing it is actually they're using data as the first trigger point. And I think that makes it easier to migrate because if you, if you look at large enterprises and if you think of the big processes that they've got and all the mainframes and everything that they need to do, if you S if you look at it as one big block, it's too difficult. But when you think about data, you can actually start to aggregate all of your data into one area and then start to analyze and unpack that. >>So I think what I'm seeing for sure is in those countries, data is the first trigger. If you go out to Israel, well that you've got all, it's really start up nation as you know, right. And then we've got more of the digital natives and they want to, you know, absorb all of the innovation that we're throwing at them. And you've heard a lot here at reinvent on some of the things, whether it's digital twins or robotics, or frankly, even using 5g private network, we've just announcement. They are adopting innovation and really taking that in. So it really does differ, but I think the one big message I would leave you with is bringing industry solutions to business is critical. So rather than just talking it and technology, we've got to be able to bring some of what we've done. So for example, the Goldman Sachs financial cloud, bring that to the rest of financial services companies and the media, or if you take the work we're doing on industrials and IOT. So it's really about connecting what industry use cases with. >>What's interesting about the Goldman Dave and I were commenting. I think we coined the term, the story we wrote on Thursday last week, and then PIP was Sunday superclouds because you look at the rise of snowflake and Databricks and Goldman Sachs. You're going to start to see people building on AWS and building these super clouds because they are taking unique platform features of AWS and then sacrificing it for their needs, and then offering that as a service. So there's kind of a whole nother tier developing in the natural evolution of clouds. So the partners are on fire right now because the creativity, the market opportunities are there to be captured. So you're seeing this opportunity recognition, opportunity, capture vibe going on. And it's interesting. I'd love to get your thoughts on how you see that, because certainly the VCs are here in force. I did when I saw all the top Silicon valley VCs here, um, and some European VCs are all here. They're all seeing this. >>So pick up on two things you mentioned that I think absolutely spot on. We're absolutely seeing with our partners, this integration on our platform is so important. So we talk about the power of three, which is you bring a JSI partner, you bring an ISV partner, you bring AWS, you create that power of three and you take it to our customers. And it doesn't matter which industry we are. Our partner ecosystem is so rich. The Adam mentioned, we have a hundred thousand partners around the world, and then you integrate that with marketplace. Um, and the AWS marketplace just opens the world. We have about 325,000 active customers on marketplace. So sassiphy cation integration with our platform, bringing in the GSI and the NSIs. I think that's the real power to, to, to coming back to your point on transformation on the second one, the unicorns, you know, it's interesting. >>So UK France, um, Israel, Mia, I spent a lot of time, uh, recently in Dubai and you can see it happening there. Uh, Africa, Nigeria, South Africa, I mean all across those countries, you're saying huge amount of VC funding going in towards developers, towards startups to at scale-ups more and more of a, um, our startup clients, by the way, uh, are actually going IPO. You know, initially it used to be a lot of M and a and strategic acquisitions, but they have actually bigger aspirations and they're going IPO and we've seen them through from when they were seed or pre-seed all the way to now that they are unicorns. Right? So that there's just a tremendous amount happening in EMEA. Um, and we're fueling that, you know, you know, I mean, born in the cloud is easy, right? In terms of what AWS brings to the table. >>Well, I've been sacred for years. I always talked to Andy Jassy about this. Cause he's a big sports nut. When you bring like these stadiums to certain cities that rejuvenates and Amazon regions are bringing local rejuvenation around the digital economies. And what you see with the startup culture is the ecosystems around it. And Silicon valley thrives because you have all the service providers, you have all the fear of failure goes away. There's support systems. You start to see now with AWS as ecosystem, that same ecosystem support the robustness of it. So, you know, it's classic, rising tide floats all boats kind of vibe. So, I mean, we don't really have our narrative get down on this, but we're seeing this ecosystem kind of play going on. Yeah. >>And actually it's a real virtuous circle, or we call flywheel right within AWS because a startup wants to connect to an enterprise. An enterprise wants to connect to a startup, right? A lot of our ISV partners, by the way, were startups. Now they've graduated and they're like very large. So what we are, I see our role. And by the way, this is one of the other reasons I came here is I see our role to be able to be real facilitators of these ecosystems. Right. And, you know, we've got something that we kicked off in EMEA, which I'm really proud of called our EMEA startup loft accelerator. And we launched that a web summit. And the idea is to bring startups into our space virtually and physically and help them build and help them make those connections. So I think really, I really do think, and I enterprise clients are asking us all the time, right? Who do I need to involve if I'm thinking IOT, who do I need to involve if I want to do something with data. And that's what we do. Super connectors, >>John, you mentioned the, the Goldman deal. And I think it was Adam in his keynote was talking about our customers are asking us to teach them how to essentially build a Supercloud. I mean, our words. But so with your McKinsey background, I would imagine there's real opportunities there, especially as you, I hear you talk about IMIA going around to see customers. There must be a lot of, sort of non-digital businesses that are now transforming to digital. A lot of capital needs there, but maybe you could talk about sort of how you see that playing out over the next several years in your role and AWS's role in affecting that transfer. >>Yeah, no, absolutely. I mean, you're right actually. And I, you know, maybe I will, from my past experience pick up on something, you know, I was in the world of industry, uh, with Schneider as an example. And, you know, we did business through the channel. Um, and a lot of our channel was not digitized. You know, you had point of sale, electrical distributors, wholesalers, et cetera. I think all of those businesses during the pandemic realized that they had to go digital and online. Right. And so they started from having one fax machine in a store. Real literally I'm not kidding nothing else to actually having to go online and be able to do click and collect and various other things. And we were able with AWS, you can spin up in minutes, right. That sort of service, right. I love the fact that you have a credit card you can get onto our cloud. >>Right. That's the whole thing. And it's about instances. John Adam talked about instances, which I think is great. How do businesses transform? And again, I think it's about unpacking the problem, right? So what we do a lot is we sit down with our customers and we actually map a migration journey with them, right? We look across their core infrastructure. We look at their SAP systems. For example, we look at what's happening in the various businesses, their e-commerce systems, that customer life cycle value management systems. I think you've got to go business by business by business use case by use case, by use case, and then help our technology enable that use case to actually digitize. And whether it's front office or back office. I think the advantages are pretty clear. It's more, I think the difficulty is not technology anymore. The difficulty is mindset, leadership, commitment, the operating model, the organizational model and skills. And so what we have to do is AWS is bringing not only our technology, but our culture of innovation and our digital innovation teams to help our clients on that journey >>Technology. Well, we really appreciate you taking the time coming on the cube. We have a couple more minutes. I do want to get into what's your agenda. Now that you're got you're in charge, got the landscape and the 20 mile stare in front of you. Cloud's booming. You got some personal passion projects. Tell us what your plans are. >>So, um, three or four things, right? Three or four, really big takeaways for me is one. I, I came here to help make sure our customers could leverage the power of the cloud. So I will not feel like my job's been done if I haven't been able to do that. So, you know, that five to 15% we talked about, we've got to go 50, 60, 70%. That that's, that's the goal, right? And why not a hundred percent at some point, right? So I think over the next few years, that's the acceleration we need to help bring in AMEA Americas already started to get there as you know, much more, and we need to drive that into me. And then eventually our APJ colleagues are going to do the same. So that's one thing. The other is we talked about partners. I really want to accelerate and expand our partner ecosystem. >>Um, we have actually a huge growth by the way, in the number of partners signing up the number of certifications they're taking, I really, really want to double down on our partners and actually do what they ask us for, which is join. Co-sell joined marketing globalization. So that's two, I think the third big thing is when you mentioned industry industry industry, we've got to bring real use cases and solutions to our customers and not only talk technology got to connect those two dots. And we have lots of examples to bring by the way. Um, and then for hire and develop the best, you know, we've got a new LP as you know, to strive to be at its best employer. I want to do that in a Mia. I want to make sure we can actually do that. We attract, we retain and we grow and we develop that. >>And the diversity has been a huge theme of this event. It's front and center in virtually every company. >>I am. I'm usually passionate about diversity. I'm proud actually that when I was back at Schneider, I launched something called the power women network. We're a network of a hundred senior women and we meet every month. I've also got a podcast out there. So if anyone's listening, it's called power. Women's speak. It is, I've done 16 over the pandemic with CEOs of women podcast, our women speak >>Or women speak oh, >>And Spotify and >>Everything else. >>And, um, you know, what I love about what we're doing is AWS on diversity and you heard Adam onstage, uh, talk to this. We've got our restock program where we really help under employed and unemployed to get a 12 week intensive course and get trained up on thought skills. And the other thing is, get it helping young girls, 12 to 15, get into stem. So lots of different things on the whole, but we need to do a lot more of course, on diversity. And I look forward to helping our clients through that as well. >>Well, we had, we had the training VP on yesterday. It's all free trainings free. >>We've got such a digital skills issue that I love that we've said 29 million people around the world, free cloud training. >>Literally the th the, the gap there between earnings with cloud certification, you can be making six figures like with cloud training. So, I mean, it's really easy. It's free. It's like, it's such a great thing. >>Have you seen the YouTube video on Charlotte Wilkins? Donald's fast food. She changed her mind. She wanted to take Korea. She now has a tech career as a result of being part of restock. Awesome. >>Oh, really appreciate. You got a lot of energy and love, love the podcast. I'm subscribing. I'm going to listen. We love doing the podcast as well. So thanks for coming on the >>Queue. Thank you so much for having me >>Good luck on anemia and your plans. Thank you. Okay. Cube. You're watching the cube, the leader in global tech coverage. We go to the events and extract the signal from the noise. I'm John furrier with Dave, a lot to here at re-invent physical event in person hybrid event as well. Thanks for watching.

>>Well, hello everybody. I'm John Walls here with the cube, and we're very happy to continue our coverage here of a splunk.com 21. And today we're going to talk about cyber security. Uh, obviously everybody is well aware of a number of, uh, breaches that have happened around the globe, but you might say there's been a surge in trying to prevent those from happening down the road. And I'm going to let our guests explain that Ryan Covar, who is the security strategist at Splunk. Ryan. Good to see you with, uh, with us here on the cube. Glad you could join us today. >>Thank you very much. I've wished we could have been doing this in person, but such as the time of life we live. >>Yeah. We have learned to live on zoom that's for sure. And, uh, it's the next best thing to being there. So, uh, again, thanks for that. Um, well, let's talk about surge, if you will. Um, uh, I know obviously Splunk and data security go hand in hand that is a high priority with the, with the company, but now you have a new initiative that you're just now rolling out to take that to an even higher level. Tell us about that. >>Yeah, something I'm extremely excited to announce. Uh, it's the first time we're really talking about it is that.com 21, which is wonderful. And it's kind of the culmination of my seven years here at Splunk. Uh, before I came to Splunk, I did about 20 years of cyber security research and defense and nation state hunting and threat intelligence and policy and compliance, and just about everything, uh, public sector in the U S and the UK private sector, a couple of different places. So I've kind of been around the block. And one of the things I've found that I'm really passionate about is just being a network defender or a blue teamer. And a lot of my time here at Splunk has been around that. It's been speaking at conferences, doing research, um, coming up with ways to basically defend organizations, but the tools they have at hand and something that we say Alon is, uh, we, we work on the problems of today and tomorrow, not the distant future, right? >>The really practical things. And we had an, you know, there was a little bit of a thing called solar winds. You might've heard of it. Um, that happened earlier in December and we were able to stand up kind of on an ad hoc ragtag group of Splunkers around the world, uh, in a matter of hours. And we worked about 24 hours for panning over to Australia, into a Mia, and then back over to America and able to publish really helpful work to, for our customers to detect or defend or mitigate against what we knew at the time around solar winds, the attack. And then as time went on, we were continuing to write and create material, but we didn't have a group that was focused on it. We were all kind of chipping in after hours or, you know, deep deprecating, other bits of work. >>And I said, you know, we really need to focus on this. This is a big deal. And how can we actually surge up to meet these needs if you will, uh, the play on the punter. So we created an idea of a small team, a dedicated to current events and also doing security research around the problems that are facing around the world insecurity who use Splunk and maybe even those who don't. And that's where the idea of this team was formed. And we've been working all summer. We're releasing our first research project, excuse me, uh, at.com, which is around supply chain, compromise using jaw three Zeke and Splunk, uh, author by myself and primarily Marcus law era. And we have other research projects coming out every quarter, along with doing this work around, just helping people with any sort of immediate cybersecurity threat that we're able to assist with. >>So what are you hoping that security teams can get out of this work? Obviously you're investing a lot of resources and doing the research, I assume, diversifying, you know, the areas and to which you're, um, exploring, um, ultimately what would be the takeaway if I was on the other end, if I was on the client and what would you hope that I would be, uh, extracting from this work? >>Sure. We want to get you promoted. I mean, that's kind of the, the joke of it, but we, we talk a lot. I want to make everyone in the world who use a Splunk or cybersecurity, looked into their bosses and defend their company as fast and quickly as possible. So one of the big, mandates for my team is creating consumable, actionable work and research. So we, you know, we joke a lot that, you know, I have a pretty thick beard here. One might even call it a neck beard and a lot of people in our community, we create things for what I would call wizards, cybersecurity wizards, and we go to conferences and we talk from wizard to wizard, and we kind of sit on our ivory tower on stage and kind of proclaim out how to do things. And I've sat on the other side and sometimes those sound great, but they're not actually helping people with their job today. And so the takeaway for me, what I hope people are able to take away is we're here for you. We're here for the little guys, the network defenders, we're creating things that we're hoping you can immediately take home and implement and do and make better detections and really find the things that are immediate threats to your network and not necessarily having to, you know, create a whole new environment or apply magic. So >>Is there a difference then in terms of say enterprise threats, as opposed to, if I'm a small business or of a medium sized business, maybe I have four or 500 employees as opposed to four or 5,000 or 40,000. Um, what about, you know, finding that ground where you can address both of those levels of, of business and of concern, >>You know, 20 years ago or 10 years ago? I would've answered that question very differently and I fully acknowledge I have a bias in nation state threats. That's what I'm primarily trained in, however, in the last five years, uh, thanks or not. Thanks to ransomware. What we're seeing is the same threats that are affecting and impacting fortune 100 fortune 10 companies. The entire federal government of the United States are the exact same threats that are actually impacting and causing havoc on smaller organizations and businesses. So the reality is in today's threat landscape. I do believe actually the threat is the same to each, but it is not the same level of capabilities for a 100% or 500 person company to a company, the size of Splunk or a fortune 100 company. Um, and that's something that we are actually focusing on is how do we create things to help every size of that business, >>Giving me the tools, right, exactly. >>Which is giving you the power to fight that battle yourself as much as possible, because you may never be able to have the head count of a fortune 100 company, but thanks to the power of software and tools and things like the cloud, you might have some force multipliers that we're hoping to create for you in a much more package consumable method. >>Yeah. Let's go back to the research that you mentioned. Um, how did you pick the first topic? I mean, because this is your, your splash and, and I'm sure there was a lot of thought put into where do we want to dive in >>First? You know, I'd love to say there was a lot of thought put into it because it would make me sound smarter, but it was something we all just immediately knew was a gap. Um, you know, solar winds, which was a supply chain, compromise attack really revealed to many of us something that, um, you know, reporters had been talking about for years, but we never really saw come to fruition was a real actionable threat. And when we started looking at our library of offerings and what we could actually help customers with, I talked over 175 federal and private sector companies around the world in a month and a half after solar winds. And a lot of times the answer was, yeah, we can't really help you with this specific part of the problem. We can help you around all sorts of other places, but like, gosh, how do you actually detect this? >>And there's not a great answer. And that really bothered me. And to be perfectly honest, that was part of the reason that we founded the team. So it was a very obvious next step was, well, this is why we're creating the team. Then our first product should probably be around this problem. And then you say, okay, supply chain, that's really big. That's a huge chunk of work. So the first question is like, well, what can we actually affect change on without talking about things like quantum computing, right? Which are all things that are, you know, blockchain, quantum computing, these are all solutions that are actually possible to solve or mitigate supply chain compromise, but it's not happening today. And it sure as heck isn't even happening tomorrow. So how do we create something that's digestible today? And so what Marcus did, and one of his true skillsets is really refining the problem down, down, down, down. >>And where can we get to the point of, Hey, this is data that we think most organizations have a chance of collecting. These are methodologies that we think people can do and how can they actually implement them with success in their network. And then we test that and then we kind of keep doing a huge fan of the concept of OODA loop, orient, orient, observe, decide, and act. And we do that through our hypothesizing. We kind of keep looking at that and iterating over and over and over again, until we're able to come up with a solution that seems to be applicable for the personas that we're trying to help. And that's where we got out with this research of, Hey, collect network data, use a tool like Splunk and some of our built-in statistical analysis functions and come out the other side. And I'll be honest, we're not solving the problem. >>We're helping you with the problem. And I think that's a key differentiator of what we're saying is there is no silver bullet and frankly, anyone that tells you they can solve supply chain, uh, let me know, cause I want to join that hot new startup. Um, the reality is we can help you go from a field of haystacks to a single haystack and inside that single haystack, there's a needle, right? And there's actually a lot of value in that because before the PR problem was unapproachable, and now we've gotten it down to saying like, Hey, use your traditional tools, use your traditional analytic craft on a much smaller set of data where we've pretty much verified that there's something here, but look right here. And that's where we kind of focused. >>You talked about, you know, and we all know about the importance and really the emphasis that's put on data protection, right? Um, at the same time, can you use data to help you protect? I mean, is there information or insight that could be gleaned from, from data that whether it's behavior or whatever the case might be, that, that not only, uh, is something that you can operationalize and it's a good thing for your business, but you could also put it into practice in terms of your security practices to >>A hundred percent. The, the undervalued aspect of cybersecurity in my opinion, is elbow grease. Um, you can buy a lot of tools, uh, but the reality is to get value immediately. Usually the easiest place to start is just doing the hard detail oriented work. And so when you ask, is there data that can help you immediately data analytics? Actually, I go to, um, knowing what you have in your network, knowing what you have, that you're actually trying to protect asset and inventory, CMDB, things like this, which is not attractive. It's not something people want to talk about, but it's actually the basis of all good security. How do you possibly defend something if you don't know what you're defending and where it is. And something that we found in our research was in order to detect and find anomalous behavior of systems communicating outbound, um, it's too much. >>So what you have to do is limit the scope down to those critical assets that you're most concerned about and a perfect example of critical asset. And there's no, no shame or victim blaming here, put on solar winds. Uh, it's just that, that is an example of an appliance server that has massive impact on the organization as we saw in 2020. And how can you actually find that if you don't know where it is? So really that first step is taking the data that you already have and saying, let's find all the systems that we're trying to protect. And what's often known as a crown jewels approach, and then applying these advanced analytics on top of those crown jewel approaches to limit the data scope and really get it to just what you're trying to protect. And once you're positive that you have that fairly well defended, then you go out to the next tier and the next tier in next year. And that's a great approach, take things you're already doing today and applying them and getting better results tomorrow. >>No, before I let you go, um, I I'd like to just have you put a, uh, a bow on surge, if you will, on that package, why is this a big deal to you? It's been a long time in the making. I know you're very happy about the rollout of this week. Um, you know, what's the impact you want to have? Why is it important? >>We did a lot of literature review. I have a very analytical background. My time working at DARPA taught me a lot about doing research and development and on laying out the value of failure, um, and how much sometimes even failing as long as you talk about it and talk about your approach and methodology and share that is important. And the other part of this is I see a lot of work done by many other wonderful organizations, uh, but they're really solving for a problem further down the road or they're creating solutions that not everyone can implement. And so what I think is so important and what's different about our team is we're not only thinking differently, we're hiring differently. You know, we have people who have a threat intelligence background from the white house. We have another researcher who did 10 years at DARPA insecurity, research and development. >>Uh, we've recently hired a, a former journalist who she's made a career pivot into cybersecurity, and she's helping us really review the data and what people are facing and come up with a real connection to make sure we are tackling the right problems. And so to me, what I'm most excited about is we're not only trying to solve different problems. And I think what most of the world is looking at for cybersecurity research, we've staffed it to be different, think different and come up with things that are probably a little less, um, normal than everyone's seen before. And I'm excited about that. >>Well, and, and rightly so, uh, Ryan, thanks for the time, a pleasure to have you here on the cube and, uh, the information again, the initiative is Serge, check it out, uh, spunk very much active in the cyber security protection business. And so we have certainly appreciate that effort. Thank you, Ryan. >>Well, thank you very much, John. You bet Ryan, >>Covar joining us here on our cube coverage. We continue our coverage of.com for 21.

>>From around the globe. It's the cube with digital coverage of IBM. Think 2021 brought to you by IBM. >>Hello everyone. Welcome back to the cubes. Ongoing virtual coverage of IBM. Think 2021. This is our second virtual think. And we're going to talk about what's on the minds of CTOs with a particular point of view from the EMEA region. I'm pleased to welcome rushy Parmer, who is an IBM fellow and vice-president of technology for AMEA that region. Hello Russia. Good to see you. >>Great to see you. So >>Let me start by, by asking, talk a little bit about the role of the CTO and why is it necessarily important to focus on the CTO role versus say some of the other technology practitioner roles? >>Yeah. You know, as you look at all the range of roles of the gut in the it department, the CTO is uniquely placed in looking forward at how technology and how digitization is going to make a difference in the business. But also at the same time, is there as the kind of thought leader for how they're going to really, um, reimagine the use of technology re-imagine automation, reimagining, how digitization helps them go to market different ways. So the CTO is a unique, a unique position from idea to impact. And in the past, we've kind of lost the CTO a little bit, but they're now reemerging as being the thought leader. That's only in driving digitization, going forward in our big clients. >>I, I would agree. I mean, it really has a deep understanding of that vision and can apply that vision to business success. So you obviously have a technical observation space and you also have some data, so maybe you could share with our audience how you inform yourself and your colleagues and IBM on, on what CTOs are thinking about and what they're worried about. >>Yeah. And so, so what we've done over the last four years now is gone out and interviewed CTOs. And can we do a very unstructured interviews? It's not, it's not a survey in the form of, uh, filling these, uh, these 10 questions and tell us yes or no. It reads a structured interview. We ask things like what's top of mind for you. What are the decisions you're making? Um, what's holding you back? What decisions do you think you shouldn't have made, or you wouldn't have liked to make? And, and it's that range of, um, of real input from the interview. So last year we interviewed a hundred CTOs. Um, this year we're actually doing a lot more, we're working with the IBM Institute of business value and we're gonna interview a lot more teachers, but for the material we're going to talk about today is really from those hundred CTO interviews. >>Yeah. And I think that, I mean, having done a lot of these myself, when you do those, we call them, you know, in depth interviews or ideas, you kind of have a structure and you do sort of follow that, but you learn so much and that maybe does inform those more structured interviews, uh, that, that, that you do down the road, you learn so much, but, but maybe you could summarize some of the concerns in the region what's on the minds of, of CTOs. Yeah. Yeah. The, >>The, the real decisions are being based around seven points, right? So the first one is we all know we're on a journey to the cloud. Um, but it's a hybrid multicloud. How do I think about the range of capabilities? I need to be able to unlock the latent potential of existing investments and the cloud-based capabilities we've got. So, so the, the hybrid cloud platform is, is, is one of the first and foundational pieces. The second challenge is that CTOs want to modernize their applications. And that modernization is a journey of, of moving towards microservices. That microservices journey has two parts. One is the business facing view, and that's what containers is all about choosing the right container platform. At the same time, they also want to use containers as a way of automation and management and reducing the effort and the infrastructure. So, so that's kind of two parts of that, that whole container journey. >>So Microsoft, this has really become the, the, the, the business developer view and containers become the operational view. At the same time, they wanna infuse new data to want to climb the AI ladder. They want to get the new, new insights from that data that plugs into those new workflows to get to those workflows. There's a decision around how do I isolate myself from some of the services of using that? And we've created a layer in the decisions around what called cloud services integration. So part service integration is, is kind of the, the modern day ESB as we might think about it. Um, but it's a way in which you choose which technology, which API I'm going to use from where, and then ultimately the CTOs are trying to build what are the new, um, uh, the new workflows, intelligent workflows. And they're really worried about how do I get the right level of automation that managing that issue between what becomes creepy and valuable, right. >>You know, there's some workflows that happen. You think, why the hell did that happen? Or I don't, that doesn't make sense. And, and, and it really sort of nerves the consumer, the user, whereas some which are wow, that's really cool. I really enjoyed that to try to get the intelligent workflows, right. Is a big concern. And then, um, on the two big, uh, parallel to that is how do we manage the systems operational automation, right from having the right data, the observability of all the infrastructure, recognizing they've got a spectrum of things from 30, 40, 50 year old systems to modern day cloud native systems, how to manage it, how to operationally automate that, keep that efficient, effective. And then of course, protecting from the perpetrator's rent business. A lot of people out there wanting to dig into the systems and, and, and, and draw all kinds of, um, you know, uh, data from their systems. So security, privacy, and making sure that align with the ethics and privacy of the business. So those are, those are the kind of range of issues, right? From the journey to cloud, through, to operational automation, through, through intelligent workflows, right. Into managing, protecting the services. >>That's interesting. Thank you for that. I mean, I remember, and you will, as well, some of the post wide thrust and sort of part of the modernization back then was during that they had budget to do that, but a lot of times organizations would make the mistake that they would, they're going to migrate off of a system that was working just fine. That was their sort of mental model of, of, of modernization. And it turned out to be disastrous in many cases. And so what, when I talk to CEOs, they talk about maybe, you know, I'd look at it as this, this abstraction layer. We want to protect what we have that works. Yes. Some stuff's going to go into the public cloud, but this hybrid connection that you talk about, and then we want control. And the way we're going to get control is we're going to use microservices to modernize and use modern API APIs. And so very, very sort of different thinking. And of course they want to avoid migration at all costs because it's so expensive and risky. I wonder if you could talk about, are there any patterns in terms of where people get started and the kinds of outcomes that they're working towards that they can measure? >>Yeah. And we kind of lump the, the learning from the work into three broad patterns, right. Um, one pattern is, is primarily around survival. They recognize that this journey, um, is, is very complex, that the pandemic has created tremendous challenges. Um, the market dynamics means that I've got to try and really be thoughtful in, in taking cost out and making sure they survive some of these issues and sort of the pattern is really around cost reduction. It may start with the hybrid cloud. It may start with in terms of workloads, but it's really about taking cost out of the systems. The second pattern is what we refer to as a simplification pattern. And this is about saying that we've got, we've got so much complexity because of technical debt, because of, you know, systems that we've half migrated in half done things with. Um, so how do I, how do I simplify my it landscape from applications through infrastructure to the data and make it more consistent and manageable and effective. >>And then the third one is that there are CTO saying, look, we've got a really pick that the time when we super scale something, we've got some things which we are unique and effective on. And I want to take that and really super scale that very quickly and make that consistent and really maximize the value of it. So that sort of pattern is really falling to those three categories of driving, driving cost reduction and survival simplification and modernization transformation. And then those that have got something which is unique and special and really super scaling up. >>Yeah. Right, right. Doubling down on those things that gave you unique, competitive advantage. Now, in this, in, in the studies that you've done over the years, you use this term ADP architectural decision points, and some of them are quite compelling. Maybe you could talk about some of those where there's some anxieties from the CTOs that, that you uncovered. >>Yeah. Yeah. The, the ADP's that we'll talk about the seven ATPs and it starts from the high rebuilt crowd through to, to intelligent workflows and so on. Um, and the ADP's themselves are really distilling the client's words in the client's, um, way of thinking about how they're going to drive those, those technologies. Um, and also how they're going to use those techniques to make a difference. But I think went through those interviews, um, what became the power is CTOs do have some anxieties as you refer to it. Um, and, and those anxiety, they couldn't necessarily put words on them and there were anxieties and like, are we thinking enough about the carbon footprint? Are we, are we being thoughtful in how we make sure we're reducing carbon footprint or reducing the environmental impact of the infrastructure you've got, we've got sprawling infrastructure, um, ripping out rare metals from the earth. >>Are we being thoughtful in how we reduce the, um, the amount of rare metals we have water consumption, uh, right through to is the code that we're producing efficient, secure and fit for, for the future? Um, are we being ethical in capturing the data for its right use, um, is the AI systems that we're building? Are they explainable? Are they ethical? Are they free from bias or are we kind of amplifying things that we shouldn't be able to find? So there was a whole bunch of those call anxieties and what we did along with the architectural decision report, um, a point after she decision report was, was identify what we call a set of responsibilities. And, and we've built a framework about around responsible computing, which is, uh, which is a basis for how you think through what your responsibilities are as a, as a CTO or as an it leader. Um, and we're right in the process of building out that, that kind of, um, responsible computing framework. >>Yeah, it's interesting. A lot of people may, may think about it. They think about the responsible computing and the sustainability, and they might think that's a, a one 80 from Milton Friedman economics, which said the job of business is to make profits. But in fact, responsible computing, there's a strong business case, uh, around it. It actually can help you reduce costs that can, can help you attract better employees because young people are passionate about this. I wonder if you could talk about how, how people can get involved with responsible computing in, in lean in. >>Yeah. So what we're about to publish is that he's actually a manifesto for responsible computing. So I think everybody, once we get that published, I'm hoping to do that in the next two to three months, we're working with a few clients, um, to there's actually three clients that have chosen, just click through your client's CTOs from the ones that we interviewed were very keen to collaborate with us in, in laying out that, um, that manifesto and the opportunity really is for anybody listening. If you, if you find this as a great value, please do come and reach out to me more than happy to collaborate with looking for more insights on this. Um, we've also had some, um, competitions. So in, in, in Mia, we've had a competition with, uh, with business partners looking for of how we can, um, really showcase examples or exemplars of being responsible computing provider, whether it's at the level of responsible data center, whether it's about responsible code data, use responsible systems, right through to responsible impact. And, you know, obviously a lot of our work around things like, um, your tech for good is, is tied directly to responsible impact. And of course, if you want to see what we IBM have been doing our responsible responsibility report, which we've been voluntarily publishing for the last 30 years, provides a tremendous set of insights on how we've done that over the years. And, and that's a, that's a great way for you to see how we've been doing things and see if that there are critical in your business. >>Yeah, so there's, so there's the, the re the ADP report is available. You can check it out on, on LinkedIn, um, go to go to Russia, LinkedIn profile, you'll find it. There's a blog post that talks about the next wave of digitization. Um, the learnings that you just talked about. So there's a lot of resources for, for people to get involved. I'll give you the last word rushy. >>Yeah. And th th this is, this is what I call job began. It's not job done. The whole ADP responsible computing is a digitization journey where we want to balance delivering business value and making a difference to the organization. But at the same time, being responsible, making sure that we're thoughtful of what's needed for the future. And we create impact that really matters. And, or we can feel proud that we've put a foundation for digitization, which will, which will serve the businesses for many years to come >>Love it, impact investing in your business and in the future. Russia, thanks so much for coming to the cube. Really appreciate it. Thank you. Okay. Keep it right there for more coverage from IBM. Think 2021. This is Dave Volante for the cube.

>>Yeah, yeah. >>Hello and welcome back. I hope you're ready for our next session. Become the analyst of the future. We'll hear the customer's perspective about their increasingly strategic role and the potential career growth that comes with it. Joining us today are Nate Weaver, director of product marketing at Thought Spot. Yasmin Natasa, senior director of national sales strategy and insights over at Comcast and Steve Would Ledge VP of customer and partner initiatives. Oughta Terex. We're so happy to have you all here today. I'll hand things over to meet to kick things off. >>Yeah, thanks, Paula. I'd like to start with a personal story that might resonate with our audience, says an analyst. Early in my career, I was the intermediary between the business and what we called I t right. Basically database administrators. I was responsible for understanding business logic gathering requirements, Ringling data building dashboards for executives and, in my case, 100 plus sales reps. Every request that came through the business intelligence team. We owned everything, right? Indexing databases for speed, S s. I s packages for data transfer maintaining Department of Data Lakes all out cubes, etcetera. We were busy. Now we were constantly building or updating something. The worst part is an analyst, If you ask the business, every request took too long. It was slow. Well, from an analyst perspective, it was slow because it's a complex process with many moving parts. So as an analyst fresh out of grad school often felt overeducated, sometimes underappreciated, like a report writer, we were constantly overwhelmed by never ending ad hoc request, even though we had hundreds of reports and robust dashboards that would answer 90% of the questions. If the end user had an analytical foundation like I did right, if they knew where to look and how to navigate dimensions and hierarchies, etcetera. So anyway, point is, we had to build everything through this complex and slow, um, process. So for the first decade of my career, I had this gut feeling there had to be a better way, and today we're going to talk about how thought SWAT and all tricks are empowering the analysts of the future by reimagining the entire data pipeline. This paradigm shift allows businesses and data teams thio, connect, transform, model and, most importantly, automate what used to be this terribly complex data analysis process. With that, I'd like to hand it over to Steve to describe the all tricks analytic process automation platform and how they help analysts create more robust data sets that enable non technical end users toe ask and answer their own questions, but also more sophisticated business questions. Using Search and AI Analytics in Thoughts Fire Steve over to you. >>Thanks for that really relevant example. Nate and Hi, everyone. I'm Steve. Will it have been in the market for about 20 years, and then Data Analytics and I can completely I can completely appreciate what they was talking about. And what I think is unique about all tricks is how we not only bring people to the data for a self service environment, but I think what's often missed in analytics is the automation and figure out. What is the business process that needs to be repeated and connecting the dots between the date of the process and the people To speed up those insights, uh, to not only give people to self service, access to information, to do data prep and blending, but more advanced analytics, and then driving that into the business in terms of outcomes. And I'll show you what that looks like when you talk about the analytic process automation platform on the next slide. What we've done is we've created this end to end workflow where data is on the left, outcomes around the right and within the ultras environment, we unify data prep and blend analytics, data science and process automation. In this continuous process, so is analysis or an end user. I can go ahead and grab whatever data is made available to me by i t. You have got 80 plus different inputs and a p i s that we connect to. You have this drag and drop environment where you conjoined the data together, apply filters, do some descriptive analytics, even do things like grab text documents and do sentiments analysis through that with text, mining and natural language processing. As people get more used to the platform and want to do more advanced analytics and process automation, we also have things like assisted machine learning and predictive analytics out of the box directly within it as well and typically within organizations. These would be different departments and different tools doing this and we try to bring all this together in one system. So there's 260 different automation building blocks again and drag a drop environment. And then those outcomes could be published into a place where thoughts about visualizes that makes it accessible to the business users to do additional search based B I and analytics directly from their browser. And it's not just the insights that you would get from thought spot, but a lot of automation is also driving unattended, unattended or automated actions within operational systems. If you take an example of one of our customers that's in the telecommunications world, they drive customer insights around likeliness to turn or next best offers, and they deliver that within a salesforce applications. So when you walk into a retail store for your cell phone provider, they will know more about you in terms of what services you might be interested in. And if you're not happy at the time and things like that. So it's about how do we connect all those components within the business process? And what this looks like is on this screen and I won't go through in detail, but it's ah, dragon drop environment, where everything from the input data, whether it's cloud on Prem or even a local file that you might have for a spreadsheet. Uh, I t wants to have this environment where it's governed, and there's sort of components that you're allowed to have access to so that you could do that data crept and blending and not just data within your organization, but also then being able to blend in third party demographic data or firm a graphic information from different third party data providers that we have joined that data together and then do more advanced analytics on it. So you could have a predictive score or something like that being applied and blending that with other information about your customer and then sharing those insights through thought spots and more and more users throughout the organization. And bring that to life. In addition to you, as we know, is gonna talk about her experience of Comcast. Given the world that we're in right now, uh, hospital care and the ability to have enough staff and and take care of all of our people is a really important thing. So one of our customers, a large healthcare network in the South was using all tricks to give not only analyst with the organization, but even nurses were being trained on how to use all tricks and do things like improve observation. Wait time eso that when you come in, the nurse was actually using all tricks to look at the different time stamps out of ethic and create a process for the understands. What are all the causes for weight in three observation room and identify outliers of people that are trying to come in for a certain type of care that may wait much longer than on average. And they're actually able to reduce their wait time by 22%. And the outliers were reduced by about 50% because they did a better job of staffing. And overall staffing is a big issue if you can imagine trying to have a predictive idea of how many staff you need in the different medical facilities around the network, they were bringing in data around the attrition of healthcare workers, the volume of patient load, the scheduled holidays that people have and being able to predict 4 to 6 months out. What are the staff that they need to prepare toe have on on site and ready so they could take care of the patients as they're coming in. In this case, they used in our module within all tricks to do that, planning to give HR and finance a view of what's required, and they could do a drop, a drop down by department and understand between physicians, nurses and different facilities. What is the predicted need in terms of staffing within that organization? So you go to the next slide done, you know, aside from technology, the number one thing for the analysts of the future is being able to focus on higher value business initiatives. So it's not just giving those analysts the ability to do this self service dragon drop data prep and blend and analytics, but also what are the the common problems that we've solved as a community? We have 150,000 people in the alter its community. We've been in business for over 23 years, so you could go toe this gallery and not only get things like the thought spot tools that we have to connect so you can do direct query through T Q l and pushed it into thought spot in Falcon memory and other things. But look at things like the example here is the healthcare District, where we have some of our third party partners that have built out templates and solutions around predictive staffing and tracking the complicating conditions around Cove. It as an example on different KPs that you might have in healthcare, environment and retail, you know, over 150 different solution templates, tens of thousands of different posts across different industries, custom return and other problems that we can solve, and bringing that to the community that help up level, that collective knowledge, that we have this business analyst to solve business problems and not just move data, and then finally, you know, as part of that community, part of my role in all tricks is not only working with partners like thought spot, but I also share our C suite advisory board, which we just happen to have this morning, as a matter of fact, and the number one thing we heard and discussed at that customer advisory board is a round up Skilling, particularly in this virtual world where you can't do in classroom learning how do we game if I and give additional skills to our staff so that they can digitize and automate more and more analytic processes in their organization? I won't go through all this, but we do have learning paths for both beginners. A swell as advanced people that want to get more into the data science world. And we've also given back to our community. There's an initiative called Adapt where we've essentially donated 125 hours of free training free access to our products. Within the first two weeks, we've had over 9000 people participate in that get certified across 100 different companies and then get jobs in this new world where they've got additional skills now around analytics. So I encourage you to check that out, learn what all tricks could do for you in up Skilling your journey becoming that analysts of the future And thanks for having me today thoughts fun looking forward to the rest of conversation with the Azmin. >>Yeah, thanks. I'm gonna jump in real quick here because you just mentioned something that again as an analyst, is incredibly important. That's, you know, empowering Mia's an analyst to answer those more sophisticated business questions. There's a few things that you touched on that would be my personal top three. Right? Is an analyst. You talked about data cleansing because everyone has data quality problems enhancing the data sets. I came from a supply chain analytics background. So things like using Dun and Bradstreet in your examples at risk profiles to my supplier data and, of course, predictive analytics, like creating a forecast to estimate future demand. These are things that I think is an analyst. I could truly provide additional value. I'd like to show you a quick example, if I may, of the type of ad hoc request that I would often get from the business. And it's fairly complex, but with a combination of all tricks and thought spots very easy to answer. Crest. The request would look something like this. I'd like to see my spend this year versus last year to date. Uh, maybe look at that monthly for Onley, my area of responsibility. But I only want to focus on my top five suppliers from this year, right? And that's like an end statement. I saw that in one of your slides and so in thoughts about that's answering or asking a simple question, you're getting the answer in maybe 30 seconds. And that's because behind the scenes, the last part is answering those complexities for you. And if I were to have to write this out in sequel is an analyst, it could take me upwards, maybe oven our because I've got to get into the right environment in the database and think about the filters and the time stamps, and there's a lot going on. So again, thoughts about removes that curiosity tax, which when becoming the analysts of the future again, if I don't have to focus on the small details that allows me to focus on higher value business initiatives, right. And I want to empower the business users to ask and answer their own questions. That does come with up Skilling, the business users as well, by improving data fluency through education and to expand on this idea. I wanna invite Yasmin from Comcast to kind of tell her personal story. A zit relates to analysts of the future inside Comcast. >>Well, thank you for having me. It's such a pleasure. And Steve, thank you so much for starting and setting the groundwork for this amazing conversation. You hit the nail on the head. I mean, data is a Trojan horse off analytics, and our ability to generate that inside is eyes busy is anchored on how well we can understand the data on get the data clean It and tools, like all tricks, are definitely at the forefront off ability to accelerate the I'll speak to incite, which is what hot spot brings to the table. Eso My story with Thought spot started about a year and a half ago as I'm part of the Sales Analytics team that Comcast all group is officially named, uh, compensation strategy and insight. We are part of the Consumer Service, uh, Consumer Service expected Consumer Service group in the cell of Residential Sales Organization, and we were created to provide insight to the Comcast sells channel leaders Thio make sure that they have database insight to drive sales performance, increased revenue. We When we started the function, we were really doing a lot of data wrangling, right? It wasn't just a self performance. It waas understanding who are customers were pulling a data on productivity. Uh, so we were going into HR systems are really going doing the E T l process, but manually sometimes. And we took a pause at one point because we realized that we're spending a good 70% of our time just doing that and maybe 5% of our time storytelling. Now our strength was the storytelling. And so you see how that balance wasn't really there. And eso Jim, my leader pause. It pulls the challenge of Is there a better way of doing this on DSO? We scan the industry, and that's how we came across that spot. And the first time I saw the tool, I fell in love. There's not a way for me to describe it. I fell in love because I love the I love the the innovation that it brought in terms of removing the middleman off, having to create all these layers between the data and me. I want to touch the data. I want to feel it, and I want to ask questions directly to it, and that's what that's what does for us. So when we launched when we launch thoughts about for our team, we immediately saw the difference in our ability to provide our stakeholders with better answers faster. And the combination of the two makes us actually quite dangerous right on. But it has been It has been a great great journey altogether are inter plantation was done on the cloud because at the time, uh, the the we had access to AWS account and I love to be at the edge of technology, So I figured it would be a good excuse for me to learn more about cloud technology on its been things. Video has been a great journey. Um, my, my background, uh, into analytics comes from science. And so, for me, uh, you know, we are really just stretching the surface off. What is possible in terms off the how well remind data to answer business questions on Do you know, tools like thought spot in combination with technologies. Like all trades, eyes really are really the way to go about it. And the up skilling, um the up skilling off the analysts that comes with it is really, really, really exciting because people who love data want to be able to, um want to be efficient about how they spend time with data. Andi and that's what? That's what I spend a lot of my Korea I'd Comcast and before Comcast doing so It gives me a lot of ah, a lot of pleasure to, um to bring that to my organization and to walk with colleagues outside off. We didn't Comcast to do so The way we the way we use stops, that's what we did not seem is varies. One of the things that I'm really excited about is integrating it with all the tools that we have in our analytics portfolio, and and I think about it as the over the top strategy. Right. Uh, group, like many other groups, wouldn't Comcast and with our organizations also used to be I tools. And it is not, um, you choose on a mutually exclusive strategies, right? Eso In our world, we build decision making, uh, decision making tools from the analysis that we generate. When we have the read out with the cells channel leaders, we we talk about the insight, and invariably there's some components off those insight that they want to see on a regular basis. That becomes a reporting activity. We're not in a reporting team. We partner with reporting team for them to think that input and and and put it on and create a regular cadence for it. Uh, the over the top strategy for me is, um, are working with the reporting team to then embed the link to talk spot within the report so that the questions that can be answered by the reports left dashboard are answered within the dashboard. But we make sure that we replicate the data source that feeds that report into thought spot so that the additional questions can then be insert in that spot. It and it works really well because it creates a great collaboration with our partners on the on the reporting side of the house on it also helps of our end the end users do the cell service in along the analytic spectrum, right? You go to the report when you can, when all you need is dropped down the filters and when the questions become more sophisticated, you still have a platform in the place to go to ask the questions directly and do things that are a bit funk here, like, you know, use for like you because you don't know what you're looking for. But you know that there's there's something there to find. >>Yeah, so yeah, I mean, a quick question. Our think would be on this year's analytics meet Cloud open for everyone and your experience. What does that mean to you? Including in the context of the thought spot community inside Comcast? >>Oh yes, it's the Comcast community. The passport commedia Comcast is very vibrant. My peers are actually our colleagues, who I have in my analytics village prior to us getting on board with hot spot and has been a great experience for us. So have thoughts, but as an additional kind of topic Thio to connect on. So my team was the second at Comcast to implement that spot. The first waas, the product team led by Skylar, and he did his instance on Prem. Um, he the way that he brings his data is, is through a sequel server. When I came what, as I mentioned earlier, I went on the cloud because, as I mentioned earlier, I like to be on the edge of technology and at the time thought spot was moving towards towards the cloud. So I wanted to be part of that wave. There's Ah, mobile team has a new instance that is on the cloud thing. The of the compliance team uses all tricks, right? And the S O that that community to me is really how the intellectual capital that we're building, uh, using thought spot is really, really growing on by what happens to me. And the power of being on the cloud is that if we are all using the same tool, right and we are all kind of bringing our data together, um, we are collaborating in ways that make the answer to the business questions that the C suite is asking much better, much richer. They don't always come to us at the same time, right? Each function has his own analytics group, Andi. Sometimes if we are not careful, we're working silo. But the community allows us to know about what each other are working on. And the fact that we're using the same tool creates a common language that translates into opportunities for collaboration, which will translate into, as I mentioned earlier, richer better on what comprehensive answers to the business. So analyst Nick the cloud means better, better business and better business answers and and better experiences for customers at the end of the day, so I'm all for it. >>That's great. Yeah. Comcast is obviously a very large enterprise. Lots of data sources, lots of data movement. It's cool to hear that you have a bit of a hybrid architecture, er thought spot both on premise. Stand in the cloud and you did bring up one other thing that I think is an important question for Steve. Most people may just think of all tricks as an E T l tool, but I know customers like Comcast use it for way more than just that. Can you expand upon the differences between what people think of a detail tool and what all tricks is today? >>Yeah, I think of E. T L tools as sort of production class source to target mapping with transformations and data pipelines that air typically built by I t. To service, you know, major areas within the business, and that's super valuable. One doesn't go away, and in all tricks can provide some of that. But really, it's about the end user empowerment. So going back to some of guys means examples where you know there may be some new information that you receive from a third party or even a spreadsheet that you develop something on. You wanna start to play around that information so you can think of all the tricks as a data lab or data science workbench, in fact, that you know, we're in the Gartner Magic Quadrant for data science and machine learning platforms. Because a lot of that innovation is gonna happen at the individual level we're trying to solve. And over time, you might want to take that learning and then have I t production eyes it within another system. But you know, there's this trade off between the agility that end users need and sort of the governance that I t needs to bring. So we work best in a environment where you have that in user autonomy. You could do E tail workloads, data prep and Glenn bringing your own information on then work with i t. To get that into the right server based environment to scale out in the thought spot and other applications that you develop new insights for the business. So I see it is ah, two sides of the same coin. In many ways, a home. And >>with that we're gonna hand it back over to a Paula. >>Thank you, Nate, Yasmin and Steve for the insights into the journey of the analyst of the future. Next up in a couple minutes, is our third session of today with Ruhollah Benjamin, professor of African American Studies at Princeton University, and our chief data strategy officer, Cindy House, in do a couple of jumping jacks or grab a glass of water and don't miss out on the next important discussion about diversity and data.

>>Yeah, yeah. Welcome back to the third session in our building, A vibrant data ecosystem track. This session is unleash the power of your cloud data warehouse. So what comes after you've moved your data to the cloud in this session will explore White Enterprise Analytics is finally ready for the cloud, and we'll discuss how you can consume Enterprise Analytics in the very same way he would cloud services. We'll also explore where analytics meets cloud and see firsthand how thought spot is open for everyone. Let's get going. I'm happy to say we'll be hearing from two folks from thought spot today, Michael said Cassie, VP of strategic partnerships, and Vika Valentina, senior product marketing manager. And I'm very excited to welcome from our partner at AWS Gal Bar MIA, product engineering manager with Red Shift. We'll also be sharing a live demo of thought spot for BTC Marketing Analytics directly on Red Shift data. Gal, please kick us off. >>Thank you, Military. And thanks. The talks about team and everyone attending today for joining us. When we talk about data driven organizations, we hear that 85% of businesses want to be data driven. However, on Lee. 37% have been successful in We ask ourselves, Why is that and believe it or not, Ah, lot of customers tell us that they struggled with live in defining what being data driven it even means, and in particular aligning that definition between the business and the technology stakeholders. Let's talk a little bit. Let's look at our own definition. A data driven organization is an organization that harnesses data is an asset. The drive sustained innovation and create actionable insights. The super charge, the experience of their customers so they demand more. Let's focus on a few things here. One is data is an asset. Data is very much like a product needs to evolve sustained innovation. It's not just innovation innovation, it's sustained. We need to continuously innovate when it comes to data actionable insights. It's not just interesting insights these air actionable that the business can take and act upon, and obviously the actual experience we. Whether whether the customers are internal or external, we want them to request Mawr insights and as such, drive mawr innovation, and we call this the for the flywheel. We use the flywheel metaphor here where we created that data set. Okay, Our first product. Any focused on a specific use case? We build an initial NDP around that we provided with that with our customers, internal or external. They provide feedback, the request, more features. They want mawr insights that enables us to learn bringing more data and reach that actual data. And again we create MAWR insights. And as the flywheel spins faster, we improve on operational efficiencies, supporting greater data richness, and we reduce the cost of experimentation and legacy environments were never built for this kind of agility. In many cases, customers have struggled to keep momentum in their fleet, flywheel in particular around operational efficiency and experimentation. This is where Richie fits in and helps customer make the transition to a true data driven organization. Red Shift is the most widely used data warehouse with tens of thousands of customers. It allows you to analyze all your data. It is the only cloud data warehouse that sits, allows you to analyze data that sits in your data lake on Amazon, a street with no loading duplication or CTL required. It is also allows you to scale with the business with its hybrid architectures it also accelerates performance. It's a shared storage that provides the ability to scale toe unlimited concurrency. While the UN instant storage provides low late and say access to data it also provides three. Key asks that customers consistently tell us that matter the most when it comes to cost. One is usage based pricing Instead of license based pricing. Great value as you scale your data warehouse using, for example, reserved instances they can save up to 75% compared to on the mind demand prices. And as your data grows, infrequently accessed data can be stored. Cost effectively in S three encouraged through Amazon spectrum, and the third aspect is predictable. Month to month spend with no hitting charges and surprises. Unlike and unlike other cloud data warehouses, where you need premium versions for additional enterprise capabilities. Wretched spicing include building security compression and data transfer. >>Great Thanks. Scout um, eso. As you can see, everybody wins with the cloud data warehouses. Um, there's this evolution of movement of users and data and organizations to get value with these cloud data warehouses. And the key is the data has to be accessible by the users, and this data and the ability to make business decisions on the data. It ranges from users on the front line all the way up to the boardroom. So while we've seen this evolution to the Cloud Data Warehouse, as you can see from the statistic from Forrester, we're still struggling with how much of that data actually gets used for analytics. And so what is holding us back? One of the main reasons is old technology really trying to work with today's modern cloud data warehouses? They weren't built for it. So you run into issues of trying to do data replication, getting the data out of the cloud data warehouse. You can do analysis and then maintaining these middle layers of data so that you can access it quickly and get the answers you need. Another issue that's holding us back is this idea that you have to have your data in perfect shape with the perfect pipeline based on the exact dashboard unique. Um, this isn't true. Now, with Cloud data warehouse and the speed of important business data getting into those cloud data warehouses, you need a solution that allows you to access it right away without having everything to be perfect from the start, and I think this is a great opportunity for GAL and I have a little further discussion on what we're seeing in the marketplace. Um, one of the primary ones is like, What are the limiting factors, your Siegel of legacy technologies in the market when it comes to this cloud transformation we're talking about >>here? It's a great question, Michael and the variety of aspect when it comes to legacy, the other warehouses that are slowing down innovation for companies and businesses. I'll focus on 21 is performance right? We want faster insights. Companies want the ability to analyze MAWR data faster. And when it comes to on prem or legacy data warehouses, that's hard to achieve because the second aspect comes into display, which is the lack of flexibility, right. If you want to increase your capacity of your warehouse, you need to ensure request someone needs to go and bring an actual machine and install it and expand your data warehouse. When it comes to the cloud, it's literally a click of a button, which allows you to increase the capacity of your data warehouse and enable your internal and external users to perform analytics at scale and much faster. >>It falls right into the explanation you provided there, right as the speed of the data warehouses and the data gets faster and faster as it scales, older solutions aren't built toe leverage that, um, you know, they're either they're having to make technical, you know, technical cuts there, either looking at smaller amounts of data so that they can get to the data quicker. Um, or it's taking longer to get to the data when the data warehouse is ready, when it could just be live career to get the answers you need. And that's definitely an issue that we're seeing in the marketplace. I think the other one that you're looking at is things like governance, lineage, regulatory requirements. How is the cloud you know, making it easier? >>That's That's again an area where I think the cloud shines. Because AWS AWS scale allows significantly more investment in securing security policies and compliance, it allows customers. So, for example, Amazon redshift comes by default with suck 1 to 3 p. C. I. Aiso fared rampant HIPPA compliance, all of them out of the box and at our scale. We have the capacity to implement those by default for all of our customers and allow them to focus. Their very expensive, valuable ICTY resource is on actual applications that differentiate their business and transform the customer experience. >>That's a great point, gal. So we've talked about the, you know, limiting factors. Technology wise, we've mentioned things like governance. But what about the cultural aspect? Right? So what do you see? What do you see in team struggling in meeting? You know, their cloud data warehouse strategy today. >>And and that's true. One of the biggest challenges for large large organizations when they moved to the cloud is not about the technology. It's about people, process and culture, and we see differences between organizations that talk about moving to the cloud and ones that actually do it. And first of all, you wanna have senior leadership, drive and be aligned and committed to making the move to the cloud. But it's not just that you want. We see organizations sometimes Carol get paralyzed. If they can't figure out how to move each and every last work clothes, there's no need to boil the ocean, so we often work with organizations to find that iterative motion that relative process off identifying the use cases are date identifying workloads in migrating them one at a time and and through that allowed organization to grow its knowledge from a cloud perspective as well as adopt its tooling and learn about the new capabilities. >>And from an analytics perspective, we see the same right. You don't need a pixel perfect dashboard every single time to get value from your data. You don't need to wait until the data warehouse is perfect or the pipeline to the data warehouse is perfect. With today's technology, you should be able to look at the data in your cloud data warehouse immediately and get value from it. And that's the you know, that's that change that we're pushing and starting to see today. Thanks. God, that was That was really interesting. Um, you know, as we look through that, you know, this transformation we're seeing in analytics, um, isn't really that old? 20 years ago, data warehouses were primarily on Prem and the applications the B I tools used for analytics around them were on premise well, and so you saw things like applications like Salesforce. That live in the cloud. You start having to pull data from the cloud on Prem in order to do analytics with it. Um, you know, then we saw the shift about 10 years ago in the explosion of Cloud Data Warehouse Because of their scale, cost reduced, reduce shin reduction and speed. You know, we're seeing cloud data. Warehouses like Amazon Red Shift really take place, take hold of the marketplace and are the predominant ways of storing data moving forward. What we haven't seen is the B I tools catch up. And so when you have this new cloud data warehouse technology, you really need tools that were custom built for it to take advantage of it, to be able to query the cloud data warehouse directly and get results very quickly without having to worry about creating, you know, a middle layer of data or pipelines in order to manage it. And, you know, one company captures that really Well, um, chick fil A. I'm sure everybody has heard of is one of the largest food chains in America. And, you know, they made a huge investment in red shift and one of the purposes of that investment is they wanted to get access to the data mawr quickly, and they really wanted to give their business users, um, the ability to do some ad hoc analysis on the data that they were capturing. They found that with their older tools, the problems that they were finding was that all the data when they're trying to do this analysis was staying at the analyst level. So somebody needed to create a dashboard in order to share that data with a user. And if the user's requirements changed, the analysts were starting to become burdened with requests for changes and the time it took to reflect those changes. So they wanted to move to fought spot with embrace to connect to Red Shift so they could start giving business users that capability. Query the database right away. And with this, um, they were able to find, you know, very common things in in the supply chain analysis around the ability to figure out what store should get, what product that was selling better. The other part was they didn't have to wait for the data to get settled into some sort of repository or second level database. They were able to query it quickly. And then with that, they're able to make changes right in the red shift database that were then reflected to customers and the business users right away. So what they found from this is by adopting thought spot, they were actually able to arm business users with the ability to make decisions very quickly. And they cleared up the backlog that they were having and the delay with their analysts. And they're also putting their analysts toe work on different projects where they could get better value from. So when you look at the way we work with a cloud data warehouse, um, you have to think of thoughts about embrace as the tool that access that layer. The perfect analytic partner for the Cloud Data Warehouse. We will do the live query for the business user. You don't need to know how to script and sequel, um Thio access, you know, red shift. You can type the question that you want the answer to and thought spot will take care of that query. We will do the indexing so that the results come back faster for you and we will also do the analysis on. This is one of the things I wanted to cover, which is our spot i. Q. This is new for our ability to use this with embrace and our partners at Red Shift is now. We can give you the ability to do auto analysis to look at things like leading indicators, trends and anomalies. So to put this in perspective amount imagine somebody was doing forecasting for you know Q three in the western region. And they looked at how their stores were doing. And they saw that, you know, one store was performing well, Spot like, you might be able to look at that analysis and see if there's a leading product that is underperforming based on perhaps the last few quarters of data. And bring that up to the business user for analysis right away. They don't need to have to figure that out. And, um, you know, slice and dice to find that issue on their own. And then finally, all the work you do in data management and governance in your cloud data warehouse gets reflected in the results in embrace right away. So I've done a lot of talking about embrace, and I could do more, but I think it would be far better toe. Have Vika actually show you how the product works, Vika. >>Thanks, Michael. We learned a lot today about the power of leveraging your red shift data and thought spot. But now let me show you how it works. The coronavirus pandemic has presented extraordinary challenges for many businesses, and some industries have fared better than others. One industry that seems to weather the storm pretty well actually is streaming media. So companies like Netflix and who Lou. And in this demo, we're going to be looking at data from B to C marketing efforts. First streaming media company in 2020 lately, we've been running campaigns for comedy, drama, kids and family and reality content. Each of our campaigns last four weeks, and they're staggered on a weekly basis. Therefore, we always have four campaigns running, and we can focus on one campaign launch per >>week, >>and today we'll be digging into how our campaigns are performing. We'll be looking at things like impressions, conversions and users demographic data. So let's go ahead and look at that data. We'll see what we can learn from what's happened this year so far, and how we can apply those learnings to future decision making. As you can already see on the thoughts about homepage, I've created a few pin boards that I use for reporting purposes. The homepage also includes what others on my team and I have been looking at most recently. Now, before we dive into a search, will first take a look at how to make a direct connection to the customer database and red shift to save time. I've already pre built the connection Red Shift, but I'll show you how easy it is to make that connection in just three steps. So first we give the connection name and we select our connection type and was on red Shift. Then we enter our red shift credentials, and finally, we select the tables that we want to use Great now ready to start searching. So let's start in this data to get a better idea of how our marketing efforts have been affected either positively or negatively by this really challenging situation. When we think of ad based online marketing campaigns, we think of impressions, clicks and conversions. Let's >>look at those >>on a daily basis for our purposes. So all this data is available to us in Thought spot, and we can easily you search to create a nice line chart like this that shows US trends over the last few months and based on experience. We understand that we're going to have more clicks than impressions and more impressions and conversions. If we started the chart for a minute, we could see that while impressions appear to be pretty steady over the course of the year, clicks and especially conversions both get a nice boost in mid to late March, right around the time that pandemic related policies were being implemented. So right off the bat, we found something interesting, and we can come back to this now. There are few metrics that we're gonna focus on as we analyze our marketing data. Our overall goal is obviously to drive conversions, meaning that we bring new users into our streaming service. And in order to get a visitor to sign up in the first place, we need them to get into our sign up page. A compelling campaign is going to generate clicks, so if someone is interested in our ad, they're more likely to click on it, so we'll search for Click through Rape 5% and we'll look this up by campaign name. Now even compare all the campaigns that we've launched this year to see which have been most effective and bring visitors star site. And I mentioned earlier that we have four different types of campaign content, each one aligned with one of our most popular genres. So by adding campaign content, yeah, >>and I >>just want to see the top 10. I could limit my church. Just these top 10 campaigns automatically sorted by click through rate and assigned a color for each category so we could see right away that comedy and drama each of three of the top 10 campaigns by click through rate reality is, too, including the top spot and kids and family makes one appearance as well. Without spot. We know that any non technical user can ask a question and get an answer. They can explore the answer and ask another question. When you get an answer that you want to share, keep an eye on moving forward, you pin the answer to pin board. So the BBC Marketing Campaign Statistics PIN board gives us a solid overview of our campaign related activities and metrics throughout 2020. The visuals here keep us up to date on click through rate and cost per click, but also another really important metrics that conversions or cost proposition. Now it's important to our business that we evaluate the effectiveness of our spending. Let's do another search. We're going to look at how many new customers were getting so conversions and the price cost per acquisition that we're spending to get each of these by the campaign contact category. So >>this is a >>really telling chart. We can basically see how much each new users costing us, based on the content that they see prior to signing up to the service. Drama and reality users are actually relatively expensive compared to those who joined based on comedy and kids and family content that they saw. And if all the genres kids and family is actually giving us the best bang for our marketing >>buck. >>And that's good news because the genres providing the best value are also providing the most customers. We mentioned earlier that we actually saw a sizable uptick in conversions as stay at home policies were implemented across much of the country. So we're gonna remove cost per acquisition, and we're gonna take a daily look how our campaign content has trended over the years so far. Eso By doing this now, we can see a comparison of the different genres daily. Some campaigns have been more successful than others. Obviously, for example, kids and family contact has always fared pretty well Azaz comedy. But as we moved into the stay at home area of the line chart, we really saw these two genres begin to separate from the rest. And even here in June, as some states started to reopen, we're seeing that they're still trending up, and we're also seeing reality start to catch up around that time. And while the first pin board that we looked at included all sorts of campaign metrics, this is another PIN board that we've created so solely to focus on conversions. So not only can we see which campaigns drug significant conversions, we could also dig into the demographics of new users, like which campaigns and what content brought users from different parts of the country or from different age groups. And all this is just a quick search away without spot search directly on a red shift. Data Mhm. All right, Thank you. And back to you, Michael. >>Great. Thanks, Vika. That was excellent. Um, so as you can see, you can very quickly go from zero to search with thought Spot, um, connected to any cloud data warehouse. And I think it's important to understand that we mentioned it before. Not everything has to be perfect. In your doubt, in your cloud data warehouse, um, you can use thought spot as your initial for your initial tool. It's for investigatory purposes, A Z you can see here with star, Gento, imax and anthem. And a lot of these cases we were looking at billions of rows of data within minutes. And as you as your data warehouse maturity grows, you can start to add more and more thoughts about users to leverage the data and get better analysis from it. So we hope that you've enjoyed what you see today and take the step to either do one of two things. We have a free trial of thoughts about cloud. If you go to the website that you see below and register, we can get you access the thought spots so you can start searching today. Another option, by contacting our team, is to do a zero to search workshop where 90 minutes will work with you to connect your data source and start to build some insights and exactly what you're trying to find for your business. Um thanks, everybody. I would especially like to thank golf from AWS for joining us on this today. We appreciate your participation, and I hope everybody enjoyed what they saw. I think we have a few questions now. >>Thank you, Vika, Gal and Michael. It's always exciting to see a live demo. I know that I'm one of those comedy numbers. We have just a few minutes left, but I would love to ask a couple of last questions Before we go. Michael will give you the first question. Do I need to have all of my data cleaned and ready in my cloud data warehouse before I begin with thought spot? >>That's a great question, Mallory. No, you don't. You can really start using thought spot for search right away and start getting analysis and start understanding the data through the automatic search analysis and the way that we query the data and we've seen customers do that. Chick fil a example that we talked about earlier is where they were able to use thoughts bought to notice an anomaly in the Cloud Data Warehouse linking between product and store. They were able to fix that very quickly. Then that gets reflected across all of the users because our product queries the Cloud Data Warehouse directly so you can get started right away without it having to be perfect. And >>that's awesome. And gal will leave a fun one for you. What can we look forward to from Amazon Red Shift next year? >>That's a great question. And you know, the team has been innovating extremely fast. We released more than 200 features in the last year and a half, and we continue innovating. Um, one thing that stands out is aqua, which is a innovative new technology. Um, in fact, lovely stands for Advanced Square Accelerator, and it allows customers to achieve performance that up to 10 times faster, uh, than what they've seen really outstanding and and the way we've achieved that is through a shift in paradigm in the actual technological implementation section. Uh, aqua is a new distributed and hardware accelerated processing layer, which effectively allows us to push down operations analytics operations like compression, encryption, filtering and aggregations to the storage there layer and allow the aqua nodes that are built with custom. AWS designed analytics processors to perform these operations faster than traditional soup use. And we no longer need to bring, you know, scan the data and bring it all the way to the computational notes were able to apply these these predicates filtering and encourage encryption and compression and aggregations at the storage level. And likewise is going to be available for every are a three, um, customer out of the box with no changes to come. So I apologize for being getting out a little bit, but this is really exciting. >>No, that's why we invited you. Call. Thank you on. Thank you. Also to Michael and Vika. That was excellent. We really appreciate it. For all of you tuning in at home. The final session of this track is coming up shortly. You aren't gonna want to miss it. We're gonna end strong, come back and hear directly from our customer a T mobile on how T Mobile is building a data driven organization with thought spot in which >>pro, It's >>up next, see you then.

>> Announcer: From around the globe, it's theCUBE with digital coverage of DevOps virtual forum. Brought to you by Broadcom. >> Hi guys, welcome back. So we have discussed the current state and the near future state of DevOps and how it's going to evolve from three unique perspectives. In this last segment, we're going to open up the floor and see if we can come to a shared understanding of where DevOps needs to go. In order to be successful next year. So our guests today are you've seen them all before. Jeffrey Hammond is here the VP and Principal Analyst serving CIO at Forrester. We've also got Serge Lucio, the GM of Broadcom Enterprise Software Division. And Glyn Martin, the head of QA Transformation at BT. Guys welcome back. Great to have you all three together. >> Hi Lisa. (Serge speaks faintly) >> Good to be here. >> All right. So we're all very socially distanced as we talked about before. Great to have this conversation. So let's start with one of the topics that we kicked off the forum with. Jeff, we're going to start with you spiritual colocation. That's a really interesting topic that we've uncovered. But how much of the challenge is truly cultural? And what can we solve through technology? Jeff, we'll start with you, then Serge, then Glyn, Jeff take it away. >> Yeah I think fundamentally, you can have all the technology in the world. And if you don't make the right investments in the cultural practices in your development organization. You still won't be effective. Almost 10 years ago, I wrote a piece. Where I did a bunch of research around what made high performance teams software delivery teams high performance. And one of the things that came out as part of that was that these teams have a high level of autonomy. And that's one of the things that you see coming out of the Agile Manifesto. Let's take that today. Where developers are on their own in their own offices. if you've got teams where the team itself had a high level of autonomy. And they know how to work, they can make decisions. They can move forward. They're not waiting for management to tell them what to do. And so what we have seen is that organizations that embraced autonomy, and got their teams in the right place. And their teams had the information that they needed to make the right decisions. Have actually been able to operate pretty well, even as they've been remote. And it's turned out to be things like well, how do we actually push the software that we've created into production that have become the challenge is not. Are we writing the right software? And that's why I think the term spiritual colocation is so important. Because even though we may be physically distant, we're on the same plane, we're connected from a shared purpose. There's a Surgeon I worked together a long, long time ago, so just it's been what, almost 15-16 years, since we worked at the same place. And yet I would say there's probably still a certain level of spiritual colocation, between us. because of this shared purposes that we've had in the past and what we've seen in the industry, and that's a really powerful tool to build on. So what do tools play as part of that, to the extent that tools make information available to build shared purpose on. To the extent that they enable communication so that we can build that spiritual colocation. To the extent that they reinforce the culture that we want to put in place. They can be incredibly valuable, especially when we don't have the luxury of physical colocation. Hope that makes sense.(chuckles) >> It does. I should have introduced this last segment as we're all spiritually colocated. All right. So Serge, clearly you're still spiritually colocated with Jeff. Talk to me about what your thoughts are about spiritual of colocation. The cultural impact and how technology can move it forward? >> Yes, so I think, while I'm going to sound very similar to Jeff in that respect. I think it starts with kind of shared purpose, and understanding how individuals teams contribute to kind of a business outcome. What is our shared goals our shared vision with what is it we're trying to achieve collectively. And keeping kind of the line to that. And so it really starts with it Now, the big challenge always is over the last 20 years, especially in large organization has been specialization of roles and functions. And so we all have started to basically measure which we do on a daily basis using metrics, which oftentimes are completely disconnected from kind of a business outcome. Or is it on purpose. We kind of revert that to Okay, what is my database uptime? What is my cycle time? Right. And I think which we can do or where we really should be focused as an industry is to start to basically provide a lens for these different stakeholders to look at what they're doing. In the context of benefiting this business outcomes. So, probably one of my theories experience was to actually witness at one of our large financial institution. Two stakeholders across development and operations staring at the same data. Like which was related to economy changes, test execution results, coverage, official liabilities, and all the overran direction of incidents. And when you start to put these things in context, and represent that in a way that these different stakeholders can look at from their different lens. And they can start to basically communicate, and understand how they jointly or complement to do that kind of common vision or objective. >> And Glyn, we talked a lot about transformation with you last time. What are your thoughts on spiritual colocation and the cultural part of technology impact? >> Yeah, I mean I agree with Jeffrey that, you know, the people and culture are the most important thing. Actually, that's why it's really important when you're transforming to have partners who have the same vision as you. Who you can work with have the same end goal in mind. And we would constantly found that with our continuing relationship with Broadcom. What it also does, are those tools can accelerate what you're doing and can drive consistency. You know, we've seen within simplify, which is BT's Flagship Transformation Program, where we're trying to as it says, simplify the number of system stacks that we have. The number of products that we have, actually at the moment we've got different value streams within that program. Who have got organizational silos who are trying to rewrite the wheel. Who are still doing things manually. So in order to try and bring that consistency, we need the right tools that actually are at an enterprise grade, which can be flexible to work with in BT. Which is such a complex and very different environment, depending on what area BT you're in. Whether it's consumer, whether it's a mobile area, whether it's large global or government organizations. We found that we need tools that can drive that consistency. But also flex to Greenfield Brownfield kind of technologies as well. So it's really important that as it's a from a number of different aspects. That you have the right partner, and to drive the right culture here, and the same vision, but also who have the tool sets to help you accelerate, They can't do that on their own. But they can help accelerate what it is you're trying to do. And a really good example of that is we're trying to shift left, which is probably a quite a bit of a buzz phrase. And they're kind of testing well at the moment. But I could talk about things like Continuous Delivery Director to Broadcom tools. And it has many different features to it, but very simply on its own. It allows us to give the visibility of what the teams are doing. And once we have that visibility, then we can talk to the teams around could they be doing better component testing? Could they be using some virtualized services here or there? And that's not even the main purpose of Continuous Delivery Director. But it's just a reason that tools themselves can just give greater visibility of have much more intuitive and insightful conversations with other teams and reduce those organizational silos. >> Thanks, Glyn So we kind of sum that up autonomy, collaboration tools that facilitate that. So let's talk now about metrics. From your perspective, what are the metrics that matter Jeff? >> Well, I'm going to go right back to what Glyn said about data that provides visibility that enables us to to make decisions with shared purpose. And so business value has to be one of the first things that we looking at. How do we assess whether we have built something that is valuable? That could be sales revenue, it could be Net Promoter Score, if you're not selling what you've built, it could even be what the level of reuse is within your organization. Or other teams picking up the services that you've created. One of the things that I've begun to see organizations do is to align value streams with customer journeys. And then to align teams with those value streams. So that's one of the ways that you get to a shared purpose. 'Cause we're all trying to deliver around that customer journey. The value associated with it. And we're all measured on that. There are flow metrics, which are really important. How long does it take us to get a new feature out. From the time that we conceive it to the time that we can run our first experiments with it. There are quality metrics, some of the classics or maybe things like defect density or meantime to response. One of my favorites came from a company called Ultimate Software. Where they looked at the ratio of defects found in Production defects found in pre production. And their developers were in fact measured on that ratio and told them that guess what quality is your job too. Not just the test departments group. The fourth level that I think is really important in the current situation that we're in, is the level of engagement in your development organization. We used to joke that we measured this with the parking lot metric. How how full was the parking lot at 9, and how full was it at 5 o'clock. I can't do that anymore, since we're not physically colocated. But what you can do is you can look at how folks are delivering. You can look at your metrics in your SCCM environment, you can look at the relative rates of churn, you can look at things like well are our developers delivering during longer periods. Earlier in the morning, later in the evening? Are they delivering on the weekends as well. Are those signs that we might be heading toward burnout, because folks are still running at sprint levels instead of marathon levels. So all of those in combination, business value, flow, engagement and quality. I think form the backbone of any sort of metrics program. The second thing that I think you need to look at is what are we going to do with the data and the philosophy behind the data is critical. Unfortunately I see organizations where they weaponize the data. And that's completely the wrong way to look at it. What you need to do is you need to say. "How is this data helping us to identify the blockers? The things that aren't allowing us to provide the right context for people to do the right thing? And then what do we do to remove those blockers to make sure that we're giving these autonomous teams, the context that they need to do their job in a way that creates the most value for the customers?" >> Great advice, Jeff. Glyn over to you metrics that matter to you that really make a big impact. And also how do you measure quality kind of following on to the advice that Jeff provided? >> I mean, Jeff provided some great advice. Actually, he talks about value, he talks about flow, both of those things are very much on my mind at the moment. But there was a time, listen to a speaker called Mia Kirsten, a couple of months ago, he talked very much around how important flow management is. And remove and using that to remove waste, to understand in terms of, making software changes. What is it that's causing us to do it longer than we need to? So where are those areas where it takes too long. So I think that's a very important thing. For us, it's even more basic than that at the moment. We're on a journey from moving from waterfall to agile. And the problem with moving from waterfall to agile is, with waterfall, the the business had a kind of comfort that everything was tested together, and therefore it's safer. And with agile, there's that kind of how do we make sure that you know, if we're doing things quick, and we're getting stuff out the door that we give that confidence, that that's ready to go? Or if there's a risk that we're able to truly articulate what that risk is. So there's a bit about release confidence. And some of the metrics around that and how healthy those releases are and actually saying we spend a lot of money, in an investment setting up agile teams training agile teams. Are we actually seeing them deliver more quickly? And are we actually seeing them deliver more value quickly? So yeah, those are the two main things for me at the moment. But I think it's also about, generally bringing it all together DevOps. We've got the kind of value ops, AI Ops. How do we actually bring that together to so we can make quick decisions, and making sure that we are delivering the biggest bang for our partners. >> Absolutely biggest bang for the partners. Serge your thoughts. >> Yes I think we all agree, right? It starts with business metrics, flow metrics. These are one of the most important metrics and ultimately, I mean, one of the things that's very common across I highly functional teams is engagements, right? When you see a team that's highly functional, and that's agile, that practices DevOps everyday. They are highly engaged. That definitely true. Now back to you, I think, Jeff's points on weaponization of metrics. One of the key challenges we see is that organizations traditionally have been kind of, setting up benchmarks. Right. So what is a good cycle time? What is a good mean time? What is a good mean time to repair? The problem is that this is very contextual, right? It's going to vary quite a bit, depending on the nature of application and system. And so one of the things that we really need to evolve as an industry. Is to understand that it's not so much about those flow metrics is about are these flow metrics ultimately contribute to the business metric. To the business outcome. So that's one thing. The second aspect, I think that's oftentimes misunderstood, is that when you have a bad cycle time or what you perceive as being a bad cycle time or bad quality. The problem is oftentimes like, how do you go and explore why, right? What is the root cause of this? And I think one of the key challenges is that we tend to focus a lot of time on metrics. And not on the I type patterns, which are pretty common across the industry. If you look at for instance things like, lead time for instance. It's very common that organizational boundaries are going to be a key contributor to bad lead time. And so I think that there is reviewing the metrics, there is I think a lot of work that we need to do in terms of classifying this untied PaaS. Back to you, Jeff, I think you're one of the cool offers of Water-Scrum Fall as a key pattern in the industry or anti-patterns. >> Yeah >> But Water Scrum Fall, right. Is the key one right? And you will detect that through kind of a defect rival rates. That's right, that looks like an S curve. And so I think it's the output of the metrics is what do you do with those metrics. >> Right. I'll tell you Serge, one of the things that is really interesting to me in that space is. I think those of us had been in industry for a long time, we know the anti patterns, 'cause we've seen them in our career,(laughs) maybe in multiple times. And one of the things that I think you could see tooling do is perhaps provide some notification of anti patterns based on the telemetry that comes in. I think it would be a really interesting place to apply machine learning and reinforcement learning techniques. So hopefully something that we'd see in the future with DevOps tools. 'Cause as a manager that maybe only a 10 year veteran or a 15 year veteran. You may be seeing these anti patterns for the first time, and it would sure be nice to know what to do when they start to pop up.(chuckles) >> That would right? Insight, always helpful. All right guys, I would like to get your final thoughts on the fit one thing that you believe our audience really needs to be on the lookout for. and to put on our agendas. For the next 12 months. Jeff will be back to you. >> I would say, look for the opportunities that this disruption presents. And there are a couple that I see. First of all, as we shift to remote central working, we're unlocking new pools of talent. Where it's possible to implement more geographic diversity. So look to that as part of your strategy. Number two, look for new types of tools. We've seen a lot of interest in usage of low code tools. To very quickly develop applications. That's potentially part of a mainstream strategy as we go into 2021. Finally, make sure that you embrace this idea that you are supporting creative workers. That agile and DevOps are the peanut butter and chocolate to support creative workers with algorithmic capabilities. >> Peanut butter and chocolate. Glyn where do we go from there? What's the one silver bullet that you think that needs to be on the look out for? >> (indistinct) out I certainly agree that low code is next year, we'll see much more low code. We've already started going moving towards more of a SaaS based world but low code also. I think as well for me, we've still got one foot in the kind of cloud camp. We'll be fully trying to explore what that means going into the next year and exploiting the capabilities of cloud. But I think the last thing for me is, how do you really instill quality throughout the kind of the life cycle When I heard the word scrum for it kind of made me shut it. 'Cause I know that's a problem. That's where we're at with some of our things at the moment. So we need to get beyond that we need to be releasing changes more frequently into production. And actually being a bit more brave and having the confidence to actually do more testing in production and going straight to production itself. So expect to see much more of that next year. Yeah, thank you. I haven't got any food analogies unfortunately. (laughs) >> We all need some peanut butter and chocolate. All right Serge, Just take us on that sir. What's that nugget you think everyone needs to have on their agendas? >> That's interesting, right? So a couple of days ago, we had kind of a latest state of the DevOps report, right? And if you read through the report, it's all about velocity, right? It's all about we still are perceiving DevOps as being all about speed. And so to me the key advice is, in order to create kind of this spiritual colocation in order to foster engagement. We have to go back to what is it we're trying to do collectively. We have to go back to tie everything to the business outcome. And so for me, it's absolutely imperative for organizations to start to plot their value streams. To understand how they're delivering value into allowing everything they do from a metrics to delivery to flow to those metrics. And only with data, I think, are we going to be able to actually start to to restart to align kind of all these roles across the organizations and drive not just speed, but business outcomes. >> All about business outcomes. I think you guys, the three of you could write a book together. So I'll give you that as food for thought. Thank you all so much for joining me. Today and our guests, I think this was an incredibly valuable, fruitful conversation. And we appreciate all of you taking the time to spiritually colocate with us today. Guys, thank you. >> Thank you Lisa. >> Thank you. >> Thank you. >> For Jeff Hammond, Serge Lucio and Glyn Martin. I'm Lisa Martin. Thank you for watching the Broadcom DevOps virtual forum. (upbeat music)

>>from around the globe. It's the queue with digital coverage of women transforming technology brought to you by VM Ware. >>Hi, Lisa Martin covering the fifth annual Women Transforming Technology event the first time it has been running in. So we're not coming to you from Palo Alto today coming to you from San Jose that I'm really excited to be talking with one of the event speakers, the founder of Happier Inc. Natalie Kogan. Natalie, Welcome to the Cube. Thanks so much for having me great to join you, even virtually. Exactly. And we're so fortunate that this I guess, if you can, if you can put a positive spin on it that this event happened when we have technology to still be able to enable as much interaction into a conversations or multiple way conversations as possible. And I know that you just did a session and a couple of days ago at the Digital Women transforming Allergy then But before we get into that, I saw your Ted talk was awesome and it's it's such a and the timeliness happier as a subject, couldn't be more, um, really pivotal. Tell me a little bit about what happier is what the inspiration Waas for your company? >>Definitely. So as many entrepreneurs. The inspiration was my personal journey. So I grew up in the former study on when I was 13 years old, my parents and I left everything and everyone behind and on a journey deep fried becomes refugees did the United States, and we had, as you can imagine, this is a really difficult experience with several months and refugee settlements in Europe before getting permission to come to the U. S. As refugees. And we started our journey and the projects that have destroyed, you know, on welfare and food stamps, very grateful to have an opportunity, but really, really tough. And I was really overwhelmed. That was a teenager. I spoke almost no English, and it was all overwhelming for me. And I kind of decided for myself that if I could just work really hard, achieve a lot of things become successful, then I would feel happy. And then I would just feel like honor this American dream. And for the next 20 years, I did work very, very hard. I did become very successful. I reached the price of four for success. I worked at Mackenzie, you know, the very well known consulting firm. By the age of 25 I was a managing director. We're a venture capital firm in New York. There's fewer than 6% women in venture capital. I started for different companies. I was part of Microsoft in the tech companies, and on the outside I was a feeding incredible stuff. And while I still am still proud of every single thing I achieved, whenever I would've David, I feel happy. And then it was just like the bubble just off, and I didn't feel happy anymore. And so I pushed myself harder and harder because I equated happiness for the achievement. Until, after two decades of doing this, I just couldn't do it anymore. I completely burnt out. Um, it was a really, really dark time in my life, and I knew I had to find a different way to live so that I could do work that's meaningful to me, but that I could also honor myself as a human and find joy in the present. And that led me to doing a lot of research in psychiatry and psychology and neuroscience and learning all of these incredible skills and practices that changed my life, starting with gratitude, which is how you cultivate join the present moment and really inspired me to leave. My career is a technology exact behind you found happier. We have the same mission since we've been founded and that is to help millions of people. Dr. In working in life by practicing science, back skills to cultivate there will be what are >>some of the scientific skills behind it and anything that that, you see that is even more pivotal in week eight of this work from home shelter in place? >>Yes. You know it It sounds really weird to say, but I feel like I've been preparing my full life. Do you help people right now? Because the skills that I have learned and I share are so essential. And >>the two that I >>would mention that I've been you know, we've been doing all these virtual sessions for teams and companies, and this is the ones I talk about. The first is the skill of gratitude. You know, gratitude is just very simply zooming in on something in your life that is good. That is positive. That is meaningful. and honoring it with your full appreciation. And you know, we're all right now going for so many challenges and we all have with all the negativity bias. And that means we're much more sensitive humans, anything that's negative and anything that positive and when we're going through a challenge, that negativity biases even more sensitive. So I know many folks right now are feeling really overwhelmed with their own feelings, but their own sense of loss and fear and with all the negative news and so practicing gratitude is essential because when you pause and you focus on the things >>in your life as it is, >>um, it's the challenge that you do appreciate. You remind your brain that the the challenge is not everything, that there is more to your life than what is going wrong. And that actually helps you to feel a little bit less stressed and anxious. And the other piece of science that I love to share is another skill that I talked about, which does Ah, and acceptance. Really. It simply means that we learn, look at how things are and how we feel with clarity instead of judgment, right and shorthand for judgment is should shouldn't feel like this. It shouldn't be this way, and that's having clarity. Allowing yourself to actually feel the difficult feelings helps us to move through them with a little bit more easy. I think it's one of the most, um, powerful mindset. A mindset shift that I learned on my journey is that happiness does not mean that you feel positive all the time. Happiness and emotional being means that we embrace all of our different feelings, including the difficult one, and we learned how to move through them with compassion. What are >>some of the things that when you're talking to the C suite executives that certain companies, whether it's bm ware or others, how our executive teams managers, where does the emotional health come in to the play? Knowing that these folks are managing teams, there are, we're seeing, as you point out, you know, the negativity vice. We're seeing the numbers of unemployment go up and up and up. Where is emotional health in terms of priority at the executive level? So this is >>one of the it, so it sounds really weird to say, but all of a sudden its like in this huge wave it already started, right? Some companies and we work with many of them already understood. The executives already understood that employee well, being an emotional health, it's not an extra. It is not optional. It is non negotiable. If you want your people to be at their best, there are literally mountains of research that show that when you cultivate, employees will be people are more productive, more resilient. More so, Cecil, they still better problems. But happened in this crisis is that the companies that were in a place where oh, this isn't really important or this is nice to have They are now recognizing that this is actually the most important thing that they could invest in for the success and longevity and survival of their businesses. And so I'm actually incredibly grateful for that. I don't like that off that we have to pay for it. But I am incredibly grateful that in this challenging time, more and more leaders there understanding that their own well being and the emotional health of their employees is non negotiable, not just for survival of their businesses, but if they want to be at their best and actually figure out how to thrive in whatever the future holds. >>And I'm glad to hear that, because the massive amount of uncertainty that we're all facing is unprecedented. You know, you can't pick up the phone and call your Brian mother and say, What did you guys do back in the day? And honestly, even if there had been something similar, 1918 hasn't been that long ago. People have nowadays are used to getting everything that you want on demand and also being able to get connected. Um, have good WiFi and be able to deliver what your clients what your what your bosses expect. The uncertainty factor that really weighs heavily on emotion is a huge inhibitor to productivity negotiation. Being worry >>if I can jump in uncertainty is the hardest thing for a brain to deal with. Our brains would rather know that something very bad will definitely happen. Then the B and uncertainty and I've actually been talking so much the companies and leaders about this, that this is literally the most stressed that we can experience because our brains number one job and I'm the founder of a company called Happier. But I always say that your brain number one job is not to keep you happy. It >>is to help you surmise. And so >>you're bring this constantly Evaluating your environment is the state of fruit or is a dangerous right fighter. But we know that was fun. What's happening right now is that the brain and I've come up with an answer. It doesn't know. Is it safe? Is it not safe? And I don't just mean in a macro way, um, macroeconomic way with the virus. I mean day to day. Things change day to day. We're juggling kids and family, and our businesses are changing so the brain doesn't give up. It's still tries really hard to figure out how to keep your state and that hard that working overtime the way it does that is by releasing stress hormones. So on top of just the very real challenges that so many folks have with worrying about loved ones juggling, working from home and family, there's also this chronic level of stress the world feeling because of uncertainty. >>Tell me a little bit about the interactive session that you held at WT through the other day. What were some of the common concerns or questions that you heard from the >>audience. Yeah, it's really interesting. It was such a great session, and we we had a lot of questions. We could not answer all the questions. Um, and I think that it means a lot to make it really thought about what they wanted to ask. There's a couple of things that emerged as common thread. The first was, How do I help someone in my life a colleague that I manage a loved one? How do I help them during this time if they're really overwhelmed or stressed? They're feeling sad, and we talked about the seal of acceptance, and we talked about how it might be our instincts to immediately cheer up the first thing. But actually, the bigger gift we can give them is to let them know that it's okay to not be okay and to honor their feelings with our effectiveness, and that actually helped them get through. So that was one of the themes that came up a lot. Another one was, with all of this uncertainty and the stress, like people would ask, I have trouble getting motivated like I love my job I love what I do, but I have so much trouble getting motivated, and that is very real. And the first thing that if anyone listening, feels this way, um, there's nothing wrong with you. Think about the amount of energy you're brain is using on all the stress. So no wonder you feel more fired and not as motivated. And so we talked about practicing self compassion, Um, in our expectations of ourselves and recognizing that we're undergoing something unprecedented and so difficult and then get motivated connecting the past on your to do list. Do How do they help someone else? Because that is where we connect first since the purpose, right, So that projects you're working on with your team or that presentation that you just can't get motivated to do. Ask yourself who does this help and actually answer the question? And in that moment, you connect yourself the purpose, which helps us be more resilient and more motivated. >>Get a notification or lack thereof is a huge problem, and I you know, you can't think it's not just may, not just you. It's got to be all the way up to the tops of companies that are really struggling because, as you say, the brain is so focused right now and busy and trying to assess things. And there are no concrete answers. But one of the things that you said I read your article in The Washington Post that you just did in the last week or so with your daughter and with my daughter. Yeah, with your daughter Mia. And the validation was Start on. And it it's so simple. But it's one of those things that I think often we think, Well, let me explain something and try to help you in that way without maybe stepping back and going well, actually help me. But what helps you? Are you seeing that that the executive leaders are also kind of stepping back and asking their teams? How are the ways that you want me to communicate with you? Or is that something that's happened? You know, I think that >>we are in an era of, um, human embracing leadership of, and I am so welcoming the era of leaders who are leading with their humanity first and are embracing the humanity of their people first. You know, I have this, um, actually working on my next book right now with this for leaders. And I have this concept, um, because I was a leader for so many years, and I always thought that I keep my emotions hidden, that emotions really didn't have anything to do with work. So I have this part that for leaders, they imagine you're holding a white board, and this is your emotional whiteboard on it are written your feeling. Whether you want to admit them or not, that team feels them, and it's the same for everyone on the team. So when you walk into a meeting, whether the virtual meeting or in person what is written on your emotional whiteboard, what are you feeling? And how are you approaching others? What do you want to be written on your emotional whiteboard, right? I think, as leaders, we would say, Well, I want to stay there, hear about you as my employees, that I want to hear how you're feeling. But think about are the actions you're taking aligning with with on your emotional whiteboard, right? And so listening and hearing, you know, I have this, um, came up with shorthand. Really? For me as a leader during a challenging time, and it's at C D. The first is acknowledge. Acknowledge your own challenges. Acknowledge your teams challenges, right. Validation. This point we're talking about, he is prepare genuinely care, right? So don't just do it as a check mark. But bring your humanity and compassionate actually care about people. There's so much research that when employees know that their leader cares about them, that on its own is hopeful for them. So there will be in their productivity. And he acts. So a c c es teach by example. So do the things that you want, your employees, the follow. And, um, I do see leaders stepping up more and more in their passion and their acceptance. And again, I think this is, ah, difficult but unique moment in time Do elevate our human embracing leadership. >>Do you advise women and men? Teoh. When we talked about gratitude a few minutes ago, right down, maybe. Right. Maybe it helps with your visual learner or someone that learns by storytelling to write things down, Maybe write down each day a few things. Maybe they seem so simple that you're grateful for, Or maybe even I like the idea of the emotional White Board. I can see that as something that would be helpful to write down. Do you recommend that to folks and maybe write down what your actual emotional thing is and what you want it to be? So a couple >>things on that. So the short answer is yes, you know, when it comes to gratitude, Um, it doesn't really matter how you practice like people say to me like I'm not a journalist, that's fine. That as long as you're specific and your gratitude So instead of I'm grateful for my family, how about I'm really grateful that I could give my daughter hug before I started interview? Right? So the more specific, the better. And actually the smaller the better. You talked about small things. Research shows that it's the frequency of small, positive experiences that contribute thoroughly. Satisfaction more than anything, grants so the smaller the better and capturing does health, so you can write in a journal. You can write it on a sticky notes. Maybe it's a text that you send to a friend to encourage them to practice practice as a leader. Maybe it's an email that you send to your teams. The factoring in some way really does help. And when it comes to the emotional white board, the practice that I share with, um, everyone is a check in. Check in with yourself, right? It's so incredible. You know, we have this group for women executives elevating women leaders. Is that all Vertical group, the year long program. It was worked well before this. So we have a group that goes with us every year, and one of the practice that we do is in the morning and in the afternoon, you check in with yourself on just day all my feeling, and you would not believe the impact that that has on their ability to solve problems on their ability to show up as their best just by pausing and checking in, like, How am I feeling what is in my emotional whiteboard? Acknowledging that without Dutchman being compassionate towards yourself and then saying, What is one thing I can shift if I would like you feel differently? >>The acknowledgement piece is critical, I think because it's it's the vulnerability to step up and go. I don't feel great about this and let me let me say that out loud. Maybe it helps me become accountable to that or expect it to a boss or a colleague that put it out there. That's a hard thing for people to do. Especially I think there is this dichotomy of people being concerned about John Safety when we're seeing what's going on in the news. Did any of that have come up during your WT two session about? I'm afraid to admit that I'm not motivated because our company's experiencing layoff. >>Yeah, it's definitely come up in the session and other sessions of kind of finding that balance. And look, you have to be realistic because we all have different filters in our teams. You have to be realistic about your leadership. But what I find over and over is that authenticity wins today, right? So, um, you have to you have to make all right how much you share. But even if it's just a little bit of Acknowledgments, it is helpful because it helps you not resist it so much and more likely than not. There's somebody on your team who feel similarly so that, by the way, there's comfort in knowing we're not alone. there's actually neurological comfort in knowing we're not alone like we need that sense of safety, but also you made them be able to move through that and brainstorm together and help each other get motivated. So you know, you have to judge by the culture of your team. But authenticity and you acknowledging your humanity to whatever degree you feel comfortable is usually an incredibly hopeful practice to help you be at your best, whatever that means. That >>day, I couldn't agree with you more. I always The authenticity is contagious. Natalie. It's been so great having you on the program. I wish we could keep chatting, but it is time to go. Thank you so much so folks can go toe happier, dot com or help your fellow happier and more. How about your home? Lots >>of lots of tons of free block posts and videos on all of the different practices I shared more about anything we do. So yes, come visit us that happier dot com and thank you so much for such thoughtful questions. I'm always incredibly grateful for thoughtful questions at interviews, but I really appreciate that. Well, >>good. Now it's been a pleasure having you. And I want to thank you for watching on behalf of Natalee code. And I'm Lisa Martin covering women transforming technology. The virtual version 2025. For now. >>Yeah! Yeah, yeah, yeah, yeah, yeah!

>>Live from Copenhagen, Denmark. It's the Q covering Nutanix dot. Next 2019 brought to you by Nutanix. >>Welcome back everyone to the cubes live coverage of dot. Next here in Copenhagen. I'm your host, Rebecca Knight along with my cohost Stu Miniman. We are joined by Sammy Zog LaMi. He is the SVP sales Europe, Nutanix and Sylvan CU. He is the senior director systems engineer for EMEA at Newtanics. Thank you so much for coming on the cube for you for returning. And this is your first time. >>First time. Absolutely. >>Well I want to, I want to start with you. You were on the main stage this morning and you were describing being one of the first few employees in France, working out of hotel lobbies, keeping all the promotional materials in your house and people not even knowing how to pronounce Nutanix. Now here you are for you six years later. Describe, describe a little bit what it, what, what this journey has been like for you. Being at Nutanix >>for this journey. Um, you know, is a, is a successful journey obviously, uh, where we started from scratch in Eva, uh, where we built a lot of relationship with the channel. We started to have our first stories with customers and, uh, you know, the only thing we could not, uh, you know, focus was the speed of growth. And I, if you told me six years ago that we would be four and a half thousand, you know, in this conference, I wouldn't have believed it. And I think the, you know, overall journey is a, you know, an accelerated journey of development and that we have, >>yeah, Sam, Sammy, prednisone side, a little bit about, uh, you know, we sometimes call it nation building, but, uh, you know, the channel of course, a very important, uh, you know, talked about some of the, kind of, the challenges in, uh, some of the successes as to what, what has made Nutanix so successful, uh, in, in your time. Yeah. I think, uh, >>you know, the technology is for sure a big element in this that is solving business problems. But when you think about it, there's many stories of great technologies that didn't make it or didn't make it big. So I think the openness of this company from day one, uh, to work with partners to work with an ecosystem of Alliance partners. Uh, we were also very open to share how the Nutanix technology is built and is working. So there's a lot of openness around your Hasise works. It's not a black box. Uh, and we integrate with the ecosystem. So for our positioning, which is mainly initially the data center, the large environments we have to integrate into customer environment, we have to integrate with existing technologies and uh, the fact that we are open from day one and we keep that line is helping a lot in the traction. >>I want to get into that strategy in a little bit, but I want to bring you into this conversation to Sylvan and, and just to have you talk a little bit about what you're seeing in the competitive landscaping, what, what are some of the things that Nutanix needs to focus on? Because the competitors are a really edging in. We are focused to deliver >>our vision and continue to build the pieces that are still under construction there right now. And to be back on the question about the partners, the adoption also come first from the partners before their customers. And really working with them on engaging with them was the result of the success was not just signing contract enabled them, but really engaging with them at customer sites. And as soon as they see the reaction of the customer, they can be believe in it. And we scaled very fast because of them. I'm wondering, get both of your comments. Talk about the, uh, the competition for talent. Also, when you talk about Nutanix over 5,000, the channel is very strong. It makes it a little bit tougher, uh, to kind of pull those pieces in. If you're Silicon Valley, Oh, there's this startup, I want to join, things like that, but have to imagine things are a little bit different. And I'm in Mia, >>I would say. Well, competition for talent is definitely here in Emir, especially on the topics that we are tackling in the cloud, the DevOps, big data, et cetera. Um, now, you know, we are not attractive brand, uh, you know, there's a demonstrated pass of development for our employees. So I think on top of being a successful company, we have a lot of proof points of building careers. So people want to join for the fun for the success. We are also to be able to fast career. That's helps now saying that it's still not an easy task. You know, there's a, especially the volume of recruitment we are doing, uh, so we have organized ourselves very well, uh, to onboard people, enable people and maybe be in a position to hire people that don't have all the skills but have the right DNA and then we can, you know, always teach the skills. That's the way we are. >>and on a technical side, uh, all the user's previous it vendor let's say, was looking for specialists of complexity. You know, what is the behind the scene and we are in different situation, meaning that we can start small first and we talk about the project of the customer. And until this project works, we cannot move forward. We cannot obsessive. So our situation is more consultative and being a trusted advisor of what they tried to achieve and not anymore on what we tried to build our own our side. >>That's a very important point. The mindset of successful employees are the ones that are focused on the outcomes. You know, they're not here to sell a product, they focus on project and the outcome of customers. >>So how do you find that person when you are, when you're interviewing your pool of applicants? I mean that, that is, that is such an important part of the culture here, this people first attitude and really being all hands on deck if a customer has an issue. So how do you, how do you know when you're interviewing someone that, that, that they have got their, the right DNA to be here? >>Well, first we knew before they, during the interview, because we are well connected on the market and we have sources of information about how they operate on day to day. Now, of course, of hiring so many people over the years helps. And there's a lot of small details that, you know, we can notice, uh, in, uh, in our recruitment process. I think we've gotten very professional in the way we recruit. We still have a lot of refills as well from employees, which helps in terms of, uh, you know, making sure we hiring the right DNA, but we want to diversify. We don't want people coming from the same background. We're doing a pretty good job on diversity, on every topic, you know, gender, ethnicity, background, uh, this is a, you know, pretty good success. Alright, so >>semi you, you've got a new role. So it gives us a little bit of insight as to your vision. What should we should expect to see as a strategy for Nutanix and EMEA? >>I would say first, uh, you know, three months on the job and I have no intent to break anything that works. Uh, I think there's a successful recipe in anemia, which is a legacy of Chris Keller Ross. Uh, lots of good methodologies, verse of good principles of working, no intention to change that and maybe the phase after that for MEA, but for the whole company is to focus on Australia. And we see that, you know, our technology is well suited for mission critical environment is well suited for strategic projects for customers. And maybe we should become the default, uh, you know, uh, vendor that you think about when you go for mission critical projects and you know, trust formation. Uh, I think today we do a very broad set of projects with customers. Um, tomorrow I would like customers to think first about Nutanix when they think about something that is critical to their business. >>And in the same way for partners, uh, if we can move from being a vendor with high grows, great margin to a vendor that is helping them transform, you know, their business model or the way they attack different segments, you know, then we will have achieved a good phase two. What do you see as the biggest challenges facing you right now? Well, the biggest challenge is inside clearly is growth. We see that in every area, every time we grow fast, then suddenly you need to change organization processes, your principle of working and you, you need to reassess yourself and your way of doing things. Even at pesonal level. Uh, that's the biggest challenge. I think we, if we are not constantly paranoid about re re assessing that uh, growth can break a lot of quality, uh, in the relationship we have with customers but also in our velocity. >>Oh, I wonder if you could bring us inside the customers a little bit. What are some of the key roles that you find in, you know, where does Nutanix has the best engagement with and you know, strategically where would Nutanix may be a change over time as to where they're, where they're engaging with a customer. >>So now there is no more question about the fact that part of the, it will be in the cloud part will be internally, some people will go more one side or the other side because Nutanix both technology >>on both sides, we can take care of old school application and be sure that can still run in the cloud. And on this society, if you develop an application totally distributed and so on, meaning a cloud native, we can run it on a Nutanix and all the platform looks like the pubic cloud for this application. So we are the unique situation where we can, we don't need to be in the cloud or outside of the cloud, meaning that we can give a strategy with the customers or what it can do. What is the good point, what is the most difficult to achieve on both sides. And also we provide a way to package application to deploy everywhere. We have all these governance tools on top of it because we know the new way of consuming the cloud is more open bar, which you need some way of controlling the situation and we are really trusted advisor on their strategy to define what will be their it in two, three or four years. >>Okay. So sounds like not just the infrastructure owner but talking to the application owner or some of the C suite that might make some of those broader strategic decisions. >>Yeah. Yeah, exactly. Uh, the platform works, meaning that there is no more cushion on that at scale. You get all the benefits that you can see on the, on the public cloud. Now it's more the way you consume it, you organize the consumption and also you've have those, the same of urine Mount whatever is the application, uh, to, to find the, to have the best place for this application. >>What would you say your, your, your here as you said, uh, at in Copenhagen, thousands of European customers all here under one roof. What are you getting out of this? What kind of conversations are you hearing? What's most surprising to you? Just to, I mean we're, I know we're only in the beginning of day one, but what, what do you, what are you hearing right now? >>Well, we talked to a few customers already and what's a very common pattern? Most of the customers I took so far, they really accelerating on becoming a service organization. So enterprise companies, they really want to organize themselves to be cloud ops. And even though we were talking about automation before, now they really are doing it and they are actually focusing on changing the skills of their teams, their organizations and of course the technology afterwards. >>Yeah. Uh, any, any particular is on automation. Cause I think back, we've been talking about automation my entire career. I agree with you today. It is a, you know, more substantial conversation on automation. Are there any particular as either in Newtanics portfolio where some of the kind of partner tooling out there that are kicking things along? >>So, uh, we talk about automation since a long time, but most of the time that was, you have an orchestrator, it's like a Swiss knife and you can orchestrate what you want, but at the end of the day, nothing was done. We believe that the platform must be automated by design, right? And everything need to be by design. So it's a, it's the difference between the, between the previous way of thinking, automation and now where the platform is totally it. >>I believe Leber GF said autonomous is what >>we were looking for. Yes. You got to the point. If it's not autonomous, why? Why bother? Yeah. Or we had examples of customers who launched private cloud projects and they had like 8,000 Mondays to build the orchestration of the private cloud. And honestly, if you don't have a a hundred thousand VMs to run, it makes no sense. So the fact that no, it's built in and it's not a project to have automation, you know, that makes sense economically as well. Great. Well semi and see you. Thank you so much for coming on the cube. It's a pleasure having you later, Rebecca. Thanks a lot. Thank you. I'm Rebecca Knight for Stu Mittleman. Stay tuned for more of the cubes live coverage of.next.

>> live from San Francisco, celebrating 10 years of high tech coverage. It's the Cube covering Veum World 2019. Brought to you by VM Wear and its ecosystem partners. >> Hey, welcome back here and live here in Mosconi North. The Emerald 2019 Cube Live coverage on Shopping Day Volante Jr Jr. Who's here? EVP general manager, Telco and Edge of Cloud for Vienna. Where Thanks for coming on. Thanks for having me. I know you're super busy. We don't have a lot of time. Get right to it. Um five g a big part of the key. No discussion that's gonna enable a whole bunch of Pakal the pregame show pre gaming not even talk about that. Also. Telco on the Edge Computing Big part Michael Dell said, Edges the future Now these air to emerging areas for you guys. What's the positioning? What's the update? >> No, absolutely. I mean, if you look a tw telecom infrastructure. For the longest time, telcos have played a role just as pure basic connectivity providers. And with five g coming on board, they finally have an opportunity to break out of that and redefine the cloud off the future. So for us the big opportunity around five g is not just the better provisioning off like Higher Man With Service is to consumer for voice and data buy the whole set off new enterprise service is that can be provided on top of this five g network. And in order to be able to do that, you really need to go in with a virtualized telco Cloud architecture. Underneath that, and so we are working with carriers globally now preparing them for five G with an architecture that's going to help them deploy. New service is faster for both their consumer as well as enterprise. >> Going to be the white knight at, so to speak. For these telcos because they've been struggling for years over the top and any kind of differentiates service is even in the network layer. Exactly. I've had tons of rack and stack machine, so they're after their well, well stacked up in terms of computer storage. Also connectivity to the edge. That's the back hall. So you have back haul, which is connectivity. Companies that have massive expertise in scale but fumbling in operational cloud natives that >> by not just that, but I also think that having the idea off on application platform that allows them to go and deploy service is faster and then decide whether they're just going to play at the network connectivity level or at the application tear or a full SAS tear. These are all options that are open to them now with this notion off. Telco five G coupled with an NFI and cloud telco cloud infrastructure. Underneath that and never before have they had this option to doing that. And this is now open to them >> and the cloud native is there greenfield for AP supporter having applications on top of it. Exact icing on the cake, right? >> Exactly, Exactly. And so they're all looking at core architectures and then, potentially, their radio architectures now all being opened up toe deploying new service is that are much faster to provisions and then extending that to EJ and >> five G's deploying. So we know it's out there. So it is pre game is Pat, Guzman said. You know, not even an inning Yet in the metaphor of baseball innings, I >> gotta ask you get my phone. That's not that's fake ill. I know it >> did that with four g to >> skeptic e stands for evolution, which is coming soon. >> That's vaporware for tell Coke language. The surface area is going to radically get bigger with this capability. Yeah, security's gonna be baked in. This is the number one concern for io ti. And more importantly, industrial I ot We've been reporting on silicon angle dot com. This is a national security issue because we're under cyber attacks. Town's getting locked out with ransomware critical infrastructure exposed. We're free country, and I want to be free. We don't lock down. So you have security built into this new promiscuous landscape that is called the coyote Edge. Because you wanna have no perimeter. You want the benefits of cloud. But one whole malware is in there. One take over physical device could cost lives. >> Yeah, there's a big concern. Yeah. What's your thoughts? Yeah, No. So I think there >> are two ways of looking at it. One is the way you looked at it in terms of the security perimeter expanding and then us making sure that we have the right level off infrastructure security baked in to enable this to be an easier, manageable security architecture. This is sort of the pitch you heard from Mia Mary, even in the context of our acquisition of carbon black and how we're thinking about baking security into the infrastructure, the other way of looking at this is if you think about some of the concerns around providers off telecom infrastructure today and how there might be or might not be security back doors. This is happening in today's hardware infrastructure. Okay, so in fact, I would argue that a sick software defined architecture, er, actually ends up providing you greater levels of security. Because what you now have is the option off running all of these network functions as secured as software workloads in a policy envelope that you can introspect. And then you can decide what kind of security you want to deploy on what kind of workload. >> That's an innovative approach. But it doesn't change much, really, from an infrastructure standpoint, does it? Or does it? >> No, it does, >> because now, instead of having a hardware box where you have to worry, I mean, if it's a close, hard red box and you don't quite know what is happening there, the question is, is that more secure than a infrastructure radio running the software that you can actually introspect. I would argue that the software defined approach is more secure than having a hardware box that you don't know. >> I would buy the premise that certainly we know that supply chain concerned. You know the speculation Super Micro, which never was proved. >> It doesn't matter who the vendor is or what the country is. It really is a concern in terms of not being able to introspect what has happened Going inside >> for my tea shop. I'm running VM where operating I want developers. So now you're going to tell Coz you revitalize their business model? They had a rule out appy. Now what did you see? That connecting is gonna be connective tissue between >> I'll think about it. I didn't feel goto a telco. We look at really three stakeholders in there. One is I t the second Is there be to be or enterprise facing business and then the 3rd 1 is their core and access network or the CTO. We're now have a value proposition of having a uniform architecture across all three stakeholders with the uniform ability to create applications and drop it on top of each of these infrastructures with the ability to manage and secure these again in a uniform way, not just that, but also make this work well with other cloud infrastructures private, hyper scale, public as well as EJ. >> That's table stakes. You have to do that. These jokers have to operate whatever >> well it is, But it's not. I mean, if you think about what the infrastructure off a tailcoat today is, it's far from that, because it's it's sort of a closed environment. You can't access anything from a telco environment in order to go build an application to it, and it does not resemble anything like any club >> you could enable Telco. Just I'm just kind of thinking connecting the dots here real time in the Cube. If I'm a telco, hell, I'll take that VM wear on a deli and see model. Make me a cloud and I'll sell Cloud Service is to markets that kind of >> it is. Actually it's a very important part of our business model because most telcos would not move their own infrastructure from a network standpoint onto a public cloud. But they are eagerly awaiting the ability to operate their own network as a cloud, and if they can have somebody manage that for them, then that is very much within the >> you're enabling. An increase in the number of cloud service provides potentially the paint on the makeup of the telco tier one tier two tier three size. Pretty much >> potentially. I mean, it's taking an existing operator and having them operate in a more agile way and potentially increasing anew form off a cloud service >> provided telcos wouldn't move into the public cloud because of they want to control. And the cost is that right or it's >> mostly control. It's not about cost. It's about taking What is your sort of coordinating for, ah, packet corps or for a radio network? Yeah, and there is also an angle around competition, I think telcos our what in about the Amazons of the world and the azure eyes of the world potentially becoming a service provided >> themselves. And that's what I wanted to ask you about the business impact of all this discussion you guys were having is, you know, the cost for bits coming down. The amount of data is increasing faster. You got over the top providers just, you know, picking off the telcos. Telcos can't compete their infrastructures of so hardened. Will this all change that? >> Absolutely So. I think that it has the potential to changing all that. I don't think all the telcos will take advantage of it. Some off them might end up being more traditional and sort of sticking to where they were. But for those that are willing to make the leap, I mean, as an example, Vodafone is a customer that has actually gone in with this architecture with us. A. T and T is working with us with the Vela Cloud software from via Mary bringing a new form off branch computer branch connectivity through SD man. So these are all examples of telcos that are actually leading the >> charter. But if they don't lean in, they have this vision there either. Well, it's either because they're protected by their local government or they're going to go out of business. No, I would >> agree. I mean, it's sort of silly from our standpoint to be talking about five G and not thinking about this as the architecture for five, right? I mean, if you only focus on radio waves and your wireless network that's like a part of the problem, but you really need to have the ability to deploy these agile service's. Otherwise, you could get killed by >> the O. T. T. So how do you compete against the competition? What's the business plan that you have? C. Five G? We see that in the horizon that's evolving its evolution, so to speak. Pun intended on edge is certainly very relevant for enterprises, whether it's manufacturing or industrial or just people. Yeah, >> I'd say there are two things. One is a CZ. I'm sure you heard from folks at GM, where our vision is this notion of any any anywhere. We've talked about any cloud at any application that any device. So that becomes one of the strongest different chaining factors in terms of what V Amir can bring. Tow any of our customers compared to the competition, right? Nobody can actually make it really across these dimensions. If you then take that architecture and use that to deploy a telco cloud, we're now making investments that are telco specific that allow the tailcoat than take this and make the most out of it. As an example, we're investing in open stack we're investing in container ization. We just bought a company called Johanna and Johanna essentially allows the operator to go and provide metrics from their radio access networks. Use at that to train a learning engine and then feed that back so that the operator can tune their network to get like fewer dropped calls in the region. So if you combined technology like that with this, any cloud infrastructure that we have underneath that that's the best in class deployment methodology for any. Tell Cho to deploy >> five. Your business model metrics for you internally is get Maur deployments. What stage of development five G certainly is in a certain stage, but you know, edges there. Where is the Progress bar? If you're the kind of oh, >> it's actually mold phenomenally. I mean, every time we have conversations like this, we're moving about further in terms off. How many carriers are deploying on via mare on a telco cloud Architecture? How many subscribers are basically being serviced by an architectural like this? And then how many network functions are being deployed? Two of'em air architecture. So we are over 100 carriers now we are over. We have about 800 million subscribers, or so that about globally are being serviced by a V M Air supported network. On then, we have essentially over 120 network functions that >> are operating on top of you. Usually bring in all the same stuff that's announced that the show that stuff's gonna fold into the operating platform or Joe Chuckles have different requirements. Off course. It's >> both. We take the best of what is there from the sort of overall vehement factory and then as a team. My team then builds other widgets on top that are telco specific. >> How big is your your tam up Terry for you? >> Well, so the best way to look at it as telcos globally spend about a trillion dollars in capital investment and then probably to X that in terms of their operating expenditure over the course off all of the things that they do right? And out of that, I would say probably a tent off that. So if you take about $100 billion opportunity, opens itself up toe infrastructure investment in terms off the kinds of things that we're talking about now, they're not gonna move from like 0 200 of course. So if you take some period of time, I would say good subset off that $100 billion opportunity is gonna open itself up >> to it. This kind of business cases, eliminating that two x factor, at least reducing it. Is that exactly? That's not just that Service is that's, >> ah, cost reduction alternative. But then you have the ability to go deploy. Service is faster, so it's really a combination off both sort of carrot and the stick, right? I mean, the character here is the ability to go monetize More new service is with five G faster. The stick is that if you don't do it, Ortiz will get there faster and your costs off. Deploying your simple service is will increase his >> telcos, in your opinion, have what they have to do to get the DNA chops to actually be able to compete with the over to top OT T providers and be more agile. I mean, it's obviously sort of new skills that they have to bring in a new talent. Yeah, >> well, first and foremost, they need toe get to a point where their infrastructure is agile and they get into a business model off knowing how to monetize that agile infrastructure. So, for example, they could offer network as a service on a consume as you go basis. They could offer a platform as a service on top off that network in order for or titties to go build applications so they can do Rev shares with the forties. Or they could have offer. Full service is where they could go in and say, We are the conferencing provider for videoconferencing for enterprises. I mean, these are all models that >> the great conversation love to do. Your Palo Alto? Yes. Have you in our studio want to do more of a deep dive? We love the serious, super provocative, and it's important Final question for you. Though Pat Sr here on the Cube, lay asked him, Look back in the past 10 years. Yeah, look back in the next 10 years. What waves should everyone be riding? He said three things that working security and kubernetes humans being number one actually promoting convinced everyone for the ride, for obvious reasons, clouded. I get that, but networking Yeah, that's your world. That's changing. Which which events do you go to where you meet your audience out there in the telco because networking is a telco fundamental thing. Sure moving packets around. This is a big thing, >> eh? So far, operator networking related stuff, I would say. I mean the biggest shows that for us would be Mobile World Congress as an example, right? It's where many operators are. But I would also say that when we do our own events like this is the ember. But the movie forums in in Asia packers an example. A lot of the telco conversations I find they are best done one on one before. Yeah, the forums are our forums, but we will goto have one on one conversations or small group conversations >> with our telco customers. Locals Shakaar Thanks for spending. You get a hard stop. Very busy. >> Thank you. Thanks for having me >> here, Sugar Yaar, Who's here inside the Cube bringing down five G, which is still pregame. A few winning something first thing is gonna come up soon, but edges super hot. A lot of telco customers be back with more live coverage of the emerald after this short break

>> live from London, England. It's the queue covering a ws summat. London twenty nineteen Brought to you by Amazon Web services >> Welcome back to London Summit Everybody, this is David Lamont and you watching the Cube, the leader in live tech coverage. We loved to go out to the events. We extract the signal from the noise. This is our one day coverage of a WS summit London, and it's packed house twelve thousand people here. The twenty six thousand people registered, which is just outstanding. Chris Bunches. Here's the general manager of a MIA for cloud reach, and he's joined by Mark Randy, whose CEO of signal FX. Gentlemen, welcome to the Cube. >> Thank you. >> Okay, let's start with signal effects. What's going on at the show? What's the buzz like? >> Very busy. Dozens deep. A lot of demonstrations feature in our massively scalable metrics platform and distributed tracing platform. So we've had a very good show. Good showing in London. >> Good. We're going to get into some of that. Chris, tell us about cloud reach. What you guys do? >> Sure. So Cloud Reach was founded in two thousand and nine. So quite a long time ago in the history of cloud confusing, at least >> was right after the Cloud City with >> quite a pure vision around helping complex organizations to adults public cloud computing technologies to doom or faster and better. That's all we've ever done. It's all we ever intend to do way work these days with enterprise organizations across the cloud lifecycle starting with adoption, helping them to understand White Cloud. How am I going to do this? How am I going to move my data center's into the cloud? How am I gonna build new services moving on through the life cycle? We help them with that. At that migration, we helped them to shut down their data centers on rebuild them in a WS. We helped build New Cloud native Services. Using the latest offerings from from Amazon and other cloud providers, we worked with him on Data analytics, helping them to generate insights from their data. Data flows in an ever faster pace from across the across the world into their organization. On all of that is wraps with an MSP manage service twenty four hours a day, seven days a week. >> So, Mark, I gotta ask you so back back in the day, the narrative was that the public law was going to kill every man, his service provider out there. It's been nothing but a tailwind for your business. Business is booming. What's what actually happened to give you that? Left >> on the signal effects side I look, the big trends are the move to the cloud number one. The second piece is just a change in the architecture's you know, the move to communities, the introduction for elastic burst e type use cases of things like Lambda and and that even more importantly, just the process of developing software movement from, you know, waterfall, Dad, agile and the Whole Dev ops movement in introduction of micro services. So that's it's It's just a lot of a lot of these ways been going on for quite some time, but they're really starting to hit the shore to shore right now, and I think it's been a great great opportunity for companies like Cloud Reach Tio to take advantage of were very excited by the partnership. >> Well, it has. It has ripple effects on the rest of the business, doesn't it? I was saying earlier in a segment that it used to be the business of No, we can't do that because and now you look around this audience, it's all doers and builders, and, you know, it's it's actually great marketing because it works, doesn't it? So clouded has been a fundamental component of >> Yeah, I mean, our whole businesses around making t v enabler helping businesses to innovate. Once upon a time, the message was all around. Cost saving is the reason to move to the cloud, and there's still an element of that. Nobody wants to pay Mohr, but actually, increasingly, what we're seeing is organizations moving to Amazon because they want the agility, they want to move faster. And they don't want to be the the culture of no and have a process that takes six months to deliver a new service to the business. They want to be out of deliver things in hours or minutes in the some cases, and they want to do so quickly on they want to innovate, a pace that they've never been able to before, partly from a competitive threat perspective and partly from a market opportunity. There's so much, but we can deliver to customers if we put our minds to it and use the primitives, the Amazon providers, as building blocks to enable new >> services. You know where you live in the Bay Area. I spent a lot of time out there, were based in Palo Alto and use a vortex that unique that sometimes I think way think that that's where all the action is. You come to London and you see all these startups. Every business is becoming a software company. And you know, we don't in Silicon Valley in America have a monopoly on innovation anymore, >> not even close. So there's a lot of great innovation all over Europe. Uh, here in the U K. All the way to Northern Europe, Doc, uh, Paris Way we see it across the board. So >> So what are people doing? They building new cloud native APS in the public loud. Are they doing a lifted shift and trying to get more agility out of those traditional APs? What's the landscape? Looks like? >> It's ah, combination of the two. The startup organizations, of course, is starting with no legacy. There's nothing to my great and they are building cloud native and they're doing so far, >> we have no I d >> no. Yeah, technically, before nine years, four hundred on eBay test migrations. But that's the only hardware for the museum. Exactly the larger organizations. They have huge volumes of legacy infrastructure, some of it dating back to the seventies. In the case of financial institutions or public sector, then all of that is an opportunity to modernize, and not just for the agility and innovation but in some cases just to reduce risk. There is huge business risk in these old, untouched, dusty, cobweb ridden servers that nobody understands anymore. And there's a really opportunity to move that to the public cloud, reduce and remove that risk. And while you're there, take advantage of the new technologies and innovative deliver a better service to you or in consumer whoever that may be >> so prik uber, Netease and micro services, even though containers have been around for a while. But the modern doctors ascendancy. You know why? To K was the year of the decade of modernization. It was like four or five years leading up to y two K at some I T shop said, Okay, we're going to modernize, but but none of these micro services existed, so it really was. It was about dates, maybe some application portfolio rationalization. What's different today that I could take those apse that were written in the seventies with a lot of custom code? How am I able to modernize, though >> I think it's the maturity of the services. You look at something a platform like Amazon. There's one hundred twenty hundred thirty, or Mohr. It grows almost every week. Building blocks primitives, the Amazon are providing, and its a rating on it. At an incredible rate on DH, there's almost a service for everything. And when you think they've run out of services to introduce, a new services is created. And, you know, we talked about micro services. They introduced Lambda back in two thousand fourteen, which was there. Serve Elice environment driving event based micro services architectures, and it's ahead of the game. It's ahead of the curve. It's causing people to think very differently about what's even possible from a night perspective. And there's no way. In most organizations, you, Khun, build that kind of infrastructure on that kind of platform that is build and costs you on a Microsoft microsecond basis. I mean, it's it's >> incredible. It was amazing. I remember the first virtual machine. It would be anywhere that I saw spun up like, Wow, this is going to change the world. And then the cloud comes along like a while. This is going to change the world. And now survivalists. I don't even have to deploy servers anymore. It's side by Amazon >> way. See this? Even even in some of the more traditional organizations we we worked with in the UK and in Germany and France and elsewhere, you don't even need to be looking at service. Just the ability toe programmatically spin up a virtual machine without a human touching anything. That's incredible to some organizations, right? They're used to it, taking six months to provision of infrastructure to deploy an application. Now they can click a button, and by the time they've made a cup of coffee, it's it's up and running, and it's It changes the way people >> think So much Talk about Cloud Region signal effects. What's the partnership like between you two and what's your partnership like with eight of us? >> Um, on the cloud reach side, we went through an extensive evaluation by cloud reach, and over several months they evaluated all the alternatives on the market and ended up selecting us to be their standard for their many service provider business. It's We're super excited about that. On the go for it, we're rolling that out with them there. Current customer based on DH. We were hoping that, uh, using signal effects, that cloud reach that will help them be the point of spear on all cloud native. You know, in their marketplaces, they go pursue other customers, so it's pretty excited about. >> So it's not a pressure release deal, not a Barney deal. Like we like to say that >> they're up there, They're a paying customer. And, you know, I made a big bet on signal effects going forward. >> So why the choice to go with manage service provider? You have You could have built it yourself and take us through that. >> Yeah. I mean, the nature of the business we're in is very much predicated on the fact that you don't build it yourself. You know, you look at the market and if somebody is already doing it well and provides excellent service as a commodity, you use it. We've been in the MSP space since round about twenty ten very soon after the the company was was founded, and we know it pretty well. We have a large customer base. We are one of the top tier MSP for along the major cloud vendors in the world, lots of large organizations. However, as we look to refresh our tooling with a view on Maura, an application centric approach, which is what all of our customers want and expect a CZ we look to micro services and the very latest platforms and technologies he's being released by the hyper scale cloud vendors. We recognize the need for a newer, more modern tooling on DH. After a thorough evaluation, a CZ mark says signal effects came out on top. Why is that? Partly it's the cloud native element. You know, some of that sounds a little bit like a marketing buzzword, but in reality, what it means is the company was founded relatively recently and as a result, was geared towards modern technology. So out of the box they support doctor, they support containers, they understand, and they're orchestrated around micro services. It deals with scale on volume, and we we want to low test things in a big way. We only serve large scale and surprise customers. And they are going to throw tens of thousands of containers on micro services at their tooling, and it has to be able to track tto handle that massive volume of transactions. >> It's a complicated picture, actually. You know, sometimes micro services aren't so micro. Yes, and you've got to secure all these containers. Got spinning up of'Em is easy. >> Well, >> you see multiples. So how do you guys deal with that? I mean, you're obviously experts at it, but But give us the sales pitch >> on. Yeah. So I think you kind of you covered it earlier with, You know, all these great new technology with introduction of micro services. I mean, developers in our writing it the running it, they're pushing code directly into production environment. You know, you went from releasing code once or twice a year, a few years back now toe several releases and you know your people lifting shift. They're starting with a few micro services. Someone we're getting up into the hundreds, even thousands in our most advanced deployments. It it it ends up being worth a situation Where Alright, all this innovation is great, but it also introduces a ton of complexity. And based on the way we've architect of our system, really time streaming like within seconds, you're going to need to see it, to react to it, whatever the use cases. And that's what differentiates signal FX is this massively scalable streaming architect we built for from a Metrix platform standpoint and then from an Eastern West standpoint for your from your custom code are Micro Services, a PM solution on top of that to go help measure what those transactions air how they're performing across the entire complex environment. So we feel like we're just purpose built for today to help in the lift and shift crowd and or for the more advanced customers, they're intothe point dozens, if not hundreds of micro services. >> Tell me more about this metrics platform you mentioned a couple times. What is that all about? >> Well, we start with essentially, you know, the three big pillars are logs, metrics and eight p. M. And you know, our company was found it. We have deep roots. Back in the two thousand seven ranges, our founders were you know, they built the monitoring stack at Facebook and so had several years, you know, kind of earning and learning that secret. You know, in the early days, they didn't call it Dev Ops. Back then they called it move fast, break things, didn't call >> it. They didn't call it >> a micro services. I mean, and then twenty, twenty, thirteen, early, two thousand fourteen. That's when the founders got together and started. The company is also the same time frame. Doctor came out. Were just purpose built for this for this environment. >> Final thoughts. Yeah. Thie event where you guys were headed. Maybe little road map, if you could. >> The event has been incredible. Every year it gets a little bit bigger. It gets a little bit more exciting. There's, ah, bigger range of organizations, different industries. And it changes a little bit over time. This year, financial services has been particularly of interest for us, but this event is a lot of large large banks, investment houses, those kind of companies here on DH. That's been really exciting for us. I think trend I'm most excited about is really around machine learning. Amazon talked about it in the keynote this morning and democratization of very, very complex technology bring it to the masses is a as a manage service that can be provisioned in minutes and seconds. And to me that something that's that's really exciting and using the signal FX platform, we're now in a position to provide manage service wrappers around the machine learning based solutions that we build for our >> customers. Yeah, the financial services. Interesting. Back in two thousand nine when you started, a lot of the banks in New York thought they could scale and compete essentially with KWS >> world. The world changes very quickly. Absolutely >> final thoughts for you. >> Yeah, I think they think we're moving past that point. You know, even the later adopters. I think we're moving past that point and look at that name there getting pressure from the startup community, whether it's intact or or any industry's gonna have that type of pressure. You talked about that y two k moment. I think in any vertical out there, it's that you know those cloud native type companies the companies are becoming software companies were going toe transform yourself or you're going to have some pressure from the start up going forward. We're >> guys. I'm thrilled that you could make time to come in the queue. Thank you. Thank you. Thanks for having us. All right. Keep it right there. But it is. Dave Alonso will be back with our next guests right after this short break. You watching the Cube from London? Eight of US Summit right back.

>> live from Boston, Massachusetts. It's the queue covering your red hat some twenty nineteen lots. You buy bread hat. >> We'LL come back. Live here on the Cube as we continue with the coverage here in Boston, Massachusetts at the Boston Convention and Exposition Center had Summit two thousand nineteen stew Minimum. John Wall's a big keynote night, By the way, we're looking forward to that. We have a preview of that coming up in our next segment. Also walled wall interviews tomorrow morning from a number of our keynote presenters tonight. But right now we're joined by Gunnar Hellickson, whose director product management for rela Red hat. Gunnar. Nice to see you, sir. Good to see you And Andrew. He cocks Whose director Product Management of insights at Red Hat. Andrew, how are you doing today? >> Doing great. Happy to be here. >> Show off to a good start for you guys. Everything good to go? >> Yeah, it's been great. Uh, I got a great response from customers. Great response from analysts. There was real excited about the really >> Andrew. Yeah, we've had overflow it. All of our sessions on its insights, the hosted service. It's also nice to go alive and not get any >> pages that it's all good there, right? Yeah. So on the rail laid side. Big announcement today, right? It's gone public now available. Ah, lot of excitement. A lot of buzz around that, and insights has been added to that. So what is that doing now for your kind of your your suite of services and what you are now concerned? Sure. Absolute more about than you were yesterday. Well, >> I think one of the benefits we've had and making this changes it can create a virtuous loop. So insights as a service works by looking at the data that we have from running environment and seeing what is successful in what is not successful. So by having a smaller group of customers were would deliver the service using a good experience, but has a number of customers increases. That means we can deliver more value because we have a better understanding of what the world looks so for us, even though we've had a really great growth rate, being able to accelerate that by putting it inside of the rail subscription means we're gonna have access even more opportunities. Teo, look. Att Customer data find new insights and deliver even more value to them. >> So, Gunnar, you know, analytics is a piece that I'm hoping you can explain to our audience some of the some of the new pieces. Yeah, that that should be looking at. >> Yeah, sure. So So, with the insights tool down available to rent enterprise, the next customers they are getting a sentry said, there's there's a virtuous loop right where the more people that use it, the smarter the system gets and the benefit for the end user is now they get. I like to think of it is coaching so often there are security fixes, their opportunities for performance tuning. There's configuration fixes you could make, which may not be immediately obvious unless you've read through all the manuals right on DSO. How much better is it that Andrew Service can now come into a real a real customer and say, Hey, have you noticed that you might want to make this performance fix or hey, you might have forgotten this. So security fixed and it really makes the day to day life for the administrator much easier on also allows them to scale and manage many more systems much more efficiently. >> Yeah, I'm curious. You know, there's certain people. Was like, Wait, no, I understand my environment. You know, I you know, am I up for sharing what I'm doing versus everyone else? What's that? Feedback? You know, you've been what are some of the kind of misperceptions you want to make sure people understand? You >> know >> what it is and what it isn't >> a customer. Talk to you too. Phrases a very funny way. He's like, Well, >> I don't need this from my team. Might you know those guys right out >> of my level? I think, actually, our customers, they feel the scale that they have to operate on. So they're managing a lot more stuff. But I think the real pressure, his line of business is expecting things faster. So if they can't turn around, then they're lined the business. They're going to go get technologies somewhere else. And so, for our customers, the ability to automate pieces of their work flow, including ensuring it too safe configuration. It's optimized. That's a really key things I've never actually heard someone say. I know what I'm. Why did once have one person say they know what they're doing? They didn't need our help. But I think everyone else, they they get the value of analytics. >> You brought up the word, you know, scale. It's, You know, I worked in operations for six years in the group I had is like, Okay, next quarter, next year, you're gonna have more to do or less to do. Are you going? More or less? Resource is we understand what the answer is for most of those. So if I can of automation, if I can't have you no smart tooling today, I'm not going to able to keep up. You know, we talk about at the core of digital transformation is data needs to drive what we're doing. Otherwise, you know you're going to be left behind. >> Yeah. Yeah, that's right. And so and so how graded it is to finally have. You know, for fifteen years we've been getting support. Ticket's been reading knowledge based articles. We've got all this technical expertise on this architectural expertise, and that's not always easy to deliver to customers, right? It's It's still, you know, we're self our company, so we could deliver them software. But it's that additional coaching, Ben, additional expertise is the kind of difficult to deliver without having a vehicle like insights available. >> So how does it in terms of let's, like, really, um, roll out the new product? Everyone's You know, it's hopefully being well, not. Hopefully it is being used right now, and now you start seeing hiccups in the system. You see some speed bumps along the way. What are you seeing holistically? That an individual user is not? Or what's the value, too, to gathering this concensus and providing Mia's maybe just a single user with an insight into my situation? >> Yeah, that's the way I'd like to think about it is if you're a customer and you have a critical issue, causes downtime and impact your business, that's that's really terrible, and you're probably gonna learn from that. You're not going to do the same thing again, at least hopefully. But the customer next door or your competitors next or partner next door. They don't generate that experience or learned from that experience, so I think of insights, his way of knowledge recapture. So something happens once in one place. The system acts as a hub for that information, so once we see that we can capture the information that was discovered at one customer site, and we can proactively alert all of our customers to avoid that scenario. So it really lets us re use knowledge that we're generating. It's Gunnar said. This expertise we're generating inside the company were already doing all these activities, but it lets us recapture that energy and sick it back out to the rest of our customers much more efficiently than we ever could before. >> And you can and you could deal what you deal went on one. So if I if I'm a unique or have a unique problem, you could help me identify that, then you keep it in a reservoir. Basically, that could be tapped into when other instances occur. And you could see we, you know, this happened. This particular situation occurred in this situation and boom. Here's the cause. Here's the proper. Here's the fix >> on everything we do with insights is totally so. We learned from different experiences, but it's totally Taylor to each environment, So it's not just like a whole bunch of knowledge based articles. It looks at exact configuration for each customer, not only verifies that they're really going to hit the issue, Not just they, you know they might or something, but they're really going to hit it, but also generates automation to fix the issue. So we generate custom Ansel playbooks, which is an automation language that red hat obviously is invested in, and our customers and community love that is specific to their environment. So they could go from discovery to fix in the safest and fastest way possible. >> Yeah, you went. I was. You know, I'm hearing automation and, of course, immediately think about answerable there. So see, it seems there is that tight integration. They just play across the other. How does that dynamic >> work? Sure, So insights is tightly integrated in the sense of think of, answerable his arms and legs like there. They can go do things for you. But that doesn't come with a brain, necessarily the brain is our customers, right? So instable, So easy to use that you can put in the hands of knowledge experts inside of different companies, and they can automate part of their job. Their TVs. That's fantastic. What we're doing with insights, though they say got the red hat brain as well, though And so we're going to connect the red at breaking in. And so we're using tools like answerable to help collect the information that we need to analyze environment and then tools like answerable to go resolve the issues once we've identified what's there? So we see there's is totally complementary pieces of the portfolio. >> So, God, we've been talking about customers about you on the inside. What are you getting out of this? Ultimately, in terms of product improvement and whatever it orations that you're going to bring on because of these insights that your gathering, how soon? You kind of hope you roll it out. Thanks. Fine. Okay. Yeah, that's right. Yeah, yeah, yeah, yeah. Hope you don't get much from Andrew, but it's inevitable that, you know, there's going to be something that needs attention. >> Well, I mean, this is just part and parcel of regular product management practice, right? I mean, you look at your support tickets. You look at what customers are worried about. You look at what? The escalation czar, and that helps you. I think one change that we have gone through is thie. Analysis of all that activity has been largely anecdotal. like always remember the last and loudest person it was yelling at you, right? And this on tools like tools like insights allow us to be much more data driven as we're making different product management decisions. All >> right. Um, yes. So what should we be looking forward, Teo, give us a little bit of where things go from here? >> Sure. No good s o. You know, I think we'LL see the service generally. As I said, as we get more people connected, the service itself increases in quality in terms of recommendations in the breath of recommendations were also started to do some interesting worked. Open it up to partners. So so far, it's really been a red hat oriented Here's red hats knowledge. But it turns out that our partners want our stuff, their stuff, to run successfully on top of our platforms. That's a huge value for them. So, for example, way have nine new recommendations that will provide for sequel server when running on rally that we generated in partnership with Microsoft. And that's certainly the type of thing that we want to keep investing Maura and I think is really impactful for Custer. Um, because they see vendors actually working together to create a solution for them instead of us, just each doing our own thing in different ways. So that's one change that we're really excited about. >> Going forward. Yeah. You know, I think focusing on the focusing on the coaching for specific workloads is going to be really important. I mean, optimizing the operative system is great. I mean, your job rating system nor Adela fixing the operating system. But customers really had The opening system is an instrumental step towards actually operating something that that is critical of customers business. And so, to the extent that we can connect infrastructure providers, IVs and all the entire partner ecosystem, together with the indigenous operating system rules, we can give customers really very nice of you in a very nice set of, well, coaching on on their full stack of the planet. >> And that's the insight they're all looking for, right? Literally what they're looking for, gentlemen. Thank you. Thank you. The time we appreciate, uh, your time here today and good luck with continued pack sessions. That goes well for you. Both appreciate back with more where it read. Had summit where in Boston. And you are watching the Cube >> live from Boston, Massachusetts. It's the queue covering your red. Have some twenty nineteen. You buy bread? >> No, that on the ground. Get back a lot of commotion.

>> live from Boston, Massachusetts. It's the you covering your red hat. Some twenty nineteen rots. You buy bread hat. >> Well, good afternoon. Welcome back here on the Cube as we continue our coverage of the Red Hat Summit and you know, every once in a while you come across one of these fascinating topics. It's what's doing I get so excited about when we do the Cube interviews is that you never know where >> you're >> going to go, the direction you're going to take. And I think this next interview has been a fit into one of those wow interviews for you at home. Along was to minimum. I am John Walls, and we're joined by Dr Ellen Grant, who was the director of the fetal neo NATO Neuroimaging and Developmental Science Center of Boston Children's Hospital. So far, so good, right? And the professor, Radiology and pediatrics at the Harvard Medical School's Dr Grant. Thank you for joining us here on the Cube and Dr Rudolph Pienaar, who is the technical director at the F n N D. S. C. And an instructor of radiology at the Harvard Medical School. So Dr Rudolph Pienaar, thank you for joining us as well. Thank you very much. All right. Good. So we're talking about what? The Chris Project, which was technically based. Project Boston Children's Hospital. I'm going to let you take from their doctor Grant. If you would just talk about the genesis of this program, the project, what its goal, wass And now how it's been carried out. And then we'LL bring in Dr PNR after that. So if you would place >> sure, it's so The goal of the Chris Project was to bring innovated imaging, announces to the bedside to the front end where clinicians are not like high are working all the time but aren't sophisticated enough or don't have enough memory to remember how to do, you know, line code in Lenox. So this is where initially started when I was reading clinical studies and I wanted to run a complex analysis, but there was no way to do it easily. I'd have tio call up someone to log into a different computer, bring the images over again lots of conflict steps to run that analysis, and even to do any of these analysis, you have to download the program set up your environment again. Many many steps, said someone. As a physician, I would rather deal with the interpretation and understanding the meaning of those images. Then all that infrastructure steps to bring it together. So that was the genesis of Chris's trying to have a simple Windows point and click way for a physician such as myself, to be able to rapidly do something interesting and then able to show it to a clinician in a conference or in the at the bedside >> and who's working on it, then, I mean, who was supplying what kind of manpower, If you will root off of the project >> kind of in the beginning, I would say maybe one way to characterize it is that we wanted to bring this research software, which lives mostly online, ex onto a Windows world, right? So the people developing that software researchers or computational researchers who do a lot of amazing stuff with image processing. But those tools just never make it really from the research lab outside of that. And one of the reasons is because someone like Ellen might not ever want to fire paternal and typing these commands. So people working on it are all this huge population of researchers making these tools on what we try to do. What I try to help with, How do we get those tools really easily usable in excess of one and, you know, to make a difference? Obviously. So that was a genesis. I was kind of need that we had in the beginning, so it started out, really, as a bunch of scrips, shell scripts, you slight a type of couple stuff, but not so many things on gradually, with time, we try to move to the Web, and then it began to grow and then kind of from the Web stretching to the cloud. And that's kind of the trajectory in the natural. As each step moved along, more and more people kind of came in to play. >> Dr Grant, I think back, you know, I work for a very large storage company and member object storage was going to transform because we have the giant files. We need to be able to store them and manage them and hold them up. But let's talk about the patient side of things. What does this really mean? You know, we had a talk about order of magnitude that cloud can make things faster and easier. But what? What does this mean to patient care? Quality service? >> Well, I think what it means or the goal for patient care is really getting to specialized medicine or individualized medicine on to be able to not just rely on my memory as to what a normal or abnormal images or the patients I may have seen just in my institution. But can we pull together all the knowledge across multiple institutions throughout the country and use more rigorous data announces to support my memory? So I want to have these big bridal in front lobes that air there, the cloud that helped me remember things into tidies connections and not have to remind just rely on my visual gestalt memory, which is obviously going to have some flaws in it. So and if I've never seen a specific disorder, say, for example, at my institution, if they've seen it at other institutions who run these comparisons all of sudden, I made be aware of a new treatment that otherwise I may not have known about >> All right, so one of my understanding is this is tied into the mass open cloud which I've had the pleasure of talking on the program at another show back here in Boston. Talk about a little bit about you know how this is enable I mean massive amounts of data you need to make sure you get that. You know the right data and it's valuable information and to the right people, and it gets updated all the time, so give us a little bit of the inner workings. >> Exactly. So thie inner workings, That's it can be a pretty big story, but kind of the short >> story time Theo Short >> story is that if we can get data in one place, and not just from one institution, from many places, that we can start to do things that are not really possible otherwise so, that's kind of the grand vision. So we're moving along those steps on the mass Open cloud for us makes perfect sense because it's there's a academic linked to Boston University. And then there's thie, Red Hat, being one of the academic sponsors as well in that for this kind of synergy that came together really almost perfectly at the right time, as the cloud was developing as where that was moving in it as we were trying to move to the cloud. It just began to link all together. And that's very much how we got there at the moment on what we're trying to do, which is get data so that we can cause medicine. Really, it's amazing to me. In some ways there's all these amazing devices, but computational e medicine lag so far behind the rest of the industry. There's so little integration. There's so little advanced processing going on. There's so much you can do with so little effort, you could do so much. So that's part of the >> vision as well. So help me out here a little bit, Yeah, I mean, maybe it before and after. Let's look at the situation may be clinically speaking here, where a finding or a revelation that you developed is now possible where it wasn't before and kind of what those consequences might have been. And then maybe, how the result has changed now. So maybe that would help paint up a practical picture of what we're talking about. >> I could use one example we're working on, but we haven't got fully to the clouds. All of these things are in their infancy because we still have to deal with the encryption part, which is a work in progress. But for example, we have mind our clinical databases to get examples of normal images and using that I can run comparisons of a case. It comes up to say whether this looks normal or abnormal sweat flags. The condition is to whether it's normal or abnormal, and that helps when there's trainees are people, not is experienced in reading those kinds of images. So again we're at the very beginnings of this. It's one set of pictures. There's many sets of pictures that we get, so there's a long road to get to fully female type are characterized anyone brain. But we're starting at the beginning those steps to very to digitally characterize each brain so we can then start to run. Comparisons against large libraries of other normals are large libraries of genetic disorders and start to match them up. And >> this is insecure. You working in fetal neural imaging as well. So you're saying you could take a an image of ah baby in a mother's womb and many hundreds thousands, whatever it is and you developed this basically a catalogue of what a healthy brain might look like. And now you're offering an opportunity to take a image here on early May of twenty nineteen. And compared to that catalogue, look and determine whether might be anabel normality that otherwise could have been spotted before. >> Correct and put a number to that in terms of a similarity value our probability values so that it's not just Mia's a collision, say Well, I think it's a little abnormal because it is hard to interpret that in terms of how severe is the spectrum of normal. How how? Sure you. So we put all these dated together. We can start to get more predictive value because we couldn't follow more kids and understand if it's that a a sima that too similar what's most likely disorder? What's the best treatment? So it gives you better FINA typing of the disorders that appear early and fetal life, some of which are linked to we think he treated, say, for example, with upcoming gene therapies and other nutritional intervention so we could do this characterization early on. We hope we can identify early therapies that our target to targeted to the abnormalities we detect. >> So intervene well ahead of time. Absolutely. >> I don't know. The other thing is, I mean Ellen has often times said how many images she looks at in the day on other radiologist, and it's it's amazing. It's she said, the number hundred thousand one point so you can imagine the human fatigue, right? So it Matt, imagine if you could do a quick pre processing on just flag ones that really are abnormal by you know they could be grossly abnormal. But at least let's get those on the top of the queue when you can look at it when you are much more able to, you know, think, think, think these things through. So there's one good reason of having these things sitting on an automated system. Stay out of the cloud over it might be >> Where are we with the roll out of this? This and kind of expansion toe, maybe other partners. >> So a lot of stuff has been happening over the last year. I mean, the the entire platform is still, I would say, somewhat prototypical, but we have a ll the pipelines kind of connected, so data can flow from a place like the hospital flowed to the cloud. Of course, this is all you know, protected and encrypted on the cloud weaken Do kind of weaken. Do any analysis we want to do Provided the analysis already exists, we can get the results back. Two definition we have the interface is the weapon to faces built their growing. So you can at this point, almost run the entire system without ever touching a command line. A year ago, it was partially there. A year ago, you had to use a command line. Now you don't have to. Next year will be even more streamlined. So this is the way it's moving right now and was great for me personally. About the cloud as well is that it's not just here in Boston where you, Khun benefit from using these technologies, you know, for the price of a cellphone on DH cell signal. You can use this kind of technology anywhere. You could be in the bush in Africa for argument's sake, and you can have access to these libraries of databases imaging that might exist. You, khun compare Images are collected wherever it might be just for the price of connecting to the Internet. >> You just need a broadband connection >> just right. Just exactly. >> Sometimes when you think about again about you know, we've talked about mobile technology five g coming on as it is here in the U. S. Rural health care leveling that and Third World, I was thinking more along the lines of here in the States and with some memories that just don't have access to the kind of, like, obviously platinum carry you get here in the Boston area. But all those possibilities would exist or could exist based on the findings that you're getting right now with Chris Project. So >> where does the Chris project go from here? >> Well, what we'd like to do is get more hospitals on board, uh, thinking pediatrics, we have a lot of challenge because there are so many different rare disorders that it's hard to study any one of them from one hospital. So we have to work together. There's been some effort to bring together some genetic databases, but we really need to being also the imaging bait databases together. So hopefully we can start to get a consortium of some of the pediatric hospitals working together. We need that also because normal for normal, you need to know the gender, the age, the thie ethnicity. You know, so many demographics that are nice to characterize what normal is. So if we all work together, we can also get a better idea of what is normal. What is normal variants. And there's a lot of other projects that are funded by N. H. Building up some of those databases as well, too. But we could put him into all into one place where we can actually now query on that. Then we could start to really do precision medicine. >> And the other thing, which we definitely are working on and I want to do, is build a community of developers around this platform because, you know, there's no way our team can write all of these tools. No, no, no, we want to. But we want everyone else who wants to make these tools very easily hop onto this platform. And that's very important to us because it's so much easier to develop to christen it just about the Amazon. There's almost no comparison. How much easier >> we'Ll Definitely theme, we hear echoing throughout Red Hat summit here is that Does that tie into, like, the open shift community? Or, you know, what is the intersection with red hat? >> It definitely does, because this is kind of the age of continue ization, which makes so many things so much easier on DH. This platform that we've developed is all about container ization. So we want to have medical by medical or any kind of scientific developers get onto that container ization idea because when they do that and it's not that hard to do. But when you do that, then suddenly you can have your your analysis run almost anywhere. >> And that's an important part in medicine, because I run the same analysis on different computers, get different results. So the container ization concept, I think, is something that we've been after, which is a reproduce ability that anybody can run it along there, use the same container we know we're going. Same result. And that is >> critical. Yes, especially with what you're doing right, you have to have that one hundred percent certainty. Yep. Standardisation goes along, Ray. Sort of fascinating stuff. Thank you both for joining us. And good luck. You're an exciting phase, that's for sure. And we wish you all the best going forward here. Thank you so much. Thank you both. Back with more from Boston. You're watching Red Hat Summit coverage live here on the Q t.