Panduan ini menunjukkan cara menyelidiki pemberitahuan menggunakan Google Security Operations.
Apa yang dimaksud dengan peringatan?
Peringatan adalah Indikator Gangguan (IOC), yang ditandai oleh Google Security Operations,
yang menunjukkan anomali dalam alur kerja traffic yang normal dalam perusahaan.
Anda harus menyelidiki pemberitahuan sebagai kemungkinan pelanggaran keamanan.
Bagaimana cara pemberitahuan masuk ke Google Security Operations?
Google Security Operations memanfaatkan berbagai sumber eksternal dalam komunitas keamanan menggunakan database di seluruh industri yang terus diperbarui. Google Security Operations juga memiliki bahasa pemrograman kaya fitur, YARA-L, sehingga Anda dapat membuat aturan kustom sendiri.
Anda dapat melakukan langkah-langkah ini dari instance Google Security Operations perusahaan Anda atau dari lingkungan demo Google Security Operations.
Google Security Operations dirancang untuk berfungsi secara eksklusif dengan browser Google Chrome atau Mozilla Firefox.
Google merekomendasikan agar Anda mengupgrade browser ke versi terbaru. Anda dapat mendownload Chrome versi terbaru dari https://www.google.com/chrome/.
Google SecOps terintegrasi ke dalam solusi single sign-on (SSO) Anda.
Anda dapat login ke Google SecOps menggunakan kredensial yang disediakan oleh perusahaan Anda.
Luncurkan Chrome atau Firefox.
Pastikan Anda memiliki akses ke akun perusahaan Anda.
Untuk mengakses aplikasi Google SecOps, dengan customer_subdomain
adalah ID khusus pelanggan Anda, buka:
https://customer_subdomain.backstory.chronicle.security.
Melihat Pemberitahuan dan Kecocokan IOC
Di panel navigasi, pilih Detection > Alerts and IOCs.
Tab Alerts dan IOC Matches ditampilkan. Anda mungkin harus menyesuaikan rentang waktu menggunakan kontrol kalender di kanan atas agar kecocokan dan pemberitahuan muncul.
Beralih ke tampilan Aset
Selanjutnya, lihat detail aset tertentu yang mungkin telah disusupi.
Dari tab IOC Matches, klik domain untuk membuka tampilan Domain.
Pilih tab Linimasa.
Untuk beralih ke tampilan Aset, pilih peristiwa dengan mengklik waktunya. Tampilan aset menampilkan detail aset yang dipilih di sekitar linimasa pemicu pemberitahuan, seperti yang ditunjukkan pada gambar berikut.
Tampilan aset
Balon di jendela utama menunjukkan prevalensi aset. Grafik disusun sehingga peristiwa yang lebih jarang terjadi berada di bagian atas. Peristiwa dengan prevalensi rendah ini dianggap mencurigakan. Gunakan Penggeser waktu di kanan atas untuk memperbesar peristiwa yang memerlukan penyelidikan.
Jika menu Pemfilteran Prosedural tidak terlihat, buka dengan mengklik ikon Filter (di dekat sudut kanan atas).
Di bagian atas menu, sesuaikan penggeser Prevalensi untuk memfilter peristiwa umum. Menggunakan penggeser Waktu dan Prevalensi untuk mengidentifikasi peristiwa mencurigakan.
Buka notifikasi dari daftar sidebar Linimasa. Di panel kiri, pilih tab Linimasa yang menampilkan peristiwa yang terjadi di sekitar pemberitahuan. Peristiwa pemicu disorot dengan warna hijau.
Menyelidiki apa yang memicu notifikasi
Ada beberapa cara untuk mendapatkan lebih banyak insight tentang peristiwa pemicu.
Di panel tengah, kotak dialog berwarna oranye dapat muncul di atas segitiga oranye kecil yang menunjukkan lokasi, dalam waktu, peringatan. Jika kotak dialog tidak ditampilkan, mengarahkan kursor ke segitiga akan membuatnya muncul. Dialog berisi tanggal, waktu, dan deskripsi notifikasi.
Panel kiri di tampilan Aset menampilkan tab Linimasa. Jika diberi label Pemberitahuan Aturan, acara tersebut juga akan menyebutkan deskripsi pemberitahuan.
Mengarahkan kursor ke peristiwa Rule Alert akan menyebabkan ikon Perluas muncul di sisi kanan peristiwa. Mengklik ikon ini akan membuka jendela baru dengan detail selengkapnya tentang peristiwa dalam format UDM, seperti yang ditunjukkan pada gambar berikut.
[[["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-08-21 UTC."],[[["\u003cp\u003eThis guide details how to investigate security alerts within Google Security Operations, which are indicators of potential security breaches identified through various external security sources and custom YARA-L rules.\u003c/p\u003e\n"],["\u003cp\u003eTo begin, access Google Security Operations via Chrome or Firefox using your enterprise credentials, and then navigate to the "Detection > Alerts and IOCs" section to view alerts and IOC matches.\u003c/p\u003e\n"],["\u003cp\u003eFrom the IOC Matches tab, you can pivot to Asset view to investigate specific assets by selecting an event's time and using the Time and Prevalence sliders to filter for suspicious events.\u003c/p\u003e\n"],["\u003cp\u003eThe Asset view's Timeline tab offers details about events surrounding an alert, with the triggering event highlighted in green, and more information available by hovering over "Rule Alert" events and expanding them.\u003c/p\u003e\n"],["\u003cp\u003eAn alert from Google security operations can be investigated to determine what specifically triggered it, by using the middle panel's orange dialog box, or the left panel's Timeline tab description.\u003c/p\u003e\n"]]],[],null,["# Quickstart: Review an alert using Google Security Operations\n\nReview an alert using Google Security Operations\n================================================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\nThis guide shows how to investigate an alert using Google Security Operations.\n\n\u003cbr /\u003e\n\n### What is an alert?\n\nAn [alert](https://cloud.google.com/chronicle/docs/investigation/alerts-iocs) is an Indicator of Compromise (IOC), flagged by [Google Security Operations](https://cloud.google.com/chronicle/docs/overview),\nindicating an anomaly in the normal workflow of traffic within the enterprise.\nYou should investigate alerts as a possible breach of security.\n\n### How do alerts get to Google Security Operations?\n\nGoogle Security Operations taps into various external sources within the security\ncommunity using industry-wide databases updated continuously. Google Security Operations\nalso has a feature-rich programming language, YARA-L, so you can craft your own custom rules.\n\nFor more information on YARA-L, see the [Overview of the YARA-L 2.0 language](/chronicle/docs/detection/yara-l-2-0-overview). For more information on rules, see [Manage Rules Using Rules Editor](/chronicle/docs/detection/manage-all-rules).\n\nBefore you begin\n----------------\n\nYou can perform these steps from your company's Google Security Operations instance or\nfrom the Google Security Operations demo environment.\n\nGoogle Security Operations is designed to work exclusively with the Google Chrome or Mozilla Firefox browsers.\n| **Note:** Google SecOps doesn't support multiple concurrent logins for the same profile.\n\nGoogle recommends upgrading your browser to the most current version. You can download the latest version of Chrome from \u003chttps://www.google.com/chrome/\u003e.\n\nGoogle SecOps is integrated into your single sign-on solution (SSO).\nYou can log in to Google SecOps using the credentials provided by your enterprise.\n\n1. Launch Chrome or Firefox.\n\n2. Ensure you have access to your corporate account.\n\n3. To access the Google SecOps application, where \u003cvar translate=\"no\"\u003ecustomer_subdomain\u003c/var\u003e\n is your customer-specific identifier, navigate to:\n https://\u003cvar translate=\"no\"\u003ecustomer_subdomain\u003c/var\u003e.backstory.chronicle.security.\n\nView Alerts and IOC Matches\n---------------------------\n\nIn the navigation bar, select **Detection \\\u003e Alerts and IOCs**.\n\nThe Alerts and IOC Matches tabs are displayed. You may have to adjust the time\nrange using the calendar control in the top right for matches and alerts to appear.\n\nPivot to Asset view\n-------------------\n\nNext, drill down to a particular asset that may have been compromised.\n\n1. From the IOC Matches tab, click on a domain to open Domain view.\n\n2. Select the Timeline tab.\n\n3. To pivot to Asset view, select an event by clicking on its time. Asset view shows details of the selected asset around the timeline of the alert trigger, as shown in the following figure.\n\n\n **Asset view**\n\n The bubbles in the main window represent the prevalence of the asset. The graph is arranged so events occurring less often are at the top. These low-prevalence events are considered suspicious. Use the Time slider in the upper right to zoom in to events requiring investigation.\n4. If the Procedural Filtering menu is not visible, open it by clicking the *Filter* icon (near the upper right corner).\n\n5. At the top of the menu, adjust the **Prevalence** slider to filter out common events. Using the Time and Prevalence sliders, to identify suspicious events.\n\n6. Open the alert from the Timeline sidebar list. In the left panel, select the Timeline tab which display events occurring around the alert. The triggering event is highlighted in green.\n\nInvestigate what triggered the alert\n------------------------------------\n\nThere are several ways to gain more insight into the triggering event.\n\n- In the middle panel, an orange dialog box may appear above a small orange triangle indicating the location, in time, of the alert. If the dialog box is not displayed, hovering over the triangle causes it to appear. The dialog contains the date, time, and description of the alert.\n\n- The left panel in Asset view shows the Timeline tab. If the event is labeled *Rule Alert*, it will also mention a description of the alert.\n\n- Hovering over the *Rule Alert* event causes an *Expand* icon to appear on the right side of the event. Clicking on this icon will open a new window with more details about the event in UDM format, as shown in the following figure.\n\n\n **Event Details**\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]