Difference between revisions of "Identity Pathology"

From MgmtWiki
Jump to: navigation, search
(Problems)
(Problems)
Line 28: Line 28:
 
* Spoofing attacks at the resource site.
 
* Spoofing attacks at the resource site.
 
**Online guessing, when user lock-out or time-out is not applied.
 
**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
 
**Reuse or Replay of user credentials
**Binding of attacker's token to the user's profile at the resource
 
 
***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.
 
***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.
 
**Using data acquired by social engineering.
Line 37: Line 37:
 
**Releasing data to others.
 
**Releasing data to others.
 
**Data breaches.
 
**Data breaches.
 +
**Social engineering at provider based on partial knowledge of user private data
  
 
==Solutions==
 
==Solutions==

Revision as of 18:38, 20 June 2018

Full Title or Meme

A list of various ways in which identity information can be misused or misappropriated on the internet.

Context

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 collect a list of the various attacks and their mitigations.

There are three 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.

Problems

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.
    • 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 valuable resources.
    • Misdirection or misleading connection to attacker sites.
    • 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.
      • 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

Solutions

These are the mitigations that should be considered based on the risk profile for the resource being protected.

"Malware" encompasses computer viruses (code injection), computer worms, ransomware, spyware, adware, trojan horses, keyloggers, rootkits, malicious Browser Helper Object (BHOs) etc.

References