Running Actions – Form-Factor & Action Type Limitations

Each Action type has different capabilities and run-time parameters, just as Actors installed from various form-factors have limitations. In this section, you will find information discussing available configuration options when selecting an Action to run.

Port Scan Action Limitations

  • Ports 22 and 443 will be skipped when running a Port Scan Action on the management interface to a Destination Actor that is set to communicate in Push mode. This is because Actors in Push mode run a web server on port 443 to listen for inbound management traffic from the Director and port 22 listens for SSH communication. These ports are not skipped for the Actor's test or monitor interfaces when the Actor is in Push mode.
  • Ports 443 will be skipped when running a Port Scan Action on the management interface to a Windows Destination Actor
  • The Scan Both Directions option that will run the Action twice, once in each direction (Actor A to Actor B and then Actor B to Actor A).

IMPORTANT: The time it takes to run a Port Scan Action is based on the total number of ports, number of closed ports within the total, timeout value when a port is closed, and the number of seconds the Action is set to sleep between each port during the scan. For example, VID A100-291 scans the Top 1000 ports and has a 0.05 second sleep time. This means the Action has 50 seconds of wait time when it runs. If an Action included 65,000 ports to scan with the same sleep-time value, the wait time when that Action runs would be 54 minutes (3,250 seconds).

Limitations for Windows Actors

The following Action types are not currently supported:

  • Email Actions
  • ICMP tunnel file transfer Actions
  • SSH tunnel file transfer Actions
  • SCP file transfer Actions

Limitations for Apple® Macintosh® Actors

File Transfer Actions that require DNS or ICMP tunnels cannot run on Mac Actors. All other File Transfer Actions run as expected.

Notes for Email Actions

When running Email Actions, the list of Destination Actors is not restricted by the defined communications (CTTA) for the Source Actor.

  • May 20, 2022
  • September 21, 2023
In This Article