Notification
Configure notifications in Traceable to control which protection events you receive and how often, across supported channels
Notifications play an essential role in application protection. Custom notifications also help you streamline the types of notifications you wish to receive and the frequency at which you would like to receive them. Some events also have severity levels, such as High, Medium, or Low. You can choose the severity of events for which you wish to be notified. For example, you can decide to be notified only for high and medium-severity events. Navigate to Settings () → Configuration → Notifications page to create custom notifications.
What you will learn from this topic
By the end of this topic, you will be able to learn:
The steps to create a custom notification.
The list of categories and their respective threat and event types.
Before you begin
Before you proceed to create a notification channel and a custom notification, make a note of the following:
Make sure you have the View and Edit RBAC permissions under Administration→ Notifications to create the channel notifications. Go to Team and roles - RBAC for more details.
Create a custom notification
Creating a custom notification is a two-step process.
After creating a channel, you must create a notification rule to select the type of threats or events for which you wish to receive notifications. During this configuration, you must also select the channel you created for Traceable to distribute the notification.
Step 1: Create a channel
A channel is a group of media or people you want to notify when a type of event is triggered. You can send notifications to one or more of the following channels:
Email Addresses: Sends notifications directly to the specified email address(es), ensuring that users receive alerts in their inbox(es). You can send these alerts to one or more users by adding a comma-separated list of email addresses.
Slack Webhook: Sends notifications to Slack channels, enabling real-time collaboration and immediate visibility of events within team workflows. For information on creating a Slack webhook, go to Sending messages using Incoming Webhooks.
S3 Webhook: Sends notification payloads in Amazon S3, allowing integration according to your requirements for further analysis or compliance. Go to S3 Integration for more details.
Splunk Webhook: Integrate with Splunk to forward notification data, which supports advanced log analysis and monitoring capabilities using its dashboard. For information on the Splunk webhook, go to Splunk documentation.
Syslog Server: Sends notifications to a Syslog server, enabling centralized logging and integration with traditional IT operational tools. Go to the Syslog documentation for more details on the Syslog server.
HTTP Event Collector Webhook: Sends a notification to the specified channel if any HTTP Event Collector events are triggered on Splunk. Go to HTTP Event Collector (HEC) Integration for more details.
Google SecOps Webhook: Sends notification data to Google Security Operations (Google SecOps), allowing you to search for Traceable events and correlate them with other security telemetry in Google SecOps.
Custom Webhook: Provides a customizable endpoint for delivering notifications, allowing integration with third-party systems or workflows according to your requirements.

On the Settings () → Configuration → Notifications page, click the Create Channel button, and provide the details to configure a channel. You can later edit or delete the channel. Once you have created a channel, the next step is to create a notification rule.
Step 2: Create a notification rule
A notification is sent through a channel for a specific category of events and a particular event type. To view all events sent through the channel, see the Notification Types and Field Definition. To create a notification rule, click + Create Notification and complete the following steps:

