US 8183980 B2
Secure access systems are discussed herein. Specifically, a method and system is provided that allows a control panel of a secure access system to verify the authenticity and fidelity of a reader within the secure access system by utilizing a rolling code agreed upon by the reader and the control panel.
1. A method of maintaining a secure access system that uses a unidirectional communication protocol, the secure access system comprising at least one credential, at least one reader, and a device upstream of said reader, the method comprising:
reading a credential with a reader;
said reader generating a first message comprising credential data associated with said credential and a first code;
transmitting said first message to an upstream device;
said upstream device analyzing said credential data in order to determine the authenticity of said credential and further analyzing said first code in order to determine the authenticity of said reader;
receiving, at said reader, a prompting signal transmitted by said upstream device;
in response to receiving said prompting signal from said upstream device, said reader generating a second message comprising a second code, wherein said second code is different from said first code; and
transmitting, by said reader, said second message to said upstream device, wherein a first code selection algorithm is used to generate said first code, wherein said first code selection algorithm generates said first code based upon at least one of time of day, total operation time of said reader, a reader unique ID, number of cards read, and a reader manufacturer ID, wherein a second code selection algorithm is used to generate said second code, and wherein the first and second code selection algorithms are different.
2. The method of
receiving at said upstream device said second message; and
said upstream device analyzing said second code in order to determine the authenticity of said reader, wherein the first and second codes are maintaining in a list of rolling codes at the reader.
3. The method of
4. The method of
5. The method of
6. The method of
7. The method of
8. The method of
said upstream device accessing a second list that corresponds to said rolling code list;
said upstream device comparing said first code to one or more valid codes from said second list;
determining that said first code matches a valid code; and
in response to said upstream device determining that said first code matches said valid code, said upstream device determining that the authenticity of said reader is valid.
9. The method of
10. The method of
11. The method of
12. The method of
13. The method of
14. The method of
15. A method of maintaining a secure access system that uses a unidirectional communication protocol, comprising:
providing a downstream device associated with at least one interrogator device that is operable to transmit a rolling code from a first list of rolling codes as a part of a message;
providing an upstream device that is operable to receive said message and analyze said rolling code by accessing a second list of rolling codes which matches the first list of colling codes and then comparing the rolling code to a valid code from the second list of rolling codes;
requiring said downstream device to transmit a first message comprising a first valid rolling code at a first time;
prompting said downstream device to transmit a second message comprising a second valid rolling code at a second time, wherein said upstream device prompts said downstream device to transmit said second message by at least one of (i) transmitting a prompting signal to said downstream device via an LED control line and (ii) interrupting power supplied to the downstream device.
16. The method of
17. The method of
18. The method of
19. The method of
20. The method of
21. The method of
22. The method of
23. The method of
24. The method of
25. A secure access system utilizing a unidirectional communication protocol, comprising:
a reader that is operable to read credential data from said credential upon presentation of said credential to said reader, generate a first message comprising some or all of said credential data and code data, and to transmit said first message;
an upstream device that is operable to receive said first message and upon receiving said first message is operable to analyze said credential data in order to determine the authenticity of said credential and to analyze said code data in order to determine the authenticity of said reader, wherein said upstream device is further operable to generate and transmit a prompting signal via an LED control line to said reader which requires the reader to transmit additional code data in a second message to confirm its authenticity to said upstream device, wherein the code data includes a rolling code selected from a list of rolling codes, wherein said rolling code is a unique code chosen from said list of rolling codes, wherein said upstream device is further operable to access a second list which matches said list of rolling codes, compare said rolling code to a valid code from said second list, determine that said first code matches said valid code, and in response to determining that said first code matches said valid code, determine that the authenticity of said reader is valid.
26. The system of
27. The system of
28. The system of
29. The system of
30. The system of
31. The system of
32. The system of
33. The system of
34. The system of
35. The system of
36. A device for use in a secure access system that uses a unidirectional communication protocol, wherein said device is operable to read credential data from a credential, comprising:
a code generator that is operable to generate a first message comprising credential data associated with a credential that is used to determine the authenticity of said credential and a first code that is used to determine the authenticity of said device, wherein said code generator comprises a code selection algorithm, wherein said code selection algorithm generates said first code based upon at least one of time of day, total time of operation, a reader unique ID, and a reader manufacturer ID, wherein a second code selection algorithm is used to generate said second code;
an LED control input which connects said device to an upstream device, wherein said LED control input is used control an LED of said reader and to receive prompting signals from said upstream device which prompts said code generator to generate a second message comprising a second code; and
an output for transmitting said first and second messages to said upstream device.
37. The device of
38. The device of
39. The device of
40. The device of
41. The device of
42. The device of
43. The device of
44. The device of
45. The device of
46. The device of
This application claims benefit of U.S. Provisional Patent Application Ser. No. 60/713,528, filed Aug. 31, 2005, which is herein incorporated by this reference in its entirety.
The present invention is generally directed to authentication of a reader in a secure access system. More specifically, the present invention provides a reader signal protocol used to protect and differentiate authorized, authentic readers from non-authorized, non-authentic readers in a secure access system.
Limiting or securing access to designated or sensitive areas is an important issue. As such, there is a current focus on technological systems for controlling access to designated areas in both the private and public venues. Such systems must be made highly impervious to attack by those wishing to gain unauthorized access to the secured area.
In access control systems, Radio Frequency Identification Devices (RFIDs) or other security credentials are typically used to store data that uniquely identify a holder of the RFID device or the holder's access authorizations. In order to gain access to an asset, such as a building, room, safe, computer, files, information, etc., a holder presents the RFID device to a reader that reads the data and subsequently transmits the data to a panel, processor, or a host system where a decision is made to either grant access to the subject asset or not. There are also readers that combine the functionality of a panel/host and the physical reader into a single unit that makes the access decision. This type of device is sometimes referred to as a stand-alone reader.
Attention has been focused on the security mechanisms employed by RFID cards to protect and secure the data exchange between the RFID device and the reader. Some of these techniques include the use of cryptography, mutual key authentication, secure channels, and even protection of the chip on the RFID device against physical and electrical attacks. However, little attention has been given to ensuring the integrity of the communications between the reader and its host/control panel as well as insuring the integrity of the reader itself.
A working assumption thus far has been that RFID device readers are trustworthy devices, when in fact this may not be the case. In many building access control applications, a reader is mounted on the unsecured side of a door in a location that is not under continuous scrutiny. In such a case, compromise of a single reader could result in a compromise of RFID device security if any secret information, such as keys, authorization codes and the like, were somehow extracted from the reader.
In addition, without knowing the authenticity of the reader an unauthorized or rogue reader could be used to replace an existing legitimate reader in a security system. This rogue reader can actually be any reader or data reply device capable of outputting data in the same format as the replaced reader.
In the access control industry, one of the most popular communication protocols used between a reader and a panel is the Wiegand protocol. Due to its popularity, the Wiegand protocol has become a de-facto industry standard. It is estimated that the majority of today's access control panels support the Wiegand protocol as the primary method to connect readers to the panel. It should be noted that several companies use their own proprietary communications protocols, but they still support the Wiegand protocol due to its popularity and widespread use. Because of this, a variety of non-RFID machine readable ID readers and other devices have standardized on the Wiegand protocol. Examples of these readers support smart card, proximity, magnetic stripe, bar code, barium ferrite, etc. There are also keypads, biometric devices, wireless Wiegand protocol extenders, protocol converters, and even robots that utilize the Wiegand protocol. The Security Industry Association (SIA) also recognizes the Wiegand protocol as an important standard in the access control industry. The Wiegand protocol has become so important that it has been published as an industry standard.
The Wiegand protocol is essentially a unidirectional protocol that only provides for data transmission from a reader to an upstream device (e.g., a control panel, host, or processor). Although there is a signal sent back from the upstream device to the reader, this signal is essentially a logic signal used to convey status to a cardholder by controlling a reader's LED. A superset of the Wiegand protocol adds additional logic signals to control an audible device in the reader and provides for additional reader LED colors. These are not bi-directional protocols because substantive data is still sent in only one direction. The host cannot give the reader a command. Only simple signals are sent from the host to the reader.
As popular as the Wiegand protocol has become, it has shortcomings. Examples of these shortcomings include the fact that the Wiegand protocol is susceptible to electrical noise, has distance limitations, and only allows data to be sent from a reader to an upstream device. Without bidirectional capabilities, it is very difficult to implement a modern protocol that provides for reader authentication.
Another issues is that the Wiegand protocol allows “party line” connections so that it is very easy to connect one or more additional devices to communication wires to monitor the communications between a card reader and a host in an attempt to harvest data streams to be used to compromise the system. Once a rogue device has been connected to monitor communications between the reader and control panel, an attacker could merely note when the door has been unlocked and flag the most recent data stream as one that will open the door. Then, whenever illicit entry is desired, the attacker could just “replay” that data stream causing the door to unlock. The attacker need not even remove the device from the communication wires because the Wiegand communications utilize an “open collector” electrical interface, which allows both the monitoring of messages and generation of messages from that same connection.
There is typically little stopping an attacker from harvesting one or more valid messages to gain illicit entry using different cardholder's data so that no suspicions are aroused. Accessibility to the Wiegand communications wires is increased by the fact that a reader is typically located on the unsecured side of a wall or door and, because of the nature of access control, may be at a location that is not under continuous observation or scrutiny. Making matters worse, many access control readers do not employ a tamper mechanism so that the removal of a reader to access the internal wiring or even to replace the reader with another compromised reader or illicit Wiegand generating device is undetectable.
There have been some attempts to address the shortcomings of the Wiegand protocol. One example of an extension to the Wiegand protocol is described in U.S. Pat. No. 6,988,203 to Davis et al., the contents of which are hereby incorporated herein by this reference. The '203 patent describes appending additional bits to the Wiegand data stream. This provides supplementary information from the reader to the upstream device as well as a CRC or other type of error detection and/or correction bits covering all of the data in the transmission. The '203 patent further describes transmitting data back to the reader from the upstream device via an LED control line.
Additionally, in PCT Application No. WO 2005/038729 to Merkert, which is herein incorporated by this reference, an access system that includes a signal generator located between a reader and a control panel is described. The reader utilizes a dynamic timing element that ensures a replay attack cannot be used to gain unauthorized access to an asset. The reader stamps any signal sent therefrom with a time stamp indicating when the message was generated. Then the control panel reads the time stamp to ensure that the message is authentic. An attempt to harvest a signal and resubmit that signal again at a later time will result in the control panel determining the signal is invalid. To ensure channel security between system elements, encryption and/or digital signatures are used. Unfortunately, this solution does not overcome most of the Wiegand deficiencies.
For instance, there is no way in the currently existing solutions that allows the control panel to continually monitor each reader in order to verify the fidelity of each reader. Thus, leaving open the possibility of having a valid reader replaced with a rogue reader without the system or system operator becoming aware of such actions.
The present invention is generally directed toward a method, apparatus, and system that allows for authentication of readers in a secure access system. Although well suited for use in an access system utilizing the Wiegand protocol, embodiments of the present invention may be suitable for use in any system utilizing a unidirectional protocol.
In accordance with embodiments of the present invention, a method of checking authenticity of devices in a secure access system utilizing a unidirectional communication protocol is provided. The method comprises the steps of reading a credential with a reader, the reader generating a first message that includes credential data associated with the credential and a first code, transmitting the first message to an upstream device, and the upstream device analyzing the credential data in order to determine the authenticity of the credential and further analyzing the first code in order to determine the authenticity of the reader.
A valid reader employing the above-described method will be able to verify its authenticity to the upstream device by sending a valid code. A reader that is not enabled to generate a valid code may be identified by the upstream device as defective and/or fraudulent. By requiring the reader to send a valid code along with credential data, the upstream device can be confident that the reader is valid and has not been tampered with.
In accordance with further embodiments of the present invention, a method of maintaining a secure access system that utilizes a unidirectional communication protocol is provided. The method comprises the steps of providing a downstream device that is operable to transmit a valid rolling code as a part of a message and further providing an upstream device that is operable to receive the message and analyze the rolling code. The method can continue by determining a required first time of check in and requiring the downstream device to transmit a first message including a first valid rolling code at a first time related to the required time of check in. The method may then determine a required second time of check in that is after the required first time of check in, and require the downstream device to transmit a second message including a second valid rolling code at a second time related to the required second time of check in.
By requiring a downstream device to check in with the upstream device at a particular time schedule, the upstream device can continually update the state of the system. In other words, the upstream device can determine fairly quickly, depending on the amount of time between required check in times, whether a downstream device has been tampered with, replaced, and/or is malfunctioning. If the time between required check in messages is very short, like one second or less, it becomes very difficult for an attacker to perform any action that would interrupt communications between the upstream device and the downstream device.
In one embodiment of the present invention, certain thresholds may be set at the upstream device that allows for missed messages due to noise or the like. For example, a threshold of N missed messages may be allowed for a particular downstream device. Thus, if a downstream device misses one predetermined check in time, it is not necessarily identified as malfunctioning or having been tampered with. Rather, the downstream device is allowed to miss up to N check-ins, which may or may not be consecutive, before an error determination is made.
In accordance with other embodiments of the present invention, a secure access system utilizing a unidirectional communication protocol is provided. The system comprises a credential, a reader that is operable to read credential data from the credential upon presentation of the credential to the reader, generate a message including the credential data and rolling code data, and to transmit the message, and an upstream device that is operable to receive the message and upon receiving the message is operable to analyze the credential data in order to determine the authenticity of the credential and to analyze the rolling code data in order to determine the authenticity of the reader.
In accordance with still further embodiments of the present invention a device adapted for use in a secure access system utilizing a unidirectional communication protocol is provided. The device comprises an input that is adapted to receive a message from a reader, where the message includes a rolling code, an authentication member operable to determine the authenticity of the reader based upon an analysis of the rolling code, and an output operable to transmit the message to an upstream device in response to the authentication member determining the authenticity of the reader is valid.
The device may be an intermediate device that is used only to monitor the authenticity of readers in a given system. The intermediate device may also be adapted to analyze credential data received from the reader in order to make a determination about the authenticity of a credential that was presented to the reader. The intermediate device may be employed in order to ensure that communications between a rogue reader and a control panel do not occur, thus protecting the control panel from potentially harmful signals. This provides a provision for updating legacy systems with embodiments of the present invention without requiring the replacement of a reader or host.
These and other advantages will be apparent from the disclosure of the invention(s) contained herein. The above-described embodiments and configurations are neither complete nor exhaustive. As will be appreciated, other embodiments of the invention are possible using, alone or in combination, one or more of the features set forth above or described in detail below.
The present invention is generally directed toward a reader authentication method, device, and system. The invention advantageously addresses deficiencies of the prior art and may be utilized within the context of access control or security systems, as well as be equally efficiently utilized in a broad range of other applications using a unidirectional communications protocol where interactive computerized data acquisition techniques are used, both contactless or requiring a physical contact with a carrier of pre-programmed information (e.g., monitoring moving objects, tracking inventory, verifying credit cards, and the like).
Additionally, the system 100 may further comprise intermediate devices 120 connected between a reader 112 and the control panel 104. In the depicted embodiment, the readers 112 are coupled to an intermediate device 112 through interface 132. The intermediate devices 120 are coupled to the hub 108 through interface 128 and the hub is coupled to the control panel 104 via interfaces 124. In an alternate embodiment (not shown), the readers 112 may be coupled to the respective inputs/outputs of the control panel 104 without a device, like the hub 108 or intermediate device 120, existing there between. Interfaces 124, 128, and 132 between the readers 112, the intermediate devices 120, the hub 108, and the control panel 104 are generally unidirectional interfaces, which may selectively be implemented in a form of wired, wireless, fiber-optic communication links, or combinations thereof.
As can be appreciated by one of skill in the art, the interfaces 124, 128, and 132 may be implemented utilizing buses or other types of connections. For example, the I/O ports may be one or more of a USB port, parallel port, serial port, Small Computer Systems Interface (SCSI) port, modem, Ethernet, and/or an RF interface. The protocols used to communicate between the control panel 104 and the readers 112 may include one or more of the TCP/IP protocol, RS 232, RS 485, Current Loop, Power of Ethernet (POE), Bluetooth, ZigBee, GSM, WiFi, and other communication methods and protocols known in the art.
An exemplary intermediate device 120 comprises an input that is adapted to receive signals via interface 132, an output that is adapted to transmit signals via interface 128, and an authentication member 140. The authentication member 140 is operable to determine the authenticity of one or more readers 112 associated with the intermediate device 120 (e.g., determine whether the reader 112 is valid or not), based upon a rolling code that is transmitted from the reader 112 to the intermediate device 120.
The control panel 104 may be a general-purpose computer adapted for multi-task data processing and suitable for use in a various settings (e.g. commercial, industrial, residential, and the like). A memory of the control panel 104 comprises software program(s) containing a database of records for the system 100. Alternatively, a database 144 may be separated from the control panel 104. The database 144 whether integral to the control panel 104, separate from the control panel 104, or both, maintains records associated with the readers 112, credentials 116 and their respective holders or users, algorithm(s) for acquiring, decoding, verifying, and modifying data contained in the readers 112, algorithm(s) for testing authenticity and validity of the credentials 116, and algorithm(s) for implementing actions based on the results of these tests. The database 144 may further comprise a list of valid rolling codes and their corresponding required time of check in and/or algorithm(s) for generating valid rolling codes and comparing them with rolling codes received from a downstream device.
As used herein, in reference to an individual or an object associated with a credential 116, the terms a “holder” and a “user” are used interchangeably.
Each reader 112 is adapted for exchanging information with the control panel 104 and for requesting data from the credential 116 placed in the active zone of the reader. The reader 112 may also be adapted for processing at least a portion of the data acquired from the credential 116. Alternatively, processing of the acquired data may be performed using the control panel 104 exclusively. In one embodiment, the reader 112 generates signals facilitating execution of the results of interrogating the credential 116 (e.g., engages/disengages a locking mechanism, allows/disallows movement of a monitored article, temporarily disables itself, activates an alarm system, updates a database, and the like). Alternatively, the control panel 104 may generate such signals.
In accordance with embodiments of the present invention, a stand-alone reader 112 may be utilized to perform the functionality of both the reader 112 and the control panel 104. This stand-alone reader may include, or have access to, the database that contains data used to determine the authenticity of a credential and/or algorithm(s) used to make the determination of authenticity of the credential 116. A determination of authenticity for a credential is made at the receiving point rather than having to transmit data across a network from the reader to a control panel 104 in order to make a determination of authenticity. The stand-alone reader is further operable to execute instructions based upon the analysis of the credential 116.
Specific configurations of the control panel 104 are determined based on and compliant with computing and interfacing capabilities of the readers 112 and/or the hub 108.
At least a portion of the plurality of readers 112 further comprise a code generator 148. The code generator 148 is used by the reader 112 to generate a code, possibly a rolling code, in order to verify its authenticity to an upstream device. The code generator 148 may comprise a table, sequence, or data structure of valid rolling codes that the reader 112 can work through as update signals are generated. The code generator 148 may also comprise a code generating algorithm that creates a valid code based on certain criteria.
Interface 136 represents the communication interface that exists between a reader 112 and a credential 116. Interface 128 may represent an RF communication interface, a biometric communication interface, a keypad, a magnetic communication interface, an optical communication interface, or combinations thereof.
In operation a credential 116, for example a credential, is brought into an active zone of the reader 112 in order to establish the communication interface 136. For a credential, a Radio Frequency (RF) communication interface 136 between the reader 112 and the credential is typically automatically established when the credential is brought within an active zone of a reader/interrogator 112. The active zone of an RF reader 112 is defined as a three dimensional space where the intensity of RF signals emitted by the reader 112 exceeds a threshold of sensitivity of the credential and the intensity of RF signals emitted by the credential exceeds a threshold of sensitivity of the reader 112. When a credential is presented to most readers, such a communication interface 136 is established and the reader 112 and credential begin transmitting data back and forth.
The credential 116 may also be implemented in a number of other machine readable devices including, but not being limited to, contact smart card, a contactless smart card, a proximity card, a magnetic stripe card, a barium ferrite card, a bar code, a Wiegand card, a PDA, a cellular phone and any other type of device used to store and transmit data relating a particular application. The active zone for each type of credential 116 may vary based upon the type of communications used between the reader 112 and the credential 116. For example, a magnetic stripe card is placed in the active zone of the reader 112 when it is swiped through the reader 112. As can be appreciated by one of skill in the art, the interface 128 is created upon presentation of the credential 116 to the reader 112 such that communications between the two is facilitated.
The reader 112 takes the information that it retrieves from the credential 116 and generates a signal to send to the control panel 104. In generating the signal the reader 112 creates a credential part of the signal and a rolling code part of the signal. The code generator 148 is typically operable to generate the code part of the signal. The credential data relates to the credential that was read (e.g., user name, social security number, title, access permissions, key, password, manufacturer ID, site code, customer code, unique ID, etc.) The code data or rolling code data is a number, letter, dataset, and/or identifier chosen from possibly a list of potential rolling codes. The rolling code sent from a valid reader 112 may possibly be a code previously agreed upon by the control panel 104 and reader 112. The reader 112 and control panel 104 may cycle through and agree upon a number of valid rolling codes as time progresses in order to provide a more secure system.
Once the control panel 104 receives the signal from the reader 112, the control panel 104 will analyze the credential data from the signal to determine if the credential 116 is authorized to gain access to the asset associated with the reader 112. Additionally, the control panel 104 will analyze the rolling code portion of the signal to determine if the reader 112 is authorized to send commands and has not been tampered with. In an alternative configuration, the signal is sent from the reader 112 to the intermediate device 120 where the rolling code data is analyzed by the authentication member 140 in order to determine if the reader 112 is still valid and has not been tampered with. The intermediate device 120 then forwards the signal on to the control panel 104 for verification of the credential 116. In still a further configuration, the reader 112 generates a signal containing only the credential data and forwards that signal on to the intermediate device 120. The intermediate device 120 then generates rolling code data and incorporates that into the signal from the reader 112. The intermediate device 120 then forwards the signal on to the control panel 104 for verification of the credential and rolling code data. As can be appreciated, any upstream device within the system 100 may perform the verification of the credential data and/or the rolling code data generated by a downstream device. However, it is advantageous to have the reader 112 verified by a device that resides in a secured area rather than an unsecured area so that the device verifying the authenticity of the reader 112 may not be as easily compromised.
Referring now to
Referring now to
Alternatively, a valid rolling code may be generated arbitrarily, as long as the control panel 104 is in synchronization with the reader 112 in determining what the next valid code is in a rolling code sequence. For example, the reader 112 may use a pseudo-random code generator and the control panel 104 may use an exact copy of the generator. The system may be initiated such that each generator determines, creates, and agrees upon the same valid rolling code as each continues to operate properly. For example, the reader 112 and the control panel 104 may use a previously agreed upon sequence or list of valid rolling codes. The control panel 104, at any random time, may change the order in which the code generator 148 goes through the list. The control panel 104 could inform the reader 112 to change how it is working through the list with a prompting signal send via an LED control signal, or may do so through an interruption to the power supply of the reader 112. This ensures that the code generator 148 does not necessarily have to go through a finite list of valid rolling codes in the same order until a new list of codes is provided to the code generator 148. Rather, the same list may be used for a relatively longer amount of time and a higher level of security can be maintained.
In an alternative embodiment, data received from the credential 116 may dictate what sequence the rolling code should follow. For example, when a first type of credential 116 is read, the reader 112 may use a first rolling code selection algorithm or select a rolling code from a first list of rolling codes. When a second type of credential 116 is read by the reader 112, the reader may change to a different rolling code selection algorithm and/or list of rolling codes. When the reader 112 switches from one rolling code selection algorithm to another, it should indicate to the upstream device that such a switch has been made. Alternatively, the upstream device may recognize that a second type of credential 116 has been read and automatically knows to switch to a different rolling code selection algorithm.
Of course different algorithms may be used in a similar fashion. The code generator 148 may use a first algorithm to generate valid codes, then upon receiving a prompting signal from an upstream device, like a control panel 104, a different algorithm is used by the code generator 148. Furthermore, data used by the algorithm to compute a valid rolling code may be changed in an analogous way.
Once the rolling code data and credential data have been determined, the reader 112 generates a message containing both the credential data and rolling code data (step 316). In step 320, it is determined if the signal containing the message is to be encrypted. If the signal is not to be encrypted, then the reader 112 transmits the message (step 332). However, if the message is to be encrypted, then an encryption key is determined (step 324). Thereafter, the message is encrypted using the encryption key (step 328). By encrypting the message, the communications between the reader 112 and the control panel 104 becomes more secure. Even if someone is harvesting signals sent from the reader 112 to the control panel 104, they must know the encryption/decryption key and decrypt the message before any substantive information about the message can be determined. Essentially, the encryption of the message makes it more difficult for an attacker to steal a valid rolling code and valid credential data.
In step 332, the message, whether encrypted or not, is transmitted. Then, if the rolling code is based upon the number of sent messages from a particular reader 112, the reader increments to the next rolling code in the valid rolling code sequence (step 336). A valid rolling code may depend on the time of day or the amount of time the reader 112 has been operational. In this case, the rolling code is not necessarily updated after a message is transmitted. In one embodiment, a list of valid rolling codes, for example rolling codes A, B, C, D, and E may be used. The reader 112 starts by appending rolling code A to the first message it generates and transmits to the control panel 104. The next rolling code the reader 112 transmits may be rolling code B, then rolling code C and so on. Once the reader 112 has went through the entire list of rolling codes, it may start over by appending rolling code A to the next message it generates. Alternatively, the reader may append rolling code D after it has appended rolling code E and work through the list of rolling codes that way. As long as the reader 112 follows the predetermined rolling code selection protocol, it will continue to generate valid rolling codes. Using a list of a select nunber of rolling codes provides for an inexpensive implementation of the present invention. However, a persistent attacker may eventually discover the finite list of rolling codes thus jeopardizing the secure access system 100. In order to create a more secure access system, valid rolling codes may be generated based on predetermined algorithms using previously agreed upon criteria.
As can be appreciated by one of skill in the art, the reader 112 is not the only device that may be used to generate a signal containing both rolling code data and credential data. If there are other devices present in an unsecured area, those devices may be required to generate rolling code data in order to guarantee their validity, and the validity of devices connected thereto to the control panel 104. These devices may include credentials 116, intermediate devices 120, and/or any other downstream device.
Referring now to
Once the credential data has been separated from the rolling code data, the control panel 104 compares the received rolling code to the required code. The required code may be maintained at the control panel 104 or in the database 144 separate from the control panel 104. In step 428 it is determined if the received code matches the required rolling code. If the received code does not match the required code, then the control panel 104 determines that a valid reader did not generate the signal or a valid reader has been tampered with. In response to determining that there is a problem with the reader 112, the control panel 104 performs invalid reader logic (step 432). An invalid reader logic action may include, sounding an alarm, notifying security/maintenance personnel that a reader is defective, not opening a door, disabling a reader by discontinuing power supply thereto, and other appropriate actions associated with determining that a reader is not valid and as are dictated by the particular circumstances. However, if the reader 112 was valid and did generate a valid rolling code, the credential data is analyzed in step 436. If the credential data is determined to be invalid, then the control panel 104 performs invalid credential logic (step 440). An invalid credential logic action may include actions similar to invalid reader logic actions. Different actions may be taken by the control panel 104 in response to determining that a credential is invalid including, taking no action and/or controlling an LED on the reader notifying the holder of the credential that access has not been granted. However, if the control panel 104 can verify both the rolling code data and credential data, then the control panel 104 performs valid message logic (step 444). A valid message logic action may include opening/unlocking a door, unlocking a computer, disabling an alarm, etc. Then if valid rolling codes are based on a list of rolling codes, the control panel 104 increments to the next valid code in the rolling code sequence (step 448). If the validity of the reader 112 could not be determined in step 428 then the control panel 104 typically does not increment to the next valid code in the rolling code sequence. However, if the reader 112 was valid, but the credential could not be authenticated, then a valid reader 112 will expect to increment to the next code in the rolling code sequence. Because of this, the control panel 104 should also increment to the next code in the rolling code sequence so that the valid reader 112 and control panel 104 continue to agree upon a valid rolling code.
Referring now to
A downstream device may be required to send in an update signal every second or fraction of a second for example. Having such a short period between update signals may preclude an attacker from cutting the connection between the upstream device and the downstream device as any interruption in communication may be discovered due to the high frequency of required updates. However, in order to conserve bandwidth, a lower frequency of update may be required.
As noted above a reader 112, intermediate device 120, hub 108, or control panel 104 may be considered an upstream and/or downstream device depending on where it resides in relation to other devices in the system. A first control panel 104 may be connected to a master control panel. The first control panel 104 may be required to update its status to the master control panel in which case the first control panel 104 would be considered the downstream device and the master control panel would be considered the upstream device.
Referring now to
Once the required update rate and number of acceptable missed messages is determined, a variable representing elapsed time is set equal to zero (step 612). During this system initialization a variable representing the number of missed messages is set equal to zero (step 616). Then as time progresses the upstream device waits to receive a signal from a downstream device. When the predetermined amount of time between required updates has passed (step 620), the upstream device determines if it has received a valid rolling code (step 624). The upstream device may require the downstream device to “check-in” right on the required time. Alternatively, a downstream device may only be required to transmit a valid code once every period. In the latter configuration, if a downstream device sends a message in response to reading a credential and appends a valid rolling code with that message, the upstream device may not require another update message from the downstream device during that time span. However, if the upstream device does require the downstream device to transmit a valid rolling code on the required time, even if the downstream device already sent a message with a valid rolling code earlier in the time period, the downstream device will be required to transmit another valid rolling code at the predetermined time or in a predetermined time window.
If the upstream device does receive a valid rolling code at step 624 for that time period, then the method returns to step 612 and the variable representing elapsed time is set equal to zero. If the upstream device does not receive a valid rolling code (e.g. no check-in signal is received or the check-in signal included an invalid rolling code), then the variable representing the number of missed messages is incremented by one (step 628). In step 632, it is determined if the number of missed check-in messages is greater than the acceptable number of missed messages. If the threshold for missed check-in messages has not been realized, then the method returns to step 620 to wait for the next required check in time or time window. If the threshold for missed check-in messages has been exceeded then the upstream device determines that there is a problem with the downstream device, typically a reader, and performs the required steps to notify personnel that the subject downstream device is malfunctioning (step 636).
Referring now to
The rolling code sequence 700 may comprise up to x rolling codes or rolling code generation variables that are required to be transmitted at a check in time up to k periods after the first check in time, where x and k are typically greater than one.
Each rolling code in the rolling code data field 704 may be a unique predetermined rolling code. Alternatively, an algorithm may use the data stored in the rolling code data field 704 in order to generate a valid rolling code. The upstream device will expect rolling code A from a downstream device at time T in order to determine the authenticity of the downstream device. Then at a time later than time T, the upstream device will expect rolling code B. Since a valid downstream device will have the rolling code sequence 700, it will know what rolling code to send and when to send it. A fraudulent reader on the other hand will not have access to the rolling code sequence 700 and thus will not be able to send a valid rolling code to the upstream device at the required time. This will result in the upstream device determining that the downstream device is not valid or is not functioning properly. A valid rolling code generally includes the next rolling code to be sent in the rolling code sequence. As can be appreciated, a less noise sensitive system may be created that identifies more than one rolling code as a valid rolling code. For example, an upstream device may accept the next rolling code up to X more rolling codes in the rolling code sequence. This valid rolling code buffer can be implemented to provide some level of resistance to one or more rolling codes being missed due to noise or other factors.
In an alternative configuration, a prompt signal may be sent from the upstream device to the downstream device asking for the next valid rolling code in the rolling code sequence 700. The prompting signal may be sent via the LED control signal in the case of the Wiegand protocol. When the prompt signal is received at the downstream device, the next rolling code is chosen in the sequence of rolling codes 700. This particular configuration is beneficial in that a predetermined period of reply does not necessarily need to be employed. Rather, a prompt signal may be sent randomly from an upstream device to a downstream device. In order for the downstream device to prove its authenticity to the upstream device, it should generate a valid rolling code and transmit it back to the upstream device.
As can be appreciated by one of skill in the art, the relationship of an upstream device and a downstream device is generally defined by the flow of credential information. The downstream device transmits credential information to an upstream device, which may further forward the information to another upstream device or analyze the information to determine an authenticity of the downstream device. Downstream devices are not limited to a reader 112, but rather may include an intermediate device 120, a credential 116, and/or a control panel 104. Moreover, upstream devices are not limited to control panels 104, but also may include a reader 112, an intermediate device 120, and/or a credential 116.
The present invention, in various embodiments, includes components, methods, processes, systems and/or apparatus substantially as depicted and described herein, including various embodiments, subcombinations, and subsets thereof. Those of skill in the art will understand how to make and use the present invention after understanding the present disclosure. The present invention, in various embodiments, includes providing devices and processes in the absence of items not depicted and/or described herein or in various embodiments hereof, including in the absence of such items as may have been used in previous devices or processes, e.g., for improving performance, achieving ease and/or reducing cost of implementation.
The foregoing discussion of the invention has been presented for purposes of illustration and description. The foregoing is not intended to limit the invention to the form or forms disclosed herein. In the foregoing Detailed Description for example, various features of the invention are grouped together in one or more embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the following claims are hereby incorporated into this Detailed Description, with each claim standing on its own as a separate preferred embodiment of the invention.
Moreover though the description of the invention has included description of one or more embodiments and certain variations and modifications, other variations and modifications are within the scope of the invention, e.g., as may be within the skill and knowledge of those in the art, after understanding the present disclosure. It is intended to obtain rights which include alternative embodiments to the extent permitted, including alternate, interchangeable and/or equivalent structures, functions, ranges or steps to those claimed, whether or not such alternate, interchangeable and/or equivalent structures, functions, ranges or steps are disclosed herein, and without intending to publicly dedicate any patentable subject matter.