Mengumpulkan log SAP BTP

Didukung di:

Dokumen ini menjelaskan cara menyerap log SAP Business Technology Platform (BTP) ke Google Security Operations menggunakan Cloud Storage V2.

SAP Business Technology Platform (BTP) adalah platform cloud yang menyediakan kemampuan pengembangan aplikasi, integrasi, pengelolaan data, dan analisis. Layanan ini menghasilkan log audit keamanan, log akses, dan log peristiwa layanan yang penting untuk memantau aktivitas platform dan mendeteksi ancaman keamanan. Fungsi Cloud Run melakukan polling pada API pengambilan log audit dari Layanan Pengelolaan Log Audit SAP sesuai jadwal, menulis log ke bucket Cloud Storage dalam format NDJSON, dan Google SecOps menyerapnya melalui feed Cloud Storage V2.

Sebelum memulai

Pastikan Anda memiliki prasyarat berikut:

  • Instance Google SecOps
  • Project Google Cloud dengan Cloud Storage API diaktifkan
  • Izin untuk membuat dan mengelola bucket Cloud Storage
  • Izin untuk mengelola kebijakan Identity and Access Management (IAM) di bucket Cloud Storage
  • Izin untuk membuat layanan Cloud Run, topik Pub/Sub, dan tugas Cloud Scheduler
  • Akses administrator ke SAP BTP dengan izin untuk mengonfigurasi pengambilan log audit (Space Developer di ruang Cloud Foundry target, dan kemampuan untuk menambahkan hak di tingkat akun global)
  • Layanan Pengelolaan Log Audit (nama teknis: auditlog-management) yang berhak atas sub-akun SAP BTP Anda

Membuat bucket Cloud Storage

  1. Buka Konsol Google Cloud.
  2. Pilih project Anda atau buat project baru.
  3. Di menu navigasi, buka Cloud Storage > Buckets.
  4. Klik Create bucket.
  5. Berikan detail konfigurasi berikut:

    Setelan Nilai
    Memberi nama bucket Anda Masukkan nama yang unik secara global (misalnya, sap-btp-logs)
    Location type Pilih sesuai kebutuhan Anda (Region, Dual-region, Multi-region)
    Location Pilih lokasi (misalnya, us-central1)
    Storage class Standard (direkomendasikan untuk log yang sering diakses)
    Kontrol akses Seragam (direkomendasikan)
    Alat perlindungan Opsional: Mengaktifkan pembuatan versi objek atau kebijakan retensi
  6. Klik Create.

Mengumpulkan kredensial SAP BTP API

Membuat instance Layanan Pengelolaan Log Audit

  1. Login ke SAP BTP Cockpit.
  2. Pastikan hak Audit Log Management Service ditetapkan ke sub-akun: di tampilan sub-akun, buka Entitlements > Edit > Add Service Plans (hak dialokasikan dari akun global).
  3. Buka sub-akun Anda.
  4. Buka Services > Instances and Subscriptions.
  5. Klik Create.
  6. Berikan detail konfigurasi berikut:
    • Layanan: Pilih Layanan Pengelolaan Log Audit (nama teknis: auditlog-management).
    • Plan: Pilih default.
    • Runtime Environment: Pilih Cloud Foundry.
    • Ruang: Pilih ruang target.
    • Instance Name: Masukkan nama (misalnya, auditlog-management-secops).
  7. Klik Create.

Membuat kunci layanan

  1. Di SAP BTP Cockpit, buka Services > Instances and Subscriptions, lalu pilih instance layanan auditlog-management.
  2. Pilih Create Service Key.
  3. Masukkan nama (misalnya, google-secops-integration).
  4. Klik Create.
  5. Salin dan simpan detail berikut dari kunci layanan di lokasi yang aman:

    • url: URL dasar untuk permintaan pengambilan log audit.
    • uaa.url: URL dasar server OAuth. Endpoint token adalah <uaa.url>/oauth/token.
    • uaa.clientid: Client ID OAuth.
    • uaa.clientsecret: Rahasia klien OAuth.

