Triggering intrusions using native Security Center events - 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

You can use native Security Center events to trigger intrusions in the RSA Surveillance plugin, using the Genetec driver tracking system, Genetec driver macro, and event-to-actions.

What you should know

When the Security Center event is generated, the event-to-action triggers the macro to run. When the macro is run, the custom event specified in the macro configuration is generated, which triggers the RSA Surveillance plugin to create an intrusion, based on the configuration of the Genetec driver tracking system.

Procedure

  1. Create and configure the Genetec tracking system to create an intrusion when the RSA Generic event is generated.
  2. Create and configure the Genetec driver macro to generate the RSA Generic event.
  3. Create an event-to-action to run the Genetec driver macro when the Security Center event is triggered.
    NOTE: Do not override the Default execution context of the macro. In the From field, make sure the entity is set to the same entity as the Source configured for the RSA Generic Event on the Genetec driver Properties page. You can also set the From field to Any entity if you have multiple source entities configured for the RSA Generic Event.
    Example: In the following example, the Genetec driver macro is configured to run when the Door forced open event is triggered from any door.

Results

When the Security Center event is generated, the Genetec driver macro is executed and generates the RSA Generic Event, which triggers the RSA Surveillance plugin to create an intrusion, based on the configuration of the Genetec driver tracking system.