Showing posts with label prevention. Show all posts
Showing posts with label prevention. Show all posts

Wednesday, October 30, 2013

Office 365 compliance controls: Data Loss Prevention

AppId is over the quota
AppId is over the quota

 Shobhit Sahay is a product marketing manager on the Exchange team.

When was the last time you asked your employees to carry your company's handbook containing all the company policies with them? Do your IT workers know whether a particular email message they're sending may violate company policy and run the risk of being noncompliant? Are they sure whether an email they're sending contains sensitive information? Almost every IT worker faces compliance questions like these daily. Learn how you can help your IT workers achieve compliance without disrupting their normal routine or yours.

A recent blog post laid out the two dimensions of Office 365 security, compliance, and privacy: built-in capabilities and customer controls. This post focuses on a key feature under customer controls in compliance: data loss prevention (DLP).

DLP Policy Tips inform your workers in real time

With the new DLP Policy Tips in Office 365, admins can inform email senders that they may be about to pass along sensitive information that is detected by the company's policies-before they click Send. This helps your organization stay compliant and it educates your employees about custom scenarios based on your organization's requirements. It accomplishes this by emphasizing in-context policy evaluation. Policy Tips not only analyzes email messages for sensitive content but also determines whether information is sensitive in the context of communication. That means you can target specific scenarios that you associate with risk, external communication for example, and configure custom policy tips for those scenarios. Reading those custom policy tips in email messages keeps your workers aware of your organization's compliance policies and empowers them to act on them, without interrupting their work.

DLP Policy Tips is supported only in Outlook 2013, but even if your users don't have the latest version of Outlook, you are still protected from disclosing sensitive data through back-end processing. Admins can configure rules and take actions by setting up DLP rules in the Exchange Administration Center (EAC). This ensures that a single DLP policy controls both the client and server endpoints, minimizing the admin administrative overhead.

How do Policy Tips work? Consider a real-life scenario. Contossoplay is a company that has an internal policy to warn its employees any time they include sensitive information like a credit card number in email communications. Sara Davis is a Contossoplay employee composing an email to Dan, who works outside her organization. She includes credit card information in the mail, and immediately a DLP policy tip shows up in the message in Outlook.

When you include sensitive information in an email message, a DLP policy tip alerts you before you send the message.

At this point Sarah can decide to: send the email message with the credit card information, send the message with the credit card information and click Report to report a false positive, or delete the credit card information before sending the message. If she's unsure what to do, she can click Learn more to understand her company's policy, which her admin may have customized. 

Let's  look at another scenario. Contossoplay has recently set up a policy that blocks emails containing multiple credit cards or that need to be overridden with a business justification. Sara starts an email message to book the travel for multiple employees in the company and attaches a document that includes the personal credit card information of the employees. A different policy tip shows up, highlighting the new compliance requirement. In Outlook 2013, the attachment that is the cause of concern is also highlighted, making it easy for her to locate the information being questioned.

A custom DLP policy tip alerts you about an attachment that may contain high-count sensitive information.

As these two scenarios show, data loss prevention empowers end users, making them part of the organization's compliance process and ensuring that the business flow is not interrupted or delayed, because achieving compliance does not get in users' way. At the same time, data loss prevention simplifies compliance management for admins, because it enables them to maintain control easily through the Exchange Administration Center in the Office 365 admin portal.

Policy Tips are similar to MailTips, and you can configure them to present a brief note in Outlook 2013 that provides information about your business policies to the person creating a message. You can configure policy tips that will merely warn workers, block their messages, or even allow them to override your block with a justification. Policy tips can also be useful for fine-tuning your DLP policy effectiveness, because they allow end users to easily report false positives. If policy tips are not available to a user in Outlook, admins can still control compliance behavior by setting up rules in the Exchange Administration Center. For example, admins can set up an action to generate incident reports if a particular DLP event occurs. Such incident reports can help tracks events in real time, because a report is generated in real time and sent to a designated mailbox, such as the mailbox for incident manager account. The figure below shows a sample incident report.

