Finding Notifications
This page covers finding notifications in the hosted dashboard. Your machines decide when a finding is worth a message, and Omnodex delivers it. The message says that something was found and links to your own dashboard, where your browser decrypts the detail. Notifications need Omnodex 0.16.0 or later on each machine you want to be notified about.
What you get
Section titled “What you get”| Hosted | Pro | |
|---|---|---|
| Email digest to your account email | Coming soon | Coming soon |
| Notifications page and header bell | HIGH and CRITICAL findings | Any severity |
| Browser notifications while the dashboard is open | Yes | Yes |
| Slack, Google Chat and Discord channels | No | Yes |
| Choosing severity, categories and investigations | No | Yes |
| Posting to a chat channel as soon as a finding happens | No | Yes |
Free accounts get no finding notifications. Email notifications, the digest and email channels, are coming soon; until then the settings page shows them as coming soon, and notifications go to the dashboard list and your browser, plus chat channels on Pro.
What a message carries
Section titled “What a message carries”A notification carries the finding’s severity, the rule ID, the time and a link to the dashboard. That is all. It never carries a file path, a command, a host, a credential, a tool argument or the name of the machine.
This is how it works: the server cannot read your findings, because they are encrypted before they leave your machine. So your machine matches each finding against your notification rules and sends Omnodex only the rule ID, severity, time, an opaque reference to the finding and where to deliver it. Omnodex refuses any request that carries another field. The link opens the dashboard, you sign in, and your browser finds the finding in your own decrypted data.
Findings you have muted never notify.
The notifications page and the bell
Section titled “The notifications page and the bell”Notifications in the sidebar lists the findings your machines told you about, newest first, with a dot on the unread ones. Select one to mark it read and open the finding. Mark all read clears the list, and Unread only hides what you have seen.
The bell in the header shows how many are unread. Its dropdown lists the most recent unread ones, with Mark all read and a link to the full page. The count updates about once a minute while the dashboard tab is visible, and does not update while the tab is hidden.
The list keeps your 200 newest notifications for 30 days. It holds only the rule ID, severity and time, as in every other message.
Browser notifications
Section titled “Browser notifications”In Settings, under Finding notifications, turn on Browser notifications and allow them when your browser asks. While the dashboard is open in a tab, a new notification also appears as a browser notification with the severity and rule ID.
This works only while the dashboard is open. It does not reach a closed browser, and the choice is per browser, so turn it on in each browser you use. If your browser has blocked notifications for the site, allow them in the browser’s site settings first.
Email digest
Section titled “Email digest”Email notifications are coming soon. When they arrive, one digest email will list the count of new findings by severity, the most frequent rule IDs and a link to the dashboard, go to your account email only, and go out hourly (Pro), daily or weekly. Until then, Finding notifications in Settings shows email as coming soon.
Choosing what notifies on Pro
Section titled “Choosing what notifies on Pro”Finding notifications in Settings has two rows. Each says how serious a finding must be and where it goes.
| Row | What it covers |
|---|---|
| Findings | Findings at or above a severity: Critical only, High or above, Medium or above or All. Optionally limit it to some categories, such as supply chain or persistence; with none chosen, every category notifies. The severity is the one after your own changes, not only Omnodex’s recommendation |
| Investigations | Findings that are part of an investigation, a chain of calls such as reading a credential and then sending it somewhere, at or above a severity |
Each row sends to the places you tick: the Dashboard list, the Email digest (coming soon), and each chat channel by name, so you can send critical findings to one Slack channel and investigations to another. Under Chat channels, add a Slack, Google Chat or Discord incoming webhook. The webhook URL is stored encrypted and is never shown again; only a short label identifies it. Test sends a sample message. You can add up to 10.
Chat channels post as soon as a finding happens. The dashboard list updates at once. The rows name categories, so they are saved encrypted with your account’s other policy settings, and only your machines can read them. Machines pick up a change on their next background pass, about 15 minutes. Until you save, machines notify for HIGH and CRITICAL findings in the dashboard list.
Limits
Section titled “Limits”Each connected stream sends at most 200 notifications a day, so one noisy machine cannot flood your channels. Chat channels that cannot be reached are retried for 3 days and then dropped.