Skip to main content

Google SecOps Events Integration Guide

Overview

The Google SecOps Events connector allows NINA to interact with the Google SecOps Events, Log Management, and Ingestion APIs. It covers the full surface of UDM event retrieval and enrichment, log type and parser management, raw log ingestion, feed configuration, forwarder and collector management, data taps, and webhook ingestion endpoints.

Capabilities

CategoryResourcesOperations
EventsUDM Events, Search Sessions, Saved Search QueriesRetrieve, enrich, import UDM events; list search session results; CRUD saved queries; manage IAM policies
Log ManagementLog Types, Log Type Settings, Log Type Analysis Reports, Log Processing PipelinesCRUD log types; get/update settings; list analysis reports; manage pipelines; run analysis
ParsersParsers, Parser Extensions, Parser Analysis Reports, Parser Validation Reports, Parser Parsing Errors, Extension Validation Reports, Extension Parsing Errors, Parser Extension Validation ReportsFull parser lifecycle: create, activate, deactivate, copy, run analysis, validate, list errors
Raw LogsRaw LogsImport and list raw log entries per log type; classify log entries
IngestionFeeds, Feed Packs, Feed Service Accounts, Feed Source Type Schemas, Data Taps, Ingestion Log Labels, Ingestion Log NamespacesManage ingestion feeds; browse feed packs and schemas; manage data taps; list labels and namespaces
InfrastructureForwarders, Collectors, WebhooksManage on-premises forwarders and their collectors; create and monitor webhook ingestion endpoints

API Versions

Resource groupAPI version
events, logTypes, logTypeSettings, logs, parserExtensions, extensionValidationReports, extensionParsingErrors, parserExtensionValidationReports, parsers, parserValidationReports, parserParsingErrors, feeds, feedPacks, feedServiceAccounts, feedSourceTypeSchemas, ingestionLogLabels, ingestionLogNamespaces, searchQueries, forwarders (import stats)v1
searchSessions, logProcessingPipelines, logTypes (runAnalysis, search), logTypeAnalysisReports, logs (classify), parsers (runAnalysis), parserAnalysisReports, dataTaps, feeds (create, update, scheduleTransfer), forwarders, collectors, webhooksv1alpha

Both v1 and v1alpha operations share the same service account credential and instance resource path.

Authentication Method

Google Cloud service account with a JSON key. The connector uses the golang.org/x/oauth2/google JWT flow to obtain short-lived OAuth2 access tokens automatically. No user interaction is required.

How Authentication Works

  1. The connector reads the service account JSON key from the serviceAccountJson credential field.
  2. It calls google.JWTConfigFromJSON to parse the key and requests the scope https://www.googleapis.com/auth/cloud-platform.
  3. An OAuth2 HTTP client is created; it fetches and caches access tokens, refreshing them before they expire.
  4. Every API request carries a Bearer <token> Authorization header added transparently by the HTTP client.

Credential Configuration

Google SecOps API Regions

region valueAPI base URLGeography
ushttps://us-chronicle.googleapis.comUnited States
euhttps://eu-chronicle.googleapis.comEurope
asia-southeast1https://asia-southeast1-chronicle.googleapis.comSingapore
asia-south1https://asia-south1-chronicle.googleapis.comIndia
northamerica-northeast2https://northamerica-northeast2-chronicle.googleapis.comCanada
me-west1https://me-west1-chronicle.googleapis.comMiddle East

Note: region and location are different fields. region is the API hostname prefix (e.g. eu). location is the GCP resource location used in the resource path (e.g. europe-west2 or eu). For most instances these share the same short value, but they can differ.

Credential Fields

FieldTypeRequiredDescriptionExample
serviceAccountJsonstringYesComplete Google service account JSON key — paste the entire file content{ "type": "service_account", ... }
regionstringYesGoogle SecOps API region prefix used to build the base URLeu
projectstringYesGCP project IDmy-project-123
locationstringYesGCP location for the Google SecOps instance resource patheu or europe-west2
instancestringYesGoogle SecOps instance UUIDfca7f167-b9d1-43b1-9d03-0257d31dcb63

Where to find these values:

  • project — GCP Console → top navigation bar → project selector → project ID.
  • location — Google SecOps Console → Settings → Instance details → Location.
  • instance — Google SecOps Console → Settings → Instance details → Instance ID.
  • region — Google SecOps Console → Settings → Instance details → Region (use the short prefix, e.g. eu).

Required IAM Permissions

Assign these predefined Google SecOps IAM roles on the GCP project to the service account:

RoleRequired for
roles/chronicle.viewerAll read-only operations (list, get, fetch, batchGet)
roles/chronicle.editorWrite operations (create, update, patch, import, activate, deactivate, enable, disable)
roles/chronicle.adminAdministrative operations (delete, revoke, batch modifications)

Least-privilege recommendation: grant chronicle.viewer for read-only ingestion monitoring workflows. Grant chronicle.editor for parser and feed management. Grant chronicle.admin only when forwarder deletion or webhook URL revocation is required.

