Difference between revisions of "Identity Lifecycle"

From IIW
Jump to: navigation, search
(Undo revision 3157 by Igiwydijok (Talk))
 
Line 1: Line 1:
----
 
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
 
----
 
=[http://erihybomex.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
 
----
 
=[http://erihybomex.co.cc CLICK HERE]=
 
----
 
</div>
 
 
Monday Session 4 Space E
 
Monday Session 4 Space E
  
Line 17: Line 9:
 

Controllably exposed (for example by contract)
retrievable/withdraw able/erasable
   - Vanish is an example of a product here.


 

Controllably exposed (for example by contract)
retrievable/withdraw able/erasable
   - Vanish is an example of a product here.


  
Is there another level here which is &quot;Assured destruction&quot;
   
+
Is there another level here which is "Assured destruction"
   
  
 
Disappearing Ink was a company in this space.

Data security becomes very much like a DRM system.


 
Disappearing Ink was a company in this space.

Data security becomes very much like a DRM system.


Line 33: Line 25:
 
Can a trusted 3rd party help ensure te dustruction/privacy/revocation.


 
Can a trusted 3rd party help ensure te dustruction/privacy/revocation.


  
A key question, &quot;what is the incentive for people to be good actors?&quot;  or what's the penalty for not obeying privacy restrictions?


+
A key question, "what is the incentive for people to be good actors?"  or what's the penalty for not obeying privacy restrictions?


  
 
Another interestion question of information lifecycle:  when the data changes context you may really care.  It can be a big problem.  The privacy boundaries here are significant and the user needs to be in control.

 
Another interestion question of information lifecycle:  when the data changes context you may really care.  It can be a big problem.  The privacy boundaries here are significant and the user needs to be in control.


Latest revision as of 15:28, 3 February 2011

Monday Session 4 Space E

Conference: IIW10 May 17-19, 2009 this is the complete Complete Set of Notes

We have several classes of data:



Uncontrollably exposed
 - Here we are throwing up our hands. 


Controllably exposed (for example by contract)
retrievable/withdraw able/erasable
   - Vanish is an example of a product here.



Is there another level here which is "Assured destruction"
   

Disappearing Ink was a company in this space.

Data security becomes very much like a DRM system.



How do we apply this to Identity Information?



Another taxonomy:


  • Permanent data that we might want to withdraw.

  • Transient data that should have a limited life.



What controls do we have here?


  • Contract

  • Legal obligation



Can a trusted 3rd party help ensure te dustruction/privacy/revocation.



A key question, "what is the incentive for people to be good actors?"  or what's the penalty for not obeying privacy restrictions?



Another interestion question of information lifecycle:  when the data changes context you may really care.  It can be a big problem.  The privacy boundaries here are significant and the user needs to be in control.