이 문서에서는 Bindplane을 사용하여 Cloudian HyperStore 로그를 Google Security Operations에 수집하는 방법을 설명합니다. 파서는 먼저 일련의 grok 패턴을 사용하여 SYSLOG 메시지에서 타임스탬프, IP 주소, 사용자 이름, 설명과 같은 관련 필드를 추출합니다. 그런 다음 추출된 필드를 통합 데이터 모델 (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:'CLOUDIAN_HYPERSTORE'raw_log_field:bodyingestion_labels:service:pipelines:logs/source0__chronicle_w_labels-0:receivers:-udplogexporters:-chronicle/chronicle_w_labels
Windows에서 Bindplane 에이전트를 다시 시작하려면 서비스 콘솔을 사용하거나 다음 명령어를 입력하면 됩니다.
net stop BindPlaneAgent && net start BindPlaneAgent
Cloudian Hyperstore Syslog 구성
CLI를 사용하여 HyperStore 구성 컨트롤러 노드에 로그인합니다.
다음 hsctl 명령어를 실행합니다.
# hsctl config set logging.syslog.remote.enabled=true# hsctl config set logging.syslog.remote.host=<Bindplane Agent IP Address># hsctl config set logging.syslog.remote.protocol=<UDP or TCP protocol># hsctl config set logging.syslog.remote.port=<Bindplane Agent port number># hsctl config apply ALL# hsctl service restart s3 iam hyperstore firewall --nodes=ALL# hsctl config set monitoring.agent.logging.level=INFO# hsctl config apply monitoring
다음을 바꿉니다.
<Bindplane Agent IP Address>를 실제 Bindplane 에이전트 IP 주소로 바꿉니다.
<UDP or TCP protocol>를 사용합니다.
<Bindplane Agent port number>를 실제 Bindplane 에이전트 포트 번호로 바꿉니다.
[[["이해하기 쉬움","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)"],[],[],null,["# Collect Cloudian HyperStore 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 Cloudian HyperStore logs to Google Security Operations using Bindplane. The parser first uses a series of `grok` patterns to extract relevant fields like timestamps, IP addresses, user names, and descriptions from the SYSLOG messages. Then, it maps those extracted fields to the corresponding fields in the unified data model (UDM) and sets the appropriate event type based on the identified activity.\n\nBefore you begin\n----------------\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, ensure firewall [ports](/chronicle/docs/ingestion/use-bindplane-agent#verify_the_firewall_configuration) are open\n- Privileged access to the Cloudian HyperStore\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 [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: 'CLOUDIAN_HYPERSTORE'\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/cloudian-hs#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\n **Services** console or enter the following command:\n\n net stop BindPlaneAgent && net start BindPlaneAgent\n\nConfigure Cloudian Hyperstore Syslog\n------------------------------------\n\n1. Sign in to your HyperStore Config Controller node using CLI.\n2. Run the following hsctl commands:\n\n # hsctl config set logging.syslog.remote.enabled=true\n # hsctl config set logging.syslog.remote.host=\u003cBindplane Agent IP Address\u003e\n # hsctl config set logging.syslog.remote.protocol=\u003cUDP or TCP protocol\u003e\n # hsctl config set logging.syslog.remote.port=\u003cBindplane Agent port number\u003e\n # hsctl config apply ALL\n # hsctl service restart s3 iam hyperstore firewall --nodes=ALL\n # hsctl config set monitoring.agent.logging.level=INFO\n # hsctl config apply monitoring\n\n3. Replace the following:\n\n - `\u003cBindplane Agent IP Address\u003e` with your actual Bindplane agent IP Address.\n - `\u003cUDP or TCP protocol\u003e` with the protocol configured in the Bindplane agent.\n - `\u003cBindplane Agent port number\u003e` with your actual Bindplane agent port number.\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
