Umesh Shankar
Umesh Shankar is a Distinguished Engineer and the Chief Technologist for Google Cloud Security. He leads many cross-cutting initiatives, most notably Google Cloud's Security AI efforts. In his 17 years at Google, Umesh has led a number of foundational security and privacy initiatives, including the creation of the Data Protection effort at Google, building global infrastructure for key management, authentication, authorization, insider risk, software supply chain security, data governance, and Access Transparency, to keep users' data safe across all Google’s products and Google Cloud Platform. He previously led the Google Assistant Ecosystem team, including its developer platform, identity, monetization, and discovery services.
Umesh has a Ph.D. in computer science from the University of California, Berkeley, and an A.B. from Harvard University. He is an avid soccer player, mixologist, clarinetist, husband, and dad to three boys.
Research Areas
Authored Publications
Sort By
Preview abstract
Offering strong data protection to cloud users while enabling rich applications is a challenging task. Researchers explore a new cloud platform architecture called Data Protection as a Service, which dramatically reduces the per-application development effort required to offer data protection, while still allowing rapid development and maintenance.
View details
Preview abstract
The current health system lacks assurances to patients of data retention and privacy control. We argue that this is due to discrepancies in how health data is reported and consumed and contrast this with how financial credit data is reported and consumed. To address these health system gaps in protection of medical data, we would like to evangelize the implementation of health record trusts. Finally, we argue that Personal Health Records (PHRs) are the closest to offering the main features of health record trusts.
View details
Preview abstract
There are several challenges in aggregating health records from multiple sources, including merging data, preserving proper attribution, and allowing corrections. unfortunately, standards for exchanging medical records data, such as CCR and CCD, tend to focus on representing particular clinical data as some subset of a patient’s complete record. This provides a snapshot of a patient record, but there is very little to describe how a sequence of changes to the record should be interpreted as a coherent whole.there is something available that gives us the data aggregation, conflict resolution, and audit trail that what we want: the Wave federation protocol.
View details
Dynamic Pharming Attacks and Locked Same-Origin Policies for Web Browsers
Preview
Chris Karlof
J. D. Tygar
David Wagner
Conference on Computer and Communications Security, ACM, Alexandria, VA (2007)
