125
The Laws of Relationships (A Work In Progress) Ian Glazer Senior Director, Identity salesforce.com @iglazer

Laws of Relationships

  • Upload
    iglazer

  • View
    2.882

  • Download
    0

Embed Size (px)

DESCRIPTION

Taking a page from the work that Kim did with “The Laws of Identity,” I wanted to provide the starting point for the community to build a similar set of design constraints and considerations for relationships and relationship management technologies. Our current IAM methods will be insufficient in a near future in which we are dealing with an unreasonable number of people and things and the relationships between them. At the IRM Summit, I’ll be presenting a strawman set of laws for relationships to help us think about this coming future. To that end, here is a preview of the laws (and axioms and attributes) of relationships.

Citation preview

Page 1: Laws of Relationships

The Laws of Relationships (A Work In Progress)

Ian Glazer

Senior Director, Identity

salesforce.com

@iglazer

Page 2: Laws of Relationships

What’s the problem?

Page 3: Laws of Relationships
Page 4: Laws of Relationships

firstName lastName email mobile ou nickname title …

firstName lastName email mobile ou nickname title …

firstName lastName email mobile ou nickname title …

firstName lastName email mobile ou nickname title …

Page 5: Laws of Relationships
Page 6: Laws of Relationships
Page 7: Laws of Relationships

Reasonably large number of identities with a reasonable

number of attributes

Page 8: Laws of Relationships
Page 9: Laws of Relationships

deviceID firmware

deviceID firmware

deviceID firmware

deviceID firmware

Page 10: Laws of Relationships
Page 11: Laws of Relationships
Page 12: Laws of Relationships

Unreasonably large number of identities

with a few attributes?

Page 13: Laws of Relationships
Page 14: Laws of Relationships

Reports To

Reports To

Reports To

Works with

Page 15: Laws of Relationships

Reports To

Reports To

Reports To

Owns

Owns

Owns

Works with

Page 16: Laws of Relationships

Reports To

Reports To

Reports To

Owns

Owns

Owns

Paired

Owns

Gets data from

Sends data to

Uses

Controls

Works with

Page 17: Laws of Relationships

Reports To

Reports To

Reports To

Owns

Owns

Owns

Paired

Owns

Gets data from

Sends data to

Uses

Controls

Works with

Drives

UsesConstrains Choice Of

Uses

Page 18: Laws of Relationships

Reports To

Reports To

Reports To

Owns

Owns

Owns

Paired

Owns

Gets data from

Sends data to

Uses

Controls

Works with

Drives

UsesConstrains Choice Of

Uses

Can send data to

Riden In

Riden In

Page 19: Laws of Relationships

Unreasonably large number of relationships between

unreasonably large numbers of people and things, each

with attributes?

Page 20: Laws of Relationships

Why build laws in the first place?

Page 21: Laws of Relationships

• Inform our designs • Test existing solutions • Identify gaps

Page 22: Laws of Relationships

Laws of Identity (2004)1. User Control and Consent

2. Minimal Disclosure for a Constrained Use

3. Justifiable Parties

4. Directed Identity

5. Pluralism of Operators and Technologies

6. Human Integration

7. Consistent Experience Across Contexts

Page 23: Laws of Relationships

The Laws* Of Relationships

Page 24: Laws of Relationships

(A Work In Progress)

Page 25: Laws of Relationships

• Axioms • Types • Laws

Page 26: Laws of Relationships

AxiomsAttributes in support of

pre-existing natural state or requirements

Page 27: Laws of Relationships

1. Scalable 2. Actionable

Page 28: Laws of Relationships

Scalable

Page 29: Laws of Relationships
Page 30: Laws of Relationships

• Number of actors• Number of relationships• Number of attributes

Page 31: Laws of Relationships

• Number of actors• Number of relationships• Number of attributes• Administration

Page 32: Laws of Relationships

Actionable

Page 33: Laws of Relationships

Relationships must be able to carry authorization data

Page 34: Laws of Relationships
Page 35: Laws of Relationships

Can perform actions X, Y, and Z

Can perform actions Q, W, and E

Page 36: Laws of Relationships

Can perform actions X, Y, and Z

Can perform actions Q, W, and E

Page 37: Laws of Relationships

Can perform actions X, Y, and Z

Can perform actions Q, W, and E

