Views:
To ensure your organization achieves effective email security protection, Cloud Email Gateway Protection recommends you perform the following tasks after data migration:

Procedure

  1. Verify migrated policy data under Inbound Protection and Outbound Protection.
    1. Go to the following locations respectively:
      • Virus Scan
      • Spam Filtering
      • Content FilteringContent Policy
      • Data Loss PreventionData Loss Prevention (DLP) Policy
      Note
      Note
      After migration, policy rules are categorized into the following four types: virus scan, spam filtering, content filtering, and DLP.
    2. Select Error or Warning from the Migration status drop-down list.
    3. Follow the on-screen instructions in the Migration Status column to fix error settings or confirm warning settings and enable the corresponding policies.
    4. Reorder policy rules.
      You can manually reorder the policy rules in each domain after migration if they do not meet your requirements. For details, see Reordering Policy Rules.
  2. Verify other migrated data.
    1. Go to Inbound ProtectionConnection FilteringIP ReputationSettings to verify email reputation settings.
    2. Go to the following locations respectively to verify approved and blocked IP addresses:
      • Inbound ProtectionConnection FilteringIP ReputationApproved IP Addresses
      • Inbound ProtectionConnection FilteringIP ReputationBlocked IP Addresses
    3. Go to Inbound ProtectionDomain-based AuthenticationDomainKeys Identified Mail (DKIM) Verification to verify the Global DKIM Enforcement rule.
    4. Go to Inbound ProtectionDomain-based AuthenticationDomain-based Message Authentication, Reporting and Conformance (DMARC) to verify DMARC settings.
    5. Go to Inbound ProtectionSpam FilteringTime-of-Click Protection to verify time-of-click protection settings.
    6. Go to Outbound ProtectionDomain-based AuthenticationDomainKeys Identified Mail (DKIM) Signing to verify DKIM signature settings.
    7. Go to AdministrationPolicy Objects to verify policy object settings.