Menguji akses API

  • Uji kredensial Anda sebelum melanjutkan integrasi:

    # Replace with your actual credentials from the service key
    UAA_URL="https://your-subdomain.authentication.region.hana.ondemand.com"
    CLIENT_ID="your-client-id"
    CLIENT_SECRET="your-client-secret"
    API_URL="https://auditlog-management.cfapps.us10.hana.ondemand.com"
    
    # Get OAuth token
    TOKEN=$(curl -s -X POST "${UAA_URL}/oauth/token" \
      -u "${CLIENT_ID}:${CLIENT_SECRET}" \
      -d "grant_type=client_credentials" \
      -H "Content-Type: application/x-www-form-urlencoded" | jq -r '.access_token')
    
    # Test API access: the API takes time_from/time_to in UTC without a
    # timezone suffix and returns a JSON array at the root. When the result
    # set is chunked, the next chunk's handle arrives in the "Paging"
    # response header.
    curl -v -H "Authorization: Bearer ${TOKEN}" \
      "${API_URL}/auditlog/v2/auditlogrecords?time_from=2026-08-07T00:00:00&time_to=2026-08-07T01:00:00"
    

Membuat akun layanan untuk fungsi Cloud Run

Fungsi Cloud Run memerlukan akun layanan dengan izin untuk menulis ke bucket Cloud Storage dan dipanggil oleh Pub/Sub.

Membuat akun layanan

  1. Di Konsol GCP, buka IAM & Admin > Service Accounts.
  2. Klik Create Service Account.
  3. Berikan detail konfigurasi berikut:
    • Service account name: Masukkan sap-btp-collector-sa.
    • Service account description: Masukkan Service account for Cloud Run function to collect SAP BTP logs.
  4. Klik Create and Continue.
  5. Di bagian Grant this service account access to project, tambahkan peran berikut:
    1. Klik Pilih peran.
    2. Telusuri dan pilih Storage Object Admin.
    3. Klik + Add another role.
    4. Telusuri dan pilih Cloud Run Invoker.
    5. Klik + Add another role.
    6. Telusuri dan pilih Cloud Functions Invoker.
  6. Klik Lanjutkan.
  7. Klik Done.

Peran ini diperlukan untuk:

  • Storage Object Admin: Menulis log ke bucket Cloud Storage dan mengelola state file
  • Cloud Run Invoker: Mengizinkan Pub/Sub memanggil fungsi
  • Cloud Functions Invoker: Mengizinkan pemanggilan fungsi

Memberikan izin IAM pada bucket Cloud Storage

Beri akun layanan izin tulis di bucket Cloud Storage:

  1. Buka Cloud Storage > Buckets.
  2. Klik nama bucket Anda (misalnya, sap-btp-logs).
  3. Buka tab Izin.
  4. Klik Grant access.
  5. Berikan detail konfigurasi berikut:
    • Tambahkan entitas: Masukkan email akun layanan (misalnya, sap-btp-collector-sa@your-project.iam.gserviceaccount.com).
    • Assign roles: Pilih Storage Object Admin.
  6. Klik Simpan.

Membuat topik Pub/Sub

Buat topik Pub/Sub yang akan dipublikasikan oleh Cloud Scheduler dan di-subscribe oleh fungsi Cloud Run.

  1. Di Konsol GCP, buka Pub/Sub > Topics.
  2. Klik Create topic.
  3. Berikan detail konfigurasi berikut:
    • ID Topik: Masukkan sap-btp-trigger.
    • Biarkan setelan lainnya sesuai default.
  4. Klik Create.

Membuat fungsi Cloud Run untuk mengumpulkan log

