Difference between revisions of "Notification"

From MgmtWiki
Jump to: navigation, search
(Created page with "==Full Title or Meme== Several best practices and ==Context== The collection of User Private Information by a Data Controller now necessitates the ability Authenti...")
 
Line 1: Line 1:
 
==Full Title or Meme==
 
==Full Title or Meme==
−
Several best practices and  
+
Several best practices and laws require that users are informed of a change of state, or a periodic confirmation of state, then user [[Notification]] is required.
  
 
==Context==
 
==Context==
−
The collection of [[User Private Information]] by a [[Data Controller]] now necessitates the ability [[Authentication|Authenticate]] the [[User]] under a wide range of challenges, like:
+
Whenever a [[Web Site]] encounters a condition that policy or legislation requires that the [[User]] be informed, or when action by the is required, the site needs to put some message in front of the user.
−
# Simplest of all the [[User]] needs to [[Authentication|Authenticate]] from time to time and on a variety of devices under less than ideal conditions where passwords are mistyped and [[Multi-factor Authentication|Alternate Authentication factors]] are lost or fail.
 
−
# More severe [[Recovery]] problems occur when the [[User]] has lost control of their account and needs it to be reset. The level of [[Authentication]] for these situation can be severely taxing to a user desperate for access to their accounts.
 
−
# When an [[Multi-factor Authentication|Authentication factor]] like an alternate email or phone number is compromised, insecure [[Recovery]] methods themselves become a means of attack, especially since factors like phone number were never intended to be secure.<ref>Lily Hay Newman,
 
−
''PHONE NUMBERS WERE NEVER MEANT AS ID. NOW WE’RE ALL AT RISK'' (2018-08-25) Wired Magazine https://www.wired.com/story/phone-numbers-indentification-authentication</ref>
 
  
 
==Problems==
 
==Problems==
−
In [[]] the concepts of [[Security]], [[Privacy]] and [[User Experience]] all collide and make any solution a compromise among competing tendencies.
+
In [[Notification]] the concepts of [[Security]], [[Privacy]] and [[User Experience]] all collide and make any solution a compromise among competing tendencies.
 
===Anti-Pattern===
 
===Anti-Pattern===
 
==Solutions==
 
==Solutions==

Revision as of 11:16, 22 September 2018

Full Title or Meme

Several best practices and laws require that users are informed of a change of state, or a periodic confirmation of state, then user Notification is required.

Context

Whenever a Web Site encounters a condition that policy or legislation requires that the User be informed, or when action by the is required, the site needs to put some message in front of the user.

Problems

In Notification the concepts of Security, Privacy and User Experience all collide and make any solution a compromise among competing tendencies.

Anti-Pattern

Solutions

References

Retrieved from "http://tcwiki.azurewebsites.net/index.php?title=Notification&oldid=3615"