
An incident is created when a particular zone service is under a DDoS attack. An incident helps to track and manage the mitigation of an attack on a zone service. If a protected zone has more than one service that is simultaneously under attack, A10 Defend Orchestrator App creates multiple incidents, one for each service in the zone under attack.
A zone incident captures information such as start and end time of the attack, attack type, total attack bandwidth, and peak attack rate.
A zone service incident can be created manually through GUI or REST API, or automatically through GUI when it receives an attack detected notification from the A10 detector (in the case of reactive deployment) or the TPS mitigator (if it's deployed in a proactive mode).
In case of proactive deployment, the inbound traffic continuously flows through the mitigator, TPS automatically starts mitigation when it detects an attack. In case of reactive deployment, A10 Defend Orchestrator App configures TPS mitigator to advertise BGP routes and redirects the traffic to the attacked service through TPS.
For a reactive mode deployment, after the incident creation, a user can enable or disable automatic start and stop mitigation for a zone. Using A10 Defend Orchestrator App, this option can be set globally under Administration > Settings or at a per zone level through the Zone Operational Policy associated with that zone.
If the automatic start and stop mitigation is enabled, A10 Defend Orchestrator App starts mitigation for a zone after the incident is created for any service. If there are attacks on multiple services, A10 Defend Orchestrator App stops mitigation after the attack stops on the last of the attacked services.
| NOTE: | Incidents are for A10 Defend Orchestrator App TPS local incidents and are not associated to incidents on ACOS TPS devices. |
Perform the following steps to access the TPS Incidents page:
Navigate to Incidents > DDoS Incidents from the main menu.
|
Field |
Purpose |
|---|---|
|
Search By |
Select one of the following zone incidents to filter the incidents:
|
|
Search Incident or Zone |
Enter a string (from the list of TPS Incidents). |
|
Filters by Time Frame |
Enter the start and end date and time. All incidents that match the Status selected for this period will be listed.
|
|
Filter By Status |
Select one of the following statuses:
|
(Optional) The following buttons appear across the upper-right side of the TPS Incidents table:
|
Options |
Purpose |
|---|---|
|
Add |
Click the button to add a new Incident, see Create a New DDoS Incident (Zone) for further information. |
|
Refresh |
Select the option to refresh the information displayed for the TPS Incidents. |
|
Bulk Actions |
Under Bulk Actions, you can take actions on all incidents in one go. To delete, hover over Bulk Actions and select Delete or download the summary of all incidents by selecting Incident Summary Report. |
|
Column heading |
Description |
|
Status |
Displays the status of the incident being mitigated. Status may be New, Ongoing, or Stopped. |
|
Incident Name |
Displays the name of the incident. Click on Incident Name to move to Mitigation Console page with selected Incident. |
|
Zone Name |
Displays the name of the zone. |
|
Service |
Displays the service provided for the incident. |
|
Attack Type |
Displays the type of attack assessed by TPS. |
| Incident Time |
Displays the time when the incident happened. The time stamp is as follows:
|
|
Peak |
Displays the peak attack rate in packets per second (PPS) and bytes per second (BPS). |
|
Total |
Displays the total number of packets and bytes passed and dropped. |
|
Chart (PPS) |
Displays the graphical representation of traffic related to the incident, plotted over time. Passed packets are shown in green and dropped packets are shown in red. |
|
Actions |
Click to view the following actions:
|