6973GH_19_R_00106_SIR_Phase_I_Attachment_4_FRD.pdf

Functional Requirements Document

Remote Video Surveillance System (RVSS) Centralized Network Operations Center /

Security Operations Center (NOC/SOC) and 24/7 Call Center Program

Doc No: ENT15-NOCSOC-00-000001 Rev A

Developed By:

United States Border Patrol, Program Management Office Directorate

1901 South Bell Street Arlington, VA 22202

CAGE: 4NHL7

ii

This Page Intentionally Left Blank iii

REV TE DESCRIPTION

A 4-13-2018 Initial release iv

Table of Contents

1. Introduction

1.1 Purpose

1.2 Scope

1.3 Background

2. System Definition

2.1 System Context

2.2 Service Functional Decomposition Diagram

2.3 Specifications, Standards, and Handbooks

2.4 Document Overview

3. Functional Requirements

3.1 Service Requirements

3.2 System Interface Requirements

3.3 System Control Requirements

3.4 Network Operations Center (NOC) Requirements

3.5 Service Desk

3.6 Security Operations Center (SOC) Requirements

3.7 NOC/SOC Testbed Requirements

4. Non-Functional Requirements

4.1 Security and Privacy Requirements

4.2 Service Life Requirements

4.3 Scalability Requirements

4.4 System Audit Requirements

Appendix 1. Acronyms

Appendix 2. Glossary v

List of Tables

Table 1: Specifications, Standards and Handbooks Referenced

List of Figures

Figure 1: RVSS NOC/SOC and 24/7 Call Center Context Diagram Figure 2: RVSS Centralized NOC/SOC and 24/7 Call Center System Functional Block Diagram

1. Introduction

1.1 Purpose

This Functional Requirements Document (FRD) supports the acquisition of the Remote Video Surveillance System (RVSS) Centralized Network Operations Center and Security Operations Center (NOC/SOC) and 24/7 Call Center Program by the Federal Aviation Administration (FAA), in support of the Department of Homeland Security/Customs and Border Protection

(DHS/CBP).

1.2 Scope

The RVSS NOC/SOC provides network and security monitoring and status of the RVSS networks and components. The RVSS NOC processing controls the system, network and network management functions. The primary services the NOC provides include: System monitoring, Incident Response, System management and Fault/Problems Reporting. The primary services the SOC provides include security compliance activities, including patching and vulnerability scanning, and monitoring of the C2 local area network (LAN) for security compliance. The 24/7 Call Center provides a single point of contact for users and operators to report, document, track, resolve and escalate system problems and account issues. The 24/7 Call Center will use the Government provided trouble ticket system in order to track, respond and report on user and operator issues.

1.3 Background

The Block-1 and Northern Border RVSS are currently monitored and maintained by a centralized NOC/SOC located at the National Data Center in Springfield, VA. The Southern Border RVSS-Upgrade project has established local NOC/SOC capabilities at the U.S. Border Patrol (USBP) Station level. The objective of the acquisition is to consolidate RVSS NOC/SOC systems into a centralized NOC/SOC.

2. System Definition The high-level functions of the services include:

• Network Operations o Monitoring the health and status of equipment o Performing remote maintenance of the sensor equipment

• Security Operations o Security patching o Vulnerability scanning o Monitoring of the C2 local area network (LAN) for security compliance

• 24/7 Call Center o Providing single point of contract for issue reporting and resolution

2.1 System Context

The following RVSS NOC/SOC and 24/7 Call Center Context Diagram includes the system boundary and the required external interfaces, as shown in Figure 1. (Definition: A system context diagram is a diagram that defines the boundary between the system and its environment, showing the entities that interact with it. This diagram is a high level view of a system.)

Note: Green is external to the system.

Figure 1: RVSS NOC/SOC and 24/7 Call Center Context Diagram

From the RVSS Centralized NOC/SOC Supervisor workstation, the supervisor is responsible for the test, approval and installation of system upgrades and patches of the centralized system. This includes the system management of the day-to-day operations of the centralized system. The supervisor is responsible for the generation of problem reports which will be processed by the systems service desk.

