I am not my phone:Avoiding Identity Relationship Pitfalls

Andrew JohnstonMember of the TELUS Team

About TELUS

British Columbia

Alberta

SaskatchewanManitoba

Ontario

Quebec

Atlantic Canada

Canada has a population of 34.88 million.

Network access lines

3.2

millionTV subscribers

865,000

Wireless subscribers

7.9

millionInternet subscribers

1.4

million

Pillars of Identity Relationship Management

BUSINESS PILLARS

1. CONSUMERS AND THINGS over employees

2. ADAPTABLE over predictable

3. TOP LINE REVENUE over operating expense

4. VELOCITY over process

TECHNICAL PILLARS

1. INTERNET SCALE over enterprise scale

2. DYNAMIC INTELLIGENCE over static intelligence

3. BORDERLESS over perimeter

4. MODULAR over monolithic

https://kantarainitiative.org/irmpillars/

http://commons.wikimedia.org/wiki/File:Banaue_Rice_Terrace_Close_Up.jpg

• Challenge: IRM encourages Adaptability,

Velocity

• Identity is primarily a data concern

• Changes to the data tier are slow and

expensive

Identity is grounded in the data tier

Data architects are your friends

Users are people, too

Photo by Maurizio Pesce https://www.flickr.com/photos/pestoverde/

• Business model vs. service model

• Favour relationships over attributes

• Born with it?

Things

• Intrinsic properties of things

• Things as credentials

• Things as service providers

Photo by A.cilia, Wikimedia Commons

individual

customer

service

resource

Relationships

Photo courtesy of pixabay.com

Authenticating people

• “Passwords have reached the end of their useful life.”

• Credential Service Provider?

• Credentials have relationships to a person

Photo by Ranjithsiji, Wikimedia Commons - http://commons.wikimedia.org/wiki/User:Ranjithsiji

• Who told you that?• When did they tell you

that?• Would there be any

advantage to them to misrepresent the truth?

How do you know that?

Sculpture by Donald Lipski, 1985; Copyright: Donald Lipski. Photo: Dorothy Zeidman

Process and Controls

Photo by Lynn Betts, USDA Natural Resources Conservation Service

• Use data and relationships for authorization

• Measure and control data quality

• Minimize data collection and distribution

• Data architects are your friends

• What data distinguishes you from others?

• Everything should have (or be) an API

Be bold, but not reckless, on a path to the IRM future

12© 2014 TELUS Communications Company

andrew.johnston@telus.com