Assail home

PLATFORM / HALO

Command your deployments. Wherever they operate.

Halo is Assail’s deployment control plane, bringing together fleet visibility, release management, and local administration. From cloud deployments to systems on your premises, see what runs where, and maintain it within your operating requirements.

Request a Demo

Discuss Your Deployment

FLEET VIEW. LOCAL CONTROL.

Fleet visibility and local control over releases, entitlements, and updates.

PLATFORM / HALO

Command your deployments. Wherever they operate.

Halo is Assail’s deployment control plane, bringing together fleet visibility, release management, and local administration. From cloud deployments to systems on your premises, see what runs where, and maintain it within your operating requirements.

Request a Demo

Discuss Your Deployment

DEPLOYMENT CONTROL

VISIBILITY · SIGNED RELEASES · LOCAL ADMIN

FLEET VIEW. LOCAL CONTROL.

Fleet visibility and local control over releases, entitlements, and updates.

PLATFORM / HALO

Command your deployments. Wherever they operate.

Halo is Assail’s deployment control plane, bringing together fleet visibility, release management, and local administration. From cloud deployments to systems on your premises, see what runs where, and maintain it within your operating requirements.

Request a Demo

Discuss Your Deployment

DEPLOYMENT CONTROL

VISIBILITY · SIGNED RELEASES · LOCAL ADMIN

FLEET VIEW. LOCAL CONTROL.

Fleet visibility and local control over releases, entitlements, and updates.

01

01 / HALO

01 / HALO

Autonomy needs an operational foundation.

Autonomy needs an operational foundation.

Autonomy needs an operational foundation.

Running autonomous security software is only part of the job. You also need to know which release is installed, whether a deployment is reachable, when its entitlement expires, and what happened during its last update.

Running autonomous security software is only part of the job. You also need to know which release is installed, whether a deployment is reachable, when its entitlement expires, and what happened during its last update.

Those questions become harder when software runs across customer cloud accounts, local hardware, and environments that cannot maintain an internet connection.

Those questions become harder when software runs across customer cloud accounts, local hardware, and environments that cannot maintain an internet connection.

Halo brings that operational context into view. It helps Assail support distributed deployments and gives local administrators a console for the installation they operate.

Halo brings that operational context into view. It helps Assail support distributed deployments and gives local administrators a console for the installation they operate.

02 / HALO

One platform. Two operational perspectives.

Fleet Console

The view across deployments.

Assail’s Fleet Console brings Ares and Reaper deployments into a common operational view. Deployment identity, reported status, release information, and contact history help Assail understand what a deployment last reported and where follow-up is needed.

An installation that has stopped reporting should look different from one that is healthy. A release offered for installation should look different from one confirmed as applied. Halo keeps those distinctions visible.

Site Console

The view from your environment.

The local Site Console gives administrators visibility into their own installation. See the installed release, entitlement status, update progress, and available operational information from the system running in your environment.

For supported Ares installations, Ares Control brings local administration into the same console, including visibility into users, findings, campaigns, and pending approvals.

02 / HALO

One platform. Two operational perspectives.

Fleet Console

The view across deployments.

Assail’s Fleet Console brings Ares and Reaper deployments into a common operational view. Deployment identity, reported status, release information, and contact history help Assail understand what a deployment last reported and where follow-up is needed.

An installation that has stopped reporting should look different from one that is healthy. A release offered for installation should look different from one confirmed as applied. Halo keeps those distinctions visible.

Site Console

The view from your environment.

The local Site Console gives administrators visibility into their own installation. See the installed release, entitlement status, update progress, and available operational information from the system running in your environment.

For supported Ares installations, Ares Control brings local administration into the same console, including visibility into users, findings, campaigns, and pending approvals.

02 / HALO

One platform. Two operational perspectives.

Fleet Console

The view across deployments.

Assail’s Fleet Console brings Ares and Reaper deployments into a common operational view. Deployment identity, reported status, release information, and contact history help Assail understand what a deployment last reported and where follow-up is needed.

