UNIVERSAL VALIDATION MODULE FOR ACCESS CONTROL SYSTEMS
First Claim
1. A validation device for an access control system, comprising:
- modular communication interfaces that provide coupling to the access control system;
at least one processor; and
a computer readable storage medium storing executable code that is executable by the at least one processor, the computer readable storage medium including;
executable code that receives cardholder data in connection with an access request at an access point controlled by the access control system;
executable code that validates the cardholder data;
executable code that, after validation of the cardholder data, extracts ID information from the validated cardholder data; and
executable code that sends the extracted ID information to an access decision component of the access control system.
2 Assignments
0 Petitions
Accused Products
Abstract
A validation module provides for the upgrading of a physical access control system (PACS) to full HSPD-12 compliance without requiring modification or replacement of the existing PACS. The validation module may contain all of the validation functionality required by federal specifications and technical requirements. The validation module may be installed between an existing PACS panel and a supported card/biometric reader. Readers may be selected based on assurance level requirements, e.g., contactless or contact readers for low and medium assurance level areas and full biometric readers for high assurance areas. The validation module may validate a card according to the assurance level setting, extract ID information from data on the card and then pass the ID information to the PACS panel for an access decision. Cardholder data captured by one validation module may be distributed to other validation modules of the PACS using a management station.
-
Citations
23 Claims
-
1. A validation device for an access control system, comprising:
-
modular communication interfaces that provide coupling to the access control system; at least one processor; and a computer readable storage medium storing executable code that is executable by the at least one processor, the computer readable storage medium including; executable code that receives cardholder data in connection with an access request at an access point controlled by the access control system; executable code that validates the cardholder data; executable code that, after validation of the cardholder data, extracts ID information from the validated cardholder data; and executable code that sends the extracted ID information to an access decision component of the access control system. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 21)
-
-
10. A non-transitory computer readable medium storing executable code executable by the at least one processor, the computer readable storage medium comprising:
-
executable code that receives cardholder data in connection with an access request at an access point controlled, by the access control system; executable code that validates the cardholder data; executable code that, after validation of the cardholder data, extracts ID information from the validated cardholder data; and executable code that sends the extracted ID information to an access decision component of the access control system. - View Dependent Claims (11, 12, 13, 14, 15, 16, 22)
-
-
17. An access control system, comprising:
-
an access decision component that controls access through an access point; a reader disposed at the access point that extracts cardholder data from a credential presented at the access point; a validation module coupled to the reader and the access decision component, wherein the validation module includes; modular communication interfaces that couple the at least one validation module to the access decision component; at least one processor; and a computer readable storage medium storing executable code executable by the at least one processor, the computer readable storage medium including; executable code that receives the cardholder data from the reader; executable code that validates the cardholder data; executable code that, after validation of the cardholder data, extracts ID information from the validated cardholder data; and executable code that sends the extracted ID information to the access decision component. - View Dependent Claims (18, 19, 20, 23)
-
Specification