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

User Guide: Protected Asset as a Central Object

Overview

The Protected Asset is now the central hub object of the Bearing Application. All security context — Configuration Items (CIs), Alerts, Incidents, Access Levels, Approval Rules, and Compliance Frameworks — is built around the Protected Asset, giving SOC Operators a single entry point for operational visibility. The result is a clear CI → Alert → Incident → Protected Asset flow with the full context of an event in one place, and far less manual searching.

What's New

  • Access Levels & Approval Rules on the Protected Asset — see which access levels and approval rules apply to a specific Protected Asset directly from its record.
  • Notification Groups — define a group per Protected Asset that receives notifications for related incidents and alerts.
  • Responsible Groups — manage all responsible groups (security, guard, assignment) directly on the Protected Asset.
  • Physical Security Operations related list — see all PS Operations related to a Protected Asset.
  • Security Alerts counter — a new sidebar badge on the Protected Asset record shows the number of related alerts (linked through common CIs). Clicking it opens a filtered list of those alerts.
  • Emergency & Facilities information blocks — store emergency and facilities contact information on the Protected Asset.
  • Compliance Frameworks — link the compliance frameworks that apply to a Protected Asset.
  • Hierarchy view — Protected Assets support parent–child hierarchy, with a hierarchical view of relationships.
  • Temporary Protected Assets — create time-limited Protected Assets (e.g., off-site venues) with automatic activation and deactivation.
  • Workspace access & bulk import — Protected Assets are accessible directly from the Workspace and can be bulk-imported via the Import Manager.
  • Improved form — redesigned Protected Asset form layout with a new Protected Asset number field.
  • Auto-linking — CIs and Protected Assets are auto-linked to alerts and incidents when they are connected by a Protected Asset in common (for example, referencing card reader events and video clips for a door-forced alarm).
  • New room/usage types — "SCIF" and "Server" are available as room types on the Protected Asset.

                            For SOC Admins: Setting Up a Protected Asset

                            1. Open Protected Assets from the Workspace.
                            2. Create or open a Protected Asset record. Complete the form, including the new asset number field and (for rooms) the room type — including SCIF or Server where applicable.
                            3. Associate the relevant CIs, Access Levels, and Approval Rules.
                            4. Define the Notification Group that should be alerted for related incidents and alerts.
                            5. Add responsible groups (guard, assignment, approval) on the record.
                            6. Enter Emergency and Facilities contact information.
                            7. Link applicable Compliance Frameworks.
                            8. If the asset is part of a campus or building structure, set its parent to build the hierarchy.

                                            For large datasets, use Bulk Import via the Import Manager to load multiple Protected Assets at once.

                                            For SOC Operators: Working with Protected Assets

                                            • Open a Protected Asset from the Workspace to see its operations, alerts counter, hierarchy, groups, and contact blocks — no manual searching for context.
                                            • When you link a Protected Asset to an incident, you are prompted to include its related CIs; only the CIs you select are linked. Navigation between the Incident, CI, and Protected Asset is a single click.
                                            • For time-limited locations (an off-site event venue, a hotel), create a Temporary Protected Asset and set its active window; activation and deactivation are automatic.