ThreatSpike Quarantined Email Release Guide

Modified on Thu, 22 Feb, 2024 at 9:55 AM

1             Overview


1.1 Document Information

 

All information about this document can be found in the following table:

 

Project Name: 

ThreatSpike Wire 

 

 

Document Reference Number: 

TSL-QUARANTINERELEASE 

Document Version No: 

1.0 

Author 

ThreatSpike Labs 

 

 

 

1.2 Document Aim

 

This document is to be used as a guide for users to release emails that are held in quarantine by the ThreatSpike Email Gateway.

 

2             What is a Quarantine Digest Email?

ThreatSpike will sender users email digests to their inboxes. These digest emails contain a list of quarantined emails that were destined for the users inbox, but have been quarantined by the email gateway. Emails get quarantined for a variety of reasons including spam, phishing and authentication failures.

 

An example of a digest email can be seen below:

  

3             How to release an email in quarantine?

If a legitimate email gets quarantined, users need to complete the following steps in order to release it to their inbox.

 

  1. Click the blue hyperlink in the digest email.

 

2. This will redirect the user to the ThreatSpike portal in a web browser. No logon is required.

 

Users can see the sender and subject of the quarantined emails. If a user believes an email is legitimate and wants it to be released, all they need to do is click the “Request Release" button next to the email.

 

This will forward the email to an on-shift SOC analyst for a final review to determine whether it is safe for release. If deemed safe, the email will be released. We guarantee email review and release within 1 hour of the requested release, however users can expect to wait roughly 10 minutes in most cases.










Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article