Additionally, the service account needs the following GCP platform-level permissions:

PermissionRequired for
iam.serviceAccounts.actAsIf the service account needs to impersonate another SA for feed ingestion
resourcemanager.projects.getReading project metadata

How to Obtain a Service Account Key

  1. Open GCP Console → IAM & AdminService Accounts.
  2. Click Create Service Account. Use a descriptive name such as nina-chronicle-events.
  3. Grant the service account the Google SecOps IAM roles listed above on the GCP project.
  4. Click the service account → Keys tab → Add KeyCreate new keyJSON.
  5. Save the downloaded JSON file. Paste its entire content as the serviceAccountJson credential value.

Security note: The JSON key is a long-lived credential. Store it using NINA's secure credential vault and never commit it to source control. Rotate keys periodically following your organisation's key management policy.

Shared Credential with Other Google SecOps Connectors

The chronicle-events credential uses the same five fields and the same service account as chronicle-instances, chronicle-cases, chronicle-soar, and chronicle-detections. A single service account configured with the appropriate IAM roles can be reused across all Google SecOps connectors.

Creating a Google SecOps Events Credential in NINA

  1. Navigate to the Credentials section in NINA.
  2. Click Add New Credential.
  3. Select Google SecOps Events as the integration.
  4. Fill in the five fields described in the table above.
  5. Click Test Connection to validate the credentials against the live API.
  6. Click Save.

API URL and Resource Path Structure

All operations are scoped to a Google SecOps instance. The connector builds URLs in the following pattern:

https://{region}-chronicle.googleapis.com
/{apiVersion}/projects/{project}/locations/{location}/instances/{instance}
/{resource}[/{subresource}][:{action}]

Examples:

OperationResolved URL
List log typesGET https://eu-chronicle.googleapis.com/v1/projects/my-project/locations/eu/instances/{uuid}/logTypes
Import UDM eventsPOST https://eu-chronicle.googleapis.com/v1/projects/my-project/locations/eu/instances/{uuid}/events:import
List pipelinesGET https://eu-chronicle.googleapis.com/v1alpha/projects/my-project/locations/eu/instances/{uuid}/logProcessingPipelines
Create webhookPOST https://eu-chronicle.googleapis.com/v1alpha/projects/my-project/locations/eu/instances/{uuid}/webhooks
List collectorsGET https://eu-chronicle.googleapis.com/v1alpha/projects/my-project/locations/eu/instances/{uuid}/forwarders/{id}/collectors

Rate Limits and Quotas

The Google SecOps API enforces per-project rate limits. The connector handles these automatically:

  • On HTTP 429 Too Many Requests: retries up to 3 times with exponential back-off (1 s → 2 s → 4 s).
  • If a Retry-After header is present in the response, that duration is used instead of the default back-off.
  • All requests time out after 90 seconds.
  • If the quota is persistently exceeded, contact Google Cloud support to request a limit increase.

Supported Operations

Resources Overview

ResourceOperationsDescription
eventsbatchGet, get, fetchEnrichedEvent, importRetrieve and import UDM events
searchSessionslistSearchedResultsList results from an existing search session
searchQueriescreate, delete, get, list, update, getIamPolicy, setIamPolicyManage and share saved search queries
logProcessingPipelinesassociateStreams, create, delete, dissociateStreams, fetchAssociatedPipeline, fetchSampleLogsByStreams, get, list, testPipeline, updateFull lifecycle management of log processing pipelines
logTypescreate, generateEventTypesSuggestions, getLogTypeSetting, legacySubmitParserExtension, list, runParser, runAnalysis, search, updateLogTypeSettingManage built-in and custom log types
logTypeSettingslistList log type settings across the instance
logTypeAnalysisReportsget, listRetrieve analysis reports for log types
logsimport, list, classifyImport raw logs, list entries, and classify unknown logs
parserExtensionsactivate, create, delete, get, listManage custom CBN parser extensions
extensionValidationReportsget, list, listValidationErrorsBrowse parser extension validation results
extensionParsingErrorslistList parsing errors from extension validation
parserExtensionValidationReportsgetGet summary validation report for a parser extension
parsersactivate, activateReleaseCandidateParser, copy, create, deactivate, delete, fetchParserCandidates, get, list, runAnalysis, updateFull lifecycle management of CBN parsers
parserAnalysisReportsget, listRetrieve analysis reports for parsers
parserValidationReportsgetGet the validation report for a parser
parserParsingErrorslistList parsing errors from parser validation
dataTapscreate, delete, get, list, updateManage data taps that capture and route log data
feedPacksget, listBrowse bundled feed packs
feedServiceAccountsfetchServiceAccountForCustomerGet service account details used for feed customer authentication
feedSourceTypeSchemaslist, listLogTypeSchemasBrowse available feed source type schemas
feedscreate, delete, disable, enable, generateSecret, get, importPushLogs, list, scheduleTransfer, updateFull lifecycle management of ingestion feeds
forwarderscreate, delete, generateForwarderFiles, get, importStatsEvents, list, updateManage on-premises Google SecOps forwarders
collectorscreate, delete, get, list, updateManage log collectors attached to forwarders
ingestionLogLabelslistList labels used in the ingestion pipeline
ingestionLogNamespaceslistList namespaces used in the ingestion pipeline
webhookscreate, delete, exportLogs, get, getLogs, getStatistics, list, revokeUrl, update, webhookIngestionManage and use webhook ingestion endpoints