The NOC/SOC Manager, which includes authorized USBP and PMOD managers, uses the NOC/SOC Manager portal to view the current status of the RVSS Centralized NOC/SOC System. The portal also allows the Manager to view the status of all Area of Responsibility (AOR) systems, individual AOR systems, and components of an individual AOR. The Manager also has access to reports including performance, configuration and fault management reports.

The Manager can access the status of the Service Desk trouble ticket process.

The NOC Operator manages NOC operations of their assigned AORs that are under their responsibility. This includes monitoring trouble reports that effect their assigned AOR, degraded component operations to include simple trouble resolution. The NOC Operator manages approved system upgrades and patch installations and system management of the day-to-day operations of assigned AORs. The NOC Operator also has access to reports including performance, configuration and fault management reports. The Operator can access the status of the Service Desk trouble ticket process of the responsible AORs.

All SOC Operator workstations are isolated from all other RVSS Centralized NOC/SOC workstations. The SOC Operator manages the RVSS Centralized NOC/SOC system security and the security of all AOR NOC/SOC systems. The SOC Operator manages approved system security upgrades and patch installations and system management of the day-to-day operations of assigned AORs. The SOC Operator is responsible for all password management, including remote password updates and resets. The SOC Operator also has access to reports including performance, configuration, and fault management reports. The Operator can access the status of the Service Desk trouble ticket process of the responsible AORs.

The RVSS Operator requests and receives AOR System and component status, performance, fault, and configuration information. The RVSS Operator requests and receives trouble report and trouble ticket status and estimates of trouble ticket closure.

The RVSS Centralized NOC continuously monitors/requests and receives RVSS AOR system and component status, including receiving live video from a specified individual camera for diagnostic analysis.

Office of Information and Technology (OIT) Security requests and receives system security scans.

The NOC/SOC Testbed provides a test environment to test vendor updates and patches before they are approved to be installed in the production system. The testbed is not connected to the RVSS Centralized NOC/SOC. The testbed replicates the RVSS Centralized NOC/SOC functionality.

2.2 Service Functional Decomposition Diagram

The services provided by the RVSS Centralized NOC/SOC and 24/7 Call Center are decomposed in Figure 2. There are seven functions, and the description of each function is detailed in subsequent sections. Functional areas are virtual, so requirements can be derived and assigned to them but do not reflect any sort of solution or end-state. (Definition: Functional decomposition diagram is defined as a top down representation of process or function. Business analysts use functional development diagram for showing business function and break these functions into lower level operations and processes.)

Figure 2: RVSS Centralized NOC/SOC and 24/7 Call Center System Functional Block Diagram

2.2.1 System Control

System Control provides system management capability to the Centralized NOC/SOC Supervisor. System control allows the supervisor to configure the system so designated workstations are responsible to manage designated AORs.

2.2.2 NOC Subsystem

The NOC provides a 24x7x365 management capability for monitoring the health and status of CBP RVSS and for performing maintenance actions. The NOC provides system monitoring, health and status reporting, and security services for all CBP deployed RVSS. A common reference model that is used by industry in describing network management functions is called FCAPS. FCAPS is an acronym that stands for Fault Management, Configuration Management, Accounting Management, Performance Management, and Security Management. The FCAPS model is described in the International Telecommunication Union (ITU) Telecommunications Management Network (TMN) management functions document (ITU-T 2000).

A multi-system NOC will eliminate the need for dedicated, or program specific monitoring and management capabilities. The NOC provides system monitoring, health and status reporting, and security services for all Border Security Systems deployed. In addition, the NOC provides a single point of contact that users and operators can use to report, document, track, and resolve system problems.

2.2.3 SOC Subsystem

The SOC provides a 24x7x365 security management capability for monitoring system conformance to DHS Security policy. Security monitoring includes monitoring and analysis of network traffic, intrusion detection through the inclusion of Intrusion Detection Systems (IDS), and security event incident response logging. Additionally, it includes conducting and tracking security events, composing and distributing security alert notifications, and preemptive measures such as centralized logging, virus protection, and system hardening.

2.2.4 The DHS OneNet

Multiprotocol Label Switching (MPLS) network provides communications between the Centralized NOC/SOC and the RVSS surveillance systems. All DHS communications between the RVSS surveillance systems and the NOC/SOC will be encrypted.

