Configuring a Whitelist for Attack Source Tracing
Context
Attack source tracing locates attack sources and takes punish actions on the attack sources. If some users do not need to be traced regardless of whether they might initiate attacks, add the users to a whitelist.
Before referencing an ACL in a whitelist, create the ACL and configure rules.
To specify a protocol type in the ACL referenced by the whitelist, ensure that this protocol supports the attack source tracing function. You can run the display auto-defend configuration command to view the protocols supported by attack source tracing. If a protocol is not supported by attack source tracing, you can run the auto-defend protocol command to configure attack source tracing to support the protocol.
- The whitelist may fail to be applied because ACL resources are insufficient.
All the packets matching an ACL referenced by a whitelist are considered to be valid packets regardless of whether the ACL rule is permit or deny.
If an ACL has no rule, the whitelist that references the ACL does not take effect.
Procedure
- Run system-view
The system view is displayed.
- Run cpu-defend policy policy-name
The attack defense policy view is displayed.
- Run auto-defend whitelist whitelist-number { acl acl-number | interface interface-type interface-number }
A whitelist is configured.
By default, no whitelist is configured for attack source tracing. If any of the following conditions is met, however, the device uses the condition as the whitelist matching rule, regardless of whether attack source tracing is enabled. After attack source tracing is enabled, the device does not perform attack source tracing for the packets matching such rules.
- If an application uses the TCP protocol and has set up a TCP connection with the switch, the switch will not consider TCP packets with the matching source IP address as attack packets. If no TCP packets match a source IP address within 1 hour, the rule that specifies this source IP address will be aged out.
- If an interface has been configured as a DHCP trusted interface using the dhcp snooping trusted command, the device will not consider DHCP packets received from this interface as attack packets.
- If an interface has been configured as a MAC forced forwarding (MFF) network-side interface using the mac-forced-forwarding network-port command, the device will not consider ARP packets received from this interface as attack packets.
For the preceding conditions, the device supports a maximum of 16 whitelist matching rules based on source IP addresses and interfaces, and a maximum of 8 whitelist matching rules based on source IP addresses of TCP packets.