Fungsi Cloud Run akan dipicu oleh pesan Pub/Sub dari Cloud Scheduler untuk mengambil log audit dari API pengambilan Layanan Pengelolaan Log Audit dan menulisnya ke Cloud Storage.

  1. Di Konsol GCP, buka Cloud Run.
  2. Klik Create service.
  3. Pilih Function (gunakan editor inline untuk membuat fungsi).
  4. Di bagian Configure, berikan detail konfigurasi berikut:

    Setelan Nilai
    Nama layanan sap-btp-collector
    Region Pilih region yang cocok dengan bucket Cloud Storage Anda (misalnya, us-central1)
    Runtime Pilih Python 3.12 atau yang lebih baru
  5. Di bagian Trigger (optional):

    1. Klik + Tambahkan pemicu.
    2. Pilih Cloud Pub/Sub.
    3. Di Select a Cloud Pub/Sub topic, pilih topik sap-btp-trigger.
    4. Klik Simpan.
  6. Di bagian Authentication:

    1. Pilih Wajibkan autentikasi.
    2. Periksa Identity and Access Management (IAM).
  7. Luaskan Containers, Networking, Security.

  8. Buka tab Keamanan:

    • Service account: Pilih akun layanan sap-btp-collector-sa.
  9. Buka tab Penampung:

    1. Klik Variables & Secrets.
    2. Klik + Add variable untuk setiap variabel lingkungan:
    Nama Variabel Nilai Contoh Deskripsi
    GCS_BUCKET sap-btp-logs Nama bucket Cloud Storage
    GCS_PREFIX sap-btp Awalan untuk file log
    STATE_KEY sap-btp-state.json Jalur state file, di luar awalan log
    SAP_API_URL https://auditlog-management.cfapps.us10.hana.ondemand.com Nilai url dari kunci layanan
    SAP_UAA_URL https://your-subdomain.authentication.region.hana.ondemand.com URL endpoint token OAuth
    SAP_CLIENT_ID your-client-id Client ID OAuth
    SAP_CLIENT_SECRET your-client-secret Rahasia klien OAuth
    LOOKBACK_HOURS 24 Periode lihat balik awal
  10. Di tab Variables & Secrets, buka Requests:

    • Request timeout: Masukkan 600 detik (10 menit).
  11. Buka tab Setelan di Penampung:

    • Di bagian Resources:
      • Memory: Pilih 512 MiB atau lebih tinggi.
      • CPU: Pilih 1.
    • Klik Done.
  12. Buka Execution environment:

    • Pilih Default (direkomendasikan).
  13. Di bagian Revision scaling:

    • Minimum number of instances: Masukkan 0.
    • Maximum number of instances: Masukkan 100 (atau sesuaikan berdasarkan beban yang diharapkan).
  14. Klik Create.

  15. Tunggu hingga layanan dibuat (1-2 menit).

  16. Setelah layanan dibuat, editor kode inline akan terbuka secara otomatis.

