|
Unique advantages of using this option with Sphinx
|
 Convenient small format
The convenient small size of this token makes it easy to carry on a keychain so that it is easily accessible. Token is simply plugged into USB slot for use.
On board data storage
This token is capable of storing all logon data on board, for optimal data portability.
PKI compatible
This token can be used for certificate-based functions in a Public Key Intrastructure (PKI) environment.
|
|
Added logon security achieved with this option
|
Stronger.
Two-factor authentication
Using this token with the Sphinx software to logon to computers, websites and
applications protects these logon processes with two-factor authentication. End-user must plug token into USB slot, and enter PIN, in order to access his Sphinx logon data and execute logon. Two-factor authentication is lauded throughout the security industry for its effectiveness at protecting information.
Enables use of strong passwords
End-users are enabled to use strong, complex passwords that provide effective protection, because Sphinx stores them securely so that end-users don’t need to remember them. Password information is entered into logon processes transparently, directly from the Sphinx software into the logon process, so that keystrokes cannot be observed or recorded.
On board security mechanisms
Because this token's chip has encryption capabilities, the communication between the token and the Sphinx application are additionally protected by an extra layer of encryption.
Provides strong encryption
The microchip on this token is capable of strong encryption which provides a high level of security for data and processes.
|
|
Data portability with this option
|
High.
Sphinx stores all logon data on these tokens.
|
|
PKI available
|
Yes.
Can be used with Sphinx Enterprise PKI version in standard format.
|
|
Impact on network setup
|
None, for Sphinx.
However, if an organization chooses to implement a Public Key Infrastructure (PKI), the maintenance of that infrastructure can be complex.
In reference to Sphinx' impact: works within existing network configuration and does not require any change to Windows configuration. Because logon entry processes are "auto-recorded" by end-user or administrator, does not require any integration effort for applications to which end-users logon. See also How it works.
|
|
Impact on facility access card infrastructure
|
Must be issued separately from facility access card.
Sphinx Enterprise version provides complete token issuance and management capabilites, for organizations that want to manage the solution.
|
|
Administrative tasks
|
For Sphinx Standalone version:
No system administration functionality included.
- Administrator installs Sphinx Logon Manager software on end-user computers, and gives Sphinx license code to each end-user.
- End-users use their tokens to self-enroll using Sphinx Logon Manager, referring to the simple instructions provided in the QuickStart guide.
- End-users click on support link to refer to the Sphinx support site for additional information and manuals, which ensure that end-users have all the information that they need to work easily and optimally with Sphinx.
- If end-user loses token, end-user can load a backup of his Sphinx data to a new token using a self-selected security code.
|
|
|
For Sphinx Enterprise version:
Administrators can control the Sphinx system as little or as much as they want.
- Administrator installs Sphinx Logon Manager software on end-user computers, and installs Sphinx CardMaker software on a server computer and specifies only three server settings.
- Administrator can leave pre-configured default settings as is, or can change the default settings of the full-featured Sphinx CardMaker software to suit the security requirements of the installation.
- End-users use their tokens to self-enroll using Sphinx Logon Manager, or administrator enrolls end-users using the Sphinx CardMaker software.
- End-users click on support link to refer to the Sphinx support site for QuickStart guide, manuals, and additional information, which ensure that end-users have all the information that they need to work easily and optimally with Sphinx.
- If end-user loses token, end-user can use a new token to "re-enroll" with the Sphinx server using a self-selected security code, or administrator can re-issue Sphinx rights to new token using Sphinx CardMaker software.
|
|
Relative overall cost
|
Low.
Compared to other Sphinx solutions:
Estimated to be equal to cost of RFID or contact chip card solution over time. Individual token cost can be comparable to cost of card reader and card combined.
Compared to other logon solutions:
Low one-time cost per seat quickly pays for itself through increased efficiency and decreased risk of data loss. Sizable savings in comparison to other solutions in terms of ongoing maintenance of the solution, for example, for solutions that require integration of logon applications or have annual fees.
|
|
System requirements
|
Operating system for Sphinx Logon Manager for end-user computers:
Windows NT4-SP6, 2000, XP or 2003.
Operating system for Sphinx CardMaker for administrator computer:
Windows XP, 2000, 2000 Server or 2003 Server (Enterprise version only).
Browser:
Internet Explorer 5.5+ or Firefox 2.0.
|
