Difference between revisions of "Trusted First Party"

Revision as of 15:45, 13 April 2021

Any Web Site that the user trusts.

Identifying a Trusted First Party has traditionally been handled by the User Agent or browsers. in 2020 nearly all browsers insist that web sites have X509 SSL certificates unless the user decides to ignore the warnings that block easy access to the site.
Single Sign on providers have typically used commercial means to establish trust with users.

Any party that holds User Information has the possibility of breach of trust that the information will not be released.

Some types of Trusted Third Party include:

Privacy Enhancing Technology Providers (PETP) can protect user's privacy by anonymizing the User's Identifier. See Microsoft UProve.^[1] or IBM Identity Mixer.^[2]
Governmental agencies that hold data for legitimate purposes will typically have a legal mandate to protect the data. Unfortunately they also have sovereign immunity should a breach be discovered.

A Trusted Third Party may be valuable in any use case where the user wants to be have some Assurance about privacy of data that does need to be shared in very limited circumstances.

@@ Line 3: / Line 3: @@
 ==Context==
-Identifying a [[Trusted First Party]] has traditionally been handled by the [[User Agent]] or browsers.
+* Identifying a [[Trusted First Party]] has traditionally been handled by the [[User Agent]] or browsers. in 2020 nearly all browsers insist that web sites have X509 SSL certificates unless the user decides to ignore the warnings that block easy access to the site.
+* Single Sign on providers have typically used commercial means to establish trust with users.
 ==Problems==