2.2.5 NOC/SOC Testbed

The NOC/SOC Testbed provides the capability to test and verify hardware, software, and firmware updates prior to implementation into the production system. The testbed is not connected to the RVSS Centralized NOC/SOC. The testbed replicates the RVSS Centralized NOC/SOC functionality.

2.2.6 Manage Interface

The Manager Interface provides a portal for CBP management to view current system status, current trouble ticket status, and current overall system and component performance, configuration and fault management reports.

2.2.7 24/7 Call Center

The 24/7 Call Center provides a single point of contact that users and operators can use to report, document, track, and resolve system problems and account issues. The Call Center also handles system change requests to the system as well as to personal accounts and associated access privileges. The Call Center will use the Government provided trouble ticket system in order to track, respond to, and report on user-reported issues.

2.3 Specifications, Standards, and Handbooks

Table 1 contains specifications, standards, and handbooks that are constraints which express conditions outside the control of the project and may limit design alternatives. The latest version shall apply.

Table 1: Specifications, Standards and Handbooks Referenced

Title Number

International Telecommunication Union, Telecommunication (ITU-T) standard Ethernet frame transfer and availability performance ITU-T Y.1563

International Telecommunication Union, Telecommunication (ITU-T) Series M: TMN AND NETWORK MAINTENANCE

ITU-T M.3010

ITU-T M.3400

Metro Ethernet Forum (MEF), Implementation Agreement MEF 23.1 MI Standards Board (MISB) Technical Reference Material, Constructing a MISP Compliant File and Stream MISB TRM 0909.4

Occupational Safety and Health Administration (OSHA) Technical Manual, Chapter 5, "Noise and Hearing Conservation”

TED 01-00-015 [TED 1-

0.15A]

Open Network Video Interface Forum (ONVIF) standard interface for Video Management System

ONVIF, Profile S specification

Department of Homeland Security (DHS) Sensitive Systems Handbook and Attachments DHS 4300A

System Safety Program Requirements MIL-STD-882 National Telecommunications and Information Administration (NTIA) Manual of Regulations and Procedures for Federal Radio Frequency Management

“NTIA Redbook”

American National Standards Institute (ANSI) Standard for Electromagnetic Compatibility-Radiated Emission Measurement in Electromagnetic Interference (EMI) Control-Calibration of Antennas

ANSI Standard C63.5

Federal Communications Commission (FCC) Electro-Magnetic Compatibility (EMC) Compliance for Un-intentional Radiators

FCC Title 47, CFR Part 15, Class A

Motorola Standards and Guidelines for Communications Sites Motorola R-56 Federal Information Processing Systems (FIPS) for “certified” devices FIPS 140-2 National Institute of Standards and Technology (NIST) SP 800-53 Rev 3 NIST SP 800-53 Rev 3

CBP Physical Security Policy and Procedure Handbook CBP HB 1400-05D

CBP HB 1400-02B

2.4 Document Overview

In this document, the term “shall” expresses a requirement that is mandatory. Threshold (minimum) performance characteristics of the system are identified as (T) and objective (desired) performance characteristics are identified as (O).

3. Functional Requirements

3.1 Service Requirements

3.1.1 The System shall be staffed and operated 24 hours per day, 7 days a week, and 365 days per year.

3.1.2 The System shall have an overall roundtrip latency of no greater than 0.750 seconds (T), 0.500 seconds (O).

3.1.3 The System shall comply with DHS 4300A and Attachments (latest version shall apply) security policy at the Moderate Level.

3.1.4 The System shall comply with National Institute of Standards and Technology (NIST) SP 800-53 Rev 3 (latest version shall apply).

3.1.5 The System shall incorporate physical protection measures compliant with CBP Physical Security Policy and Procedure Handbook HB 1400-05D - HB 1400-02B (latest version shall apply).

3.1.6 The System shall comply with DHS Enterprise Architecture (EA) and DHS Security Architecture (SA).

3.1.7 The System shall protect against Denial of Service (DoS) attacks.

3.1.8 The System (equipment and software) shall be IP Version 6.

3.1.9 The System shall not degrade the performance of the systems that it manages.

3.1.10 The System shall continuously back up all system events, SysLogs and component data for a sliding window within the last 24 hours.

