Dokumen ini menjelaskan cara menyerap log DNS F5 ke Google Security Operations menggunakan
Bindplane. Parser mengekstrak kolom dari pesan syslog DNS F5 menggunakan pola grok berdasarkan kolom aplikasi, lalu memetakannya ke Model Data Terpadu (UDM). Aplikasi ini menangani berbagai aplikasi F5 seperti gtmd, mcpd, big3d, dan
lainnya, mem-parsing kolom tertentu dan menetapkan jenis peristiwa UDM, tingkat
keparahan, dan deskripsi yang sesuai berdasarkan tingkat log dan aplikasi.
Sebelum memulai
Pastikan Anda memenuhi prasyarat berikut:
Instance Google SecOps
Host Windows 2016 atau yang lebih baru, atau host Linux dengan systemd
Jika dijalankan di belakang proxy, port firewall terbuka
Akses istimewa ke F5 BIG-IP
Mendapatkan file autentikasi penyerapan Google SecOps
Login ke konsol Google SecOps.
Buka Setelan SIEM > Agen Pengumpulan.
Download File Autentikasi Penyerapan. Simpan file dengan aman di sistem tempat BindPlane akan diinstal.
Mendapatkan ID pelanggan Google SecOps
Login ke konsol Google SecOps.
Buka Setelan SIEM > Profil.
Salin dan simpan ID Pelanggan dari bagian Detail Organisasi.
Menginstal agen Bindplane
Instal agen Bindplane di sistem operasi Windows atau Linux Anda sesuai
dengan petunjuk berikut.
Penginstalan Windows
Buka Command Prompt atau PowerShell sebagai administrator.
Mengonfigurasi agen BindPlane untuk menyerap Syslog dan mengirimkannya ke Google SecOps
Akses file konfigurasi:
Cari file config.yaml. Biasanya, file ini berada di
direktori /etc/bindplane-agent/ di Linux atau di direktori penginstalan
di Windows.
Buka file menggunakan editor teks (misalnya, nano, vi, atau Notepad).
Edit file config.yaml sebagai berikut:
receivers:udplog:# Replace the port and IP address as requiredlisten_address:"0.0.0.0:514"exporters:chronicle/chronicle_w_labels:compression:gzip# Adjust the path to the credentials file you downloaded in Step 1creds_file_path:'/path/to/ingestion-authentication-file.json'# Replace with your actual customer ID from Step 2customer_id:<customer_id>
endpoint:malachiteingestion-pa.googleapis.com# Add optional ingestion labels for better organizationlog_type:'F5_DNS'raw_log_field:bodyingestion_labels:service:pipelines:logs/source0__chronicle_w_labels-0:receivers:-udplogexporters:-chronicle/chronicle_w_labels
Ganti port dan alamat IP sesuai kebutuhan di infrastruktur Anda.
Ganti <customer_id> dengan ID pelanggan yang sebenarnya.
Mulai ulang agen Bindplane untuk menerapkan perubahan
Untuk memulai ulang agen Bindplane di Linux, jalankan perintah berikut:
sudosystemctlrestartbindplane-agent
Untuk memulai ulang agen Bindplane di Windows, Anda dapat menggunakan konsol Services
atau memasukkan perintah berikut:
net stop BindPlaneAgent && net start BindPlaneAgent
Mengonfigurasi kumpulan server logging jarak jauh
Login ke UI web F5 BIG-IP.
Pada tab Main, buka DNS > Delivery > Load Balancing > Pools or Local Traffic > Pools.
Klik Buat.
Berikan detail konfigurasi berikut:
Nama: Masukkan nama unik untuk pool.
Menggunakan setelan Anggota Baru:
Masukkan alamat IP agen Bindplane di kolom Address.
Masukkan nomor port agen Bindplane di kolom Service Port.
Klik Tambahkan > Selesai.
Mengonfigurasi tujuan log jarak jauh
Di tab Main, buka System > Logs > Configuration > Log Destinations.
Klik Buat.
Berikan detail konfigurasi berikut:
Nama: Masukkan nama unik untuk tujuan ini.
Jenis: Pilih Log Kecepatan Tinggi Jarak Jauh.
Pool Name: Pilih kumpulan server log jarak jauh yang ingin Anda kirimi pesan log oleh sistem BIG-IP.
Protokol: Pilih protokol yang digunakan.
Klik Selesai.
Membuat tujuan log jarak jauh yang diformat
Di tab Main, buka System > Logs > Configuration > Log Destinations.
Klik Buat.
Berikan detail konfigurasi berikut:
Nama: Masukkan nama unik untuk tujuan ini.
Jenis: Pilih Remote Syslog.
Format: Pilih format log.
Teruskan Ke: Pilih Tujuan Log Kecepatan Tinggi > tujuan yang mengarah ke kumpulan server Syslog jarak jauh.
Klik Selesai.
Mengonfigurasi Log Publisher
Di tab Main, buka System > Logs > Configuration > Log Publishers.
Klik Buat.
Berikan detail konfigurasi berikut:
Nama: Masukkan nama unik untuk penayang ini.
Tujuan: Pilih tujuan yang baru dibuat untuk
Remote Syslog dari daftar Tersedia, lalu
klik
keyboard_double_arrow_left
Pindahkan untuk memindahkan tujuan ke daftar Dipilih.
Klik Selesai.
Mengonfigurasi profil logging DNS kustom
Di tab Main, buka DNS > Delivery > Profiles > Other > DNS Logging atau Local Traffic > Profiles > Other > DNS Logging.
Klik Buat.
Berikan detail konfigurasi berikut:
Nama: Masukkan nama unik untuk profil ini.
Log Publisher: Pilih tujuan yang baru dibuat tempat sistem mengirim entri log DNS.
Log Kueri: Centang kotak Diaktifkan.
Log Respons: Centang kotak Diaktifkan.
Sertakan ID Kueri: Centang kotak Diaktifkan.
Klik Selesai.
Tambahkan profil DNS ke DNS Listener
Di tab Main, buka DNS > Delivery > Listeners > pilih DNS listener.
Dari DNS profile di bagian Service, pilih DNS profile yang Anda konfigurasi sebelumnya.
Klik Perbarui.
Tabel pemetaan UDM
Kolom Log
Pemetaan UDM
Logika
application
principal.application
Dipetakan langsung dari kolom application.
cipher_name
network.tls.cipher
Dipetakan langsung dari kolom cipher_name.
command_line
principal.process.command_line
Dipetakan langsung dari kolom command_line.
desc
security_result.description
Dipetakan langsung dari kolom desc.
desc_icrd
security_result.description
Dipetakan langsung dari kolom desc_icrd.
dest_ip
target.ip
Dipetakan langsung dari kolom dest_ip.
dest_port
target.port
Dipetakan langsung dari kolom dest_port.
file_path
principal.process.file.full_path
Dipetakan langsung dari kolom file_path. Disetel ke true jika level adalah "alert", jika tidak, tidak ada. Disetel ke true jika level adalah "alert", jika tidak, tidak ada.
msg3
security_result.description
Dipetakan langsung dari kolom msg3 saat application adalah "run-parts".
metadata.event_type
Disetel ke GENERIC_EVENT jika event_type kosong, atau dipetakan dari event_type. Dikodekan secara permanen ke "DNS". Dikodekan secara permanen ke "F5".
principal_hostname
principal.hostname
Dipetakan langsung dari kolom principal_hostname.
proc_id
principal.process.pid
Dipetakan langsung dari kolom proc_id.
received_bytes
network.received_bytes
Dipetakan langsung dari kolom received_bytes.
resource_id
target.resource.id
Dipetakan langsung dari kolom resource_id.
resource_parent
principal.resource.parent
Dipetakan langsung dari kolom resource_parent.
response_code
network.http.response_code
Dipetakan langsung dari kolom response_code. Ditentukan berdasarkan kolom level.
src_ip
principal.ip
Dipetakan langsung dari kolom src_ip.
src_port
principal.port
Dipetakan langsung dari kolom src_port.
tls_version
network.tls.version
Dipetakan langsung dari kolom tls_version.
userName
principal.user.userid
Dipetakan langsung dari kolom userName.
when
event.timestamp
Dihitung dari datetime1 dan timezone atau datetime dan timezone.
[[["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-04 UTC."],[],[],null,["# Collect F5 DNS logs\n===================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n| **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).\n\nThis document explains how to ingest F5 DNS logs to Google Security Operations using\nBindplane. The parser extracts fields from F5 DNS syslog messages using grok\npatterns based on the application field, then maps them to the Unified Data Model\n(UDM). It handles various F5 applications like `gtmd`, `mcpd`, `big3d`, and\nothers, parsing specific fields and setting the appropriate UDM event type,\nseverity, and descriptions based on the log level and application.\n\nBefore you begin\n----------------\n\nMake sure you have the following prerequisites:\n\n- A Google SecOps instance\n- A Windows 2016 or later, or a Linux host with `systemd`\n- If running behind a proxy, firewall [ports](/chronicle/docs/ingestion/use-bindplane-agent#verify_the_firewall_configuration) are open\n- Privileged access to F5 BIG-IP\n\nGet Google SecOps ingestion authentication file\n-----------------------------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Collection Agents**.\n3. Download the **Ingestion Authentication File**. Save the file securely on the system where Bindplane will be installed.\n\nGet Google SecOps customer ID\n-----------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Profile**.\n3. Copy and save the **Customer ID** from the **Organization Details** section.\n\nInstall the Bindplane agent\n---------------------------\n\nInstall the Bindplane agent on your Windows or Linux operating system according\nto the following instructions.\n\n### Windows installation\n\n1. Open the **Command Prompt** or **PowerShell** as an administrator.\n2. Run the following command:\n\n msiexec /i \"https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi\" /quiet\n\n### Linux installation\n\n1. Open a terminal with root or sudo privileges.\n2. Run the following command:\n\n sudo sh -c \"$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)\" install_unix.sh\n\n### Additional installation resources\n\nFor additional installation options, consult the\n[installation guide](/chronicle/docs/ingestion/use-bindplane-agent#install_the_bindplane_agent).\n\nConfigure the Bindplane agent to ingest Syslog and send to Google SecOps\n------------------------------------------------------------------------\n\n1. Access the configuration file:\n - Locate the `config.yaml` file. Typically, it's in the `/etc/bindplane-agent/` directory on Linux or in the installation directory on Windows.\n - Open the file using a text editor (for example, `nano`, `vi`, or Notepad).\n2. Edit the `config.yaml` file as follows:\n\n receivers:\n udplog:\n # Replace the port and IP address as required\n listen_address: \"0.0.0.0:514\"\n\n exporters:\n chronicle/chronicle_w_labels:\n compression: gzip\n # Adjust the path to the credentials file you downloaded in Step 1\n creds_file_path: '/path/to/ingestion-authentication-file.json'\n # Replace with your actual customer ID from Step 2\n customer_id: \u003ccustomer_id\u003e\n endpoint: malachiteingestion-pa.googleapis.com\n # Add optional ingestion labels for better organization\n log_type: 'F5_DNS'\n raw_log_field: body\n ingestion_labels:\n\n service:\n pipelines:\n logs/source0__chronicle_w_labels-0:\n receivers:\n - udplog\n exporters:\n - chronicle/chronicle_w_labels\n\n - Replace the port and IP address as required in your infrastructure.\n - Replace `\u003ccustomer_id\u003e` with the actual customer ID.\n - Update `/path/to/ingestion-authentication-file.json` to the path where the authentication file was saved in the [Get Google SecOps ingestion authentication file](/chronicle/docs/ingestion/default-parsers/F5-dns#get-auth-file) section.\n\nRestart the Bindplane agent to apply the changes\n------------------------------------------------\n\n- To restart the Bindplane agent in **Linux**, run the following command:\n\n sudo systemctl restart bindplane-agent\n\n- To restart the Bindplane agent in **Windows** , you can either use the **Services**\n console or enter the following command:\n\n net stop BindPlaneAgent && net start BindPlaneAgent\n\nConfigure a pool of remote logging servers\n------------------------------------------\n\n1. Sign in to the **F5 BIG-IP** web UI.\n2. On the **Main** tab, go to **DNS \\\u003e Delivery \\\u003e Load Balancing \\\u003e Pools or Local Traffic \\\u003e Pools**.\n3. Click **Create**.\n4. Provide the following configuration details:\n - **Name**: Enter a unique name for the pool.\n - Using **New Members** setting:\n - Enter the Bindplane agent IP address in the **Address** field.\n - Enter the Bindplane agent port number in the **Service Port** field.\n5. Click **Add \\\u003e Finished**.\n\nConfigure the remote log destination\n------------------------------------\n\n1. On the **Main** tab, go to **System \\\u003e Logs \\\u003e Configuration \\\u003e Log Destinations**.\n2. Click **Create**.\n3. Provide the following configuration details:\n - **Name**: Enter a unique name for this destination.\n - **Type** : Select **Remote High-Speed Log**.\n - **Pool Name**: Select the pool of remote log servers to which you want the BIG-IP system to send log messages.\n - **Protocol**: Select the protocol used.\n4. Click **Finished**.\n\nCreating a formatted remote log destination\n-------------------------------------------\n\n1. On the **Main** tab, go to **System \\\u003e Logs \\\u003e Configuration \\\u003e Log Destinations**.\n2. Click **Create**.\n3. Provide the following configuration details:\n - **Name**: Enter a unique name for this destination.\n - **Type** : Select **Remote Syslog**.\n - **Format**: Select the log format.\n - **Forward To** : Select **High-Speed Log Destination \\\u003e the destination that points to the pool of remote Syslog servers**.\n4. Click **Finished**.\n\nConfigure Log Publisher\n-----------------------\n\n1. On the **Main** tab, go to **System \\\u003e Logs \\\u003e Configuration \\\u003e Log Publishers**.\n2. Click **Create**.\n3. Provide the following configuration details:\n - **Name**: Enter a unique name for this publisher.\n - **Destinations** : Select the newly-created destination for **Remote Syslog** from the **Available** list, and then click keyboard_double_arrow_left **Move** to move the destination to the **Selected** list.\n4. Click **Finished**.\n\nConfigure a custom DNS logging profile\n--------------------------------------\n\n1. On the **Main** tab, go to **DNS \\\u003e Delivery \\\u003e Profiles \\\u003e Other \\\u003e DNS Logging or Local Traffic \\\u003e Profiles \\\u003e Other \\\u003e DNS Logging**.\n2. Click **Create**.\n3. Provide the following configuration details:\n - **Name**: Enter a unique name for this profile.\n - **Log Publisher**: Select the newly-created destination to which the system sends DNS log entries.\n - **Log Queries** : Select the **Enabled** checkbox.\n - **Log Responses** : Select the **Enabled** checkbox.\n - **Include Query ID** : Select the **Enabled** checkbox.\n4. Click **Finished**.\n\nAdd the DNS profile to the DNS Listener\n---------------------------------------\n\n1. On the **Main** tab, go to **DNS \\\u003e Delivery \\\u003e Listeners \\\u003e select DNS listener**.\n2. From the **DNS profile** in the **Service** section, select the **DNS profile** that you configured previously.\n3. Click **Update**.\n\nUDM mapping table\n-----------------\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
