Notifications

Aether AI runs continuously, so the exposures it finds and resolves change over time. Notifications are how the platform surfaces those changes to the right people without anyone having to sit and watch a dashboard. The goal is simple: when your risk moves, you hear about it.

Why it matters

Continuous offensive testing and attack surface monitoring only pay off if the results reach a human in time to act. A new directly exploitable finding on a production asset is a different conversation to a low-severity change on something you already knew about, and both are different again to a finding that just resolved itself after a fix. Notifications carry that signal out of the platform and into wherever you already work, so validated exposure does not sit unread in a queue.

Security leaders get assurance that material changes are seen, and the people who own remediation get the prompt that something needs attention now.

Where notifications appear

Aether AI delivers notifications through three channels:

• In-app notification bell. A bell in the interface shows unread activity at a glance, so you can catch what changed during your session without leaving the page you are on.
• Notifications page. A full page collects your notification history in one place, so nothing depends on happening to see the bell at the right moment.
• Email. Notifications also go out by email, so the people who need to know are reached even when they are not signed in.

What triggers a notification

Notifications track the lifecycle of a finding, so they fire on the moments that matter for risk:

• New exposure. A new finding has been surfaced against your attack surface, whether from ASM, the Autonomous AI Pentest, or a Threat Radar plugin.
• Resolved. A finding is no longer observed on re-validation, so the exposure has cleared and your risk drops accordingly.
• Regressed. A finding that was previously resolved has been observed again, so something that looked fixed has come back.

Because these events map to the same resolve, retest and regression lifecycle used across the platform, a notification is always tied to a concrete change in state rather than to noise. When a finding resolves, that change is reflected in the asset risk score too, which drops back as confirmed live findings clear.

Working from a notification

A notification is a pointer, not the whole story. From it you move into the finding itself, where you get the evidence, the source, and the fix, and where the Risk Inbox lets you triage across everything in one queue. That keeps notifications lightweight while the detail and the workflow stay in one place.

Related