3.2 System Interface Requirements

3.2.1 The System shall interface with a OneNet connection with each AOR which will be a GFE point to point DS3 dedicated duplex line with a bandwidth of 45 MBs.

3.2.2 The System shall interface with a OneNet connection for PKI security which will be a GFE dedicated email line with an overall roundtrip latency of no greater than

5.0 seconds (T), 2.50 seconds (O).

3.3 System Control Requirements

3.3.1 The System shall manage software patches and updated from vendors, OIT, CBP, and DHS.

3.3.2 Upon NOC/SOC Supervisor command, the System shall manage system event definitions.

3.3.3 Upon NOC/SOC Supervisor command, system event definitions shall not degrade system operations.

3.4 Network Operations Center (NOC) Requirements

The NOC is a separate and distinct workstation from the SOC. The NOC provides a 24x7x365 management capability for monitoring the health and status of CBP RVSS and for performing maintenance actions. The NOC provides system monitoring, health and status reporting, and security services for all CBP deployed RVSS. The NOC Operator supervises the entire RVSS network, including troubleshooting, software distribution and updating, router and domain name management, performance monitoring, patch management, vulnerability management, and coordination with affiliated networks. The NOC reporting requirements will comply with ITU-T M.3010, Principles for a telecommunications management network (TMN) and the ITU-T M.3400, TMN management functions.

3.4.1 NOC User Interface Requirements

3.4.1.1 Upon NOC Operator command, the NOC User Interface shall implement and manage user accounts including AOR Operator Accounts and AOR User Accounts.

3.4.1.2 Upon NOC Operator command, the NOC shall remotely force a logoff of any workstation associated with RVSS Systems.

3.4.1.3 Upon NOC Operator command, the NOC shall remotely re-boot and/or re-start any workstation, any server, and any sensor equipment associated with RVSS Systems.

3.4.1.4 Upon NOC Operator command, the NOC shall access and manage the storage of log data, including network logs, and RVSS System logs.

3.4.1.5 Upon NOC Operator command, the NOC shall display data in the order specified by the operator template. Note: The NOC user interface allows the user to specify the layout of data display.

3.4.1.6 Upon NOC Operator command, the NOC shall display or print NOC Reports, network traffic status, component performance health and status, and network performance trends.

3.4.1.7 Upon NOC Operator command, the NOC shall edit fault type and alarm priority.

3.4.1.8 Upon NOC Operator command, the NOC shall install software updates and vendor patches to select or all RVSS Systems.

3.4.1.9 Upon NOC Operator command, the NOC shall display or print network configuration and network topology.

3.4.1.10 Upon NOC Operator command, the NOC shall create custom dashboards to allow quicker access, definition, and understanding of network performance and diagnostics.

3.4.1.11 The NOC User Interface shall display an alert when software updates are available.

3.4.2 NOC Processing Requirements

3.4.2.1 The NOC shall record events/alerts history, deduce events/alerts patterns and correlation events/alerts with any other observed system events/alerts, performance issues, trouble tickets, or security incidents.

3.4.2.2 The NOC shall detect and isolate system events within 300 seconds of occurrence, 99.99% of the time.

3.4.2.3 The NOC shall create a System Performance Analysis Report to include performance trends, Motion Image quality, network link data, network traffic and capacity latency analysis, and component availability.

3.4.2.4 The NOC shall perform network fault management to include the detection, isolation, and corrective response.

3.4.2.5 The NOC shall create a System Fault Report to include detected component failures, failure status, component availability, alerts, fault alarms, and fault priority.

3.4.2.6 The NOC shall maintain a record of all system component restorations to include component identifier, the reason the system restoration was required, along with a description of any associated system events, performance issues, security incidents, or trouble tickets.

3.4.2.7 The NOC shall record the root cause of the system events and component failures, if known.

3.4.2.8 The NOC shall record a list of all system component identifiers for system components affected by the system event along with a description of the corresponding impact for each.

3.4.2.9 The NOC shall manage network configurations and changes for all devices and software.

3.4.2.10 The NOC shall manage and detect changes to hardware and software configurations.

3.4.2.11 Upon NOC Operator command, the NOC shall remove software from network/system components.

