Electronic Physical Access Control Systems
Overlay Name: Electronic Physical Access Control System
Overlay Publication Date: April 2021
Technology or System: Electronic Physical Access Control System (ePACS)
Overlay Author: PACS Modernization Working Group (PACSmod WG)
Comments: Electronic Physical Access Control Systems (ePACS) use a combination of IT components and physical security elements (e.g., card readers, doors/locks) to enable access to real-world resources such as secured facilities or controlled areas within facilities. This overlay provides a standardized template for Chief Security Officers (CSOs) and other ePACS professionals working to secure Federal facilities in a secure and interoperable fashion. Additionally, it should help to inform those Authorizing Officials (AOs) asked to evaluate the cyber specific risks posed to the IT infrastructure comprising its ePACS.
Overlay Point of Contact: Matthew Arnold
Return to Control Overlay Repository Overview
Disclaimer Statement The National Institute of Standards and Technology (NIST) has established the Security Overlay Repository as a public service. Security control overlays are made available by NIST on an “AS IS” basis with NO WARRANTIES Some submitted overlays may be available for free while others may be made available for a fee. It is the responsibility of the User to comply with the Terms of Use of any given overlay. Overlay users are solely responsible for determining the appropriateness of using and distributing the security control overlays. User assumes all risks associated with their use, including but not limited to compliance with applicable laws; damage to or loss of data, programs or equipment; and the unavailability or interruption of operation. NIST MAKES NO WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR STATUTORY, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT AND DATA ACCURACY
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