Operation Details

events

UDM events are the normalised records stored in Google SecOps. All event operations use API version v1.

events.batchGet

Retrieve multiple UDM events in a single request.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/projects/{project}/locations/{location}/instances/{instance}/events:batchGet
ParameterTypeRequiredDescription
idsstringYesComma-separated list of event IDs to retrieve

events.get

Retrieve a single UDM event by resource name.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/projects/{project}/locations/{location}/instances/{instance}/events/{name}
ParameterTypeRequiredDescription
namestringYesResource name of the event

events.fetchEnrichedEvent

Retrieve a UDM event with additional enrichment data (entity context, threat intelligence).

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/projects/{project}/locations/{location}/instances/{instance}/events:fetchEnrichedEvent
ParameterTypeRequiredDescription
idstringYesID of the event to fetch with enrichment

events.import

Import UDM events directly into the Google SecOps instance.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/projects/{project}/locations/{location}/instances/{instance}/events:import
ParameterTypeRequiredDescription
inlineSourceobjectNoInline source object containing the UDM events to import

searchSessions

Search sessions represent asynchronous UDM Search executions. Results are paged separately.

searchSessions.listSearchedResults

List results from an existing search session.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/projects/{project}/locations/{location}/instances/{instance}/searchSessions/{id}/searchedResults
ParameterTypeRequiredDescription
namestringYesResource name of the search session
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

searchQueries

Saved search queries are user-scoped UDM query strings that can be shared via IAM policies.

searchQueries.create

Save a new UDM search query for the current user.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/projects/{project}/locations/{location}/instances/{instance}/users/{userId}/searchQueries
ParameterTypeRequiredDescription
displayNamestringYesDisplay name for the search query
querystringYesThe UDM search query string
descriptionstringNoDescription of the search query

searchQueries.delete

Delete a saved search query.

  • HTTP Method: DELETE
  • API Version: v1
  • Path: /v1/projects/{project}/locations/{location}/instances/{instance}/users/{userId}/searchQueries/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the search query to delete

searchQueries.get

Retrieve a specific saved search query.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/projects/{project}/locations/{location}/instances/{instance}/users/{userId}/searchQueries/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the search query

searchQueries.list

List all saved search queries for a user.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/projects/{project}/locations/{location}/instances/{instance}/users/{userId}/searchQueries
ParameterTypeRequiredDescription
parentstringNoParent resource path (e.g. users/{userId})
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

Known limitation: This endpoint returns HTTP 404 on some Google SecOps tiers. Verify availability on your Google SecOps subscription.

searchQueries.update

Update an existing saved search query.

  • HTTP Method: PATCH
  • API Version: v1
  • Path: /v1/projects/{project}/locations/{location}/instances/{instance}/users/{userId}/searchQueries/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the search query
displayNamestringNoNew display name
querystringNoNew query string
updateMaskstringNoComma-separated list of fields to update

searchQueries.getIamPolicy

Retrieve the IAM policy for a saved search query.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/projects/{project}/locations/{location}/instances/{instance}/users/{userId}/searchQueries/{id}:getIamPolicy
ParameterTypeRequiredDescription
resourcestringYesResource name of the search query

searchQueries.setIamPolicy

Set the IAM policy for a saved search query (used to share queries with other users).

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/projects/{project}/locations/{location}/instances/{instance}/users/{userId}/searchQueries/{id}:setIamPolicy
ParameterTypeRequiredDescription
resourcestringYesResource name of the search query
policyobjectYesIAM policy object

logProcessingPipelines

Log processing pipelines define transformation and routing rules applied to ingested log streams before they are parsed.

logProcessingPipelines.associateStreams

Associate log streams with a processing pipeline.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../logProcessingPipelines/{id}:associateStreams
ParameterTypeRequiredDescription
namestringYesResource name of the pipeline
streamsarrayYesList of stream resource names to associate

logProcessingPipelines.create

Create a new log processing pipeline.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../logProcessingPipelines
ParameterTypeRequiredDescription
displayNamestringYesDisplay name for the pipeline
configobjectNoPipeline configuration

logProcessingPipelines.delete

Delete a log processing pipeline.

  • HTTP Method: DELETE
  • API Version: v1alpha
  • Path: /v1alpha/.../logProcessingPipelines/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the pipeline

logProcessingPipelines.dissociateStreams

Remove stream associations from a processing pipeline.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../logProcessingPipelines/{id}:dissociateStreams
ParameterTypeRequiredDescription
namestringYesResource name of the pipeline
streamsarrayYesList of stream resource names to dissociate

logProcessingPipelines.fetchAssociatedPipeline