3.4.2.12 The NOC shall maintain a record of all software changes, to include a history of any associated back-outs/restores.

3.4.2.13 The NOC shall manage and monitor Border Patrol Station workstations and wall displays.

3.4.2.14 The NOC shall manage Border Patrol Station servers and storage systems.

3.4.2.15 The NOC shall manage portable systems, when connected to the network.

3.4.2.16 Upon NOC Operator command, the NOC shall restore network/system components.

3.4.2.17 Upon NOC Operator command, the NOC shall change network/system configuration settings.

3.4.2.18 The NOC shall track hardware details such as purchase dates, usage, and warranty expiration dates.

3.4.2.19 The NOC shall track software assets such as version, installation and purchase dates, and the latest software updates.

3.4.2.20 The NOC shall create a System Configuration Report to include total System and component health and status, System state changes, network topology, backup and restore configurations, and software versions.

3.4.2.21 The NOC shall filter event /alarms to reduce the number of alarms.

3.4.2.22 The NOC shall suppress (temporarily inhibit) alarms.

3.4.2.23 The NOC shall create a System Accounting Report to include component usage, System usage, threshold status, and database usage.

3.4.2.24 The NOC shall remotely monitor, administratively control and report on RVSS System components such as cameras, radars, laser devices, spot lights, communication elements, workstations, shelter/LAN room monitoring sensors, and C2 elements.

3.4.2.25 The NOC shall remotely monitor, control and report on RVSS System elements such as Uninterrupted Power Supplies (UPS), backup generators, propane tanks, photovoltaic (PV) Systems, and grid power.

3.4.3 NOC Data Storage Requirements

3.4.3.1 The NOC shall store all network and component reports for a sliding window of ninety (90) days in the NOC data storage.

3.4.3.2 The NOC shall store all administrative actions for a sliding window of ninety (90) days in the NOC data storage.

3.4.3.3 The NOC shall retrieve all network and component reports from the NOC data storage.

3.4.3.4 The NOC shall backup the NOC data storage.

3.4.3.5 The NOC shall force a backup before any software modifications are installed.

3.4.3.6 The NOC System backup software shall support configurable incremental and full back up periods with default settings of daily and weekly for incremental and full backups, respectively.

3.5 Service Desk

The Service Desk provides a means for system operators to report system and account issues that they are experiencing and to request changes to the system as well as to their personal accounts and associated accesses. The Service Desk will use a trouble ticket system (USBP ILSS Maximo) in order to track, resolve, escalate, and report on user-reported issues.

3.5.1 RVSS Operator Interface

3.5.1.1 The Service Desk shall maintain a group email box.

3.5.1.2 The Service Desk shall maintain a service desk portal accessible to authorized users via OneNet.

3.5.1.3 The Service Desk shall resolve or escalate service requests in accordance with the following parameters:

3.5.1.3.1 For Priority 1 requests, within 1 hour of receipt, 96% of the time.

3.5.1.3.2 For Priority 2 requests, within 4 hours of receipt, 96% of the time.

3.5.1.3.3 For Priority 3 requests, within 8 hours of receipt, 96% of the time

3.5.2 Trouble Report Processing

3.5.2.1 The Service Desk shall manage a trouble ticket system (USBP ILSS Maximo) to receive, track, and resolve user-reported issues and requests.

3.5.3 Trouble Report Data Base

3.5.3.1 The Service Desk shall record all communications (along with date/time) associated with the trouble ticket (to include all calls, all emails, and all portal communications sent/received by the service desk to the Trouble Report Data Base).

3.5.3.2 The Trouble Report Data Base shall record the Trouble Ticket’s correlation with any related System events, performance issues, security events, or other trouble tickets.

3.6 Security Operations Center (SOC) Requirements

Security Management functionality includes Security services for continuous monitoring, communications and Security event detection, incident management, vulnerability management, and reporting.

3.6.1 SOC User Interface Requirements

3.6.1.1 Upon SOC Operator command, the SOC User Interface shall display security control options.

3.6.1.2 Upon SOC Operator command, the SOC User Interface shall display alerts when unauthorized activities occur on the System.

3.6.1.3 Upon SOC Operator command, the SOC User Interface shall display a logged alert that show unauthorized activities that occurred on the System.