Menambahkan kode fungsi

  1. Masukkan main di Function entry point.
  2. Di editor kode inline, buat dua file:

    • File pertama - main.py:

      import functions_framework
      from google.cloud import storage
      import hashlib
      import json
      import os
      import urllib3
      from datetime import datetime, timezone, timedelta
      import time
      import base64
      import uuid
      
      # Initialize HTTP client with timeouts
      http = urllib3.PoolManager(
          timeout=urllib3.Timeout(connect=5.0, read=30.0),
          retries=False,
      )
      
      # Initialize Storage client
      storage_client = storage.Client()
      
      # Environment variables
      GCS_BUCKET = os.environ.get('GCS_BUCKET')
      GCS_PREFIX = os.environ.get('GCS_PREFIX', 'sap-btp')
      STATE_KEY = os.environ.get('STATE_KEY', 'sap-btp-state.json')
      SEEN_KEY = STATE_KEY + '.seen'
      API_URL = os.environ.get('SAP_API_URL')
      UAA_URL = os.environ.get('SAP_UAA_URL')
      CLIENT_ID = os.environ.get('SAP_CLIENT_ID')
      CLIENT_SECRET = os.environ.get('SAP_CLIENT_SECRET')
      LOOKBACK_HOURS = int(os.environ.get('LOOKBACK_HOURS', '24'))
      
      def parse_datetime(value: str) -> datetime:
          """Parse ISO datetime string to datetime object."""
          if value.endswith("Z"):
              value = value[:-1] + "+00:00"
          return datetime.fromisoformat(value)
      
      # message_uuid is the identifier of an audit log record; the parser maps it to
      # metadata.product_log_id.
      ID_FIELDS = ('message_uuid',)
      
      def event_keys(event):
          """Return every identity this event can be recognised by."""
          keys = {'sha256:' + hashlib.sha256(
              json.dumps(event, sort_keys=True, ensure_ascii=False).encode('utf-8')
          ).hexdigest()}
          for field in ID_FIELDS:
              value = event.get(field)
              if value:
                  keys.add(f'{field}:{value}')
          return keys
      
      def get_oauth_token():
          """Get OAuth 2.0 access token using client credentials flow."""
          token_url = f"{UAA_URL.rstrip('/')}/oauth/token"
      
          credentials = f"{CLIENT_ID}:{CLIENT_SECRET}"
          encoded_credentials = base64.b64encode(credentials.encode('utf-8')).decode('utf-8')
      
          headers = {
              'Authorization': f'Basic {encoded_credentials}',
              'Content-Type': 'application/x-www-form-urlencoded',
              'Accept': 'application/json'
          }
      
          body = 'grant_type=client_credentials'
      
          backoff = 1.0
          max_retries = 3
      
          for attempt in range(max_retries):
              response = http.request('POST', token_url, body=body, headers=headers)
      
              if response.status == 429:
                  retry_after = int(response.headers.get('Retry-After', str(int(backoff))))
                  print(f"Rate limited (429) on token request. Retrying after {retry_after}s...")
                  time.sleep(retry_after)
                  backoff = min(backoff * 2, 30.0)
                  continue
      
              if response.status != 200:
                  raise RuntimeError(f"Failed to get access token: {response.status} - {response.data.decode('utf-8')}")
      
              data = json.loads(response.data.decode('utf-8'))
              return data['access_token']
      
          raise RuntimeError(f"Failed to get token after {max_retries} retries due to rate limiting")
      
      @functions_framework.cloud_event
      def main(cloud_event):
          """
          Cloud Run function triggered by Pub/Sub to fetch SAP BTP
          audit logs and write to GCS.
      
          Args:
              cloud_event: CloudEvent object containing Pub/Sub message
          """
      
          if not all([GCS_BUCKET, API_URL, UAA_URL, CLIENT_ID, CLIENT_SECRET]):
              # Raise rather than return: a bare return acks the Pub/Sub message and
              # reports the run as successful, silently discarding the schedule tick.
              raise RuntimeError('Missing required environment variables')
      
          try:
              bucket = storage_client.bucket(GCS_BUCKET)
      
              # Load state
              state = load_state(bucket, STATE_KEY)
              seen_keys = load_seen(bucket, SEEN_KEY)
      
              # Determine time window
              now = datetime.now(timezone.utc)
              last_time = None
      
              if isinstance(state, dict) and state.get("last_event_time"):
                  try:
                      last_time = parse_datetime(state["last_event_time"])
                      last_time = last_time - timedelta(minutes=2)
                  except Exception as e:
                      print(f"Warning: Could not parse last_event_time: {e}")
      
              if last_time is None:
                  last_time = now - timedelta(hours=LOOKBACK_HOURS)
      
              print(f"Fetching audit logs from {last_time.isoformat()} to {now.isoformat()}")
      
              # Get OAuth token
              token = get_oauth_token()
      
              # Fetch audit logs
              records, newest_event_time = fetch_audit_logs(
                  token=token,
                  start_time=last_time,
                  end_time=now,
              )
      
              # Drop the events already written by a previous run (overlap window)
              fresh = [r for r in records if not (event_keys(r) & seen_keys)]
      
              if not fresh:
                  print("No new audit log records found.")
                  return
      
              # Write to GCS as NDJSON
              timestamp = now.strftime('%Y%m%d_%H%M%S')
              # The random suffix keeps concurrent executions (Pub/Sub delivers at
              # least once) from overwriting each other's object within one second.
              object_key = f"{GCS_PREFIX}/audit_{timestamp}_{uuid.uuid4().hex[:8]}.ndjson"
              blob = bucket.blob(object_key)
      
              ndjson = '\n'.join([json.dumps(record, ensure_ascii=False) for record in fresh]) + '\n'
              blob.upload_from_string(ndjson, content_type='application/x-ndjson')
      
              print(f"Wrote {len(fresh)} records to gs://{GCS_BUCKET}/{object_key}")
      
              # Remember every fetched record so the next overlap window is deduplicated
              save_seen(bucket, SEEN_KEY, records)
      
              # Update state with newest event time. The watermark must be an event
              # timestamp, never wall clock: a wall-clock watermark skips every event
              # the vendor indexes late.
              if not newest_event_time:
                  raise RuntimeError('Records were returned but no event timestamp could be parsed')
              save_state(bucket, STATE_KEY, newest_event_time)
      
              print(f"Successfully processed {len(fresh)} records")
      
          except Exception as e:
              print(f'Error processing audit logs: {str(e)}')
              raise
      
      def load_state(bucket, key):
          """Load state from GCS."""
          try:
              blob = bucket.blob(key)
              if blob.exists():
                  state_data = blob.download_as_text()
                  return json.loads(state_data)
          except Exception as e:
              print(f"Warning: Could not load state: {e}")
              raise
      
          return {}
      
      def save_state(bucket, key, last_event_time_iso: str):
          """Save the last event timestamp to GCS state file."""
          try:
              state = {'last_event_time': last_event_time_iso}
              blob = bucket.blob(key)
              blob.upload_from_string(
                  json.dumps(state, indent=2),
                  content_type='application/json'
              )
              print(f"Saved state: last_event_time={last_event_time_iso}")
          except Exception as e:
              print(f"Warning: Could not save state: {e}")
              raise
      
      def load_seen(bucket, key):
          """Load the event keys written by the previous run."""
          try:
              blob = bucket.blob(key)
              if blob.exists():
                  return set(json.loads(blob.download_as_text()))
          except Exception as e:
              print(f"Warning: Could not load seen keys: {e}")
              raise
      
          return set()
      
      def save_seen(bucket, key, records):
          """Save the keys of every fetched record for the next overlap window."""
          try:
              keys = set()
              for record in records:
                  keys |= event_keys(record)
              blob = bucket.blob(key)
              blob.upload_from_string(
                  json.dumps(sorted(keys)),
                  content_type='application/json'
              )
              print(f"Saved {len(keys)} seen keys")
          except Exception as e:
              print(f"Warning: Could not save seen keys: {e}")
              raise
      
      def fetch_audit_logs(token: str, start_time: datetime, end_time: datetime):
          """
          Fetch audit logs from the Audit Log Management Service retrieval API.
      
          The API takes time_from/time_to in UTC without a timezone designator and
          returns a JSON array at the root (HTTP 204 when the window is empty).
          When the result set is chunked, the next chunk's handle arrives in the
          "Paging" response header as handle=<value> and is passed back as the
          handle query parameter; the server chunk size is fixed at 500 records.
      
          Args:
              token: OAuth 2.0 access token
              start_time: Start time for log query
              end_time: End time for log query
      
          Returns:
              Tuple of (records list, newest_event_time ISO string)
      
          Raises:
              RuntimeError: on any API failure, so a failed fetch can never be
                  mistaken for an empty result.
          """
          base_url = API_URL.rstrip('/')
          endpoint = f"{base_url}/auditlog/v2/auditlogrecords"
      
          headers = {
              'Authorization': f'Bearer {token}',
              'Accept': 'application/json',
              'User-Agent': 'GoogleSecOps-SAPBTPCollector/1.0'
          }
      
          records = []
          newest_time = None
          page_num = 0
          backoff = 1.0
          rate_limit_retries = 0
          token_refreshed = False
      
          # The API expects UTC timestamps with no timezone suffix.
          time_from = start_time.strftime('%Y-%m-%dT%H:%M:%S')
          time_to = end_time.strftime('%Y-%m-%dT%H:%M:%S')
          handle = None
      
          from urllib.parse import urlencode
      
          while True:
              page_num += 1
      
              # Rebuild the full parameter set on every request.
              params = {'time_from': time_from, 'time_to': time_to}
              if handle:
                  params['handle'] = handle
              url = f"{endpoint}?{urlencode(params)}"
      
              response = http.request('GET', url, headers=headers)
      
              # The documented rate limit is 4 requests per second (burst 20).
              if response.status == 429:
                  rate_limit_retries += 1
                  if rate_limit_retries > 5:
                      raise RuntimeError('Rate limited repeatedly; giving up without advancing the watermark')
                  retry_after = response.headers.get('Retry-After')
                  try:
                      delay = float(retry_after) if retry_after else backoff
                  except (TypeError, ValueError):
                      delay = backoff
                  delay = min(max(delay, 1.0), 60.0)
                  print(f"Rate limited (429). Retrying after {delay}s...")
                  time.sleep(delay)
                  backoff = min(backoff * 2, 30.0)
                  continue
      
              backoff = 1.0
              rate_limit_retries = 0
      
              if response.status == 401:
                  # One refresh per run: a second consecutive 401 means the audit
                  # service rejects tokens UAA still issues, and retrying forever
                  # would hammer both services until the platform kills the run.
                  if token_refreshed:
                      raise RuntimeError('Audit log request still unauthorized after a token refresh')
                  print("Token expired, refreshing...")
                  token = get_oauth_token()
                  headers['Authorization'] = f'Bearer {token}'
                  token_refreshed = True
                  continue
      
              token_refreshed = False
      
              if response.status == 204:
                  # Documented empty result for the requested window.
                  break
      
              if response.status != 200:
                  raise RuntimeError(
                      f"Audit log request failed: {response.status} - "
                      f"{response.data.decode('utf-8')}"
                  )
      
              data = json.loads(response.data.decode('utf-8'))
      
              # The records arrive as a JSON array at the root. Tolerate wrapped
              # shapes defensively, but never call .get on a list: doing so
              # crashed previous revisions of this function.
              if isinstance(data, list):
                  page_results = data
              elif isinstance(data, dict):
                  page_results = data.get('value', data.get('results', []))
              else:
                  page_results = []
      
              print(f"Page {page_num}: Retrieved {len(page_results)} audit records")
              records.extend(page_results)
      
              # Track newest event time. Parse before assigning: an unparseable
              # stamp must never become the persisted watermark.
              for record in page_results:
                  event_time = record.get('time') or record.get('timestamp')
                  if not event_time:
                      continue
                  try:
                      parsed = parse_datetime(event_time)
                  except Exception as e:
                      print(f"Warning: Could not parse event time: {e}")
                      continue
                  if newest_time is None or parsed > parse_datetime(newest_time):
                      newest_time = event_time
      
              # More chunks are signaled only by the Paging response header.
              paging = response.headers.get('Paging') or response.headers.get('paging') or ''
              handle = paging.split('=', 1)[1] if '=' in paging else None
              if not handle:
                  break
      
          print(f"Retrieved {len(records)} total audit records from {page_num} pages")
          return records, newest_time
      

    • File kedua - requirements.txt:

      functions-framework==3.*
      google-cloud-storage==2.*
      urllib3>=2.0.0
      
  3. Klik Deploy untuk menyimpan dan men-deploy fungsi.

  4. Tunggu hingga deployment selesai (2-3 menit).

