System Security Checklist - Avaya Communication Manager Administrator's Manual

System Security Checklist

Here's some of the steps required for indemnification. Use these to analyze your system
security.
1. Remove all default factory logins of cust, rcust, browse, nms, and bcms and assign
unique logins with 7-character alphanumeric passwords and a 90-day password aging. Use
the list logins command to find out what logins are there.
2. If you do not use Remote Access, be sure to disable it permanently.
Tip:
You can use the display remote-access command to check the status of
Tip:
your remote access.
To disable Remote Access, on the Remote Access screen, in the Permanently Disable
field, type y.
Note:
Avaya recommends that you permanently disable Remote Access using the
Note:
change remote-access command. If you do permanently disable Remote
Access, the code is removed from the software. Avaya charges a fee to restore
the Remote Access feature.
3. If you use Remote Access, but only for internal calls, change announcements or remote
service observing.
a. Use a 7-digit barrier code.
b. Assign a unique COR to the 7-digit barrier code.
The unique COR must be administered where the FRL is 0, the Calling Party
Restriction field is outward, the Calling Permissions field is n on all unique Trunk
Group COR.
c. Assign Security Violation Notification Remote to 10 attempts in 2 minutes.
d. Set the aging cycle to 90 days with 100 call limit per barrier code.
4. If you use Remote Access to process calls off-net or in any way access the public network:
a. Use a 7-digit barrier code.
b. Assign a unique COR to the barrier code.
c. Restrict the COR assigned to each barrier code by FRL level to only the required calling
areas to conduct business.
d. Set the aging cycle to 90 days with 100 call limit per barrier code.
e. Suppress dial tone where applicable.
f. Administer Authorization Codes.
System Security Checklist
Issue 1 June 2005 389