Configuring alarm behavior for the CCURE Access Control plugin - CCURE 3.7

CCURE Access Control Plugin Guide 3.7.0

Applies to
CCURE 3.7
Last updated
2021-10-28
Content type
Guides > Plugin and extension guides
Language
English (United States)
Product
CCURE
Version
3.7

You can configure the behavior of CCURE XFEvents that trigger alarms; including choosing the conditions that trigger an alarm, how acknowledging an alarm in Security Center affects the corresponding XFEvent in the CCURE 9000 system, choose which users receive alarm notifications, and to choose which partitions the alarm entities belong.

What you should know

  • The alarm behavior settings are global. They are applied to all CCURE alarms.
  • Recipients are assigned to a CCURE alarm during the first synchronization of an XFEvent. To change alarm recipients, see Modifying alarm recipients for the CCURE Access Control plugin.
  • Partitions added from the Alarms task are replaced by the partitions defined here.
  • By default, CCURE XFEvents that require acknowledgment are imported as Security Center alarm entities. But, you can turn any CCURE XFEvent into an alarm entity, for instructions see, Configuring the behavior of XFEvents imported from CCURE 9000.
  • It is NOT recommended to acknowledge a CCURE alarm that has active causes in Security Center. Doing so resets the workflow and overrides the logical causes that need to be investigated.
  • CCURE alarms that do not required acknowledgment are automatically acknowledged in Security Center when the related XFEvent state changes to normal in CCURE 9000.

Procedure

  1. From the Config Tool home page, open the Plugins task.
  2. In the Plugins task, select the CCURE plugin role from the entity browser, and then click the Alarms and events tab.
  3. In the Alarm behavior area, configure the following:
    Alarm Trigger > Acknowledged status
    When a CCURE 9000 event must be acknowledged, an alarm is triggered in Security Center. When the CCURE 9000 event no longer requires acknowledgment, the corresponding alarm is acknowledged in Security Center.
    Alarm trigger > Active status
    This is the default setting. When a CCURE 9000 event becomes active, the corresponding alarm or custom event is triggered in Security Center. When an CCURE 9000 event becomes inactive, the corresponding alarm is acknowledged in Security Center.
  4. Configure how alarm acknowledgment works in Security Center:
    Acknowledge from Security Center
    When this option is ON and a user acknowledges a CCURE alarm in Security Desk, then the corresponding event is acknowledged in the CCURE 9000 software.
    When this option is OFF, the acknowledge alarm command is unavailable in Security Desk, so users must acknowledge the corresponding event in the CCURE 9000 software.
    Acknowledge while causes are active
    When this option is ON, you can force the acknowledgment of an alarm even if the alarm has an active cause. This option is only available when the Acknowledge from Security Center option is on.
    When this option is OFF, you can only clear alarms that have no causes. If an alarm has an active cause and the alarm is acknowledged in Security Center, the alarm is cleared, and then reappears. For this reason, it is recommended to always review the causes of an alarm before you clear it.
    Acknowledge and clear
    When this option is ON and a user acknowledges an alarm in Security Desk, the corresponding event is acknowledged and cleared in the CCURE 9000 software. Alarms that have active causes cannot be acknowledged.
    When this option is OFF, users must first acknowledge the alarm, and then clear the alarm.
    Clear while causes are active
    When this option is ON, users can clear alarms from Security Desk, even if the alarm has active causes. The alarms are also cleared in the CCURE 9000 software.
    When this option is OFF, the clear option is unavailable in Security Desk for an alarm until all causes are cleared.
  5. In Alarm recipients, add the users to notify when an alarm occurs.
    If the list is empty, when an alarm is triggered in Security Center, no users are notified.
    IMPORTANT: The alarm recipients listed here are only added when CCURE alarm entities are synchronized for the first time. If you change the recipients list here, the changes are applied to new alarms. If you need to change the recipients list, follow the steps in Modifying alarm recipients for the CCURE Access Control plugin.
  6. (Optional) In the Alarm partitions list, select the partition for all synchronized CCURE alarm entities.
    Alarms created by the plugin are always members of the selected partitions.
    CAUTION:
    Partitions added using the Alarms task are removed by the plugin when these Alarm partitions are changed.
  7. Click Apply.