Re: [projectvrm] Towards a Behavioural Identity Framework

[Kevin Cox < >]

Devon,

Websites that become Customer Aware agree, as part of the joining with other CAWs, that they will not use device prints for other purposes.  To enforce this if a CAW captures device prints and passes them on to others, without the individual's consent, then they will be taken from the list of trusted CAWs.  We want to be able to use device prints to help reduce identity fraud, but we do not want it them being passed on to advertisers, spies, etc.

It is for this reason that CAW should be operated by trusted organisations.  The enforcement of the rules of CAW is to set up a mechanism to punish those who break the rules with a red card. This also means that CAW operators have to be easily replaced.  This in turn increases the reliability of the system.

Kevin

On Mon, Jul 15, 2013 at 12:27 AM, Devon M T Loffreto < " target="_blank"> > wrote:

So... the device id is encrypted... email is used for personal control of context... behavior is correlated at the site level based on a matrix of weighted characteristics applied to devices... what about the leaky data that comes with the user like IP, location ,etc...? How are those managed (captured/not captured)?

Devon

On Sat, Jul 13, 2013 at 7:35 PM, Kevin Cox < " target="_blank"> > wrote:

To implement Customer Aware Websites we need an identity framework.  Here is an outline of what we are working on.

http://cscoxk.wordpress.com/2013/07/14/towards-a-behavioural-identity-framework/

Kevin