This topic describes the attack source tracing feature of Security Center. This feature automatically traces the sources of attacks and provides original data previews.
The attack source tracing feature processes, aggregates, and visualizes logs from various Alibaba Cloud services by using a big data analytics engine. Then, the feature generates an event chain diagram of intrusions based on the analysis result. This way, you can identify the cause of intrusions and make informed decisions at the earliest opportunity. You can use this feature in scenarios that require urgent response and source tracing, such as web intrusions, worm events, ransomware, and unauthorized communications to suspicious sources in the cloud.
Security Center generates a chain of automated attack source tracing 10 minutes after a threat is detected. We recommend that you view the attack source tracing information 10 minutes after an alert is generated.
This feature can trace the sources of all types of alerts. For more information, see Alert types.
Only Security Center Enterprise supports the automatic attack source tracing feature. If you use the Basic, Basic Anti-Virus, or Advanced edition of Security Center, you must upgrade Security Center to the Enterprise edition before you can use this feature.
- Attack source tracing is implemented based on the big data analytics engine. If attacks do not form an attack chain, the attack source tracing information may not be displayed. In this case, you can directly view the details about alerts.
- Security Center automatically handles alerts, such as alerts that are triggered by malicious process, and sets the status of these alerts to Blocked. By default, the attack source tracing information about malicious processes is not provided.
- Log on to the Security center console.
- In the left-side navigation pane, click .
- On the Alerts page, find the alert that is next to the icon and click the icon.
Click the Diagnosis tab to view the attack name, attack type, attack request details, affected resources, source IP address, and HTTP request details.
On the Diagnosis tab, you can also view the information about each node in the chain diagram of the attack source tracing event. Click a node. On the Node Attributes page, you can view details about the node.
Attack source tracing examples
- Worm propagation events
The following figure shows how a worm propagates by using the source IP address of
185.234.*.*. The worm initiates SSH brute-force attacks to log on to the server and runs the curl command by using Bash to download and run mining programs on the server.
- Web intrusion events
The following figure shows how an attacker initiates attacks from the IP address of
202.144.*.*. The attacker exploits web vulnerabilities to implant webshells and mining programs into a Linux server. Meanwhile, the attacker writes code to the crond scheduled task to achieve persistence. The node information on the Diagnosis tab helps you understand this process more clearly. In addition, you can view the multiple IP addresses that are used by the attacker and the URL information of malicious download sources on the Diagnosis tab.Click an HTTP attack node to view its details. Traffic data indicates that an attacker exploited unauthorized Apache Solr access vulnerabilities to call API operations and run system commands. To block the attack, we recommend that you fix the vulnerabilities to avoid similar attacks in the future.