Skip to content

Sublime Security

Integrate your Incident Register with Sublime Security. This integration imports flagged email message groups as Incident records. Each Sublime message group becomes one incident. Adversarial sets each incident’s status from what Sublime reports: the review verdict, Sublime’s attack score, the flagged rules, and what recipients did with the email. Attacks are imported without a severity, so you can score them with AI scoring or by hand. A group that turns out not to be an attack closes its incident at SEV-5.

  • Source: Email Protection
  • Opened By: The integration’s integration user, which has the same name as the integration.

You need a Sublime API key. A Sublime API key carries the role of the user who creates it and cannot be scoped. Create it while signed in as a user with a custom read-only role that can view message groups and detection rules.

  1. In Adversarial, go to Settings > Integrations and select Add.
  2. Select INC in the Sublime Security row.
  3. Enter an Instance Name, such as Sublime Production.
  4. Open Connection and select Add a connection…. Enter a Connection Name and complete the fields:
    • Region — the Sublime Cloud region in your dashboard URL. Enter na-east if your dashboard is at platform.sublime.security. Otherwise, enter the part before .platform.sublime.security, for example eu for eu.platform.sublime.security. The supported regions are na-east, na-east-2 to na-east-5, na-west, na-west-2, na-west-3, ca, eu, uk, and au.
    • API Key — the Sublime API key.
  5. Select Save Connection, then Save.

One connection can be used for every Sublime Security integration you add, or you have the flexibility to use multiple connections with API keys created by users with different roles to bring in different data. Each integration can tag the incidents it imports, so you can filter each integration’s incidents separately. Make sure each connection’s API key brings in unique message groups, not the same message groups, which would import as duplicate incidents. See Connections.

The integration reads message groups that Sublime flagged. It does not import:

  • Groups that Sublime classifies as graymail.
  • Groups reviewed by a Sublime auto-review rule.
  • Groups that are not an attack. A group is not an attack when either of these is true:
    • A reviewer classified it in Sublime as Benign, Non-violation, Spam, Graymail, Unwanted, or Simulation.
    • Nobody has reviewed it, Sublime’s attack score is Likely benign, Spam, or Graymail, and no user reported it.

An incident that was imported before its group became “not an attack” is not deleted. The next sync sets it to SEV-5 and closes it. An incident whose group a Sublime auto-review rule reviews after import is also not deleted: the next sync closes it.

Sublime’s rule severity rates how confident a detection is, not the targeted intent and operational impact that the Cyber Incident Response Procedure (CIRP) rates, so it does not set the incident’s severity. It appears in the incident’s description instead.

Sublime Message Group Adversarial Severity
An attack None on import. AI scoring or a person sets it.
Not an attack, as defined in What Is Imported SEV-5
  • Attacks: an incident is imported without a severity. If the integration’s AI switch is on in Settings > Integrations, each new incident is AI scored when it is imported. Otherwise, select AI Score or set Severity yourself. AI scoring reads the incident’s description, which lists the flagged rules, any targeting, and what recipients did with the email.
  • Not an attack: the integration sets SEV-5 and a Severity Reasoning that names why, for example: “SEV-5: reviewed in Sublime as benign, so not attempted unauthorized activity.” This replaces an AI score.
  • An attack’s severity is left alone. A sync does not change or clear the severity of an attack, whether AI scoring or a person set it, including when the incident closes or reopens.
  • A group that becomes “not an attack” closes its incident and sets SEV-5.
  • A person set the severity: if a person set the severity last in Adversarial, a sync never changes it, including the SEV-5 for a group that is not an attack.
  • A group that becomes an attack again keeps its SEV-5 until you rescore it.

Status follows what happened to the email, then the Sublime review:

Sublime Message Group Adversarial Status
Not an attack Closed
Not reviewed, and no recipient opened, forwarded, replied to, clicked, or reported any message Closed
Not reviewed, and a recipient opened, forwarded, replied to, clicked, or reported a message New
Reviewed in Sublime with any classification except Skip Closed
Reviewed in Sublime as Skip In Progress
An unrecognized review status New
  • Unopened attacks close. An attack that nobody touched closes whether Sublime removed it from the inbox or it was delivered and never opened. A later sync reopens the incident if a recipient opens the message.
  • Opened attacks stay open, even with no tracked click. Sublime cannot see a click on a message it did not track.
  • A status a person set stays. If a person set the status last in Adversarial, a sync does not change it. Any other status follows Sublime on each sync.
Sublime Field Adversarial Field Notes
Flagged rule name, message subject Title Composed as the most severe flagged rule’s name followed by the first message’s subject
(multiple fields) Description Assembled from the message group; see Description
Earliest message time Detected Date When Sublime processed the earliest message. Falls back to the earliest user report.
Earliest message time Occurred Date Same as Detected Date
Message actions Contained Date When Sublime removed the email from the inbox by quarantine, trash, or spam. See Contained Date
(computed) Severity SEV-5 for a group that is not an attack; otherwise left for AI scoring or a person. See Severity Mapping
(computed) Severity Reasoning Set with the SEV-5; see Severity Mapping
(static) Source Always “Email Protection”

Title, Description, and the dates are updated on every sync. Severity changes only as Later syncs describes. A title edited by hand in Adversarial is overwritten on the next sync. To keep your edits, stop syncing the incident. Incidents are imported unassigned.

A group that Sublime removed from the inbox gets a Contained Date. Quarantine, move to trash, and move to spam count as removal. A warning banner does not count, because the email stays in the inbox.

  • Date: when Sublime removed the email. A sync can move the date earlier when it finds an earlier removal. It moves the date later only when Sublime restored the email and then removed it again.
  • No action date: if Sublime does not report when it removed the email, the date is the first sync that sees the removal, and later syncs keep that date. An incident that is already Closed does not get a date this way.
  • A date a person set stays. A sync never changes or clears a Contained Date that a person set in Adversarial.

The description starts with a View in Sublime link to the message group, followed by:

  • Flagged rules: each rule’s name, Sublime rule severity, tags, attack types, and tactics.
  • Targeting: shown when a flagged rule’s tactics or tags include Impersonation: Employee or Impersonation: VIP, which means the sender impersonates someone in your organization. The BEC/Fraud attack type on its own does not count as targeting, because Sublime also uses it for opportunistic scams.
  • Sender and Recipients: up to ten recipients from the messages Sublime previews.
  • Reported by: users who reported the email.
  • Outcome: whether Sublime removed the email from the inbox, how many messages were opened, and any replies, forwards, or tracked link clicks. Sublime tracks clicks only for messages covered by a link-click tracking rule in your Sublime tenant. For example: “removed from the inbox by Sublime; 0 of 2 messages opened; no replies, forwards or tracked link clicks”.
  • Classification and Review comment: when a reviewer classified the group in Sublime.

Sublime does not report when a group was last reviewed, so a sync cannot ask only for the groups that changed. Instead, each 15-minute sync re-reads every flagged group whose newest message arrived in the last 14 days, or since the last successful sync if that is earlier. This picks up reviews, opens, and reports on those groups, whenever they happen. A change to a group whose newest message is older than 14 days shows up after the nightly full sync, which reads every flagged group.