SolidPass™ uses a robust encryption mechanism appropriate for soft tokens, including a powerful time-based token. The allowed maximum validity period of a generated OTP is set to 3 minutes by default, and the OTP timeout period is a configurable parameter. The shorter the validity period, the higher the security level provided. The length of the OTP also contributes to the security level provided. Longer OTPs make a system more secure. The suggested minimum OTP length in the SolidPass™ System is 8 digits or 6 alphanumeric characters. SolidPass also supports event-based tokens for Linux. The user is provided a numerical password and an algorithm that turns the password into a new number. At the next login, this new number is submitted and checked against what the provider knows the algorithm should have produced. If there is a match, the user is allowed to log in.

SolidPass for Linux is easy to download, install, and use. It provides users with an easy and secure way to access critical information from their Linux machine.

Provisioning of Mobile Token

The application can be provisioned in a number of ways include OTA (Over-the-air), Bluetooth, Wap Push, download, SMS request from a short-code or a long number or from an SMS push from a web interface or a URL from a WAP or mobile Internet portal or from a relevant applications store.

Strong Two-Factor Authentication (2FA)

The following strong authentication methods are supported in the mobile token:

• PIN control mandatory/optional
• Security Question
• Challenge-Response
• Transaction Data Signing (TDS)
• Mutual Authentication

SolidPass mobile security token can be used to prevent the following :

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

Embedded Token

SolidPass™ can be embedded in any number of mobile apps such as mobile banking that would require strong two-factor authentication and security.