3.6.1.4 Upon SOC Operator command, the SOC shall alert the SOC Operator of a System security event.

3.6.1.5 Upon SOC operator command, The SOC shall restore user profiles.

3.6.1.6 Upon SOC Operator command, the SOC shall display current System vulnerability status.

3.6.2 SOC Processing Requirements

3.6.2.1 The SOC processing shall continuously monitor and analyze system components and network traffic for security incidents.

3.6.2.2 The SOC processing shall manage security events and incidents.

3.6.2.3 The SOC processing shall display System alerts and associated metadata.

3.6.2.4 Upon SOC Operator command, the SOC processing shall administer System security access controls.

3.6.2.5 Upon SOC Operator command, the SOC processing shall administer security access controls of specified data.

3.6.2.6 The SOC processing shall store System alerts and associated metadata to the SOC Data Storage.

3.6.2.7 Upon SOC Operator command, the SOC processing shall retrieve System alerts and associated metadata previously stored the SOC Data Storage.

3.6.2.8 Upon SOC Operator command, the SOC processing shall retrieve System security administrative actions previous stored the SOC Data Storage.

3.6.2.9 Upon SOC Operator command, the SOC processing shall set re-authentication time of user session inactivity.

3.6.2.10 Upon SOC Operator command, the SOC processing shall set lockout time of user inactivity.

3.6.2.11 Upon SOC Operator command, the SOC processing shall set session termination time of user inactivity.

3.6.2.12 The SOC shall manage an Intrusion Detection System (IDS) that monitors the end-to-end system, to detect unauthorized attempts to access the system.

3.6.2.13 The SOC shall maintain up-to-date antivirus software on all system computing resources to include those at the SOC.

3.6.2.14 The SOC shall perform security scans on the entire system and manage vulnerabilities detected.

3.6.2.15 Upon SOC Operator command, the System shall provide port availability or port management to alert, prevent, and report unauthorized universal serial bus (USB) connections to System and network devices.

3.6.3 SOC Data Storage Requirements

3.6.3.1 The SOC shall back up all active user profiles for a sliding window within the last 24 hours.

3.6.3.2 The SOC shall store all security alerts and associated metadata for a sliding window of ninety (90) days.

3.6.3.3 The SOC shall store all security administrative actions for a sliding window of ninety (90) days.

3.7 NOC/SOC Testbed Requirements

3.7.1 Testbed Facility Requirements

3.7.1.1 The Testbed Facility shall be a dedicated, separate, and a controlled access area.

3.7.1.2 The Testbed Facility shall be virtually connected to the In-Service Management Authority / Software Support Authority (ISMA/SSA) support facility located in St. Inigoes, Maryland and Oklahoma City, Oklahoma via commercial internet service provider (ISP).

3.7.1.3 The Testbed Facility shall contain hardware, software, and firmware configurations that duplicate the Centralized NOC/SOC production hardware, software, and firmware configurations.

3.7.1.4 The Testbed Facility shall not be connected to OneNet.

3.7.2 Test Requirements

3.7.2.1 The Testbed shall verify hardware, software, firmware updates meet their specification requirements and System enterprise requirements.

3.7.2.2 The Testbed shall verify vendor updates to include software patches and security patches.

4. Non-Functional Requirements

4.1 Security and Privacy Requirements

The RVSS NOC/SOC System is required to protect its data and information from intrusion, corruption, repudiation, theft, unauthorized access and control of access to the data. Below are the requirements regarding security or privacy based on the DHS 4300A policy.

4.1.1 The System shall record System security events for a sliding window of ninety

(90) days.

4.1.2 The System shall protect security audit data from unauthorized users.

4.1.3 The System shall protect security operator audit tools from unauthorized users.

4.1.4 The System shall create security audit reports, upon operator command.

4.1.5 The System shall meet the moderate level security controls specified in NIST SP 800-53 rev 3.

4.1.6 The System shall provide intrusion detections services.

4.1.7 The System shall operate with the current DHS approved software versions.

4.1.8 The System shall display the DHS CISO banner when a user logs into the System.