Fetch the pipeline currently associated with a log stream.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../logProcessingPipelines:fetchAssociatedPipeline
ParameterTypeRequiredDescription
streamstringYesResource name of the log stream

logProcessingPipelines.fetchSampleLogsByStreams

Fetch sample log entries for specified streams to preview pipeline transformations.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../logProcessingPipelines:fetchSampleLogsByStreams
ParameterTypeRequiredDescription
streamsstringYesComma-separated list of stream resource names
maxLogsnumberNoMaximum number of sample logs to return

logProcessingPipelines.get

Retrieve a specific log processing pipeline.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../logProcessingPipelines/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the pipeline

logProcessingPipelines.list

List all log processing pipelines.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../logProcessingPipelines
ParameterTypeRequiredDescription
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

logProcessingPipelines.testPipeline

Test a pipeline configuration against sample log entries without committing changes.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../logProcessingPipelines/{id}:testPipeline
ParameterTypeRequiredDescription
namestringYesResource name of the pipeline
sampleLogsarrayNoSample log entries to test

logProcessingPipelines.update

Update an existing log processing pipeline.

  • HTTP Method: PATCH
  • API Version: v1alpha
  • Path: /v1alpha/.../logProcessingPipelines/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the pipeline
configobjectNoUpdated pipeline configuration
updateMaskstringNoComma-separated list of fields to update

logTypes

Log types define how Google SecOps ingests and parses a category of logs. Includes built-in types (e.g. WINDOWS_DNS) and custom types.

logTypes.create

Create a new custom log type.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes
ParameterTypeRequiredDescription
logTypestringYesIdentifier for the new log type
displayNamestringNoDisplay name for the log type
descriptionstringNoDescription of the log type

logTypes.generateEventTypesSuggestions

Generate UDM event type suggestions for a log type based on sample log entries.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes:generateEventTypesSuggestions
ParameterTypeRequiredDescription
logTypeIdstringYesID of the log type
sampleLogsarrayNoSample raw log entries

logTypes.getLogTypeSetting

Retrieve settings for a specific log type.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes:getLogTypeSetting
ParameterTypeRequiredDescription
logTypeIdstringYesID of the log type

Known limitation: Returns HTTP 404 on some Google SecOps tiers. Verify availability on your Google SecOps subscription.

logTypes.legacySubmitParserExtension

Submit a parser extension using the legacy submission endpoint.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes:legacySubmitParserExtension
ParameterTypeRequiredDescription
logTypeIdstringYesID of the log type
parserExtensionstringYesParser extension content (CBN format)

logTypes.list

List all available log types in the Google SecOps instance.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes
ParameterTypeRequiredDescription
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response
filterstringNoFilter expression

logTypes.runParser

Run the log type parser against a sample raw log entry to preview parsing output.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes:runParser
ParameterTypeRequiredDescription
logTypeIdstringYesID of the log type
sampleLogstringYesRaw log entry to parse

logTypes.runAnalysis

Run analysis on a log type to evaluate parser coverage and quality.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../logTypes:runAnalysis
ParameterTypeRequiredDescription
logTypeIdstringYesID of the log type

logTypes.search

Search for log types matching specific criteria.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../logTypes:search
ParameterTypeRequiredDescription
querystringNoSearch query string
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

logTypes.updateLogTypeSetting

Update settings for a specific log type.

  • HTTP Method: PATCH
  • API Version: v1
  • Path: /v1/.../logTypes:updateLogTypeSetting
ParameterTypeRequiredDescription
logTypeIdstringYesID of the log type
settingobjectYesUpdated log type setting object
updateMaskstringNoComma-separated list of fields to update

logTypeSettings

logTypeSettings.list

List settings for all log types in the Google SecOps instance.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/logTypeSettings
ParameterTypeRequiredDescription
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

Known limitation: Returns HTTP 404 on some Google SecOps tiers. Verify availability on your Google SecOps subscription.


logTypeAnalysisReports

Analysis reports are generated asynchronously after calling logTypes.runAnalysis.

logTypeAnalysisReports.get

Retrieve a specific log type analysis report.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../logTypes/{logTypeId}/analysisReports/{reportId}
ParameterTypeRequiredDescription
namestringYesResource name of the analysis report

logTypeAnalysisReports.list

List analysis reports for a log type.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../logTypes/{logTypeId}/analysisReports
ParameterTypeRequiredDescription
parentstringYesResource name of the log type
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

logs

Raw log operations allow direct import and retrieval of unprocessed log entries associated with a specific log type.

logs.import

Import raw log entries for a specific log type.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/logs:import
ParameterTypeRequiredDescription
logTypestringYesID of the log type
entriesarrayYesList of raw log entry strings

logs.list

List raw log entries for a specific log type within a time window.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/logs
ParameterTypeRequiredDescription
logTypestringYesID of the log type
startTimestringNoStart of the time range (RFC3339 format, e.g. 2024-01-01T00:00:00Z)
endTimestringNoEnd of the time range (RFC3339 format)
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

