Trend Micro Apex Central

Integration version: 4.0

Note: This integration uses one or more open source components.You can download a copy of the full source code of this integration from thestorage bucket.

How to obtain API Key

For more information about how to obtain API Key, seeAdding an Application.

Configure Trend Micro Apex Central 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
API RootStringhttp://x.x.x.xYesAPI root of the Trend Micro Apex Central instance.
Application IDStringN/AYesApplication ID of the Trend Micro Apex Central instance.
API KeyPasswordN/AYesAPI Key of the Trend Micro Apex Central instance.
Verify SSLCheckboxCheckedYesIf enabled, verify the SSL certificate for the connection to the Trend Micro Apex Central server is valid.
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 to Trend Micro Apex Central with parameters provided at theintegration configuration page in the Google Security Operations Marketplace tab.

Parameters

N/A

Run On

This action doesn't run on entities.

Action Results

Script Result
Script Result NameValue Options
is_successis_success=False
is_successis_success=True
Case Wall
Result TypeValue / DescriptionType
Output message*

If successful:
print Successfully connected to the Trend Micro Apex Central server with the provided connection parameters!

Not successful: Failed to connect to the Trend Micro Apex Central server! Error: {0}".format(exception.stacktrace)

General

Enrich Entities

Description

Enrich entities with information from Trend Micro Apex Central. Supportedentities: IP Address, MAC Address, Hostname, URL, Hash.

Note: Only SHA-1 hashes are supported.

Parameters

entity
NameDefault ValueIs MandatoryDescription
Create Endpoint InsightTrueNoIf enabled, action will create an insight consisting of the information regarding the endpoints that were enriched.
Create UDSO InsightTrueNoIf enabled, action will create an insight consisting of the information regarding the entities that matched UDSO.
Mark UDSO EntitiesTrueNoIf enable, action will mark all of the entities that were seen in the User-Defined Suspicious Objects list as suspicious.
Extract DomainFalseNoIf enabled, action will extract domain part of the URL entity and use it for enrichment.

Run On

This action runs on the following entities:

  • IP Address
  • Mac Address
  • Hostname
  • URL
  • Hash

Action Results

Script Result
Script Result NameValue Options
is_successis_success=False
is_successis_success=True
Entity Enrichment

Host, IP, MAC

Enrichment Field NameLogic - When to apply
ip_addressReturns if it exists in JSON result.
mac_addressReturns if it exists in JSON result.
hostnameReturns if it exists in JSON result.
has_endpoint_sensorReturns if it exists in JSON result.
isolation_statusReturns if it exists in JSON result.
ad_domainReturns if it exists in JSON result.

URL, Hash, IP

Enrichment Field NameLogic - When to apply
typeReturns if it exists in JSON result.
noteReturns if it exists in JSON result.
actionReturns if it exists in JSON result.
expirationReturns if it exists in JSON result.
Case Wall
Result TypeValue / DescriptionType
Output message*

The action should not fail nor stop a playbook execution:

  • if successful for 1 entity - Successfully retrieved information about the following entities from Trend Micro Apex Central: {\n entity.identifier}

  • if not successful for 1 entity - Action wasn't able to retrieve information about the following entities from Trend Micro Apex Central: {\n entity.identifier}

  • not successful for all - No entities were enriched using information from Trend Micro Apex Central

The action should fail and stop a playbook execution:

  • Fatal error, invalid creds, API root - Error executing action "Enrich Entities". Reason: {error traceback}
General
Case Wall Table

Name: Found Endpoints

Column:

IP Address

MAC Address

Hostname

Has Endpoint Sensor

Isolation Status

AD Domain

(Host, IP, MAC)
Case Wall Table

Name: Found UDSO

Column:

Entity

Note

Action

(URL, Hash, IP)

Create File UDSO

Description

Create a User-defined suspicious object based on a file in Trend Micro ApexCentral.

Known Issues

When working with .eml files, the action will not return the JSON result.

Parameters

NameDefault ValueIs MandatoryDescription
File PathsN/AYesSpecify a comma-separated list of file paths that needs to be used to created a UDSO.
Action

Block

Possible Values:

Block

Log

Quarantine

YesSpecify what action should be applied to the UDSO.
NoteN/AFalseSpecify an additional note for the provided UDSO. Warning: the note can't contain more than 256 characters.
Expire In (Days)N/AFalseSpecify in how many days the UDSO should expire. If nothing is provided, UDSO will never expire.

Run On

This action doesn't run on entities.

Action Results

