The reader should read the card UID directly from the card memory and not rely on other data that may or may not be present on the card. The local system should obtain the card details – including the card UID – from the Card API using an automated data feed, fetching data at regular intervals to ensure the local access system maintains the current list of ISSUED cards while automatically removing RETURNED, REVOKED and EXPIRED cards from the local access system. Authentication ManagementĬardholder authentication is performed by comparing the card’s unique identifier (UID) read electronically from the physical card to the card UID retrieved from the Card API (Application Programming Interface). public access area into a University building.Ĭonsideration should be given to the sensitivity of the assets located in the area and whether higher security enclaves should be established inside the secure area, e.g., the cage used to protect high value assets in the University Library, the additional access control systems used for Physical Containment Lab (PC3), and server room restricted access. The card can be used to grant the cardholder access from a non-secure area to a secure area e.g. The University Card – in conjunction with the card reader and door controller – forms one part of the University’s security environment. The detailed specification for the current card technology is available on request. The term 'Unique Identifier (UID)' is used to refer to any number, present or future, that is uniquely assigned to a card, for the purpose of identifying a that card. The purpose of this is to equip security decision-makers with the guidance they need to make informed decisions. This document provides best-practice guidance for managing security with regards to the University's electronic card and card systems. University physical security: University Card best practice
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |