Smartphone based Access Control: Adventures in Usability Lujo Bauer - - PowerPoint PPT Presentation

smartphone based access control adventures in usability
SMART_READER_LITE
LIVE PREVIEW

Smartphone based Access Control: Adventures in Usability Lujo Bauer - - PowerPoint PPT Presentation

Carnegie Mellon Smartphone based Access Control: Adventures in Usability Lujo Bauer Carnegie Mellon Device enabled Authorization Smartphones on a trajectory to win in the market Stand to inherit mobile phone market that


slide-1
SLIDE 1

Carnegie Mellon

Smartphone‐based Access Control: Adventures in Usability

Lujo Bauer

slide-2
SLIDE 2

Carnegie Mellon

2

Smartphones on a trajectory to “win” in the market

Stand to inherit mobile phone market that shipped over 1.1 billion

units in 2008 [IDC]—or more than one phone per six people in the world

Unique combination of capabilities

Computation, communication, user interface

Device‐enabled Authorization

Goal: to use smartphones to intelligently control

environment

Loan you my car without giving you my phone Send money from my phone to my friend’s phone Give my secretary temporary access to my email without revealing

information (e.g., password) that could be used at a later time

Use my phone to open my hotel room door, without ever stopping by

the front desk

… and do it all from a distance

slide-3
SLIDE 3

Carnegie Mellon

3

Universal, flexible, end‐user‐

driven access‐control system for physical and virtual resources

Deployed in Carnegie Mellon’s

Collaborative Innovation Center

Approximately 35 Grey‐capable doors

and 30+ users at the moment

Grey‐compatible Windows XP, Vista

and Linux login modules

Plus a deployment in progress at

UNC Chapel Hill

Grey Deployment

slide-4
SLIDE 4

Carnegie Mellon

4

Grey: An Example Scenario

Lujo’s Office, 2121 Lujo Scott

Lujo must authorize access I need to grade the midterms for Lujo’s class

  • Lujo’s students are allowed in 2121
  • Faculty are allowed in 2121
  • At CMU, Lujo’s secretary speaks on

behalf of Lujo …

slide-5
SLIDE 5

Carnegie Mellon

5

Grey: An Example Scenario

  • 1. Hi, Please open 2121
  • 2. Prove Lujo says open 2121

Lujo’s Office, 2121 Lujo Scott

  • 5. Proof of Lujo says open 2121
  • 3. Prove Scott says open 2121

→ Lujo says open 2121

  • 4. Proof of Scott says open 2121

→ Lujo says open 2121

This is Lujo’s

  • belief. I’ll ask

Lujo for help.

Provable if Lujo says:

  • Open 2121
  • Scott speaks for Lujo
  • Scott is a student
  • Scott is faculty

Scott is a student.

Generate credential stating Scott’s desire to open 2121

slide-6
SLIDE 6

Carnegie Mellon

6

Grey: An Example Scenario

  • 1. Hi, Please open 2121
  • 2. Prove Lujo says open 2121

Lujo’s Office, 2121 Lujo Scott

  • 5. Proof of Lujo says open 2121
  • 3. Prove Scott says open 2121

→ Lujo says open 2121

  • 4. Proof of Scott says open 2121

→ Lujo says open 2121

Digitally signed credentials ... … assembled in a formal, mechanically verifiable proof

High assurance Rich audit logs Flexibility in policies

slide-7
SLIDE 7

Carnegie Mellon

7

slide-8
SLIDE 8

Carnegie Mellon

8

Some Research Challenges

[w/ Reiter, Cranor, others]

Logics for access control

[ESORICS 2006, NDSS 2007, SACMAT 2009]

Distributed theorem proving

[IEEE S&P 2005, ESORICS 2007]

Helping users configure access‐control policies

[CHI 2008a, SACMAT 2008, CMU TR 2009]

Improving usability / evaluating usefulness in practice

[SOUPS 2007, CHI 2008b]

slide-9
SLIDE 9

CMU Usable Privacy and Security Laboratory http://cups.cs.cmu.edu/

Lessons Learned From the Deployment of a Smartphone-Based Access-Control System

Lujo Bauer, Lorrie Cranor, Michael K. Reiter and Kami Vaniea

slide-10
SLIDE 10

Carnegie Mellon

10

Can a smartphone‐based access control system gain

acceptance?

Our contribution is to illustrate how six design principles

manifest themselves in a smartphone‐based access‐control system

Deployment Study

Research Question

slide-11
SLIDE 11

Carnegie Mellon

11

Year long study 19 users Periodic interviews Analysis of log data

Deployment Study

Grey Field Trial

slide-12
SLIDE 12

Carnegie Mellon

12

Solicited from those who need access to resources protected

by Grey

6 computer science and engineering faculty 9 computer science and engineering graduate students 3 technical staff 1 administrative assistant

Deployment Study

Field Trial: Participants

slide-13
SLIDE 13

Carnegie Mellon

13

Deployment Study

Field Trial: Environment