Page 38: Laws of Relationships
Page 39: Laws of Relationships
Page 40: Laws of Relationships
Page 41: Laws of Relationships

?

?

Page 42: Laws of Relationships

But relationships do not have to carry authZ data

Page 43: Laws of Relationships

TypesInforms the greater context

Page 44: Laws of Relationships

1. Immutable 2. Contextual 3. Transferrable

Page 45: Laws of Relationships

Immutable

Page 46: Laws of Relationships

Built by

Built by

Page 47: Laws of Relationships

Contextual

Page 48: Laws of Relationships

Relationship is active when conditions are met

Page 49: Laws of Relationships

Inactive relationships• None of the parties “use” the relationship until a condition is satisfied. • The set of driver, car, insurer

relationships isn’t “used” until there is a claim.

• Inert, inactive relationships are still important because they provide context • This widget was made by Yoyodyne.

Page 50: Laws of Relationships

Inactive relationships• None of the parties “use” the relationship until a condition is satisfied. • The set of driver, car, insurer

relationships isn’t “used” until there is a claim.

• Inert, inactive relationships are still important because they provide context • This widget was made by Yoyodyne.

Drives

Page 51: Laws of Relationships

Inactive relationships• None of the parties “use” the relationship until a condition is satisfied. • The set of driver, car, insurer

relationships isn’t “used” until there is a claim.

• Inert, inactive relationships are still important because they provide context • This widget was made by Yoyodyne.

Drives Insures

Page 52: Laws of Relationships

Inactive relationships• None of the parties “use” the relationship until a condition is satisfied. • The set of driver, car, insurer

relationships isn’t “used” until there is a claim.

• Inert, inactive relationships are still important because they provide context • This widget was made by Yoyodyne.

Drives Insures

Manufactured by

Page 53: Laws of Relationships

Active Relationships

• Context toggles a relationship into a usable state

Page 54: Laws of Relationships

Active Relationships

• Context toggles a relationship into a usable state

Page 55: Laws of Relationships

Active Relationships

• Context toggles a relationship into a usable state

Customer

Page 56: Laws of Relationships

Active Relationships

• Context toggles a relationship into a usable state

Customer

Possesses

Page 57: Laws of Relationships

Active Relationships

• Context toggles a relationship into a usable state

Customer

Owns

Possesses

Page 58: Laws of Relationships

Active Relationships

• Context toggles a relationship into a usable state

Customer

Owns

Owns

Possesses

Page 59: Laws of Relationships

Active Relationships

• Context toggles a relationship into a usable state

Customer

Owns

Owns

Possesses

Page 60: Laws of Relationships

Active Relationships

• Context toggles a relationship into a usable state

Customer

Owns

Owns

Possesses

Page 61: Laws of Relationships

Context is a requirement• Related Research:

– Death of authentication and rise of recognition – Relationship context metadata and the need for durable metadata

Page 62: Laws of Relationships

Transferable

Page 63: Laws of Relationships

Client

Temporary Transference

Page 64: Laws of Relationships

Client

Temporary Transference

Delegate

Page 65: Laws of Relationships

Client

Temporary Transference

Delegate

Acts on behalf of client

Page 66: Laws of Relationships

Client

Temporary Transference

Delegate

Acts on behalf of client

Page 67: Laws of Relationships

Client

Temporary Transference

Acts on behalf of client

Page 68: Laws of Relationships

Client

Temporary Transference

Page 69: Laws of Relationships

Permanent Transference

Owns

Page 70: Laws of Relationships

Permanent Transference

Owns

Customer Of

Page 71: Laws of Relationships

Permanent Transference

Owns

Customer Of

Page 72: Laws of Relationships

State of transference• Do we need a system of record for transference state?

• Who would maintain such a system of record?

• Can/should the relationship carry history?

Page 73: Laws of Relationships

Laws

If a thing cannot be X, then it is not a relationship

Page 74: Laws of Relationships

1. Provable 2. Acknowledgeable 3. Revocable 4. Constrainable

Page 75: Laws of Relationships

Provable

Page 76: Laws of Relationships

Mechanism to prove that a relationship

exists between parties

Page 77: Laws of Relationships

• Single-party asserted • Multi-party asserted • 3rd-party asserted

Page 78: Laws of Relationships

Single Party Asserted: X relates to Y because X says so

I work for her

Page 79: Laws of Relationships