Script Result
Script Result NameValue Options
is_successis_success=False
is_successis_success=True
Case Wall
CaseSuccessFailMessage
if successful for 1 filetruefalseSuccessfully created UDSO based on the following files in Trend Micro Apex Central: {\n file paths}
if not successful for 1 entitytruefalseAction wasn't able to create UDSO based on the following files in Trend Micro Apex Central: {\n file paths}
If already existtruefalseThe following UDSO already exist in Trend Micro Apex Central: {\n file paths}
not successful for allfalsefalseNo UDSO were created in Trend Micro Apex Central.
Fatal error, invalid creds, API rootfalsetrueError executing action "Create File UDSO". Reason: {error traceback}
If note > 256 charsfalsetrueError executing action "Create File UDSO". Reason: note can't contain more than 256 characters.

Create Entity UDSO

Description

Create a User-defined suspicious object based on the entities in Trend MicroApex Central. Supported entities: IP, URL, Hash.

Note: Only SHA-1 hashes are supported.Note: IP is of IPV4 type. URL has to start with http:// or https:// (maximumlength of 2047 character). File Hash (SHA-1 only and maximum length of 40characters).

Parameters

NameDefault ValueIs MandatoryDescription
Action

Block

Possible Values:

Block

Log

YesSpecify what action should be applied to the UDSO.
NoteN/AFalseSpecify an additional note for the provided UDSO. Warning: the note can't contain more than 256 characters.
Expire In (Days)N/AFalseSpecify in how many days the UDSO should expire. If nothing is provided, UDSO will never expire.

Run On

This action runs on the following entities:

  • IP Address
  • URL
  • Hash

Action Results

Script Result
Script Result NameValue Options
is_successis_success=False
is_successis_success=True
Case Wall
CaseSuccessFailMessage
if successful for 1 entitytruefalseSuccessfully created UDSO based on the following entities in Trend Micro Apex Central: {\n entity.identifier}
if not successful for 1 entitytruefalseAction wasn't able to create UDSO based on the following entities in Trend Micro Apex Central: {\n entity.identifier}
If already existtruefalseThe following UDSO already exist in Trend Micro Apex Central: {\n entity.identifier}
not successful for allfalsefalseNo UDSO were created in Trend Micro Apex Central.
Fatal error, invalid creds, API rootfalsetrueError executing action "Create Entity UDSO". Reason: {error traceback}
If note > 256 charsfalsetrueError executing action "Create Entity UDSO". Reason: note can't contain more than 256 characters.

Unisolate Endpoints

Description

Unisolate endpoints in Trend Micro Apex Central. Supported entities: IP, Mac,Hostname.

Note: this action can take several minutes to finish, so consider increasing thetimeout in the IDE.

Parameters

NameDefault ValueIs mandatoryDescription
N/AN/AN/AN/A

Run On

This action runs on the following entities:

  • IP Address
  • Mac Address
  • Hostname

Action Results

Script Result
Script Result NameValue Options
is_successis_success=False
is_successis_success=True
Case Wall
CaseSuccessFailMessage
if successful for 1 entitytruefalseSuccessfully unisolated the following endpoints in Trend Micro Apex Central: {\n entity.identifier}
if not successful for 1 entitytruefalseAction wasn't able to unisolate the following endpoints in Trend Micro Apex Central: {\n entity.identifier}
not successful for allfalsefalseNo endpoints were unisolated in Trend Micro Apex Central.
Async MessagefalsefalseInitiated endpoint unisolation on the following endpoints: {entity.identifier}. Waiting for the unisolation to finish.
Timeout messagefalsefalse

Action initiated unisolation, but it's still pending for the following endpoints: {entity.identifier}.

Please consider increasing the timeout in the IDE.

Fatal error, invalid creds, API rootfalsetrueError executing action "Unisolate Endpoints". Reason: {error traceback}

Isolate Endpoints

Description

Isolate endpoints in Trend Micro Apex Central. Supported entities: IP, Mac,Hostname.

Note: this action can take several minutes to finish, so consider increasing thetimeout in the IDE.

Parameters

NameDefault ValueIs mandatoryDescription
N/AN/AN/AN/A

Run On

This action runs on the following entities:

  • IP Address
  • Mac Address
  • Hostname

Action Results

Script Result
Script Result NameValue Options
is_successis_success=False
is_successis_success=True
Case Wall
CaseSuccessFailMessage
if successful for 1 entitytruefalseSuccessfully isolated the following endpoints in Trend Micro Apex Central: {\n entity.identifier}
if not successful for 1 entitytruefalseAction wasn't able to isolate the following endpoints in Trend Micro Apex Central: {\n entity.identifier}
not successful for allfalsefalseNo endpoints were isolated in Trend Micro Apex Central.
Async MessagefalsefalseInitiated endpoint isolation on the following endpoints: {entity.identifier}. Waiting for the isolation to finish.
Timeout messagetruefalse

Action initiated isolation, but it's still pending for the following endpoints: {entity.identifier}.

Please consider increasing the timeout in the IDE.

Fatal error, invalid creds, API rootfalsetrueError executing action "Isolate Endpoints". Reason: {error traceback}

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.