Metal security token todays world is increasingly getting connected due to rapid development in information and internet technology industry, peoples work, study and life-style is changing greatly and growing more efficiency; meanwhile, E-Commerce, E-Government, Digital Currency, E-Banking, financial and retail sectors are accelerating utilization of digital information resources every day.
mToken CryptoID is a security token, a new generation of smartcard chip based two-factor authentication device utilizing CCID drivers. CCID drivers work to protect the device and are therefore less susceptible to packet sniffing thus providing stronger authentication. Moreover, the embedded Smartcard technology allows for highly robust authentication and verification deployments across multi-industry.
mToken CryptoID, an USB Token, is certified from Microsoft HCK/HLK and automatically install drivers from Microsoft Windows Update.
Other Major Features and Benefits
Authentication support: mToken CryptoID security token supports standard smart card applications like Windows smart card logon, VPN, Bit Locker etc.
-
Smart Card Based:utilizes 32-bit smart card technology enabling smart card based authentication and strong authentication.
-
On-Board Encryption processing:encryption and decryption processes take place on-board the mToken device, minimizing the risk of performing the process locally on the host computer.
-
Non-Repudiation Digital Signing:offers non-repudiation digital signing and storing of transactions and documents through PKI technology; ensuring the authenticity of electronic transactions in finance and retail industries.
-
Multiple Algorithms Employed:makes use of several industry-approved encryption algorithms including:DES, 3DES, AES168, AES192, DES256, RSA1024/2048,MD5, SHA1, SHA256, SHA384, SHA512
-
Secure File System:secure file system for storage of digital credentials and files using the three-level permission system.
-
Self-Lock Capability:ability to automatically self-lock the device after a set limit of maximum logon attempts has been reached.
-
Unique Global Hardware ID:employs both a unique global hardware ID and user-defined 32-bit software ID for device own identification.
-
Three Level Permission System:hardware serial number will be read when token plug in. Token is in super user mode after super password verified.Token is in usage mode after password verified. Implements a three-level high security permission system: Administrator, User, and Guest
-
Encrypted Credentials:credentials are encrypted and stored on the device and cannot be exported.
-
Cryptography Standards Compliant: Microsoft CryptoAPI and CNG X509 v3 certificate storage
-
Custom API Support for numerous applications
-
Multiple Platform Compatibility:support across various OS platform including XP, Server 2003, Vista and 7,8,10 ,Mac OS X , and Linux
-
OEM Customization:distinguishing features such as logos and the device’s general appearance, casing, are customizable upon customers’ request.
Supporting OS
mToken CryptoID follows international cross-platform standards thus suitable for multiple operating systems. Supported Operating System include the following:
Windows XP, 2003, Vista, 7 , 8 , 10 (both 32 and 64-bit), Windows SERVER 2003/2012/2015 and more, Linux 2.6 and more, Mac OS X 10 and above
Meanwhile, multiple secure algorithms and middleware are also supported.
mToken CryptoID offers Microsoft Mini Driver, Microsoft Crypto API and PKCS#11 interface; supports multiple certificates and key pairs. All applications compatible with these standard interfaces can be integrated with and hence secured.
COS Features
ISO 7816 Standard
 |
FIPS certified token (FIPS 140 level 3)
- Support for DES, 3DES, AES128/192/256, SHA1/SHA256/SHA384/SHA512, RSA(1024/2048)
- Support multiple applications, multiple containers and multiple certificates;
- Support for X.509 v3 certificate storing and certificate importing.
- Software and Middleware
- In-built CD-ROM – designed for users to store custom middleware.
- Support for mToken API libraries, mToken PKI middleware (for PKCS#11 v2.2 and MS-CAPI applications) and self-defined interfaces.
