Notifications
Purpose
This document describes the notification function in the portal.
Notification
To keep track of an ongoing progress of the vulnerability management program, specific events are defined to monitor and maintain a solution.
These evens include:
Scanner updates.
An alteration is made.
Unsuccessful scans.
Accessing Notifications
To access Notifications:
Click the bell icon in the upper right corner.
All notifications that the logged in user has received are displayed. The blue notification dot under the bell icon indicates the number of unread notifications.
Once the user clicks on a notification it becomes marked as read.
The notice can be toggled between read and unread by using the Mark as reador Mark as unread icons in the upper right corner of the highlighted notification message.
All the notifications can be marked as read by using the Mark all as read function located under the tools icon.
The unread notices can be filtered by toggling the Only show unread switch.
Longer notices are expanded to full view by clicking See more at the bottom of the notice.
Notifications from the last 30 days are visible, with to a maximum of 500 notifications being kept in the notification history.
Icon | Description |
---|---|
| Mark as read |
| Mark as unread |
| Tools |
Only show unread |
Notification Configuration
Go to Configuration > Notification Settings.
Click the green icon in the lower right corner to add a new event notification.
Select a Name for the setting.
Select a Trigger for the event. See Event Notification - Triggers.
Select an Integration for the event. See Event Notification - Integration.
Select a View Template. See View Templates.
Select Users to receive the notifications.
Add a Subject. You can add predefined variables from Available Variables drop down. See Event Notification - Variables.
When starting to type the curly brackets {{ a list is displayed and filtered automatically while typing for easy access to the predefined variables.Add the Content to the notification. You can add predefined variables from Available Variables drop down. See Event Notification - Variables.
The same list as in #8 is displayed when writing two curly brackets.Click the blue ADD button to save the Notification Setting.
The Users field is only active if E-mail is selected as an integration in step 5. If Notification is selected as an integration, the setting only applies on current user/sub-user.
If the Integration is set to E-mail, the content can be toggled between Text or HTML format.
Edit Notifications Settings
Go to Configuration > Notification Settings.
Select the notification setting you want to edit.
Edit the content of the Notification Setting.
Click the blue Save button to save.
Remove Notifications Settings
Go to Configuration > Notification Settings.
Right click the Notification Setting you want to remove.
In the pop-up menu, click Delete.
or
Select the Notification Setting you want to remove by checking the check box.
In the toolbar at the bottom, click the bin icon to delete.
To learn more about Notification configuration, see Notification Settings.
The Watching Column in Findings
In the Watching column in the vulnerabilities table, the user can toggle the Watching switch on and off to monitor specific findings, which will be displayed in Notifications.
Multiselecting several findings and changing the watching setting will override the current watching setting for all selected findings.
Icon | Description |
---|---|
Watching On | |
Watching Off |
The watching by itself does not do anything and needs to be associated with a Notification Setting. The watching is user-specific.
Create a default Event subscriptions or Notification setting called Watch Finding Updates
with Notification as the integration type, and the trigger set as Watched finding updated
with the default Jinja template for Subjects and Content of the message.
Example:
Subject
{% if setting.originalTrigger == "FINDING_DELETED" %}A finding you are currently watching has been deleted.
{% elif setting.originalTrigger == "FINDING_MODIFIED" %}A finding you are currently watching has been modified.
{% elif setting.originalTrigger == "FINDING_STATUS_TRANSITIONED" %}A finding you are currently watching has been transitioned.
{% elif setting.originalTrigger == "FINDING_RISK_ACCEPTED_EXPIRATION" %}The acceptance period of a finding you are currently watching has expired.
{% elif setting.originalTrigger == "COMMENT_CREATED" %}A new comment has been made on a finding you are currently watching.
{% else %}An action of type: {{setting.originalTrigger }} has occured to a finding you are currently watching. {% endif %}
Content
{% if setting.originalTrigger == "FINDING_DELETED" %}Finding "{{ finding.name }}" of asset "{{ finding.assetName }}" has been deleted.
{% elif setting.originalTrigger == "FINDING_MODIFIED" %}Finding "{{ finding.name }}" of asset "{{ finding.assetName }}" has been modified.
{% elif setting.originalTrigger == "FINDING_STATUS_TRANSITIONED" %}The status of finding "{{ finding.name }}" of asset "{{ finding.assetName }}" has been transitioned from {{ setting.from }} to {{ setting.to }}.
{% elif setting.originalTrigger == "FINDING_RISK_ACCEPTED_EXPIRATION" %}The acceptance period of finding "{{ finding.name }}" of asset "{{ finding.assetName }}" has expired.
{% elif setting.originalTrigger == "COMMENT_CREATED" %}{{ comment.createdBy }} has commented on finding "{{ finding.name }}" of asset "{{ finding.assetName }}": "{{ comment.comment }}"".
{% else %}Finding "{{ finding.name }}" of asset "{{ finding.assetName }}" has been updated.{% endif %}en
The user can modify this to their liking, and they can change the integration type from Notification to others, such as Email.
Related Articles
Copyright
© 2024 Outpost24® All rights reserved. This document may only be redistributed unedited and unaltered. This document may be cited and referenced only if clearly crediting Outpost24® and this document as the source. Any other reproduction and redistribution in print or electronically is strictly prohibited without explicit permission.
Trademark
Outpost24® and OUTSCAN™ are trademarks of Outpost24® and its affiliated companies. All other brand names, product names or trademarks belong to their respective owners.