Supported Tags; Tag Security - Nedap uPASS REACH Installation Manual

UPASS REACH | INSTALLATION GUIDE
Introduction
1.3

SUPPORTED TAGS

Any EPC Class 1 Gen 2 tag is supported by the uPASS Reach. NEDAP formatted UHF
tags can have the following formats:
NEDAP UHF Wiegand tags
•
These tags will contain all Wiegand information including facility code and
parity bits. All Wiegand formats can be supported. The reader transparently
sends this information via the Wiegand outputs. There is no need to change
any DIP-switches or configuration settings. See chapter 3.4.1 for wiring
details.
NEDAP UHF Magstripe tags
•
These tags will contain all magstripe information. The reader transparently
sends this information onto the magstripe interface. There is no need to
change any DIP-switches or configuration settings. See chapter 3.4.1 for
wiring details.
NEDAP UHF XS tag
•
These tags are especially programmed in the same format as our 2.45GHz
AVI tags (Compact-Tag, Window-Button and Heavy-Duty-Tag). The tags will
also have a customer-code and id-number. The reader will automatically
transmit the tag-info to the TRANSIT compatible processor.
1.4

TAG SECURITY

EPC (Electronic Product Code) tags were introduced as a possible successor to the
barcode with added functionalities. The tag emits its EPC in plain text. This makes
the tags vulnerable to cloning and counterfeiting attacks. Unlike many 13MHz
smartcards, EPC tags do not support any DES, 3DES or AES encryption.
EPC tags contain a data field known as the Tag Identifier (TID). At the discretion of
the EPC manufacturer, the value may be factory programmed and locked, ensuring
that tags have a unique identity and (theoretically) cannot be cross-copied. This TID
based anti-cloning mechanism is not considered to be a strong protection.
NEDAP UHF tags support a locked serialized TID and the uPASS Reach reader can be
configured to read the TID data field.
In addition NEDAP has also implemented an advanced anti-cloning and anti-
counterfeiting method based upon a two way authentication. This feature is
supported in combination with all NEDAP UHF tags. See also chapter 7.
By default the uPASS Reach reader is configured to read any EPC tag.
We encourage customers to enable the TID-check or the two way authentication. But
also advise not to completely rely on these methods in high-security applications.
Tag security is not evaluated by UL
Note
The Wiegand output format
is determined by the tag
and not by the reader.
Note
The magstripe output
format is determined by the
tag and not by the reader.
Note
When using the TRANSIT
compatible processor make
sure the compatibility
mode DIP-switch is set
correctly (see chapter 4.1
on page 19).
5/35