Block a sender in Mimecast
Automatically block a sender in Mimecast from a Slack request with Stepwork, adding the address or domain to the blocked senders policy.
- Use case
- Security response & remediationInfoSec & Compliance
- Best for
- Security Analyst
- Applications used
Mimecast
Slack
- Business outcome
- Risk reduction
The problem
Sender blocks queue behind the email admin.
When phishing is active, analysts still wait for someone with Mimecast access to add the block. Mail keeps landing while the ticket ages.
Each delay is another inbox hit. Response time depends on who is free, not on the threat.
The outcome
Active phishing senders blocked in minutes
Stepwork adds the sender address or domain to the Mimecast blocked senders policy. The run records who asked and what was blocked.
- The sender address or domain is added to the block policy.
- New mail from that sender is blocked going forward.
- If the policy change cannot be completed, the run stops.
The process
From Slack request to a Mimecast sender block
Security posts the sender in Slack. Stepwork adds the block in Mimecast.
- Step 1
Request it in Slack
A teammate posts the sender address or domain to block. That message starts the flow, and Stepwork records who asked and when.
- Step 2
Open blocked senders
Stepwork signs in to Mimecast and opens the blocked senders policy. If the console path cannot be reached, the run stops.
- Step 3
Add the block
Stepwork adds the address or domain to the policy, the same change an email admin makes during an active phishing response.
- Step 4
Confirm and reply in Slack
Stepwork checks that the sender is blocked, then posts the result back in Slack.
Why Stepwork
Sender blocks stay on the response path
A deterministic agent runs the Mimecast block path you recorded. Active phishing does not wait on the next free admin.
Similar use cases
Similar use cases
Release a held message in MimecastLocates a specified held message and releases it to the recipient.
Contain a host in CrowdStrikeNetwork-contains a specified host from the Falcon console during incident response.
Lift host containment in CrowdStrikeReleases a host from network containment after remediation and verifies connectivity status.
FAQ
Common questions
Ask about this use case
Bob answers from this page and the rest of stepwork.com, and links each source.
Bob answers only from what Stepwork has published, and links every source. Questions are saved to improve answers, so leave out anything confidential.

