>> live from San Francisco. It's the Cube covering Google Club Next nineteen Rodeo by Google Cloud and its ecosystem partners. >> Hey, welcome back. Everyone's the live Cube covers here in San Francisco for Google Cloud. Next nineteen. I'm Javert Day Volante here on the ground floor, day two of three days of wall to wall coverage to great guests. We got Kartik lost. Meena Ryan, product management director of Cloud Identity for Google and Kim parent chief security officer for Doctor on Demand. Guys, welcome to the Cube. Appreciated Coming on. >> Great to be here. >> Thank you so honestly Way covering Google Cloud and Google for many, many years. And one of the things that jumps out at me, besides allows the transformation for the enterprise is Google's always had great technology, and last year I did an interview, and we learned a lot about what's going on the chip level with the devices you got. Chrome browser. Always extension. All these security features built into a lot of the edge devices that Google has, so there's definitely a security DNA in there and Google the world. But now, when you start getting into cloud access and permissions yesterday and the Kino, Thomas Kurian and Jennifer Lin said, Hey, let's focus on agility. Not all his access stuff. This is kind of really were identity matters. Kartik talk about what's going on with cloud identity. Where are we? What's the big news? >> Yeah, thank you. So clouded. Entities are solution to manage identity devices and the whole axis management for the clouds. And you must have heard of beyond Corp and the whole zero trust model and access. One thing we know about the cloud if you don't make the access simple and easy and at the same time you don't provide security. You can get it right. So you need security and you need that consumer level simplicity. >> Think it meant explain beyond core. This is important. Just take a minute to refresh for the folks that might not know some of the innovations. They're just start >> awesome. Yeah. So traditional on premises world, the security model was your corporate network. Your trust smaller. Lose The corporate network invested a lot to get to keep the bad people out. You get the right people on and that made ten T applications on premises. Your data was on premises now the Internet being a new network, you work from anywhere. Work is no longer a thing. You work from anywhere. What gets done right? So what is the new access? More look like? That's what people have been struggling with. What Google came up with in two thousand eleven is this model called Beyond Core versus Security Access Model will rely on three things. Who you are is a user authentication the device identity and security question and last but not least, the context off. What are you trying to access in very trying to access from So these things together from how you security and access model And this is all about identity. And this is Bianca. >> And anyone who has a mobile device knows what two factor authentication is. That's when you get a text messages. That's just two factor M. F. A multi factor. Authentication really is where the action is, and you mentioned three of them. There's also other dimensions. This is where you guys are really taking to the next level. Yeah, where are we with FAA and some of the advances around multi factor >> s O. So I think keeping you on the highlight is wear always about customer choice. We meet customers where they are. So customers today have invested in things like one time use passwords and things like that. So we support all of that here in cloud identity. But a technology that we are super excited about the security, Keith. And it's built on the fighter standard. And it's inserted this into your USB slot of that make sense. And we just announced here at next you can now use your android phone as a security key. So this basically means you don't have to enter any codes because all those codes you enter can be fished on way. Have this thing at Google and we talked about it last time. Since we roll our security keys. No Google account, it's >> harder for the hackers. Really Good job, Kim. Let's get the reality. You run a business. You've been involved in a lot of start ups. You've been cloud nated with your company. Now talk about your environment does at the end of the year, the chief security officer, the buck stops with you. You've got to figure this out. How are you dealing with all this? These threats at the same time trying to be innovative with your company. >> So for clarity. So I've been there six years since the very beginning of the company. And we started the company with zero hardware, all cloud and before there was beaten beyond Corp. Where there was it was called de-perimeterization. And that's effectively the posture we took from the very beginning so our users could go anywhere. And our I always say, our corporate network is like your local coffee shop. You know, WiFi like that's the way we view it. We wanted to be just a secure there at the coffee shop, you know, we don't care. Like we always have people assessing us and they're looking at a corporate network saying, You know, where your switches that you're, you know, like where your hardware like, we want to come in and look at all like we don't have anything like, >> there's no force. The scan >> is like way. Just all go to the Starbucks will be the same thing. So that's part of it. And now you know, when we started like way wanted to wrap a lot of our services in the Google, but we had the problem with hip a compliance. So in the early days, Google didn't have six years ago. In our early days, Google didn't have a lot of hip, a compliant services. Now they do. Now we're moving. We're trying to move everything we do almost in the Google. That's not because we just love everything about Google. It's for me. I have assessed Google security are team has assessed their security. We have contracts with them and in health care. It's very hard to take on new vendors and say Hey, is there security? Okay, are their contracts okay? It's like a months long process and then even at the end of the day, you still have another vendor out there that sharing your day, that you're sharing your data with them and it's precarious for me. It just it doubles my threat landscape. When I go from Google toe one more, it's like if I put my data there, >> so you're saying multi vendor the old way. This is actually a problematic situation for you. Both technically and what operate timewise or both are super >> problematic for me in terms of like where we spread our data to like It just means that company every hack against that company is brutal for us, like And you know, the other side of the equation is Google has really good pricing. Comparatively, yes, Today we're talking about Big Query, for example, and they wanted to compare Big Query to some other systems and be crazy. G, c p. And And we looked at the other systems and we couldn't find the pricing online. And, like Google's pricing was right there was completely transparent. Easy to understand. The >> security's been vetted. The security's >> exactly Kim. Can you explain when you said the multi vendor of creates problems for you? Why is this? Is it not so much that one vendor is better? The other assistant? It's different. It's different processes or their discernible differences in the quality of the security. >> There are definitely discernible differences in quality, for sure. Yeah, >> and then add to that different processes. Skill sets. Is that writer? Yes, Double click on that E >> everybody away. There's always some I mean almost every vendor. You know, there's always something that you're not perfectly okay with. On the part of the security is something you don't totally like about it. And the more vendors you add, you have. Okay. This person, they're not too good on their physical security at their data center or they're not too good on their policies. They're not too good on their disaster recovery. Like there's you always give a little bit somewhere. I hate to say it, but it's true. It's like nobody's super >> perfect like it's It's so it's a multiplication effects on the trade offs that you have to make. Yeah, it's necessarily bad, but it's just not the way you want to do it. All right? Okay. >> All the time. So you got to get in an S L A u have meetings. You gotta do something vetting. It's learning curves like on the airport taking your shoes off. Yeah. Yeah. And then there's the >> other part. Beyond the security is also downtime. Like if they suffer downtime. How much is that going to impact our company? >> Karthik, you talked about this This new access mall, this three layer who authentication that is the device trusted in the context. I don't understand how you balance the ratio between sort of false positives versus blocking. I think for authentication and devices pretty clear I can authenticate. You are. I don't trust this device. You're not getting in, but the context is interesting. Is that like a tap on the shoulder with with looking at mail? Hey, be careful. Or how are you balancing that? The context realm? >> Yeah, I think it's all about customer choice. Again, customers have, but they look at their application footprint there, making clear decisions on Hey, this is a parole application is a super sensitive as an example, maybe about based meeting application. Brotherly, not a sensitive. So when they're making decisions about hey, you have a manage device. I will need a manage device in order for you to access the payroll application. But if you have you bring your own device. I'm off perfectly fine if you launch a meeting from that. So those are the levels that people are making decisions on today, and it's super easy to segment and classify your application. >> Talk about the the people that are out there watching might say, You know what? I've been really struggling with identity. I've had, you know, l'd app servers at all this stuff out there, you name it. They've all kinds of access medals over the years, the perimeters now gone. So I got a deal to coffee shop, kind of working experience and multiple devices. All these things are reality. I gotta put a plan together. So the folks that are trying to figure this out, what's that? You guys have both weigh in on on approach to take or certain framework. What's what's? How does someone get the first few steps off to go out towards good cloud identity? >> Sure, I only go first, so I think many ways. That's what we try to simplify it. One solution that we call cloud identity because what people want is I want that model. Seems like a huge mountain in front of me, like how do I figure these things out? I'm getting a lot of these terminologies, so I think the key is to just get started on. We've given them lots of ways. You can take the whole of cloud identity solution back to Kim's point. It can be one license from us, that's it and you're done. It's one unified. You I thinks like that. You can also, if you just want to run state three applications on DCP we have something called identity ofher Proxy. It's very fast. Just load yaps random on disability and experience this beyond >> work Classic enterprise Khun >> Yeah, you run all the applications and dcpd and you can And now they're announcing some things that help you connect back with John Thomas application. That's a great way to get started. >> Karthik painted this picture of Okay, it's no perimeter. You can't just dig a moat. The queen wants to leave the castle. All the security, you know, metaphors that we use. I'm interested in how you're approaching response to these days because you have to make trade us because there are discernible differences with different vendors. Make the assumption that people are going to get in so response becomes increasingly important. What have you changed to respond more quickly? What is Google doing to help? >> Well, yeah, So in a model where we are using, a lot of different vendors were having to like they're not necessarily giving us response and detection. Google. Every service we'd wrap into them automatically gets effectively gets wrapped into our security dashboard. There's a couple of different passwords we can use and weaken. Do reporting. We do it. A tremendous amount of compliance content, compliance controls on our DLP, out of e mail out of Dr and there's detection. There's like it's like we don't have to buy an extra tool for detection for every different type of service we have, it's just built into the Google platform, which is it's It's phenomenal from >> detection baked in, It's just >> baked in. We're not to pay extra for it. In fact, I mean way by the enterprise license because it's completely worth it for us. Um, you know, assumes that came out, the enterprise part of it and all the extra tools. We were just immediately on that because the vault is a big thing for us as well. It's like not only response, but how you dig through your assets toe. Look for evidence of things like, if you have some sort of legal case, you need vault, Tio, you know, make the proper ah, data store for that stuff >> is prioritization to Is it not like, figure it out? Okay, which, which threats to actually go after and step out? And I guess other automation. I mean, I don't know if you're automating your run book and things of that nature. But automation is our friends. Ah, big friend of starting >> on the product measures I What's the roadmap looks like and you share any insight into what your priorities are to go the next level. Aussie Enterprise Focus. For Google Cloud is clear Customs on stage. You guys have got a lot of integration points from Chromebooks G Sweep all the way down through Big Query with Auto ML All the stuff's happening. What's on your plate for road map? What things are you innovating around? >> I mean, it's beyond car vision that we're continuing to roll out. We've just ruled out this bit of a sweet access, for example, but all these conditions come in. Do you want to take that to G et? You're gonna look. We're looking at extending that context framework with all the third party applications that we have even answers Thing called beyond our devices FBI and beyond Corp Alliance, because we know it's not just Google security posture. Customers are made investments and other security companies and you want to make sure all of that interoperate really nicely. So you see a lot more of that coming out >> immigration with other security platform. Certainly, enterprises require that I buy everything on the planet these days to protect themselves >> Like there's another company. Let's say that you're using for securing your devices. That sends a signal thing. I trust this device. It security, passing my checks. You want to make sure that that comes through and >> now we're gonna go. But what's your boss's title? Kim Theo, you report to the CEO. Yeah, Awesome guys. >> Creation. Thank you >> way. We've seen a lot of shifts in where security is usually now pretty much right. Strategic is core for the operations with their own practices. So, guys, thanks for coming on. Thanks for the thing you think of the show so far. What's the What's The takeaway came I'll go to you first. What's your What's the vibe of the >> show? It's a little tough for me because I have one of my senior security engineers here, and he's been going to a lot of the events and he comes to me and just >> look at all >> this stuff that they have like, way were just going over before this. I was like, Oh my God, we want to go back to our r R R office and take it all in right today. You know, if we could So yeah, it's a little tough because >> in the candy store way >> love it because again, it's like it's already paying for it. It's like they're just adding on services that we wanted, that we're gonna pay for it now. It's >> and carted quickly. Just get the last word I know was commenting on our opening this morning around how Google's got all five been falling Google since really the beginning of the company and I know for a fact is a tana big day that secures all spread for the company matter. Just kind of getting it. Yeah, share some inside quickly about what's inside Google. From a security asset standpoint, I p software. >> Absolutely. I mean, security's built from the ground up. We've been seeing that and going back to the candy store analogy. It feels like you've always had this amazing candy, but now there's like a stampede to get it, and it's just built in from the ground up. I love the solution. Focus that you found the keynotes and all the sessions that's happening. >> That's handsome connective tissue like Antos. Maybe the kind of people together. >> Yeah. I don't like >> guys. Thanks for coming on. We appreciate Kartik, Kim. Thanks for coming on. It's accused. Live coverage here on the ground floor were on the floor here. Day two of Google Cloud next here in San Francisco on Jeffrey David Lantz Stevens for more coverage after this short break.