Buat tugas Cloud Scheduler

Cloud Scheduler akan memublikasikan pesan ke topik Pub/Sub secara berkala, sehingga memicu fungsi Cloud Run.

  1. Di Konsol GCP, buka Cloud Scheduler.
  2. Klik Create Job.
  3. Berikan detail konfigurasi berikut:

    Setelan Nilai
    Nama sap-btp-collector-hourly
    Region Pilih region yang sama dengan fungsi Cloud Run
    Frekuensi 0 * * * * (setiap jam, tepat pada jamnya)
    Zona Waktu Pilih zona waktu (UTC direkomendasikan)
    Jenis target Pub/Sub
    Topik Pilih topik sap-btp-trigger
    Isi pesan {} (objek JSON kosong)
  4. Klik Create.

Opsi frekuensi jadwal

Pilih frekuensi berdasarkan volume log dan persyaratan latensi:

Frekuensi Ekspresi Cron Kasus Penggunaan
Setiap 5 menit */5 * * * * Volume tinggi, latensi rendah
Setiap 15 menit */15 * * * * Volume sedang
Setiap jam 0 * * * * Standar (direkomendasikan)
Setiap 6 jam 0 */6 * * * Volume rendah, pemrosesan batch
Harian 0 0 * * * Pengumpulan data historis

