6973GH_19_R_00106_SIR_Phase_I_Attachment_5_RTM.pdf

Requirements Traceability Matrix (RTM)

Remote Video Surveillance System (RVSS)

Centralized Network Operations Center /

Security Operations Center (NOC/SOC) and

24/7 Call Center Program

Doc No: USBP-PMO-NOCSOC-00-000001 Rev. B

Developed By:

United States Border Patrol, Program Management Office Directorate

1901 South Bell Street, Arlington, VA 22202

CAGE: 4NHL7

Doc No: USBP-PMO-NOCSOC-00-000001 (RevB) Centralized NOCSOC Reqmts Traceability Matrix

THIS PAGE INTENTIONALLY BLANK

TABLE OF CONTENTS

1. Introduction

1.1 Purpose

1.2 Scope

1.3 Background

2 Requirements Traceability Matrix

2.1 RTM Information

Appendix 1. Acronyms

Appendix 2. Glossary

1. Introduction

1.1 Purpose

This Requirements Traceability Matrix (RTM) supports the acquisition of the Remote Video

Surveillance System (RVSS) Centralized Network Operations Center and Security Operations

Center (NOC/SOC) Program by the Federal Aviation Administration (FAA), in support of the

Department of Homeland Security/Customs and Border Protection (DHS/CBP).

1.2 Scope

This RTM identifies 120 functional and non-functional requirements that were derived from a functional analysis of the RVSS systems. This RTM defines the priority and the verification method for each requirement. The RVSS NOC/SOC and 24/7 Call Center 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 as well as a single point of contact for problem reporting, escalation, and resolution.

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 (RVSS-U) 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 Requirements Traceability Matrix

2.1 RTM Information

Table 1 defines the requirement priorities and verification methods for the associated RTM, which is shown in Table 2.

Table 1: RTM Column Descriptions

Item Column Title Content/Description

1 Rqmt Item # Sequential numbering of requirements (220 total)

2 Can Offeror Meet (Yes / No) Offeror’s to respond with “Yes” or “No” as to whether they can meet the requirement

3 Requirement Statement Self-explanatory

4 Requirement Priority

1 Critical Priority: Program Critical

2 High Priority: Mandatory

3 Moderate Priority: in contractor’s design space, may be modified

4 Optional Priority: in contractor’s design space, may be eliminated

5 Desired Verification Method

The desired verification method type to validate the requirement

Analysis: the use of recognized analytical techniques to interpret or explain the behavior/performance of the system element.

Demonstration: the performance of operations at the system/sub-system level where visual observations are primary means of verification the system meets requirements.

Inspection: the visual inspection of equipment and evaluation of drawings/specifications and other pertinent design data and processes are used to verify conformance with characteristics such as physical, material, part and product marking and workmanship.

Test: an activity designed to provide data on the functional features and performance characteristics of equipment operations in an operational environment under fully controlled and traceable conditions.

2.2 Requirements Traceability Matrix Details

Table 2 describes the requirements and the associated priority and verification method for each.

Table 2. Requirements Traceability Matrix

Reqm Item No.

Can Offeror Meet?

(Yes / No) Requirement Statement Priority

Desired Verification

Method

SYSTEM REQUIREMENTS

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

1 Demo

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

2 Test

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

2 Inspection

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

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).

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

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

2 Inspection

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

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

2 Analysis

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

2 Demo

System Interface Requirements

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.

2 Demo

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).

System Control Requirements

Reqm Item No.

Can Offeror Meet?

(Yes / No) Requirement Statement Priority

Desired Verification

Method

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

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

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

2 Demo

NOC User Interface Requirements

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

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

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.

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

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.

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

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

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

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

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

Reqm Item No.

Can Offeror Meet?

(Yes / No) Requirement Statement Priority

Desired Verification

Method

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

2 Demo

NOC Processing Requirements

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.

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

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.

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

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

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.

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

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.

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

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

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

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

Reqm Item No.

Can Offeror Meet?

(Yes / No) Requirement Statement Priority

Desired Verification

Method

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

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

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

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

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

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

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

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.

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

2 Demo

48 The NOC shall suppress (temporarily inhibit) alarms. 2 Demo

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

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.

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.

2 Demo

NOC Data Storage Requirements

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

Reqm Item No.

Can Offeror Meet?

(Yes / No) Requirement Statement Priority

Desired Verification

Method

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

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

2 Demo

55 The NOC shall backup the NOC data storage. 2 Demo

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

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.

2 Demo

Service Desk

58 The Service Desk shall maintain a group email box. 2 Demo

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

3.5.1.3 The Service Desk shall resolve or escalate service

requests in accordance with the following parameters:

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

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

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

2 Demo

Trouble Report Processing

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

2 Demo

Trouble Report Data Base

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).

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.

SOC User Interface Requirements

Reqm Item No.

Can Offeror Meet?

(Yes / No) Requirement Statement Priority

Desired Verification

Method

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

display alerts when unauthorized activities occur on the System.

display a logged alert that show unauthorized activities that occurred on the System.

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

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

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

2 Demo

SOC Processing Requirements

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

The SOC processing shall manage security events and incidents.

The SOC processing shall display System alerts and associated metadata.

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

administer security access controls of specified data.

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

retrieve System alerts and associated metadata previously stored the SOC Data Storage.

retrieve System security administrative actions previous stored the SOC Data Storage.

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

lockout time of user inactivity.

Reqm Item No.

Can Offeror Meet?

(Yes / No) Requirement Statement Priority

Desired Verification

Method session termination time of user inactivity.

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

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

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

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.

2 Demo

SOC Data Storage Requirements

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

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

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

2 Demo

NOC/SOC Testbed Requirements

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

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).

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

2 Demo

94 The Testbed Facility shall not be connected to OneNet. 2 Demo

Test Requirements

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

Reqm Item No.

Can Offeror Meet?

(Yes / No) Requirement Statement Priority

Desired Verification

Method

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

2 Demo

Security and Privacy Requirements

The System shall record System security events for a sliding window of ninety (90) days.

The System shall protect security audit data from unauthorized users.

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

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

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

2 Inspection

102 The System shall provide intrusion detections services. 2 Demo

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

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

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.

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

3 Demo

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

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

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

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

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

Reqm Item No.

Can Offeror Meet?

(Yes / No) Requirement Statement Priority

Desired Verification

Method

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

2 Demo

113 The System shall backup System and application data. 2 Demo

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

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

The System shall provide password management services to comply with CBP HB 1400-05D.

2 Inspection

Service Life Requirements

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

2 Inspection

Scalability Requirements

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

The System shall simultaneously support 10,000 (T), 15,000

(O) RVSS System components.

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.

2 Analysis

System Audit Requirements

The System shall perform self-audits including using Nessus AppDetective, and WebInspect and anti-virus scans.

Appendix 1. Acronyms

2FA - Two-Factor Authentication

Ao - Operational Availability

ANSI - American National Standards Institute

BDD - Block Definition Diagram

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 Imagery

MIQ - MI Quality

MTBF - Mean Time between Failures

MTBM - Mean Time between Maintenance

MTTR - Mean Time to Repair

NOC - Network Operations Center

NFR - Non-functional requirements

NTIA - National Telecommunications and Information Administration

O – Objective Requirement

OSHA - Occupational Safety and Health Act

OTIA - Office of Technology Innovation & Acquisition

PIV - Personal Identity Verification

PKI - Public Key Infrastructure

PM – Performance Management

RVSS-U - Remote Video Surveillance System Upgrade

SC - System Components

SM - System Management

SNMP - Simple Network Management Protocol

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, as defined in

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-U 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.

End of Document