Why Hasn't This Been Done Before?

This approach to accessing Web sites and SaaS providers has not been done before, for several reasons:

  • Complex Technology:
    • SSL/TLS and digital certificates are complex technologies that are not widely understood in detail even in IT or security groups.
    • It is not widely known that browsers support digital certificates or how TLS combats phishing.  
       
  • Today's Service Models are Different:
    • Several firms offer digital certificates to end users today.  However, they are focused on INTRA enterprise usage.  Pseudo-Nym is focused on INTER enterprise usage.
    • Those firm's include the owner's legal identity in the certificate.  This increases costs, overhead and liability dramatically.  Pseudo-Nym offers a pseudo identity in the certificate.
       
  • Many Disparate Technologies:
    • The technologies used to support digital certificates and TLS are disparate. They include:
      • X.509 Digital Certificates
      • Public Key Infrastructure and Certificate Authority
      • Online Certificate Status Protocol
      • Transport Layer Security 
      • Trusted Platform Module
      • Active Directory
    • Pseudo-Nym brings them all together as a service to solve the problem of too many unmanaged passwords.
       
  • Complexity and Inertia
    • In spite of their weaknesses, UserID's and Passwords are widely used and understood. 
    • Digital Certificates and TLS are complex technologies that are not as widely understood and work behind the scenes, invisible to the end user.
    • Finally, this solution requires changes by both the end user or their corporate sponsor and participating web sites.  This presents a 'chicken or the egg' problem.