4.1.9 The System shall incorporate physical protection measures compliant with CBP Physical Security Policy and Procedure Handbook (HB 1400-02B) and based on the criticality of the operations and missions supported by the information processed by the IT Systems.

4.1.10 The System shall support configurable limits on invalid access attempts before an account is locked in a 24 hour period.

4.1.11 The System shall require passwords to be changed every 90 days.

4.1.12 The System shall require passwords to be reset within 5 minutes of receiving a reset password request.

4.1.13 The System shall initiate a session lock after a configurable period of inactivity with a default value of 20 minutes.

4.1.14 The System shall automatically prompt reset passwords after a configurable time period.

4.1.15 The System shall use Two-Factor Authenticate (2FA) user authentication with a DHS-issued Personal Identity Verification (PIV) card.

4.1.16 The System shall restrict data export to only CBP approved USB devices or DVDs.

4.1.17 The System shall backup System and application data.

4.1.18 The System shall accept DHS Public Key Infrastructure (PKI) Certificates.

4.1.19 The System transport shall use a minimum of AES 256 bit encryption, as specified in FIPS 140-2 standard.

4.1.20 The System shall provide password management services to comply with CBP

HB 1400-05D.

4.2 Service Life Requirements

4.2.1 The Systems service life shall be at least 10 years after Government acceptance of the system.

4.3 Scalability Requirements

4.3.1 The System shall simultaneously support 600 (T), 1,000 (O) operator workstations.

4.3.2 The System shall simultaneously support 10,000 (T), 15,000 (O) RVSS System components.

4.3.3 The System shall manage 10,000 (T), 25,000 (O) events per day. Note: An event is a state change in an item being monitored.

4.4 System Audit Requirements

4.4.1 The System shall perform self-audits including using scanning tools compliant with current DHS policy (currently those tools are Nessus AppDetective, and WebInspect) and anti-virus scans.

Appendix 1. Acronyms

2FA - Two-Factor Authentication

Ao - Operational Availability

ANSI - American National Standards Institute

C2 - Command & Control

CBP - Customs and Border Protection

CM – Configuration Management

DHS - Department of Homeland Security

DoS - Denial of Service

FM – Fault Management

FRD - Functional Requirements Document

H&S - Health & Status

IP – Internet Protocol

IT - Information Technology

MDT - Mean Down Time

MEF - Metro Ethernet Forum

MI - Motion Image / Motion Imagery

MIQ - MI Quality

MTBF - Mean Time between Failures

MTBM - Mean Time between Maintenance

MTTR - Mean Time to Repair

NOC - Network Operations Center

NTIA - National Telecommunications and Information Administration

O – Objective Requirement

OSHA - Occupational Safety and Health Act

PIV - Personal Identity Verification

PKI - Public Key Infrastructure

PM – Performance Management

SOC - Security Operations Center

T – Threshold Requirement

TMN - Telecommunication Management Network

U.S. - United States

USB - Universal Serial Bus

USBP - United States Border Patrol

Appendix 2. Glossary

Actionable Events – Events which require corrective action from NOC/SOC personnel, due to exceptions from non-acceptable performance measurement event, non-arrival of an expected event within a specified period of time, faults which require restoration of service and repair.

Actionable events occur when high priority emergency service is required, and when a security event is detected or from a security violation (e.g. unauthorized user, unauthorized activity or physical tampering).

Alert - A cue or reminder provided by the HMI that prompts and guides the user to take some action.

Alarm – Visually and audibly alerts the operator to a dangerous condition requiring immediate action.

Audible or "plainly audible" - Any sound for which the information content of that sound is unambiguously communicated to the listener, such as understandable spoken speech.

Authorized Personnel - User with valid login and appropriate access.

Auxiliary Power Unit - Unit used to power the close hauls, nose winch, and rotary drive. (In emergency mode is back up for the MPU).

C2 Facility - A room or worksite which supports one or more workstations for RVSS-U, as well as other surveillance systems.

Camera - The camera includes optics, electronics and the H.264 video compression device (encoder). The camera MI is created by optical sensors and electronics sending MI through the encoder out to C2 VMS.

Component - component is an identifiable part of a larger system that provides a particular function.

Configuration Management (CM) – CM identifies location of interface point or component, collects component configuration, and controls component configuration, as specified in this

