AMX NXA-ENET8-POE+, Instruction Manual, Page: 134 / 283

Security Measures
134
Instruction Manual - NXA-ENET8-POE+
Security Measures
You can configure this switch to authenticate users logging into the system for management access using local or remote
authentication methods. Port-based authentication using IEEE 802.1x can also be configured to control either management
access to the uplink ports or client access to the data ports. This switch provides secure network management access using the
following options:

AAA - Use local or remote authentication to configure access rights, specify authentication servers, configure remote
authentication and accounting.

User Accounts - Manually configure access rights on the switch for specified users.

Network Access - Configure MAC authentication, intrusion response, dynamic VLAN assignment, and dynamic QoS
assignment.

HTTPS - Provide a secure web connection.

SSH - Provide a secure shell (for secure Telnet access).

ACL - Access Control Lists provide packet filtering for IP frames (based on address, protocol, Layer 4 protocol port number
or TCP control code).

ARP Inspection - Security feature that validates the MAC Address bindings for Address Resolution Protocol packets.
Provides protection against ARP traffic with invalid MAC to IP Address bindings, which forms the basis for certain "man-in-
the-middle" attacks.

IP Filter - Filters management access to the web, SNMP or Telnet interface.

Port Security - Configure secure addresses for individual ports.

Port Authentication - Use IEEE 802.1x port authentication to control access to specific ports.

DHCP Snooping - Filter IP traffic on insecure ports for which the source address cannot be identified via DHCP snooping.

DoS Protection - Protects against Denial-of-Service attacks.

IPv4 Source Guard - Filters IPv4 traffic on insecure ports for which the source address cannot be identified via DHCPv4
snooping nor static source bindings.
NOTE: The priority of execution for the filtering commands is Port Security, Port Authentication, Network Access, Web
Authentication, Access Control Lists, IP Source Guard, and then DHCP Snooping.
AAA (Authentication, Authorization, and Accounting)
The authentication, authorization, and accounting (AAA) feature provides the main framework for configuring access control on
the switch. The three security functions can be summarized as follows:

Authentication - Identifies users that request access to the network.

Authorization - Determines if users can access specific services.

Accounting - Provides reports, auditing, and billing for services that users have accessed on the network.
The AAA functions require the use of configured RADIUS or servers in the network. The security servers can be defined
as sequential groups that are applied as a method for controlling user access to specified services. For example, when the switch
attempts to authenticate a user, a request is sent to the first server in the defined group, if there is no response the second server
will be tried, and so on. If at any point a pass or fail is returned, the process stops.
The switch supports the following AAA features:

Accounting for IEEE 802.1x authenticated users that access the network through the switch.

Accounting for users that access management interfaces on the switch through the console and Telnet.

Accounting for commands that users enter at specific CLI privilege levels.

Authorization of users that access management interfaces on the switch through the console and Telnet.
To configure AAA on the switch, you need to follow this general process:
1.
Configure RADIUS and server access parameters. See the Configuring Local/ Remote Logon Authentication section
on page 135 for more information.
2. Define RADIUS and server groups to support the accounting and authorization of services.
3. Define a method name for each service to which you want to apply accounting or authorization and specify the RADIUS or
server groups to use.
4. Apply the method names to port or line interfaces.
NOTE: This guide assumes that RADIUS and servers have already been configured to support AAA. The configuration of
RADIUS and server software is beyond the scope of this guide, refer to the documentation provided with the RADIUS or
server software.