You can generate incident reports for specific DLP events in Office 365.

What does data loss prevention in Office 365 offer?

Data loss prevention in in Office 365 helps you identify, monitor, and protect sensitive information in your organization through deep content analysis. DLP is increasingly important for enterprise message systems, because business-critical email often includes sensitive data that needs to be protected. Worrying about whether financial information, personally identifiable information (PII), or intellectual property data might be accidently sent to unauthorized users can keep a Chief Security Officer (CSO) up all night. Now you can protect sensitive data more easily than ever before, without affecting worker productivity. Admins can easily set up compliance management in email using the Exchange Administration Center (EAC) in the Office 365 admin portal. In the EAC, you can:

Start with a preconfigured policy template that can help you detect specific types of sensitive information such as PCI-DSS data, Gramm-Leach-Bliley act data, or even locale-specific personally identifiable information (PII).Use the full power of existing transport rule predicates and actions and add new transport rules.Test the effectiveness of your DLP policies before fully enforcing them by running the rule in the Test mode.Incorporate your own custom DLP policy templates and sensitive information types.Detect sensitive information in message attachments, body text, or subject lines and adjust the confidence level at which Exchange takes action.Add policy tips, which can help contextually educate your end users by displaying a policy tip in Outlook. This can also enable users to provide feedback via false-positive reporting.Review incident data in message-tracking logs or add reporting by using a new generate-incident report action.Look at the different DLP reports in the Office 365 admin center to drive compliance adoption in the organization.

How do I get started with data loss prevention?

Using the Microsoft-supplied DLP policy templates is an easy way to get started. DLP policies are packages of transport rules with new features that you can customize. These rules include classification types that define the type of content you are looking for in the DLP policy. You can use the Exchange management shell, the Exchange Administration Center (EAC), or even your own XML file editor to start incorporating DLP policies into your messaging environment. The screenshot below shows the data loss prevention management interface within EAC.

You can manage DLP from the Exchange Administration Center in the Office 365 admin portal.

DLP is accomplished through what is called "transport rules" in Exchange. The new transport rules include a significant new approach to detecting sensitive information that can be incorporated into mail flow processing. This new DLP feature performs deep content analysis through keyword matches, dictionary matches, regular expression evaluation, internal functions such as validate checksum on credit card numbers, and other content examination to detect specific content types within the message body or attachments. Here is a screenshot for the policy tip rule that triggered the policy tip above in the second screenshot.

You can configure policy tip rules to trigger specific alerts about sensitive content in email.

How do I establish policies that protect  sensitive data?

You can start using DLP in one of these three ways:

Apply an out-of-the-box template supplied by Microsoft. The quickest way to start using DLP policies is to create and implement a new policy using a template. This saves you the effort of building a new set of rules from scratch.Import a prebuilt policy file from outside your organization. You can import policy templates that have already been created outside of your messaging environment by independent software vendors. In this way you can extend the DLP solution to suit your business requirements.Create a custom policy without any preexisting conditions. Your enterprise may have its own requirements for monitoring certain types of data known to exist within a messaging system. You can create a custom DLP policy to check and act on your own unique message data.

Sensitive information types in DLP policies

When you create DLP policies, you can include rules that include checks for sensitive information. The conditions that you establish within a policy, such as how many times something has to be found before an action is taken or exactly what that action is, can be customized within your new custom policies in order to meet your business requirements. Sensitive information rules are integrated with the transport rules framework by introducing a condition that you can customize: If the message contains...Sensitive Information. This condition can be configured with one or more sensitive information types that are contained within messages.

To make it easy for you to use the sensitive information-related rules, Microsoft supplies policy templates that already include some of the sensitive information types. Here is the inventory of the sensitive information types supplied out of the box.

