
GPW/AMK ©2005 Avaya Inc. All Rights Reserved. Avaya and the Avaya logo are trademarks of Avaya Inc. and
may be registered in certain jurisdictions. All trademarks identified by ® and ™ are registered
trademarks or trademarks respectively, of Avaya Inc. All other registered trademarks or trademarks
are property of their respective owners.
Avaya G250/G350
Media Gateway
Security Features
Overview
13
related to security, such as adding a new user accounts and setting the
device policy manager access source. An example of the source would be
issuing the no ip telnet command.
Username commands:
---------------------------------------------------------------------------
Usage: username <name> password <passwd> access-type {read-only|read-
write|admin}
•Does the ability exist to force a minimum length username and/or
password (other than default minimum of 4 characters username and 8
characters for password)? No. However, this can be accomplished by
using an external authentication database such as RADIUS.
•Does the configuration file include user account passwords or SNMP
Community Strings? The configuration file does not include SNMP
community strings and user/password data.
•Are there any “undocumented” usernames or SNMP community strings?
No. All "diag" accounts are in-accessible without first logging into
the G350 via a super-user account first. Backdoor password recovery
exists but can only be used via a direct connection to the console
port. It can also be disabled.
•Is there any way to enforce password aging on “local” accounts used
to administer the G350? No. However, this can be accomplished by
using an external authentication database such as RADIUS.
•Is there any way to enforce account "lock-out" after user inactivity
of that account – i.e. user has not logged in for 60 days? No.
However, this can be accomplished by using an external
authentication database such as RADIUS.
•Any way to enforce "lock-out" of accounts after excessive retries?
Yes in addition to a RADIUS external authentication which provides its
own set of options for lock-out, the following global command to set
login authentication lockout parameters for local administers.
G350-002<super>#login authentication lockout?
Login authentication lockout commands:
--------------------------------------------------------------------
Syntax : login authentication lockout <time> attempt <count?
<time> - integer <30..3600> seconds.
Interval of time account lockout is enforced.
0 –No timeout
<count> - integer <1..10>.
Successive number of failures before lockout
0- NO timeout
Example: login authentication lockout 360 attempt 5
The login authentication command supports the ability to enable local craft
user from services and a password
•Any way for the G350 to prevent simple/dictionary words from being
chosen as passwords? No. However, this can be accomplished by using
an external authentication database such as RADIUS.