logs.classify

Classify raw log entries to automatically determine their log type.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../logs:classify
ParameterTypeRequiredDescription
entriesarrayYesList of raw log entry strings to classify

parserExtensions

Parser extensions supplement built-in parsers with custom Google SecOps Border Network (CBN) parsing logic.

parserExtensions.activate

Activate a parser extension for a log type.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parserExtensions/{id}:activate
ParameterTypeRequiredDescription
namestringYesResource name of the parser extension

parserExtensions.create

Create a new parser extension for a log type.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parserExtensions
ParameterTypeRequiredDescription
logTypeIdstringYesID of the log type
parserExtensionstringYesParser extension content in CBN format

parserExtensions.delete

Delete a parser extension.

  • HTTP Method: DELETE
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parserExtensions/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the parser extension

parserExtensions.get

Retrieve a specific parser extension.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parserExtensions/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the parser extension

parserExtensions.list

List all parser extensions for a log type.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parserExtensions
ParameterTypeRequiredDescription
parentstringYesResource name of the log type
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

extensionValidationReports

Validation reports are generated when a parser extension is submitted or activated.

extensionValidationReports.get

Retrieve a specific extension validation report.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parserExtensions/{extId}/extensionValidationReports/{reportId}
ParameterTypeRequiredDescription
namestringYesResource name of the validation report

extensionValidationReports.list

List validation reports for a parser extension.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parserExtensions/{extId}/extensionValidationReports
ParameterTypeRequiredDescription
parentstringYesResource name of the parser extension
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

extensionValidationReports.listValidationErrors

List individual validation errors from a specific extension validation report.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parserExtensions/{extId}/extensionValidationReports/{reportId}/validationErrors
ParameterTypeRequiredDescription
parentstringYesResource name of the validation report
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

extensionParsingErrors

extensionParsingErrors.list

List parsing errors from a parser extension validation report.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parserExtensions/{extId}/validationReports/{reportId}/parsingErrors
ParameterTypeRequiredDescription
parentstringYesResource name of the validation report
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

parserExtensionValidationReports

parserExtensionValidationReports.get

Retrieve the summary validation report for a parser extension.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parserExtensions/{extId}/validationReports/{reportId}
ParameterTypeRequiredDescription
namestringYesResource name of the validation report

parsers

Parsers convert raw log entries into Google SecOps UDM events using CBN (Google SecOps Border Network) rules.

parsers.activate

Activate a custom parser for a log type.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers/{id}:activate
ParameterTypeRequiredDescription
namestringYesResource name of the parser

parsers.activateReleaseCandidateParser

Promote the release candidate parser to active for a log type.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers:activateReleaseCandidateParser
ParameterTypeRequiredDescription
logTypeIdstringYesID of the log type

parsers.copy

Copy an existing parser to create a new one, optionally targeting a different log type.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers/{id}:copy
ParameterTypeRequiredDescription
namestringYesResource name of the parser to copy
targetLogTypeIdstringNoTarget log type ID for the copied parser

parsers.create

Create a new custom parser for a log type.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers
ParameterTypeRequiredDescription
logTypeIdstringYesID of the log type
textstringYesParser content in CBN format

parsers.deactivate

Deactivate an active custom parser (reverts to the default Google SecOps parser).

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers/{id}:deactivate
ParameterTypeRequiredDescription
namestringYesResource name of the parser

parsers.delete

Delete a custom parser.

  • HTTP Method: DELETE
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the parser

parsers.fetchParserCandidates

Fetch candidate parsers suggested for a log type.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers:fetchParserCandidates
ParameterTypeRequiredDescription
logTypeIdstringYesID of the log type

parsers.get

Retrieve a specific parser.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the parser

parsers.list

List all parsers for a log type.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers
ParameterTypeRequiredDescription
parentstringYesResource name of the log type
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

Known limitation: Requires a valid log type resource path segment. Returns HTTP 404 if the log type ID is not provided correctly.

parsers.runAnalysis

Run analysis on a parser to evaluate its quality and coverage.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../logTypes/{logTypeId}/parsers/{id}:runAnalysis
ParameterTypeRequiredDescription
namestringYesResource name of the parser

parsers.update

Update an existing parser's content.

  • HTTP Method: PATCH
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the parser
textstringNoUpdated parser content (CBN format)
updateMaskstringNoComma-separated list of fields to update

parserAnalysisReports

parserAnalysisReports.get

Retrieve a specific parser analysis report.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../logTypes/{logTypeId}/parsers/{parserId}/analysisReports/{reportId}
ParameterTypeRequiredDescription
namestringYesResource name of the analysis report

parserAnalysisReports.list

List analysis reports for a parser.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../logTypes/{logTypeId}/parsers/{parserId}/analysisReports
ParameterTypeRequiredDescription
parentstringYesResource name of the parser
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

parserValidationReports

parserValidationReports.get

Retrieve the validation report for a parser.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers/{parserId}/validationReports/{reportId}
ParameterTypeRequiredDescription
namestringYesResource name of the validation report

