Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini menjelaskan jenis temuan ancaman di Security Command Center. Temuan ancaman dibuat oleh
pendeteksi ancaman saat mendeteksi
potensi ancaman di resource cloud Anda. Untuk daftar lengkap temuan ancaman yang tersedia, lihat Indeks temuan ancaman.
Ringkasan
Proses dimulai dengan pengalihan aliran ke soket yang terhubung dari jarak jauh. Memunculkan shell yang terhubung ke jaringan dapat memungkinkan penyerang melakukan tindakan arbitrer setelah penyusupan awal yang terbatas.
Buka temuan Reverse Shell seperti yang diarahkan dalam Meninjau temuan.
Tinjau detail di tab Ringkasan dan JSON.
Di tab Summary, tinjau informasi di bagian berikut:
Apa yang terdeteksi, terutama kolom berikut:
Biner program: jalur absolut proses yang dimulai dengan
pengalihan aliran ke soket jarak jauh
Argumen: argumen yang diberikan saat biner proses dipanggil
Resource yang terpengaruh, terutama kolom berikut:
Nama lengkap resource: nama lengkap resource
dari resource Cloud Run yang terpengaruh
Nama lengkap project: project Google Cloud yang terpengaruh
Link terkait, terutama kolom berikut:
Indikator VirusTotal: link ke halaman analisis VirusTotal
Di tab JSON, perhatikan kolom berikut:
resource:
project_display_name: nama project yang berisi aset.
sourceProperties:
Reverse_Shell_Stdin_Redirection_Dst_Ip: alamat IP jarak jauh koneksi
Reverse_Shell_Stdin_Redirection_Dst_Port: port jarak jauh
Reverse_Shell_Stdin_Redirection_Src_Ip: alamat IP lokal koneksi
Reverse_Shell_Stdin_Redirection_Src_Port: port lokal
Container_Image_Uri: nama image container yang sedang dieksekusi.
Cari temuan terkait yang terjadi pada waktu yang serupa untuk penampung yang terpengaruh. Temuan tersebut mungkin menunjukkan bahwa aktivitas ini berbahaya, bukan karena kegagalan mengikuti praktik terbaik.
Periksa nilai hash SHA-256 untuk file biner yang ditandai sebagai berbahaya di
VirusTotal dengan mengklik link di
Indikator VirusTotal. VirusTotal adalah layanan milik Alphabet yang memberikan konteks tentang file, URL, domain, dan alamat IP yang berpotensi berbahaya.
Untuk mengembangkan rencana respons, gabungkan hasil penyelidikan Anda dengan riset MITRE dan analisis VirusTotal.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[],[],null,["| Premium and Enterprise [service tiers](/security-command-center/docs/service-tiers)\n\nThis document describes a threat finding type in Security Command Center. Threat findings are generated by\n[threat detectors](/security-command-center/docs/concepts-security-sources#threats) when they detect\na potential threat in your cloud resources. For a full list of available threat findings, see [Threat findings index](/security-command-center/docs/threat-findings-index).\n\nOverview\n\nA process started with stream redirection to a remote connected socket. Spawning\na network-connected shell can allow an attacker to perform arbitrary actions\nafter a limited initial compromise.\n\n[Cloud Run Threat Detection](/security-command-center/docs/cloud-run-threat-detection-overview) is the source\nof this finding.\n\nHow to respond\n\nTo respond to this finding, do the following:\n\nReview finding details\n\n1. Open the `Reverse Shell` finding as directed in [Reviewing\n findings](/security-command-center/docs/how-to-investigate-threats#reviewing_findings).\n Review the details on the **Summary** and **JSON** tabs.\n\n2. On the **Summary** tab, review the information in the following sections:\n\n - **What was detected** , especially the following fields:\n - **Program binary**: the absolute path of the process started with stream redirection to a remote socket\n - **Arguments**: the arguments provided when the process binary was invoked\n - **Affected resource** , especially the following fields:\n - **Resource full name** : the [full resource name](/apis/design/resource_names) of the affected Cloud Run resource\n - **Project full name**: the affected Google Cloud project\n - **Related links** , especially the following fields:\n - **VirusTotal indicator**: link to the VirusTotal analysis page\n3. On the **JSON** tab, note the following fields:\n\n - `resource`:\n - `project_display_name`: the name of the project that contains the asset.\n - `sourceProperties`:\n - `Reverse_Shell_Stdin_Redirection_Dst_Ip`: the remote IP address of the connection\n - `Reverse_Shell_Stdin_Redirection_Dst_Port`: the remote port\n - `Reverse_Shell_Stdin_Redirection_Src_Ip`: the local IP address of the connection\n - `Reverse_Shell_Stdin_Redirection_Src_Port`: the local port\n - `Container_Image_Uri`: the name of the container image being executed.\n4. Look for related findings that occurred at a similar time for the affected\n container. Such findings might indicate that this activity was malicious,\n instead of a failure to follow best practices.\n\n5. Review the settings of the affected container.\n\n6. Check the logs for the affected container.\n\nResearch attack and response methods\n\n1. Review the MITRE ATT\\&CK framework entries for this finding type: [Command and\n Scripting Interpreter](https://attack.mitre.org/techniques/T1059/) and [Ingress Tool Transfer](https://attack.mitre.org/techniques/T1105/).\n2. Check the SHA-256 hash value for the binary flagged as malicious on [VirusTotal](https://www.virustotal.com) by clicking the link in **VirusTotal indicator**. VirusTotal is an Alphabet-owned service that provides context on potentially malicious files, URLs, domains, and IP addresses.\n3. To develop a response plan, combine your investigation results with the MITRE research and VirusTotal analysis.\n\nImplement your response\n\nFor response recommendations, see [Respond to Cloud Run threat\nfindings](/security-command-center/docs/respond-cloud-run-threats).\n\nWhat's next\n\n- Learn [how to work with threat\n findings in Security Command Center](/security-command-center/docs/how-to-investigate-threats).\n- Refer to the [Threat findings index](/security-command-center/docs/threat-findings-index).\n- Learn how to [review a\n finding](/security-command-center/docs/how-to-investigate-threats#reviewing_findings) through the Google Cloud console.\n- Learn about the [services that\n generate threat findings](/security-command-center/docs/concepts-security-sources#threats)."]]
