Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

User Guide: Everbridge Integration Expansion — Executive Protection

Overview

The Bearing–Everbridge integration now supports synchronizing Protected Assets (PRAs) with Everbridge Assets, asset-type management, geofencing, and automated alert creation — enabling SOC teams to manage Everbridge Assets directly from Bearing while keeping both platforms aligned.

What's New

  • Create Everbridge Assets from the PRA form — create and manage a corresponding Everbridge Asset directly from a Protected Asset, including temporary activation periods, location data, and alertability settings.
  • PRA geofence — define a configurable geofence radius on a PRA; Bearing creates a corresponding area in Everbridge around the PRA location and links it to the Everbridge Asset.
  • Automatic alert creation — when an Everbridge Alert affects a synchronized Everbridge Asset or intersects a linked geofence area, Bearing automatically creates and links a Bearing Alert, so impacted PRAs are identified without manual action.
  • Affected PRA parsing — Everbridge alerts ingested into Bearing include the affected Protected Asset.
  • Asset type import & flow actions — administration support for asset-type imports and a set of reusable flow actions for Everbridge operations.

            For SOC Admins: Synchronizing a PRA with Everbridge

            1. Open the Protected Asset you want to synchronize.
            2. Use the Everbridge section/action on the PRA form to create the Everbridge Asset, setting location data, alertability, and (if temporary) the activation period.
            3. Set the geofence radius for the PRA. Bearing creates the corresponding Everbridge area and links it to the asset.

                  For SOC Operators

                  No manual steps are required: when Everbridge issues an alert affecting a synchronized asset or intersecting a geofence, a linked Bearing Alert is created automatically and identifies the impacted PRA(s). Process it from the Alert queue as usual.