Contents

What is AMF Security

Quick Tour > What is AMF Security

---

---

Where does AMF Security Fit In

AMF-SECurity (AMF-SEC) is our solution to streamline network operations and enhance security in office environments.
AMF Security is the SDN controller that is the core of the solution, and it realizes the cooperation between our products supporting the AMF (Allied Telesis Management Framework) and various business security related applications.

What does AMF Security Manage (OpenFlow)

AMF Security can centrally control the network access from various devices by installing packet control flows for the devices' MAC address on the OpenFlow Switches it manages.

AMF Security controls network traffic by using the OpenFlow protocol over the TCP connections established with the switches.

For each device, administrators can define two conditions on AMF Security, where and when the device can access the network. The first one is called "Location" and the other is called "Schedule".
Condition can be more granular like "From this OpenFlow Switch in that location" or "on this particular switchport of the switch in that location".
If a device meets those conditions, it is allowed to join the logical network defined by a VLAN ID.

• Location
  Where a device can access the network.
  By associating OpenFlow Switches with a location, you can define a physical network space.
  
  
• Schedule
  When a device can access the network.
  You can specify a period of time with a Start Date / Time and End Date / Time.
  
  
• OpenFlow Switch
  OpenFlow Switches from which a device can access the network.
  You can allow a device to access the network only when it connects to a specific OpenFlow Switch.
  
  
• Switch Port
  A port on an OpenFlow Switch from which a device can access the network.
  You can allow a device to access the network only when it connects to a specific port on a particular Switch.
  
  
• Network
  A VLAN subnet to which a device can belong (a logical network space defined by a VLAN ID).
  

The MAC address interface of the device is managed by connecting, blocking, and isolating based on the security policy assigned to the device.
A device can have more than one MAC address interface.
Assuming that a device has two MAC addresses - one for a wireless interface and the other for a wired interface, both of them can access the same network if they meet the conditions for Location and Schedule.

Table 1: Configurable Security Policies (OpenFlow)

Device Information
Device	network-capable equipment which connects to an OpenFlow Switch
└	MAC Address	a MAC address of the device interface
	:	(multiple items can be defined)
└	Security Policies	Network			a VLAN segment (VLAN ID) to which a device is assigned.
		Location			a physical location where a device can access the network.
		└	OpenFlow Switch		a switch in the location.
			└	Switch Port	a port on the switch from which a device can access the network.
			:		(multiple items can be defined)
		Schedule			a range of time during a device can access the network (Start Date / Time, and End Date / Time).
		(multiple items can be defined)

OpenFlow Switches have two types of network ports: control plane ports and data plane ports. The former is used for communicating with OpenFlow controllers while the latter is used for delivering user traffic and controlled by OpenFlow protocol.
In AMF Security, data plane ports are further categorized into "upstream port" and "client port".

• Upstream Port
  A port connected to an uplink network. An OpenFlow Switch can have only one upstream port.
  
  
• Client Port
  All ports other than the upstream port. User devices are connected to the client ports.
  

AMF Security is designed to manage user devices which are connected to client ports of OpenFlow Switches, assuming that the upstream ports are protected by other security measures such as firewalls.
By default, a switch port with the lowest OpenFlow port number is configured as the upstream port. This can be changed on each OpenFlow Switch.

What is AMF Application Proxy

The AMF Application Proxy controls traffic from edge devices, which are connected to AMF Members (Edge Nodes) where AMF Master (Proxy Node) authenticates the devices by querying AMF Security (AMF Application Proxy Whitelist).
It is also possible for AMF Security to notify the AMF Proxy Node of suspected node and make Edge Nodes to block the devices (AMF Application Proxy Blacklist).

Note

◼ AMF Application Proxy Whitelist and AMF Application Proxy Blacklist
・ A Proxy Node also can be an Edge Node (Only supported models).
・ Cannot be linked with AMF controller.

◼ AMF Application Proxy Whitelist
・ Use Virtual Chassis Stack (VCS) to provide redundancy to the AMF Master (Only supported models).
・ When linking with multiple local masters under AMF controller, make each local master a separate area.

