Skip to main content
Skip table of contents

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:

  1. Click the bell icon in the upper right corner.

  1. 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.

  1. Once the user clicks on a notification it becomes marked as read.

  2. 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.

  3. All the notifications can be marked as read by using the Mark all as read function located under the tools icon.

  4. The unread notices can be filtered by toggling the Only show unread switch.

  5. 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

Portal_NotificationSettings_Form.png

  1. Go to Configuration > Notification Settings.

  2. Click the green (plus) 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 Event Notification - Triggers.

  5. Select an Integration for the event. See Event Notification - Integration.

  6. Select a View Template. See View Templates.

  7. Select Users to receive the notifications.

  8. 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.

    Portal_NotificationSettings_SubjectContent_FilteredTooltip.png

  9. 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.

  10. 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

  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.

    Portal_NotificationSettings_Tag.png

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.

    Portal_NotificationSettings_Toolbar.png

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.

Portal_Notifications_WatchingColumn.png


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






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.



JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.