Sensitive data: highlights and what happened to them

Insights > Sensitive data shows how often BeeSensible highlighted sensitive data in your organisation, in which apps, what types of data were involved and what employees did about the highlight. You use the screen to see whether sensitive data is adjusted before it is sent and whether a change to your settings has an effect. Here too you see counts only: the typed text appears nowhere, and a detection carries no user ID.

#Period and filters

Period sets the time frame, from Last 7 days to Last year, or a time frame with your own dates. You cannot look back further than the 24-month retention period. When Department insights is on, you can also pick a department. Filters narrows every card at once by Platform, Entity type (custom terms included) and Level (Standard or Critical). Clear all removes the filters again.

#The four headline figures

Each headline figure shows the change from the previous period.

• Detections is the total number of detections.
• Critical detections is the number of detections at Critical level, with their share of the total.
• Adjusted before sending is the share of detections the user masked or removed before sending. Masking on send and replacements from earlier versions are included.
• Critical sent despite warning is the number of critical detections sent without changes, with their share and the number of messages they were in. This figure says most about the risk that remains, which is why it is the one to steer by.

Detections over time shows the number of detections per day, with Standard and Critical shown separately. This chart tells you whether a change to a detection profile, a policy or a notice has had an effect.

#Outcomes

The Outcomes card divides all detections in the period across a single bar:

A Replaced segment appears only while the chosen period includes replacements made before version 5.7.1. The grey segment, No action recorded, is not a judgement of what employees did: it also includes detections from before BeeSensible tracked outcomes.

#By platform, data type and department

Detections by platform shows, for each app, the number of detections, how many of them were critical and what share was adjusted. An app found both in the browser and in the desktop app is labelled Web or Desktop. Detected entity types shows the same figures per type of data, with critical types first and custom terms marked "(custom term)". Clicking a row filters the whole page. It is worth looking at the smaller bars as well, because financial data and identification numbers are usually rare but weigh heavily when they are sent.

When Department insights is on (under Organisation > Settings), Departments shows the number of critical detections per person in each department, and how many of those took place in disallowed tools. The figure is calculated per person so that a large department does not automatically look worse than a small one. Departments smaller than the minimum (5 people by default) and people without a department are grouped together under Other. With a department filter, the period is at least 7 days.

#From 5 active users

Figures appear from 5 active users, meaning members who have activated the extension or the desktop app. Invited members who never started do not count. As long as your organisation is below that number, this screen shows the Figures from 5 active users card. From that card you invite colleagues, and during a trial you can switch on demo data or the sandbox.

However narrowly you filter, BeeSensible records no user with a detection and the dashboard has no per-employee view. Roles and responsibility explains this in more detail.