Dokumen ini menjelaskan cara menyerap log audit 1Password ke Google Security Operations menggunakan BindPlane. Parser mengubah data log berformat JSON mentah menjadi format terstruktur yang sesuai dengan Model Data Terpadu (UDM) Google SecOps. Fitur ini secara khusus berfokus pada menormalisasi dan memperkaya peristiwa yang terkait dengan upaya login pengguna, mengekstrak detail tentang pengguna, lokasi, informasi klien, dan hasil upaya tersebut.
Sebelum memulai
Pastikan Anda memiliki prasyarat berikut:
Instance Google SecOps
Windows 2016 atau yang lebih baru atau host Linux dengan systemd
Jika dijalankan di belakang proxy, port firewall terbuka
Akses istimewa ke 1Password
Mendapatkan file autentikasi penyerapan Google SecOps
Login ke konsol Google SecOps.
Buka Setelan SIEM > Agen Pengumpulan.
Download File Autentikasi Penyerapan. Simpan file dengan aman di sistem tempat BindPlane akan diinstal.
Mendapatkan ID pelanggan Google SecOps
Login ke konsol Google SecOps.
Buka Setelan SIEM > Profil.
Salin dan simpan ID Pelanggan dari bagian Detail Organisasi.
Menginstal agen Bindplane
Penginstalan Windows
Buka Command Prompt atau PowerShell sebagai administrator.
Mengonfigurasi agen BindPlane untuk menyerap Syslog dan mengirimkannya ke Google SecOps
Akses file konfigurasi:
Cari file config.yaml. Biasanya, file ini berada di direktori /etc/bindplane-agent/ di Linux atau di direktori penginstalan di Windows.
Buka file menggunakan editor teks (misalnya, nano, vi, atau Notepad).
Edit file config.yaml sebagai berikut:
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:'ONEPASSWORD_AUDIT_EVENTS'raw_log_field:bodyservice:pipelines:logs/source0__chronicle_w_labels-0:receivers:-udplogexporters:-chronicle/chronicle_w_labels
Ganti port dan alamat IP sesuai kebutuhan di infrastruktur Anda.
Ganti <customer_id> dengan ID pelanggan yang sebenarnya.
Mulai ulang agen Bindplane untuk menerapkan perubahan
Untuk memulai ulang agen Bindplane di Linux, jalankan perintah berikut:
sudosystemctlrestartbindplane-agent
Untuk memulai ulang agen Bindplane di Windows, Anda dapat menggunakan konsol Services atau memasukkan perintah berikut:
net stop BindPlaneAgent && net start BindPlaneAgent
Mendapatkan token API 1Password
Login ke UI web 1Password.
Buka Integrations.
Klik Direktori di bagian atas halaman.
Masukkan nama untuk token dan tetapkan masa berlaku token.
Di Pelaporan Peristiwa, klik Lainnya.
Pilih Peristiwa audit dari Jenis Peristiwa.
Klik Issue Token untuk membuat kunci token akses.
Klik Save in 1Password dan pilih brankas tempat Anda ingin menyimpan token.
Klik Lihat Detail Integrasi untuk melihat token.
Konfigurasi host Linux untuk menjalankan perintah berikut
Jalankan perintah berikut:
import datetime
import requests
import os
import socket
import json
# For more information, check out the support page: https://support.1password.com/events-reporting
api_token = os.environ.get('EVENTS_API_TOKEN')
url = "https://events.1password.com"
if not api_token:
print("Please set the EVENTS_API_TOKEN environment variable.")
exit(1)
start_time = datetime.datetime.now() - datetime.timedelta(hours=24)
# Define the bindplane agent details
syslog_server_ip = <ip-address> # Replace with your Bindplane IP
syslog_server_port = <port-number> # Replace with your Bindplane port
headers = {
"Content-Type": "application/json",
"Authorization": f"Bearer {api_token}"
payload = {
"limit": 20,
"start_time": start_time.astimezone().replace(microsecond=0).isoformat()
# Alternatively, use the cursor returned from previous responses to get any new events
# payload = { "cursor": cursor }
try:
r = requests.post(f"{url}/api/v1/signinattempts", headers=headers, json=payload)
r.raise_for_status() # Raise an exception if the request fails
if r.status_code == requests.codes.ok:
# Send the response to the bindplane server
syslog_message = f"{json.dumps(r.json())}"
with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as sock:
sock.connect((syslog_server_ip, syslog_server_port))
sock.sendall(f"{syslog_message}\n".encode())
else:
print(f"Error getting sign-in attempts: status code {r.status_code}")
except requests.exceptions.RequestException as e:
print(f"Request error: {e}")
except Exception as e:
print(f"Error during syslog logging: {e}")
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[],[],null,["# Collect 1Password audit 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 1Password audit logs to Google Security Operations\nusing Bindplane. The parser transforms raw JSON formatted log data into a\nstructured format compliant with the Google SecOps Unified Data\nModel (UDM). It specifically focuses on normalizing and enriching events related\nto user sign-in attempts, extracting details about the user, their location,\nclient information, and the outcome of the attempt.\n\nBefore you begin\n----------------\n\nEnsure that you have the following prerequisites:\n\n- Google SecOps instance\n- Windows 2016 or later or 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 1Password\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\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: '/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: 'ONEPASSWORD_AUDIT_EVENTS'\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 [Get Google SecOps ingestion authentication file](/chronicle/docs/ingestion/default-parsers/onepassword-audit-events#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\nGet the 1Password API token\n---------------------------\n\n1. Sign in to the **1Password** web UI.\n2. Go to **Integrations**.\n3. Click **Directory** at the top of the page.\n4. Enter a name for the **token** and set the token **expiration**.\n5. In **Events Reporting** , click **Other**.\n6. Select **Audit events** from **Event Types**.\n7. Click **Issue Token** to generate the access token key.\n8. Click **Save in 1Password** and select which vault to save your token to.\n9. Click **View Integration Details** to view the token.\n\nConfigure a Linux host to run the following command\n---------------------------------------------------\n\n- Run the following command:\n\n import datetime\n import requests\n import os \n import socket \n import json\n\n # For more information, check out the support page: https://support.1password.com/events-reporting\n\n api_token = os.environ.get('EVENTS_API_TOKEN')\n url = \"https://events.1password.com\"\n if not api_token:\n print(\"Please set the EVENTS_API_TOKEN environment variable.\")\n exit(1)\n start_time = datetime.datetime.now() - datetime.timedelta(hours=24)\n\n # Define the bindplane agent details\n\n syslog_server_ip = \u003cip-address\u003e # Replace with your Bindplane IP\n syslog_server_port = \u003cport-number\u003e # Replace with your Bindplane port\n headers = {\n \"Content-Type\": \"application/json\",\n \"Authorization\": f\"Bearer {api_token}\"\n payload = {\n \"limit\": 20,\n \"start_time\": start_time.astimezone().replace(microsecond=0).isoformat()\n\n # Alternatively, use the cursor returned from previous responses to get any new events\n # payload = { \"cursor\": cursor }\n try:\n r = requests.post(f\"{url}/api/v1/signinattempts\", headers=headers, json=payload)\n r.raise_for_status() # Raise an exception if the request fails\n if r.status_code == requests.codes.ok:\n\n # Send the response to the bindplane server\n syslog_message = f\"{json.dumps(r.json())}\"\n with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as sock:\n sock.connect((syslog_server_ip, syslog_server_port))\n sock.sendall(f\"{syslog_message}\\n\".encode())\n else:\n print(f\"Error getting sign-in attempts: status code {r.status_code}\")\n except requests.exceptions.RequestException as e:\n print(f\"Request error: {e}\")\n except Exception as e:\n print(f\"Error during syslog logging: {e}\")\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
