Trusted Identifier - Revision history

Tom: /* Context */

2021-09-05T22:09:27Z

‎Context

Tom: /* Context */

2021-09-05T22:08:44Z

‎Context

Tom: /* Context */

2021-09-05T22:07:30Z

‎Context

Tom: /* Context */

2021-09-05T22:07:05Z

‎Context

Tom: /* Context */

2021-09-05T22:06:46Z

‎Context

Tom: /* Context */

2021-09-03T23:53:40Z

‎Context

Tom: /* Problems */

2021-09-03T23:52:12Z

‎Problems

Tom: /* Context */

2021-09-03T23:51:44Z

‎Context

Tom: /* Context */

2021-09-03T23:50:00Z

‎Context

Tom: /* Context */

2021-09-03T23:46:28Z

‎Context

@@ Line 9: / Line 9: @@
 *Legal entities, like corporations, are not permitted to hide their real world [[Identity]] although many jump though many legal loopholes to try to distance themselves from discovery.
 *A [https://tools.ietf.org/html/rfc7591#section-2.3 software statement] is a [https://tools.ietf.org/html/rfc7519 JSON Web Token (JWT)] that asserts metadata values about the client software as a bundle. It is also defined in the [https://openbanking.atlassian.net/wiki/spaces/DZ/pages/36667724/The+OpenBanking+OpenID+Dynamic+Client+Registration+Specification+-+v1.0.0-rc2#TheOpenBankingOpenIDDynamicClientRegistrationSpecification-v1.0.0-rc2-SoftwareStatementAssertion(SSA) UK Open banking standards.] Whatever it might have been designed to accomplish, it has been used to identifier the owner of a [[Web Site]] endpoint. It will typically include some sort of GUID for the specific instance, but that is often incidental to its real use as a [[Web Platform Identifier]].
-* While [[Trusted Identifier]]s were the focus of [https://www.nist.gov/itl/applied-cybersecurity/tig NIST Trusted Identity] and the IDESG, the term has fallen out of favor since [[NSTIC]] fell out of favor with the change in administrations. The new buzz word for the Biden administration is cybersecure and zero trust.
+* While [[Trusted Identifier]]s were the focus of [https://www.nist.gov/itl/applied-cybersecurity/tig NIST Trusted Identity] and the IDESG, the term has fallen out of favor since [[NSTIC]] fell out of favor with the change in administrations. The new buzz words for the Biden administration are cybersecure and zero trust.
 ===The Goal===

@@ Line 9: / Line 9: @@
 *Legal entities, like corporations, are not permitted to hide their real world [[Identity]] although many jump though many legal loopholes to try to distance themselves from discovery.
 *A [https://tools.ietf.org/html/rfc7591#section-2.3 software statement] is a [https://tools.ietf.org/html/rfc7519 JSON Web Token (JWT)] that asserts metadata values about the client software as a bundle. It is also defined in the [https://openbanking.atlassian.net/wiki/spaces/DZ/pages/36667724/The+OpenBanking+OpenID+Dynamic+Client+Registration+Specification+-+v1.0.0-rc2#TheOpenBankingOpenIDDynamicClientRegistrationSpecification-v1.0.0-rc2-SoftwareStatementAssertion(SSA) UK Open banking standards.] Whatever it might have been designed to accomplish, it has been used to identifier the owner of a [[Web Site]] endpoint. It will typically include some sort of GUID for the specific instance, but that is often incidental to its real use as a [[Web Platform Identifier]].
-* While [[Trusted Identifier]]s were the focus of [https://www.nist.gov/itl/applied-cybersecurity/tig NIST Trusted Identity] and the IDESG, the term has fallen out of favor since [[NSTIC]] fell out of favor with the change in administrations.
+* While [[Trusted Identifier]]s were the focus of [https://www.nist.gov/itl/applied-cybersecurity/tig NIST Trusted Identity] and the IDESG, the term has fallen out of favor since [[NSTIC]] fell out of favor with the change in administrations. The new buzz word for the Biden administration is cybersecure and zero trust.
 ===The Goal===

@@ Line 9: / Line 9: @@
 *Legal entities, like corporations, are not permitted to hide their real world [[Identity]] although many jump though many legal loopholes to try to distance themselves from discovery.
 *A [https://tools.ietf.org/html/rfc7591#section-2.3 software statement] is a [https://tools.ietf.org/html/rfc7519 JSON Web Token (JWT)] that asserts metadata values about the client software as a bundle. It is also defined in the [https://openbanking.atlassian.net/wiki/spaces/DZ/pages/36667724/The+OpenBanking+OpenID+Dynamic+Client+Registration+Specification+-+v1.0.0-rc2#TheOpenBankingOpenIDDynamicClientRegistrationSpecification-v1.0.0-rc2-SoftwareStatementAssertion(SSA) UK Open banking standards.] Whatever it might have been designed to accomplish, it has been used to identifier the owner of a [[Web Site]] endpoint. It will typically include some sort of GUID for the specific instance, but that is often incidental to its real use as a [[Web Platform Identifier]].
-* While [[Trusted Identifier]]s were the focus of [https://www.nist.gov/itl/applied-cybersecurity/tig NIST Trusted Identity] and the IDESG, the term have fallen out of favor since [[NSTIC]] fell out of favor with the change in administrations.
+* While [[Trusted Identifier]]s were the focus of [https://www.nist.gov/itl/applied-cybersecurity/tig NIST Trusted Identity] and the IDESG, the term has fallen out of favor since [[NSTIC]] fell out of favor with the change in administrations.
 ===The Goal===

@@ Line 9: / Line 9: @@
 *Legal entities, like corporations, are not permitted to hide their real world [[Identity]] although many jump though many legal loopholes to try to distance themselves from discovery.
 *A [https://tools.ietf.org/html/rfc7591#section-2.3 software statement] is a [https://tools.ietf.org/html/rfc7519 JSON Web Token (JWT)] that asserts metadata values about the client software as a bundle. It is also defined in the [https://openbanking.atlassian.net/wiki/spaces/DZ/pages/36667724/The+OpenBanking+OpenID+Dynamic+Client+Registration+Specification+-+v1.0.0-rc2#TheOpenBankingOpenIDDynamicClientRegistrationSpecification-v1.0.0-rc2-SoftwareStatementAssertion(SSA) UK Open banking standards.] Whatever it might have been designed to accomplish, it has been used to identifier the owner of a [[Web Site]] endpoint. It will typically include some sort of GUID for the specific instance, but that is often incidental to its real use as a [[Web Platform Identifier]].
-* While [[Trusted Identifier]]s were the focus of [https://www.nist.gov/itl/applied-cybersecurity/tig NIST Trusted Identity]] and the IDESG, the term have fallen out of favor since [[NSTIC]] fell out of favor with the change in administrations.
+* While [[Trusted Identifier]]s were the focus of [https://www.nist.gov/itl/applied-cybersecurity/tig NIST Trusted Identity] and the IDESG, the term have fallen out of favor since [[NSTIC]] fell out of favor with the change in administrations.
 ===The Goal===

@@ Line 9: / Line 9: @@
 *Legal entities, like corporations, are not permitted to hide their real world [[Identity]] although many jump though many legal loopholes to try to distance themselves from discovery.
 *A [https://tools.ietf.org/html/rfc7591#section-2.3 software statement] is a [https://tools.ietf.org/html/rfc7519 JSON Web Token (JWT)] that asserts metadata values about the client software as a bundle. It is also defined in the [https://openbanking.atlassian.net/wiki/spaces/DZ/pages/36667724/The+OpenBanking+OpenID+Dynamic+Client+Registration+Specification+-+v1.0.0-rc2#TheOpenBankingOpenIDDynamicClientRegistrationSpecification-v1.0.0-rc2-SoftwareStatementAssertion(SSA) UK Open banking standards.] Whatever it might have been designed to accomplish, it has been used to identifier the owner of a [[Web Site]] endpoint. It will typically include some sort of GUID for the specific instance, but that is often incidental to its real use as a [[Web Platform Identifier]].
 ===The Goal===

@@ Line 5: / Line 5: @@
 * It is common by 2020 for all web sites to have a [https://en.wikipedia.org/wiki/Transport_Layer_Security TLS] (SSL) certificate so that they can establish a trusted connection between the [[User Agent]] (typical the local browser) and the web site. This trusted connection prevents tampering or eavesdropping on the connection which solves some of the security and privacy issues on the open web. This wiki page looks at the issues associated with the users' trust of the web site that is needed before sharing [[User Private Information]] with the site.
 *Individuals have [[Identifier]]s that must be associated with the real world person even if access to that [[Identifier]] is lost for any reason. Health care is one good requirement for a high assurance [[Health Care Digital Identity]].
-* Individuals have rights to [[Privacy]] that do not apply to enterprises and so are treated on other wiki pages. This wiki page focus on the Enterprise need for a high assurance [[Trusted Identifier]].
+* Individuals have rights to [[Privacy]] that do not apply to enterprises and so are treated on other wiki pages. This wiki page focus on user's need to understand the identity and reputation of the web site that is asking for access to their information.
 * Other wiki pages focus on digital endpoints that are called [[Web Platform Identifier]] or [[Trusted Location]]s. This page is focused on the link from the digital entity to the real-world entity that the user can trust.
 *Legal entities, like corporations, are not permitted to hide their real world [[Identity]] although many jump though many legal loopholes to try to distance themselves from discovery.

@@ Line 14: / Line 14: @@
 ==Problems==
-* See the wiki page on [[Trusted Location]] for a list of the ways that a URL can be spoof to see why it is a bad idea to expect users to get a [[Trusted Identifier]] from a URL.
+* See the wiki page on [[Trusted Location]] for a list of the ways that a URL can be spoof to see why it is a bad idea to expect users to get a [[Trusted Identifier]] from the web site's URL.
 * [[EV Cert]]s were introduced to give user's good knowledge of who was behind a web site. They didn't work out as planned as shown on the [[EV Cert]] wiki page.

@@ Line 3: / Line 3: @@
 ==Context==
-* It is common by 2020 for all web sites to have a [https://en.wikipedia.org/wiki/Transport_Layer_Security TLS] (SSL) certificate so that they can establish a trusted connection between the [[User Agent]] (typical the local browser) and the web site. This trusted connection prevents tampering or eavesdropping on the connection which solves some of the security and privacy issues on the open web. This wiki page looks at the issues associated with the users' trust of the web site that is needed before sharing user private information with the site.
+* It is common by 2020 for all web sites to have a [https://en.wikipedia.org/wiki/Transport_Layer_Security TLS] (SSL) certificate so that they can establish a trusted connection between the [[User Agent]] (typical the local browser) and the web site. This trusted connection prevents tampering or eavesdropping on the connection which solves some of the security and privacy issues on the open web. This wiki page looks at the issues associated with the users' trust of the web site that is needed before sharing [[User Private Information]] with the site.
 *Individuals have [[Identifier]]s that must be associated with the real world person even if access to that [[Identifier]] is lost for any reason. Health care is one good requirement for a [[Trusted Identifier]].
 * Individuals have rights to [[Privacy]] that do not apply to enterprises and so are treated on other wiki pages. This wiki page focus on the Enterprise need for a solid [[Trusted Identifier]].