이 문서에서는 Bindplane을 사용하여 Trellix (이전 McAfee) IPS (침입 방지 시스템) Network Security Manager 로그를 Google Security Operations에 수집하는 방법을 설명합니다. 파서는 McAfee IPS syslog 메시지에서 보안 이벤트 데이터를 추출합니다.
일련의 그록 패턴을 사용하여 소스 및 대상 IP, 포트, 프로토콜, 공격 세부정보, 심각도와 같은 필드를 식별하고 매핑하여 정보를 Google SecOps 통합 데이터 모델 (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 organizationingestion_labels:log_type:'MCAFEE_IPS'raw_log_field:bodyservice:pipelines:logs/source0__chronicle_w_labels-0:receivers:-udplogexporters:-chronicle/chronicle_w_labels
protocol 필드가 HTTP, SSL 또는 TCP인 경우 TCP로 설정합니다. protocol 필드가 ICMP이면 ICMP로 설정합니다. protocol 필드가 SNMP이고 alert_message 필드에 Empty UDP Attack DoS이 포함된 경우 UDP로 설정합니다.
read_only_udm.security_result.action
result 필드가 Attack Blocked, Attack Failed 또는 Attack SmartBlocked인 경우 BLOCK로 설정합니다. result 필드가 Attack Successful이면 ALLOW로 설정합니다. result 필드가 Inconclusive이면 UNKNOWN_ACTION로 설정합니다. alert_message 필드가 정규 표현식 File Submitted .*? for Analysis와 일치하면 QUARANTINE로 설정됩니다.
read_only_udm.security_result.category
alert_message 필드를 기준으로 분류됩니다. result 필드가 n/a이면 NETWORK_SUSPICIOUS로 설정됩니다.
read_only_udm.security_result.description
result 필드가 n/a이 아닌 경우 (result)로 설정된 _result 변수의 값과 연결된 alert_message 필드
[[["이해하기 쉬움","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 Trellix IPS 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 Trellix (formerly McAfee) IPS (Intrusion\nPrevention System) Network Security Manager logs to Google Security Operations using\nBindplane. The parser extracts security event data from McAfee IPS syslog messages.\nIt uses a series of grok patterns to identify and map fields like source and\ndestination IP, port, protocol, attack details, and severity,\nstructuring the information into the Google SecOps Unified Data\nModel (UDM).\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, firewall [ports](/chronicle/docs/ingestion/use-bindplane-agent#verify_the_firewall_configuration) are open\n- Privileged access to McAfee Network Security Platform Manager\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 ingestion_labels:\n log_type: 'MCAFEE_IPS'\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\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/trellix-ips#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 McAfee Network Security Platform Manager Syslog\n---------------------------------------------------------\n\n1. Sign in to the **McAfee Network Security Platform Manager** interface.\n2. Click **Configure \\\u003e Resource Tree \\\u003e IPS Settings**.\n3. Click the **Alert Notification tab \\\u003e Syslog tab**.\n4. Provide the following configuration details:\n - Select **Yes** to **enable syslog notifications** for McAfee Network Security Platform.\n - **Admin Domain** : Select the **Current** checkbox to send syslog notifications for alerts in the current domain.\n - **Server Name or IP Address**: Enter the Bindplane agent IP address.\n - **UDP Port** : Enter the port `514`.\n - **Facility** : Select syslog facility value `local0`.\n - **Severity** : Select **informational**.\n - **Send Notification If** : Select **all** the options to always receive syslog\n - **IPS Quarantine Alert Notification** : Select **No**.\n5. Click **Save**.\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)"]]
