Locking Down Your Firewall explained
Dear Primary Contact,
This graphic illustrates the steps required to connect your infrastructure to Mimecast. If you'd like more information click the image to visit our knowledge base. Green indicates your current step, while gray indicates completed steps.
As our SLA doesn't apply to attacks delivered from sources outside of Mimecast, we can't over emphasize the importance of the lockdown and suggest you do this as soon as possible.
If you are using Office 365, you can lock down your inbound mail flow as shown here.
If you are using another hosted mail platform, you'll want to inquire with your vendor as to what's possible in this regard. If they can't configure rules to only accept messages from Mimecast, please let us know so we can close out the project.
Final Steps
1. Ensure you've switched over all applicable MX records to point to Mimecast. We recommend in factoring two to three days to complete propagation of your new DNS records. This should account for varying TTLs, and poorly configured servers that are outside of your control.
2. Update your firewall settings to only allow connections from the IP addresses used for INBOUND mail delivery from the relevant Mimecast data center IP ranges.
3. Respond to this email to confirm you have locked your firewall down. We'll run a security check and email you to confirm whether this was successful.
Please respond to this email if you have any questions about this step.
Kind regards,
Mimecast North America, Inc.
480 Pleasant Street
Watertown, MA 02472
Carlos Rios
Comments