Phone as Personal Identifier Provider - Revision history

Tomjones: /* References */

2020-05-24T17:40:23Z

References

← Older revision		Revision as of 17:40, 24 May 2020
Line 32:		Line 32:
	* [https://identity.foundation/did-siop/ Self-Issued OpenID Connect Provider DID Profile] DIF Working Group Draft		* [https://identity.foundation/did-siop/ Self-Issued OpenID Connect Provider DID Profile] DIF Working Group Draft
	*[https://www.theverge.com/2019/4/10/18295348/google-android-phone-fido-webauthn-phishing-two-factor-authentication Google will now let you use your Android phone as a physical security key] using the phone and PC blue tooth connection.		*[https://www.theverge.com/2019/4/10/18295348/google-android-phone-fido-webauthn-phishing-two-factor-authentication Google will now let you use your Android phone as a physical security key] using the phone and PC blue tooth connection.
	*[[Phone as Health Care Credential]]		*[[Phone as Health Care Credential]] is one specific vertical instance which was created before this proposal.
	*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]		*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]
	*[https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-11/EPC%20269-19v1.0%20Mobile%20Initiated%20SEPA%20%28Instant%29%20Credit%20Transfer%20Interoperability%20Guidance%20%28MSCT%20IG%29.pdf Mobile Initiated SEPA (Instant) Credit Transfer (MSCT) Interoperability Guidance] from the European Payments Council (EPC) AISBL contains many use case. Many of the use cases appear to require more user entered data than users are likely to tolerate.		*[https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-11/EPC%20269-19v1.0%20Mobile%20Initiated%20SEPA%20%28Instant%29%20Credit%20Transfer%20Interoperability%20Guidance%20%28MSCT%20IG%29.pdf Mobile Initiated SEPA (Instant) Credit Transfer (MSCT) Interoperability Guidance] from the European Payments Council (EPC) AISBL contains many use case. Many of the use cases appear to require more user entered data than users are likely to tolerate.

Tomjones: /* References */

2020-05-24T17:38:44Z

References

← Older revision		Revision as of 17:38, 24 May 2020
Line 30:		Line 30:
	==References==		==References==
	* This wiki page is derived, in part, from the [[Privacy Enhanced by User Agent]] created by Tom Jones in September 2013.		* This wiki page is derived, in part, from the [[Privacy Enhanced by User Agent]] created by Tom Jones in September 2013.
			* [https://identity.foundation/did-siop/ Self-Issued OpenID Connect Provider DID Profile] DIF Working Group Draft
	*[https://www.theverge.com/2019/4/10/18295348/google-android-phone-fido-webauthn-phishing-two-factor-authentication Google will now let you use your Android phone as a physical security key] using the phone and PC blue tooth connection.		*[https://www.theverge.com/2019/4/10/18295348/google-android-phone-fido-webauthn-phishing-two-factor-authentication Google will now let you use your Android phone as a physical security key] using the phone and PC blue tooth connection.
	*[[Phone as Health Care Credential]]		*[[Phone as Health Care Credential]]
	*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]		*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]
	*[https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-11/EPC%20269-19v1.0%20Mobile%20Initiated%20SEPA%20%28Instant%29%20Credit%20Transfer%20Interoperability%20Guidance%20%28MSCT%20IG%29.pdf Mobile Initiated SEPA (Instant) Credit Transfer (MSCT) Interoperability Guidance] from the European Payments Council (EPC) AISBL contains many use case. Many of the use cases appear to require more user entered data than users are likely to tolerate.		*[https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-11/EPC%20269-19v1.0%20Mobile%20Initiated%20SEPA%20%28Instant%29%20Credit%20Transfer%20Interoperability%20Guidance%20%28MSCT%20IG%29.pdf Mobile Initiated SEPA (Instant) Credit Transfer (MSCT) Interoperability Guidance] from the European Payments Council (EPC) AISBL contains many use case. Many of the use cases appear to require more user entered data than users are likely to tolerate.

Tomjones: /* Context */

2020-05-24T17:34:11Z

Context

← Older revision		Revision as of 17:34, 24 May 2020
Line 2:		Line 2:
	Mobile Device Security: Phone as Personal Identifier Provider (PPIP)		Mobile Device Security: Phone as Personal Identifier Provider (PPIP)
	==Context==		==Context==
			This is an extension of the [[Phone as Health Care Credential]] proposal to a broader audience of teams interested in high assurance [[Authentication]].

	==Challenge==		==Challenge==

Tomjones at 17:13, 24 May 2020

2020-05-24T17:13:59Z

← Older revision		Revision as of 17:13, 24 May 2020
Line 2:		Line 2:
	Mobile Device Security: Phone as Personal Identifier Provider (PPIP)		Mobile Device Security: Phone as Personal Identifier Provider (PPIP)
	==Context==		==Context==
	* This paper is designed to be a proposal to NIST for a SP 1800-xx document in their series of Cybersecure Infrastructure papers.
	* It is an extension of the Kantara work to provide such a solution for US Healthcare.
	* The following are the 3 parts of a sp 1800 document. We propose an outline of the first part below:
	~~#SP 1800-xxA: Executive Summary (PDF)~~
	~~#SP 1800-xxB: Approach, Architecture, and Security Characteristics (PDF)~~
	~~#SP 1800-xxC: How-To Guides (PDF)~~
	==Challenge==		==Challenge==
	* User want to be in control of their own private information.		* User want to be in control of their own private information.
