|
Unique advantages of using this option with Sphinx
|
 Turns any RFID facility access card into a data carrying card
Organizations that have selected a facility access card can leverage the value of the card by using the same card to secure access to computers, by embedding a contact chip on the card. When Sphinx is added to facility access card installations, there is no need for a separate issuance step. End-users self-enroll for Sphinx functionality using their ID card and a desktop card reader at their computer.
On card data storage
This card is capable of storing all logon data on the card, for optimal data portability.
PKI compatible
This card 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 card with the Sphinx software to logon to computers, websites and
applications protects these logon processes with two-factor authentication. Cardholder must
present card to desktop card reader, 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 card security mechanisms
Because this card has encryption capabilities, the communication between the card, the card reader, and the Sphinx application are additionally protected by an extra layer of encryption.
Provides strong encryption
The microchip on this card 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 cards.
|
|
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
|
None, if chip is embedded on facility access card.
Works with existing card infrastructure and card management system, with no change. Cards are issued from and managed by facility access card management system, as before.
Contact chips can easily be embedded on cards by the manufacturer or supplier. If all card stock is embedded each time new ID cards are ordered, there is no additional administrative effort required.
For Sphinx Enterprise version:
Built-in APIs are available that can be used to link third-party facility access control systems or HR database systems to Sphinx, so that adding and deleting of cardholders can be sychronized with Sphinx system, if desired.
|
|
Administrative tasks
|
For Sphinx Standalone version:
No system administration functionality included.
- Administrator installs Sphinx Logon Manager software and card readers on end-user computers, and gives Sphinx license code to each end-user.
- End-users self-enroll using Sphinx Logon Manager, using 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 card, end-user can load a backup of his Sphinx data to a new card 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 and card readers 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 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 card, end-user can use a new card to "re-enroll" with the Sphinx server using a self-selected security code, or administrator can re-issue Sphinx rights to new card using Sphinx CardMaker software.
|
|
Relative overall cost
|
Low.
Compared to other Sphinx solutions:
Estimated to be equal to cost of RFID card solution over time.
Initial cost of contact chip
readers is lower than RFID desktop card readers, and added cost of chip is reasonable, but costs for card replacement and the extra maintentance cost
related to multi-technology cards is greater.
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.
|