Name: A name for your notification rule, for example, Sample Notification Rule.
Who should receive this notification: A channel where you wish to receive the notification. You can change the channel to which you want to send the notification at any time post-creation. However, a notification can be sent to only one channel.
Category: The category to which the threat or event belongs.
Environment(s): The environment for which you wish to receive the notification.
Threat Types: The type of event or threat for which you wish to receive notifications. Each category has different threat types or event types. Go to Threat and Event Types for more details on the availability.
Severity: The severity of the event that is being notified, for example, High.
Impact: The impact of the threat or event types you wish to receive the notification, for example, you may wish to receive notifications only for threat activities with a High impact score.
Confidence: The confidence of the threat or event types you wish to receive the notification for. For example, you may wish to receive notifications only for threat activities that have a Medium confidence level.
(Optional) Select the frequency of notification from one notification every hour to one notification in 24 hours.
Click Save.
Threat and event types
The following tables list the different category and their corresponding threat types or event types:
| Category | Threat type |
|---|---|
Logged threat activity | Authorization Bypass - Object Level |
Authorization Bypass - User Level | |
Content Size Anomaly | |
Content Type Anomaly | |
Cross-Site Scripting (XSS) | |
Custom Signature | |
Data Loss Prevention | |
Email Domain Malicious Sources | |
Enumeration | |
GraphQL Attacks | |
HTTP Protocol Attacks | |
Invalid Enumerations | |
IP Range Malicious Sources | |
IP Type Malicious Sources | |
Java Application Attacks | |
Local File Inclusion | |
Mass Assignment | |
Missing Field | |
NodeJS Injection | |
Rate Limiting | |
Region Malicious Sources | |
Remote Code Execution | |
Remote File Inclusion | |
Scanner Detection | |
Server Side Request Forgery (SSRF) Signatures | |
Session Fixation | |
SQL Injection | |
Type Anomaly | |
Value Out of Range | |
XML External Entity Injection (XXE) | |
Blocked threat activity | Cross-Site Scripting (XSS) |
Custom Signature | |
Data Loss Prevention | |
Email Domain Malicious Sources | |
Enumeration | |
GraphQL Attacks | |
HTTP Protocol Attacks | |
In-Agent Vulnerable Library | |
IP Range Malicious Sources | |
IP Type Malicious Sources | |
Java Application Attacks | |
Local File Inclusion | |
NodeJS Injection | |
Rate Limiting | |
Region Malicious Sources | |
Remote Code Execution | |
Remote File Inclusion | |
Scanner Detection | |
Server Side Request Forgery (SSRF) Signatures | |
Session Fixation | |
SQL Injection | |
Threat Actor | |
XML External Entity Injection (XXE) |
| Category | Event type |
|---|---|
Threat actor status change | Normal |
Threat Actor | |
Resolved | |
Always Allowed | |
Always Denied | |
Suspended | |
Snoozed | |
Threat actor severity state change | Low |
Medium | |
High | |
Critical | |
Protection configuration change | Signature-Based Blocking |
Rate Limiting | |
Data Loss Prevention | |
Enumeration | |
Malicious Sources IP Range | |
Malicious Sources Region | |
Malicious Sources Email Domain | |
Malicious Sources IP Type | |
Custom Signature | |
Detection | |
Exclusions | |
Team activity | Create User |
Update User | |
Delete User | |
Invite User | |
User Accept Invite | |
User Login | |
User Logout | |
Threat scoring configuration change | Anomalous Behavior Score Contribution |
Severity Score Contribution | |
Threat Actor Score Contribution | |
Events Contribution | |
IP Reputation Score Contribution | |
Status Code Contribution | |
Threat Auto Blocking | |
Bot Actor | Credential Stuffing |
Browser Bypass | |
Advanced Rules | |
Likely Distributed Attacks | |
Landspeed Violation | |
Velocity Aggregation | |
Bot Activity | Landspeed Violation |
Credential Stuffing | |
Browser Bypass | |
Advanced Rules | |
Likely Distributed Attacks | |
Velocity Aggregation | |
Bot Account | Landspeed Violation |
Credential Stuffing | |
Browser Bypass | |
Advanced Rules | |
Likely Distributed Attacks | |
Velocity Aggregation | |
Bot Event | Landspeed Violation |
Credential Stuffing | |
Browser Bypass | |
Advanced Rules | |
Likely Distributed Attacks | |
Velocity Aggregation | |
Pre-categorized Bots |
You can create notifications for any change made to the notification configurations.
| Category | Event Type | Event Category |
|---|---|---|
API naming rule configuration change | Create | - |
Update | - | |
Delete | - | |
API documentation configuration change | Create | - |
Update | - | |
Delete | - | |
Exclude rule configuration change | Create | - |
Update | - | |
Delete | - | |
Label configuration change | Create |
|
Update | - | |
Delete | - | |
Risk scoring configuration change | Update | - |
Posture event | API Discovery | - |
Risk Score Change | - | |
Sensitive Data Discovery | - | |
Sensitive Data Shared With Third Party | - | |
Service Discovery | - | |
Vulnerability Discovery | - | |
Notification configuration change | Create |
|
Update | - | |
Delete | - | |
Data classification configuration change | Create |
|
Update | - | |
Delete | - | |
Integration configuration change | Create config | - |
Update config | - | |
Delete config | - | |
Certificate Configuration Change | Create | - |
Update | - | |
Delete | - | |
Expiry | - | |
Renewal | - |
Additionally, you can create notifications for data collection activities to stay informed when an agent comes online or goes offline.
| Category | Agent activity type |
|---|---|
Data Collection Activity | New agent deployed |
No data in the environment | |
Agent status change |
Last updated
Was this helpful?