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 | .png?inst-v=6798c1ab-130a-491a-a9e4-b9ecc9e7d788) |
Connected agent selected in the Connection |  |
Result Command was run on the Agent Python Executor completely and result was returned successfully | .png?inst-v=6798c1ab-130a-491a-a9e4-b9ecc9e7d788) |
Scenario 2
☑ Allow command to be run on agent |  |
Disconnected agent selected in the Connection |  |
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 |  |
Scenario 3
☑ Allow command to be run on agent | .png?inst-v=6798c1ab-130a-491a-a9e4-b9ecc9e7d788) |
NO agent selected in the Connection |  |
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 |  |
Scenario 4
☐ Allow command to be run on agent | .png?inst-v=6798c1ab-130a-491a-a9e4-b9ecc9e7d788) |
Connected agent selected in the Connection |  |
Result Command was run on the vSOC Remote Python Executor. Rest API request was redirected to run on the Agent Result was returned successfully |  |
Scenario 5
☐ Allow command to be run on agent | |
Disconnected agent selected in the Connection |  |
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 |  |
Scenario 6
☐ Allow command to be run on agent | |
NO agent selected in the Connection | .png?inst-v=6798c1ab-130a-491a-a9e4-b9ecc9e7d788) |
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 |  |
On Cloud Integration Example: VirusTotal V3 Custom Command
Scenario 1
☑ Allow command to be run on agent |  |
Connected agent selected in the Connection |  |
Result Command was run on the Agent Python Executor completely and result was returned successfully |  |
Scenario 2
☑ Allow command to be run on agent | .png?inst-v=6798c1ab-130a-491a-a9e4-b9ecc9e7d788) |
Disconnected agent selected in the Connection |  |
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 |  |
Scenario 3
☑ Allow command to be run on agent | .png?inst-v=6798c1ab-130a-491a-a9e4-b9ecc9e7d788) |
NO agent selected in the Connection |  |
Result Command was run on the vSOC Remote Python Executor completely and result was returned successfully |  |
Scenario 4
☐ Allow command to be run on agent |  |
Connected agent selected in the Connection |  |
Result Command was run on the vSOC Remote Python Executor. Rest API request was redirected to run on the Agent Result was returned successfully |  |
Scenario 5
☐ Allow command to be run on agent | |
Disconnected agent selected in the Connection |  |
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 | .png?inst-v=6798c1ab-130a-491a-a9e4-b9ecc9e7d788) |
Scenario 6
☐ Allow command to be run on agent | |
NO agent selected in the Connection | .png?inst-v=6798c1ab-130a-491a-a9e4-b9ecc9e7d788) |
Result Command was run on the vSOC Remote Python Executor completely and result was returned successfully |  |