What's new in the RSA Surveillance plugin 3.5 - Restricted Security Area Surveillance 3.5

Restricted Security Area Surveillance Plugin Guide 3.5

series
Restricted Security Area Surveillance 3.5
revised_modified
2020-07-06

The RSA Surveillance plugin 3.5 includes the following new integrations and features.

New integrations
The following integrations are now supported:
New report task for RSA events
Using the RSA events task, you can now generate a report to find out which events related to RSA were triggered during a given time range.

For more information, see Investigating RSA events.

New custom events
When a tracking system is created in Security Center, you can now activate one or more of the following custom events to be triggered by that tracking system, depending on the type of tracking system:
  • Intrusion detected
  • Perimeter intrusion detected
  • Intrusion alert

For more information, see Custom events added by the RSA Surveillance plugin.

Maintenance mode for RSA zones
You can now set an RSA zone to maintenance mode when you want to test that intrusions are properly triggered for the zone.

For more information, see RSA zones.

Support for RabbitMQ failover
You can now configure multiple servers for RabbitMQ failover.

For more information, see Configuring failover for RabbitMQ.

Arm and disarm RSA zones on events
You can configure RSA zones to be armed and disarmed automatically when specific events are triggered. These events are configured per RSA zone.

For more information, see Creating RSA zones in Security Center.

Trigger intrusions using events
You can now use custom or native events to trigger intrusions in the RSA Surveillance plugin by using the Genetec driver tracking system, the Genetec driver macro, and event-to-actions.

For more information, see Triggering intrusions using native Security Center events and Adding the Genetec driver tracking system in Security Center.

Monitor intrusions in the Alarm monitoring task
You can now use the Alarm monitoring task to monitor when targets are created and acknowledge them by acknowledging their associated alarms.

For more information, see Acknowledging targets.