User Guide: AMF Security version 2.6.1 for VST-APL

# Registering Actions

## What is Action

AMF Security has an authentication rule called Action. In addition to processing by Device Authentication Data and the UnAuth Group, this device individually isolates or blocks devices that meet specific conditions, or connects to a network different from the Device Authentication Data registration.
If you are using external security applications which are interacting with AMF Security, actions are automatically generated and executed when AMF Security receives instructions from those applications.
You can also manually create actions without using external applications.
In either case with OpenFlow, the Action takes precedence over the Device Authentication Data and the UnAuth Group.
With AW+ AMF Application Proxy, when the Action is registered, it is notified to the proxy node and processed by the proxy node and edge node side.
With TQ's AMF Application Proxy, the Action takes precedence over the Device Authentication Data and the UnAuth Group, similar to OpenFlow.
You can use the following data as conditions for an action.

- Device MAC Address
- Device IPv4 Address
- Device
- Device Tag
- Location
- OpenFlow Switch
- Connecting Network

If the conditions are met, the OpenFlow and TQ's AMF Application Proxy performs the specified OpenFlow/TQ Action: Pass(Permit), Quarantine, or Drop(Block) the device's connection. For permit and quarantine actions, you can also specify a VLAN ID to assign a matched device to.
AW+ AMF Application Proxy Blacklist notifies proxy nodes of AMF Actions.

- When a Device MAC Address is specified → The MAC Address is sent to the AMF Master
- When a Device IPv4 Address is specified → The IPv4 Address is sent to the AMF Master
- When a Device MAC Address and a Device IPv4 Address are specified → Only the IPv4 Address is sent to the AMF Master
- When a Device or a Device Tag is specified → The MAC Address associated with the device is sent to the AMF Master

To specify an AMF action "IP-Filter", a Device IPv4 Address must be specified.

## Manually Adding Action

Action can be registered on the Policy Settings > Add Action page.
A suspicious packet was sent from the device with MAC Address "00:00:5E:00:53:01" connected to the OpenFlow Switch "AT-TQ4400" that provides the guest network to the UnAuth Group. The following explains how to block the communication of this device. To add an action manually, follow those steps:

1. Open the Policy Settings > Action List page.
   This page lists registered actions in AMF Security. As you see, no action is registered at this point.
2. Click the "Add Action" button at the top right corner of the Policy Settings > Action List page to open Policy Settings > Add Action page.
3. Enter information for the action to add.
   As an example, configure the settings shown in the following table:

   Table 1: Sample Configuration Data
   Item Name | Value | Description
   --- | --- | ---
   Action ID (Mandatory) | Block suspicious device | ID (Name) of the action to register. Action ID must be unique. Max 255 characters
   Priority | 10 | Priority of the action. It must be an integer between 1 and 65535. Smaller number has higher priority. Thus the matching action with the smaller priority value is executed. Priority value is set to 10 if it is unspecified.
   Reason | Port Scan | Administrative comment such as a reason for running this action. Max 255 characters

4. Enter conditions to trigger the action.
   In this example, specify the suspicious device as Device MAC Address.

   Table 2: Sample Configuration Data / Conditions
   Item Name | Value | Description
   --- | --- | ---
   Device MAC Address | 00:00:5E:00:53:01 | Unicast MAC Address of the target device. Valid formats are as follows xx:xx:xx:xx:xx:xx, xx-xx-xx-xx-xx-xx, xxxx.xxxx.xxxx
   Device IPv4 Address | (empty) | Unicast IPv4 Address of the target device.
   Device | (empty) | Device ID of the target device. Maximum 100 device IDs are shown in the dropdown list. If you enter text in the field, device IDs in the dropdown list are dynamically filtered to the ones which contain the input text in Device ID, Tag or Note (it shows maximum 100 elements). From the dropdown list, select a Device ID for the device.
   Device Tag | (empty) | Device Tag of the target device.
   Location | (empty) | Location ID for the target device. Maximum 100 IDs of the existing locations are shown in the dropdown list. If you enter text in the field, location IDs in the dropdown list are dynamically filtered to the ones which contain the input text in Location ID or Note (it shows maximum 100 elements). From the dropdown list, select a Location ID.
   OpenFlow Switch | (empty) | Switch ID for the target device. Maximum 100 IDs of the existing switches are shown in the dropdown list. If you enter text in the field, switch IDs in the dropdown list are dynamically filtered to the ones which contain the input text in Switch ID, Datapath ID, Upstream Port or Note (it shows maximum 100 elements). From the dropdown list, select a Switch ID.
   Connecting Network | (empty) | Network ID for the target device. Maximum 100 IDs of the existing networks are shown in the dropdown list. If you enter text in the field, Network IDs in the dropdown list are dynamically filtered to the ones which contain the input text in Network ID, VLAN ID or Note (it shows maximum 100 elements). From the dropdown list, select a Network ID.

5. Enter the action to perform when a device met the conditions.
   In this example, the communication from the device is discarded, so it is not necessary to specify the Pass/Quarantine VLAN ID.
   Also, leave the AMF Action as default ("AMF Dependency") because the AMF Application Proxy is not used in this example.

   Table 3: Sample Configuration Data / Action
   Item Name | Value | Description
   --- | --- | ---
   OpenFlow/TQ Action | Drop(Block) | An action of the OpenFlow/TQ's AMF Application Proxy to be applied to the target device. ・Pass(Permit): Permit traffic from the device. ・Quarantine: Move the device to the quarantine network. ・Drop(Block): Block traffic from the device. ・Log-Only: AMF Security does not notify you of the action and does not control the communication of the device. Output only the log of the applicable device. ・Redirect-URL: Apply Redirect-URL Action to the device to connect to the quarantine network. This action is only supported by TQ's AMF Application Proxy, not supported by OpenFlow.
   Pass/Quarantine VLAN ID | (empty) | A VLAN ID on which the device is allowed to transmit packets.
   AMF Action | AMF Dependency | Contents of the action when instructing the communication interruption of the corresponding device using AW+ AMF Application Proxy. ・AMF Dependency: AMF Security does not specify an action and lets AMF devices determine its action. ・Quarantine: Move the device to the quarantine VLAN. ・Drop Packets: Block traffics from the device at the layer two (MAC) level. ・Link-Down: Shutdown the port where the device is connected. ・IP-Filter: Block traffics from the device at the layer 3 (IP) level. ・Log-Only: AMF Security notifies the action of the log, but only outputs the log without controlling the communication of the corresponding device.

   > Note

   > > The behavior of the "Quarantine" action depends on the firmware version of your AlliedWare Plus device (Edge Nodes).
   > > ・Version 5.5.0-2.x or later when using multiple dynamic VLANs with port authentication (including AMF Application Proxy Whitelist) and AMF Application Proxy Blacklist: Move only the MAC Address of the affected device to the quarantine VLAN
   > > ・Otherwise: Move the port to which the affected device is connected to the quarantine VLAN

   > Note

   > > Prior to version 5.5.0-2.x, dynamic VLANs cannot be used when using quarantine action and port authentication (including AMF Application Proxy Whitelist) on the same port.

6. Click the "Submit" button.
   Once the action was added, the Policy Settings > Action List page reflects the added information.

Configuration is complete.
After the action is activated, all traffic from the MAC Address is dropped unless you delete the action or you add an action with higher priority (smaller priority value) to permit the MAC Address.

01 Oct 2025 12:50