73
Controlling user access to the device
Use ACLs to prevent unauthorized access, and configure command authorization and accounting to
monitor and control user behavior. For more information about ACLs, see
ACL and QoS
Configuration Guide.
FIPS compliance
The device supports the FIPS mode that complies with NIST FIPS 140-2 requirements. Support for
features, commands, and parameters might differ in FIPS mode and non-FIPS mode. For more
information about FIPS mode, see
Security Configuration Guide
.
Telnet and HTTP are not supported in FIPS mode.
Controlling Telnet and SSH logins
Use different types of ACLs to filter Telnet and SSH logins by different match criteria:
•
Basic ACL (2000 to 2999)
—Source IP address.
•
Advanced ACL (3000 to 3999)
—Source IP address and destination IP address.
•
Ethernet frame header ACL (4000 to 4999)
—Source MAC address.
If an applied ACL does not exist or does not have any rules, no user login restriction is applied. If the
ACL exists and has rules, only users permitted by the ACL can access the device through Telnet or
SSH.
Configuration procedures
To control Telnet logins:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Apply an ACL to filter
Telnet logins.
•
telnet server acl
[
mac
]
acl-number
•
telnet server ipv6 acl
{
ipv6
|
mac
}
acl-number
By default, no ACL is used to filter
Telnet logins.
3.
(Optional.) Enable
logging for Telnet login
attempts that are
denied by the Telnet
login control ACL.
telnet server acl-deny-log enable
By default, logging is disabled for
Telnet login attempts that are
denied by the Telnet login control
ACL.
To control SSH logins:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Apply an ACL to filter
SSH logins.
•
ssh server acl
[
mac
]
acl-number
•
ssh server ipv6 acl
{
ipv6
|
mac
}
acl-number
By default, no ACL is used to filter
SSH logins.
For more information about these
two commands, see
Security
Command Reference
.
Summary of Contents for FlexNetwork 10500 Series
Page 139: ...130 Sysname display version ...