117
Programming Operations Guide
Chapter 4
Managing system and user security access levels
This section provides information about how you can set up and maintain the access security to
your system by users and client applications.
To define security parameters for the system and for users, you need to consider what level of
security you need to achieve to meet your network security standard. Note that the default security
settings are not set to their maximum secure settings and can be changed to suit your specific
requirements. If you change the default settings, ensure that you understand the interoperability
implications between your system and client applications, the computer you use to access the
system, and network impacts. For instance, some levels of security are not compatible with clients
running Windows
©
95
©
, 98
©
, or ME
©
.
Unified Manager security considerations include:
•
How long you want the Unified Manager to remain open if there is no input from the user.
Refer to
“Setting the interface timeout” on page 118
.
•
If you want to use secure web access to Unified Manager through SSL (Secure Sockets Layer).
Note that SSL encryption does not secure the Configuration Menu. To secure communication
with the Configuration Menu, a VPN client connection is required. Refer to
“Setting system
security compatibility levels” on page 119
and
“Virtual Private Networks (VPN)” on page 753
.
•
How much access to the Unified Manager interface users are allowed. Access is based on user
privileges defined through user group membership.There are two default administrator
accounts,
ee_admin
and
supervisor,
which both also have default dial-in access privileges
.
Refer to
“Managing access passwords” on page 121
. This section also contains information
about determining password and lockout policies.
!
Security note:
This symbol will be used throughout this section to indicate areas of
possible security concern, primarily in regard to default settings that could pose a security
risk if they are not changed.
!
Security note:
Minimum configuration should include changing all default system
passwords.
!
Summary of Contents for BCM 3.7
Page 4: ...4 Software licensing N0008589 3 3...
Page 32: ...32 Contents N0008589 3 3 W 937 Index 939...
Page 46: ...46 Tables N0008589 3 3...
Page 64: ...64 How to get help N0008589 3 3...
Page 90: ...90 Manually activating Telnet N0008589 3 3...
Page 116: ...116 Delayed system restart N0008589 3 3...
Page 194: ...194 Configuring a data module N0008589 3 3...
Page 276: ...276 Setting line telco features N0008589 3 3...
Page 310: ...310 Using COS passwords N0008589 3 3...
Page 364: ...364 Enhanced 911 E911 configuration N0008589 3 3...
Page 380: ...380 Renumbering DNs N0008589 3 3...
Page 398: ...398 Saving wizard pages on your computer N0008589 3 3...
Page 458: ...458 Voice Mail settings N0008589 3 3...
Page 488: ...488 Setting system telco features N0008589 3 3...
Page 508: ...508 Other programming that affects public networking N0008589 3 3...
Page 522: ...522 PRI networking using Call by Call services N0008589 3 3...
Page 592: ...592 Monitoring Hunt groups N0008589 3 3...
Page 636: ...636 Configuring Double Density N0008589 3 3...
Page 640: ...640 Using the Network Update Wizard N0008589 3 3...
Page 666: ...666 Importing and Exporting DHCP data N0008589 3 3...
Page 722: ...722 Restarting the router N0008589 3 3...
Page 726: ...726 Important Web Cache considerations N0008589 3 3...
Page 748: ...748 Configuring an Interface with NAT N0008589 3 3...
Page 794: ...794 IPSec N0008589 3 3...
Page 818: ...818 Configuring the Policy Agent characteristics N0008589 3 3...
Page 832: ...832 Firewall rules for Business Communications Manager with Dialup interfaces N0008589 3 3...
Page 876: ...876 ISDN Programming N0008589 3 3...
Page 1004: ...1004 Index N0008589 3 3...