This document explains how to ingest logs from your SAP systems managed by SAP as part of the [SAP RISE](https://www.sap.com/products/erp/rise.html) offering and forward them to Google SecOps.

<br />

## Select your ingestion path

In an SAP RISE environment, the ingestion path depends on the log
layer. To achieve comprehensive log coverage across your
infrastructure and application layers, follow both paths described
in this document:

| Log layer | Log type | Ingestion path |
|---|---|---|
| Infrastructure logs | ICM, Gateway, Web Dispatcher, and HANA Audit logs. | SAP LogServ and Google SecOps feeds |
| Application logs | Security Audit Logs and Change Documents. | Application Telemetry Collector, Bindplane agent, and Bindplane server |

## Before you begin

Before you start the ingestion process, ensure that you have completed the following steps:

- **Planning** : Review the ingestion paths and technical requirements in the [Plan for log ingestion](https://docs.cloud.google.com/sap/docs/secops/plan-log-ingestion.md.txt) guide.
- **Foundation** : Provision your Google SecOps instance and complete the [onboarding process](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#onboarding-to-google-security-operations) in Google Cloud. Review with your SAP ECS representative that SAP LogServ is provisioned for your environment.
- **Bindplane setup** : Install and configure the centralized Bindplane server as described in the [Prepare your environment for log ingestion](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#setup-bindplane-server) guide.
- **Network access** : Ensure your network architecture allows the host running the Bindplane server to receive incoming traffic on port `4317` (gRPC) from the Application Telemetry Collector.
- **SAP preparation** : Ensure your SAP system is prepared (service user, authorizations, and SNC) as described in the [Prepare your environment for log ingestion](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#prepare-for-application-layer-logs) guide.
- **Google Cloud resources** : Ensure that you have configured the required Google Cloud resources, such as APIs, storage buckets, and IAM roles, as described in the [Prepare your environment for log ingestion](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#configure-gcp-resources-app-logs) guide.

## Ingest infrastructure logs

Follow this path to ingest logs that are automatically extracted and
delivered to your storage bucket by using SAP LogServ.

Infrastructure log ingestion in an SAP RISE environment involves the following components:

- **SAP LogServ**: An SAP Enterprise Cloud Services (ECS) service that extracts infrastructure logs from your RISE landscape and writes them to a storage bucket.
- **Storage bucket**: A bucket (Cloud Storage, Amazon S3, or Azure Blob Storage) in the cloud provider where your SAP systems are hosted.
- **Notification mechanism**: An event-driven service (Pub/Sub, Amazon SQS, or Azure Storage Queue) that notifies Google SecOps as soon as a new log file is written to the bucket.
- **Google SecOps feed** : A configured ingestion point that retrieves the logs from the storage bucket based on the notifications. For more information, see [Feed management overview](https://docs.cloud.google.com/chronicle/docs/administration/feed-management-overview.md.txt).

The specific components used depend on the cloud provider where your SAP RISE
landscape is hosted:

| Cloud provider | Log storage | Notification mechanism |
|---|---|---|
| **Google Cloud** | Cloud Storage | Pub/Sub |
| **AWS** | Amazon S3 | Amazon SQS |
| **Azure** | Azure Blob Storage | Azure Storage Queue |

Before configuring the ingestion feeds, coordinate with your
SAP ECS representative to enable LogServ and provision the destination storage bucket
and notification mechanism as described in the [Prepare your environment for log ingestion](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#configure-sap-rise-logserv) guide. This information is required to set up the ingestion feeds.

### Set up Google SecOps feeds

To ingest logs from LogServ, you must create a separate feed in
Google SecOps for each log type. For detailed step-by-step
instructions on creating a feed, see the
[Google SecOps documentation](https://docs.cloud.google.com/chronicle/docs/administration/feed-management.md.txt#configure-your-feeds).

#### Configure a feed for Cloud Storage

Use the following parameters to configure a feed for logs delivered to a Cloud Storage bucket.

| Parameter | Description |
|---|---|
| **Source type** | Select `Cloud Storage Event Driven`. |
| **Log type** | Select the log type that corresponds to the logs you are ingesting, for example, `SAP_ICM`. For more information about the supported log types, see the [Review supported log sources](https://docs.cloud.google.com/sap/docs/secops/plan-log-ingestion.md.txt#review-supported-log-sources) guide. |
| **Storage bucket URI** | Enter the storage bucket URI including the path for the log source, for example, `gs://sap-logserv-bucket/logserv/abap/icm/`. |
| **Pub/Sub subscription name** | Enter the Pub/Sub subscription name provided by SAP. |

##### Storage bucket URIs for LogServ

When specifying the **Storage bucket URI** parameter in your feed
configuration, use the URI that matches your SAP log source. For
SAP RISE environments on Google Cloud, LogServ delivers logs to dedicated
subdirectories within your storage bucket.

The following list of storage bucket URIs represents a subset of commonly
ingested SAP logs. Depending on your SAP RISE deployment, LogServ might also
deliver additional logs, such as OS, DNS, proxy, or Java logs:

- **SAP Web Dispatcher Logs** : `gs://BUCKET_NAME/logserv/webdispatcher/`
- **SAP HANA Audit Logs** : `gs://BUCKET_NAME/logserv/hana/hanaaudit/`
- **SAP Gateway Logs** : `gs://BUCKET_NAME/logserv/abap/gateway/`
- **SAP ICM Logs** : `gs://BUCKET_NAME/logserv/abap/icm/`

#### Configure a feed for Amazon S3

Use the following parameters to configure a feed for logs delivered to an Amazon S3 bucket.

| Parameter | Description |
|---|---|
| **Source type** | Select `Amazon SQS V2`. |
| **Log type** | Select the log type that corresponds to the logs you are ingesting, for example, `SAP_ICM`. For more information about the supported log types, see the [Review supported log sources](https://docs.cloud.google.com/sap/docs/secops/plan-log-ingestion.md.txt#review-supported-log-sources) guide. |
| **S3 URI** | Enter the S3 path provided by SAP. |
| **Queue name** | Enter the SQS queue URL or name provided by SAP. |

#### Configure a feed for Azure Blob Storage

Use the following parameters to configure a feed for logs delivered to Azure Blob Storage.

| Parameter | Description |
|---|---|
| **Source type** | Select `Microsoft Azure Blob Storage`. |
| **Log type** | Select the log type that corresponds to the logs you are ingesting, for example, `SAP_ICM`. For more information about the supported log types, see the [Review supported log sources](https://docs.cloud.google.com/sap/docs/secops/plan-log-ingestion.md.txt#review-supported-log-sources) guide. |
| **Azure URI** | Enter the Azure Blob Storage URI provided by SAP. |
| **Connection string** | Enter the token or connection string provided by SAP. |

### Confirm your log ingestion

To verify that your infrastructure logs are being correctly ingested from LogServ,
do the following:

1. **In Google SecOps** , go to **SIEM Settings** \> **Feeds**.
2. Confirm that the feeds you created are in **Active** status.
3. Check the **Last Run Status** to ensure that log files are being successfully retrieved from your storage bucket.
4. Go to **Search** and enter a UDM query for your log type, for example, `metadata.log_type = "SAP_ICM"`. For more information, see [Search and filter SAP logs](https://docs.cloud.google.com/sap/docs/secops/detect-sap-threats.md.txt#search-and-filter-sap-logs).
5. Confirm that logs are appearing and are correctly parsed into UDM fields.
6. Open the **Event Viewer** to inspect the raw log and the normalized UDM fields. For example, verify that the **Principal Host** (`principal.host.hostname`) and relevant network or database details are correctly populated.

## Ingest application logs

Follow this path to ingest logs such as Security Audit Logs and Change Documents
directly from the SAP application layer using the RFC protocol.

Application log ingestion involves the following components:

- **Application Telemetry Collector**: A containerized Java application that connects to your SAP application servers using the RFC protocol to extract security logs.
- **Bindplane agent**: A lightweight agent installed on the collector host that receives OTLP data and forwards the data to the Google SecOps gateway.
- **Bindplane server**: Receives the logs from the Bindplane agents and forwards them to Google SecOps.

> [!NOTE]
> **Note:** You can use the [SAP Telemetry Collector Setup Wizard](https://github.com/chronicle/ingestion-scripts/blob/main/sap_telemetry_collector_setup_wizard/README.md) on GitHub to install and configure the Application Telemetry Collector in a guided web interface. The wizard generates reproducible Terraform scripts to provision the required log ingestion infrastructure, including the Bindplane agents and telemetry collectors. Alternatively, you can follow the manual steps in the following sections to prepare, configure, and deploy the artifacts for the collector.

### Prepare the collector host

Provision the host machine to run the Application Telemetry Collector container:

- **Host options**: You can use Compute Engine instances, on-premises servers, or container orchestration platforms such as GKE.
- **Specifications**: Use a standard Linux distribution, such as Debian 11 or 12, with Docker Engine 20.10 or later.
- **Network** : The host requires a network connection to your SAP RISE instance, such as VPC peering or Cloud Interconnect. Open egress to SAP Gateway ports `32INSTANCE_NUMBER` or `33INSTANCE_NUMBER` (where `INSTANCE_NUMBER` is your instance number).
- **Continuity**: Ensure the host is "always-on" to prevent log gaps. Don't use serverless platforms like Cloud Run.
- **Identity (Within Google Cloud)** : Attach the service account created in the [Configure Google Cloud resources](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#configure-gcp-resources-app-logs) section to the host. In the console, set **Access Scopes** to **Allow full access to all Cloud APIs**.
- **Identity (Outside Google Cloud)** : Use [service account keys](https://docs.cloud.google.com/iam/docs/keys-create-delete.md.txt) or [Workload Identity Federation](https://docs.cloud.google.com/iam/docs/workload-identity-federation.md.txt).

### Update the Application Telemetry Collector

Skip this section if you are deploying the collector for the first time, and
go to [Configure the collector](https://docs.cloud.google.com/sap/docs/secops/ingest-sap-rise-logs.md.txt#configure-the-collector).

If you're using an older version of the Application Telemetry Collector, you
must update to the latest General Availability (GA) image.

To update your existing deployment, do the following:

1. Pull the latest GA image from Artifact Registry for your region.

   ```bash
   docker pull IMAGE_PATH
   ```

   Replace `IMAGE_PATH` with the URI of the collector image.
   Use one of the following regional paths:
   - `us-docker.pkg.dev/sap-core-eng-products/sap-application-telemetry/google-cloud-sap-application-telemetry:latest`
   - `europe-docker.pkg.dev/sap-core-eng-products/sap-application-telemetry/google-cloud-sap-application-telemetry:latest`
   - `asia-docker.pkg.dev/sap-core-eng-products/sap-application-telemetry/google-cloud-sap-application-telemetry:latest`
2. Stop the running collector instance gracefully.

   ```bash
   docker stop sap-telemetry-collector
   ```
3. Restart the container again using the exact same `docker run` command, environment variables, and volume mounts that you used during the initial setup.

   ```bash
   docker run -d \
       --name sap-telemetry-collector \
       --restart always \
       --network host \
       -v /etc/sap-collector:/tmp/keys:ro \
       -e GOOGLE_APPLICATION_CREDENTIALS=/tmp/keys/creds.json \
       -e COLLECTOR_GCS_BUCKET=gs://BUCKET_NAME \
       -e LOCK_LEASE_TIMEOUT_MINUTES=LEASE_TIMEOUT \
       -e LOCK_HEARTBEAT_INTERVAL_MINUTES=HEARTBEAT_INTERVAL \
       IMAGE_PATH
   ```

   For information about the placeholder variables in this command, see
   [Run the collector container](https://docs.cloud.google.com/sap/docs/secops/ingest-sap-rise-logs.md.txt#run-the-collector-container).

### Configure the collector

The Application Telemetry Collector uses a `collector_config.json` file to
define your SAP connections, authentication settings, and the application-layer
logs that you want to ingest.

To create and upload the collector configuration file, do the following:

1. In your local working directory, create a `collector_config.json` file using the [configuration example and field descriptions](https://docs.cloud.google.com/sap/docs/secops/ingest-sap-rise-logs.md.txt#configuration-example-and-field-descriptions).
2. Optional: To monitor multiple SAP systems through a single collector deployment, add multiple entries to the `systems` array in the configuration file. Each system must have a unique `system_id`.
3. Upload the `collector_config.json` file to the `config/` folder in the Cloud Storage bucket that you created in [Configure Google Cloud resources](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#configure-gcp-resources-app-logs).

#### Configuration example and field descriptions

Use the following JSON example to create your collector configuration file, and
refer to the field descriptions for detailed parameter information:

```json
{
  "systems": [
    {
      "system_id": "PRD-HANA",
      "connection": {
        "host": "sap-prd.example.com",
        "client": "100",
        "system_number": "00",
        "language": "en"
      },
      "auth": {
        "basic": {
          "username_secret": "projects/SAP_PROJECT_ID/secrets/SAP_COLLECTOR_USER/versions/latest",
          "password_secret": "projects/SAP_PROJECT_ID/secrets/SAP_COLLECTOR_PASS/versions/latest"
        }
      },
      "log_sources": [
        {
          "log_type": "SAP_SECURITY_AUDIT",
          "interval": "60s"
        },
        {
          "log_type": "SAP_CHANGE_DOCUMENT",
          "interval": "300s",
          "change_document_object_classes": ["PFCG", "IDENTITY"]
        }
      ],
      "initial_lookback_window": "86400s",
      "sap_timezone": "UTC"
    },
    {
      "system_id": "DEV-HANA-SNC",
      "connection": {
        "host": "10.128.0.50",
        "client": "200",
        "system_number": "01",
        "language": "en"
      },
      "auth": {
        "x509": {
          "snc_name": "p:CN=SAP-Collector, O=MyCompany, C=US",
          "snc_partner_name": "p:CN=SAP-Server-DEV, O=MyCompany, C=US",
          "snc_qop": "3",
          "x509_cert_secret": "projects/SAP_PROJECT_ID/secrets/SAP_X509_CERT/versions/latest"
        }
      },
      "log_sources": [
        {
          "log_type": "SAP_SECURITY_AUDIT",
          "interval": "120s"
        }
      ],
      "initial_lookback_window": "3600s",
      "sap_timezone": "UTC"
    }
  ],
  "bindplane_host": "127.0.0.1",
  "bindplane_port": 4317,
  "heartbeat_enabled": true,
  "heartbeat_interval": "30s",
  "heartbeat_metric_name": "custom/sap/collector_heartbeat",
  "jco_pse_secret": "projects/SAP_PROJECT_ID/secrets/SAP_COLLECTOR_PSE/versions/latest",
  "jco_cred_secret": "projects/SAP_PROJECT_ID/secrets/SAP_COLLECTOR_CRED/versions/latest"
}
```

The following table describes the fields in the `collector_config.json` file.

| Section | Field | Description |
|---|---|---|
| **System connection (`systems`)** List of SAP systems to monitor. | `system_id` | A unique name for your SAP system within the collector configuration, for example, `PRD-HANA`. In the example, replace `PRD-HANA` with your specific system label. |
| **System connection (`systems`)** List of SAP systems to monitor. | `sap_timezone` | The timezone of the SAP application server, for example, `UTC`. This is critical for accurate log querying. |
| **System connection (`systems`)** List of SAP systems to monitor. | `initial_lookback_window` | How far back the collector looks for logs on its first run, for example, `86400s` for 24 hours. |
| **System connection (`systems`)** List of SAP systems to monitor. | `connection` | Contains the following RFC connection parameters: - `host`: The fully qualified domain name (FQDN) or IP address of your SAP server. Replace `sap-prd.example.com` in the example. - `client`: The 3-digit SAP client number, for example, `100`. - `system_number`: The 2-digit SAP system instance number, for example, `00`. - `language`: The logon language, which defaults to `en`. |
| **Authentication (`auth`)** Choose one of the authentication methods. | `basic` | Username and password authentication. Provide the full Secret Manager paths for `username_secret` and `password_secret`. These secrets must contain the credentials of the [SAP service user](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#create-an-sap-service-user) created in the preparation guide. For more information, see [Basic authentication](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#auth-option-basic). |
| **Authentication (`auth`)** Choose one of the authentication methods. | `x509` (SNC) | Secure Network Communication authentication. For setup instructions, see [Secure Network Communication (SNC)](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#configure-snc-x509). Provide the following: - `snc_name`: The collector's SNC identity, for example, `p:CN=SAP-Collector,O=MyCompany,C=US`. - `snc_partner_name`: The SNC identity of the SAP application server. - `snc_qop`: (Optional) The Quality of Protection level required by the SAP server, for example, `3` for end-to-end data privacy and payload encryption. - `x509_cert_secret`: (Optional) The full Secret Manager path to the secret containing the collector's public X.509 certificate. For more information, see [Store SNC artifacts in Secret Manager](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#store-snc-artifacts). |
| **Log sources (`log_sources`)** Defines logs and frequency. | `log_type` | The type of log to ingest. Options include: - `SAP_SECURITY_AUDIT` - `SAP_CHANGE_DOCUMENT` For more information, see [Review supported log sources](https://docs.cloud.google.com/sap/docs/secops/plan-log-ingestion.md.txt#review-supported-log-sources). |
| **Log sources (`log_sources`)** Defines logs and frequency. | `interval` | The polling frequency for this specific log source, for example, `30s`. |
| **Log sources (`log_sources`)** Defines logs and frequency. | `change_document_object_classes` | (Optional) Used only for `SAP_CHANGE_DOCUMENT`. A list of specific SAP object classes to track, for example, `["MATERIAL", "USER"]`. |
| **Global collector settings** Applied to the entire instance. | `bindplane_host` | The hostname or IP address of your Bindplane agent, such as `localhost` or `10.0.0.5`. We recommend deploying Bindplane agent on the same host as Application Telemetry Collector. In this configuration, set the `bindplane_host` value to `localhost`. |
| **Global collector settings** Applied to the entire instance. | `bindplane_port` | The port number the Bindplane server listens on. Default is `4317`. |
| **Global collector settings** Applied to the entire instance. | `heartbeat_enabled` | A boolean, which is `true` or `false`, to toggle a "stay-alive" metric. |
| **Global collector settings** Applied to the entire instance. | `heartbeat_interval` | How often the heartbeat metric is sent to Monitoring through Bindplane. Must be a string followed by "s", for example, `30s`. Defaults to `60s`. |
| **Global collector settings** Applied to the entire instance. | `heartbeat_metric_name` | (Optional) The name that appears in your monitoring dashboard for this heartbeat, for example, `sap_collector_status`. Defaults to `sap_appl_telemetry_collector_heartbeat`. |
| **Global collector settings** Applied to the entire instance. | `jco_pse_secret` | The full Secret Manager path to the secret containing your binary `.pse` file (for example, `sapcrypto.pse`). For more information, see [Store SNC artifacts in Secret Manager](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#store-snc-artifacts). |
| **Global collector settings** Applied to the entire instance. | `jco_cred_secret` | The full Secret Manager path to the secret containing your binary credentials file (`cred_v2`). For more information, see [Store SNC artifacts in Secret Manager](https://docs.cloud.google.com/sap/docs/secops/prepare-environment-ingestion.md.txt#store-snc-artifacts). |

### Deploy the collector

Run the Application Telemetry Collector as a Docker container on your host machine.

#### Prepare host directory and credentials (external hosts)

If your host machine is outside Google Cloud,
such as on-premises or in another cloud, and you don't use a VM service
account, then prepare the configuration directory and credentials:

1. **Create the directory**: Create the designated configuration directory:

   ```bash
   sudo mkdir -p /etc/sap-collector
   ```
2. **Prepare credentials**: For hosts outside of Google Cloud, you can
   provide a service account key or configure Workload Identity Federation (WIF).

   - **Service account key** : [Create a service account key](https://docs.cloud.google.com/iam/docs/keys-create-delete.md.txt) and configure the key as [application default credentials](https://docs.cloud.google.com/docs/authentication/provide-credentials-adc.md.txt) on your host. Rename the downloaded JSON key to `creds.json` and move the key to the directory: `bash
     sudo mv /path/to/downloaded-key.json /etc/sap-collector/creds.json`
   - **Workload Identity Federation** : [Configure Workload Identity Federation](https://docs.cloud.google.com/iam/docs/workload-identity-federation.md.txt) to authenticate using an external identity provider.

#### Run the collector container

Choose the deployment command that matches your host environment:

### Google Cloud

Use this command if your host runs on Google Cloud and uses an
attached Service Account for authentication.

```bash
docker run -d \
    --name sap-telemetry-collector \
    --restart always \
    --network host \
    -e COLLECTOR_GCS_BUCKET=gs://BUCKET_NAME \
    -e LOCK_LEASE_TIMEOUT_MINUTES=LEASE_TIMEOUT \
    -e LOCK_HEARTBEAT_INTERVAL_MINUTES=HEARTBEAT_INTERVAL \
    IMAGE_PATH
```

### External host

Use this command if your host is outside Google Cloud. This command
uses the Docker volume mount (`-v`) to link your host's `/etc/sap-collector`
directory to the container's `/tmp/keys` directory, and the
`GOOGLE_APPLICATION_CREDENTIALS` environment variable (`-e`) to point
the collector to your `creds.json` key.

```bash
docker run -d \
    --name sap-telemetry-collector \
    --restart always \
    --network host \
    -v /etc/sap-collector:/tmp/keys:ro \
    -e GOOGLE_APPLICATION_CREDENTIALS=/tmp/keys/creds.json \
    -e COLLECTOR_GCS_BUCKET=gs://BUCKET_NAME \
    -e LOCK_LEASE_TIMEOUT_MINUTES=LEASE_TIMEOUT \
    -e LOCK_HEARTBEAT_INTERVAL_MINUTES=HEARTBEAT_INTERVAL \
    IMAGE_PATH
```

Replace the following:

- `BUCKET_NAME`: The name of the Cloud Storage bucket where you uploaded the SAP JCo libraries and the `collector_config.json` file. Ensure that the value follows the format `gs://BUCKET_NAME` without trailing slashes or subdirectories.
- `LEASE_TIMEOUT`: (Optional) The duration, in minutes, that the collector instance holds a lease on the lock file. If an instance stops unexpectedly, then a new instance can acquire the lock after this period expires. Default value: `5`.
- `HEARTBEAT_INTERVAL`: (Optional) The frequency, in minutes, at which the collector renews its lease on the Cloud Storage lock file. Default value: `1`.
- `IMAGE_PATH`: The URI of the collector
  image in Artifact Registry. Use one of the following regional paths:

  - `us-docker.pkg.dev/sap-core-eng-products/sap-application-telemetry/google-cloud-sap-application-telemetry:TAG`
  - `europe-docker.pkg.dev/sap-core-eng-products/sap-application-telemetry/google-cloud-sap-application-telemetry:TAG`
  - `asia-docker.pkg.dev/sap-core-eng-products/sap-application-telemetry/google-cloud-sap-application-telemetry:TAG`

  Replace `TAG` with the version of the collector image that you want to download, for example, `latest`. For more information about how tags work, see [Artifact Registry container concepts](https://docs.cloud.google.com/artifact-registry/docs/container-concepts.md.txt#tags).

To ensure that only one collector instance pulls logs at a time, the
Application Telemetry Collector uses a distributed lease-lock mechanism
through Cloud Storage generation preconditions. This mechanism
prevents duplicate log ingestion and supports containerized deployments across
multiple hosts.

If an instance stops and you start a new instance, the new
instance only begins log collection after the `LOCK_LEASE_TIMEOUT_MINUTES`
period expires.
To skip this waiting period and start log collection immediately, manually
delete the `sap_app_telemetry_collector.lock` file from the root folder of your
Cloud Storage bucket.

### Install the Bindplane agent on the Application Telemetry Collector host

To forward application logs, install the Bindplane agent on the
Application Telemetry Collector host by running the command generated in
the Bindplane UI. For detailed instructions, see the [Bindplane agent installation guide](https://docs.bindplane.com/readme/install-your-first-collector).

To verify the installation, go to the **Agents** tab in the **Bindplane UI**
and confirm that the agent is visible with a **Connected** status.

### Configure the Bindplane gateway

Configure a gateway in the Bindplane UI to receive logs from the
Application Telemetry Collector and forward them to Google SecOps.

#### Create the log forwarding configuration

Define the basic settings for the pipeline on your central Bindplane server.

1. In the **Bindplane UI** , go to the **Configurations** tab.
2. Click **Create Configuration**.
3. Enter a **Name** , for example, `sap-app-logs`.
4. Select **BDOT 1.x (Stable)** as the **Agent Type**.
5. Select **Linux** as the **Platform**.
6. Click **Next**.

#### Add the Bindplane gateway source

Configure an OpenTelemetry (OTLP) listener on the Bindplane server to
receive logs from the Application Telemetry Collector.

1. In the **Add Sources** stage, select the **Bindplane Gateway** source type.
2. Enter a **Short Description**.
3. In the **Listen Address** field, enter `0.0.0.0`.
4. Ensure the **Port** is set to `4317` (gRPC) and ensure that your host's firewall allows traffic on this port.
5. Click **Save**.

#### Add the Batch processor

To prevent overwhelming the Google SecOps API, batch your requests.

1. Click **Add Processor** and select **Batch**.
2. Use the recommended defaults (usually `8192` units or a `200ms` timeout).
3. Click **Save**.

#### Obtain Google SecOps credentials

To securely forward logs to Google SecOps, you must obtain
your ingestion authentication file and customer ID from the Google SecOps console.

##### Google SecOps ingestion authentication file

To download the ingestion authentication file, do the following:

1. Open the Google SecOps console.
2. Go to **SIEM Settings** \> **Collection Agent**.
3. Download the Google SecOps ingestion authentication file.
   Your next step depends on your transfer method:

   - **gRPC**: Use the downloaded ingestion authentication file.
   - **HTTPS** : Create a service account in the Google Cloud project linked to Google SecOps and assign the **Chronicle Editor** role to the service account.

##### Google SecOps customer ID

To find the customer ID, do the following:

1. Open the Google SecOps console.
2. Go to **SIEM Settings** \> **Profile**.
3. Copy the customer ID from the **Organization Details** section.

#### Create the Google SecOps destination in Bindplane

Set up the final destination in Bindplane to securely forward your processed logs to Google SecOps.

1. In the **Bindplane UI** , go to the **Destinations** tab and click **Create Destination**.
2. Select **Google SecOps** as the destination type.
3. Enter a **Name** , for example, `secops-destination`.
4. In the **Customer ID** field, paste your Google SecOps customer ID.
5. In the **Credentials** field, click **Upload** and select the ingestion authentication file you downloaded, or paste the file content directly.
6. Click **Save**.

#### Add the Monitoring destination

To monitor the health of your collectors within Monitoring,
ensure that heartbeat metrics are enabled and routed through the gateway.

1. Click **Add Destination** and select **Google Cloud Monitoring**.
2. In the **Project ID** field, enter your Google Cloud project ID.
3. In the **Authentication** field, select **Auto** if your Bindplane server is running on a Google Cloud instance. Otherwise, provide your Service Account credentials.
4. Click **Save**.

### Deploy the configuration to agents

Once the configuration is ready, assign the configuration to your installed Bindplane agents.

1. In the **Bindplane UI** , go to the **Configurations** tab.
2. Select your new configuration, for example, `sap-app-logs`.
3. Click **Add Agents**.
4. Select the Bindplane agent on the Application Telemetry Collector host and click **Apply**.

### Confirm your log ingestion

To ensure the setup is working correctly, follow the verification steps
in [Confirm your log ingestion](https://docs.cloud.google.com/sap/docs/secops/ingest-sap-rise-logs.md.txt#confirm-infra-logs).

When verifying application logs in Google SecOps, use a
UDM query to filter by your specific log type, for example, `metadata.log_type = "SAP_SECURITY_AUDIT"`. For more information, see [Search and filter SAP logs](https://docs.cloud.google.com/sap/docs/secops/detect-sap-threats.md.txt#search-and-filter-sap-logs).

## Troubleshooting

For information about diagnosing and resolving common issues related to setting
up Google SecOps for SAP, see [Troubleshoot SAP log ingestion](https://docs.cloud.google.com/sap/docs/secops/troubleshooting.md.txt).

## Get support


For issues related to Google SecOps for SAP,
[contact Google SecOps support](https://docs.cloud.google.com/chronicle/docs/getting-support.md.txt).
Our team provides assistance or guides you to the right resource to help ensure a timely resolution.

For issues involving SAP systems or the LogServ service, contact SAP support.
For issues related to other third-party products, such as Bindplane, contact the appropriate third-party vendor for assistance.

Get technical answers and peer support in the [Google SecOps Community](https://security.googlecloudcommunity.com/google-security-operations-2).

<br />

## What's next

- [Detect and investigate threats in SAP logs](https://docs.cloud.google.com/sap/docs/secops/detect-sap-threats.md.txt)
- [SAP to UDM field mapping reference](https://docs.cloud.google.com/sap/docs/secops/udm-mapping-overview.md.txt)
- [Troubleshoot SAP log ingestion](https://docs.cloud.google.com/sap/docs/secops/troubleshooting.md.txt)