Breadcrumbs

Agent Configuration Scenarios

Last Updated: Oct 16, 2024

Agent Configuration Scenarios

Overview

Scenario

Configuration

Status

On-Prem Integration

On Cloud Integration

1

Allow command to be run on agent

☑

Command will be run on the Agent Python Executor completely

Command will be run on the Agent Python Executor completely

Agent selected in the Connection

Connected

2

Allow command to be run on agent

☑

The execution of the command is stopped by the initial Agent Health Check. (Error Message "Proxy is invalid or closed.")

Cannot run the command at all

The execution of the command is stopped by the initial Agent Health Check. (Error Message "Proxy is invalid or closed.")

Cannot run the command at all

Agent selected in the Connection

Disconnected

3

Allow command to be run on agent

☑

Command will be run on the vSOC Remote Python Executor first.

Rest API request will fail since it cannot connect to integration inside vSOC environment

Command will be run on the vSOC Remote Python Executor completely

Agent selected in the Connection

None

4

Allow command to be run on agent

☐

Command will be run on the vSOC Remote Python Executor.

Rest API request will be redirected to run on the Agent

Command will be run on the vSOC Remote Python Executor.

Rest API request will be redirected to run on the Agent

Agent selected in the Connection

Connected

5

Allow command to be run on agent

☐

The execution of the command is stopped by the initial Agent Health Check. (Error Message "Proxy is invalid or closed.")

Cannot run the command at all

The execution of the command is stopped by the initial Agent Health Check. (Error Message "Proxy is invalid or closed.")

Cannot run the command at all

Agent selected in the Connection

Disconnected

6

Allow command to be run on agent

☐

Command will be run on the vSOC Remote Python Executor first.

Rest API request will fail since cannot connect to integration inside vSOC environment

Command will be run on the vSOC Remote Python Executor completely

Agent selected in the Connection

None

On-Premises Integration Example: IBM QRadar Custom Command

Scenario 1

☑ Allow command to be run on agent

Group 375 (1).png

Connected agent selected in the Connection
Group 394.png

Result

Command was run on the Agent Python Executor completely and result was returned successfully
Group 377 (1).png

Scenario 2

☑ Allow command to be run on agent

Group 378.png

Disconnected agent selected in the Connection
Group 395.png

Result

The execution of the command was stopped by the initial Agent Health Check. (Error Message "Proxy is invalid or closed.")

Cannot run the command at all
Group 396.png

Scenario 3

☑ Allow command to be run on agent

Group 378 (1).png

NO agent selected in the Connection
Group 397.png

Result

Command was run on the vSOC Remote Python Executor first.

Rest API request would fail since it cannot connect to integration inside vSOC environment
Group 398.png

Scenario 4

☐ Allow command to be run on agent

Group 387 (2).png

Connected agent selected in the Connection
Group 399.png

Result

Command was run on the vSOC Remote Python Executor.

Rest API request was redirected to run on the Agent

Result was returned successfully
Group 381.png

Scenario 5

☐ Allow command to be run on agent

Group 387 (2).png

Disconnected agent selected in the Connection
Group 400.png

Result

The execution of the command was stopped by the initial Agent Health Check. (Error Message "Proxy is invalid or closed.")

Cannot run the command at all
Group 401.png

Scenario 6

☐ Allow command to be run on agent

Group 387 (2).png

NO agent selected in the Connection
Group 397 (1).png

Result

Command was run on the vSOC Remote Python Executor first.

Rest API request would fail since it cannot connect to integration inside vSOC environment
Group 402.png

On Cloud Integration Example: VirusTotal V3 Custom Command

Scenario 1

☑ Allow command to be run on agent

Group 385.png

Connected agent selected in the Connection
Group 403.png

Result

Command was run on the Agent Python Executor completely and result was returned successfully
att_47_for_15007789.png

Scenario 2

☑ Allow command to be run on agent

Group 385 (1).png

Disconnected agent selected in the Connection
Group 404.png

Result

The execution of the command was stopped by the initial Agent Health Check. (Error Message "Proxy is invalid or closed.")

Cannot run the command at all
Group 405.png

Scenario 3

☑ Allow command to be run on agent

Group 385 (2).png

NO agent selected in the Connection
Group 406.png

Result

Command was run on the vSOC Remote Python Executor completely and result was returned successfully
att_48_for_15007789.png

Scenario 4

☐ Allow command to be run on agent

Group 389.png

Connected agent selected in the Connection
Group 407.png

Result

Command was run on the vSOC Remote Python Executor.

Rest API request was redirected to run on the Agent

Result was returned successfully
att_48_for_15007789 1.png

Scenario 5

☐ Allow command to be run on agent

Group 389.png

Disconnected agent selected in the Connection
Group 408.png

Result

The execution of the command was stopped by the initial Agent Health Check. (Error Message "Proxy is invalid or closed.")

Cannot run the command at all
Group 405 (1).png

Scenario 6

☐ Allow command to be run on agent

Group 389.png

NO agent selected in the Connection
Group 406 (2).png

Result

Command was run on the vSOC Remote Python Executor completely and result was returned successfully
att_49_for_15007789.png