A Framework for Reasoning About the Human in the Loop

By Lorrie Faith Cranor. UPSEC, 2008

384 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/c6e8d366fc185801995423a2cbe5d54b4ce31103

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

Scaling the Security Wall: Developing a Security Behavior Intentions Scale (SeBIS) (2015, background): “, [47, 9, 30]), which researchers have used to offer recommendations.”
Predicting phishing websites based on self-structuring neural network (2013, background): “they are focused on their main tasks, while paying attention to security indicators is considered secondary task [6].”
Takeover Time in Highly Automated Vehicles: Noncritical Transitions to and From Manual Control (2017, background): “…increase of reaction times when drivers are engaged in other tasks will have to be expected, but measures must be taken to reduce the increase in reaction time, for example, through the addition of informative displays, to reduce the risk of accidents (Cranor, 2008; Eriksson & Stanton, 2016).”
Crying Wolf: An Empirical Study of SSL Warning Effectiveness (2009, background): “Thus users’ attitudes and beliefs about SSL warnings are likely to undermine their effectiveness [3].”
A Survey of Human-in-the-loop for Machine Learning (2021, methodology): “Systems Application Year Role of human Description Quantitative resultsSECS CP SIMS SE Others Supervisor Supervisee Collaborator User Brostoff & Sasse [117] X 2001 X X Security system for traditional tasks −− Cranor [118] X 2008 X X Security system for traditional tasks −− MacHiry et al. [119] X 201”
You Get Where You're Looking for: The Impact of Information Sources on Code Security (2016, methodology): “We deliberately minimized security priming to account for the fact that security and privacy are generally secondary tasks compared to basic app functionality [2], [10], [18], [19].”
Android permissions: user attention, comprehension, and behavior (2012, methodology): “Cranor used the C-HIP model as the basis for her “human in the loop” framework, which addresses problems for designers of interactive systems [11].”
Teaching Johnny not to fall for phish (2010, background): “These categories of anti-phishing strategies mirror the three high-level approaches to usable security discussed in the literature: build systems that “just work” without requiring intervention on the part of users, make security intuitive and easy to use, and teach people how to perform security-cr”
A Design Space for Effective Privacy Notices (2015, methodology): “According to the C-HIP model [32, 132], users process warning messages by switching their attention to them, extracting relevant information from the warning, and comprehending the information; a user’s attitudes and beliefs determine if the user acts on the warning.”