Adding .local secondary domain in CMP does not propagate over to CloudSOC

Products

• CASB Gateway Advanced
• CASB Advanced Threat Protection
• CASB Audit
• CASB Gateway
• CASB Security Advanced
• CASB Security Advanced IAAS
• CASB Security Premium
• CASB Security Premium IAAS
• CASB Security Standard
• CASB Securlet IAAS
• CASB Securlet SAAS
• CASB Securlet SAAS With DLP-CDS

Issue/Introduction

Adding a .local secondary domain in CMP does not propagate over to CloudSOC

Resolution

Email addresses associated with ,local domains may not be globally routable therefore are not allowed to be added as secondary domains in CloudSOC

CloudSOC tasks that requiring the  system to send an email won't work.

Some examples are sending CloudSOC User a password, getting an email with link to large report, Protect policy email alerts, etc.

Additional Information

The CloudSOC (CASB) email validator we use marks .local domains as invalid and the reason is:

 # RFC 6762 says that applications "may" treat ".local" as special and    # that "name resolution APIs and libraries SHOULD recognize these names    # as special," and since ".local" has no global definition, we reject    # it, as we expect email addresses to be globally routable.