Cisco Systems OL-5742-01 User Manual

CHA PT ER

Configuring SGM Security

This chapter provides the following information about configuring SGM security
and limiting access to SGM:

• Configuring SGM User-Based Access, page 18-1

• Implementing SSL Support in SGM, page 18-26

• Limiting SGM Client Access to the SGM Server (Solaris Only), page 18-40

Configuring SGM User-Based Access

SGM enables you to control who is allowed to do what in SGM, beyond simply
specifying root and non-root users. SGM calls this ability User-Based Access.

User-Based Access provides multi-level password-protected access to SGM
features. Each user can have a unique user name and password. Each user can also
be assigned to one of five levels of access, which control the list of SGM features
accessible by that user.

18

OL-5742-01

To configure SGM User-Based Access, perform the tasks in the following
sections. Required and optional tasks are indicated.

• Implementing SGM User-Based Access (Solaris Only), page 18-2 (Required)

• Creating Secure Passwords, page 18-5 (Required)

• Configuring SGM User Authentication Levels (Solaris Only), page 18-6

(Required)

• Automatically Disabling Users and Passwords (Solaris Only), page 18-10

(Optional)

Cisco Signaling Gateway Manager User Guide

18-1

Chapter 18 Configuring SGM Security

Configuring SGM User-Based Access

• Manually Disabling Users and Passwords (Solaris Only), page 18-14

(Optional)

• Enabling and Changing Users and Passwords (Solaris Only), page 18-16

(Optional)

• Displaying a Message of the Day, page 18-18 (Optional)

• Manually Synchronizing Local SGM Passwords, page 18-21 (Optional)

• Listing All Currently Defined Users, page 18-21 (Optional)

• Displaying the Contents of the System Security Log, page 18-22 (Optional)

• Restoring Security-Related SGM Data, page 18-23 (Optional)

• Disabling SGM User-Bases Access, page 18-24 (Optional)

• Specifying a Super User (Solaris Only), page 18-24 (Optional)

Implementing SGM User-Based Access (Solaris Only)

Before you can access SGM’s full suite of security commands, you must enable
SGM User-Based Access, configure the type of security authentication you want
to use, and begin adding users to your authentication lists.

To implement SGM User-Based Access, use the following procedure:

18-2

Step 1 Log in as the root user, as described in the “Becoming the Root User (Solaris

Only)” section on page 2-3, or as a super user, as described in the “Specifying a
Super User (Solaris Only)” section on page 18-24.

Step 2 Enter the following commands:

# cd /opt/CSCOsgm/bin

# ./sgm useraccess enable

SGM User-Based Access is enabled the next time you restart the SGM server.

Cisco Signaling Gateway Manager User Guide

OL-5742-01

Chapter 18 Configuring SGM Security

Step 3 If you have already configured the type of SGM security authentication you want

to use, skip to Step 4.

Otherwise, configure the type of SGM security authentication you want to use:

• Local authentication allows you to create user accounts and passwords local

to the SGM system. When using this method, you can use SGM User-Based
Access commands manage user names, passwords, and access levels.

To enable local authentication, enter the following command:

# ./sgm authtype local

• Solaris authentication uses standard Solaris-based user accounts and

passwords, as specified in the /etc/nsswitch.conf file. Authentication can be
provided by the local /etc/passwd file or from a distributed Network
Information Services (NIS) system. You can use all SGM User-Based Access
commands except the following commands:

–

sgm disablepass

–

sgm passwordage

–

sgm userpass

Configuring SGM User-Based Access

OL-5742-01

You must use Solaris commands, such as passwd, to manage passwords.

Users also cannot change their passwords using the SGM client. Instead, they
must manage their passwords on the external authentication servers, using
Solaris commands, such as passwd.

All new passwords take effect the next time SGM automatically synchronizes
local SGM passwords with Solaris, or you can manually synchronize
passwords at any time using the sgm syncusers command.

In addition, if you have enabled Solaris authentication, you must be logged in
as the root user, not a super user, to use the following SGM commands:

–

sgm adduser

–

sgm disableuser

–

sgm enableuser

–

sgm updateuser

Cisco Signaling Gateway Manager User Guide

18-3

Configuring SGM User-Based Access