>> Live from San Francisco. It's theCUBE covering Google Cloud Next 2018. Brought to you by Google Cloud and its ecosystem partners. >> Hey welcome back everyone. It's theCUBE live here in San Francisco for Google Next 2018. I'm John Furrier with Dave Vellante. This is day one of wall to wall three days of live coach here on the floor. Our next guest is Karthik Lakshminarayanan who is the director of product manage for cloud identity, one of the core products at the edge authenticating users, people, and applications and devices. Karthik thanks for coming on. >> Yeah thank you, it's great to be here. >> So take a minute to explain because obviously cloud identity, we've seen identity systems in the enterprise, anyone who's dealt in the enterprise who have been buying I.T., who have been buying I.T. stuff. >> Yes. >> That's around identity and then something new comes out and I got to refresh that, I got to buy this, rip this out, replace this. So identity has been super important but it's been kind of stovepiped within applications. The cloud is horizontally scaled but the benefit of the cloud is that you kind of do it once, if you do it right, architecturally you can scale it. >> Absolutely. >> Take a minute to explain how cloud identity works, and how does it fit into the future of what people expect from the cloud. >> Yeah, absolutely, thank you. And cloud identity, our solution is to help organizations securely manage people, applications, and devices in the cloud. So it's exactly like what you're talking about. User identity is evolving because organizations are now coming in and saying "What is this mobile cloud thing? "How do I adjust?" Because users are getting increasingly trained on continual like behavior they just want to turn on, connect to their cloud services, use their mobile devices and be up and running. Organizations have been trained for years to think about the corporate network as their security parameter, so how does that happen in the cloud when the data is no longer on premises? So that's what we do with cloud identity where we look at signals from your users, from your devices, and other things that we're trying to do and give you a different way of accessing the cloud. >> For the folks watching who might have missed the keynote it's going to be on demand, go to YouTube, but I'm sure it's on the Google Cloud channel. Now one of the things Diane Green said, and then also we saw in the demos, we were talking before we came on camera was, you showed a demo of basically cloud and on-prem solution, looked just like one dashboard just the note and the network, and everything's kind of clean. Diane Green then mentioned that when she came to Google Cloud 20 years ago, was to just share what was already built over 25 years or 20 years to the masses. So okay, that's cool. But the question I want to ask you is, people don't want to be like Google or buy Google stuff to implement it in their non Google environment. They want to use the Google services. So they want the benefits of what you guys have experienced, so this is kind of a cultural nuance within Google Cloud where it's like you don't have to tell them be like Google, just use the services. Identity is super important. You have all this institutional knowledge, and low latency signals, from whether it's Android, Chrome, search, user experience. How are you guys putting that into.. Does that help your product? Is that a benefit of the cusp? Or is that more of a future thing? Because when you're at a service I can almost see identity as a service scaling to a point where all these things are kind of taken care of. What's your vision? >> Yeah, absolutely. A couple things. One is something called BeyondCorp. I think a lot of folks are familiar with, it stands for beyond the corporate network. And I want to touch on a couple things. One, is that today we make the access decisions based on who you are as a user, the state of your device, and then context. And context is really king now in a cloud based world. Where we look at signals, signals around the data that we can get even from our consumer services, but carefully curated and making sure we meet all of the compliance policies. Where we can now look at these signals and we do what we call context server access. So the idea that, what are you trying to access? Where are you accessing from? And who are you as a user and what kind of device are you at? That's the perfect combination of what you just said and we call that context server access and that is absolutely central to how we offer cloud identity. >> That's the classic example I've seen that we are Gmail customers, with Gsuite So when I log in from Paris, "Hey wait a minute, you're not in Paris." So you guys, is this an example of that? >> Yeah, it's funny, I feel like you're part of our team because we call this the superman scenario. Because if you just logged in from say California, then a moment later we see an access request coming in from Paris, we know it's not just because you have the valid username or password, we know that's not right. That's just a trivial example. Like Google does a great job of crawling the web. So we don't just know what the good sides are, we know what the bad sides are. So you even try to access a bad site we can stop you. There's all kinds of things we do with this. >> So I wonder if I can ask you about enterprise I.T. John at our kick off this morning said Google's 10 or maybe even 15 years ahead. And as he was just saying, people can't go that fast to be like Google. So how do you.. I think of a caravan with the fastest truck in the military caravan, has to slow down so the whole caravan can keep up. How do you manage the fact that you're going so fast but enterprises move, we sometimes joke, they move at the speed of the CIO. What's your perspective on that and how do you deal with that challenge? >> No, absolutely. So I think our core philosophy and design philosophy is how we built the product is meeting customers from where they are that's key. So meeting customers where they are, so we recognize, take some of our advanced technology. And we recognize that organizations are still building a lot of applications on premises, so we took the power and made that available on premises. You just saw that today. Another example, we connect to systems of record. We know Microsoft Active directly is largely the identity record of choice in large organizations. So we connect very seamlessly with them, we sync with them, and we use a federated identity story so you don't have to move to all in Google Cloud, you connect Google Cloud, you augment your existing infrastructure and that's how we make it all work. So, really making sure that we are inclusive, and meeting customers where they are is how we've designed everything including cloud identity. >> And I follow up with, is architecturally, how do you future proof it? Now part of it is you have a lead on the rest of the world. You have visibility on things that others aren't going to see for years. But at the same time, you don't know, you can't predict the future, right? So how do you future proof your system architecturally? Maybe talk about that. >> Yeah, I think that a couple things for us, we are big on open systems, so we make sure that the cloud as we all know is built on standards. So as an example, the security keys that we talked about was largely invented at Google but we made sure we contributed that back into the standards community. That's an example. We are big on APIs, making sure all our APIs are out there and we support federated standards like Skim and those others things. So we make sure that an organization can use not just us, but whatever identity system of choice, and we interconnect to standards and APIs and I think that's the way forward. >> So I asked you since you do product management which is you're building products, I mean, I used to run a product group at a big company and products are built differently now, than they are with the cloud. So how has the role in building a product change? Product management, you got to have the right features, you got to have customers. We're living in a services world, where you have a service as the product or the platform is the product in a cloud centric world. How do you guys do that product and share some insights for the folks watching, customers get an insight into how you guys work because it's not your classic product management, or is it? How are you guys doing things differently because business models are being built as a service. Things are changing so fast that a new service like Istio can literally change someone's business overnight, leveraging some of these core services that you guys have. >> So let me share a couple things. I think some things are always going to be the same if we do our jobs right. Which is that customers, customer needs, and making sure the solutions we provide, not features, but solutions, meet customer needs. I think in that regard, whether you deliver it as a service, or as a on-prem, does not matter, that's a delivery model. But we want to make sure we take care of our customers. I think one of the challenges we find on the cloud side is the piece of which we are delivering features and a lot of times the I.T. person or the decision maker in an organization want to make sure they stay in the loop on this, they are getting ahead of planning. You don't want to change that vent out so rapidly that the users are confused, they're getting help desk calls and things like that. So we are have a very structured communications mechanism that we work with, we share roadmaps and timelines so it helps organizations really think about what's coming. I think the service delivery and service consumption is more of a partnership now, even though on the consumer side you might think it's just as a service we push a change. I think its really a partnership. >> And it's faster too, I imagine. >> Absolutely faster. >> Your acceleration of service is faster. >> I think we can meet needs exactly, we can meet needs a lot faster. I wanted to call out that Google consciously takes into account the fact that we don't want our changes to be so fast and so disruptive, we want them to be well received so we really partner with our partners in the custom organizations. >> Its interesting Dave mentioned the caravan example, I would say that enterprises move at a glacial pace. >> Any users feel that way. >> But they're buying I.T. in the past, now they're essentially leveraging scaled services that are prebuilt so they can get things going faster. This is the new normal where they'll be buying services not I.T. products. >> Correct. >> You mentioned solutions, solutions and services. Is that kind of what you're getting at? >> Yeah, I think absolutely. If you think about what's happened as mentioned earlier today, I.T. was a cost center, now they're moving into like, hey how do we get ahead and build a competitive advantage? So I think absolutely, you said it well so plus one. >> Karthik you talked about some of the standards that built up the internet, and now you're seeing with blockchain a spate of new protocols being developed, all this innovation, a lot of talk about K.Y.C. know your customer, and antimoney laundering, AML. Perspectives on what's happening in that blockchain world. Obviously it's relevant to identity, what are you thoughts on what's happening there? >> Yeah, a couple things. One is that we think blockchain is very interesting, it's something that we continue to look at. I personally look at blockchain as amazing technology but we go back to what are the use cases and needs that we need to solve. So let me throw something out there, it's not very well thought out, it's just an idea. But we think about one of the things we've tossed around is bring your own identity. There's a time when identity was think about your cell phone number, if you remember was once tied to your provider, you change your provider, you had to get a new number. And now you have portability you don't think about it. So if you think about you as a user you are who you are, and then there is an identity or a profile that exists on a personal side. There's identity that happens so there is protection in this context that is accessed things like that that blockchain can now enable 'cause you now take your identity and you go with you whether you are in the consumer context, you are in the work context, or even switching from one job to another or one role to another within the organization. So I think blockchain could be technology that is very foundational and fundamental to decentralize notions where I as an organization manage your policies and lots of other things but who you are as a person stays with you. >> The old model was bring your device to work. >> Yes. >> Your base was bring your identity to the world under one immutable own your own data, trustful way. Enabling, identity as a service on a whole 'nother level. >> Very different level. I think were not dead today because right now I think organizations are shifting mainly from wrap their arms around the user and the identity and they're super paranoid about moving to the cloud. I think the first step is making them fundamentally comfortable with everything they need. But once we build I think your trust point is key once you have that governance and that secure platform we can start shifting towards bring your own identity and how can that all coexist. >> And why do you think the consternation about moving to the cloud. Is it because it's still unknown? It's still somewhat new? Because I mean by all accounts when you talk to the experts, they'll admit the cloud is more secure than what I can do on prem. Why the consternation? >> Absolutely, I think the key part is the simplicity that comes and I think it's a new model that has not yet been mastered, so cloud is secure, yes, but when my users start doing things that I don't really want them to do, what we call is shadow I.T., they're very worried about it. And then on the flip side they've been trained for years, decades on this whole old model of corporate network and now were saying the cloud is open and the internet is your new network. So that I think scares a lot of people but customers when they come to Google and they see our BeyondCorp story and our cloud identity story, then they know that they can achieve both. Higher access for employees and advanced security for organizations. >> I think the Beyond Corporate is very relevant. We've been tracking that we find that super fascinating. On the shadow I.T., we've been reporting on shadow I.T., it's our ninth year today. But shadow I.T. though, is just an early adopter form of DevOps, so I think shadow I.T. has kind of regulated itself to as a stepping stone for cloud. SAP used to do shadow I.T. as presales and then customers moved everything to the cloud so I think shadow I.T. is much more of a kind of kindergarten or first step to DevOps. >> I think DevOps is where a lot of organizations are moving. I think depending on where the organization is going back they like the I.T. admin led model, they're experimenting with DevOps, there's a lot of experimentation going on. I think what I like about shadow I.T. and not from a security risk perspective but it's signal that clear intent from the user to the organization saying I want access to these services fast and make it simple. >> It's like an R and D sand box the way I look at it. Final question for you I know you got to go. Thanks for coming on, I appreciate your time. How are you guys going to roll out this identity as a service, who's your competition, how do you guys compare, what's the story, what's the vision? Share some of the competitive strengths and weakness. What's going on? >> Yeah, I think three things for us. It's already available today, you can go to cloud.google.com/identity. Sign up for a free trial and we give you everything from identity as a service to device management and all of that. The things that we focus on is like smart, secure, and simple. The idea that we can use ML based security to automatically protect, no longer can an I.T. admin go in and set reactive policies. We just have to use data and set proactive policies and protect them. To your points earlier about end points and other data coming into that's the smart piece. We also have a unified single pane of glass, unified administration, one admin controlled to manage everything because people are complaining about the complexity of these solutions that they got to put together. So you get cloud identity you get one thing everything from not just the administration but also the licensing. One price and you're done. You never have to worry about it. And the last but not the least, it has to be secure. The things we talked about from security keys, I've never changed my password for the two years I've been at Google. I use security keys and never typed an RSA key or anything like that. It's fascinating how simple we can make it so that's really what we like smart, secure, and simple. >> Awesome, well congratulations. Looking forward to see how this scales out certainly foundationally identity is super important. Identity is one of the bedrock of cloud. It's part of that system that scales theCUBE. Bringing you all the best content scaling here at Moscone with all the great content from Google Next. I'm John Furrier and Dave Vellante. Stay with us from day one coverage of three days of live coverage here in San Francisco. We'll be right back.