Enhancing incident monitoring in Mission Control 3.2

Set workstation-based privileges

Mission Control is now compatible with the Security Center workstation-based privileges released in Security Center 5.11.1. With this new compatibility, you can configure privileged access rights for incident management features based on the physical workstation rather than having it tied to individual users. For example, a user might not have access to Mission Control on a standard workstation but can access Mission Control on another workstation dedicated to incident management. This way, your organization can control accessibility to certain capabilities that take into account the location that your operators are logging in from.

Shunt door inputs through Mission Control

Many false alarms can arise from defective hardware; sometimes, you can’t repair it immediately. With Mission Control 3.2, we’ve added a new feature that allows you to shunt door inputs using automation. This new functionality helps remove noise from defective door hardware until you can repair it while keeping the door operational and accessible through badging.

 

Auto-open incidents based on their priority

Mission Control allows you to set incidents to open up automatically in their own tab, which is typically desired for incidents requiring urgency. When several incidents set to auto-open are triggered, they wait in a queue and are opened sequentially in chronological order once the current incident is closed.

In Mission Control 3.2, the subsequent incidents in the queue will now auto-open based on their priority and not simply chronologically. This new auto-open behavior for incidents works the same way for alarms in Security Center. For example, suppose the third incident in the queue has a higher incident priority than the second incident. In that case, given its priority, the third incident will auto-open before the second one. With this new functionality, it’s easier for you and your team to stay on top of urgent incidents, especially when dealing with a long list of incidents.

Sound looping for incidents

We’ve added the ability to set an incident to play a sound continuously until an operator takes ownership of the incident. This new functionality helps capture operators' attention, allowing security teams to speed up their response time for critical incidents.

 

 

Additional enhancements and features

With Mission Control 3.2, we’ve also added a few other additional enhancements, including:

• The ability to trigger incidents from event to actions
• The capability to recall full-screen monitoring display user preferences by workstation
• The latest version of Rabbit MQ (version 3.12)