Browse Prior Art Database

Method and Apparatus for Cloud Bursting with Dynamic Data De-Identification

IP.com Disclosure Number: IPCOM000240534D
Publication Date: 2015-Feb-06
Document File: 2 page(s) / 71K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for cloud bursting with data de-identification. It allows cloud bursting while maintaining the data on the provider's private premises.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 2

Method and Apparatus for Cloud Bursting with Dynamic Data De-Identification

De-identification is the process by which a collection of data is stripped of information that can allow the identification of the source of the data. Anonymization is a more severe form of de-identification as it refers to irreversibly severing the data set from the identity of the data source, thus inhibiting any future re-identification, even by the data owner, under any condition. Data de-identification is a key requirement in many emerging technologies such as hybrid cloud, business analytics, and social media and computing services.

Cloud bursting is the process of scaling out applications in the public cloud.

This disclosure presents a method for cloud bursting with data de-identification. It allows cloud bursting while maintaining the data on the provider's private premises. The novel method comprises the bursting architecture that allows data de-identification, combining private/public clouds to allow control over data via anonymization. The novelty lies in the method for combining private and public clouds. The novel contribution also includes the runtime mechanism that identifies the source of the calls and the process of deploying the application for cloud bursting with data anonymization.

At run time, depending on the volume/response requirement, the private cloud, through the load balancer, bursts into the public cloud as an infrastructure for performance elasticity, resulting in the availability of both the private and the public cloud to the users. Users can then access a data set either via the private cloud or via the public cloud.

When the user accesses data (e.g., reads, updates, creates, etc.) the Load Balancer directs all POST, PUT or any...