Home' RTCA Documents for Review : DO-230H FRAC Contents 82
© 2017, RTCA, Inc.
Configuration of field controllers to accommodate the access portal hardware as required at each
portal to implement policies in the security plan
Establish naming conventions of system components for proper identification and location. As an
example “Reader at West entrance ATC Tower” and intrusion detection sensors such as: “Door
contact at TSA Entrance”
Log maintenance and service activities
The PACS application software enables central management of the various hardware components
comprising the PACS and is responsible for communication to the local Field Controllers, Readers, Alarm
Sensors, and the Security Management Server.
Selection of the PACS application software should be a primary focus of the system acquisition process.
Determine integration requirements to subsystems, such as ID badging, video systems, intercom systems,
intrusion detection systems, vehicle/operator authentication systems, etc. The software should have a user
interface that enables PACS operators to receive and respond to alarms in a timely manner with a graphical
user interface and multimedia alarm annunciation.
Local policies may require a combination of two or more authentication factors to cross a boundary to a
restricted area. Card + PIN and Card +PIN + Biometric are examples of traditional multifactor
authentication. Deployments of credentials that are based upon FIPS 201 are increasingly common at the
federal level and these types of credentials could be used as access credentials in airports. PACS software
should be capable of supporting both these as well as traditional card technologies.
If an airport operator chooses to support federal identification credentials, local airport policies should be
considered. This includes training requirements, challenge policies, and badge accountability requirements.
The PACS software should be an “open architecture” with an open database connectivity compliant
database structure that allows an efficient and effective interface with the internal and external variety of
products and vendors providing IDMS and other security-related functions.
Organizations such as the Security Industry Association (SIA) as well as others are excellent sources of
information on standards for this level integration and data exchange methods.
The software should be “scalable” to allow for growth without having to replace or upgrade major software
components. It must support the bandwidth and network traffic caused by access transactions at card readers
and other field devices.
The software should have authentication and encryption support to prevent access from unauthorized users.
Features such as “automatic logoff” should be supported that prevent unattended computers from being
tampered with. The database structure should be such that sensitive information is not vulnerable by being
accessed or transmitted across communication lines. [Refer: Biometrics Section 3.]
Peripheral software modules, such as report generation programs, cardholder and identity record
management programs, video capture, alarm map processing, system administrator programs, mustering,
guard tour software, etc., should be considered as part of a single security management system. It is
recommended that the aforementioned is located at a secure facility such as a Security Operations Center.
PACS software should have the following minimum characteristics:
Links Archive Navigation Previous Page Next Page