Data loss prevention in Office 365 is one of the major customer compliance control features offered to customers. Other compliance features under customer controls are available, such as in-place eDiscovery and in-place legal hold. We'll discuss these customer controls more in-depth in future blog posts.

So get started today and make your organization more compliant, without impacting your users' or your productivity, using data loss prevention.

--Shobhit Sahay


View the original article here

Friday, July 12, 2013

The Garage Series for Office 365: Stop that smoking gun! The latest in eDiscovery and data loss prevention

AppId is over the quota
AppId is over the quota

Episode 3 out of a 6 part special filmed in New Orleans, our intrepid host Jeremy Chapman is joined by Microsoft SharePoint and Microsoft Exchange experts Mark Kashman and Bharat Suneja to share an overview the very latest in integrated Enterprise Search, eDiscovery and Data Loss Prevention to harden your data protection. See how these technologies work across both Office 365 Cloud implementations and your on-premises Office stack to help save users and organizations proactively and reactively from themselves while helping to reduce the complexity of discovery and high costs of legal review due to compliance audits.

Jeremy: So our last show got quite a reaction by way of offering an exclusive first look deep dive on the upcoming real-time co-authoring capabilities with Office Web Apps which we demonstrated in Word, Excel and PowerPoint. This was the first time that we had showed the pre-release code capabilities. You can continue to catch that show here or by visiting the Garage Series show channel.

For our latest New Orleans show special, I’m joined by SharePoint and Exchange experts Mark Kashman and Bharat Suneja to take a look at another important topic, the very latest in data protection with eDiscovery and Data Loss Prevention across Cloud and Hybrid environments.

Mark: That’s right, data lives everywhere and the foundation to any data hardening and compliance strategy is to be able to locate key sources of data wherever they may be and you’ll see that not only are we making it so you can quickly discover content through key word searches across the Office stack with integrated enterprise search (formally FAST), but we’ve also greatly enhanced your ability to preserve content versions with eDiscovery and the new eDiscovery Center in SharePoint which allows you to perform in-place holds on SharePoint content, email in Exchange, saved Lync conversations etc.. This means users cannot manipulate or change data from an earlier point in time, and while we can put a document version on hold, we can do this without impacting the ability for the user to continue to be productive.

SharePoint eDiscovery Center showing unified search, filters, statistics, on-hover previews, and tabs for the various sources and content type – from an example “Northwind Traders” case.

Jeremy: This is pretty game changing – I know that for a typical audit it could previously take months to discover the data sources and then you were at risk of the data source being obscured or changed.

Mark: Yes we can now get a real-time response but the other thing that is significant is when you go to export documents and assets we aim to help reduce the footprint. If you consider that the cost of legal review is sometimes $10,000 per GB, these advances mean you can now minimize the volume of what gets reviewed without having to first export everything, saving a ton of time and money in lawyer’s fees wherever there is a suspected issue.

Once you discover data in an audit and use an in-place hold, the original file is preserved in that state in the preservation hold library. Even a SharePoint Site Administrator cannot modify the file and edits made in the Preservation Hold Library will result in another instance of the file. That is why you see two links to what appears to be the same file in the demo on the show. Then once you narrow in on the required content, you export it in a standards based EDRM XML format once from across the entire Office stack – not multiple time from various silos. 

Jeremy: So we had a bit of fun showing how this all works with SharePoint online and the eDiscovery center on the show. It was great to see what you can do reactively from a data compliance/protection perspective, so then we looked at what you can also put in place more proactively from a data protection perspective with the new Data Loss Prevention capability in Exchange. 

As we were in New Orleans we did this New Orleans style and tested whether or not Exchange Online could stop a smoking gun email leaving the organization as our test study Mr. #dealwithit tried to send out his boss’s credit card details.

Before you get too trigger-happy in the comments section with other ways to communicate the credit card number, we all know he could have used a plethora of other means to succeed in his task – but this is an example of how Data Loss Prevention rules can be set up to work to prevent the worse from happening within the corporate domain. It not only helped train our user, but it also blocked the offensive message at the backend using the new transport rules enabled via Data Loss Prevention. 

