Skip to main content

Securing sensitive info Xerox way


How can Hadoop help to address the challenge of securing sensitive information in a document and limit it to your private cloud? If you want to know how the amazing guys at Xerox have proposed novel architecture to this business problem, then read on.

Since many documents and applications such as electronic medical records (EMR), tax forms, surveys, claims may contain both sensitive private as well as public information, there needs to be a way to protect private and still be able to distribute public info from the same document.

In the architecture approach invented by Shanmuga-nathan Gnanasambandam, Naveen Sharma, Wendell Lewis Kibler (Xerox), firstly, a processor executes to determine document structure from interconnected documents and intelligently indicate “specific information, passages, and/or components of the document as sensitive or insensitive information”. The private information is stored as a file along with meta data on internal cloud storage while the public information is stored as a public file on the external cloud storage like Amazon.

Private and public files may be stored in a replicated fashion in a distributed file system (like HDFS) where a file may be replicated and/or split into a plurality of pieces. “Each piece or replica differs slightly from the others in that each piece or replica includes a bit pattern different from the other (i.e., each replica is not identical byte-for-byte to any other replica)”.



The team goes one step further and once the replicas are stored, the replication process of Hadoop kicks in to store one or more replicas relatively close to the point of consumption and one or more replicas one or more hops away from the point of consumption. “As a result, the farther a particular replicated file is from the point of consumption, the larger the number of replicated files to decode or crack and the longer the encryption key”.

When a user needs to access the entire document, the client program may access and decrypt private file from private cloud along with public file from public cloud, merges them to show one consolidated document view. Hadoop here is architected to compute and store documents in accordance with a multi split/replica approach enabling the unique design.

Comments

Popular posts from this blog

Data deduplication tactics with HDFS and MapReduce

As the amount of data continues to grow exponentially, there has been increased focus on stored data reduction methods. Data compression, single instance store and data deduplication are among the common techniques employed for stored data reduction.
Deduplication often refers to elimination of redundant subfiles (also known as chunks, blocks, or extents). Unlike compression, data is not changed and eliminates storage capacity for identical data. Data deduplication offers significant advantage in terms of reduction in storage, network bandwidth and promises increased scalability.
From a simplistic use case perspective, we can see application in removing duplicates in Call Detail Record (CDR) for a Telecom carrier. Similarly, we may apply the technique to optimize on network traffic carrying the same data packets.
Some of the common methods for data deduplication in storage architecture include hashing, binary comparison and delta differencing. In this post, we focus on how MapReduce and…

Pricing models for Hadoop products

A look at the various pricing models adopted by the vendors in the Hadoop ecosystem. While the pricing models are evolving in this rapid and dynamic market, listed below are some of the major variations utilized by companies in the sphere.
1) Per Node:Among the most common model, the node based pricing mechanism utilizes customized rules for determining pricing per node. This may be as straight forward as pricing per name node and data node or could have complex variants of pricing based on number of core processors utilized by the nodes in the cluster or per user license in case of applications.
2) Per TB:The data based pricing mechanism charges customer for license cost per TB of data. This model usually accounts non replicated data for computation of cost.
3) Subscription Support cost only:In this model, the vendor prefers to give away software for free but charges the customer for subscription support on a specified number of nodes. The support timings and level of support further …

5 online tools in data visualization playground

While building up an analytics dashboard, one of the major decision points is regarding the type of charts and graphs that would provide better insight into the data. To avoid a lot of re-work later, it makes sense to try the various chart options during the requirement and design phase. It is probably a well known myth that existing tool options in any product can serve all the user requirements with just minor configuration changes. We all know and realize that code needs to be written to serve each customer’s individual needs.
To that effect, here are 5 tools that could empower your technical and business teams to decide on visualization options during the requirement phase. Listed below are online tools for you to add data and use as playground.
1)      Many Eyes: Many Eyes is a data visualization experiment by IBM Researchandthe IBM Cognos software group. This tool provides option to upload data sets and create visualizations including Scatter Plot, Tree Map, Tag/Word cloud and ge…