Configuring alarm behavior for the CCURE 9000 Access Control plugin - CCURE Access Control 3.9.0

CCURE 9000 Access Control Plugin Guide 3.9.0

Product
CCURE 9000 Access Control
Content type
Guides > Plugin and extension guides
Version
3.9
Release
3.9.0
ft:locale
en-US
Last updated
2025-01-31

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

What you should know

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

Procedure

  1. From the Config Tool homepage, open the Plugins task.
  2. In the Plugins task, select the CCURE 9000 Access Control 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 a 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 the user acknowledges a CCURE 9000 alarm in Security Desk, then the corresponding event is acknowledged in the CCURE 9000 software.
    When this option is off and the user acknowledges a CCURE 9000 alarm in Security Desk, then the alarm is acknowledged in Security Center but reappears after the next synchronization.
    Override default alarm acknowledgment button
    When this option is on, Security Center overrides its default alarm acknowledgment behavior. If the user acknowledges an alarm with active causes in the CCURE 9000 software , Security Center prompts the user to clear the active causes. If there are no active causes, Security Center proceeds to acknowledge the alarm.
    Command to send
    When the Acknowledge option is on and a user acknowledges an alarm in Security Desk, the corresponding event is acknowledged in the CCURE 9000 software. Events that require clearing then need to be manually cleared in the CCURE 9000 software.
    When the Acknowledge and clear 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 can’t be acknowledged.
    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.
    If an alarm with an active cause is acknowledged in Security Center, the alarm is cleared but reappears. For this reason, it is recommended to always review the causes of an alarm before you acknowledge it. Refer to examples 2, 3 and 5 in Examples of CCURE alarm behavior configurations.
    IMPORTANT: If you select this option and acknowledge an alarm in Security Center, the Allow acknowledgement while causes are active option is automatically enabled in the CCURE 9000 software. Once the alarm is acknowledged, the Allow acknowledgement while causes are active option reverts back to what its original state was before the alarm was acknowledged.

    Clear while causes are active
    When this option is on, users can clear alarms on the CCURE 9000 software, even if the alarm has active causes.
    IMPORTANT: If you select this option and acknowledge an alarm in Security Center, the Allow event to be cleared while causes are active option is automatically enabled in the CCURE 9000 software. Once the alarm is acknowledged, the Allow event to be cleared while causes are active option reverts back to what its original state was before the alarm was acknowledged.

  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 9000 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 9000 Access Control plugin.
  6. (Optional) In the Alarm partitions list, select the partition for all synchronized CCURE 9000 alarm entities.
    Alarms created by the plugin are always members of the selected partitions.
    CAUTION:
    The plugin removes partitions added using the Alarms task when these Alarm partitions are changed.
  7. Click Apply.