Notifications

Purpose

This document describes the Notification function.

Notification

To monitor and maintain the solution, specific events should be defined to keep track of the ongoing progress of the vulnerability management program. This includes knowing when the scanner is updated, when alterations are made, and when scanning occurs unsuccessfully.

Accessing Notifications

Click the bell icon in the upper right corner to access Notifications.

This displays the notifications that the logged in user have received. The blue button 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 read or  Mark as unread icons in the upper right corner of the highlighted notification message. All the notification 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 toggle the Only show unread switch.

Longer notices are expanded to full view by clicking See more at the bottom of the notice.

30 days history is kept with up to a maximum of 500 notifications.

Icon	Description
	Mark as read
	Mark as unread
	Tools
	Only show unread

Notification Configuration

Add Notifications Settings

1. Go to Configuration > Notification Settings.
2. Click the green icon in the lower right corner to add a new event notification.
3. Select a name for the setting.
4. Select a trigger for the event. See Appendix A.
5. Select an integration for the event. See Appendix B.
6. Select a View Template. See View Templates.

7. Select users to receive the notifications.
   
   

   

   Users field is only active if E-mail is selected as integration in step 5. If Notification is selected as the setting only apply on current user/sub-user.

8. Add a subject. You can add predefined variables from Available Variables drop down. See Appendix C.

9. Add the content to the notification. You can add predefined variables from Available Variables drop down. See Appendix C.

   

   If the Integration is set to E-mail, then the content can be toggled between Text or HTML format.

10. Click the blue ADD button to save the Notification Setting.
    
    

Edit Notifications Settings

1. Go to Configuration > Notification Settings.
2. Select the notification setting you want to edit.
3. Edit the content of the Notification Setting.
4. Click the blue Save button to save.

Remove Notifications Settings

1. Go to Configuration > Notification Settings.
2. Right click the Notification Setting you want to remove.
3. In the pop-up menu, click Delete.
   
   

   

or

1. Select the Notification Setting you want to remove by checking the check box.
2. In the toolbar at the bottom, click the bin icon to Delete.
   
   

   

To learn more about Notifications configuration, see Notification Settings.

The Watching Column in Findings

In the Watching column in the vulnerabilities table, user can toggle the Watching on and off to monitor specific findings in the Notifications.

When multi-selecting several rows with mixed watching settings it will toggle all of them to on, and if all are on it should toggle to off.

Icon	Description
	Watching On
	Watching Off

The watching by it self does not do anything and need to be associated with a Notification Setting. The watchings are user specific. and each user have their own watching set up. 

Create a default Event subscriptions or Notification settings 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:

{% 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 %}

{% 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.}