Message platform for automated threat simulation, reporting, detection, and remediation
摘要
說明書
The system can also be configured to quarantine specific messages that were received by users, but not reported. As a non-limiting example, if an individual message, or a cluster of messages is designated for quarantine, then messages that would be in the cluster, or are similar to a specific message, but are un-reported messages, can also be quarantined.
To effect this, in some embodiments, the search module can execute a persistent search. The search module can be provided with a set of parameters and can be configured to trigger on new messages that match that criteria. In response to that match, the triggering message can be automatically removed from user accounts by the generation of the corresponding command to the enterprise server through the operator portal.
In some embodiments, when a portal user initiates a quarantine request, the system does not permanently delete the selected emails from the organization's email server. Rather, it inspects the unique message ID of the emails to be quarantined and instructs the enterprise email server to move the original emails to a folder that is hidden from the recipient's view. The organization's email team can still access the emails from the hidden folder if needed. Similarly, the quarantined, e.g., hidden, email can then be quickly restored by moving it from the hidden folder to a visible folder, such as the user inbox.
In some embodiments, the quarantine function does not permanently delete quarantined emails from an organization's email server. Rather, it moves the emails to a separate folder, e.g. called Quarantined Items, that is hidden from the recipient's view. The organization's email team can still access the emails from this folder if needed.
Out-of-Band On-Demand Simulation
