Gunakan kolom Aturan penelusuran untuk menelusuri aturan yang ada. Anda juga dapat men-scroll aturan menggunakan scroll bar. Klik salah satu aturan di panel kiri untuk melihat aturan di panel tampilan aturan.
Pilih aturan yang Anda inginkan dari Daftar Aturan. Aturan ditampilkan di jendela pengeditan aturan. Dengan memilih aturan, Anda membuka menu aturan dan dapat memilih dari opsi berikut:
Aturan Aktif—Aktifkan atau nonaktifkan aturan.
Duplikasikan Aturan—Buat salinan aturan; berguna jika Anda ingin membuat aturan yang serupa.
Lihat Deteksi Aturan—Buka jendela Deteksi Aturan untuk menampilkan deteksi yang diambil oleh aturan ini.
Gunakan jendela Pengeditan Aturan untuk mengedit aturan yang ada dan membuat aturan baru.
Jendela Pengeditan Aturan mencakup fitur penyelesaian otomatis untuk memungkinkan Anda
melihat sintaks YARA-L yang benar yang tersedia untuk setiap bagian aturan.
Setiap kali menyusun atau mengedit aturan, Google Security Operations merekomendasikan untuk menelusuri rekomendasi otomatis guna memastikan aturan yang telah selesai menggunakan sintaksis yang benar. Untuk memperbarui cakupan aturan, pilih cakupan dari menu
Ikat ke cakupan. Untuk mengetahui informasi selengkapnya tentang cara mengaitkan cakupan dengan aturan, lihat dampak RBAC data pada Aturan.
Untuk mengetahui informasi selengkapnya, lihat sintaksis bahasa YARA-L 2.0.
Klik Baru di Editor Aturan untuk membuka Jendela Editor Aturan. Secara otomatis, template ini akan diisi dengan template aturan default.
Google SecOps secara otomatis membuat nama unik untuk
aturan tersebut. Buat aturan baru Anda di YARA-L. Untuk menambahkan cakupan ke aturan, pilih cakupan dari menu Ikat ke cakupan. Untuk mengetahui informasi selengkapnya tentang cara menambahkan cakupan ke aturan, lihat dampak RBAC data pada Aturan.
Setelah selesai, klik SIMPAN ATURAN BARU. Google SecOps memeriksa sintaksis aturan Anda. Jika valid, aturan akan disimpan dan diaktifkan secara otomatis.
Jika sintaksis tidak valid, error akan ditampilkan. Untuk menghapus aturan baru, klik HAPUS.
Untuk melihat informasi tentang deteksi saat ini yang terkait dengan aturan, klik
aturan dalam daftar aturan, lalu klik Lihat Deteksi Aturan untuk membuka tampilan
Deteksi Aturan.
Tampilan Deteksi Aturan menampilkan metadata yang dilampirkan ke aturan dan
grafik yang menunjukkan jumlah deteksi yang ditemukan oleh aturan selama beberapa hari terakhir.
Klik Edit Aturan untuk kembali ke Editor Aturan.
Tampilan multi-kolom
Tab Linimasa juga tersedia dan mencantumkan peristiwa yang terdeteksi oleh aturan. Seperti tab Linimasa di tampilan Google SecOps lainnya, Anda dapat memilih peristiwa dan membuka log mentah atau peristiwa UDM terkait.
Anda juga dapat memanipulasi informasi yang ditampilkan di tab Linimasa dengan mengklik ikon Kolom untuk membuka opsi tampilan multi-kolom. Tampilan multikolom memungkinkan Anda memilih berbagai kategori informasi log untuk ditampilkan, termasuk jenis umum seperti nama host dan pengguna serta banyak kategori yang lebih spesifik yang disediakan oleh UDM.
Klik JALANKAN UJI untuk menjalankan aturan yang ditampilkan di jendela pengeditan aturan. Google SecOps mulai mengumpulkan deteksi. Dengan begitu, Anda dapat dengan cepat memeriksa apakah aturan berfungsi seperti yang diharapkan. Informasi deteksi ditampilkan di jendela HASIL ATURAN PENGUJIAN. Kapan saja Anda dapat mengklik BATALKAN TES untuk menghentikan proses ini.
Untuk blog Komunitas tentang mengelola aturan, lihat:
[[["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\u003eThe Rules Editor allows users to manage both existing and new rules within Google SecOps.\u003c/p\u003e\n"],["\u003cp\u003eUsers can search for rules, view rule details, enable/disable rules, duplicate rules, and view rule detections within the Rules Editor.\u003c/p\u003e\n"],["\u003cp\u003eThe Rule Editing window offers an automatic completion feature, guiding users through the correct YARA-L syntax and allows for the association of rules with specific scopes via the "Bind to scope" menu.\u003c/p\u003e\n"],["\u003cp\u003eNew rules can be created using a default template, and the system automatically generates a unique rule name, performing syntax checks upon saving, with valid rules being automatically enabled.\u003c/p\u003e\n"],["\u003cp\u003eUsers can run tests on rules to check if they are working as expected, with results displayed in a dedicated window, though these test results are not saved.\u003c/p\u003e\n"]]],[],null,["# Manage rules using the Rules Editor\n===================================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n\nTo use the Rules Editor to create and edit rules, follow these steps:\n\n1. Click **Detections \\\u003e Rules \\& Detections** \\\u003e the **Rules Editor** tab.\n\n2. Use the **Search rules** field to search for an existing rule. You can also scroll through the rules using the scroll bar. Click any of the rules in the left panel to view the rule in the rule display panel.\n\n3. Select the rule you are interested in from the Rules List. The rule is displayed in the rule editing window. By selecting a rule, you open the rule menu and can select from the following options:\n\n - **Live Rule**---Enable or disable the rule.\n - **Duplicate Rule**---Make a copy of the rule; helpful if you want to make a similar rule.\n - **View Rule Detections**---Open the Rule Detections window to display the detections captured by this rule.\n4. Use the Rule Editing window to edit existing rules and to create new rules.\n The Rule Editing window includes an automatic completion feature to enable you\n to view the correct YARA-L syntax available for each section of the rule.\n Whenever composing or editing a rule, Google Security Operations recommends walking\n through the automatic recommendations to ensure your completed rule uses the\n correct syntax. To update the rule scope, select the scope from the\n **Bind to scope** menu. For more information about associating a scope\n with a rule, see [data RBAC impact on Rules](/chronicle/docs/administration/datarbac-impact#rules).\n For more information, see [YARA-L 2.0 language syntax](/chronicle/docs/detection/yara-l-2-0-syntax).\n\n5. Click **New** in the Rules Editor to open the Rules Editor Window. It\n automatically populates it with the default rule template.\n Google SecOps automatically generates a unique name for\n the rule. Create your new rule in YARA-L. To add a scope to the rule, select the\n scope from the **Bind to scope** menu. For more information about adding a scope\n to rules, see [data RBAC impact on Rules](/chronicle/docs/administration/datarbac-impact#rules).\n When you have finished, click **SAVE NEW RULE** . Google SecOps checks the\n syntax of your rule. If the rule is valid, it is saved and automatically enabled.\n If the syntax is invalid, it returns an error. To delete the new rule, click **DISCARD**.\n\n | **Note:** After you have saved a rule, you cannot delete it from the Rules Editor or the Rules Dashboard.\n | **Note:** For Multi-event rules correlating more than one event with a match section size of over one hour, the rule's run frequency (when executing as a Live Rule) is automatically set to 1 hour.\n6. To view information on the current detections associated with a rule, click\n the rule in the rules list and click **View Rule Detections** to open Rule\n Detections view.\n\n The **Rule Detections** view displays the metadata attached to the rule and\n a graph showing the number of detections found by the rule over recent days.\n7. Click **Edit Rule** to return to the Rules Editor.\n\n #### Multicolumn view\n\n The **Timeline** tab is also available and lists the events detected by the rule.\n As with the **Timeline** tab in other Google SecOps views, you can\n select an event and open the associated raw log or UDM event.\n\nClick view_column **Columns**\nto open the multicolumn view options and\nchange the information shown on the **Timeline** tab. The multicolumn view lets\nyou choose from various categories of log information, including common types,\nsuch as `hostname` and `user` and more specific categories provided by UDM.\n\n1. Click **RUN TEST** to test your rule. Google SecOps runs the rule on events in the specified time range, generates results, and displays them in the **TEST RULE RESULTS** window. \n Click **CANCEL TEST** at any time to stop the process.\n\n| **Note:** Successive executions of the same test rule may generate different test detections and is expected behavior. Google SecOps runs a test rule in multiple parallel processes and detections are streamed to the dashboard as each process finishes. Minor timing differences can affect which duplicate detections are removed. By extension, results may not match those of live rules or retrohunts.\n| **Note:** Test rule detections aren't persisted and don't generate alerts. This behavior allows rule authors to iterate without affecting production. Test rule detections may differ from retrohunt or live rule detections because the evaluation windows may be aligned differently.\n| **Note:** These test results are not saved and won't be viewable in the Rules Dashboard.\n\nFor Community blogs on managing rules, see:\n\n- [Rules Editor Navigation](https://www.googlecloudcommunity.com/gc/Google-Security-Operations-Best/Getting-to-Know-Google-SecOps-SIEM-Rules-Editor-Navigation/ta-p/659309)\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
