An unlocked mobile device can be a treasure trove of private information. Adversaries that are socially close to the user are in a particularly favorable position to explore it: they have access, can observe the victim's authentication code and can even be handed the device for a legitimate task. To address this threat, we propose a new authentication concept that assumes that, by default, a user is authenticating under duress. An inconspicuous side-channel interaction with the device at authentication time dictates whether it grants regular access or enters a secure mode. This paper explores how systems based on this concept can help coping with shoulder-surfing while also allowing for impromptu device sharing.
Security; Mobile; Authentication; Access Control
H.5.m. Information interfaces and presentation (e.g., HCI): Miscellaneous.
Personal mobile devices, like smartphones and tablets, employ unlock authentication has a security mechanism against adversaries with physical access. But these adversaries are not all created equal. While unlock authentication may work as an effective deterrent when a device is lost or stolen, it is hardly a match for socially close adversaries intent on snooping.
Consider the following example: Alice and Eve are roommates. Alice does not like living with Eve and is thinking of moving, but can't tell her before she finds a new roommate. Eve gets suspicious and decides to find out more by looking through Alice's PIN-locked smartphone. She can find out the PIN easily by observing when Alice distractedly enters it. Or she can ask for the device to take a picture of the cat; Alice would never say no.
Access control through knowledge-based authentication (e.g. passwords, graphical codes), however common, is a largely ineffective against adversaries like Eve. Her objective is to snoop though personal communication, which is conveniently centralized in a device she has easy access to. Furthermore, she does not need any technical knowledge to conduct an attack.
Recent work suggest that Eve's behavior is not a corner case. A survey of crowdworkers found that 9% admitted to snopping through someone else's device [8]. Our own data suggests that this number can be as high as 60% among young adult smartphone users [7]. Personal mobile devices store a great deal of information that is considered sensitive, including passwords, files, contacts, emails, text messages, call logs, location traces, schedules, pictures and videos [2, 8]. Exposure of this information is particularly harmful, since it can damage social relationships [5,6].
The authentication moment is at the crux of this vulnerability. Inserting a secret code in the presence of others is potentially dangerous, but understandable. Either for convenience or as not to signal distrust, it must be expected to happen, in a context where mobile devices permeate our social lives [5].
Authentication methods that assume that a user is under threat when entering the code are a possible solution. Panic passwords are used in some security systems, including commercial home alarms. Users can purposefully fail to enter the correct code, and instead enter one that apparently deactivates it, but actually triggers security measures (e.g. calling the police). This concept, however, does not translate directly to securing mobile devices against socially close adversaries. After repeatedly seeing Alice authenticate with the correct code, Eve would be able to tell if she used a different code before sharing the device. The more general concept of duress codes, where the distress is signaled covertly, can be applied. In the TV show "24", fictional counter -terrorism agent Jack Bauer inconspicuously includes the phrase "flank two" when communicating with HQ to indicate that he's compromised. This duress signal, although explicit, is covertly included in the interaction, and is thus undetectable by an unknowing third-party.
We propose a new authentication concept for mobile devices combining features of duress codes (covert signaling) and panic passwords (engaging security measures).
Here we define the main flow of operation and discuss different alternatives for the specific mechanics. The concept is based upon the user resorting to a side-channel to inconspicuously indicate if, upon entering the correct secret code, the system should grant regular access or otherwise trigger security mechanisms. These mechanisms must be such that the third-party does not realize they are in place. We further propose that the security measures are triggered by default. That is, when the covert behavior is not detected, but the correct authentication secret is inserted, the adversary is given some access, although controlled. This concept addresses both a) the handling of attempted unauthorized access and b) impromptu device sharing. Returning to the example:
The side-channel input can be explicit or implicit. An explicit input is a specific, purposeful action by the user. For instance, the user could enter a PIN by clicking all digits on the leftmost side of the button. Implicit input, on the other hand, is based on actions users would carry out anyway [4], i.e. the behavior while authenticating. For instance, while authenticating with Android's pattern unlock, the touch screen data can be used to distinguish the legitimate owner from others [3]
Reacting to the signal: bogus account vs. logging Upon not detecting the covert input, the device enters in a secure mode. As much as possible, its activation should not be transparent the third-party. For instance, if Alice were to share her device using Android's restricted accounts [1] functionality, this would be visible to Eve, and therefore signal distrust. Instead, we propose two possible security mechanisms:
To start assessing this proposal, we conceived of a simple authentication method, based on Android's pattern unlock, that includes an explicit covert action. Namely, after performing the last stroke, making a small movement against the natural flow is required for unlocking.

Figure 1. Instructions on how to perform the side-channel covert code as they were shown to user study participants.
We recruited 8 students and asked them to perform two tasks. Task 1 involved observing, from a front angle, as the experimenter authenticated 3 times and, afterwards, trying to repeat it 10 times. Subjects were told that the objective was to see if they could rotate the pattern mentally. The unlock code would only be accepted if they performed the covert action. Task 2 started by explaining that they had been deceived, showing them the instructions on Figure 1, and having them try again 10 times.
We found that on task 1 the mean success rate was .26 (SD=0.39). This is largely explained by two subjects that perceived the code to have a returning stroke at the end. Although a full stroke was not necessary, it satisfied the criteria of the covert action. Of the remaining 6 users, only one was successful in one of its trials, by accident. This suggests that the covert action was difficult to observe and thus mostly successful as a side-channel code. For task 2, the mean success rate was .9 (SD=.16). Five users were successful on all attempts. This suggests that the explicit covert code is usable with no training.
The authentication method that was evaluated could not be used in the real-world because wide knowledge would render it insecure. It is conceivable that a whole vocabulary of subtle gestures could be made available to the user, which would then be able to compose its personal secret. The evaluated method, nevertheless, speaks to the overall feasibility of using covert codes to cope with shoulder-surfing while supporting impromptu device sharing. Future work will focus on devising methods with large-enough dictionaries of explicit, covert side-channel actions, while still preserving usability. Furthermore, ways to give credibility to bogus accounts will also be investigated.
This work was supported by FCT (SFRH/BD/98527/2013, PTDC/EIA-EIA/117058/2010, PEst-OE/EEI/UI0408/2014).