Lucent Technologies Remote Port Security Device Users Guide

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Introduction 
Page 1-9 Hardware Components 
1
RPSD Lock or Key Administration Terminal
The administration terminals for both Lock and Key are customer supplied. Any 
administration terminal for the RPSD Lock or for the RPSD Key must meet the 
following requirements:
nAsynchronous
nFull or half-duplex
nStandard RS-232 interface for connection to a DCE interface
nBaud rate in the range 300–19.2K (19.2K is the maximum rate for the DB9 
AUX PORT.)
nAny word size and parity
Use a standard RS-232 cable to connect the administration terminal to the 
DB9/DB25 cable connected to the AUX. PORT of the RPSD Lock or Key. This 
RS-232 cable is not supplied. The AUX. PORT is the same port used if a printer is 
installed. You may wish to install a switch to make changing the AUX. PORT 
connection easier (for example, from a terminal to a printer).
The terminal should initially be set to 9600 bps and 8 bits, no parity. These are 
the factory default settings of the Lock and the Key. You may change these 
parameters later on Lock, Key, and administration terminals.
RPSD Lock Administration Printer
The RPSD Lock requires a serial printer with XON/XOFF flow control.
Connect the printer (via its cable) to the DB9/DB25 cable connected to the AUX. 
PORT of the RPSD Lock. The printer cable is not supplied. This is the same port 
used by the administration terminal. You may wish to install a switch to make 
changing the AUX. PORT connection easier (for example, from a terminal to a 
printer). 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Introduction 
Page 1-10 Software Components 
1
Software Components
The software for the RPSD system is contained within the hardware components 
and does not need to be loaded separately. If you are not installing an RPSD 
Key, you need only set the date and time for the RPSD Lock and, in the case of 
multiple Locks, a Lock ID. If you are installing RPSD Keys, you must do some 
additional initialization on the Lock(s). 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Introduction 
Page 1-11 System Administration 
1
System Administration
The RPSD Lock prevents unauthorized access to the channel used by Lucent 
Technologies personnel to perform maintenance and/or to administer your 
communications system. When you administer the RPSD, keep in mind that 
access via telephone lines is not the only means of breaching the security of your 
system. A system can be breached, for example, by physically intercepting lines 
and adding unauthorized equipment. RPSD users may need to take many 
actions to enhance overall telecommunication security. These actions include, 
but are not limited to, providing physical security for RPSD installation sites 
(locked rooms, cabinets, etc.) and wiring room sites. Monitor the RPSD System 
Activity Log for patterns of activity, such as repeated denied call attempts. 
Contact your computer security group for assistance.
!Security Alert:
The Remote Port Security Device, if properly installed and managed, 
provides a significant and substantial barrier to unauthorized access to a 
dial-up communication port.
The Remote Port Security Device is not impregnable but is an important 
addition to the tools and measures used by system managers to prevent 
unauthorized access to dial-up ports.
Time of Day Access
The RPSD Lock can be administered to prevent access from one or more Key or 
from all Keys during specified times of day. The default setting is no blockage of 
access for any Key user at any time. The administrable parameters are time, 
date, and user ID. Up to 14 separate time restrictions (periods of no access) may 
be set for any one user ID. Time restrictions may overlap.
For example, you can use this feature to prevent any administration of the 
communications system while a system administrator is not present to oversee 
the administration. In this instance, you could administer the Lock to block all 
users from 6:00 p.m. (18:00 hours using a 24-hour clock format) when the system 
administrator leaves the office until 8:00 a.m. (08:00 hours using a 24-hour clock 
format) when the system administrator returns to the office. 
To specify Time of Day Access, see the instructions for the Change Restriction 
command, for the List Restrictions command, and for the User Restrictions 
command in Chapter 3. 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Introduction 
Page 1-12 System Administration 
1
System Activity Log
The System Activity Log retains a log history of the last 500 status messages 
generated by the Lock. Status messages include a history (including date and 
time) of the following RPSD system activity:
nAny RPSD system administration
nCalls received attempting to access the host resource
nThe outcome of any access attempts (connected or failed)
nThe reason for the failure of call attempts
nWhen the call was disconnected
As a new message is generated, the oldest message in the buffer is deleted. The 
most recent 20 messages are displayed on the first page in real-time on the 
RPSD Lock administration terminal. That is, the oldest message scrolls off the 
screen on the administration terminal as the new message is added to the 
bottom. When a printer is connected to the RPSD Lock administration terminal, 
each new message is printed at the bottom of the page as it is received from the 
Lock. This allows you to create a more permanent hard-copy record of status 
messages.
The messages are numbered consecutively from 000 to 999. If a printer is used, 
any breaks in this sequence indicate an interruption of log printing.
Figure 1-4
 shows a sample log history. 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Introduction 
