Category filter
Hexnode XDR Portal Notification: Orchestrating Real-Time Admin & Security Alerts
Hexnode XDR portal notifications provide IT admins with real-time visibility into critical security anomalies, administrative changes, and endpoint detection events, ensuring immediate awareness and control over the organizational environment.
What can you get notified about?
Notifications in Hexnode XDR keep admins updated on platform activities such as technician management, role configurations, and incident updates to maintain better visibility and control.
The portal events that are notified to the admins are:
- Technician Created: A new technician has been created in the Hexnode XDR portal.
- Technician Deleted: An existing technician has been deleted from the XDR portal.
- Role Created: A new role with custom permissions has been created.
- Role Deleted: An existing role has been deleted from the XDR portal.
- Agent Deployed: The Hexnode XDR agent has been successfully installed on an endpoint.
- Agent Uninstalled: The Hexnode XDR agent has been removed from an endpoint.
- Endpoint Group Created: A new group of endpoints has been created in the XDR portal.
- Endpoint Group Deleted: An existing endpoint group has been removed from the XDR portal.
- Incident Updated: Details of an existing incident, such as status or severity, have been updated.
How to Set Notifications
Admins can customize which portal events trigger an alert to ensure only relevant security and administrative actions generate notifications.
- Log in to Hexnode XDR.
- Navigate to Settings > Notification > Portal Notification.
- Select the specific portal events for which admins need to be notified.
How are Admins Notified?
Hexnode XDR delivers event notifications via email. While a default email server is provided, admins can configure a custom SMTP server for personalized notification delivery.
Setting up the Email Server
To configure a custom outgoing mail server, follow these steps:
- Log in to Hexnode XDR.
- Go to Settings > Notifications > Email.
- Complete the following fields:
| Field | Description |
|---|---|
| Server Name | Enter the hostname of the outgoing mail server (e.g., smtp.example.com). |
| Port | Enter the port number used by the outgoing mail server. |
| Sender Email | Enter the email address from which emails are to be sent. |
| Protocol | TLS: Authenticates both client and server before data transfer. Enable if supported.
SSL: Protects communication between the server and device. Enable if supported. |
| Enable Authentication | Check this if the server requires a login. Provide the User Name (full email address) and Password. |
- Click Save.
Test the Email Server Setup
Verify the configuration by sending a test message:
- Click the Test button (top-right corner).
- Enter the recipient’s email, subject, and message.
- Hit Save and confirm the test message is received successfully.
Integrating Real-Time Webhooks
Webhooks enable Hexnode XDR to push event data to external platforms like Slack or Microsoft Teams via HTTP requests, facilitating automated workflows and instant team communication.
To configure a webhook URL:
- Log in to your Hexnode XDR portal.
- Navigate to Settings > Notification > Webhook.
- Click Add New.
- Enter a Name and optional Description.
- Provide the destination URL and the required Access Token for authentication.
- Click Save.
To receive alerts, the webhook must be selected as a delivery channel under Settings > Alert Profiles.
Troubleshooting Guides
| Problem | Resolution |
|---|---|
| Notifications not being received via email | Ensure the specific events are checked in Portal Notification settings. If using a custom server, verify that the Server Name, Port, and Authentication credentials are correct. |
| Webhook alerts not appearing in external apps | Confirm the URL and Access Token are accurate. Ensure the webhook is properly linked to an active Alert Profile in the settings. |
| Test email fails to send | Check if your network allows outbound traffic on the specified Port and ensure the chosen Protocol (TLS/SSL) is supported by your mail provider. |
FAQs (Frequently Asked Questions)
Q. Where do admins get the webhook URL and Access Token?
A. The webhook URL and Access Token are obtained from the third-party application (e.g., Slack, Teams). For example, creating an “Incoming Webhook” in Slack provides a unique URL and token to be pasted into Hexnode XDR.
