Remote Agent Utilities

Integration version: 4.0

Configure Remote Agent Utilities integration in Google Security Operations

For detailed instructions on how to configure an integration inGoogle SecOps, seeConfigureintegrations.

Integration parameters

Use the following parameters to configure the integration:

Parameter Display NameTypeDefault ValueIs MandatoryDescription
Instance NameStringN/ANoName of the Instance you intend to configure integration for.
DescriptionStringN/ANoDescription of the Instance.
Run RemotelyCheckboxUncheckedNoCheck the field in order to run the configured integration remotely. Once checked, the option appears to select the remote user (agent).
Note: You can make changes at a later stage if needed. Once configured, theInstances can be used in Playbooks. For detailed information on configuring andsupporting multiple instances, please seeSupporting multiple instances.

Actions

Ping

Description

Test Connectivity.

Run On

This action doesn't run on entities.

Action Results

Script Result
Script Result NameValue OptionsExample
successTrue/Falsesuccess:False

Serialization

Description

The action will get the file path (relative path) as the action parameter, willserialize it to a GZIP Base64 string, and will return it in a resultJSON outputparam.

Note: The file limit size: 15 MB. The restriction will be enforced at the TIPlevel.

Parameters

Parameter Display NameTypeIs MandatoryDescription
File PathStringYesFull path of the file

Run On

This action doesn't run on entities.

Action Results

Script Result
Script Result NameValue OptionsExample
file_bs64N/AN/A
Case Wall
Result TypeValue / DescriptionType
Output message*

In case of general error: "{{Action didn't complete due to error: {error}"}}, result value should be set to false and the action should fail

If action completed successfully: "Successfully serialized <file path>"

If action failed to run: "Failed to serialized <file path>"

General

Deserialization

Description

The action will get the GZIP Base64 string from the JSON result and will storethe data from the original file in a new file in the destination path in theaction.

Parameters

Parameter Display NameTypeIs MandatoryDescription
File NameStringYes

File Name

The purpose is to get as a placeholder from prev action (key in json result - u'file_name)

File base64StringYes

File base64

The purpose is to get as a placeholder from prev action (key in json result - u'base64_file_content)

Run On

This action doesn't run on entities.

Action Results

Script Result
Script Result NameValue OptionsExample
file_new_pathN/AN/A
Case Wall
Result TypeValue / DescriptionType
Output message*

In case of general error print: "{{Action didn't complete due to error: {error}"}}, result value should be set to false and the action should fail

If action failed to run: "Failed to deserialized file base64"

If action completed successfully: "Successfully deserialized file Base64. New file available here: <file_new_path>"

General

Need more help?Get answers from Community members and Google SecOps professionals.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-19 UTC.