Trustmark

From IDESG Wiki
Jump to navigation Jump to search

Full Title

The purpose of a Trustmark is to give the users of a web site sufficient information to make an informed decision about whether the site is trustworthy.

Context

Users of the internet today face a daunting array of risks each time they land on a website, including the possibility of the misuse of personal information, outright fraud or theft of credentials, to infection of their computers with malware or viruses.

The primary goals of this effort are to establish a trusted identity:

  1. The user can unambiguously determine the real-world identity (as a real-world Entity name) responsible for any web site that has any pretense to be trustworthy.
  2. The user knows the context that the site operates by the rules of the federation(s) to which the site has subscribed (many need to follow link for details.
  3. The user knows that if the Trustmark is present that it is tested to be valid by the browser (UX will clearly show if not valid)

The secondary goals of this effort are to establish the rules by which the interaction proceeds.:

  1. The user can clearly determine the purpose of the web site, especially in regard to the intent of the site to use their personal information.
  2. The user can stipulate their own conditions on which they are willing to interoperate with the site.

Problems

  • Users do not pay attention to existing Trustmarks.
  • Users not understanding the purposes or meaning of Trustmarks.
  • Existing Trustmarks are trivial to copy on sites that are not trusted.
  • Web site URLs can be spoofed as a result of the many alphabets that are now supported on the web.

Solution

The following are the current characteristics of the new Trustmark:

  1. The mark is cryptographically bound to an Identifier of the current web site which is linked to, but not the same as, its URL.
  2. The Identifier of the site has a signed certificate of membership in the framework that issued the Trustmark.
  3. The companies that report on web site safety (Microsoft, Google, Apple, etc.) are informed of the conditions under which the Trustmark is issued.
  4. The W3C is encouraged to standardize on the method to validate Trustmarks and encourages members to mark any website misuse of the Trustmark as unsafe.
  5. The OpenID Json Web Token (JWT) based as much as possible on the OpenID federation specification.
  6. Kantara proselytizes not only the adoption of the W3C rules, but actively recruits sites to prominently feature the Trustmark and to assist in educating the meaning and benefits to users.

Possible implementation details

  • The Trustmark will be included in an <img> element with a tag that can be recognized by the browser as indicative of a Trustmark.
  • At competition of page load browsers will check for the tag so that they can run a check on the cryptographic binding of the mark.
  • If the check fails two events will occur, the header of the browser will flag the site as unsafe, a message will be sent by the browser to any user authorized malware checker.
  • A new schema is developed for trusted web site Identifiers, e.g. tid:// (if it is a URI) or just tid: (if it is a URN) similar to the did: (which is a URN).

Connecting to the IDEF Registry

The wiki page Trust Framework Membership Validation#Federation_Operator contains information on how the Federation Operator would respond to queries from a Web Site or User Agent. One possible outcome of this effort is the formation of a single Trust Registry that would serve as the root of trust for all Web Site addresses.

References and Coordination

Retrieved from "https://wiki.idesg.org/index.php?title=Trustmark&oldid=12597"