parserParsingErrors

parserParsingErrors.list

List parsing errors from a parser validation report.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../logTypes/{logTypeId}/parsers/{parserId}/validationReports/{reportId}/parsingErrors
ParameterTypeRequiredDescription
parentstringYesResource name of the validation report
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

dataTaps

Data taps capture log data at a specific point in the ingestion pipeline and route it to an alternate destination.

dataTaps.create

Create a new data tap.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../dataTaps
ParameterTypeRequiredDescription
displayNamestringYesDisplay name for the data tap
configobjectNoData tap configuration

dataTaps.delete

Delete a data tap.

  • HTTP Method: DELETE
  • API Version: v1alpha
  • Path: /v1alpha/.../dataTaps/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the data tap

dataTaps.get

Retrieve a specific data tap.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../dataTaps/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the data tap

dataTaps.list

List all data taps.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../dataTaps
ParameterTypeRequiredDescription
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

dataTaps.update

Update an existing data tap.

  • HTTP Method: PATCH
  • API Version: v1alpha
  • Path: /v1alpha/.../dataTaps/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the data tap
configobjectNoUpdated data tap configuration
updateMaskstringNoComma-separated list of fields to update

feedPacks

Feed packs are curated bundles of pre-configured feeds. They are read-only in the API; you browse them and then deploy individual feeds from a pack.

feedPacks.get

Retrieve a specific feed pack.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../feedPacks/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the feed pack

feedPacks.list

List all available feed packs.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../feedPacks
ParameterTypeRequiredDescription
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

feedServiceAccounts

feedServiceAccounts.fetchServiceAccountForCustomer

Fetch the service account details used for feed customer authentication. This is the SA that Google SecOps uses to pull data from external sources on your behalf; grant it read access to your data source (e.g. S3 bucket, GCS bucket).

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../feedServiceAccounts:fetchServiceAccountForCustomer

No parameters required.


feedSourceTypeSchemas

Feed source type schemas describe the configuration fields available for each Google SecOps feed type.

feedSourceTypeSchemas.list

List all available feed source type schemas.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../feedSourceTypeSchemas
ParameterTypeRequiredDescription
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

feedSourceTypeSchemas.listLogTypeSchemas

List log type schemas for a specific feed source type.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../feedSourceTypeSchemas/{sourceTypeId}/logTypeSchemas
ParameterTypeRequiredDescription
parentstringYesResource name of the feed source type schema
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

feeds

Feeds are configured pull or push ingestion channels. Google SecOps polls external sources (cloud storage, APIs, SIEMs) or receives pushed data on a schedule.

feeds.create

Create a new ingestion feed.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../feeds
ParameterTypeRequiredDescription
displayNamestringYesDisplay name for the feed
feedSourceTypestringYesSource type identifier (use feedSourceTypeSchemas.list to discover values)
configobjectNoFeed configuration object — structure depends on feedSourceType

feeds.delete

Delete an ingestion feed.

  • HTTP Method: DELETE
  • API Version: v1
  • Path: /v1/.../feeds/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the feed

feeds.disable

Disable an active feed without deleting it.

  • HTTP Method: DELETE
  • API Version: v1
  • Path: /v1/.../feeds/{id}:disable
ParameterTypeRequiredDescription
namestringYesResource name of the feed

feeds.enable

Enable a previously disabled feed.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../feeds/{id}:enable
ParameterTypeRequiredDescription
namestringYesResource name of the feed

feeds.generateSecret

Generate a new ingestion secret for a push-type feed. The secret is used by external systems to authenticate when pushing logs.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../feeds/{id}:generateSecret
ParameterTypeRequiredDescription
namestringYesResource name of the feed

feeds.get

Retrieve a specific feed configuration.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../feeds/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the feed

feeds.importPushLogs

Push log data directly to Google SecOps through a push-type feed.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../feeds/{id}:importPushLogs
ParameterTypeRequiredDescription
namestringYesResource name of the feed
logsarrayYesLog entries to import

feeds.list

List all ingestion feeds.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../feeds
ParameterTypeRequiredDescription
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

feeds.scheduleTransfer

Schedule a data transfer for a feed.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../feeds/{id}:scheduleTransfer
ParameterTypeRequiredDescription
namestringYesResource name of the feed

feeds.update

Update the configuration of an existing feed.

  • HTTP Method: PATCH
  • API Version: v1alpha
  • Path: /v1alpha/.../feeds/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the feed
configobjectNoUpdated feed configuration
updateMaskstringNoComma-separated list of fields to update

forwarders

Forwarders are Google SecOps software agents deployed on-premises or in cloud VMs that collect logs and relay them to Google SecOps.

forwarders.create

Create a new Google SecOps forwarder.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../forwarders
ParameterTypeRequiredDescription
displayNamestringYesDisplay name for the forwarder
configobjectNoForwarder configuration

forwarders.delete

Delete a forwarder.

  • HTTP Method: DELETE
  • API Version: v1alpha
  • Path: /v1alpha/.../forwarders/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the forwarder

