Proprietary Information Notice / Freedom of Information Act (Foia) Notice

ETM® System Test Plan

Test Plan

For

The ETM® System

November 2002

PROPRIETARY INFORMATION NOTICE / FREEDOM OF INFORMATION ACT (FOIA) NOTICE

THIS DOCUMENT CONTAINS TRADE SECRETS AND/OR PROPRIETARY, COMMERCIAL, OR FINANCIAL INFORMATION NOT GENERALLY AVAILABLE TO THE PUBLIC. IT IS CONSIDERED PRIVILEGED AND PROPRIETARY TO THE OFFEROR, AND IS SUBMITTED IN CONFIDENCE WITH THE UNDERSTANDING THAT ITS CONTENTS ARE SPECIFICALLY EXEMPTED FROM DISCLOSURE, AND SHALL NOT BE DISCLOSED BY THE RECIPIENT [WHETHER IT BE GOVERNMENT (FEDERAL, STATE, LOCAL, OR FOREIGN), PRIVATE INDUSTRY, OR NON-PROFIT ORGANIZATION], AND SHALL NOT BE DUPLICATED, USED, OR DISCLOSED IN WHOLE OR IN PART FOR ANY PURPOSE OTHER THAN TO EVALUATE THIS PROPOSAL, WITHOUT THE EXPRESS WRITTEN CONSENT OF SECURELOGIX CORPORATION OF SAN ANTONIO, TEXAS.

Prepared by:

SecureLogix Corporation

13750 San Pedro Ave., Suite 230

San Antonio, Texas 78232

(210) 402-9669

(800) 817-4837

(210) 402-6996 (Fax)

TABLE OF CONTENTS

1.0Purpose

1.1Functional Requirements

1.1.1Connectivity

1.1.2Call Type Discrimination

1.1.3Policy Triggers

1.1.4Generating Tracks

1.1.5Other Telco Functions

1.1.6Report Generation

1.1.7Enterprise Policy Execution

2.0 System Test Cases

2.1Prerequisites

2.2ETM™ System Functional Test Cases

Test Case #1 – Connectivity

Test Case #2 – Call Type Discrimination

Call Type Voice

Call Type Fax

Call Type Modem

Call Type STU-III

Call Type Video Teleconferencing

Test Case #3 – Policy Triggers

Call Direction

Source Telephone Number

Destination Telephone Number

Call Type Voice

Call Type Fax

Call Type Modem

Time of Day / Day of Week

Test Case #4 – Generating Tracks

Track Action – Log

Track Action – Alert

Track Action – Email

Track Action – Page

Track Action – SNMP Alert

Test Case #5 – Other Telco Functions

Detection and Reporting of Telco Service Events

Loss of IP Network Connectivity

Loss of Power to Appliance

Unauthorized Telnet to Appliance

Modification of the Emergency Group

Test Case # 6 – Reports

Generating a Predefined Report

3.0Enterprise Test Cases

3.1Prerequisites

3.2ETM™ System Enterprise Test Case

Test Case #1 – Remote Security Policy Installation and Notification

4.0Acceptance Documentation

1.0Purpose

The purpose of this Test Plan is to provide an objective acceptance testing procedure to customer witnesses. Each test case will include a section for the installation technician and the customer to document the completion of the test case. Successful completion of all test objectives will be the prerequisite to allow the customer to sign the appropriate formal acceptance documentation. The test will be conducted from the server location and will first verify functionality at the server location, and then demonstrate enterprise connectivity to subordinate locations.

1.1Functional Requirements

The installation technician will execute an objective demonstration of key functional capabilities for a customer witness.

1.1.1Connectivity

All distributed elements of the ETM® system must be capable of communicating with each other. Successful connectivity includes the ability to connect remote clients, push policies to remote appliance arrays and communicate with the report server on centralized management servers.

1.1.2 Call Type Discrimination

The ETM Appliances are capable of correctly discriminating between voice, fax, modem, STU-III, and Video teleconferencing traffic. This test case will verify that the appliances are correctly configured for the local telephony signaling types and are capable of recognizing all types of call traffic.

1.1.3Policy Triggers

This test case will verify that the ETM system is capable of triggering policy execution calls based on call direction, source telephone number, destination telephone number, call type and time of day or day of week.

1.1.4Generating Tracks

This test case will verify that the ETM system is capable of generating all track actions to include log, alert, email, page and SNMP traps.

1.1.5Other Telco Functions

This test case will verify that the ETM system is capable of other Telco functions such as alerting based on various Telco events, policy execution without network connectivity to the server, uninterrupted telephone service during power loss, denying and alerting on unauthorized Telnet request to the appliances. It will also demonstrate the ability to modify the Emergency Group and provide alerts whenever calls are made to emergency numbers.

1.1.6Report Generation

