Triage
Investigate an incident, record your verdict, and choose a remediation action.
Navigate the workspace
Use the header’s previous and next controls to move between incidents. The subject and case information identify the incident you’re reviewing.
Select a side-panel icon to open:
- Remediation
- Triage activity
- Release requests (requires read permission)
Collapse the panel for more space; select an icon to reopen it. Evidence and side panels scroll independently.
Keyboard shortcuts
| Key | Action |
|---|---|
h | Next incident |
l | Previous incident |
e | Scroll to the email section |
e, then a | Expand and scroll to attachments |
i | Scroll to identity analysis |
Cmd-K / Ctrl-K | Open Command Search |
Letter shortcuts are disabled while typing in text fields. Leaving an unsaved review prompts you to stay or discard your changes.
Overview section
Overview shows SucuriLabs’s verdict and the reasoning behind it.
Classification reasoning
Verdicts include:
- Benign
- Malicious
- Spam
- Unknown
Reasoning can reference:
- Sender authentication
- Message content
- Links
- Attachments
- Other detection signals
Using the overview
Read the reasoning, then compare it with the email, attachments, identity analysis, and activity before recording your review.
Remediation
Record your classification and any mailbox action in Remediation.
How remediation works
The panel shows:
- Review status
- AI verdict
- Last action
- Saved notes
Select a classification under Review to expand the action and comment controls. Select an existing review to edit it.
Review decision
Choose the classification that matches your investigation.
| Review option | When to use it |
|---|---|
| Spam | Unwanted or unsolicited, but not necessarily malicious |
| Benign | Legitimate message |
| Malicious | Harmful message or attack attempt |
| Simulation | Authorized simulation |
Your classification can confirm or override the AI verdict.
Remediation action
Optionally select an action to apply when you submit the review. You can save a classification or comment without choosing a new mailbox action.
| Action | What it does |
|---|---|
| Move to spam | Moves the message to the recipient’s spam folder |
| Quarantine | Isolates the message from the recipient |
| Restore | Returns the message to the inbox |
| Banner | Adds a warning banner |
| Trash | Moves the message to trash |
Restore is available when the current action is:
- Trash
- Move to spam
- Quarantine
Other actions depend on the integration and workspace policy. Individual release requests are reviewed separately.
Comment and sharing
Add a comment to explain your decision. Enable Share with SucuriLabs to share the incident for detection improvements, or leave it off to keep it private to your organization.
Select Submit to save the review and apply the selected action, or Cancel to reset your edits. Use Skip review to set aside an unreviewed incident and Review to return a skipped incident to the workflow.
Triage activity
Open Triage activity to see changes, actors, and timestamps. Verified release restorations include the mailbox and completion time without changing the incident-wide classification or action. The timeline refreshes while the panel is open and the page is visible.
Saving a review or approving a release does not confirm a completed mailbox move. Restoration activity appears only after verification.
Release requests
Open Release requests to review requests linked to this incident. Filter by:
- Pending
- Denied
- Approved
Inspect or decide a request according to your permissions. Approval starts restoration of only the requested message.
See Review Release Requests for bulk decisions, retries, and restoration outcomes.
View the original message details and available content in Email.
Metadata
The message header includes these fields.
| Field | Description |
|---|---|
| Subject | Message subject |
| Sender | Sender name and email address |
| Recipients | Message recipients |
| Received | Receipt date and time |
Message content access
Your message-content policy sets one of these access modes:
- Immediate access
- Opt-in confirmation
- Justification
Enter a reason when prompted and select Request Access. Justifications are recorded, not sent to another person for approval.
Once access is granted, use the available content tabs:
- Preview
- Text
- HTML
- Headers
- EML
Tabs depend on retained content. Expired content may be unavailable even when metadata remains. Access is audited and also controls downloads.
Attachments
Expand Attachments in the email section to inspect included files.
Attachment metadata
The attachment list includes these fields.
| Column | Description |
|---|---|
| File Name | Attachment filename |
| Mime/Type | Detected content type |
| File Size | File size |
| First Obs. | First observation in SucuriLabs |
Select the filename or copy control to copy its SHA-256 hash. A Malicious indicator marks files classified as malicious; its absence does not guarantee that a file is safe.
Reviewing attachments
Compare file metadata with the expected message. Unusual types or names and repeated hashes can help identify a broader campaign. Where policy permits, download files for analysis in a safe environment.
Identity analysis
Use Identity Analysis to check the sender and possible impersonation.
Detected entities
Entities identify the following people and accounts mentioned in the message:
- Recipients
- Monitored users
- Accounts
- Contacts
Review them for targeting or impersonation of a known identity.
Sender assessment
Compare the assessed identity and display name with the email address and domain. Mismatches may indicate spoofing or impersonation.
Sender metadata
Sender metadata provides infrastructure and authentication details.
| Field | Description |
|---|---|
| Domain | Sender’s email domain |
| IP | Message source IP or network |
| Geolocation | Detected location of the sending infrastructure |
| ASN | Autonomous system associated with the sender IP |
| Authentication | SPF, DKIM, and DMARC results |
Authentication results help assess whether the sender was authorized to use the domain. Failures can indicate spoofing or misconfiguration. Consider these results alongside the content and attachments, not as a verdict on their own.