Page 1-13 System Administration 
1
:
Figure 1-4. Sample Log History
The fields of the System Activity Log entries are:
nMessage Authentication Code/ Sequence Number—The Message 
Authentication code generated for each entry on the System Activity Log. 
The code is generated to protect the integrity of the Log History. The 
Message Authentication is followed by a period (“.”) and the sequence 
number of each status message. The messages appear in sequence from 
000 to 999 and then restart at 000.
nDate—The date of the message
nTime—The time the message was generated in 24-hour clock format
nMessage—The status message
In Figure 1-4
, KEY20 is a user ID. Information shown in square brackets is the 
RPSD user ID number (as in the fifth message in Figure 1-4
). Users can be 
assigned the same user ID; the user ID number provides a second means of 
identifying the calling party.
> lh
--- Log History ---
CC85.000 7/12/96 13:23:18 KEY20 -- User Removed OK
D4E2.001 7/12/96 13:23:51 KEY19 -- User Added OK
A011.002 7/12/96 13:24:12 KEY20 -- Admin. User Added OK
6FD2.003 7/12/96 13:26:51 Call Received
12BB.004 7/12/96 13:26:59 Attempt by KEY20 [#4321] Failed 
(4) Blocked User
7EF4.005 7/12/96 13:27:00 KEY20 [#4321] Disconnected
BE31.006 7/12/96 13:27:06 Lucent RPSD Lock - V1.0 - Idle/Locked
A3F3.007 7/12/96 13:27:45 KEY20 -- User Unblocked OK
4C23.008 7/12/96 13:27:55 Call Received
DD52.009 7/12/96 13:28:04 KEY20 [#4321] Connected
21CC.010 7/12/96 13:32:13 KEY20 [#4321] Disconnected
66D3.011 7/12/96 13:32:15 Lucent RPSD Lock - V1.0 - Idle/Locked
B1A3.012 7/12/96 13:32:50 Call Received
D311.013 7/12/96 13:33:02 Attempt by KEY20 [#8765] Failed 
(5) Invalid Response
C453.014 7/12/96 13:32:12 KEY20 [#8765] Disconnected
F67A.015 7/12/96 13:32:17 Lucent RPSD Lock - V1.0 - Idle/Locked
5534.016 7/12/96 13:34:59 Date Changed OK
BA14.017 7/12/96 13:43:55 Call Received
FF32.018 7/12/96 13:44:04 KEY20 [#4321] Connected
BC03.019 7/12/96 13:49:13 KEY20 [#4321] Disconnected
-- End of List -- 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Introduction 
Page 1-14 System Administration 
1
When a user’s access attempt fails, an access failure status message is 
generated indicating the reason for the failure. Table 3-2 on page 3-43
 lists the 
codes and status messages, and the meaning of each failure message. The List 
Statistics command can also be used to get a very brief description for each 
code. For instructions on how to use the Log History command to generate a Log 
History and how to use the List Statistics command, see Chapter 3, “RPSD 
System Administration.”
Single Point Administration
You can use a single administration terminal or printer to administer multiple 
Locks. To use a single administration terminal for multiple Locks, administer the 
Locks from teletype (tty) ports via the UNIXÒ Operating System. To use a single 
printer for multiple Locks, connect a printer-sharing device.
When your system includes multiple Locks, assign a Lock ID to each Lock. The 
ID is included on status messages to allow you to associate system activity with 
each specific Lock. To assign an ID to a Lock, use the ID Set command 
described in the “System Administrator Command Set” in Chapter 3. 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Introduction 
Page 1-15 System Administration 
1
Block Lucent Technologies and Other Key Users
You may wish to block one or more Key users from accessing the RPSD Lock. Do 
this by using the Block User command. You do not need to inform the Key user 
that the Key has been blocked. If a blocked Key user attempts access, the Lock 
blocks the attempt and sends a message to the Lock administration terminal or 
printer, explaining the cause of the failed access. An example of the message 
follows:
The following message is sent to the Key user’s administration terminal:
To block a Key user or Key users, use the Block User command described in the 
“System Administrator Command Set” section of Chapter 3.
Force Connect/Disconnect
The RPSD Lock can be forced to connect an incoming call from any source or to 
disconnect a call in progress. A connection can be forced or a call disconnected 
whether or not the caller is using an RPSD Key.
See the Force Connect and Force Disconnect commands described in the 
“System Administrator Command Set” section of Chapter 3.
!Security Alert:
Use of the Force Connect command bypasses RPSD Lock security. Use 
only with extreme caution!
JPLock 01334 7/24/96 09:33:01 Attempt by KEY20 [#1234] Failed 
(4) Blocked User
>
KEY20 7/24/9609:33:01Attempt Failed (4) Blocked User
> 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Introduction 
Page 1-16 System Administration 
1
Authorized Keys
You may authorize up to 50 RPSD Key user IDs on each RPSD Lock. Ten 
additional Key user IDs are permanently reserved for Lucent Technologies 
personnel to administer and maintain the communications system, peripheral 
equipment, or adjuncts via the RMATS port. The 10 user IDs permanently 
reserved for Lucent Technologies personnel cannot be deleted. However, the 
permanently reserved user IDs can be blocked by issuing a block command on 
the Lock or can be blocked by administering time of day restrictions on the user 
IDs.
The following are the 10 permanent Lucent Technologies RPSD user IDs:
nUser IDs reserved for Lucent Technologies personnel using the INADS 
system
— ATT-INADS1
— ATT-INADS2
— ATT-INADS3
— ATT-INADS4
nUser IDs reserved for Key users and engineers at the Technical Services 
Center in Englewood, Colorado (all products):
—ATT-TSC001
—ATT-TSC002
nUser ID reserved for Lucent Technologies personnel at the Tier 3 location 
at the Denver Works Factory:
— ATT-PECC01
nUser ID reserved for Bell Laboratories field support for System 85 and 
DEFINITY Enterprise Communications Server (ECS), Generic 2
— ATT-LABS01
nUser ID reserved for Bell Laboratories field support for System 75 and 
DEFINITY ECS Generic 1
— ATT-LABS02
nUser ID reserved for Bell Laboratories field support for AUDIX®
— ATT-LABS03
In addition to the 10 Lucent Technologies Key user IDs, 50 additional user IDs 
are available for your own applications. These can be added to or removed from 
the Lock by the Lock administrator as necessary. They can also be blocked or 
restricted in the same ways as the permanent user IDs. Each of the 50 
non-permanent user IDs is matched to a separate Key. 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Introduction 
Page 1-17 System Administration 
1
NOTE:
A single Key can be used to access multiple Locks.
See the Add User command for the procedure for adding users and the Remove 
User command for the procedure for removing users, both described in the 
“System Administrator Command Set” section of Chapter 3. 
						

							Remote Port Security Device
User’s Guide  555-024-402  Issue 1
October 1996
Introduction 
Page 1-18 System Administration 
1