forwarders.generateForwarderFiles

Generate the configuration files (YAML/binary) needed to deploy a forwarder agent.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../forwarders/{id}:generateForwarderFiles
ParameterTypeRequiredDescription
namestringYesResource name of the forwarder

forwarders.get

Retrieve a specific forwarder.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../forwarders/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the forwarder

forwarders.importStatsEvents

Import telemetry and stats events from a forwarder.

  • HTTP Method: POST
  • API Version: v1
  • Path: /v1/.../forwarders/{id}:importStatsEvents
ParameterTypeRequiredDescription
namestringYesResource name of the forwarder
eventsarrayYesStats event entries

forwarders.list

List all forwarders.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../forwarders
ParameterTypeRequiredDescription
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

forwarders.update

Update an existing forwarder configuration.

  • HTTP Method: PATCH
  • API Version: v1alpha
  • Path: /v1alpha/.../forwarders/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the forwarder
configobjectNoUpdated forwarder configuration
updateMaskstringNoComma-separated list of fields to update

collectors

Collectors are sub-resources of forwarders. Each collector defines a specific log source (syslog port, file path, Kafka topic, etc.) and its associated log type.

collectors.create

Create a new collector on a forwarder.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../forwarders/{forwarderId}/collectors
ParameterTypeRequiredDescription
parentstringYesResource name of the parent forwarder
displayNamestringYesDisplay name for the collector
configobjectNoCollector configuration (source type, log type, port/path, etc.)

collectors.delete

Delete a collector from a forwarder.

  • HTTP Method: DELETE
  • API Version: v1alpha
  • Path: /v1alpha/.../forwarders/{forwarderId}/collectors/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the collector

collectors.get

Retrieve a specific collector.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../forwarders/{forwarderId}/collectors/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the collector

collectors.list

List all collectors for a forwarder.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../forwarders/{forwarderId}/collectors
ParameterTypeRequiredDescription
parentstringYesResource name of the parent forwarder
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

collectors.update

Update an existing collector.

  • HTTP Method: PATCH
  • API Version: v1alpha
  • Path: /v1alpha/.../forwarders/{forwarderId}/collectors/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the collector
configobjectNoUpdated collector configuration
updateMaskstringNoComma-separated list of fields to update

ingestionLogLabels

ingestionLogLabels.list

List all ingestion log labels used in the Google SecOps ingestion pipeline.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../ingestionLogLabels
ParameterTypeRequiredDescription
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

Known limitation: This endpoint rejects standard pageSize query parameters on some Google SecOps instances. Omit pageSize if you receive INVALID_ARGUMENT errors.


ingestionLogNamespaces

ingestionLogNamespaces.list

List all namespaces used in the Google SecOps ingestion pipeline.

  • HTTP Method: GET
  • API Version: v1
  • Path: /v1/.../ingestionLogNamespaces
ParameterTypeRequiredDescription
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

webhooks

Webhooks provide push ingestion endpoints — external systems POST log data to a Google SecOps-hosted URL, and Google SecOps ingests it immediately.

webhooks.webhookIngestion

Send log data to Google SecOps via a webhook ingestion endpoint.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../webhooks/{id}:WebhookIngestion
ParameterTypeRequiredDescription
namestringYesResource name of the webhook
datastringYesBase64-encoded or raw log payload

webhooks.create

Create a new webhook ingestion endpoint.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../webhooks
ParameterTypeRequiredDescription
displayNamestringYesDisplay name for the webhook
logTypestringNoLog type to associate with this webhook

webhooks.delete

Delete a webhook.

  • HTTP Method: DELETE
  • API Version: v1alpha
  • Path: /v1alpha/.../webhooks/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the webhook

webhooks.exportLogs

Export logs received by a webhook to a destination.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../webhooks/{id}:exportLogs
ParameterTypeRequiredDescription
namestringYesResource name of the webhook
startTimestringNoStart of the time range (RFC3339 format)
endTimestringNoEnd of the time range (RFC3339 format)

webhooks.get

Retrieve a specific webhook.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../webhooks/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the webhook

webhooks.getLogs

Retrieve recent log entries received by a webhook.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../webhooks/{id}:getLogs
ParameterTypeRequiredDescription
namestringYesResource name of the webhook
pageSizenumberNoMaximum number of log entries to return
pageTokenstringNoPagination token from a previous response

webhooks.getStatistics

Retrieve throughput and error rate statistics for a webhook.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../webhooks/{id}:getStatistics
ParameterTypeRequiredDescription
namestringYesResource name of the webhook
startTimestringNoStart of the time range (RFC3339 format)
endTimestringNoEnd of the time range (RFC3339 format)

webhooks.list

List all webhook ingestion endpoints.

  • HTTP Method: GET
  • API Version: v1alpha
  • Path: /v1alpha/.../webhooks
ParameterTypeRequiredDescription
pageSizenumberNoMaximum number of results to return
pageTokenstringNoPagination token from a previous response

webhooks.update

