Alert

Notification Policy

The Notification Policy module serves as the notification management layer of the alerting system. It routes security events received from alert rules to appropriate notification channels and delivers them to designated recipients. It provides support for intelligent routing, rate limiting, and multi-channel notifications.
The alert system works with SMTP or SMS system. To use the alert system, you must first configure your preferred system.
πŸ‘‰ SMTP ConfigurationπŸ“©
πŸ‘‰ SMS ConfigurationπŸ’¬

Policy Management Architecture πŸ—

The notification system adopts a policy-based routing approach. Each policy links specific alert rules to predefined recipient groups and communication channels. This design enables scalable notification management and centralized alert distribution.

The policy engine operates through three core components:

  • Rule Association: Defines which alert rules are bound to which policies.
  • Channel Configuration: Enables multi-platform notification delivery mechanisms.
  • Recipient Management: Manages target audience segmentation and delivery preferences.

Policy Types 🎯

Custom Policies 🎨

Custom policies are tailored for specific business requirements, enabling flexible notification logic. These policies support organization-specific workflows through flexible rule selection, conditional triggers, and custom recipient mapping.

Template Policies πŸ“Œ

The template system provides pre-configured notification policies for common security scenarios. Policies are organized by category, allowing domain-specific notification templates:

  • Authentication Security: Notification patterns for identity-related security events.
  • Data Protection: Specialized routing for data loss and unauthorized access incidents.
  • Executive Alerts: Executive-level notifications for high-severity incidents.
  • Insider Threat Detection: Targeted alerting for internal threat patterns.
  • Malware Defense: Rapid response notifications for malware detection events.
  • Network Protection: Infrastructure team notifications for network security incidents.
  • Web Application Security: Development team alerting for application-layer attacks.

Alert Routing Engine πŸ”§

The policy engine performs intelligent alert routing based on multi-criteria evaluation:

Rule Association 🀝🏼

Policies consolidate multiple alert rules into a single notification stream. This ensures coordinated response to related security events and reduces notification noise.

Conditional Logic πŸ“‘

  • Min Score Filtering: Policies define trigger conditions using a minimum risk score threshold, preventing unnecessary notifications for low-priority alerts.
  • Rate Limiting: Configurable thresholds and time windows prevent notification flooding and maintain system stability during high-volume alert generation.

Multi-Channel Notification πŸ“’

Supported Channels:

SMS: GSM infrastructure integration for real-time mobile alerts

Email: Rich alert details with attachment support

Channel Strategy πŸ“Ί

The multi-channel strategy ensures delivery redundancy and recipient preference optimization. Critical alerts are delivered simultaneously across multiple channels, while routine notifications follow preferred channels.

Recipient Management πŸ“₯

Recipient Categories 🏷️

The system supports role-based recipient categorization, including:

  • Security Operations: SOC team members and security analysts
  • Identity Management: Teams responsible for identity governance and access control
  • Application Security: Developers and DevSecOps teams
  • Executive Level: C-level executives and security leadership
  • Infrastructure Teams: Network operations and system administrators

Dynamic Recipient Selection ☰

The policy engine performs context-aware recipient selection, dynamically determining the appropriate recipients based on alert type, severity level, and business impact.

Policy Configuration βš™οΈ

Rate Limiting Controls 🚧

  • Threshold Configuration: Defines the maximum number of notifications within a specific time window.
  • Window Management: Prevents notification bursts through time-based rate limiting.

Delivery Optimization α―“βž€

Policies optimize notification delivery through:

  • Priority-based Routing: Expedited delivery for high-severity alerts
  • Batch Processing: Efficient batch delivery for low-priority alerts
  • Delivery Confirmation: Acknowledgment requirements for critical notifications

Integration Architecture πŸ—

Alert System Integration❗

Notification policies are tightly integrated with the alert rule engine. Triggering events automatically invoke policy evaluation and initiate the corresponding notification workflow.

External System Integration πŸ”Œ

Native integration with communication platforms through:

  • Webhook Support: HTTP webhook delivery for custom integrations
  • API Connectivity: RESTful API integration with third-party systems
  • Message Formatting: Platform-specific message formatting for optimal delivery

Use Cases ✍️

  • Incident Response Automation: Rapid response team activation via automated notification cascades for critical events.
  • Compliance Reporting: Automated stakeholder notifications and audit trail generation for regulatory compliance.
  • Operational Monitoring: Proactive notifications for infrastructure and application health.
  • Executive Dashboards: Summarized alerts focused on high-level security posture for executive visibility.
  • Cross-Functional Coordination: Coordinated notifications to multiple departments for optimized organizational response to security events.

How To Use ? πŸ€”

To create a rule on the Alert page, go to Alert > Notification Policy

Create Custom Policy

Follow the steps below to create a custom rule;

  • Go to Create New > Create Custom > Custom Rule and then click Add button.
  • Write a Policy name and then select rule from Policy Rules menu.
  • Enter the Threshold and Window values from the Rate Limit menu below.
  • From the Conditions menu, select the score at which the Notification will be triggered.
  • Finally, enter Recipients and Channels to which the Notification will be sent. Click the Add button and save.

For Exemple: In this example, when failed SSH attempts within 60 seconds are repeated 15 times within 1 hour and reach a score of 70, the SOC analyst team will be notified via sms.

Policy Rules

Rate Limit

Conditions

Recipients

Channels

Create From Template

Follow the steps below to create a new rule using a ready-made template;

  • Go to Create New > Create from template.The Rule Templates page will welcome you. Select the template you need from this page and click the Add button.
  • The predefined rule template for you will appear in detail. You can edit it on this page if you want or you can leave it as default and click the Add button.
    After finishing the rule definitions in the Alert module, you need to bind the alerts to a policy in the notification policy section. Go to the notification policy document for these operations.