To enable Solaris authentication, enter the following command:

# ./sgm authtype solaris

See the “SGM Command Reference” section on page C-1 for more
information on the use of each of the above SGM commands.

Step 4 To add a user to your SGM User-Based Access authentication list, use the

following command:

# ./sgm sgm adduser username

where username is the name of the user.

Note If sgm authtype is set to solaris, you must be logged in as the root user, not as a

super user, to enter this command.

SGM also prompts you for the authentication level for the user. Valid levels are:

• 1—Basic User

• 2—Power User

Chapter 18 Configuring SGM Security

18-4

• 3—Network Operator

• 4—Network Administrator

• 5—System Administrator

For more information about authentication levels, see the “Configuring SGM User

Authentication Levels (Solaris Only)” section on page 18-6.

If sgm authtype is set to local, SGM also issues the following prompts:

• SGM prompts you for the user’s password. When setting the password, follow

the rules and considerations in the “Creating Secure Passwords” section on

page 18-5.

• SGM asks whether you want to force the user to change the password at the

next login. The default is not to force the user to change the password.

(Whenever a user needs to change a password, SGM issues an appropriate
message and prompts for the user name and new password.)

Cisco Signaling Gateway Manager User Guide

OL-5742-01

Chapter 18 Configuring SGM Security

Note If sgm authtype is set to solaris, users cannot change their passwords

using the SGM client. Instead, they must manage their passwords on the
external authentication servers, using Solaris commands, such as passwd.
All new passwords take effect the next time SGM automatically
synchronizes local SGM passwords with Solaris, or you can manually
synchronize passwords at any time using the sgm syncusers command.
See the “sgm syncusers” section on page C-118 for more information.

At this point, you have implemented your basic SGM User-Based Access. Users
must now log in before using the SGM client, the GTT client, and SGM
Web-based functions. Use the remaining procedures in this section to customize
your SGM security system.

Note After you implement SGM User-Based Access, if a user logs in on one SGM or

GTT client, then logs in on a second SGM or GTT client, SGM closes the first
client and records the event in the system security log.

Configuring SGM User-Based Access

Creating Secure Passwords

When setting passwords in SGM, keep in mind the following rules and
considerations:

• The password must be at least 6 characters, up to an unlimited number of

characters. However, passwords longer than 15 characters are not
recommended.

• The password cannot be identical to the user name.

• The new password cannot be the same as the old password.

• SGM does not allow users to switch back-and-forth between two passwords.

OL-5742-01

Cisco Signaling Gateway Manager User Guide

18-5

Chapter 18 Configuring SGM Security

Configuring SGM User-Based Access

• The password cannot be a common word. SGM uses the dictionary located at

/usr/lib/share/dict/words to determine whether a word is common. To
override the SGM dictionary, change the DICT_FILE entry in the
System.properties file:

–

To disable the SGM dictionary and allow common words, change the
DICT_FILE entry to:

DICT_FILE=/dev/null

–

To use a custom dictionary, change the DICT_FILE entry to:

DICT_FILE=/new-dictionary

where new-dictionary is the path and filename of the custom dictionary
file, such as /users/rolive/words. Each line in the custom dictionary must
contain a single word, with no leading or trailing spaces.

Configuring SGM User Authentication Levels (Solaris Only)

18-6

This section describes the user authentication levels in SGM, and the SGM
functions and Web displays available at each level:

• Basic User (Level 1) Access, page 18-7

• Power User (Level 2) Access, page 18-8

• Network Operator (Level 3) Access, page 18-8

• Network Administrator (Level 4) Access, page 18-9

• System Administrator (Level 5) Access, page 18-9

The authentication level that includes a function is the lowest level with access to
that function. The function is also available to all higher authentication levels. For
example, a System Administrator also has access to all Network Administrator
functions.

Authentication levels are based on the function to be performed, not on the target
object. Therefore, if a user can perform a function on one SGM object (such as
deleting a node), the user can perform the same function on all similar SGM
objects (such as deleting a signaling point or linkset).

Cisco Signaling Gateway Manager User Guide

OL-5742-01

Chapter 18 Configuring SGM Security

Note Access to SGM information and downloads on Cisco.com is already protected by

