Physical security teams don’t lose the most time to the threats themselves. They lose it trying to piece together enterprise context across tools that were never designed to work together, often under intense time pressure.
Every minute spent searching for that context is a minute the team isn’t applying judgment, deciding what a situation means and what to do next.
Bearing is designed to close that gap by connecting corporate security operations on ServiceNow. Our latest release advances that work across three parts of the operating model: connecting the operational picture, operationalizing it into the team’s daily workflows, and orchestrating routine work so it can move forward without someone pushing every step by hand.
The core idea is simple: the people, assets, incidents, and alerts a security team cares about should already be linked. Investigators shouldn’t have to reconstruct those relationships from memory and three separate systems after something happens.
That’s the biggest shift in this Bearing release. When an incident occurs, the related asset, its access history, and earlier alerts are already connected. The context is available from the start instead of assembled under pressure.
We’ve also extended that connected picture to more of the organization, including contractors and short-term assets tied to a specific project or event, while making those relationships easier to understand at a glance.
The value compounds over time. As more of the operational picture becomes connected, every future investigation requires less manual reconstruction.
Connected data only matters if it makes the work easier, not just the reporting.
For field teams, Bearing now supports guard tours that guide officers through each check step by step instead of relying on a static checklist and institutional memory.
For teams managing access, approval workflows can reflect how the organization makes decisions rather than forcing every request through the same generic process.
For teams handling requests such as HR investigations or event security coverage, guided intake captures the right information from the beginning.
This may not be the most visible work in a security program, but it’s where a significant amount of operational time is lost. Making it lighter gives teams more capacity for the situations that demand their attention.
Once information is connected and daily work is operationalized, automation and AI can take on more of the routine load.
In this release, natural-language requests work across more of Bearing’s day-to-day catalog. Follow-up work generated from a risk assessment can move forward automatically instead of waiting in someone’s inbox.
We also deepened integrations with systems security teams already use, helping information remain consistent instead of drifting out of sync.
The principle is the same across Bearing: automation and AI should amplify a security team’s judgment, not replace it. That requires a connected, trustworthy foundation—the foundation created by the connect and operationalize work that comes first.
The goal isn’t more data to collect or another system to monitor. It’s to close the gap between the enterprise a security team is responsible for protecting and the fragmented, manual operating model many teams still rely on.
Every connected asset, simplified workflow, and automated handoff returns time and attention to the part of the job that requires a person: recognizing what matters and deciding what to do about it.
This release is another step toward Bearing’s larger vision for corporate security operations on ServiceNow. The foundation it strengthens is the same foundation future releases will continue to build on.
Curious what’s new in detail? Request a demo or see how Bearing runs natively on ServiceNow.
Attending GSX 2026? See Bearing live at our booth.
