Verified Wallet - Revision history

Tom: /* References */

2023-10-10T19:13:34Z

‎References

Tom: /* Full Title or Meme */

2023-10-10T19:12:49Z

‎Full Title or Meme

Tom: /* Problems */

2021-09-21T17:42:31Z

‎Problems

Tom: /* Problems */

2021-09-21T17:29:18Z

‎Problems

Tom at 17:25, 21 September 2021

2021-09-21T17:25:14Z

Tom: /* Requirements */

2021-09-21T16:52:12Z

‎Requirements

Tom: /* Requirements */

2021-09-21T16:38:04Z

‎Requirements

Tom: /* Terminology */

2021-09-21T16:37:26Z

‎Terminology

Tom: /* Requirements */

2021-09-21T16:37:03Z

‎Requirements

Tom: /* Terminology */

2021-09-21T16:34:32Z

‎Terminology

@@ Line 45: / Line 45: @@
 [[Category: Glossary]]
 [[Category: Trust]]
 [[Category: Identifier]]

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
 A [[Verified Wallet]] is a piece of software that can be installed on a mobile computing device with a [[Secure Enclave]] that an  [[App Assessor]] has determined to meet the [[Software Assessment Criteria]] for protecting user data both on-site and in-flight.
 ==Context==

@@ Line 13: / Line 13: @@
 The FTC issued the [https://www.ftc.gov/policy/federal-register-notices/health-breach-notification-rule-final-rule Health Breach Notification Rule], on 2009-08-17 which requires vendors of personal health records and related entities to notify consumers, the FTC, and, in some cases, the media when that data is disclosed '''or acquired without the consumers’ authorization'''. Over a decade later, health apps and other connected devices that collect personal health data are not only mainstream—and have increased in use during the pandemic—but are targets ripe for scammers and other cyber hacks. Yet, there are still too few privacy protections for these apps.
-===Problems===
+==Problems==
 * There are existing policy, procedures and contracts that specified older, obesolete security methods that cannot be just changed without some rule making.
 * For example changing password on a set schedules or odd password complexity rues are still written into contracts.

@@ Line 15: / Line 15: @@
 ===Problems===
 * There are existing policy, procedures and contracts that specified older, obesolete security methods that cannot be just changed without some rule making.
 ==Solutions==

← Older revision		Revision as of 17:25, 21 September 2021
Line 12:		Line 12:

	The FTC issued the [https://www.ftc.gov/policy/federal-register-notices/health-breach-notification-rule-final-rule Health Breach Notification Rule], on 2009-08-17 which requires vendors of personal health records and related entities to notify consumers, the FTC, and, in some cases, the media when that data is disclosed '''or acquired without the consumers’ authorization'''. Over a decade later, health apps and other connected devices that collect personal health data are not only mainstream—and have increased in use during the pandemic—but are targets ripe for scammers and other cyber hacks. Yet, there are still too few privacy protections for these apps.		The FTC issued the [https://www.ftc.gov/policy/federal-register-notices/health-breach-notification-rule-final-rule Health Breach Notification Rule], on 2009-08-17 which requires vendors of personal health records and related entities to notify consumers, the FTC, and, in some cases, the media when that data is disclosed '''or acquired without the consumers’ authorization'''. Over a decade later, health apps and other connected devices that collect personal health data are not only mainstream—and have increased in use during the pandemic—but are targets ripe for scammers and other cyber hacks. Yet, there are still too few privacy protections for these apps.
		+
		+	===Problems===
		+	* There are existing policy, procedures and contracts that specified older, obesolete security methods that cannot be just changed without some rule making.

	==Solutions==		==Solutions==

@@ Line 32: / Line 32: @@
 # Control access to user private information.
 # Establish user intent is freely provided before any protected information is released.
 ==References==

@@ Line 22: / Line 22: @@
 # Trust Authority (The active Trust Authority will be the one involved in a current connection supported by the wallet.)
 # Trusted Service Provider
 # User Private Information.

@@ Line 22: / Line 22: @@
 # Trust Authority (The active Trust Authority will be the one involved in a current connection supported by the wallet.)
 # Trusted Service Provider
 ===Requirements===
@@ Line 27: / Line 29: @@
 # Store in protected storage a user credential that can be used to authenticate the holder to a service provider.
 # Bind the wallet to one (or more) Trust Authorities.
-# Validate any service provider to be sure that it is trusted by the
+# Validate any service provider to be sure that it is trusted by the active Trust Authority.
 ==References==