이 문서에서는 IBM Verify Identity Access 로그를 수집하는 방법을 설명합니다.
파서는 Grok 패턴을 사용하여 공통 필드를 추출하고 설명 필드에 삽입된 자세한 이벤트 정보에 XML 파싱을 활용하여 추출된 데이터를 표준화된 보안 이벤트 표현을 위한 통합 데이터 모델 (UDM)에 매핑합니다.
Syslog를 수집하여 Google SecOps로 전송하도록 Bindplane 에이전트 구성
구성 파일에 액세스합니다.
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_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:'IBM_SVA'raw_log_field:bodyingestion_labels:service:pipelines:logs/source0__chronicle_w_labels-0:receivers:-udplogexporters:-chronicle/chronicle_w_labels
[[["이해하기 쉬움","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(UTC)"],[[["\u003cp\u003eThis guide explains how to collect IBM Security Verify Access (ISVA) logs and ingest them into Google Security Operations (SecOps) using Bindplane Agent.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves setting up Bindplane Agent on Windows or Linux, configuring it to receive Syslog data, and forwarding that data to Google SecOps using an authentication file and a customer ID.\u003c/p\u003e\n"],["\u003cp\u003eISVA configuration includes setting the log format in the WebSEAL configuration file and enabling remote Syslog forwarding, specifying the Bindplane server details and log sources.\u003c/p\u003e\n"],["\u003cp\u003eThe parser provided will analyze log fields using Grok patterns and XML parsing, converting them into the unified data model (UDM) for normalized representation within SecOps.\u003c/p\u003e\n"],["\u003cp\u003eThis document details how the collected data from ISVA is mapped to the UDM, covering fields such as timestamps, hostnames, user information, and security event details.\u003c/p\u003e\n"]]],[],null,["Collect IBM Verify Identity Access logs \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 describes how to collect IBM Verify Identity Access logs.\nThe parser extracts common fields using Grok patterns and leverages XML\nparsing for detailed event information embedded within the description field,\nultimately mapping extracted data to the Unified Data Model (UDM) for\nstandardized security event representation.\n\nBefore you begin\n\nMake sure you have the following prerequisites:\n\n- Google SecOps instance\n- 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 IBM Verify Identity Access (IVIA)\n\nGet Google SecOps ingestion authentication file\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\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\nInstall the Bindplane agent on your Windows or Linux operating system according to the following instructions.\n\nWindows 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\nLinux 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\nAdditional installation resources\n\nFor additional installation options, consult the [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\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: 'IBM_SVA'\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/ibm-sva#get-auth-file) section.\n\nRestart the Bindplane agent to apply the changes\n\n1. To restart the Bindplane agent in **Linux**, run the following command:\n\n sudo systemctl restart bindplane-agent\n\n2. 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 Syslog Forwarding in IVIA\n\n1. Sign in to **IBM Security Verify Governance**.\n2. Go to **Monitor \\\u003e Logs \\\u003e Remote Syslog Forwarding**.\n3. In the **Remote Syslog Forwarding** page, click **Add**.\n4. Provide the following configuration details:\n - **Server**: Enter the Bindplane agent IP address.\n - **Port**: Enter the Bindplane agent port number.\n - **Protocol** : Select **UDP** (the other possible option is **TCP**, depending on your Bindplane agent configuration).\n - Format: Select the format (BSD Syslog Protocol or Syslog Protocol) in which you want to send the system logs.\n5. Click **Save Configuration**.\n\nConfigure Log Sources for the remote log server\n\n1. In the **Remote Syslog Forwarding** page, click the **Sources** tab.\n2. Provide the following configuration details:\n - **Name**: Select a log source from the drop-down list.\n - **Instance Name** : The option is only available if you select Name as **IsimNode**.\n - **Log File** : When you select Name as **IsimNodes** , **Install logs** , or **IsimDmgr** then the respective logs file is automatically shown in the drop-down.\n - **Tag** : This tag name must be unique across all the sources, and must not contain any space (for example: `My_Tag` or `MyTag`).\n - **Facility**: Select a category name for the system log to be forwarded.\n - **Severity** : Select **Informational**.\n3. Click **Save Configuration**.\n\n| **Note:** You can configure multiple sources in the same way.\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
