My Photo

Your email address:


Powered by FeedBlitz

November 2016

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30      
Blog powered by Typepad

Become a Fan

« Re-hosting Legacy Systems: Ground Hog Day | Main | The Data is the Query »

February 14, 2011

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Stephan Engberg

Hi Jeff.

Nice to see you are on the track to asking the questions related to privacy and security.

But I politely would point out a very simple problem in your presentation. You assume linking non-related databases using reuse of identifiers. This is a fundamental flaw representing both a failure by design in the source systems and in the data analysis.

The solution is empowering the Citizen - give them the tools to mange these interconnections and eliminate the problem at source.

Cloud BI simply should not be able to correlate multiple transactions with the same user/device unless they are explicity joined as the same logical context.

Yes, I say "able to" instead of "allowed with consent" - data will find data if the link is there, so the only sustainable way to secure a cloud/internet of things-world is through logical isolation @ source.

This also push the root problem upstream to user-centric person/device identity management where the Failure by Design is originating. The question is not what e.g. Google is allowed to do(legal compliance), but what Google CAN do (technical security and allignment according to the value chains).

The comments to this entry are closed.