User Private Information

From IDESG Wiki
Revision as of 18:17, 23 January 2017 by Tom Jones (Talk) (2=Weakly Authenticated)

Jump to: navigation, search


Most of the discussion of user authentication is based on NIST Special Publication 800-63-2 and the Levels of Authentication (LOA). This page looks at user authentication from the point of view of the user and so will exhibit the status of authentication from the view of the information that the user needs to provide for the session to be authorized to achieve the users intentions.

The only function of the internet is to move information from one point to another point. The internet protocols structure data and provide context that allows the systems communicating on the internet to infer meaning. It is the action that information has when it moves from one site to another that unlocks the full potential of the internet. This page address the visibility to the user as to the amount of information that a user needs to provide to a relying party (RP) web site to achieve their goals.


Web sites are more easily transparent about what personal information from users the plan to use and reference.

Specifically there will be some icon which will be always visible to the user that will instantly inform them of the amount of personal information that is expected by the site they are currently viewing.


This is a proposal to the UX committee on the way to display the current privacy context to the user.

The Content

The Problem

Users move between privacy contexts on a single display device and are not sure what level of personal information they have agreed to share in the current context.

When to use this Solution

The user is on an internet connected display device using a browser or other HTML display screen. This solution is based on a display to the user by a Relying Party (RP). It is expected that the same values could be used by other entities, like an IdP.

User Identity Status Levels

These levels are created specifically to give the user feedback on the risk to their private information.


The user provides no information and the RP does not try to link the user by placing cookies or other tracking methods.


The user provides or permits some credential that can be reused over time to link a continued presence. The RP does not try to link the user to a human. The user implicitly intends to assert DO NOT TRACK.

LOA 1 or 2

2=Weakly Authenticated

The user is associated with an identifier that may be linked from one site to another under limited conditions permitted by the user expressed intent.

LOA 1 or 2 if provided by the user. Note that the identifier may be supplied by the RP.

3=Strongly Authenticated

The RP has some specific requirement to know the identity of the use, such a KYC regulations for a bank.


4=User Identity Proofed in Person

The user has some legal obligation to be well-known to the system in order to be authorized to perform their duties. The user will have some physical authentication factor like a CAC or PIV card.