Alert Policy

⌘K

The Alert Policy module in Zecurit enables administrators to define intelligent rules for monitoring hardware, software, licenses, certificates, security settings and system health. These policies proactively notify admins when certain conditions are met during inventory scans, helping teams detect anomalies, compliance violations and system issues in real-time.

How It Works

  • Admins create alert policies based on predefined conditions and assign them to specific device groups.
  • During scheduled or on-demand inventory scans, these conditions are evaluated.
  • If a device within the group meets the condition, an alert is generated.
  • Notifications can also be sent to the configured email addresses for prompt action.

Navigating the Alerts Module

The Alerts module has three tabs:

  1. Alerts: View triggered alerts and their status.
  2. Alert Policy: Create and manage alert policies (this document).
  3. Associate Policy: Link alert policies to device groups.

Creating an Alert Policy

To create a new alert policy:

  1. Navigate to Alerts → Alert Policy tab.
  2. Click Create Policy.
  3. Fill in the following details:

Alert Policy Inputs

FieldDescription
Alert Policy Name*A unique name for the alert policy.
DescriptionOptional context for the policy’s purpose.
Priority*Set the severity level: Critical, High, Medium, or Low.
Notification EmailEmail address(es) to notify when the alert is triggered.

Supported Alert Types & Conditions

The platform supports alert policies across various asset categories:

Alert TypeExample Use Case
Hardware AlertsGet alerted when a USB device is added to a sensitive endpoint.
Software AlertsAlert when prohibited or unapproved software is installed on a device.
License AlertsNotify when your antivirus license is about to expire in 10 days.
Certificate AlertsEnsure expiring TLS certificates are renewed before service disruption.
Disk Space AlertsAlert if any system partition drops below 10% free space.
Security AlertsHigh-priority alert if an endpoint’s antivirus service is stopped or disabled.

Trigger when hardware components are added or removed:

  • Audio
  • Battery
  • BIOS
  • Keyboard
  • Monitors
  • Motherboard
  • Pointing Devices
  • Printers
  • USB Controller
  • USB Hub
  • TPM
  • Network Adapter
  • Physical Memory
  • Hard Disk
  • Processors
  • Video Controllers

Monitor software installation/uninstallation:

  • Software Installed
  • Software Uninstalled
  • Prohibited Software Detected
  • Commercial Software Detected
  • All Software Changes
  • Custom Software Changes

Example: Alert when prohibited or unapproved software is installed.

Stay informed about license compliance and expiry:

  • Software License has Expired
  • License nearing expiration in X days
  • Software Compliance Under Licensed
  • Software Compliance Over Licensed

Example: Get notified when your antivirus license is about to expire in 10 days.

  • Certificate Expiring in X days
  • Self-signed Certificate Detected
  • Untrusted Root Certificate Authority Detected

Example: Ensure expiring TLS certificates are renewed before outage occurs.

  • Overall Disk Usage Below X%
  • Individual Disk Usage Below X%

Example: Alert if any system partition drops below 10% free space.

  • Firewall Disabled or Not Running
  • BitLocker / FileVault Turned Off
  • Antivirus/Antimalware Service Stopped

Example: Get high-priority alerts if an endpoint’s antivirus stops running.

Publishing the Policy

After configuring the conditions:

  • Click Publish to activate the policy.
  • Or save as Draft if you plan to review or edit later.
  • Click Cancel to discard changes.

Once published, go to the Associate Policy tab to link this alert policy to specific device groups.

Associating Alert Policies

An alert policy has no effect until it’s associated with one or more device groups. To associate:

  1. Go to the Associate Policy tab.
  2. Select the policy and choose target groups.
  3. Save your changes.

Notes

  • Alert evaluation occurs during inventory scans.
  • One policy can be assigned to multiple groups.
  • Multiple policies can apply to a single group.
  • All triggered alerts will be listed under the Alerts tab with full context, timestamp, and status.

Best Practices

  • Use critical priority for security and license expiry issues.
  • Group devices by function (e.g., servers, endpoints) and assign tailored alert rules.
  • Regularly review email recipients for up-to-date notification routing.
  • Periodically audit draft policies that haven’t been published.

Next Step:

Associate this alert policy with groups to enable alert monitoring.

How can we help?