2 Planning your SafeCom solution
D60829-07
9
2
Planning your SafeCom solution
2.1
Overview
The Nuance Mx proximity readers come with preloaded firmware with all
supported protocols enabled. This means that in most cases the readers can be
deployed as is. However, there are some scenarios that require some planning:
User behavior:
Presenting multiple cards at a time
If a user is storing multiple proximity cards in a wallet and is placing the
wallet on top of the card reader, it will vary which card is read. The same
applies if the user has multiple key fobs chained together.
Users should present only one card (or key fob) at a time.
General considerations:
Security policies
Organizations’ security policies may allow users to only authenticate by
means of their provided ID card. Configuring the Nuance Mx Proximity
Reader to only support that particular protocol limits the risk of other
cards being used. Also the SafeCom solution can be configured to allow
only one ID code per user.
Self-service
Users are allowed to have multiple ID codes and they can register these
themselves at the device. This allows the users to authenticate with ID
cards that are not necessarily provided by administration.
ID cards with multiprotocol support
If the ID card support multiple protocols, then it will vary which protocol
will be returned. The card reader should be configured for selective card
reading so only one of the card’s supported protocols are enabled.
Existing solutions:
Existing SafeCom Proximity Readers are in use
Please refer to (2.2) for information on compatibility. It is good practice
to do some card testing (2.5) to get additional details.
ID code conversion
Existing filtercard.dll is installed to perform on-the-fly ID code
conversion.