Menguji integrasi

  1. Di konsol Cloud Scheduler, temukan tugas Anda (sap-btp-collector-hourly).
  2. Klik Force run untuk memicu secara manual.
  3. Tunggu beberapa detik, lalu buka Cloud Run > Services > sap-btp-collector > Logs.
  4. Pastikan fungsi berhasil dieksekusi. Cari:

    Fetching audit logs from YYYY-MM-DDTHH:MM:SS+00:00 to YYYY-MM-DDTHH:MM:SS+00:00
    Page 1: Retrieved X audit records
    Wrote X records to gs://sap-btp-logs/sap-btp/audit_YYYYMMDD_HHMMSS.ndjson
    Successfully processed X records
    
  5. Periksa bucket Cloud Storage (sap-btp-logs) untuk mengonfirmasi bahwa log audit telah ditulis.

Jika Anda melihat error di log:

  • HTTP 401: Periksa kredensial OAuth di variabel lingkungan atau token mungkin telah habis masa berlakunya (fungsi menangani pembaruan secara otomatis)
  • HTTP 403: Pastikan kunci layanan adalah milik instance auditlog-management di sub-akun yang sama yang log-nya Anda harapkan; koleksi peran pengguna tidak berlaku untuk token kredensial klien
  • HTTP 429: Pembatasan kapasitas - fungsi akan otomatis mencoba lagi dengan backoff
  • Gagal mendapatkan token akses: Pastikan SAP_UAA_URL, SAP_CLIENT_ID, dan SAP_CLIENT_SECRET sudah benar

