We had this lightning talk available. The speaker didn't turn up. He had some issues.  So, we are... So, Kunal will be speaking about a tool called DataSplite. It's an open source intelligence framework. Okay, so, over to you Kunal. Hello. Good evening guys. Audible? Yeah. Hello. Yeah. What is it? Yeah. Okay. Hello. Peter? Yeah. Like this. Yeah. So, here I'm to present DataSplite, an open source intelligence tool. So, we are the main three contributors to DataSplite. Right? So, what is DataSplite? That's going to make noise on a record. Okay. Okay. Better now. Okay. So, it's an automated OSIN framework. So, basically we have four major modules called domain, email, username and IP. So, you feed in any of these things like domain, test.com, email ID and IP address or username. And then it fetches these information from a lot of data sources that we have configured behind all the modules. It's completely written in Python and currently it runs either on a console or you can export the output that's there on a JSON format. So, one of the major things for... The major use case for this would be a pen test probably because let's say for a domain you get a list of subdomains. You might be interested in finding which of those domains might be vulnerable. Right? So, why DataSplite? So, we have a lot of information that's available open source. Something like username, passwords that might be accidentally posted to GitHub. Then address, email ID, phone numbers, credentials. All this information might be available accidentally or on purpose sometimes. Right? So, real time. So, as you can see these are some screenshots of how the information is available. If you do a Google search for, let's say a site-paste pen, you'll find some database leaks, you know, credentials that someone's done and then posted them online. Then you can either do an index of search, you know, use those Google search terms to find open indexes of different websites. Then finding credentials on GitHub. So, finding credentials on GitHub that have been, you know, accidentally posted. Then, so, as I mentioned, we have four main components called domain OSINT. So, these are the basically the four main scripts that you use to actually trigger the various data sources. Domain OSINT, email OSINT, IP OSINT and username OSINT.  Active modules, actually passing that information to active attack modules. Then CV, data aggregation, the CV, IDs that you get from modules and then auto-generated reports. So, as I mentioned, we have multiple data sources. So, as you can see from domain, we have about these about 10-15 odd data sources. So, this is how the data flows. From domain, you can get a lot of email IDs from the email harvester module. That gets passed to email module that again can fetch a lot of information from these data sources. So, it gets, let's say, enumerated usernames. So, from those usernames, you can pass it down to get details, profile pictures, hashtags, the conversation that the user has been posting. And similarly, from a domain, you can get IP addresses, which you can actually pass down to find out which all ports are open and the services that are accessible. So, how do you set it up? So, we have two modes. One is a manual mode, which includes a Git clone, which is used to set up a standalone mode as a standalone tool in itself. And the second way, so, how do you do it? You do a Git clone, install the requirements. There's a config.py that holds all your API keys because these data sources that we have configured, most of them might require an API key for you to configure to actually use them. Then, we have a structured, structured, you know, folders basically holding each of your scripts. So, as you can see on the right, we have folders called domain, email, IP, and then username. So, the domain has scripts specific to the domain OSINT. And then, we also support PIP recently. So, it can be installed as a Python package and be used as a library in your projects. Then, we also have a Docker implementation. You just do a Docker pull and you have data splurter running. Then, how do you write modules? It's been recently converted to a framework. So, there's a single file that you call a template.py in each folder. It has three major functions, a banner, a main, and an output. So, banner displays some text about the module. Main does the main logic behind, you know, the module. Some, you know, the processing that needs to be done. And finally, the data returned from the main is actually what gets passed to the output for printing on console in a, you know, human readable way. Then, so, we have a very nice documentation, a very step-by-step documentation on how to set things up in both manual and automated ways. And then, how to write in your own modules. And then, the work in progress. Currently, we support JSON. We are planning to support HTML reports and e-mail text files that can be, you know, passed to another tools, like e-mails and subdomain lists. Okay, so, the demo. Just to add to that, the documentation also has step-by-step, you know, guidelines on how to generate the API keys, how to sign up for the different services that we use here. Yeah. It tells you exactly how, which things you have to copy and put back into quantum.py. So, basically, the sites you need to visit, how to sign up for them, where to get an API key and paste it in the config.py. Yeah. So, so, as I... Domain. Domain. No, just fine. Okay. So, let's say we have an IP address. You just pass it to the IP OS in framework. You can see it first searches for Shodan. So, Shodan has no information, then virus total, whether or not this IP address was listed as a, you know, compromise domain, and then some who has information to get the ASN, the Autonomous System number to actually find out more related IP ranges for this. So, before we go ahead, like, suppose if you have got an e-mail address, okay, you're trying to see someone and you've got an e-mail address, what kind of information would you like to collect about them? Any pointers? Yeah. Anything else you would like to, like, find out about a person? You've got an e-mail ID of a person. Yeah. Yeah. Yeah. Good. Sorry? What was that? True name. True name. Good. Exactly. Yeah. So, what we're trying to do with Datasploit is, you know, it's no rocket science. We're just the things which we'll do manually, going on one site and finding out information. We're just collecting bunch of such sites, calling those APIs, getting it sorted, like, it goes in an automated manner. There is a difference which Datasploit brings in comparison to other tools, because a lot of other tools, you know, they... Nice. That's funny. Yeah. So, a lot of other tools, you know, they are really good, but one thing which I really miss in other tools is, like, they do not have an automated approach. You have to manually pick and use things. Sometimes you don't really know what modules you should use. I mean, for a person who do not do ocean on a daily basis, it becomes very difficult. Yeah. So, that's the problem we're trying to solve here. We're trying to do everything in an automated manner. So, even if you do not know anything about ocean, just configure your config.py, and it will do the things for you. Yeah.  So, as he mentioned, so let's say you get a domain test.com, and you need to find out what all information is available. We have all this information. Punk, spider, the DNS records that are there. The email address harvested related to that domain. These email addresses you might be interested. So, let's say you find the combination of first name, last name. So, you can figure out what kind of format the organization uses to actually name their employees. Then you can, you know, actually brute force them. So, after this, then you get... So, basically, where all this domain has been mentioned on GitHub. So, let's say files where, you know, they might be username passwords or AWS keys, let's say, suppose. So, you can see the files, the specific file where this domain name was seen. And then some page links, then the paste bin. So, as you can see, for test.com, you can have something like an email ID and then a password. So, probably this email ID password will mostly work on different websites that you find related to this email ID. So, finding things on GitHub and Pastebin is something which I always do in my pen test, you know? So, whenever I'm doing a pen test, I come across any domain name. I always make sure that I search these things on GitHub and Pastebin. You never know.  So, you don't even need to explore the vulnerability. It gets pretty easy for me. So, yeah. Then, so that domain then gets searched on Shodan for, you know, the ports that are open, as you can see. So, you might find something like open... an SSH open on an IP address related to test.com. So, that might be exploitable. And then all that information, AD443, what services are running, what's the geolocation for that. And then, so that's like a lot of information. Then, the subdomains that are there. As I mentioned, this might be interesting for a pen tester guy to actually find subdomains that are there and might be exploitable. Then... So, not only pen tester, but even if you're running a company, you are managing something for a company. You may check your parameter. Like, sometimes, what happens is, there are some legacy subdomains like abc.xpig.com, and you are not aware of them. And so, most of the legacy code is very much vulnerable to things. And it gets very easy to pop up a shell out of it. You know, so it's probably worth the while checking all the domains which are lying out. Yes. And then, we also saw that domain for any WikiLeaks documents that are related to that domain. Then, ZoomI, similar to Shodan, gets all that IP-related information, the services that are running, the header information that gets returned to those IPs. Then, the next module we have is e-mail... It's a wrong one. Pause the username. Yeah. So, let's say a username. You get a username. So, Keybase is a very good source of information where, you know, a user actually has to verify his own accounts. So, the information you get here is actually the profiles that it belongs to the same user. So, you won't find data that is mismatching or, let's say, false positives, right? So, here, this might be a very good information to find out all that accounts that are listed for this user. So, let's say you found this username previously on, let's say, a paste bin and has a username password combination in a paste bin document. You can go here on these sites and try that out. So, obviously, that, you know, opens up a very good opportunity for you. And another thing which this could be used is, like, a lot of people, you know, use devices and they leave their device name as they are.  So, as I mentioned, we also allow you to... Sorry, yeah, question. So, it's like we're not grabbing from anywhere else. The person generally verifies their devices on Keybase. So, the Keybase have an open API. You don't even need authentication for that. So, it's pretty easy to get it out. Sure. Yeah. Okay, so, yeah. Yeah. Yeah, that's a valid thing. I mean, so, as of now, we are completely relying on information. That's... Which exists online. As of now, no. As of now, no. Because, you know, we thought of doing that, but it becomes really tricky to... Because we will have to do a lot of correlation. We have to do match images and stuff. Yeah. We... Yeah. Yeah, right now, we are making the best effort, but we are trying to work on those things. Yeah. Exactly. So, if you... Yeah. We will be coming on the roadmap. Those things are in the roadmap. So, you can schedule... You can schedule the things. Right now. Okay. No, we don't have. As of now. So, as I mentioned, we also support Datasploit as a library. So, let's say if you do a simple import Datasploit, you have it available to use in your own Python project. And let's say if you do a Datasploit, I'll just show a quick demo for it. The username. That's our main module for... Oh, sorry. User name. And then, let's say, the module that's in there is username underscore git scrape. Right. And then, we have a main function for each module that needs to be implemented. And then, you pass in the actual username. Let's say I'll pass in my colleagues. So, user typo. User... What's happened to your keyboard? I don't know. He messed it up. He just messed it up. Okay. So, he hasn't defined any API keys for it, but let's say if he had, you'll have that data returned to you in a native Python object, probably a dictionary, a list, whatever, you know, is relevant to that module. So, for git scrape, you'll probably find the repositories that the user have, and in those, you'll find the commits. So, you can find out which all are the most active, you know, repositories that the user contributes to, and probably in that, you can find something, you know, similar like a password username combination that might be there. Yeah. And then, the last one might be... So, similarly... So, rather than, you know, using the consolidated script called domain oscent or even email oscent, the individual modules themselves are callable. You can just say a Python domain, then the specific module that you need to call domain subdomains.py, and then just pass in the domain name that's there, you'll find all the specific subdomains that are there. Okay. So, for subdomain, right now, we are using DNS dumpster, we are using NetCraft, and we are using certificate transparency from Google. And we plan to introduce DNS walking right later on, but that's in the plan. Yeah, yeah. So, most of the APIs might have a throttling there. So, they obviously return, you know, rate limit exceeded, something like that. And here's this one script called emailoscent.py. Is that... No? Okay, I'm sorry. Sorry, was that your... So, we can't, but obviously we can, you know, get in touch with the, you know, specific... Yeah, exactly. So, about the emailoscent, this is what we do. Yeah. So, the very first thing, it will check for some basic things. For example, if you are running a phishing campaign, it will tell you whether it's a disposable email or not, whether this domain can receive emails or not. So, if you are trying to send emails, it will tell you those things. It will tell you search information from Clearbit. It will tell you a bunch of information about the person, the name, the tentative location, or the profile, or whatever things. So, as mentioned by you, for an email you get the true name that's there, the user names that are there. Then it goes to full contact. We are not relying on just one source. There are another source called full contact. We're using them. It tells you the name. It tells you the designation of the person, social profiles. We have got like 500 profiles which we check for, but we are trying to get more. And then Twitter, and it will download all the images from these respective places. What you can do is you can use these images to do Google reverse image search and stuff. So you can get more information. Then it goes and check on have I been pawned, whether this email ID was a part of a compromise or not. So as you see, my email ID was part of three compromises. So what you can do is you can go back to, you know, other places where you can get these database terms. You might get correct thread hashes or passwords. And then there might be chances that I'm using the same password somewhere else. So it gets an easy win. It checks for a page on other places. Right now my email is expired. So yeah. So that's probably what you were asking, right? Slide shares. When API send us a forbidden. Slides, any slides which I have published and associated subdomains for me. So this is the information which you are getting from email ID. I think that's it. That's what we have for the demonstration. We have Twitter account, World Data Despite, where we post in tweets and announcement about this. Yeah. The same feed goes into Facebook also. This is a small roadmap which we think of. We plan to, we are not lazy. We'll try to get this coded. It's like ad hoc tool. So you run it as in when you want. So probably you want to integrate it with automated tools. So you want, let's say, incremental change that's happening to find out the difference between a previous run and a next run, right? Yeah. Yeah. Yeah, we can. I mean, we can, what we can do, I mean, there's no point writing the same code for Maltico because anywhere we are writing in our tool. What we can do is we can write code which, which generates an output which could be directly used by Maltico. I mean, that, that will be a better way. Otherwise there's no point in writing the feed, right? Right. So yeah, we can, we can work on that lines. So far the tool has been covered on multiple places. But I don't want to brag about it right now. Yeah. What do you, how the, the point what, what I raised, what, what I wanted to raise is how you can contribute. You can test the tool. You can write blogs about tool. You can promote the tool. So now it's, since it's a framework, we encourage you to actually go through the framework that's there and actually implement the function.  We'll try to integrate it there. Yeah. So we are the core contributors. I'm Shubham. So now I'm Shubh Kunal and Newton is missing reason in the other room. And if you've got any questions. Yeah. Please show, shoot. That's it. Thanks.