Line 25:		Line 20:
	* The user feels like, and is, in control of their data sharing.		* The user feels like, and is, in control of their data sharing.

			==Next Steps==
			* This paper is designed to be a proposal to NIST for a SP 1800-xx document in their series of Cybersecure Infrastructure papers.
			* It is an extension of the Kantara work to provide such a solution for US Healthcare.
			* The following are the 3 parts of a sp 1800 document. We propose an outline of the first part below:
			#SP 1800-xxA: Executive Summary (PDF)
			#SP 1800-xxB: Approach, Architecture, and Security Characteristics (PDF)
			#SP 1800-xxC: How-To Guides (PDF)
	==References==		==References==
	* This wiki page is derived, in part, from the [[Privacy Enhanced by User Agent]] created by Tom Jones in September 2013.		* This wiki page is derived, in part, from the [[Privacy Enhanced by User Agent]] created by Tom Jones in September 2013.

Tomjones: /* Benefits */

2020-04-09T16:52:53Z

Benefits

← Older revision		Revision as of 16:52, 9 April 2020
Line 23:		Line 23:

	==Benefits==		==Benefits==
	* The ~~Age~~ of ~~Aquarius reigns~~.		* The user feels like, and is, in control of their data sharing.

	==References==		==References==

Tomjones: /* References */

2019-12-11T19:43:54Z

References

← Older revision		Revision as of 19:43, 11 December 2019
Line 30:		Line 30:
	*[[Phone as Health Care Credential]]		*[[Phone as Health Care Credential]]
	*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]		*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]
	*[https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-11/EPC%20269-19v1.0%20Mobile%20Initiated%20SEPA%20%28Instant%29%20Credit%20Transfer%20Interoperability%20Guidance%20%28MSCT%20IG%29.pdf Mobile Initiated SEPA (Instant) Credit Transfer (MSCT) Interoperability Guidance] from the European Payments Council (EPC) AISBL contains many use case. Many of the use cases appear to require more ~~use~~ entered data than users are likely to ~~accept~~.		*[https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-11/EPC%20269-19v1.0%20Mobile%20Initiated%20SEPA%20%28Instant%29%20Credit%20Transfer%20Interoperability%20Guidance%20%28MSCT%20IG%29.pdf Mobile Initiated SEPA (Instant) Credit Transfer (MSCT) Interoperability Guidance] from the European Payments Council (EPC) AISBL contains many use case. Many of the use cases appear to require more user entered data than users are likely to tolerate.

Tomjones: /* References */

2019-12-11T18:46:04Z

References

← Older revision		Revision as of 18:46, 11 December 2019
Line 30:		Line 30:
	*[[Phone as Health Care Credential]]		*[[Phone as Health Care Credential]]
	*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]		*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]
	*[https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-11/EPC%20269-19v1.0%20Mobile%20Initiated%20SEPA%20%28Instant%29%20Credit%20Transfer%20Interoperability%20Guidance%20%28MSCT%20IG%29.pdf Mobile Initiated SEPA (Instant) Credit Transfer (MSCT) Interoperability Guidance] from the European Payments Council (EPC) AISBL		*[https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-11/EPC%20269-19v1.0%20Mobile%20Initiated%20SEPA%20%28Instant%29%20Credit%20Transfer%20Interoperability%20Guidance%20%28MSCT%20IG%29.pdf Mobile Initiated SEPA (Instant) Credit Transfer (MSCT) Interoperability Guidance] from the European Payments Council (EPC) AISBL contains many use case. Many of the use cases appear to require more use entered data than users are likely to accept.

Tomjones: /* References */

2019-12-11T18:40:49Z

References

← Older revision		Revision as of 18:40, 11 December 2019
Line 30:		Line 30:
	*[[Phone as Health Care Credential]]		*[[Phone as Health Care Credential]]
	*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]		*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]
	*[https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-11/EPC%20269-19v1.0%20Mobile%20Initiated%20SEPA%20%28Instant%29%20Credit%20Transfer%20Interoperability%20Guidance%20%28MSCT%20IG%29.pdf Mobile Initiated SEPA (Instant) Credit Transfer Interoperability Guidance] from the European Payments Council (EPC) AISBL		*[https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-11/EPC%20269-19v1.0%20Mobile%20Initiated%20SEPA%20%28Instant%29%20Credit%20Transfer%20Interoperability%20Guidance%20%28MSCT%20IG%29.pdf Mobile Initiated SEPA (Instant) Credit Transfer (MSCT) Interoperability Guidance] from the European Payments Council (EPC) AISBL

Tomjones: /* References */

2019-12-11T18:38:41Z

References

← Older revision		Revision as of 18:38, 11 December 2019
Line 30:		Line 30:
	*[[Phone as Health Care Credential]]		*[[Phone as Health Care Credential]]
	*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]		*[https://csrc.nist.gov/publications/detail/sp/1800-21/draft SP 1800-21 (DRAFT) Mobile Device Security: Corporate-Owned Personally-Enabled (COPE)]
			*[https://www.europeanpaymentscouncil.eu/sites/default/files/kb/file/2019-11/EPC%20269-19v1.0%20Mobile%20Initiated%20SEPA%20%28Instant%29%20Credit%20Transfer%20Interoperability%20Guidance%20%28MSCT%20IG%29.pdf Mobile Initiated SEPA (Instant) Credit Transfer Interoperability Guidance] from the European Payments Council (EPC) AISBL

Tomjones: /* Mobile Identifier Sources */

2019-11-27T22:41:12Z

Mobile Identifier Sources

← Older revision		Revision as of 22:41, 27 November 2019
Line 20:		Line 20:
	===Mobile Identifier Sources===		===Mobile Identifier Sources===
	* [https://ims.ul.com/interoperability-mobile-driver-license-mdl-application Interoperability with Mobile Driver's Licence]		* [https://ims.ul.com/interoperability-mobile-driver-license-mdl-application Interoperability with Mobile Driver's Licence]
	8 [[Phone as Health Care Credential]]		* [[Phone as Health Care Credential]]

	==Benefits==		==Benefits==