> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/integrations/processors/google-secops-standardization.md).

# Google SecOps Standardization

{% hint style="danger" %}
**WARNING**

This processor requires collector version 1.64.0 or newer to send fields to Google SecOps. In older collector versions, namespace and ingestion label fields will be added to telemetry but not parsed in Google SecOps.
{% endhint %}

***

### Description

The Google SecOps Standardization processor can be used to add the `log_type` [ingestion label](https://cloud.google.com/chronicle/docs/ingestion/parser-list/supported-default-parsers), which specifies the appropriate SecOps Parser for your logs.

### Use

The Google SecOps Standardization processor is to be used alongside the [Google SecOps Exporter](/integrations/destinations/google-secops-chronicle.md). This processor allows the user to configure the log type, namespace, and ingestion labels for logs sent to SecOps.

### Supported Types

| Metrics | Logs | Traces |
| ------- | ---- | ------ |
|         | ✓    |        |

### Configuration

<table><thead><tr><th width="117.93359375">Field</th><th>Description</th></tr></thead><tbody><tr><td>Log Type</td><td>The type of log that will be sent.</td></tr><tr><td>Namespace</td><td>User-configured environment namespace to identify the data domain the logs originated from.</td></tr><tr><td>Ingestion Labels</td><td>Key-value pairs of labels to be applied to the logs when sent to chronicle.</td></tr></tbody></table>

### Example Configuration

#### Configure Google SecOps for Windows events

This example configuration sets `logType` to "WINEVTLOG", `namespace` to "security", and `ingestionLabels` to a key-value pair: "environment" and "production".

**Web Interface**

<figure><img src="/files/AbL6uNmOuaabUFILP5TK" alt="Bindplane docs - Google SecOps Standardization - image 1"><figcaption></figcaption></figure>

**Standalone Processor**

```yaml
apiVersion: bindplane.observiq.com/v1
kind: Processor
metadata:
  id: google_secops_standardization
  name: google_secops_standardization
spec:
  type: google_secops_standardization
  parameters:
    - name: telemetry_types
      value: ['Logs']
    - name: condition
      value: 'true'
    - name: googleSecOpsStandardization
      value:
        condition: true
        logType: WINEVTLOG
        namespace: status
        ingestionLabels:
          environment: production
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bindplane.com/integrations/processors/google-secops-standardization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.