Home
Arc
Learn how Arc provides endpoint security in high availability environments.
Configuration
Details on how to configure Arc.
Local configuration UI
The default method to manage Arc is through the parent system software. However, it is also possible to manage Arc through a local configuration UI.
Execution info(rmation)
The Execution Info section displays the status of Arc's sensors, execution modes, and network connectivity. It also provides details about service status, version, and execution controls.

Arc
Learn how Arc provides endpoint security in high availability environments.
- 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.
  - Local configuration UI
    The default method to manage Arc is through the parent system software. However, it is also possible to manage Arc through a local configuration UI.
    - Execution info(rmation)
      The Execution Info section displays the status of Arc's sensors, execution modes, and network connectivity. It also provides details about service status, version, and execution controls.
      - Execution modes
        The Change execution mode button lets you select and manage how Arc collects data. You can configure execution time, start or stop processes, and optimize data collection based on the selected mode.
    - Required dependencies
      The Required dependencies section shows a list of all the required dependencies for the selected sensor, and the installation status for each dependency.
    - Offline archives
      The Offline archives section gives you access to the archives that have been created in Offline mode for the current session.
    - Active detection
      The Active detection section shows up-to-date execution details and status for Discovery and Smart Polling operations.
    - Settings
      The Settings page gives you access to the Upstream connection, Execution options, and Traffic monitoring pages.
    - Open the local configuration UI
      The local configuration 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 useful shell commands.
  - Configuration in Guardian
  - Configuration in Vantage
- 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.
- Print format documentation
  A list of all the print-format documentation that is available for Arc.

Execution info(rmation)

The Execution Info section displays the status of Arc's sensors, execution modes, and network connectivity. It also provides details about service status, version, and execution controls.

Execution info(rmation) — Figure 1. Execution info(rmation)

Version

This shows the version of Arc that has been deployed.

Execution status

Running, remaining time XXXX s - in case of One-shot or Offline executions

Running as service

Stopped

Service status

Not installed

Stopped

Running

Unknown - in case of generic issues

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.

Actions button

This button lets you:

Change the execution mode
Run the Arc process, if it is not currently running
Stop the Arc process, if it is currently running

For more details, seeExecution modes.

Note: You can also stop the Arc process from the terminal with the command: CTRL+C.