Mengonfigurasi feed di Google SecOps untuk menyerap log SAP BTP

  1. Buka Setelan > Pengelolaan Data > Feed. Jika Anda menggunakan platform khusus SIEM, buka Settings > Feeds.
  2. Klik Tambahkan Feed Berita Baru.
  3. Klik Konfigurasi satu feed.
  4. Di kolom Nama feed, masukkan nama untuk feed (misalnya, SAP BTP Logs).
  5. Pilih Google Cloud Storage V2 sebagai Source type.
  6. Pilih Sap Business Technology Platform sebagai Log type.
  7. Klik Get Service Account. Email akun layanan yang unik akan ditampilkan, misalnya:

    chronicle-12345678@chronicle-gcp-prod.iam.gserviceaccount.com
    
  8. Salin alamat email ini. Anda akan menggunakannya pada langkah berikutnya.

  9. Klik Berikutnya.

  10. Tentukan nilai untuk parameter input berikut:

    • Storage bucket URL: Masukkan URI bucket Cloud Storage dengan jalur awalan:

      gs://sap-btp-logs/sap-btp/
      
      • Ganti:
        • sap-btp-logs: Nama bucket Cloud Storage Anda.
        • sap-btp/: Jalur tempat log disimpan.
    • Opsi penghapusan sumber: Pilih opsi penghapusan sesuai preferensi Anda:

      • Jangan pernah menghapus file: Jangan pernah menghapus file dari sumber (direkomendasikan untuk pengujian).
      • Hapus file yang ditransfer dan direktori kosong: Hapus file dan direktori kosong dari sumber setelah pengambilan berhasil diselesaikan.
    • Usia File Maksimum: Sertakan file yang diubah dalam jumlah hari terakhir (defaultnya adalah 180 hari).

    • Namespace aset: Namespace aset.

    • Label penyerapan: Label yang akan diterapkan ke peristiwa dari feed ini.

  11. Klik Berikutnya.

  12. Tinjau konfigurasi feed berita baru Anda di layar Finalize, lalu klik Submit.

Memberikan izin IAM ke akun layanan Google SecOps

