MSFT - Cloud - Architecture - O365 File Protection
MSFT - Cloud - Architecture - O365 File Protection
Office 365
in Office 365
This topic is 1 of 4 in a series 1 2 3 4
2 Sensitive data
Some organizations have a subset of data that personally identifiable information, and some
needs to be protected both internally and categories of regulated data. Apply increased
externally from accidental oversharing and protection to targeted files within your Office
leakage. Examples include executive strategy 365 environment.
plans, product specifications, files with
File protection capabilities Microsoft provides a range of capabilities to protect your data. This document describes capabilities for
protecting files so you can choose the best options to protect your organization s data.
Baseline protection Increased data protection Protection for highly regulated data
Permissions for SharePoint and OneDrive for Hold Your Own Key (HYOK) with Active Directory
Data Loss Prevention (DLP) in Office 365
Business libraries Rights Management Service and SharePoint Online
Device access policies for SharePoint Online and Windows 10 capabilities: Bitlocker and Windows
OneDrive for Business Information Protection (WIP)
Identity and device capabilities Microsoft recommends protecting your identities and devices at similar levels that you protect your
data. These capabilities can be used together with file protection capabilities. For more information, see
Identity and Device Protection for Office 365.
Microsoft Cloud App Security -or- Office 365 Advanced Security Management
July 2017 © 2017 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at CloudAdop [email protected].
File Protection Solutions
Recommended architectures for protecting files in
Office 365
in Office 365
This topic is 2 of 4 in a series 1 2 3 4
Baseline protection This topic describes capabilities you can use to increase the baseline level of protection of files
in Office 365. Some of these capabilities apply broadly. Some of these capabilities can be
targeted to specific data sets.
Visitors
read
More information:
Understanding permission levels in SharePoint
Understanding SharePoint groups
• Don t allow sharing outside your • Prevent external users from sharing files, Currently only available in OneDrive for Business.
organization folders, sites they don t own Notify owners when:
• Allow sharing to authenticated external users • Require external users to accept sharing • Users invite additional external users to
only (allow new or limit to existing) invitations with the same account the shared files
• Allow sharing to external users with an invitation was sent to • External users accept invitations to access
anonymous access link files
• Limit external sharing using domains (allow • An anonymous access link is created or
and deny list) changed
• Choose the default link type (anonymous,
company shareable, or restricted)
Device access policies for SharePoint Online and OneDrive for Business
Conditional access and network location policies let you determine Azure Active Directory — The device based policies require two conditional
whether access to data is limited or blocked. access rules in Azure AD. These rules can be targeted to specific user groups,
otherwise they apply tenant-wide.
The device-based policies require Microsoft Intune (or another mobile device
management tool) and Azure Active Directory Premium P1. The network Microsoft Intune — Intune or another mobile device management tool is
location policy does not require additional licensing. required to enforce device compliance requirements. Devices must be
enrolled. Other mobile device management tools can only enforce these
Network location policy (in preview) — You can configure network location
conditional access rules for Windows 10 computers.
policies both in SharePoint admin center and in Azure Active Directory. Azure
Active Directory enforces this policy at sign in. Office 365 enforces this policy Settings apply tenant-wide unless conditional access policies in Azure Active
when resources are accessed. You can configure this in one or both places. Directory are targeted to specific users or groups. Coming soon is the ability
There is no dependency for configuring this in SharePoint admin center. to configure device access policies at the site level.
The chart below summarizes the capabilities and dependencies.
Objective Only allow access from Prevent users from Block access on non- Prevent users from Block access on non-
specific IP address downloading files to non- domain joined devices downloading files to compliant devices
locations domain joined devices non-compliant devices
SharePoint
admin center
Azure Active
Directory
Microsoft Intune
More information
SharePoint Online admin center: Control access from unmanaged devices
For information about implementing conditional access, see page two in this
content: Identity and Device Protection for Office 365.
July 2017 © 2017 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at CloudAdop [email protected].
File Protection Solutions Recommended architectures for protecting files in
Office 365
in Office 365
This topic is 3 of 4 in a series 1 2 3 4
On-premises
Office 365 Other SaaS services Other cloud provider
datacenters
SharePoint Online and Exchange Highly regulated & File repositories &
OneDrive for Business Online trade secret files other applications
Start with Office 365 labels Add Azure Information Protection to make sure
Office 365
Use Office 365 labels for files and mail in Office your data remains protected and your polices are
365. honored as files travel outside of Office 365
• Users can manually apply labels. Azure Information Protection labels can be
• SharePoint libraries can automatically assign additionally applied to files that require protection
labels. that travels with the files and persists outside of
Office 365.
• DLP rules can automatically assign labels.
• Any type of file that require protection or policy
• DLP rules can take action based on labels, such compliance inside and outside of your org, such
as blocking mail or files from being shared as visual markings, encryption, and permissions.
externally.
• Files that are shared across SaaS applications.
• Files stored on-premises or with other cloud
providers.
Office 365 DLP rules can also be used to take action
based on these labels.
Recommended use cases Retention and Office DLP. Sensitivity protection and persistency across apps and
environments.
Applying labels Choose labels from the document panel in SharePoint Online Choose labels within Office client apps from the Azure
and OneDrive for Business. Information Protection client ribbon. The client works with
Office versions 2010, 2013, and 2016. Azure Information
For mail, apply labels directly from Outlook 2016, Outlook
Protection policies can be configured to automatically
2013, or Outlook Web Access.
suggest or assign labels based on the contents of the file.
Use Office 365 DLP rules to automatically find and label
files. Users can also classify files by using Windows File Explorer.
Select a file, multiple files, or a folder. Right-click, and select
Configure SharePoint Online libraries to automatically Classify and protect.
label documents.
Additionally, administrators can use PowerShell with the
client to efficiently label files in bulk on Windows computers
and file shares. Similar support for SharePoint is coming
soon.
Azure Information Protection user guide
Protect and encrypt files Use DLP rules to protect files based on labels. Apply visual markings (such as watermarks) based on these
labels.
Protection does not currently include encryption.
Use DLP rules in Office 365 to protect files based on labels.
Use Azure Rights Management templates in Azure to
automatically apply encryption based on labels. This
protection includes defining rights for files. You can encrypt
using the defualt service encryption key, your own key (Bring
Your Own Key), or your own key that you hold on premises
(Hold Your Own Key).
File type support Office 365 labels work with all file types that are allowed File types supported by the Azure Information Protection
by the service. client
Types of files that cannot be added to a list or library
• Labels are created in the Security and Compliance Center. • Start with a template and identify what type of content to
• Publish labels to specific audiences (users or groups). automatically detect and label, such as content with passport
• Choose which locations to publish labels to—Exchange, numbers or social security numbers.
SharePoint, OneDrive accounts, and Office 365 Groups. • Apply the policy to all content in Office 365 or define specific
• Users apply labels or you can automatically apply labels by using locations. Specific locations include Exchange, SharePoint, and
a query (KQL query language) or other condition. OneDrive accounts. You can choose specific SharePoint sites and
OneDrive accounts.
• Add labels to DLP policy conditions.
• Detect when content is shared and determine what action to
SharePoint Online integration includes: take. Actions include, block sharing, alert user that sharing is not
• Labels show up in the document panel where users can easily allowed, allow the user to override the policy, and alert on the
apply them. sharing.
• Use labels as a library column and group documents by More information:
classification label.
New Office 365 capabilities help you proactively manage security and
• Configure a library to automatically classify all documents with a compliance risk
specific label.
Deployment
1 Activate Azure Rights Management 2 Decide what classification label(s) to 3 Update the labels to support your
apply to your sensitive files decisions
If you have implemented IRM with
SharePoint, this service is already You can customize the default labels and add Reconfigure the default Azure Information
activated. new labels. Protection labels to make any changes you
Default Azure Information Protection policy need to support your classification
Activating Azure Rights Management
settings decisions.
How to configure a label to apply Rights
Management protection
Azure Information Protection user guide The client side of Azure Information
Protection
Installing the Azure Information Protection
client
1 Install the Information Protection client 2 Use the client toolbar to apply labels 3 Upload files to the SharePoint library
If installation isn t automated, users can Be sure users know which IRM-protected
install the client manually. SharePoint library to use for your sensitive
A
files.
Download page for manual installation
OneDrive for
Business
Deployment
1 Create your own key vault in Azure 2 Add your key to the key vault 3 Enable your key with Office 365
Create a hardened container (a vault) in Generate your own key and transfer it to the Authorize your Office 365 tenant to use the
Azure, to store and manage cryptographic keys Azure Key Vault or create it directly in the vault. encryption key for files in OneDrive and
and secrets in Azure. SharePoint Online.
Add a key or secret to the key vault
Get started with Azure Key Vault
July 2017 © 2017 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].
File Protection Solutions Recommended architectures for protecting files in
Office 365
in Office 365
This topic is 3 of 4 in a series 1 2 3 4
For both BYOK and HYOK solutions: For BYOK: For HYOK:
• Review the classification labels and • Modify one of the default Azure Rights • Create a custom AD RMS rights policy
make any changes you need. Management Templates or create a new template on-premises for your highly
template with the desired protection. classified or regulated data.
Cloud On premises
Confidential
Confidential
(Default template)
You can customize the default labels and add You can associate one of the default Azure For HYOK file protection solutions, create an
new labels to the default Azure Information Rights Management templates to a label. You AD RMS rights policy template for the on-
Policy. can also customize the two default Azure premises AD RMS cluster.
The default Azure Information Protection Rights Management templates.
Then, associate the AD RMS protection policy
policy You can create new Azure Rights Management with an Azure Information Protection
Create a new label for Azure Information templates and apply these to a label. classification label by copying the AD RMS
Protection Create, configure, and publish a custom template GUID and cluster licensing URL into
template your Azure Information Protection admin
How to configure a label to apply Rights
portal.
Management protection Configure usage rights for Azure Rights
Management AD RMS Policy Templates
Continued on next page See Configuring HYOK in this blog
Bring Your Own Key (BYOK) with Azure Information Protection and
SharePoint Online
This solution is all in the cloud.
Microsoft Azure
• You generate an encryption key based on
your requirements and store it in Azure Key
Vault. Azure Rights Management Azure Key Vault
• You customize or create a new Azure Rights
Management template with the protections Azure Rights Management template Your BYOK key
needed for your data. Authorize your key to be
used by Azure Rights
• You associate this policy template with a
Management
label in the Azure Information policy.
Azure Information Protection
• Users apply protection by using the Azure
Information Protection client toolbar to Azure Information Protection Policy
select a label. Default
Highly
• You can use a private Office 365 Group or a Confidential
Labels Associate a
Microsoft Teams team to manage label with the
permissions to these files, including who can Confidential template
see the library.
General
Public
Personal
SharePoint Online
SharePoint Online
When users apply the label, the BYOK encryption key is used library
to encrypt the file. Labels can be applied before or after
adding the file to a SharePoint library. Labels can be modified.
Deployment
1 Create your own key vault in Azure 2 Add your key to the key vault 3 Activate Azure Rights Management
Create a hardened container (a vault) in Generate your own key and transfer it to the This service might already be activated for
Azure, to store an d manage cryptographic keys Azure Key Vault or create it directly in the your organization.
and secrets in Azure. vault.
Activating Azure Rights Management
Get started with Azure Key Vault Add a key or secret to the key vault
4 Configure the Azure Rights Management 5 Decide what classification labels) to 6 Update the labels to support your
service to use your encryption key apply to your sensitive files decisions
Authorize the Azure Rights Management You can customize the default labels and add Reconfigure the default Azure Information
service to use the key. new labels. Protection labels to make any changes you
Planning and implementing your Azure Default Azure Information Protection policy need to support your classification
Information Protection tenant key settings decisions.
How to configure a label to apply Rights
Management protection
7 Configure Azure Rights Management 8 Create a private Office 365 group or a 9 Install the Information Protection client
templates and associate these with labels Microsoft Teams team and add members and train users
Modify one of the default templates or create a You can script and automate the installation, You can script and automate the installation,
new template. Choose the protections to apply or users can install the client manually. or users can install the client manually.
to your sensitive data, in addition to encryption. The client side of Azure Information
Create an Office 365 Group in the admin center
Create, configure, and publish a custom template Protection
Turn on Microsoft Teams
Configure usage rights for Azure Rights Installing the Azure Information Protection
Management Microsoft Teams Help client
1 Install the Information Protection client 2 Use the client toolbar to apply labels 3 Upload files to the SharePoint library
If installation isn t automated, users can HYOK encryption is applied, including Be sure users know which SharePoint library
install the client manually. additional protections that are configured in to use for your highly confidential or
the RMS policy template. A
regulated data. Be sure the SharePoint
Download page for manual installation library is NOT IRM protected.
Hold Your Own Key (HYOK) with RMS and SharePoint Online
This solution brings together
components on premises and in the Microsoft Azure
cloud. On-premises network
Deployment
1 Activate Azure Rights Management 2 Decide what classification label(s)s to 3 Update the labels to support your
Azure Information Protection services are
apply to your sensitive files decisions
always cloud hosted but they enable you to You can customize the default labels and add Reconfigure the default Azure Information
operate in a cloud-only, hybrid, or on- new labels. Protection labels to make any changes you
premises only deployment. Default Azure Information Protection policy need to support your classification
settings decisions.
Activating Azure Rights Management
How to configure a label to apply Rights
Management protection
4 Deploy an Active Directory RMS cluster 5 Create, configure, and deploy a custom 6 Associate the AD RMS policy template
on premises RMS policy template with an Azure Information Protection
Hold your own key (HYOK) requirements and This policy template is part of the on-
classification label
restrictions for AD RMS protection premises RMS deployment. Copy the AD RMS template GUID and
Active Directory Rights Management Services cluster licensing URL into our Azure
AD RMS Policy Templates
Overview Information Protection admin portal.
AD RMS Rights Policy Templates
Test Lab Guide: Deploying an AD RMS Cluster See Configuring HYOK in this blog: Azure
Deployment Step-by-Step Guide Information Protection with HYOK
7 Create a private Office 365 group or a 8 Get ready to train users 9 Install the Information Protection client
Microsoft Teams team and add members
Produce user guidance that explains You can script and automate the
You can script and automate the installation, which label to apply and when. installation, or users can install the client
or users can install the client manually. manually.
Create an Office 365 Group in the admin center The client side of Azure Information
Protection
Turn on Microsoft Teams
Installing the Azure Information Protection
Microsoft Teams Help client
1 Install the Information Protection client 2 Use the client toolbar to apply labels 3 Upload files to the SharePoint library
If installation isn t automated, users can HYOK encryption is applied, including Be sure users know which SharePoint library
install the client manually. additional protections that are configured in to use for your highly confidential or
the RMS policy template. A
regulated data. Be sure the SharePoint
Download page for manual installation library is NOT IRM protected.
July 2017 © 2017 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].