Update an existing webhook.

  • HTTP Method: PATCH
  • API Version: v1alpha
  • Path: /v1alpha/.../webhooks/{id}
ParameterTypeRequiredDescription
namestringYesResource name of the webhook
displayNamestringNoNew display name
updateMaskstringNoComma-separated list of fields to update

webhooks.revokeUrl

Revoke the current webhook ingestion URL and generate a new one. Use when the URL has been compromised.

  • HTTP Method: POST
  • API Version: v1alpha
  • Path: /v1alpha/.../webhooks/{id}:revokeUrl
ParameterTypeRequiredDescription
namestringYesResource name of the webhook

Known Limitations

The following operations are unavailable on some Google SecOps tiers or require specific resource IDs that are only available through upstream operations. They are implemented in the connector but will be skipped in automated evidence tests.

OperationLimitationWorkaround
logTypes.getLogTypeSettingReturns HTTP 404 on instances that do not have per-log-type settings enabledUse logTypeSettings.list to check what settings are available
logTypeSettings.listReturns HTTP 404 on some Google SecOps tiersConfirm tier supports this endpoint; use logTypes.list instead
searchQueries.listReturns HTTP 404 on some Google SecOps tiersVerify your subscription includes saved search query sharing
parsers.listRequires a concrete log type ID in the path; returns HTTP 404 if called without oneObtain a valid log type ID via logTypes.list first
ingestionLogLabels.listReturns INVALID_ARGUMENT when pageSize is supplied on some instancesCall the endpoint without pageSize; the API returns all labels in a single response

Best Practices

  1. Use logTypes.list before parser operations. Parser, parser extension, and analysis report operations all require a concrete log type ID. Always retrieve the log type list first and resolve the exact log type identifier before making downstream calls.

  2. Paginate all list operations. All list operations accept pageSize and pageToken. Request a reasonable pageSize (e.g. 100–500) and follow nextPageToken in the response until it is empty.

  3. Test parsers before activating. Use logTypes.runParser with a sample log entry and logProcessingPipelines.testPipeline to validate output before activating a parser or deploying a pipeline.

  4. Retrieve the feed service account before creating feeds. Use feedServiceAccounts.fetchServiceAccountForCustomer to get the Google SecOps-managed SA email, then grant it the necessary read permissions on your data source (GCS bucket, S3 bucket, etc.) before creating a feed.

  5. Rotate webhook secrets after URL revocation. After calling webhooks.revokeUrl, update the webhook URL in all systems that POST to it. Maintain a short rotation window to avoid data loss.

  6. Least-privilege IAM. Use roles/chronicle.viewer for monitoring workflows. Only grant roles/chronicle.editor or roles/chronicle.admin to credentials used by automation that performs write operations.

  7. Handle 429 responses. The connector retries automatically up to 3 times with back-off. If persistent 429 responses occur outside of the connector, reduce request frequency or contact Google Cloud support to increase quota.

  8. Use updateMask on PATCH operations. Always specify updateMask to avoid unintentionally overwriting fields not included in the request body.

  9. RFC3339 time formats. All startTime and endTime parameters must be in RFC3339 format (e.g. 2024-06-01T00:00:00Z). Omitting the timezone suffix may cause API errors.

  10. Use v1alpha endpoints cautiously. Endpoints on v1alpha are subject to breaking changes without advance notice. Prefer v1 equivalents where available.


Troubleshooting

IssuePossible CauseSolution
401 UnauthorizedService account key is invalid or expiredVerify the JSON key is complete and correctly pasted; rotate the key if it has been revoked
403 PERMISSION_DENIEDService account lacks the required Google SecOps IAM roleGrant roles/chronicle.viewer or roles/chronicle.editor as appropriate on the GCP project
404 Not Found on list/getResource ID is incorrect or the feature is not available on this Google SecOps tierVerify the resource ID exists; check whether the endpoint is supported on your Google SecOps subscription
404 Not Found on parser operationsLog type ID not provided or invalidObtain the log type ID via logTypes.list and use it in the resource path
400 INVALID_ARGUMENTA query parameter is not supported by the endpoint (e.g. pageSize rejected by ingestionLogLabels.list)Remove the rejected parameter and retry; consult the Known Limitations section
429 Too Many RequestsAPI rate limit exceededThe connector retries automatically; if persistent, reduce call frequency or request a quota increase
UNAUTHENTICATEDOAuth2 token has expired or scope is insufficientVerify cloud-platform scope is present in the service account; check system clock drift
Field not found in updateMaskupdateMask references a non-existent field nameVerify field names against the Google SecOps API documentation for the resource
Connection timeoutNetwork connectivity issue or incorrect region valueVerify the region prefix and that outbound HTTPS traffic to *.googleapis.com is allowed

Support

For issues with this integration, provide:

  • The operation name attempted (e.g. parsers.create)
  • The error message and HTTP status code
  • The Google SecOps region and instance ID
  • The parameters used (excluding the service account JSON key)

For Google SecOps API reference documentation, see the Google SecOps API documentation.

Updated: 2026-07-07