Cisco.com, and is not protected by SGM.

To configure the authentication level for a user, use the sgm adduser command,
as described in the “Implementing SGM User-Based Access (Solaris Only)”

section on page 18-2, or the sgm updateuser or sgm newlevel command, as

described in the “Enabling and Changing Users and Passwords (Solaris Only)”

section on page 18-16.

Basic User (Level 1) Access

Basic Users can view SGM data, load SGM files, and use SGM drill-down menus.

Basic Users have access to the following SGM functions:

• Connecting to a new server

• Applying changes to views

• Loading the DEFAULT view and existing views, but not saving them

• Editing, loading, and applying preferences files, but not saving them

Configuring SGM User-Based Access

OL-5742-01

• Viewing and manipulating the topology map, and saving it as a JPEG, but not

saving icon locations

• Viewing network objects, events, details, and notes

• Viewing the ITP home page

• Loading existing event filters, but not saving them

• Printing SGM windows

• Launching CiscoWorks2000

Basic Users have access to the following SGM Web displays:

• Server Home Page

• System README

• Network Status

Cisco Signaling Gateway Manager User Guide

18-7

Configuring SGM User-Based Access

• System Data Files

–

Notes

–

Views

–

Preferences

• Viewing SGM documentation

• Downloading client software

Power User (Level 2) Access

Power Users have access to all Basic User functions.

Power Users can change some aspects of the way SGM works.

Power Users have access to the following SGM functions:

• Editing network objects, events, and views

• Unignoring network objects and views

• Saving preferences files, event filters, and views

• Acknowledging events

• Viewing ITP real-time data and charts

Chapter 18 Configuring SGM Security

• Viewing the event configuration, but not editing it

Power Users have access to the following SGM Web displays:

• System Status, excluding User Accounts and System Troubleshooting

• Accounting Statistics Reports

• Network Statistics Reports

Network Operator (Level 3) Access

Network Operators have access to all Basic User and Power User functions.

Network Operators can make changes to SGM network files.

Network Operators have access to the following SGM functions:

• Ignoring network objects and views

• Polling nodes

Cisco Signaling Gateway Manager User Guide

18-8

OL-5742-01

Chapter 18 Configuring SGM Security

• Telnetting to the ITP

• Viewing route table files and GTT files, but not editing them

Network Operators have access to the following SGM Web displays:

• Point Code Inventories

• System Data Files

–

Route table files

–

Global Title Translation (GTT) table files

–

System ITP IOS README

Network Administrator (Level 4) Access

Network Administrators have access to all Basic User, Power User, and Network
Operator functions.

Network Administrators have access to all SGM client functions.

Network Administrators have access to the following SGM functions:

Configuring SGM User-Based Access

• SNMP configuration

• Network Discovery

• Deleting network objects

• Managing and unmanaging nodes

• Editing and saving route table files and GTT files

• Using the Deployment Wizard

Network Administrators have access to the following SGM Web displays:

• System Data Files: Discovery Seeds

System Administrator (Level 5) Access

System Administrators have access to all Basic User, Power User, Network
Operator, and Network Administrator functions.

System Administrators have access to all functions in SGM.

OL-5742-01

Cisco Signaling Gateway Manager User Guide

18-9

Configuring SGM User-Based Access

System Administrators have access to the following SGM Web displays:

• System Messages and Logs

• System Status, including User Accounts and System Troubleshooting

• Trap Host Configuration, including SNMP configuration information

• System Information

–

–

–

–

–

–

–

–

–

Chapter 18 Configuring SGM Security

System Command Log

System Console Log

System Event Automation Log

System Install Log

System Process Services

System Properties

System Report Parameters and Timers Page

System Reports Log

System Root Variables

–

System Security Log

–

System Web Access Log

–

System Web Error Log

Automatically Disabling Users and Passwords (Solaris Only)

After you have implemented the basic SGM User-Based Access security system,
you can customize the system to automatically disable users and passwords when
certain conditions are met.

To automatically disable users and passwords, use the following procedures:

Step 1 Log in as the root user, as described in the “Becoming the Root User (Solaris

Only)” section on page 2-3, or as a super user, as described in the “Specifying a
Super User (Solaris Only)” section on page 18-24.

