이 문서에서는 Bindplane을 사용하여 CyberArk Privileged Threat Analytics 로그를 수집하는 방법을 설명합니다. CyberArk Privileged Threat Analytics는 권한이 있는 계정과 관련된 악성 활동을 감지하고 대응하는 데 도움이 되는 보안 솔루션입니다. 고급 분석 및 머신러닝을 사용하여 잠재적인 내부자 위협이나 도용된 사용자 인증 정보를 나타낼 수 있는 비정상적인 행동을 모니터링, 분석, 표시합니다.
시작하기 전에
Google Security Operations 인스턴스가 있는지 확인합니다.
Windows 2016 이상 또는 systemd가 설치된 Linux 호스트를 사용하고 있는지 확인합니다.
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:'/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:SYSLOGnamespace:cyberark_ptaraw_log_field:bodyservice: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 outlines the process of collecting CyberArk Privileged Threat Analytics logs for ingestion into Google Security Operations (SecOps) using the Bindplane agent.\u003c/p\u003e\n"],["\u003cp\u003eThe Bindplane agent installation process is detailed for both Windows and Linux environments, with specific commands provided for each operating system.\u003c/p\u003e\n"],["\u003cp\u003eConfiguration of the Bindplane agent requires modifying the \u003ccode\u003econfig.yaml\u003c/code\u003e file to set up the \u003ccode\u003eudplog\u003c/code\u003e receiver and the \u003ccode\u003echronicle\u003c/code\u003e exporter, including providing the ingestion authentication file and customer ID.\u003c/p\u003e\n"],["\u003cp\u003eThe guide explains how to configure CyberArk Privileged Threat Analytics to export logs to the Bindplane agent by modifying the \u003ccode\u003esystemparm.properties\u003c/code\u003e file with the necessary syslog parameters, such as IP address, port, and protocol.\u003c/p\u003e\n"],["\u003cp\u003eUsers are reminded that this feature is considered a Pre-GA offering and thus may have limited support and compatibility, according to the terms described.\u003c/p\u003e\n"]]],[],null,["# Collect CyberArk Privileged Threat Analytics 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 CyberArk Privileged Threat Analytics logs by using Bindplane. CyberArk Privileged Threat Analytics is a security solution that helps to detect and respond to malicious activities involving privileged accounts. It uses advanced analytics and machine learning to monitor, analyze, and flag abnormal behaviors that may indicate potential insider threats or compromised credentials.\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 Cyberark PTA.\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: SYSLOG\n namespace: cyberark_pta\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/cyberark-pta#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 CyberArk Privileged Threat Analytics log export\n---------------------------------------------------------\n\n1. Sign in to the **Privileged Threat Analytics** machine.\n2. Run the **DEFAULTPARM** command to open the default `systemparm.properties` file.\n3. Copy the line containing the `syslog_outbound` property and exit the `systemparm.properties` file.\n4. Run the **LOCALPARM** command to open the local `systemparm.properties` file.\n5. Press `i` on the keyboard to edit the file.\n6. In the `systemparm.properties` file, uncomment the `syslog_outbound` property.\n7. Paste the line that you copied earlier and edit the parameters according to the following example:\n\n syslog_outbound=[{\"siem\": \"Chronicle\", \"format\": \"CEF\", \"host\": \"\u003cvar translate=\"no\"\u003eBINDPLANE_IP_ADDRESS\u003c/var\u003e\", \"port\": \u003cvar translate=\"no\"\u003eBINDPLANE_PORT_NUMBER\u003c/var\u003e, \"protocol\": \"\u003cvar translate=\"no\"\u003ePROTOCOL\u003c/var\u003e\"}]\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eBINDPLANE_IP_ADDRESS\u003c/var\u003e: enter the Bindplane IP address.\n - \u003cvar translate=\"no\"\u003ePORT_NUMBER\u003c/var\u003e: enter the Bindplane port number (for example, **514**).\n - \u003cvar translate=\"no\"\u003ePROTOCOL\u003c/var\u003e: Enter **UDP** as the protocol.\n8. Save the configuration file and close it.\n\n9. Restart the **Privileged Threat Analytics** machine.\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