Multi-Party Asserted: X relates to Y because X and Y say so

I work for her

She works for me

Page 80: Laws of Relationships

3rd-Party Asserted: X relates to Y because Z says so

Sally works for Mary

HR

Page 81: Laws of Relationships

3rd-Party Asserted: Does this require other relationships?

HR

Page 82: Laws of Relationships

Acknowledgeable

Page 83: Laws of Relationships

All parties must be able to acknowledge they are

in a relationship

Page 84: Laws of Relationships
Page 85: Laws of Relationships
Page 86: Laws of Relationships

I acknowledge my relationship

with Twitter

Page 87: Laws of Relationships

I acknowledge my relationship

with Twitter

Page 88: Laws of Relationships

I acknowledge my relationship

with Twitter Do I acknowledge my followers?

Page 89: Laws of Relationships
Page 90: Laws of Relationships
Page 91: Laws of Relationships

They will acknowledge

their relationship with me

Page 92: Laws of Relationships

They will acknowledge

their relationship with me

But can I acknowledge my relationship with

them?

Page 93: Laws of Relationships
Page 94: Laws of Relationships

Is this really a Law or a feature request from the VRM/PDE/Privacy-types?

Page 95: Laws of Relationships

Revocable

Page 96: Laws of Relationships

Real-world revocation

Page 97: Laws of Relationships

Real-world revocation

Page 98: Laws of Relationships

Real-world revocation

Owns

Owns

Page 99: Laws of Relationships

Real-world revocation

Owns

Owns

Built By

Page 100: Laws of Relationships

Real-world revocation

Owns

Owns

Paired

Built By

Acts on behalf of

Page 101: Laws of Relationships

Real-world revocation

Owns

Owns

Paired

Built By

Acts on behalf of

Page 102: Laws of Relationships

Real-world revocation

Owns

Owns

Paired

Built By

Acts on behalf of

Page 103: Laws of Relationships

Real-world revocation

Owns

Paired

Built By

Acts on behalf of

Page 104: Laws of Relationships

Real-world revocation

Owns

Paired

Built By

Acts on behalf of

Page 105: Laws of Relationships

Questions that need answers• Can either party revoke a relationship?

• If I sever a relationship should any party who was part of the relationship still have access and use of what was shared in the course of the relationship?

• Does this imply the idea of cascading delete?

Page 106: Laws of Relationships

Constrainable

Page 107: Laws of Relationships
Page 108: Laws of Relationships

With my permission, it can report its location

Page 109: Laws of Relationships

With my permission, it can report its location

It can constantly report energy use to my power company

Page 110: Laws of Relationships

With my permission, it can report its location

It can constantly report energy use to my power company

It can only used by customers with active licenses

Page 111: Laws of Relationships

Consent

It can constantly report energy use to my power company

It can only used by customers with active licenses

Page 112: Laws of Relationships

Consent

Consent

It can only used by customers with active licenses

Page 113: Laws of Relationships

Consent

Consent

DRM

Page 114: Laws of Relationships

Now what?

Page 115: Laws of Relationships

Laws, Types, and Axioms

Laws Types Axioms

• Provable • Acknowledgeable • Revocable • Constrainable

• Immutable • Contextual • Transferrable

• Scalable • Actionable

Page 116: Laws of Relationships

Join the Kantara WG!

Page 117: Laws of Relationships

Send me comments : https://www.tuesdaynight.org/

2014/05/28/the-laws-of-relationships-a-work-in-

progress.html

Page 118: Laws of Relationships

Go test this!

Page 119: Laws of Relationships

Where should we try and test relationship management?• IoT is a natural case

– Industrial settings (factories, planes, etc) – Citizen (smart homes, sensors in public)

• Familial Relationships – Insurance – Healthcare

• Finance – Complex authorization models – Regulatory influence

Page 120: Laws of Relationships

Where else can we test this?• Product architecture

• User stories

• Random strangers on the bus

Page 121: Laws of Relationships
Page 122: Laws of Relationships
Page 123: Laws of Relationships

Reports To

Reports To

Reports To

Owns

Owns

Owns

Paired

Owns

Gets data from

Sends data to

Uses

Controls

Works with

Drives

UsesConstrains Choice Of

Uses

Can send data to

Riden In

Riden In

Page 124: Laws of Relationships

The Laws Of Relationships

Page 125: Laws of Relationships