The ETM system is capable of generating reports from both the security logs and audit logs. This test case will verify authorized clients are capable of generating reports from the remote report server.

1.1.7Enterprise Policy Execution

The ETM system is capable of enforcing security policy across the enterprise. This test case will verify remote connectivity to subordinate bases and the ability to install security policy and receive notifications from those remote bases when that policy is triggered.

2.0 System Test Cases

Functional requirements are derived from the functions of the individual units as well as the ETM system as a whole. Successful completion of these test cases will demonstrate the proper functioning of the ETM system and the successful integration of all spans and appliances.

2.1Prerequisites

Prior to executing the functional test cases, the following test prerequisites must be satisfied:

1. The IP network is properly configured and fully operational

1. All appliances are connected to the telephone trunks and are properly recognizing call traffic
2. All ETM System distributed elements (clients, servers) are configured for proper communication
3. The ETM system is correctly parsing SMDR data from the PBX as applicable
4. Caller ID, Automatic Number Identification (ANI), Dialed Number Identification Service (DNIS) or Integrated Services Digital Network (ISDN) D-Channel information is configured for “source number recognition” where available
5. Sufficient telephones, faxes and modems are available at the test site along with the necessary equipment to receive those calls
6. Open the Channel Monitor Tool
7. Open the Alert Tool

ETM® System Functional Test Cases

2.2 ETM® System Functional Test Cases

The following test cases will demonstrate the installed ETM® system is operating properly and meets all functional and operational requirements.

Test Case #1 – Connectivity

Objectives: All distributed elements of the ETM system must be capable of communicating with each other. The test will show that that through any client workstation you will be able create a policy and push it down to all the appliance arrays through the ETM server.

Procedures: Use the functional system diagram of the installed system to explain to customers which elements of the system are being exercised to communicate with other elements. This test case begins by logging into the server through a client and creating a policy that will be pushed to all the appliances. The Alert Tool will be used to verify connectivity. You will connect to the report service from a remote client, retrieve data and preview a report to verify connectivity to the report service.

Steps:

1. From the TeleView™ Client, log into the ETM server.

1. From the TeleView Client select Start, Run then CMD to open a command system window and then type “ipconfig,” Extract client IP address and record ______. Exit the command window.

1. From the Server menu, select Admin menu, select Server Administration, select the Client Hosts tab, and verify IP address from client above is on list.

1. On the Tree Pane, expand span group array, verify the span icons are green indicating they are communicating with the Management Server.

1. In the Security Policy Editor, click File select New. The new Security Policy Dialog appears, enter a unique name for the policy then click OK, record the name of the policy______then select OK.

1. Select the array you want the security policy installed on by placing a check in the appropriate box and click ok.

1. With the new security policy open in the Security Policy Editor, click File and Save.

1. Verify connectivity by adding a rule to the policy as illustrated, and exercising the policy by creating a simple alert to the client. Click on Edit, select Add Rule, and select Bottom. Right click on the rule in the Track column, select Add Object, then select Real Time Alert. Click on File and select Save.

1. On the Tree Pane, right click on the policy just created, and select Install

1. In the Security Policy Editor, click on Tools, and select Alerts.

1. Place a call with your cell phone to any number within the organization being monitored by the ETM system, record number______. Open Alert Tool, and verify receipt of the Real Time Alert.

1. Re-install the default security policy to stop receipt of the alerts.

1. Ensure the TeleAudit® Report Service is running on the server.

1. At the TeleView Client in the Security Policy Editor click on Tools, and select Reports, wait for the Reports Tool to initialize.

1. Select a sample report, preferably a report that shows data for the previous hour such as All Calls by Call Type. Select the Date and time for both the report From and To fields. Edit the From field to specify how far back in time you wish to extract log data to create this report keeping in mind how long the system has been logging information. Generally you will be able to select a report type that is suitable for a one-hour retrieval and that amount of log data will be available on the server.

1. At the Source drop down menu, select Audit as the log source to build the report.

1. Select Preview to begin building a report. As this is most likely a newly installed system, there may not be a significant amount of log data stored in the server to extract and build a report. The report will be displayed automatically after it has complied all the data from the given parameters in step 15.

1. If a printer has been defined for the network, verify the report can be printed without errors.

Installation Technician Initials ______

Customer Initials ______

Test Case #2 – Call Type Discrimination

Objectives: The ETM Appliances correctly discriminate between voice, fax, modem, STU-III, and Video Teleconference (VTC) traffic. This test case will verify that the appliances are correctly configured for the local telephony signaling types and are capable of recognizing these types of call traffic.

Procedures: Using the policy created for Test Case #1, modify the rule as shown to demonstrate call type discrimination. Make calls of each type and verify the correct discrimination on the Channel Monitor.

Steps:

1. Modify the test policy as illustrated.

1. On the Tree Pane, right click on the policy just created, and select Install.