5 perimeter doors to a large

research area (locked at 6pm)

11 offices 2 storage closets 1 conference room 1 lab space 1 machine room

slide-14
SLIDE 14

Carnegie Mellon

14

Interviewed participants

Security practices Types of resources managed and needed

Gave participants a smartphone with Grey pre‐installed and

brief instruction on use

Interviewed one month later

Changes in security practices Resource management activity General reactions to Grey

Additional interviews as needed

Deployment Study

Field Trial: Interview Procedure

slide-15
SLIDE 15

Carnegie Mellon

15

Deployment Study

Data

Audiotaped over 30 hours of interviews Logged 19,500 Grey access requests Active users averaged 12 access a week

Five users accessed their office almost exclusively with Grey Three users gave away their keys

Users interacted with an average of 7.4 different doors

during the study

slide-16
SLIDE 16

Carnegie Mellon

16

Deployment Study

Overall Usage

slide-17
SLIDE 17

Carnegie Mellon

17

Observed how six known principles apply to the design of

applications based on emerging technology

Deployment Study

Lessons Learned

slide-18
SLIDE 18

Carnegie Mellon

18

Perceived speed and convenience are critical to user

satisfaction and acceptance

Deployment Study

Principle 1

slide-19
SLIDE 19

Carnegie Mellon

19

Users quickly began to complain about speed and

convenience

We knew Grey and keys required similar amounts of time to

  • pen a door

Videotaped a highly trafficked door to better understand

how doors are opened differently with Grey and keys

Deployment Study

Perceived Speed

slide-20
SLIDE 20

Carnegie Mellon

20

Videotaped participants accessing

kitchenette door

Videotaped two hours daily after 6pm

for two weeks

18 users taped

5 Grey participants 13 additional participants were solicited as

they passed through the door Deployment Study

Videotaping

slide-21
SLIDE 21

Carnegie Mellon

21

Deployment Study

Door Access Average Times

slide-22
SLIDE 22

Carnegie Mellon

22

A single failure can strongly discourage adoption

Deployment Study

Principle 2

slide-23
SLIDE 23

Carnegie Mellon

23

Cost of failure is potentially high Rebooting a phone or door was considered very inconvenient Several users stopped using Grey actively after a single

inopportune failure

Deployment Study

A Single Failure

slide-24
SLIDE 24

Carnegie Mellon

24

Delays can be interpreted as failures even when the system

is functioning perfectly

Humans can be slow or unresponsive

Providing feedback on the

status of the request is very important

Did it arrive? Is a human currently responding?

Deployment Study

Delays Interpreted as Failures

slide-25
SLIDE 25

Carnegie Mellon

25

Users won’t use features they don’t understand

Deployment Study

Principle 3

slide-26
SLIDE 26

Carnegie Mellon

26

Deployment Study

Confusing Features

Users would rather choose a

suboptimal solution that they understand than one with an uncertain outcome

Initially tried for terse interface (top) Adopted wizard solution (bottom)

slide-27
SLIDE 27

Carnegie Mellon

27

Systems that benefit from the network effect are often

untenable for small user populations

Deployment Study

Principle 4

slide-28
SLIDE 28

Carnegie Mellon

28

A service becomes more valuable as more people use it Our participants were selected so that their work network

included others with Grey

Still had many people who would have benefited if Grey

participant could have given access

Deployment Study

Network Effect

slide-29
SLIDE 29

Carnegie Mellon

29

Deployment Study

Jim’s Colleagues

Marie Frank Mark Joe Jake Sue Lillian Bob

Jim

No Grey Have Grey

slide-30
SLIDE 30

Carnegie Mellon

30

Low overhead for creating and changing policies encourages

policy change

Deployment Study

Principle 5

slide-31
SLIDE 31

Carnegie Mellon

31

Using Grey our participants successfully granted and received

more access than they previously had

Participants granted new access because it was convenient Covered further in technical report

  • L. Bauer, L. Cranor, R. W. Reeder, M. K. Reiter and K. Vaniea.

Comparing access‐control technologies: a study of keys and smartphones, Technical Report CMU‐CyLab‐07‐005. http://www.cylab.cmu.edu/default.aspx?id=2284 Deployment Study

Policy Change

slide-32
SLIDE 32

Carnegie Mellon

32

Unanticipated uses can bolster acceptance

Deployment Study

Principle 6

slide-33
SLIDE 33

Carnegie Mellon

33

Unlocking door from inside the office without having to

stand

Unlocking nearby door for someone else without leaving

  • ffice

Deployment Study

Unanticipated Uses

slide-34
SLIDE 34

Carnegie Mellon

34

Users treat Grey like an appliance

Low tolerance for failure

Advanced functionality wasn’t always used Education and background seemed to have little effect on

usage

Deployment Study

Discussion

slide-35
SLIDE 35

A User Study of Policy Creation in a Flexible Access-Control System

Lujo Bauer, Lorrie Faith Cranor, Robert W. Reeder, Michael K. Reiter, Kami Vaniea