An installation that has stopped reporting should look different from one that is healthy. A release offered for installation should look different from one confirmed as applied. Halo keeps those distinctions visible.

Site Console

The view from your environment.

The local Site Console gives administrators visibility into their own installation. See the installed release, entitlement status, update progress, and available operational information from the system running in your environment.

For supported Ares installations, Ares Control brings local administration into the same console, including visibility into users, findings, campaigns, and pending approvals.

THE HALO METHOD

THE HALO METHOD

Workflow

Workflow

Workflow

Bring every deployment into view, from setup to release.

Bring every deployment into view, from setup to release.

01

Establish deployment.

Establish deployment.

Set the environment and operating mode. Use authenticated central communication and a local Site Console.

Set the environment and operating mode. Use authenticated central communication and a local Site Console.

02

Make its state visible.

Make its state visible.

Review the reported release, contact history, entitlements, and local data. Identify what needs attention.

Review the reported release, contact history, entitlements, and local data. Identify what needs attention.

03

Prepare a release.

Prepare a release.

Fetch the next release online, or deliver its bundle through the approved offline process.

Fetch the next release online, or deliver its bundle through the approved offline process.

04

Install and confirm.

Install and confirm.

An administrator requests installation. The host verifies and applies the release; the console reports the outcome.

An administrator requests installation. The host verifies and applies the release; the console reports the outcome.

Four steps. One controlled deployment lifecycle.

Ares product interface used as a temporary placeholder for Halo

HALO

Capabilities

Know the state. Know how current it is.

Operational visibility depends on when information was received and how it was established.

Halo distinguishes reported deployment state from stale information and operator-attested status. Connected deployments check in. Intermittently connected deployments can report again when connectivity returns. Air-gapped deployments use a separate, offline workflow.

01 / FLEET CONSOLE

The view across deployments.

Assail’s Fleet Console brings Ares and Reaper deployments into a common operational view. Deployment identity, reported status, release information, and contact history help Assail understand what a deployment last reported and where follow-up is needed. An installation that has stopped reporting should look different from one that is healthy. A release offered for installation should look different from one confirmed as applied. Halo keeps those distinctions visible.

02 / SITE CONSOLE

The view from your environment.

The local Site Console gives administrators visibility into their own installation. See the installed release, entitlement status, update progress, and available operational information from the system running in your environment. For supported Ares installations, Ares Control brings local administration into the same console, including visibility into users, findings, campaigns, and pending approvals.

03 / VISIBILITY

Deployment visibility

Identify installations and review their reported release and contact status.

04 / RELEASES

Release tracking

Distinguish the release offered, the release approved, and the release a deployment reports running.

05 / ENTITLEMENTS

Entitlement awareness

See entitlement status and expiry alongside connectivity, so a licensing issue and a communication issue can be investigated separately.

06 / HISTORY

Deployment history

Review recorded release requests and outcomes, including who initiated supported local fetch and update actions.

07 / CHANGE CONTROL

Signed, host-verified updates

Halo’s local release workflow lets an administrator request a release download, follow its progress, and request installation from the console. Signed release bundles give the host a basis for checking what it has received before applying it. The console submits the request. The host validates the release and determines whether installation may proceed. Progress, completion, and refusal information return to the console, giving administrators a record of the outcome.

08 / DISCONNECTED

A local operating view

Halo’s Site Console supports a local operating view, with release bundles delivered through the organization’s approved media process when a download is unavailable. Local entitlement information and update outcomes remain relevant even when there is no central connection.

HALO

Capabilities

Know the state. Know how current it is.

Operational visibility depends on when information was received and how it was established.

Halo distinguishes reported deployment state from stale information and operator-attested status. Connected deployments check in. Intermittently connected deployments can report again when connectivity returns. Air-gapped deployments use a separate, offline workflow.

01 / FLEET CONSOLE

The view across deployments.

