Mengkueri detail alert.
Coba sekarang
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
yundun-mss:GetAlarmDetailById |
get |
*全部资源
|
None | None |
Parameter permintaan
|
Parameter |
Type |
Required |
Description |
Example |
| Id |
integer |
Yes |
ID kunci utama. |
20077761 |
Elemen respons
|
Element |
Type |
Description |
Example |
|
object |
Tanggapan. |
||
| Data |
object |
Data yang dikembalikan oleh operasi. |
|
| EventDetails |
array<object> |
Detail event. |
|
|
object |
Objek data. |
||
| NameDisplay |
string |
Nama tampilan event peringatan. |
Login with unusual location |
| ValueDisplay |
string |
Jalur tempat event peringatan terjadi. |
/etc/crontab |
| Type |
string |
Tipe event dari event peringatan. |
text |
| Value |
string |
Jalur tempat event peringatan terjadi. |
/etc/crontab |
| Desc |
string |
Deskripsi. |
webshell |
| TacticDisplayName |
string |
Nama taktik ATT&CK. |
Malicious scripts-Malicious script code execution |
| AlarmEventTypeDisplay |
string |
Tipe event Peringatan. |
Login with unusual location |
| ContainHwMode |
boolean |
Apakah mode perlindungan event kritis diaktifkan. Nilai valid:
|
false |
| AlarmId |
integer |
ID alert. |
202427220 |
| AlarmSource |
string |
Sumber alert. |
SUSP_EVENT |
| AlarmName |
string |
Nama alert. |
负载均衡可挂载服务器数量告警 |
| AlarmTime |
string |
Pengatur waktu alert terbaru. |
2018-09-26 01:51:01 |
| DealTime |
string |
Pengatur waktu saat alert ditangani. |
2018-09-26 01:51:01 |
| Status |
string |
Status penanganan. |
要查询的告警事件状态。取值: 0:全部 1:待处理 2:已忽略 4:已确认 8:已标记为误报 16:处理中 32:处理完毕 64:已经过期 128:已经删除 512:自动拦截中 513:自动拦截完毕 |
| OwnerId |
string |
Pemilik. |
324546 |
| Remark |
string |
Metode penanganan. |
192.168.XX.XX |
| InstanceName |
string |
Aset terdampak. |
nginx |
| EventLevel |
string |
Level alert. |
suspicious |
| OccurrenceTime |
string |
Pengatur waktu saat alert pertama kali terjadi. |
2018-09-26 01:51:01 |
| InternetIp |
string |
Alamat IP publik. |
47.116.126.79 |
| IntranetIp |
string |
Alamat IP internal. |
172.19.195.176 |
| Id |
integer |
ID kunci utama Tiket. |
9772 |
| AlarmEventType |
string |
Tipe event Peringatan. |
Unusual Logon |
| AnalysisResult |
string |
Proses analisis. |
[{"value":"服务器可能已被黑客攻击,存在恶意进程在运行。 分析过程:告警显示,服务端存在一个名为”dns.exe”的进程在访问”polling.burpcollaborator.net”,这是一个被黑名单列出的恶意域名。在正常情况下,”dns.exe”不应该单独存在于系统的路径下,并且也不应该访问这类恶意域名。因此,这个进程可能是黑客留下的恶意进程。","key":"结论"},{"value":"尽快对服务器进行全面扫描,清除恶意进程。同时,联系网络安全专家进行深入调查,以确定是否有其他潜在的安全威胁。","key":"处置建议"}] |
| RequestId |
string |
ID permintaan. |
5C1B0668-442C-57AE-9668-D894B0B012EB |
| Code |
string |
Kode tanggapan. |
200 |
| Message |
string |
Paket yang dikembalikan. |
successful |
| HttpStatusCode |
integer |
Kode status HTTP. |
200 |
| Success |
boolean |
Apakah operasi berhasil. Nilai valid:
|
true |
Contoh
Respons sukses
JSONformat
{
"Data": {
"EventDetails": [
{
"NameDisplay": "Login with unusual location",
"ValueDisplay": "/etc/crontab",
"Type": "text",
"Value": "/etc/crontab"
}
],
"Desc": "webshell",
"TacticDisplayName": "Malicious scripts-Malicious script code execution",
"AlarmEventTypeDisplay": "Login with unusual location",
"ContainHwMode": false,
"AlarmId": 202427220,
"AlarmSource": "SUSP_EVENT",
"AlarmName": "负载均衡可挂载服务器数量告警",
"AlarmTime": "2018-09-26 01:51:01",
"DealTime": "2018-09-26 01:51:01",
"Status": "要查询的告警事件状态。取值:\n\n0:全部\n1:待处理\n2:已忽略\n4:已确认\n8:已标记为误报\n16:处理中\n32:处理完毕\n64:已经过期\n128:已经删除\n512:自动拦截中\n513:自动拦截完毕",
"OwnerId": "324546",
"Remark": "192.168.XX.XX",
"InstanceName": "nginx",
"EventLevel": "suspicious",
"OccurrenceTime": "2018-09-26 01:51:01",
"InternetIp": "47.116.126.79",
"IntranetIp": "172.19.195.176",
"Id": 9772,
"AlarmEventType": "Unusual Logon",
"AnalysisResult": "[{\"value\":\"服务器可能已被黑客攻击,存在恶意进程在运行。 分析过程:告警显示,服务端存在一个名为”dns.exe”的进程在访问”polling.burpcollaborator.net”,这是一个被黑名单列出的恶意域名。在正常情况下,”dns.exe”不应该单独存在于系统的路径下,并且也不应该访问这类恶意域名。因此,这个进程可能是黑客留下的恶意进程。\",\"key\":\"结论\"},{\"value\":\"尽快对服务器进行全面扫描,清除恶意进程。同时,联系网络安全专家进行深入调查,以确定是否有其他潜在的安全威胁。\",\"key\":\"处置建议\"}]"
},
"RequestId": "5C1B0668-442C-57AE-9668-D894B0B012EB",
"Code": "200",
"Message": "successful",
"HttpStatusCode": 200,
"Success": true
}
Kode kesalahan
Lihat Error Codes untuk daftar lengkap.
Catatan rilis
Lihat Release Notes untuk daftar lengkap.