This article applies to:
- SEG Cloud
Question:
- What are the best practices for SEG Cloud configuration?
Reply:
SEG Cloud default configuration generally reflects good security practice. Customers can enhance security and efficiency by following some simple guidelines.
- Complete recommended setup steps from the Quick Start Guide.
- Be sure to populate the Executive Name List for anti-fraud.
- Lock down the local network so that email can only be sent inbound from SEG Cloud.
- Ensure all outbound mail is sent through SEG Cloud.
- Configure your SPF record in DNS with the SEG Cloud inclusion (for details see the pre-provisioning info for your region, linked from article Q21094).
- Set up and enable Invalid Recipient Handling (Inbound). This feature helps to reduce unwanted mail and potential attacks.
- Trustwave plans to require this feature for new customers soon.
- Set up the end user Spam Quarantine Management site (SQM) and message digests, to allow users to review blocked mail.
- Minimize exceptions to anti-spam rules.
- Do not exempt entire domains. Never exempt your own domain.
- As far as possible, avoid making exceptions for individual users. It is particularly important to NOT make exceptions for company executives - they are common targets of phishing and scams.
- Enable the "Block Spoofed Messages" rule for inbound messages. Before enabling this rule, you should review the results of the default "Monitor Spoofed Messages" to find any valid items that might be affected.
- Configure DKIM signing. Consider enabling DKIM signature verification rules.
- Configure DMARC:
- Add a DMARC record to DNS for each of your domains.
- Submit a support request to enable DMARC for your domains in SEG Cloud.
- Consider enabling additional security rules, such as attachment control block rules.
- Each customer will have unique requirements. Restricting un-needed items is the best security practice.
- Check this article from time to time. It will be edited to reflect new features and current security recommendations.
Trustwave MailMarshal Cloud KB article Q21154
Last Modified: October 6, 2020