Live from the Sands Convention Center, Las Vegas, Nevada, extracting the signal from the noise. It's theCUBE, covering HP Discover 2015, brought to you by HP. And now your host, Dave Vellante. Hi everybody, we're back, this is Dave Vellante. Dennis Dean is here with Jeff Chuck. And Dennis is the Vice President and the AGM of the Alcatel Lucent Relationship at HP. And Jeff is the Vice President of the Global HP Alliance at Alcatel Lucent. Gentlemen, welcome to theCUBE. Thank you. Dennis, let me start with you. So what's going on between HP and Alcatel? Could you describe the relationship? Absolutely, so it's a multi-year relationship. Basically HP has three roots markets with Alcatel Lucent. We are their preferred partner in terms of providing their IT services for them, which we do through our Enterprise Services Division. We also have a very strong technology partnership in terms of supplying them IT infrastructure platforms as Alcatel Lucent sell out towards their end telco customer base. And we also have a pretty interesting joint-coder market relationship. Yes, the joint-coder market's something that we've really been focusing a lot lately. And we've worked to get Alcatel Lucent products embedded into HP's portfolio. So HP OEM, some of our technology, and calls it distributed cloud networking. They also have just at Discover launched taking our high-end routers into their networking portfolio, as well as some of our optical products so that they can do data replication with HP storage. So you primarily sell to telcos, right? Primarily that's where Alcatel Lucent's heritage has been, is telco focused. And that's one of the real strengths of our relationship with HP, is HP obviously has the tremendous heritage in the enterprise marketplace. And that's an area that Alcatel Lucent wants to break into now. And so it's a natural fit for our two companies to really work together. And then is there another path as well for HP into telcos with things like NFV or? Absolutely, so you hit them now on the head. Now we see an emergency in the industry of a couple of sort of new megatrends. We have software-defined networking, we see cloud of course, you know, NFV. And what's actually happening is it's a real convergence between the traditional enterprise IT worlds and the traditional telco worlds. I think what we're seeing is that the telcos are getting more familiarized and they can see the value of enterprise IT infrastructure, X86 platforms and so forth. And at the same time, as HP becomes more relevant in these telco sectors, Alcatel Lucent also provides us with some additional technology capability to fill some gaps in our own portfolio. So what we've done is we've looked at not these two markets completely independently, but we've looked at them, what is our end-to-end offering as a joined up portfolio? And how can we best address both the enterprise IT market that it was a traditional HP space as well as the Alcatel Lucent telco traditional space too? We've certainly seen that there have been two worlds of IT and telecom and they truly are starting to converge more and more every day. Our portfolio, again, was based towards the telco marketplace, but the requirements that the telco had, we're starting to see become much more prevalent in the enterprise world as well. So when it comes to scalability, reliability, that was just table stakes within the telco world that's starting to really have a relevance within the enterprises world. Yeah, you're kind of serving client bases that are sort of birds of a feather in the sense of the complexity. So the enterprise customers, they're a mess. They got a zillion applications, they're siloed all over the place, their organizations are not talking to each other, they're different hardware and software and services, and the telcos, maybe even more so. I mean, I'm not an expert in that base, but there's a lot of heterogeneity. And then here they are, and everything's changing. They're competing now with Amazon and Netflix or sort of driving into their base. So can you sort of talk about some of the solutions that you guys have to solve those problems and where they fit in enterprise and where they fit in telco? Absolutely. So I think, I'll take the HP side. So I think what we've noticed is, as you mentioned before, the enterprises are becoming more like service providers.  So the way that their network architecture is actually constructed is very similar to a telco. It's just at a smaller scale. But in terms of their problems and the challenges that they face, their requirements in terms of latency, in terms of security, it almost starts looking like a real service provider. Similar, like you said, Amazon, Netflix. I mean, these are players which are now pushing out video, it's on demand, it's in the clouds. All of a sudden they're starting to look much more like a telco than actually an enterprise space. So what we've done is we've taken a good look at this and we've said, okay, we need some carrier-grade technologies to support HP's existing enterprise portfolio. So one of the key assets has been the high-end router from Alcatel Lucent. It's a 7750 service router we're really excited about. It's been positioned within the HP networking family of products and we will take that to market. The second part is the optical switch, the 1830 PSS from Alcatel Lucent. Super high speeds, very, very secure, speed of light, right? That's what the optics are all about, which is combined with our storage. So HP storage is already a great value proposition. Now we have the transportability to connect data centers at the speed of light together. So we're super excited about that. And then finally, we look at the application side and we're seeing some convergence in the communication. So video and voice. And what we've done there is we've taken Alcatel Lucent's rapport solution, which is based on their IMS application and we've pulled it together with our HP Helion Cloud. So the three assets are being launched here at Discover. We're really excited about it. And we see them being extremely relevant in the HP enterprise space. Absolutely, to continue on to Dennis's comments. With Alcatel Lucent, we've been helping our telco customers for years effectively deliver cloud services. If you look at something like IPTV, which we helped launch all around the world, that effectively really is a cloud service. And so the capabilities that we've had with those telco customers for years, when it comes to managing multiple points for a single user getting in and actually looking at the specific service of that user as opposed to a port, for example, the ability to rapidly turn up and equally as importantly turn off services. Those are things that we've been doing in the IPTV world for years. And working with HP, we can now leverage that capability that we have inherently within our portfolio and our areas of expertise and take that into the enterprise world and the cloud environment also. So, Jeff, let's unpack that a little bit. So you're talking about granularity of services and the ability to turn them on and off real time, essentially, what does that mean for your and customers and their monetization strategies? So if you take, for example, distributed cloud networking that HP uses today, if you think of your cell phone, when you flew out here, you didn't have to coordinate with your cell phone provider ahead of time to tell them, hey, I'm going to be in Las Vegas and when I get there, I'm going to need all these features, right? You came here, turned on your cell phone and it works. And that's effectively what DCN or Distributed Cloud Networking does in the data center as well. Is it's a policy based system so you can set up and say, okay, I need a new virtual machine. That virtual machine has a certain profile of characteristics. DCN will build a network connectivity within the data center automatically, nearly instantaneously, the same way that your cell phone works, effectively. So take that through a little further to the enterprise customer. Give me an example of how somebody might use that and how it drives business. Yeah, no, it's a great question. So I think we've been playing in the virtualization market for some time, so HP has been very strong in the data center space. But now what we're seeing is, rather than virtualize a server, our customers are virtualizing whole data centers. And then the question becomes, what do you do when you have multiple data centers spread across multiple regions? Why do you need to have the physical boundaries anymore? I mean, at the end of the day, the software and what the client experience the users want to see, they don't care where it's hosted from a physical perspective. What they need is the right service at the right time at the right speed. So with technologies like DCN, what we're able to do is actually create the optimized path of the network, irrespective of the underpinning network actual infrastructure, doesn't matter which switch it is, doesn't matter which carrier it is. So technology from Alcatelucin allows us for our enterprise customers, just by flicking a switch on the policy-based system, they can create a VM wherever it's needed in any data center of the world, in any manner they need it. It could be a large application, it could be a small one, it could be for a branch office, it could be for the head office. So that kind of disaggregation of the physical layer and the virtual layer is really starting to pay dividends for enterprise customers, because they no longer have to marry the two together and do painful configuration of port by port, they can actually build application-centric profiles, and then the technology from Alcatelucin will help build the appropriate paths throughout the network to ensure the right client experience. Is there a, okay, so that's, I get that, and that sounds like you're solving there, largely a hardware problem, is there a software analog as well, my software management layer on top of that? Can you? There is, there's a couple of different assets. I mean, we talked, when you think about the software behavior of when a client is using it, right? You usually run into a couple of traditional pain points, right? One of them is, for example, the speed, right? The latency, the actual response time of the application. The second thing is security, right? So actually, how are you building that? How are you routing that? Where's the packets going? How do you do it? And the third thing is scalability. So traditionally, if you think about a financial application, it's got a month then, let's say the CFO is running reports, all of a sudden you need to spin out a series of VMs, you might need to burst out and get some additional compute capacity. That's usually been a bit of a manual effort so far. With this kind of technology, what we're able to do is have the actual compute layer as well as the networking infrastructure respond to exactly what that application needs, when it needs it.  So that's a good enterprise example. Now let's come into the telco side of things. And I don't know, is the telco world even more, I said it before, heterogeneous than the, I mean enterprise world is largely Linux and Windows OSs, right? The telco world sounds like it's got a lot of more specialization. It's certainly evolving very rapidly and particularly when you look at the go-to market, how we as Alcatel Lucent have been taking some of our network functions to market in the past, such as IMS that Dennis just mentioned, you know, you had also touched upon NFV and that certainly is the trend that the industry is adopting is toward NFV. We as Alcatel Lucent, we've had a long history of working with HP and using the HP hardware as the underlying capabilities on top of which our software then wrote. And so we see now where the telcos are trying to decouple those two. They want to build this NFV environment and then they want to buy the network functions directly from various vendors and have one common NFV environment. So we're working very closely with HP to make sure that our network functions can work well with HP's NFV environment as well. And vice versa, you know, it's important for HP to work back with Alcatel Lucent to show that the NFV architecture that HP is proposing, it has wide industry adoption and interoperability. So you're essentially virtualizing the network function and then sort of abstracting that from the hardware. So now my hardware problem goes away. Same question though. I would think there's an even worse software management problem in the telcos. Is that a problem that you guys can attack yet or is that sort of? We work together with that. So if you look at the open NFV architecture that HP has, for example, you'll see distributed cloud networking as one of the components in the open NFV architecture. So the capabilities that Dennis was describing in that enterprise environment are very true in the telco world as well and it's that burstability and again, it's not only bursting up, but one that application is not being used. It's the ability to go back down and free up those resources for some other application that may be bursting and requiring those. And that's the capability that we help bring. I think what Jeff is saying is it's a similar behavior in the enterprise is just at scale. I mean, the carriers at the end of the day, they have to make a decision in terms of how they want to run their operations. They have a series of extremely powerful apps, how our cell phones work, how our fixed line works. These things need to operate. So in addition to having their network as virtualized as possible, there's also a secret sauce in terms of how they orchestrate those VNFs. And that's where we have a lot of good discussions between us in terms of what does that optimized stack look like? And the truth of the matter is it's a relatively nascent industry. You know, we're talking here in 12, 18 months old maybe. And at the moment we have different joint customers who are doing different things. Some are in trials. Some are actually, they've made a big bet, you know, they're in production. And I think it's exciting because I have a couple of, you know, we've got some very good Telco customers we've engaged with together and we show up as a team and we say, here's the HP perspective and the Alcatel Lucent perspective and this is what we think is going to be the winning combination. And I have to say it's starting to pay dividends. You know, they started to recognize that the combination of Telco and IT technologies as well as our respective points of opinion are helping them differentiate in the marketplace as well. So how do you guys look at the market? You know, you're seeing customer problems. There's some similarities. You get together, hey, we can help solve these problems. We can make some money at it. So how do you look at the market? Do you do TAM exercises? And I mean, you got to justify the effort that you put again. How big is this opportunity? Yeah, and certainly we've looked at whenever we've added products to the HP portfolio we've done business cases for each one of those. And then certainly with NFV that's a whole other area as well. And you know, with NFV I know that that's one of the big bets of HP as well. And it certainly is a huge opportunity I think for both companies.  I just know it's big. Yeah, it's in the bees. Yes, it's in at least tens, maybe hundreds of bees. How many hundreds of bees? That's the way that things are going, right? I mean, people don't want to have hardware that's dedicated to a specific application because like you said, it creates this environment of so many different varieties that you have to then manage. They want to try to simplify that world, new to a commercial off the shelf underlying technology, hardware technology and then have the applications run on top of that common information. Yeah, I mean, we learned from the hyperscale guys that homogeneity is the key to scale. And if you have all this diversity you're going to limit your scale. That's really true in the telco business. Increasingly, if you want to go into the digital enterprise, it's true in your company. When you look at the digital enterprise, when you look at how many end points you as a user have today, that's something that's just rapidly growing more and more, right?  Maybe you have an application on your tablet that is your old desk phone. You know, there are all those new trends that are out there. So it's not even you as one user anymore. You as one user now has and now have multiple devices that you're working with that the IT departments need to manage within that enterprise. So now a 10,000 employee enterprise really is like a 40 or 50,000 user enterprise, right? And more and more what we're seeing, you know, it's trying to predict the future with a crystal ball. As much as the products that both companies have, you know, we feel their industry leading, we try very hard to have them. It's about the solutions and it's about repeatability. So what we're trying to do is develop this winning combination of solutions that address certain problems. And the way we do that is we take a look at our flagship products. We say how do these coexist? There's going to be a little bit of a call petition. Sometimes we partner with a lot of people. So does Alcatel Lucent. And at the end of the day, we think about the customer problem, not from how can I put this particular product in that particular customer. It's what's the problem they're trying to solve. And then what is the aggregated solution? And with that solution, you're going to have some HP technology, some Alcatel Lucent technology, some services wrapping around it. But at the end of the day, I think what's very exciting in this space is we take these different assets whether it be a hardware underlay, network infrastructure, compute servers, or whether it be software assets, orchestration, helium, I mean, any kind of virtual environment. And I think that's what's exciting right now. Every engagement we do, we're starting to recognize certain characteristics that they all require and look for. However, the actual end solution is still down to customer choice and their particular problem, right? Where they're based, what they need, what their size is, and so forth. So it's an exciting time for both of us. So what should we look for going forward? Out of time, you guys got to catch a plane. You know, all this digital world, we still got to fly, so it's physical. One day we'll teleport. Limitation, you try it. So what should we look for? Is sort of indications of progress, signs of success, things that are going to make you guys happy? Yeah, we're certainly continuing. You know, we're adding more capabilities together as we work more closely together. We're looking to do things to help automate the rollout of, to address the small and medium businesses with some things. And I don't know how you want to describe that, the virtual CPE. We're trying to, we have our basic building blocks today. The three solutions that Dennis mentioned, the Distributor Cloud Networking, the resale of our routers, the resale of our optics. We're adding the rapport capabilities in for a next generation type communication suite to offer people. And then we're also trying to simplify the approach of rolling out those services to end users themselves. So we're also, in addition to working directly with enterprise customers, we're also seeing a major opportunity to work with large service providers to help them reach enterprise customers in an automated fashion. I think, just spot on, at the end of the day, what it means is you'll see a lot more HV Alcatel-Lusen partnering in the field. We feel that there is a winning combination here in terms of a strong network equipment provider like Alcatel-Lusen, a player like HP. Yeah, two powerhouses. I mean, it's not a Barney deal. Yeah. A lot of times, I didn't know what to expect. And a lot of times people go, eh, we get a press release. But no, it sounds like you guys are really tightly working together. And that's because the dollars are big. Big opportunity and the problems are large, so. And time is now. Awesome. Well, thanks very much for coming on theCUBE, sharing your story. Thank you. Appreciate it. All right, keep right there, everybody, we'll be back. Thanks. Right after this, this is theCUBE, we're live from HP Discover. HP Storage Guy Calvin Zito, and I want to help.