The SafeNet OTP 111 and SafeNet OTP 112 are OATH-certified OTP devices enabling user authentication to a broad range of resources. Featuring time and event-based configurations and waterproof casing, the SafeNet OTP 111 and SafeNet OTP 112 OTP tokens can be used anywhere a static password is used today, improving security and allowing regulatory compliance with a broad range of industry regulations. These OTP devices replace our market-proven SafeNet OTP 110 token, offering full backward compatibility with the OTP 111 and compliance with the latest standards with the OTP 112. SafeNet OTP 111 replaces SafeNet OTP 110 and SafeNet OTP 112 replaces eToken PASS.
Secure Access to Cloud, VPN and On Prem Resources
OTP authentication helps organizations eliminate the risk associated with fixed passwords and increase the security of user access controls implemented to protect local network access, remote network (VPN) access, cloud-based applications, VDI, web portals and custom applications.
Supported by SafeNet Authentication Service solutions
SafeNet OTP 111 and SafeNet OTP 112 OTP tokens are available with SafeNet Authentication Service Private Cloud Edition (SAS PCE) and SafeNet Trusted Access (STA) solutions that delivers fully-automated, highly secure authentication with flexible token options that are tailored to the unique needs of your organization, substantially reducing the total cost of operation:
SafeNet Trusted Access (STA), which is a cloud access management service that offers policy-based access management and multi-factor authentication, allowing to manage, maintain, and provision a wide-range of tokens.
SafeNet Authentication Service Private Cloud Edition (SAS PCE), which is an on-premises authentication management solution that can be used to extend authentication services beyond the corporate perimeter. Users can authenticate with the same user ID and token(s) that they use for the corporate network.
Main features and benefits of SafeNet OTP 111-112 OTP devices
Comply with market regulations
- Can be used within MFA (Multi-Factor Authentication) systems
- OATH certified
Easy to carry
- Can be carried on a key ring
Easy to use
- PC independent: Press the button and get your OTP
Secure access to various systems
- Networks (VPNs)
- SaaS applications
- VDI
- Web portals
- Custom applications
Easy to manage
- Effortless back-end configuration
- Low maintenance
- Long lasting battery duration
- Robust design
Customizable
- Case color
- Logo
- OTP length
- Event or time based
Token Build
- Single button
- No PIN needed
- LCD display of up to eight digits
- High contrast single line display
- Unconnected key fob token with keychain ring holder
OTP Security Algorithm
Available in two configurations:
- Support of Hmac SHA1 (OTP 111) or Hmac SHA256 (OTP 112)
- Event-based OTP ( OATH H-OTP)—on demand
- Time-synced OTP (OATH T-OTP)—on demand
OTP length
- 6-8 digits
- “Grouped” display option
Battery Lifetime
- Approximately 7 years
Casing
- Default color: Black
- Case color and logo are customizable for large orders, min. 5k tokens
- Serial number printed on the back
- Waterproof IP67
Supported Management Platforms
- SafeNet Trusted Access (STA)
- SafeNet Authentication Service Private Cloud Edition (SAS PCE)
Certifications and Compliance
- OATH compliant
- CE - CEM & Europe security
- FCC - CEM USA (FCC part 15, UL 1950)
- ROHS compliant
- WEEE (environment friendly)
Recommended resources
Frequently Asked Questions
OTP means One Time Passcode or One Time Password. OTP is an authentication method replacing traditional weak password by a code that is valid for only one login session on a computer system or other digital service.
OATH is an open reference architecture for implementing strong authentication, produced by an industry-wide collaboration of security vendors for the universal adoption of strong authentication. The OATH standard can be used by IT and security professionals as a template for integrating strong authentication into their organisation’s current infrastructure.
Learn more about OATH authentication tokens
Yes, both tokens are OATH certified.
No, they are 1FA tokens (what you have) that can be integrated into MFA systems.
Yes, both tokens are compatible with SafeNet Trusted Access and SAS PCE.
For more information:
Yes
To access a digital resource, the users enter their username and the numeric code generated by the OTP device. The authentication server validates the code and access is granted to the appropriate digital resource.
The difference is the algorithm used for the OTP generation:
- SafeNet OTP 111 supports Hmac SHA1
- SafeNet OTP 112 supports Hmac SHA256. For more details refer to SafeNet OTP 111 and SafeNet OTP 112 – Product Brief
SafeNet OTP 110 is the previous version of SafeNet OTP 111.
Hash-based OTP (HOTP): OTP is generated and sent to a user, based on a hash algorithm that synchronizes the OTP code with a counter changing incrementally each time the user gains access.
Time-based OTP (TOTP): Provides a window of time within which the OTP code will be valid. In general, time steps are 30-60 seconds in length. If the user does not enter the OTP code within the specified time step, they must request a new one.