slide-36
SLIDE 36

Carnegie Mellon

36

How well do implemented access‐control policies match

ideal access‐control policies?

In other words: are users able to create access‐control

policies that do what they want?

Policy‐creation Study

Our Question

slide-37
SLIDE 37

Carnegie Mellon

37

Interviewed participants about their current access control

practices

Gave participants a Grey phone Periodically interviewed Used interviews to create policy maps for each resource

  • wner’s ideal, key and Grey policy

Counted number of potential false rejects and accepts based

  • n the policies

Policy‐creation Study

Study Overview

slide-38
SLIDE 38

Carnegie Mellon

38

Over three dozen Grey‐enabled doors

8 offices A machine room

29 Grey users

9 faculty 11 graduate students 9 staff

8 resource owners

Policy‐creation Study

Environment

Building Floor Plan

slide-39
SLIDE 39

Carnegie Mellon

39

Interviewed 8 resource owners

Security policies Types of resources managed and needed

Gave participants a smartphone with Grey

pre‐installed and brief instruction on use

Interviewed one month later

Changes in policy Resource management activity General reactions to Grey

Periodically conducted follow‐up interviews at

approximately one month intervals

Policy‐creation Study

Interview Procedure

slide-40
SLIDE 40

Carnegie Mellon

40

Audiotaped over 20 hours of interviews for the eight

resource owners

System was actively used

Logged 19,500 Grey accesses for 29 users Active users averaged 12 accesses a week Five users accessed their office almost exclusively with Grey Users interacted with an average of 7.4 different doors during the

study

Study lasted a year

Policy‐creation Study

Data

slide-41
SLIDE 41

Carnegie Mellon

41

Ideal Policy – Policy the user would enact if not restricted by

technology

Based on interview data Looked at not only what was enacted but endeavored to

determine why

Policy‐creation Study

Ideal Policies

slide-42
SLIDE 42

Carnegie Mellon

42

Policy‐creation Study

Policy Synthesis

Garry Frank Rick Larry Lab True Logged Lab owner is notified Mary Joan . . . . . . Logged Logged False

slide-43
SLIDE 43

Carnegie Mellon

43

True (can access anytime) Logged Owner notified Owner gives real‐time approval Owner gives real‐time approval and witness present Trusted person gives real time approval and is present False (no access)

Policy‐creation Study

Ideal Conditions

slide-44
SLIDE 44

Carnegie Mellon

44

We compared each of the 244 ideal access rules,

with the key and Grey rules and marked them as:

False Accept – User not required to fulfill all conditions

required by the ideal policy

False Reject – User must fulfill conditions not required

by the ideal policy

Faithfully Implemented – Matched the ideal policy

The frequency of false accepts, false rejects and faithful

implementations were counted

Policy‐creation Study

Policy Analysis

slide-45
SLIDE 45

Carnegie Mellon

45

Policy‐creation Study

Policy Analysis Example

Ideal Access anytime Owner notified Logged Keys Has a key Has a key No access

Alice Sue Bob Lab Faithfully implemented False Accept False Reject

slide-46
SLIDE 46

Carnegie Mellon

46

Keys vs Ideal

Lab

User 5 Alice User 23 User 8 User 26 User 19 User 7 Sue User 11 User 15 User 28 User 25 User 21 User 17 User 4 User 27 User 6 User 14 User 10 User 13 User 29 User 22 User 24 Bob User 9 User 12 User 16 User 18 User 20

20 Faithful Implementations (Green) 4 False Accepts (Red) 5 False Rejects (Yellow)

slide-47
SLIDE 47

Carnegie Mellon

47

Policy‐creation Study

Key Conditions

True (can access

anytime)

Logged Owner notified Owner gives real‐time

approval

Owner gives real‐time

approval and witness present

Trusted person gives real

time approval and is present

False (no access) True (has a key) Ask trusted person with key

access

Know location of hidden

key

Ask owner who contacts

witness

False (no access)

? Ideal Keys

slide-48
SLIDE 48

Carnegie Mellon

48

Policy‐creation Study

Key Implementation Accuracy

Ideal Conditions Rules

slide-49
SLIDE 49

Carnegie Mellon

49

Policy‐creation Study

Grey Conditions

True (can access

anytime)

Logged Owner notified Owner gives real‐time

approval

Owner gives real‐time

approval and witness present

Trusted person gives real

time approval and is present

False (no access) True (has a delegation) Ask trusted person with

Grey access

Ask owner via Grey Ask owner who contacts

witness

False (no access)

Ideal Grey

slide-50
SLIDE 50

Carnegie Mellon

50

Policy‐creation Study

Implementation Accuracy

Ideal Conditions Rules

slide-51
SLIDE 51

Carnegie Mellon

51

Grey policies more accurately implemented the desired

policy

Logging, notification and real‐time approval upon request

were desired features

Future work: explore organization‐wide policy and provide

more supportive access‐control technologies

Policy‐creation Study

Conclusion