Akun layanan Google SecOps memerlukan dua peran di bucket Cloud Storage Anda: Storage Object Viewer untuk membaca objek log, dan peran level bucket untuk membaca metadata bucket.

  1. Buka Cloud Storage > Buckets.
  2. Klik nama bucket Anda (sap-btp-logs).
  3. Buka tab Izin.
  4. Klik Grant access.
  5. Berikan detail konfigurasi berikut:
    • Add principals: Tempel email akun layanan Google SecOps.
    • Assign roles: Pilih kedua opsi berikut:
      • Storage Object Viewer: membaca objek log.
      • Storage Legacy Bucket Reader: membaca metadata bucket. Jika Anda memilih opsi penghapusan Delete transferred files and empty directories, pilih Storage Legacy Bucket Writer, yang juga memberikan izin penghapusan.
  6. Klik Simpan.

Tabel pemetaan UDM

Kolom Log Pemetaan UDM Logika
time metadata.event_timestamp Diurai sebagai ISO8601
principal_present metadata.event_type Dipetakan: true → STATUS_UPDATE
user_present metadata.event_type Dipetakan: true → USER_RESOURCE_ACCESS, true → USER_UNCATEGORIZED
json_message_uuid metadata.product_log_id Dipetakan secara langsung
host principal.asset.hostname Dipetakan secara langsung
key principal.asset.ip Dipetakan: ip → value
principal_ip principal.asset.ip Digabung
value principal.asset.ip Digabung
host principal.hostname Dipetakan secara langsung
key principal.ip Dipetakan: ip → value
principal_ip principal.ip Digabung
value principal.ip Digabung
principal_user_role principal.user.attribute.roles Digabung
key principal.user.email_addresses Dipetakan: "new","old" → value2, "new","old" → value1
key1 principal.user.email_addresses Dipetakan: emails → value2, userName → value1
key2 principal.user.email_addresses Dipetakan: value → value2
value1 principal.user.email_addresses Dipetakan: ^.+@.+$ → value1
value2 principal.user.email_addresses Digabung
user principal.user.user_display_name Dipetakan secara langsung
json_message.data_subject.id.userid principal.user.userid Dipetakan secara langsung
value1 principal.user.userid Dipetakan secara langsung
category security_result.category_details Digabung
als_service_id_label security_result.detection_fields Digabung
app_or_service_id_label security_result.detection_fields Digabung
attri_label security_result.detection_fields Digabung
attribute_label security_result.detection_fields Digabung
attribute_label1 security_result.detection_fields Digabung
custom_status_label security_result.detection_fields Digabung
custom_success_label security_result.detection_fields Digabung
custom_type_label security_result.detection_fields Digabung
desc_label security_result.detection_fields Digabung
format_version_label security_result.detection_fields Digabung
key security_result.detection_fields Mapped: json_message → message_label, id → attribute_label, "new","old" → `attribu...
message_id_label security_result.detection_fields Digabung
message_label security_result.detection_fields Digabung
message_label_json_message security_result.detection_fields Digabung
message_label_msgId security_result.detection_fields Digabung
message_label_msgNo security_result.detection_fields Digabung
message_label_uuid security_result.detection_fields Digabung
message_label_version security_result.detection_fields Digabung
org_id_label security_result.detection_fields Digabung
space_id_label security_result.detection_fields Digabung
tenant_label security_result.detection_fields Digabung
key security_result.severity Dipetakan: level → INFORMATIONAL, level → MEDIUM, level → UNKNOWN_SEVERITY
level security_result.severity Dipetakan: INFO → INFORMATIONAL
value security_result.severity Dipetakan: INFO → INFORMATIONAL, WARN → MEDIUM
level security_result.severity_details Dipetakan secara langsung
value1 target.resource.product_object_id Dipetakan secara langsung
key1 target.resource.resource_type Dipetakan: clusterID → CLUSTER
T/A metadata.event_type Konstanta: GENERIC_EVENT
T/A metadata.product_name Konstanta: SAP_BTP
T/A metadata.vendor_name Konstanta: SAP_BTP
T/A security_result.severity Konstanta: INFORMATIONAL
T/A target.resource.resource_type Konstanta: CLUSTER

Log Perubahan

Melihat Log Perubahan untuk parser ini

Perlu bantuan lain? Dapatkan jawaban dari anggota Komunitas dan profesional Google SecOps.