Home
Arc
Learn how Arc provides endpoint security in high availability environments.
Arc
Configuration
Details on how to configure Arc.
Local UI
The default method to manage Arc is through the parent system software. However, it is also possible to manage Arc through a local UI.
Latest run
The Latest run section shows the status and mode of the latest run that was executed.

Arc
Learn how Arc provides endpoint security in high availability environments.
- Arc
  - Introduction
    An overview of Arc.
  - Requirements
    The machine and network requirements necessary to use Arc.
  - Preparation
    Information on how to import Arc packages, and install a license.
  - Configuration
    Details on how to configure Arc.
    - Configure an Arc sensor in Guardian
      You can configure an individual Arc sensor in Guardian directly from the Sensors details page for the related sensor.
    - Configure an Arc sensor in Vantage
      You can configure an individual Arc sensor in Vantage directly from the Sensors details page for the related sensor.
    - Local UI
      The default method to manage Arc is through the parent system software. However, it is also possible to manage Arc through a local UI.
      - Offline archives
        The Offline archives page shows a list of all the offline archives.
      - Configuration
        The Configuration page lets you define upstream connection settings, execution options, protection preferences, and traffic monitoring parameters for the Arc sensor.
      - Status
        The Status section shows a list of all the required dependencies for the selected sensor, and the installation status for each dependency.
      - Latest run
        The Latest run section shows the status and mode of the latest run that was executed.
      - Asset inventory
        The Asset inventory section displays the status of Discovery and Smart Polling. These features provide visibility into networked devices and asset details.
      - Last 100 runs
        The Last 100 runs section shows the status of the last 100 runs.
      - Open the local UI
        The local UI lets you manage Arc without the use of a parent system software. It gives you access to the Status page to monitor the status of Arc executions, and the Configuration page to configure Arc executions. You can double-click the executable file to open it, or use the command-line interface (CLI),
    - Shell commands
      A list of available shell commands.
  - Deployment
    Information on how to deploy Arc. This includes details for manual and automatic deployments, and deployment through a mobile device management (MDM) system.
  - Execution
    Information on the different modes that you can use with Arc.
  - Troubleshooting
    Troubleshooting procedures to help you solve problems that might occur when you use Arc.
- Arc Embedded
  Arc Embedded is a cybersecurity sensor built into PLCs to provide real-time visibility and deep threat detection within industrial control systems.
- Print format documentation
  A list of all the print-format documentation that is available for Arc and Arc Embedded.

Latest run

The Latest run section shows the status and mode of the latest run that was executed.

Latest run status showing 'Pending' with 0% progress and execution mode 'Online - Paired' — Figure 1. Latest run

Current status

This shows the current status of the latest run. A percentage value will show.

Execution mode

This shows the current execution mode and connectivity status.

Not available - while not running.

Disconnected - while in Offline mode.

Sending - standard behavior, data goes upstream.

Sending, Buffering - data is being sent and buffering is happening due to incoming data.

Sending, Dropping - data is being sent and dropped because incoming data and buffering limits were reached.

Disconnected (never connected) - network was absent before Arc could ever connect to the upstream.

Buffering (never connected) - network was absent before Arc could ever connect to the upstream: buffering started due to incoming data.

Dropping (never connected) - network was absent before Arc could ever connect to the upstream: dropping started due to reaching buffering limits.

Disconnected (last connection at dd-mm-yyyy hh:mm:ss) - network was absent since the indicated time.

Buffering (last connection at dd-mm-yyyy hh:mm:ss) - network was absent since the indicated time: buffering started due to incoming data.

Dropping (last connection at dd-mm-yyyy hh:mm:ss) - network was absent since the indicated time: dropping started due to incoming data and buffering limits were reached.