| Table of Contents |
|---|
2024-112-1731
| Status | |
|---|---|
|
...
|
...
|
...
In the coming weeks INKY will roll out a new User Dashboard as the default where users can manage their Blocked Sender Addresses, Blocked Sender Domains, Personal Allow List, Graymail Handling, and Signature Settings.
You’ll soon see a new pink banner at the top of the current User Dashboard with a link to the new User Center.
...
Selecting the banner will take you to the new User Center that streamlines the user experience and provides a single application for all users and admins within INKY.
...
Please reach out to support@inky.com if you experience any issues with the new User Center or feedback@inky.com with any thoughts!
| Status | ||||
|---|---|---|---|---|
|
...
Burst Detection
Burst Detection will gradually roll out. If you are under a Burst Attack—often referred to as a Spam Bomb, Subscription Attack, Email Bomb, Email Flood Attack, or Email Storm—please reach out to support@inky.com to have this feature enabled specifically for your team or organization.
INKY introduces Burst Detection, a powerful new feature to help administrators detect and respond to sudden surges in email volume targeting specific recipients over a short period. These bursts can be part of a strategy to overwhelm or distract users, often paired with unsolicited tech support calls or other suspicious offers to help “resolve” the issue.
Configuration can be found on: https://app.inkyphishfence.com/settings/api-access, you’ll now be able to add M365 or Google Workspace groups directly to the Admin Management page. This allows members to access INKY at the level of access assigned to the group.
This was previously handled through manually adding the Tenant ID and Group ID directly to the page - this enhancement now allows you to scroll the list of groups within your tenant to directly select the intended group.
Follow the steps found here to get started: https://inkyops.atlassian.net/wiki/spaces/AG2/pages/1800438086/Admin+Management#Add-Admin-by-Active-Directory-Groups
...
You can also assign groups to an organization level. Organizations are denoted with the “Skyscraper” icon, options listed when you have an organization selected affect all of the child teams - including which users can manage a child team. Groups pulled at an organization level come from the base team that’s created to build an organization.
For example: polvocapital-o365 is the base teamid used for INKY’s honeypot account. In the picture above there is no “Skyscraper” icon next to “Polvo Capital” in the top left corner of the picture - this means we’re looking at the base team.
In the picture below you’ll see fewer settings options and the “Skyscraper” icon next to “Polvo Capital” - these means we’re looking at the organization level. The groups in the Tenant Group dropdown are the same as the base team because the organization inherits them. This allows MSPs (organizations) the ability to assign groups to specific INKY roles, giving members access at the appropriate level to all child teams.
...
Learn more here: Burst Detection
| Info |
|---|
You can configure Burst Detection at either the team level or the organization level to apply consistent detection parameters across all teams. Any team-level setting will override the organization-level values. |
With the new Burst Detection feature, administrators can configure:
Burst Interval (seconds)
Define a time window — for example, 300 seconds — within which to measure a surge in email volume.Message Threshold
Set the minimum number of messages (e.g., 20) needed to trigger detection of a burst in that time interval.Burst Mode Cache Duration (seconds)
Keep a recipient in “burst mode” for a set duration after the initial burst detection to ensure continued protection, even if the volume temporarily dips.Ignore Senders/Recipients for Burst Detection
Specify email addresses or domains that should never trigger or be flagged as part of a burst (useful for high-volume internal senders or privileged services).Result Bucket
Choose the category (e.g., “Caution (Spam)”) that INKY assigns when a message is detected as part of a burst.Delivery Target
Override the delivery action (e.g., route to “Junk Folder”) for burst-detected messages.Exclude Internal or Trusted 3rd Party Messages
Automatically skip internal or trusted third-party messages from burst calculations.Exclude Known External Messages
Similarly, skip known external, trusted contacts from contributing to burst detection.
...
How It Works
When a sudden surge in email volume meets or exceeds the specified “Message Threshold” within the configured “Burst Interval,” the target recipient is immediately considered in “burst mode.” Messages are flagged under the “Suspicious Mail Burst” threat category, and INKY will apply the configured result bucket and delivery target for the duration of the “Burst Mode Cache.”
Use Burst Detection to protect against potential social engineering attacks that rely on message spamming, or to stay alert when a specific user suddenly becomes a high-volume email target.
For more information on setting up or fine-tuning Burst Detection, refer to your INKY documentation or contact your INKY support representative.
| Status | ||
|---|---|---|
|
Found within the Dashboard Widget Filter Editor under Analysis → Brand Impersonation is a new capability to filter messages based on the detected brands domain. Selecting a specific brand’s domain or multiple brand domains will retrieve a list of messages that INKY has identified as Brand Impersonation based on the brand selected.
...
| Status | ||
|---|---|---|
|
With this update, hovering over the From and Reply-To email addresses in a message header will display a popup rendering the address in a mono-font and lowercase. This design improvement helps users quickly identify confusable characters and spot potential phishing attack vectors with greater ease.
...
| Status | ||
|---|---|---|
|
We've added concise, helpful descriptions to some of the less obvious filters in the Filter Editor. For example, the Brand Impersonation Filter now includes guidance on detecting impersonations based on a brand's primary domain. These updates make it easier to understand and configure filters for your security needs.
...