To use the AMF Application Proxy, you have to configure all of AMF Security, Proxy Node and Edge Nodes.

What does AMF Security Manage (AMF Application Proxy Whitelist)

AMF Security can centrally control the network access from various devices by utilizing the port authentication feature on the AMF Members it manages.

The AMF Application Proxy Whitelist is an AMF Security's integration feature where AMF devices ask the AMF Security's whitelist server if a specific device can be allowed access to the network.
If a device meets those conditions, it is allowed to join the logical network defined by a VLAN ID.

• Location
  Where a device can access the network.
  By associating AMF Members with a location, you can define a physical network space.
  
  
• Schedule
  When a device can access the network.
  You can specify a period of time with a Start Date / Time and End Date / Time.
  
  
• Switch Port
  A port on an AMF Member from which a device can access the network.
  You can allow a device to access the network only when it connects to a specific port on a particular Switch.
  
  
• Network
  A VLAN subnet to which a device can belong (a logical network space defined by a VLAN ID).
  

The MAC address interface of the device is managed by connecting, blocking, and isolating based on the security policy assigned to the device.
A device can have more than one MAC address interface.
Assuming that a device has two MAC addresses - one for a wireless interface and the other for a wired interface, both of them can access the same network if they meet the conditions for Location and Schedule.

Table 2: Configurable Security Policies (AMF Application Proxy Whitelist)

Device Information
Device	network-capable equipment which connects to an AMF Member
└	MAC Address	a MAC address of the device interface
	:	(multiple items can be defined)
└	Security Policies	Network			a VLAN segment (VLAN ID) to which a device is assigned.
		Location			a physical location where a device can access the network.
		└	AMF Member		a switch in the location.
			└	Switch Port	a port on the switch from which a device can access the network.
			:		(multiple items can be defined)
		Schedule			a range of time during a device can access the network (Start Date / Time, and End Date / Time).
		(multiple items can be defined)

Note

To use this feature, your Proxy Node and Edge Nodes must have AlliedWare Plus firmware version 5.4.9-0.x or later installed.

Note

Authenticate with the AMF application proxy function displayed on the Device > Active Device List page with the following settings or operations. To display the displayed terminal information, your Proxy Node and Edge Nodes must have AlliedWare Plus firmware version 5.4.9-1.x or later installed. Also, enable the "service http" command on both the Proxy Node and the Edge Nodes.

・The check box of "Reload authorized device list when AMF member connects to network." on the AMF > AMF Application Proxy Settings page is checked.
・Click the "Sync" button on the Switches > Active AMF Member List page.

Blocking with AMF Application Proxy

Notifying Proxy Node of Suspected Node Information

AMF Security notifies the Proxy Node of suspected node when receiving information from security software or devices that detect suspected node, or adding an action on the Policy Settings > Add Action page. The suspected node's information is stored on AMF Security and can be viewed on the Policy Settings > Action List page.
AMF Security does not notify the proxy node of the information again.

Note

If the proxy node holding the suspected node information reboots, the information is removed from the proxy node.
Because the proxy node cannot receive the information from AMF Security again, the proxy node cannot relearn the suspected node automatically.
To manually tell the proxy node about the suspected node, follow the steps:
1. Open the Policy Settings > Action List page.
2. Click the "Export to CSV" button to save a CSV file.
3. Open the System Settings > System Information page.
5. Click the "Import" button for the Authentication Data item to open the "Upload Authentication Data" dialog.
5. Click the "Choose File" button, select the saved CSV file, and click the "Submit" button.

AMF Actions

When AMF Security notifies the Proxy Node of suspected nodes, it can also specify a blocking action (AMF action).
AMF Security can specify the following AMF actions:

• AMF Dependency
  
• Quarantine
  
• Drop Packets
  
• Link-Down
  
• IP-Filter
  
• Log-Only
  

When "Quarantine", "Drop Packets", "Link-Down", "IP-Filter", or "Log-Only" are set, these AMF actions are executed with priority over the AMF actions set on the edge node side.
When "AMF Dependency" is selected, AMF Security does not send the AMF action, but the AMF action set on the edge node side is executed.

