Personal Privacy

From MgmtWiki
Revision as of 08:08, 21 June 2018 by Tom (talk | contribs) (Context)

Jump to: navigation, search

Full Title or Meme

A list of various ways in which user private information can be protected by user actions now and in the future.


Pages on the site where the broad definitions may be found:

  • Privacy is the page where the broad definitions may be found.
  • Identity Pathology is the page where the various vulnerabilities are delineated.

User private data is required for release of web resources. Minimizing the amount of data released or its misuse after release is the object of this effort to list the steps that can be taken today by user as well as the developments that are still evolving.

There are four entities that are in play here.

  1. The user on a user device (aka a user agent).
  2. The resource provider (aka a relying party.)
  3. Identifier and Attribute Providers.
  4. Data Harvester or Broker


Threats against authentication, federation or user private data, as that can be used in spoofing.

  • Attacks at the user device or user agent.
    • User private data, including credentials used in authentication or secret seed value.
    • Theft of user device or second factor token
    • Data of the user's contacts' email address for spamming.
    • Insertion of malware on the user's device.
    • Interception of legitimate user connections to valuable resources, including elevation of priviledge.
  • Attacks on the transmission of user private data.
    • Interception of legitimate user connections to steal authentication data.
    • Misdirection or misleading connection to attacker sites.
    • Hijacking a legitimate user connection (Man in the middle attacks).
  • Spoofing attacks at the resource site.
    • Online guessing, when user lock-out or time-out is not applied.
    • Binding of attacker's token to the user's profile at the resource
    • Reuse or Replay of user credentials
      • User reliance on passwords alone is known to result in password reuse, so if an attack succeeds on one site, it may work on others.
    • Using data acquired by social engineering, such as using a pretext for the user to enable the authentication.
      • Complex passwords that are unique to one site or service will force users to write down passwords which can be found.
    • Initiating connections through other compromised sites, including compromised Identifier or Attribute Providers.
  • Misuse of user private data.
    • Releasing data to others.
    • Data breaches.
    • Social engineering at provider based on partial knowledge of user private data


These are the steps that should be considered now

These are some of the steps under development