找出 config.yaml 檔案。通常位於 Linux 的 /etc/bindplane-agent/ 目錄，或 Windows 的安裝目錄。
使用文字編輯器 (例如 nano、vi 或記事本) 開啟檔案。
按照下列方式編輯 config.yaml 檔案：
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:'/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 organizationingestion_labels:log_type:ARUBA_WIRELESSraw_log_field:bodyservice:pipelines:logs/source0__chronicle_w_labels-0:receivers:-udplogexporters:-chronicle/chronicle_w_labels
視基礎架構需求，替換通訊埠和 IP 位址。
將 <customer_id> 替換為實際的客戶 ID。
將 /path/to/ingestion-authentication-file.json 更新為「取得 Google SecOps 擷取驗證檔案」一節中儲存驗證檔案的路徑。
重新啟動 Bindplane 代理程式，以套用變更
如要在 Linux 中重新啟動 Bindplane 代理程式，請執行下列指令：
sudosystemctlrestartbindplane-agent
如要在 Windows 中重新啟動 Bindplane 代理程式，可以使用「服務」控制台，或輸入下列指令：
net stop BindPlaneAgent && net start BindPlaneAgent
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eThis document provides instructions on how to collect Aruba Wireless Controller and Access Point logs using Bindplane for Google SecOps, which includes parsing SYSLOG messages and mapping them to the Unified Data Model (UDM).\u003c/p\u003e\n"],["\u003cp\u003eTo begin, ensure you have a Google SecOps instance, a compatible operating system (Windows 2016 or later, or Linux with \u003ccode\u003esystemd\u003c/code\u003e), and the required network ports open if using a proxy, as well as privileged access to the Aruba Wireless Controller.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves obtaining a Google SecOps ingestion authentication file and customer ID, installing the Bindplane agent on Windows or Linux, configuring the Bindplane agent to receive Syslog and send to Google SecOps, and setting up the Aruba Wireless Controller to forward logs.\u003c/p\u003e\n"],["\u003cp\u003eThe UDM mapping table outlines how various fields from the Aruba logs, such as \u003ccode\u003eAP\u003c/code\u003e, \u003ccode\u003eBSSID\u003c/code\u003e, and \u003ccode\u003eUSER\u003c/code\u003e, are translated to specific UDM fields like \u003ccode\u003etarget.hostname\u003c/code\u003e, \u003ccode\u003etarget.mac\u003c/code\u003e, and \u003ccode\u003etarget.user.userid\u003c/code\u003e, respectively, enabling detailed analysis within Google SecOps.\u003c/p\u003e\n"],["\u003cp\u003eThe document includes a change log with enhancements and bug fixes, such as adding support for new syslog log patterns and handling unparsed SYSLOG logs, as well as directing users to a community forum for further assistance.\u003c/p\u003e\n"]]],[],null,["# Collect Aruba Wireless Controller and Access Point 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 collect Aruba Wireless Controller and Access Point logs by using Bindplane. The parser processes SYSLOG messages, extracting fields related to observer, intermediary, and access point details. It then maps these fields to the Unified Data Model (UDM), enriching the event data with security result severity and handling various error conditions during the process.\n\nBefore you begin\n----------------\n\n- Ensure that you have a Google Security Operations instance.\n- Ensure that you are using Windows 2016 or later, or a Linux host with `systemd`.\n- If running behind a proxy, ensure firewall [ports](/chronicle/docs/ingestion/use-bindplane-agent#verify_the_firewall_configuration) are open.\n- Ensure that you have privileged access to an Aruba Wireless Controller.\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\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\n- For additional installation options, consult this [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\n 1. Locate the `config.yaml` file. Typically, it's in the `/etc/bindplane-agent/` directory on Linux or in the installation directory on Windows.\n 2. 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: '/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 ingestion_labels:\n log_type: ARUBA_WIRELESS\n raw_log_field: body\n\n service:\n pipelines:\n logs/source0__chronicle_w_labels-0:\n receivers:\n - udplog\n exporters:\n - chronicle/chronicle_w_labels\n\n3. Replace the port and IP address as required in your infrastructure.\n\n4. Replace `\u003ccustomer_id\u003e` with the actual customer ID.\n\n5. Update `/path/to/ingestion-authentication-file.json` to the path where the authentication file was saved in the\n [Get Google SecOps ingestion authentication file](/chronicle/docs/ingestion/default-parsers/aruba-wc#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** console or enter the following command:\n\n net stop BindPlaneAgent && net start BindPlaneAgent\n\nConfigure Aruba Wireless Controller and Access Point\n----------------------------------------------------\n\n1. Sign in to the Aruba controller web UI.\n2. Go to the top menu and select **Configuration \\\u003e System**.\n3. Select **Logging** to open the logging configuration page.\n4. In the **Syslog servers** section, click **+ Add** to add a new syslog server.\n5. A new form will appear where you need to enter the following details:\n - **Name** : enter a unique name for the syslog server; for example, `Google SecOps Syslog`.\n - **IP Address**: enter the Bindplane IP address.\n - **Port**: enter the Bindplane port number (typically 514 for UDP).\n - **Logging Facility** : select **local 6** from the menu (this is commonly used for network devices).\n - **Logging Level** : select **Informational** to capture information logs.\n - **Format** : select **bsd-standard** format (this is the default syslog format used by Aruba controllers).\n6. Click **Submit** to save your settings.\n7. Click **Pending Changes**.\n8. Click **Deploy Changes** to apply the new syslog server configuration.\n\n | **Note:** After deploying the changes, you'll need to configure the logging level for specific categories of logs.\n9. Go to the **Logging Level** settings and set the **Logging Level** to **Informational** for each of the following categories:\n\n - Network\n - All\n - Cluster\n - DHCP\n - GP\n - Mobility\n - Packet-Dump\n - SDN\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)"]]
