Questo documento spiega come importare i log di FileZilla in Google Security Operations
utilizzando Bindplane. Il codice del parser Logstash estrae i campi pertinenti, come
timestamp, nomi host, ID utente e descrizioni dai log del server FTP FileZilla.
Quindi, struttura questi campi estratti in un modello Unified Data Model (UDM) per
un'analisi e una correlazione della sicurezza coerenti.
Prima di iniziare
Assicurati di soddisfare i seguenti prerequisiti:
Istanza Google SecOps
Windows 2016 o versioni successive oppure un host Linux con systemd
Se l'esecuzione avviene tramite un proxy, le porte del firewall sono aperte
Accesso con privilegi a un'istanza di FileZilla Server
Recuperare il file di autenticazione importazione di Google SecOps
Accedi alla console Google SecOps.
Vai a Impostazioni SIEM > Agenti di raccolta.
Scarica il file di autenticazione importazione. Salva il file in modo sicuro sul
sistema in cui verrà installato Bindplane.
Recuperare l'ID cliente Google SecOps
Accedi alla console Google SecOps.
Vai a Impostazioni SIEM > Profilo.
Copia e salva l'ID cliente dalla sezione Dettagli dell'organizzazione.
Installa l'agente Bindplane sull'istanza di FileZilla Server
Installa l'agente Bindplane sul sistema operativo Windows o Linux
seguendo le istruzioni riportate di seguito.
Installazione di Windows
Apri il prompt dei comandi o PowerShell come amministratore.
Configura l'agente Bindplane per importare Syslog e inviarli a Google SecOps
Accedi al file di configurazione:
Individua il file config.yaml. In genere, si trova nella directory /etc/bindplane-agent/ su Linux o nella directory di installazione su Windows.
Apri il file utilizzando un editor di testo (ad esempio nano, vi o Blocco note).
Modifica il file config.yaml come segue:
receivers:filelog:# Adjust the path to the log filefile_path:<PATH_TO>/filezilla-logs.loglog_type:'file'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:'FILEZILLA_FTP'raw_log_field:bodyservice:pipelines:logs/source0__chronicle_w_labels-0:receivers:-filelogexporters:-chronicle/chronicle_w_labels
Sostituisci la porta e l'indirizzo IP in base alle esigenze della tua infrastruttura.
Sostituisci <customer_id> con l'ID cliente effettivo.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-10 UTC."],[],[],null,["Collect FileZilla FTP 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 explains how to ingest FileZilla logs to Google Security Operations\nusing Bindplane. The Logstash parser code extracts relevant fields like\ntimestamps, hostnames, user IDs, and descriptions from FileZilla FTP server logs.\nIt then structures these extracted fields into a Unified Data Model (UDM) for\nconsistent security analysis and correlation.\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 an instance of FileZilla Server\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 on FileZilla Server instance\n\nInstall the Bindplane agent on your Windows or Linux operating system according\nto 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 filelog:\n # Adjust the path to the log file\n file_path: \u003cPATH_TO\u003e/filezilla-logs.log\n log_type: 'file'\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: 'FILEZILLA_FTP'\n raw_log_field: body\n\n service:\n pipelines:\n logs/source0__chronicle_w_labels-0:\n receivers:\n - filelog\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/filezilla-ftp#get-auth-file) section.\n\nRestart the Bindplane agent to apply the changes\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 logging in FileZilla\n\n1. Sign in to the server with **FileZilla**.\n2. Open the FileZilla software.\n3. Go to **Edit \\\u003e Settings**.\n4. Select **Logging** from the menu.\n5. Provide the following configuration details:\n - Select the checkbox **Show timestamps in messagebox**.\n - Select the checkbox **Log to file**.\n - **Filename** : Enter a filename and select the storage path (for example, `filezilla-logs`).\n - Optional: **Limit size of logfile**: Select this checkbox to limit the amount of space a log file can use.\n - Optional: **Limit**: You can enter a max file size for your log file here in Megabytes.\n6. Click **OK**.\n7. Restart FileZilla.\n\nUDM mapping table\n\n| Log field | UDM mapping | Logic |\n|-----------|------------------------------------------------|-------------------------------------------------------------------------------------------------|\n| data | read_only_udm.metadata.description | The raw log `data` field content. |\n| data | read_only_udm.metadata.event_timestamp.seconds | Extracted from the `data` field using a grok pattern and converted to epoch seconds. |\n| data | read_only_udm.network.http.response_code | Extracted from the `data` field using a grok pattern. |\n| data | read_only_udm.principal.hostname | Extracted from the `data` field using a grok pattern. |\n| data | read_only_udm.principal.port | Extracted from the `data` field using a grok pattern. |\n| data | read_only_udm.principal.user.userid | Extracted from the `data` field using a grok pattern, only if the value is not `not logged in`. |\n| data | read_only_udm.target.ip | Extracted from the `data` field using a grok pattern. |\n| data | read_only_udm.target.process.pid | Extracted from the `data` field using a grok pattern. |\n| | read_only_udm.metadata.event_type | Set to `NETWORK_FTP` if target.ip exists, otherwise set to `GENERIC_EVENT`. |\n| | read_only_udm.metadata.log_type | Set to `FILEZILLA_FTP`. |\n| | read_only_udm.metadata.product_name | Set to `FILEZILLA`. |\n| | read_only_udm.metadata.vendor_name | Set to `FILEZILLA`. |\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]