Note

If AMF Security and AMF Master receive suspected node information from multiple sources (e.g. external applications), specify the same AMF action for all the sources.
The AMF Action for each application can be specified in the "Rules" section on the System Settings > Trap Monitor Settings page.
To change the AMF action for a suspected node which has already been registered on the Policy Settings > Action List page, delete the existing action and recreate it.

Note

If you also use the "Quarantine" action on the whitelist port, your Proxy Node and Edge Nodes must have AlliedWare Plus firmware version 5.5.0-2.x or later installed.

Note

Even if the device is permitted by the whitelist, if it is the target of AMF Action, the communication from the corresponding device is processed according to the action.

Unblocking Suspected Nodes

To unblock a suspected node (delete the suspected node information), delete the corresponding action on the Policy Settings > Action List page. When the action is deleted, AMF Security tells the proxy node to delete the suspected node information.

Note

You can also unblock the suspected node by running commands on the proxy node. But in this case, the proxy node does not request AMF Security to delete the node information. So AMF Security keeps the suspected node information. If you want to delete it, manually delete the action on the Policy Settings > Action List page.
Refer to the AlliedWare Plus Product's command reference manual for the commands.

Displaying and Emailing Blocking Status of the Suspected Node

Status of the suspected node which has been applied an AMF action by an edge node can be view on the Device > Active Device List page.
AMF Security regularly gets this information from the proxy node at 30 second interval.

Note

To use this feature, your Proxy Node and Edge Nodes must have AlliedWare Plus firmware version 5.4.8-1.x or later installed.

By using AMF Security's Email Notification Settings, you can also get email notifications of blocking.

• "Send Email Notification on Block Event" : An email is sent when a node is blocked by one of "Drop Packets", "Link-Down", "IP-Filter" or "Log-Only" actions.
  
• "Send Email Notification on Quarantine Event" : An email is sent when a node is quarantined by "Quarantine" action.
  

Note

When AMF Security queries the proxy node and finds that suspected node information is changed (e.g. a node moved to other switch and got blocked there again), AMF Security updates the information on the Device > Active Device List page and sends an email notification.

Configuring AMF Master (Proxy Node) and AMF Members (Edge Nodes)

Refer to the AlliedWare Plus Product's command reference manual for how to configure Proxy Node and Edge Nodes.
Depending on the AlliedWare Plus product model you use for a Proxy Node, you may have to install the proper license on the products.

Note

To view the blocking status of suspected nodes and use email notification, please run "atmf topology-gui enable" command on AMF Master (Proxy Node) in addition to the AMF Application Proxy's basic configurations.

Configuring AMF Security

To use AMF Application Proxy on AMF Security, you have to configure an IP address, level 15 (privileged) username and password of the AMF Master (Proxy Node) on AMF Security.

1. Open the AMF > AMF Application Proxy Settings page.
   
   
2. Click "Add".
   
   
3. Enter an IP address of the AMF Master (Proxy Node) in "IPv4 Address".
   
   
4. Enter a username and a password for a level 15 (privileged) user account on the AMF Master (Proxy Node).
   
   
5. Click "Submit".
   

Note

When you finish this configuration, AMF Security starts regular queries to the AMF Master (Proxy Node) at 30 second interval.

Refer to System Settings > Trap Monitor Settings for how to configure integration options with external applications.

Supported OpenFlow Switches

List of OpenFlow Switch models supported by AMF Security can be found on the release notes of AMF Security, switches and wireless access points.
Please find those documents on our website.
https://www.alliedtelesis.com

Application Integration Solutions

AMF Security can be used with other applications such as threat detection, device management and HR management in order to further enhance network administration efficiency and security.

The latest information on the services or applications which can be integrated into AMF Security system is published under the AMF-SEC Technology Partner Program. Contact our sales engineer for the Technology Partner Program.

---

(C) 2021 Allied Telesis, Inc. All rights reserved.

C613-04096-00 Rev B

14 Jun 2021 09:30