Cisco Signaling Gateway Manager User Guide

18-10

OL-5742-01

Chapter 18 Configuring SGM Security

Step 2 Enter the following command:

# cd /opt/CSCOsgm/bin

Step 3 (Optional) You can configure SGM to generate an alarm after a specified number

of unsuccessful login attempts by a user. To do so, enter the following command:

# ./sgm badloginalarm number-of-attempts

where number-of-attempts is the number of unsuccessful login attempts allowed
before SGM generates an alarm.

The valid range is 1 unsuccessful attempt to an unlimited number of unsuccessful
attempts. The default value is 5 unsuccessful attempts.

To disable this function (that is, to prevent SGM from automatically generating
an alarm after unsuccessful login attempts), enter the following command:

# ./sgm badloginalarm clear

Step 4 (Optional) You can configure SGM to disable a user’s security authentication

automatically after a specified number of unsuccessful login attempts. To do so,
enter the following command:

Configuring SGM User-Based Access

OL-5742-01

# ./sgm badlogindisable number-of-attempts

where number-of-attempts is the number of unsuccessful login attempts allowed
before SGM disables the user’s authentication. SGM does not delete the user from
the authentication list, SGM only disables the user’s authentication.

The valid range is 1 unsuccessful attempt to an unlimited number of unsuccessful
attempts. The default value is 10 unsuccessful attempts.

To re-enable the user’s authentication, use the sgm enableuser command.

To disable this function (that is, to prevent SGM from automatically disabling a
user’s authentication after unsuccessful login attempts), enter the following
command:

# ./sgm badlogindisable clear

Cisco Signaling Gateway Manager User Guide

18-11

Configuring SGM User-Based Access

Step 5 (Optional) SGM keeps track of the date and time each user last logged in. You can

configure SGM to disable a user’s security authentication automatically after a
specified number of days of inactivity. To do so, enter the following command:

# ./sgm inactiveuserdays number-of-days

where number-of-days is the number of days a user can be inactive before SGM
disables the user’s authentication. SGM does not delete the user from the
authentication list, SGM only disables the user’s authentication.

The valid range is 1 day to an unlimited number of days. There is no default
setting.

To re-enable the user’s authentication, use the sgm enableuser command.

This function is disabled by default. If you do not specify the
sgm inactiveuserdays command, user accounts are never disabled as a result of
inactivity.

If you have enabled this function and you want to disable it (that is, to prevent
SGM from automatically disabling user accounts as a result of inactivity), enter
the following command:

Chapter 18 Configuring SGM Security

18-12

# ./sgm inactiveuserdays clear

Step 6 (Optional) If sgm authtype is set to local, you can configure SGM to force users

to change their passwords after a specified number of days.

To configure SGM to force users to change their passwords after a specified
number of days, enter the following command:

#./sgm passwordage number-of-days

where number-of-days is the number of days allowed before users must change
their passwords.

The valid range is 1 day to an unlimited number of days. There is no default
setting.

This function is disabled by default. If you do not specify the sgm passwordage
command, users never need to change their passwords.

Cisco Signaling Gateway Manager User Guide

OL-5742-01

Chapter 18 Configuring SGM Security

If you have enabled this function and you want to disable it (that is, prevent SGM
from forcing users to change passwords), enter the following command:

# ./sgm passwordage clear

Note If sgm authtype is set to solaris, you cannot use the sgm passwordage

command. Instead, you must manage passwords on the external
authentication servers.

Step 7 (Optional) You can configure SGM to disconnect an SGM or GTT client

automatically after a specified number of minutes of inactivity. To do so, enter the
following command:

# ./sgm clitimeout number-of-minutes

where number-of-minutes is the number of minutes an SGM or GTT client can be
inactive before SGM disconnects the client.

The valid range is 1 minute to an unlimited number of minutes. There is no default
value.

Configuring SGM User-Based Access

OL-5742-01

This function is disabled by default. If you do not specify the sgm clitimeout
command, clients are never disconnected as a result of inactivity.

If you have enabled this function and you want to disable it (that is, never
disconnect a client as a result of inactivity), enter the following command:

# ./sgm clitimeout clear

Cisco Signaling Gateway Manager User Guide

18-13