Summary of Local Attack Defense Configuration Tasks

Table 1 lists the tasks for configuring local attack defense.

**Table 1** Local attack defense configuration tasks
Scenario	Tasks
Configuring CPU Attack Defense	When configuring CPU attack defense, create an attack defense policy first. The other tasks can be performed in any sequence and can be selected as required. An attack defense policy takes effect only after it is applied to an object. There is no limitation on when the attack defense policy is applied. Creating an Attack Defense Policy Configuring a Blacklist Configuring a User-Defined Flow Configuring a Rule for Sending Packets to the CPU Configuring Dynamic CPCAR Adjustment for Protocol Packets Configuring Adaptive CPCAR Adjustment for Protocol Packets Enabling Alarm Reporting for Packet Loss Caused by CPCAR Exceeding Specifying Interface Types for Protocol Packets Applying an Attack Defense Policy
Configuring Attack Source Tracing	When configuring attack source tracing, create an attack defense policy first and enable the attack source tracing function (enabled by default). The other tasks can be performed in any sequence and can be selected as required. An attack defense policy takes effect only after it is applied to an object. There is no limitation on when the attack defense policy is applied. Creating an Attack Defense Policy Enabling Attack Source Tracing Configuring the Threshold for Attack Source Tracing Setting the Packet Sampling Ratio for Attack Source Tracing Configuring an Attack Source Tracing Mode Configuring the Types of Traced Packets Configuring a Whitelist for Attack Source Tracing Configuring Event Reporting Function Configuring Attack Source Punish Actions Applying an Attack Defense Policy
Configuring Port Attack Defense	When configuring port attack defense, create an attack defense policy first and enable the port attack defense function (enabled by default). The other tasks can be performed in any sequence and can be selected as required. An attack defense policy takes effect only after it is applied to an object. There is no limitation on when the attack defense policy is applied. Creating an Attack Defense Policy Enabling Port Attack Defense Specifying the Protocols to Which Port Attack Defense Is Applied Setting the Rate Threshold for Port Attack Defense Setting the Sampling Ratio for Port Attack Defense Setting the Aging Time for Port Attack Defense Configuring the Whitelist for Port Attack Defense Configuring the Report of Port Attack Defense Events Applying an Attack Defense Policy
Configuring the User-Level Rate Limiting NOTE: Only S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S6720-HI, S6730-H, S6730S-H, S6730-S, and S6730S-S support this function. You are advised to disable user-level rate limiting on the network-side interfaces of access switches and gateway switches.	When configuring user-level rate limiting, enable the user-level rate limiting function first (enabled globally by default). The other tasks can be performed in any sequence and can be selected as required. By default, user-level rate limiting is enabled on interfaces. You can disable it on the interfaces where this function is not required. Enabling the User-Level Rate Limiting Configuring the User-Level Rate Limit Specifying the Packet Types to Which the User-Level Rate Limiting Applies Disabling User-Level Rate Limiting on an Interface