Assurance Enhancements for IdPv2

[Tom Scavo]

On Fri, May 17, 2013 at 6:16 PM, Caskey, Paul <pcaskey at utsystem.edu> wrote:
> One thing that was sort of neat about Duo was that you could consider a NACK of the Duo push to be an account compromise (I think it was Duo who mentioned this).

Randy Frank first mentioned it to me, but yes, that is nice.

> In other words, if my phone lights up and I didn't cause it, then it means my account has been compromised and when I click the red button, our security group should be automatically alerted.

The latest version of Duo Mobile asks the user why they are
disallowing the authentication step. The response is logged in the
admin console, so yes, all kinds of fireworks can be made to happen
(via the admin API).

> If that same dialog is also used for consent, it takes that other security functionality away if I NACK (perhaps).

That's a good point but I claim it boils down to an (interesting) UI
problem. In any case, separating the authentication factors (using the
post-login handler or whatever) permits some interesting flows that
are currently not possible.

Tom