TriCipher Armored Credential System combines multi-part keys and many modes of multi-factor authentication
The TriCipher Armored Credential System really is a suite of utility programs and appliances that allow a company to have secure internal and external communications using authentication that’s difficult or impossible to compromise. TACS strengthens authentication by using multipart encryption keys, storing portions in separate locations, and providing multiple means of storing or deriving those keys to support a wide range of security requirements and user scenarios.
This means you can use features such as tokens, SecureID cards, embedded chips, or even passwords alone as part of the authentication process. And regardless of which methods you use, the split keys (one portion stored locally and the other on the TACS server) prevent the possibility of a compromise even if the user’s device, token, username, and password are all stolen.
If this sounds as if it could be complex, it is. There’s a lot you can do with TACS. The flexibility is remarkable. But putting it into operation will take work. The reason, of course, is that for most users TACS will exist as a collection of APIs. You must modify your applications to call on TACS for authentication.
For easier integration with existing applications, TriCipher will soon offer the TACS Authentication Gateway, which will sit between the authentication appliance and the Web application and handle authentication tasks for the application. Company reps say organizations lacking development support may find the Gateway a good fit, while organizations that require more control over authentication flows and related code may choose to use the APIs directly. The TACS Authentication Gateway wasn’t available for testing in time for this review.
TACS itself consists of the APIs, an appliance that handles key storage and authentication, some management utilities, and a client application. The client application is a Microsoft CAPI (Cryptographic Application Programming Interface) driver, called the TACS ID Tool, which is only required for certain types of credentials, such as device or token multifactor.
Exactly how all of this fits together depends on your mix of applications, users, and security requirements. For example, if you’re creating a Web-based application, you could use the system in a clientless environment in which multifactor authentication includes a browser cookie as part of one of the authentication keys. As always, the authentication server will store the other part of the key.
However, you could also use a more advanced means of authentication. In such a situation, you’d install the ID Tool client application on the Windows computer that’s accessing the protected network, and the client would communicate with TACS via an SSL channel that supports mutual authentication of the client and server. In this case, part of the multifactor authentication could involve a security chip in the PC (some IBM machines have this), a USB key, or even an iPod or digital camera. You could also use tokens and some biometrics. You could, in fact, use more than one of these methods at the same time, and you could use different methods for different users.
In any case, once the TACS client is running on a user’s machine, it’s basically transparent. Users will have to log on with a user name and password, but that doesn’t need to look any different than what they do now.
The TriCipher management interface, where you set up the type of authentication and the place where the authentication package should look for its keys, consists of a series of forms with pull-down boxes or fields to fill in. It’s not particularly difficult once you learn how TriCipher’s tools work. On the other hand, it’s not totally intuitive, either. You can select the details for every user individually if you need to, and you can tailor the means of authentication and the source for encryption, along with a number of other options for virtually every circumstance.
Because TriCipher protects the encryption keys so completely, spoofing a user without having both the user’s log-in information and the user’s token or laptop computer is highly unlikely. It may be impossible, especially considering that your users and business partners will never know exactly how your security works.
In short, the security is good, but getting there may not be easy. TriCipher has a professional services staff, and the company will help its customers get everything up and running. But the process of doing this will cost money in terms of staff or consulting time, and that’s in addition to the six-figure price tag just to get the product in the door. TACS will be an effective product for many companies, but it’s not for everyone. Smaller organizations in particular may be priced out of the market.
Ease of use (20.0%)
Overall Score (100%)
|TriCipher Armored Credential System V. 3.2||6.0||7.0||7.0||9.0||7.0||9.0|
Microsoft buried a Get Windows 10 ad generator inside this month's Internet Explorer security patch for...
Hot or not? From the Web to the motherboard to the training ground, get the scoop on what's in and...
Microsoft’s 'Fall Update' promised to put the finishing touches on Windows 10 -- it doesn’t
For Android to win over the enterprise, it needs the right apps -- and these offerings definitely mean...
Internet messaging has broken the rule of universal communication standards, and it needs to be fixed ...
We're inundated with exciting new enterprise tech. But for it all to amount to more than the sum of its...
Splunk may be the most famous way to make sense of mass quantities of log data, but it's far from the...