FRD.

Control Of Motion Image Display – is the control of motion image display of two consecutive MI frames, when operator controls are applied to the camera.

Discover – System queries components to establish system inventory.

Management System (EMS) - A management system which is responsible for managing of system components as defined by International Telecommunication Union (ITU).

False Alarm - The deceptive or erroneous display of a non-emergent event, causing nuisance to the operator. In some cases, repeated false alarms may cause operators to develop alarm fatigue and to start ignoring alarms, knowing that each time it will probably be false.

Fault Report - Is an information report such as alarm report, H&S report, and test results report generated from automatic or manual testing routines.

Fault Management (FM) - FM detects, isolates and corrects abnormal operation of the system and its environment. It provides facilities for the performance of the maintenance phases from ITU-T M.20. The quality assurance measurements for Fault Management include component measurements for Reliability, Availability, and Survivability (RAS).

Health & Status – Is the state of a component, SS or system. It states whether it is operating as intended, degraded, failed or does not operate or function. H&S also states the component configuration and version.

Service desk – Manages, co-ordinates and resolves system Health & Status and support System Operator functions.

MI Quality (MIQ) – Is the quality of the MI for the operator to be able to perform the mission tasks.

Mission Critical SS - Any component required by the System to perform one or more of its intended mission elements (i.e., CBP Mission Elements: Deter, Detect, Track, Identify, and Classify).

Network Connection – Is a network IP to IP link referred to as circuit-specific link.

NOC Alarm Summary – Severity, status, and cause of specified SS or component failure as defined by ITU.

NOC – The NOC controls the system, network, and network management functions. The NOC analyzes problems, performs troubleshooting, communicates with sites and other NOCs, to track problems through resolution The NOC’s primary responsibilities include: System monitoring, Incident Response (Helpdesk), System management (FCAP), Fault/Problems Reporting.

NOC Report – Reporting event in media: display, indicators, recording, lamps, speakers, printers, as defined by ITU.

NOC Data – System Performance, Fault, Configuration, and Accounting data.

Operational Availability (Ao) - The percentage of time that a system will be available to perform its operational functions; Ao = (Mission Capable Time) / (Total Time). To determine how to increase availability, the components of Total Time (i.e., up time plus down time) must be quantified. Up time is simply Mission Capable Time or Mean Time Between Maintenance (MTBM). Down time is the sum of MTTR and MLDT (Mean Logistics Down Time).

Therefore, the formula for predicting Ao can be written as:

Ao = (MTBM) / (MTBM+MTTR+MLDT) = (MTBM) / (MTBM + MDT).

Operator - CBP person using the RVSS C2 User Interface.

Performance Management (PM) - PM evaluates and reports upon the behavior of system components and the effectiveness of the system and components. Its role is to gather and analyze statistical data for the purpose of monitoring and correcting the behavior and effectiveness of the system for the purpose of planning, provisioning, maintenance and the measurement of quality.

Provisioning – Is component configuration and changes in resource selection and assignment, network path design, installed software, and system inventory query.

Response Time - The time it takes the system to react to a given system control as defined by National Telecommunications and Information Administration (NTIA).

RVSS-U System – Is a remotely controlled system of either daylight or infrared cameras mounted to a permanent structure. The images are transmitted, monitored, and recorded at a central location. This system is deployed to monitor large spans of the international border or critical transit notes and the system defined in this specification. The system is technically administrated by the NOC/SOC.

Security event – Is when security violation occurs (e.g. unauthorized user, physical tampering with equipment, etc.).

Time Stamp– An absolute, reliable, common time reference for motion imagery and metadata.

Time Stamping gives precise event occurrences and facilitates photogrammetric analysis, interoperability and exploitation of motion imagery products, as defined by MISB ST 0603.2.

Trouble Report – Created by CBP Operators as trouble tickets originated by proactive failure detection checks. Trouble Reports support action to investigate and clear the trouble and provides access to the status of services and the progress in clearing each trouble.

U.S. Border - Borders of U.S./Canada; and U.S./Mexico.

Video - Sequential or continuous streaming of MI that appear unbroken to the human eye, typically at specified temporal rates greater than 25 frames/second (Hertz). It does not differentiate between digital and analog.