1. From the Security Policy Editor, select the Switch that the call will be going out over and right click on it, select the Channel Monitor Tool to verify call type.

Call Type Voice

1. Call Type Voice – Use any site telephone monitored by the ETM system to call any number outside the customer site that will participate in the test. If no other number is available, place the call to an appropriate cell phone, find the call on the Channel monitor, and continue talking until the call type “voice” is displayed on the channel monitor.

Call Type Fax

1. Call Type Fax – Using a fax machine at the site being monitored by the ETM system and call a known fax number (local fax number preferred), and actually send a fax. Open the Channel Monitor Tool and verify the call type “fax” is shown on the Channel Monitor.

1. Record customer site telephone number ______

1. Record telephone number called ______

Call Type Modem

1. Call Type Modem – Use a modem at the customer site being monitored by the ETM system and call a known modem number (local ISP number preferred) and actually connect the modems. Keep the call active, open the Channel Monitor Tool and verify the call type “modem” is shown on the Channel Monitor.

1. Record customer site telephone number ______

b. Record telephone number called ______

Call Type STU-III

1. Call Type STU-III (if applicable) – Use a STU-III at the customer site to call a known STU-III number off site, on a line being monitored by the ETM system and actually connect the STU-IIIs in the “Secure” mode. Find the call on the Channel Monitor Tool and keep the call in place until the call type “STU-III” is shown as call type on the Channel Monitor.

1. Record customer site telephone number ______

1. Record telephone number called ______

Call Type Video Teleconferencing

8. Call Type Video Teleconferencing (VTC) (if applicable) – If possible actually set up a VTC session, open the Channel Monitor Tool and verify the call type “WIDEBAND” is shown as call type on the Channel Monitor.

Installation Technician Initials ______

Customer Initials ______

Test Case #3 – Policy Triggers

Objectives: This test case will demonstrate that the ETM system is capable of triggering policy execution based on call direction, source telephone number, destination telephone number, call type and time of day or day of week.

Procedures: Each of the possible conditions for triggering a policy will be tested individually as independent variables. Testing each condition as an independent variable is central to proving that the ETM system is also capable of more complex, multiple-condition variables such as terminating calls based on call type and destination telephone number.

Steps:

Call Direction

1. Call Direction – The following steps will demonstrate that the ETM system is capable of triggering a policy based on call direction.

1. Edit the test policy to generate alerts on inbound calls.

1. On the Tree Pane, right click on the policy and select Install.

1. Open the Channel Monitor Tool and the Alert Tool. Using any telephone at the customer site being monitored by the ETM system, place a call to your cell phone and verify connectivity. While keeping the call active, open the Channel Monitor Tool and verify the call direction is outbound. Open the Alert Tool and verify that there was no alert generated.

(1) Record customer site telephone number ______

(2) Record telephone number called ______

1. Place a call from your cell phone to the same number above or to any other number being monitored by the ETM system, open the Channel Monitor Tool and verify the call direction is Inbound. Open the Alert Tool and verify receipt of the Real Time Alert.

(1) Record customer site telephone number ______

(2) Record telephone number called ______

1. Edit the test policy to resume default status: call direction-any, source-any, destination-any, call type-any, time-any, action-allow, track-none, and install-any.

1. Install the default policy.

Source Telephone Number

1. Source Telephone Number – The following steps will demonstrate that the ETM system trigger policy execution based on source telephone number. Note: This test case requires the customer’s telephone lines to be provisioned with Caller ID, ANI or have an ISDN-PRI D-channel providing the source telephone number. If the lines are not equipped with these services, skip these steps and move on to step 3.

1. Edit the test policy to terminate calls from a specific telephone number and generate alerts as illustrated below.

1. On the Tree Pane, right click on the policy and select Install.

1. Using any telephone at the customer site being monitored by the ETM system, place a call TO your cell phone and verify connectivity. While keeping the call active, open the Channel Monitor Tool and verify the call destination is the telephone number of your cell phone. Open the Alert Tool and verify that the call is not being terminated and that there was no alert generated.

(1) Record customer site telephone number ______

(2) Record telephone number called ______

1. Place a call FROM your cell phone to the same number as above or to any other number being monitored by the ETM system. Open the Channel Monitor Tool and verify the call source is your cell phone number, and the call terminated. Open the Alert Tool and verify receipt of the Real Time Alert.

(1) Record customer site telephone number ______

(2) Record telephone number called ______

1. Edit the test policy to resume default status: call direction-any, source-any, destination-any, call type-any, time-any, action-allow, track-none, and install-any.

1. Install the default policy.

Destination Telephone Number

1. Destination Telephone Number – The following steps will demonstrate that the ETM system is capable of triggering policy based on the destination telephone number.
2. Edit the test policy to terminate calls to a specific telephone number and generate alerts as illustrated below.