Skip to main content

Sonar rule: spotting employee accounts exposed in a data breach

How the Sonar data breaches rule works, how to configure it, what admins and employees see, and what changes compared with the old Breaches module.

❶ Purpose of the data breaches rule

Breaches is now a Sonar rule, called “data breaches”. Every day, Riot checks whether your employees’ email addresses appear in a known data breach. If they do, the employee concerned receives a task to secure their accounts (for example, change their password), and you track each breach from the rule page.

💡 Prerequisite: the data breaches rule is available with the Sonar Pro and Sonar Max plans. Customers who subscribed to the old Breaches module keep it, whatever their Sonar plan.

👍 Good to know: the Breaches page now leads to Sonar › Rules › Data breaches. The Breaches entry stays in the left-hand menu and opens the rule.

❷ Data breaches: what are we talking about?

  • Data breach: a leak of information (credentials, emails, passwords, etc.) from a compromised third-party service.

  • Source: Riot relies on Have I Been Pwned and checks addresses every day.

  • Addresses checked: work addresses on your verified domains, and the personal addresses that your employees have chosen to add.

👉 A breach’s sensitivity level matches the most sensitive piece of data it exposed:

  • High: a password, bank details or private messages;

  • Medium: a phone number, a postal address, a date of birth or an ID document;

  • Low: a name, an email address or a username.

❸ Configuring the rule

💡 Prerequisite: you must be an Administrator, logged in to hub.tryriot.com. The rule requires no Google or Microsoft integration.

👉 Step 1: open Sonar › Rules › Data breaches.

👉 Step 2: open the rule’s configuration and choose your settings:

  • Monitored addresses: work and personal addresses (default), or work addresses only.

  • Breach age: breaches reported in the last 1 year, 3 years (default) or 5 years. A breach counts from the day it was made public, not the day it took place.

  • Sensitivity: high-sensitivity data only, medium or high (default), or all data.

  • Task delivery: in the next mission (default), or during the next working hours (a message with the task is then sent straight away).

  • Time before closing without a response: 1, 2 (default) or 3 missions, or 7, 14 or 30 days with delivery during working hours.

👍 Good to know: it is the setting for sending tasks to employees, in the Sonar settings, that decides whether tasks are sent. If it is turned off, breaches are detected but no task is sent. Tasks go to the employees in the Sonar audience, as with all rules.

❹ What you see as an administrator

  • The rule page lists one row per breach, with its pending issues and the number of exposed employees.

  • A breach’s details (click on a row) show the service concerned, the date of the breach, its sensitivity level, its source and its publication date, followed by the status of each employee concerned.

  • An issue’s details show the employee, the status, and when the task was sent or completed.

You can close issues one by one or in bulk. Employees are not notified, and a closed issue cannot be reopened.

To be alerted to new breaches, turn on the “A new breach has been detected” notification, in the Sonar block of your notification settings: in real time, as a digest, or not at all. See the article on managing notifications

❺ What employees see

Each employee receives a single “Secure your accounts” task, which groups all of their breaches together. For each one, the task shows what was leaked, then what to do: change the password on that service and everywhere it was reused, and beware of scam attempts that use the exposed information. The employee ticks off each step and marks the breach as dealt with: the issue then moves to the resolved status.

  • Breaches linked to the work address are tracked by the administrator.

  • Breaches linked to a personal address remain anonymous: you know that a personal address is affected, but never which one or who it belongs to. The task tells the employee this.

❻ What changes compared with the old Breaches module

When you move to the rule, your settings are carried over automatically and the old module stops sending tasks and messages. A “Breaches is now a Sonar rule” banner appears on the list of Sonar rules, and the rule’s configuration opens on your first visit.

  • A breach already dealt with by an employee in the old module becomes a resolved issue: they will not be asked to deal with it again.

  • A breach that was reported but never dealt with is picked up by the rule if it matches your settings, and the employee receives the new task.

  • Breach age and sensitivity start on the default values: 3 years, medium or high sensitivity data.

⚠️ Important: the “Notify employees” and “Create a campaign” options from a breach no longer exist. Infostealer detection, the Breaches role (replaced by the Sonar role: a member who only had the Breaches role can no longer see breaches), the Breaches tab on the employee profile, the home page widget and the “An employee has been detected in a breach or an infostealer” notification are no longer available.

❼ Frequently asked questions

Why is an old breach only appearing now?

  • Breach age counts from the day the breach was made public, not the day it took place.

  • Some breaches are revealed years later.

Why do some leaks visible on haveibeenpwned.com not appear in Riot?

Riot only reports a breach when it can name the compromised service. Generic compilations (combolists, infostealer log compilations, leaks from unknown sources) are excluded: they do not allow the employee to take concrete action, and they contain many duplicates.

How does Riot get my employees’ personal addresses?

  • The employee adds it themselves: the introductory course asks for it, and an employee with no verified personal address receives a task to add one.

  • If they decline, Riot does not ask again.

  • Only addresses verified through the link sent by email are checked. The employee can remove their personal address from Riot.

Can you see breaches on personal addresses as an admin?

  • You can see that a personal address is affected, but never which one or who it belongs to.

  • If the Sonar audience has fewer than 20 employees, issues linked to personal addresses are not listed at all, so that nobody can be identified. The employee still receives their task.

How can I tell whether the employee has really changed their password?

Riot cannot verify a password change. The issue is resolved on the employee’s say-so, when they complete the task.

Will my employees be chased endlessly?

  • No. All of their open breaches are grouped into a single task.

  • If there is no response after the chosen time (2 missions by default), the issue closes and Riot stops asking them about that breach.

  • A new breach opens a new issue.

Can breaches be tracked without notifying employees?

Not for this rule alone. The only way is to turn off the sending of tasks to employees in the Sonar settings, which stops the tasks for all Sonar rules.

What if my plan does not include the rule?

The rule can still be turned on: it shows a one-off scan with a link to change plan. Issues are listed but stay at the detected status, and no employee is contacted.

How does the rule work if I am still on Karma?

  • The employee receives one Riot task per service concerned, instead of a task in their mission.

  • The rule refers to “months” instead of “missions”, and the time limit is counted in months.

  • With delivery during working hours, the employee also receives a message.

What data does Riot keep?

The list of known breaches, the addresses found in each breach, the personal addresses added by employees, and the issues. Riot sends the addresses it checks to Have I Been Pwned.


Key takeaways

  • Breaches has become the Sonar data breaches rule (Sonar Pro and Max plans), found in Sonar › Rules.

  • Addresses are checked every day, and each employee receives a single “Secure your accounts” task.

  • You choose the monitored addresses, the breach age, the sensitivity, the delivery time and the closing delay.

  • Personal addresses remain anonymous on the admin side.

  • Issues can be closed one by one or in bulk.

Did this answer your question?