Assail’s Fleet Console brings Ares and Reaper deployments into a common operational view. Deployment identity, reported status, release information, and contact history help Assail understand what a deployment last reported and where follow-up is needed. An installation that has stopped reporting should look different from one that is healthy. A release offered for installation should look different from one confirmed as applied. Halo keeps those distinctions visible.

02 / SITE CONSOLE

The view from your environment.

The local Site Console gives administrators visibility into their own installation. See the installed release, entitlement status, update progress, and available operational information from the system running in your environment. For supported Ares installations, Ares Control brings local administration into the same console, including visibility into users, findings, campaigns, and pending approvals.

03 / VISIBILITY

Deployment visibility

Identify installations and review their reported release and contact status.

04 / RELEASES

Release tracking

Distinguish the release offered, the release approved, and the release a deployment reports running.

05 / ENTITLEMENTS

Entitlement awareness

See entitlement status and expiry alongside connectivity, so a licensing issue and a communication issue can be investigated separately.

06 / HISTORY

Deployment history

Review recorded release requests and outcomes, including who initiated supported local fetch and update actions.

07 / CHANGE CONTROL

Signed, host-verified updates

Halo’s local release workflow lets an administrator request a release download, follow its progress, and request installation from the console. Signed release bundles give the host a basis for checking what it has received before applying it. The console submits the request. The host validates the release and determines whether installation may proceed. Progress, completion, and refusal information return to the console, giving administrators a record of the outcome.

08 / DISCONNECTED

A local operating view

Halo’s Site Console supports a local operating view, with release bundles delivered through the organization’s approved media process when a download is unavailable. Local entitlement information and update outcomes remain relevant even when there is no central connection.

HALO

Capabilities

Know the state. Know how current it is.

Operational visibility depends on when information was received and how it was established.

Halo distinguishes reported deployment state from stale information and operator-attested status. Connected deployments check in. Intermittently connected deployments can report again when connectivity returns. Air-gapped deployments use a separate, offline workflow.

01 / FLEET CONSOLE

The view across deployments.

Assail’s Fleet Console brings Ares and Reaper deployments into a common operational view. Deployment identity, reported status, release information, and contact history help Assail understand what a deployment last reported and where follow-up is needed. An installation that has stopped reporting should look different from one that is healthy. A release offered for installation should look different from one confirmed as applied. Halo keeps those distinctions visible.

02 / SITE CONSOLE

The view from your environment.

The local Site Console gives administrators visibility into their own installation. See the installed release, entitlement status, update progress, and available operational information from the system running in your environment. For supported Ares installations, Ares Control brings local administration into the same console, including visibility into users, findings, campaigns, and pending approvals.

03 / VISIBILITY

Deployment visibility

Identify installations and review their reported release and contact status.

04 / RELEASES

Release tracking

Distinguish the release offered, the release approved, and the release a deployment reports running.

05 / ENTITLEMENTS

Entitlement awareness

See entitlement status and expiry alongside connectivity, so a licensing issue and a communication issue can be investigated separately.

06 / HISTORY

Deployment history

Review recorded release requests and outcomes, including who initiated supported local fetch and update actions.

07 / CHANGE CONTROL

Signed, host-verified updates

Halo’s local release workflow lets an administrator request a release download, follow its progress, and request installation from the console. Signed release bundles give the host a basis for checking what it has received before applying it. The console submits the request. The host validates the release and determines whether installation may proceed. Progress, completion, and refusal information return to the console, giving administrators a record of the outcome.

08 / DISCONNECTED

A local operating view

Halo’s Site Console supports a local operating view, with release bundles delivered through the organization’s approved media process when a download is unavailable. Local entitlement information and update outcomes remain relevant even when there is no central connection.

04 / HALO

Bring updates into your change-control process.

Your deployment should follow the requirements of your environment.

Halo’s local release workflow lets an administrator request a release download, follow its progress, and request installation from the console. Signed release bundles give the host a basis for checking what it has received before applying it.

The console submits the request. The host validates the release and determines whether installation may proceed. Progress, completion, and refusal information return to the console, giving administrators a record of the outcome.

You choose when to request an update. The host verifies what can be installed.

