The SolidPass family of securtiy tokens provide strong authentication. SolidPass helps organizations and entities to realize stronger authentication than a static username and password by providing two-factor authentication. The SolidPass security token is engineered to to dynamically generate a one-time password (OTP). Potential uses of SolidPass include securing access to enterprise applications and vpn connections. The security token can also be used to authenticate users and sign transactions. This is especially useful for online banking and mobile banking security, where it can be embedded in a mobile banking application for seamless authentication.

SolidPass supports the following strong authentication methods:

• Event-based One-Time Password (OTP)
  
• Time-based One-Time Password (OTP)
  
• PIN control mandatory/optional
  
• Security Question
  
• Challenge-Response
• Transaction Data Signing (TDS)
• Mutual Authentication

SolidPass can be used to prevent the following attacks:

• Phishing
• Pharming
• Man-In-The-Middle
• DNS Cache Poisoning
• Trojans
• Man-In-The-Phone
• Browser Poisoning

Mobile Token Convenience

The key advantage of the mobile token is that there are no new devices or wallet-fillers for customers – just an add-on to the device they already carry everywhere. Since customers already own the “hardware” (the mobile phone), SolidPass can be provided and managed at a fraction of the true cost of a hardware token solution. Thanks to its flexible framework, the application can also be updated to guard against new security threats.

SolidPass works on a number of different platforms. The mobile platforms supported are as follows:

• Android
• Blackberry
  
• Brew
• iPhone
• Java ME
• Linux
  
• Palm
• Symbian
• Windows Mobile

Desktop Soft Token

SolidPass also supports desktop-based software tokens as well. The Desktop Operating Systems and Browsers supported are:

• Toolbar Token
  
• Java Token
• Linux Token
  
• Mac Token
  
• Windows Token

Software Token Embedded

SolidPass is a software token built such that it can be used as a standalone product or embedded in mobile applications such as mobile banking.

Thus strong authentication can be built into standalone applications.

Regulatory Compliance

Regulatory requirements are pressuring organizations to adopt strong authentication methods and to secure access to data systems and applications. Static username/password identity management are no longer suitable to authenticate users accurately. This has led to adopting

two-factor authentication systems. Legislation from the Sarbanes-Oxley Act (SOX), guidelines from the Federal Financial Institutions Examination Council (FFIEC), and recommendations from the Health Insurance Portability and Accountability Act (HIPAA) all require that organizations use stronger forms of authentication to mitigate data theft, prevent fraud, protect customer information and patient privacy. SolidPass helps organizations and enterprises keep in compliance with regulatory regimes that cover authorization rules and auditing protocols.

In addition to non-compliance, organizations that continue to use static username/passwords face numerous problems ranging from brute force attacks, dictionary attacks, guessing and social engineering.

OATH

SolidPass is a member of OpenAuthentication.