Bharat: Yes that guy definitely needed to be saved from himself, and in this particular case, he was behaving a little drunk and malicious and not using his best judgment.  Most users on the other hand, don’t try and send stuff out maliciously. That’s why we have Outlook Policy tips to focus users on going the right thing. But we can also set up custom policies which we demonstrate on the show. 

This is pretty powerful as you saw it means that even where Outlook tips are overlooked by the user we can forcibly stop data leaving the organization by email via the Exchange back-end, by setting up custom rules, which are like transport rules but a lot more sophisticated and allows for deep content inspection. Exchange now in fact ships with thousands of templates to assist with this.

When you create DLP policies, you can include rules that include checks for sensitive information. The conditions that you establish within a policy, such as how many times something has to be found before an action is taken. Sensitive information rules are integrated with the transport rules framework by introduction of a condition that you can customize. Exchange also supplies policy templates that already include some of the sensitive information types. A list of what is supplied in-box is provided here.

Jeremy: So eDiscovery and Data Loss Prevention are two major advancements with the new Office, to help with data hardening and compliance. But there’s also a lot more to it such as Windows Azure Active Directory Rights Management Services for file-level security, and Exchange Active Sync for device management and security, both of which we’ll cover more on future shows. So what are next steps that our viewer/readers can take?

Mark: If you want to go deeper into eDiscovery, dive into this “What’s new in eDiscovery” article, and then I would suggest beginning to Plan for eDiscovery to understand how it can best serve the needs and compliance requirements of your organization. 

Bharat: TechNet's library for Data Loss Prevention is a great place to start – the important point though is that with templates and such we are making it a whole lot easier to implement policy and so this should be mostly a no-brainer for both seasoned and new Exchange administrators out there.

Jeremy: Great, thanks Mark and Bharat, I look forward to having you back on the show as we cover more topics on SharePoint and Exchange in future. Data Loss Prevention and eDiscovery along with Windows Azure Active Directory Rights Management Services (AD RMS) provide excellent proactive and reactive security for data. We'll dig a bit deeper into Windows Azure AD RMS in a future show. Our next show will take a look at the new Fasttrack tools and process for speeding up time to value for Office 365 inside of your organization. If you think that it is slower or more complex to get the new Office tenant deployed inside of your organization – think again!

Bye for now, 

Jeremy Chapman, Mark Kashman and Bharat Suneja

Garage Series Video Channel

The Exchange Team Blog

SharePoint Blog

Garage Series Season 1 Blog Archive

 

By day, Jeremy Chapman works at Microsoft, responsible for optimizing the future of Office client and service delivery as the senior deployment lead. Jeremy’s background in application compatibility, building deployment automation tools and infrastructure reference architectures has been fundamental to the prioritization of new Office enterprise features such as the latest Click-to-Run install. By night, he is a car modding fanatic and serial linguist. Mark Kashman is a Senior Product Manager on the SharePoint team focusing primarily on SharePoint Online & SharePoint Mobility. He lives in the Redmond, WA area and enjoys kayaking, biking, hiking, ballet/soccer/science club/swimming (all the Dad duties), and quiet-bird-chirping moments for reading books on his #WP8 Kindle app when not playing that darned addictive Bejeweled LIVE+. Follow Mark on Twitter @Mkashman. Bharat joined Microsoft on a mysterious day between the end of March and beginning of April 2008. He's a Senior Technical Writer in the Exchange Customer Experience (CXP) team, responsible for content related to Compliance (Archiving, Retention, eDiscovery, In-Place Hold), Security, and Search. Bharat is a former Exchange MVP, current MCT, MCSE (+Messaging +Security), MCITP. He is the coauthor of Exchange Server 2007: The Complete Reference (Osborne McGraw-Hill), and publishes Exchangepedia blog.


View the original article here