04 / HALO

Bring updates into your change-control process.

Your deployment should follow the requirements of your environment.

Halo’s local release workflow lets an administrator request a release download, follow its progress, and request installation from the console. Signed release bundles give the host a basis for checking what it has received before applying it.

The console submits the request. The host validates the release and determines whether installation may proceed. Progress, completion, and refusal information return to the console, giving administrators a record of the outcome.

You choose when to request an update. The host verifies what can be installed.

04 / HALO

Bring updates into your change-control process.

Your deployment should follow the requirements of your environment.

Halo’s local release workflow lets an administrator request a release download, follow its progress, and request installation from the console. Signed release bundles give the host a basis for checking what it has received before applying it.

The console submits the request. The host validates the release and determines whether installation may proceed. Progress, completion, and refusal information return to the console, giving administrators a record of the outcome.

You choose when to request an update. The host verifies what can be installed.

05 / HALO

Disconnected is an operating condition.

Some environments cannot depend on continuous access to a central service. Others must remain air-gapped by design.

Halo’s Site Console supports a local operating view, with release bundles delivered through the organization’s approved media process when a download is unavailable. Local entitlement information and update outcomes remain relevant even when there is no central connection.

For security teams working under network restrictions, that creates a practical path for maintaining software within their operating boundary.

Bring in the approved release bundle. Request installation locally. Review the result on site.

05 / HALO

Disconnected is an operating condition.

Some environments cannot depend on continuous access to a central service. Others must remain air-gapped by design.

Halo’s Site Console supports a local operating view, with release bundles delivered through the organization’s approved media process when a download is unavailable. Local entitlement information and update outcomes remain relevant even when there is no central connection.

For security teams working under network restrictions, that creates a practical path for maintaining software within their operating boundary.

Bring in the approved release bundle. Request installation locally. Review the result on site.

05 / HALO

Disconnected is an operating condition.

Some environments cannot depend on continuous access to a central service. Others must remain air-gapped by design.

Halo’s Site Console supports a local operating view, with release bundles delivered through the organization’s approved media process when a download is unavailable. Local entitlement information and update outcomes remain relevant even when there is no central connection.

For security teams working under network restrictions, that creates a practical path for maintaining software within their operating boundary.

Bring in the approved release bundle. Request installation locally. Review the result on site.

06 / HALO

A deployment model that fits your environment.

Assail-hosted service

Fleet visibility and operational administration for Assail-managed deployments

Customer cloud

Deployment context and supported release workflows for installations in the customer’s account or project

On-premises

A local Site Console for installed release information, entitlement status, and supported administration

Air-gapped

Local status and release requests using bundles delivered through an approved offline process

Deployment capabilities depend on the product, release, hardware, and connectivity mode. Assail works with your team to define the appropriate configuration.

06 / HALO

A deployment model that fits your environment.

Assail-hosted service

Fleet visibility and operational administration for Assail-managed deployments

Customer cloud

Deployment context and supported release workflows for installations in the customer’s account or project

On-premises

A local Site Console for installed release information, entitlement status, and supported administration

Air-gapped

Local status and release requests using bundles delivered through an approved offline process

Deployment capabilities depend on the product, release, hardware, and connectivity mode. Assail works with your team to define the appropriate configuration.

06 / HALO

A deployment model that fits your environment.

Assail-hosted service

Fleet visibility and operational administration for Assail-managed deployments

Customer cloud

Deployment context and supported release workflows for installations in the customer’s account or project

On-premises

A local Site Console for installed release information, entitlement status, and supported administration

Air-gapped

Local status and release requests using bundles delivered through an approved offline process

Deployment capabilities depend on the product, release, hardware, and connectivity mode. Assail works with your team to define the appropriate configuration.

08 / HALO

Frequently asked questions

TALK TO ASSAIL

Put your deployment lifecycle in view.

Talk with Assail about cloud, on-premises, and disconnected deployment requirements.

Your environment. Your objectives. A mission built around both.

https://api.peec.ai/agent-analytics/generic-access-log