1 Setup Guide Revision F Using McAfee SaaS Protection to Secure Exchange Online in Microsoft Office 365 Setting up Microsoft Office 365 Use this guide to configure Microsoft Office 365 and Microsoft Exchange Online for use with McAfee SaaS Protection. Perform these steps at a time when the volume of traffic is low to minimize the impact on your users. Also, follow your standard maintenance procedures and notify your users ahead of time of potential interruptions in service. About Microsoft Office 365 Microsoft Office 365 is a cloud-based service that offers online mail hosting and productivity software, including hosted Microsoft Exchange (Exchange Online). Securing Exchange Online with McAfee SaaS Protection provides superior threat protection, spam filtering, and the latest encryption, DLP, and click-time technologies. Securing inbound mail flow To secure inbound mail flow, configure your MX Records and inbound servers in Protection. Then, create rules in Exchange Online to restrict flow to your hosted server. How inbound is routed The MX records for your domain determine the server that is responsible for accepting inbound for your users. With Office 365, the MX records point to the Exchange Online service in the cloud. However, when you secure Office 365 with Protection, your MX records point to the 1
2 McAfee SaaS service. McAfee SaaS then filters and relays inbound to Exchange Online and your users. The following examples explain each process. Inbound mail without McAfee SaaS Protection Figure 1 Inbound mail with Office Someone sends an to an Exchange Online recipient. 2 Their server performs an MX Record lookup and determines that Exchange Online is the destination for the message. Exchange Online receives and stores the in the cloud. 3 The recipient's client communicates with Exchange Online so that the user can access their . The recipient opens the using Microsoft Outlook or the Outlook Web Application (OWA). Inbound mail with Office 365 secured by Protection Figure 2 Inbound mail with Office 365 secured by Protection 1 Someone sends an to an Exchange Online recipient who is secured by McAfee SaaS Protection. 2 An MX record lookup determines that McAfee SaaS Protection is the destination for the message. 2
3 3 McAfee SaaS Protection scans the and then forwards it to Exchange Online. 4 The recipient's client communicates with Exchange Online so that the user can access their . The recipient opens the using Microsoft Outlook or the Outlook Web Application (OWA). Set up inbound servers in SaaS Protection Add an inbound server in Protection so that filtered is routed to Exchange Online. Before you begin Add or migrate all your domains to Office 365. Make sure you can access your DNS provider's administrative application. Repeat this process for each of your domains. Task 1 Locate and copy the MX record for the domain in Office 365. Microsoft generates MX records for your domains when you set them up in Exchange Online. a Log on to your Microsoft Office 365 account as an administrator. b Select Admin Office 365. c d e In the left pane, click Domains. Select the domain, click Manage DNS. Under Exchange Online, find the MX row in the table and copy the value from the Points to address column. Figure 3 Exchange Online MX record Use this value in the next step. 3
4 2 Go to the Control Console and configure an inbound server using the value you copied in the SMTP Host Address field. a Select Protection Setup Inbound Servers. Figure 4 Inbound Servers Setup b Click Add New Host. A new row appears. c In the SMTP Host Address field, paste the value you copied in Office 365. d e f g In the Port field, enter 25 (default value). In the Preference field, enter 10 (default value). Select Active to enable the inbound server. Click Save. The inbound server is now setup and active, and filtered is relayed to Office 365. However, no will flow through Protection until the next step. 4
5 3 Determine the MX records to use for your region. a In the Control Console, select Protection Setup MX Records. Figure 5 MX records setup page with sample values b Select your preferred region. The page refreshes with the recommended MX records for your region. Have this information ready for the next step. 5
6 4 Configure your DNS provider's administrative application. a In a separate window, open your DNS provider's administrative application. b Copy and paste the recommended MX records found in the Control Console as the MX values in your DNS provider's administrative application. Your MX record setup is complete. is now flowing through Protection to Office 365 and Exchange Online. However, due to DNS caching, some DNS servers might not recognize the change for up to three days or longer. Add a mail flow rule to bypass spam filtering Create a mail flow rule to turn off spam filtering in Exchange Online and use SaaS Protection exclusively. Before you begin Allow 72 hours for your MX records to update before activating rules in Office 365. Copy the CIDR /21 Notation values from the Lock Down section of the MX Records Setup page in SaaS Protection. Access your Exchange Online Protection (EOP) Console. Task 1 Log on to your Microsoft Office 365 account. 2 From the title bar, select Admin Exchange to open the Exchange admin center page. Figure 6 Admin menu 6
7 3 In the left navigation, click mail flow. Select rules. Figure 7 mail flow rules 4 Click the pull-down menu for the add icon and select Bypass spam filtering. 7
8 5 In the Rule window, complete the required fields. Figure 8 new rule 8
9 Option Name Apply this rule if Instructions Enter a name for the rule. For example, Disable spam filtering in Office Select The sender IP address is in any of these ranges or exactly matches. 2 In the specify IP address ranges window, enter the /21 IP address range you copy and paste from the Lock Down section of the MX Records Setup page in the Control Console. 3 Click the add icon for each range. 4 Click ok. Do the following Except if Audit this rule with severity level Choose a mode for this rule Set the spam confidence level (SCL) to... Bypass spam filtering (Default Values). Do not add an exception. Deselect. Select Enforce. 6 Click save. The rules list updates with the new rule. You can review the rule logic in the right side of the page. Add a mail flow rule to lock down Exchange Online Create a mail flow rule that only accepts from SaaS Protection. This change ensures that spammers cannot bypass the service. Before you begin Allow 72 hours for your MX records to update before activating rules in Office 365. Copy the CIDR /21 Notation values from the Lock Down section of the MX Records Setup page in SaaS Protection. Access your Exchange Online Protection (EOP) Console. Task 1 Log on to your Microsoft Office 365 account. 2 From the title bar, select Admin Exchange to open the Exchange admin center page. Figure 9 Admin menu 9
10 3 In the left navigation, click mail flow. Select rules. Figure 10 mail flow rules 4 Click the pull-down menu for the add icon and select Restrict messages by sender or recipient... 10
11 5 In the Rule window, complete the required fields. Figure 11 new rule Option Name Apply this rule if Instructions Enter a name for the rule. For example, Only accept inbound mail from SaaS Protection. 1 Select The sender is located. 2 In the select sender location window, select Outside the organization. 3 Click ok. Do the following Audit this rule with severity level Choose a mode for this rule Select Delete the message without notifying anyone. Deselect. Select Enforce. You have completed the basic form requirements. The rule as it is written blocks all incoming . 11
12 6 Add an exception to allow flow from SaaS Protection. Figure 12 new rule Except if specify IP address ranges a Click More options. New fields appear. b Under Except if, click add exception. A new drop-down menu appears. c d e f Select The sender... IP address is in any of these ranges or exactly matches. In the specify IP address ranges window, enter the /21 IP address range you copy and paste from the Lock Down section of the MX Records Setup page in the Control Console. Click the add icon for each range. Click ok. The window closes and the new exception logic appears in the Except if field. 7 Click save. The rules list updates with the new rule. You can review the rule logic in the right side of the page. 12
13 Securing outbound mail flow To secure outbound mail, configure your outbound servers in the McAfee SaaS Control Console and add an outbound connector in Exchange Online. The outbound mail setup process is optional. Follow these steps if you have purchased outbound service. How outbound mail is routed To secure your outbound mail, relay your through the McAfee SaaS service using an outbound connector in Exchange Online. The following examples explain each scenario. Outbound mail without McAfee SaaS Protection Figure 13 Outbound mail with Office You send an to an external recipient using the Microsoft Outlook desktop application or the Outlook Web Application (OWA). 2 Office 365 performs an MX lookup and sends the to the recipient's server. 3 The recipient opens the in their client. Outbound mail with Exchange Online secured by McAfee SaaS Protection Figure 14 Outbound mail with Office 365 secured by McAfee SaaS Protection 13
14 1 You send an using the Microsoft Outlook desktop application or the Outlook Web Application (OWA). 2 Office 365 uses the outbound connector to route all outbound messages through Protection. 3 Protection performs the MX lookup and sends the to the recipient's server. 4 The recipient opens the in their client. Set up outbound servers in SaaS Protection In the Outbound Server Setup page, allow Protection to filter from Microsoft Office 365. Repeat this process for each of your domains. Before you begin Outbound server configuration is region aware. Before adding outbound servers, select your region by going to Setup MX Records. Task 1 In the Control Console, select Protection Setup Outbound Servers. Figure 15 Outbound Server Setup Office If necessary, use the domain link in the upper right to change domains. 3 Click More Options... 4 Under Allow filtering from, select Microsoft Office Click Save. Wait at least 30 minutes for your new settings to take effect. 14
15 Add an outbound connector to set up your outbound server Configure Microsoft Office 365 to route outbound to Protection. Before you begin Set up your Outbound Servers in Protection before configuring Office 365. Copy the host name (in bold text) from the Outbound Servers Setup page in Protection. Figure 16 Copy the host name displayed in bold text Task 1 Log on to your Microsoft Office 365 account. 2 Select Admin Exchange to open the Exchange admin center page. Figure 17 Admin menu 15
16 3 In the left navigation, click mail flow. Select connectors. Figure 18 mail flow connectors 4 Under Outbound Connectors, click the add icon. 16
17 5 In the new outbound connector window, complete the required fields. Figure 19 new outbound connector Option Name Enable outbound connector Connector Type Definition Enter a name for the new outbound connector. For example, Relay outbound mail to McAfee SaaS. Select to enable (default value). Select Partner (default value). 17
18 Option Comment Connection Security Outbound Delivery Definition Enter a description. For example, Relays all outbound from all domains on Office 365 to all recipient domains through McAfee SaaS Protection. Select Opportunistic TLS (default value). Select Route mail through smart hosts and add a smart host. 1 Click the add icon to add a smart host. 2 In the add smart host window, enter the host name that appeared in bold that you copied from the Outbound Servers Setup page. 3 Click save. Recipient Domains Add domains. 1 Click the add icon to add a domain. 2 In the add domain window, enter * to specify all domains. 3 Click ok. 6 Click save. The page updates to display the new outbound connector. Congratulations! You have completed the installation process. Office 365 is now secured by McAfee SaaS Protection. Copyright 2015 McAfee, Inc. Intel and the Intel logo are trademarks/registered trademarks of Intel Corporation. McAfee and the McAfee logo are trademarks/ registered trademarks of McAfee, Inc. Other names and brands may be claimed as the property of others gde_O365- integrationguide_0215f00
Product Guide Revision A SaaS Email Encryption Enablement for Customers, Domains, and Users Email Encryption Customers who are provisioned for SaaS Email Encryption can easily configure their Content Policies
Trend Micro Email Encryption Gateway 5.0 Deployment Guide January 2009 Trend Micro, Inc. 10101 N. De Anza Blvd. Cupertino, CA 95014 USA T +1.800.228.5651 / +1.408.257.1500 F +1.408.257.2003 www.trendmicro.com
Product Guide McAfee Enterprise Mobility Management 11.0 Software For use with epolicy Orchestrator 4.6.5-5.0 Software COPYRIGHT Copyright 2013 McAfee, Inc. Do not copy without permission. TRADEMARK ATTRIBUTIONS
Archive Add-in Administrator Guide RESTRICTION ON USE, PUBLICATION, OR DISCLOSURE OF PROPRIETARY INFORMATION Copyright 2011 McAfee, Inc. This document contains information that is proprietary and confidential
Getting Started Guide Cloud Server powered by Mac OS X Getting Started Guide Page 1 Getting Started Guide: Cloud Server powered by Mac OS X Version 1.0 (02.16.10) Copyright 2010 GoDaddy.com Software, Inc.
Chapter 10 Encryption Service The Encryption Service feature works in tandem with Dell SonicWALL Email Security as a Software-as-a-Service (SaaS), which provides secure data mail delivery solutions. The
CHAPTER114 The window in Cisco Unified Communications Manager Administration allows the administrator to add, search, display, and maintain information about Cisco Unified Communications Manager end users.
Trend Micro Incorporated reserves the right to make changes to this document and to Hosted Email Security described herein without notice. Before installing and using Hosted Email Security, please review
PureMessage for Microsoft Exchange Help Product version: 3.1 Document date: June 2015 Contents 1 About PureMessage for Microsoft Exchange...4 2 Key concepts...5 2.1 Key concepts overview...5 2.2 Inbound,
Configuration Guide BES12 Version 12.1 Published: 2015-04-22 SWD-20150422113638568 Contents Introduction... 7 About this guide...7 What is BES12?...7 Key features of BES12... 8 Product documentation...
DEPLOYMENT GUIDE Version 1.2 Deploying the BIG-IP System v10 with Microsoft IIS 7.0 and 7.5 Table of Contents Table of Contents Deploying the BIG-IP system v10 with Microsoft IIS Prerequisites and configuration
Dell KACE K1000 Management Appliance Service Desk Administrator Guide Release 5.3 Revision Date: May 13, 2011 2004-2011 Dell, Inc. All rights reserved. Information concerning third-party copyrights and
Iomega EZ Media and Backup Center User Guide Table of Contents Setting up Your Device... 1 Setup Overview... 1 Set up My Iomega StorCenter If It's Not Discovered... 2 Discovering with Iomega Storage Manager...
USER CONFERENCE 2011 SAN FRANCISCO APRIL 26 29 Running MarkLogic in the Cloud DEVELOPER LOUNGE LAB Table of Contents UNIT 1: Lab description... 3 Pre-requisites:... 3 UNIT 2: Launching an instance on EC2...
Product Guide McAfee Help Desk 2.0 Software About Help Desk McAfee Help Desk is an extension installed in McAfee epolicy Orchestrator (McAfee epo ). Administrators use McAfee Help Desk to issue challenge/response
E-mail Filter SurfControl E-mail Filter 5.0 for SMTP Getting Started Guide www.surfcontrol.com The World s #1 Web & E-mail Filtering Company CONTENTS CONTENTS INTRODUCTION About This Document...2 Product
SonicWALL Email Security Appliance Administrator Guide Version 7.3 SonicWALL, Inc. 2001 Logic Drive San Jose, CA 95124-3452 Phone: +1.408.745.9600 Fax: +1.408.745.9300 E-mail: email@example.com Part Number:
This release connector is deprecated. Use Kofax Capture and the appropriate Kofax Capture release script to release documents to a specific destination. KOFAX Front-Office Server 2.7 Configuration Guide