Follow me on Twitter @AntonioMaio2

Sunday, June 26, 2016

How to Disable Directory Synchronization in Office 365

I was working with a test Tenant in Office 365 recently where I had previously configured Directory Synchronization from an on premise Active Directory domain (which actually lived in an Azure VM).  I had recently turned off the Azure VM that hosted the AD domain, and I was now getting Directory Sync errors in Office 365 - which made sense since the domain had not synchronized in a few days.  At the same time, I was getting more and more familiar with the new Office 365 Admin Console which is quite nice actually, but I'm still trying to figure out where everything is found.

I decided to deactivate Directory Sync in my tenant to get rid of the errors.  I know I had seen it before because I've activated and deactivated it many times as I've tested the feature for clients.  But I couldn't find where you do that in the new Admin Console.  Let's take a look.

New Office 365 Admin Console

Here I've logged into my tenant and you can see my Directory Sync errors in the top left of the dashboard.  A sync hadn't happened in 68 hours, which made sense because I had turned the Azure VM off.


If I click on the GEAR icon in the left menu, which represents Settings, I get several options:


I select DirSync Errors in the menu... and I get nothing:


I select Services and Add-Ins and again I get several options:


Select Directory Synchronization in order to (hopefully) manage our directory synchronization options, and then we click another link to get to DirSync Management:


And we get to a nice screen which gives us several status indicators about our Directory Synchronization status (including that it has not synced in 68 hours), but no option to deactivate it:


I clicked the Troubleshooting link thinking that perhaps the option to deactivate the sync process could be found there:

 
 
 
I ran the scans, but again no luck.  I could not find the option to deactivate the sync process, despite how much I searched through the new Admin Console.  At this point, I returned to the old Admin Console to check if the option was still there.

Old Office 365 Admin Console

Once in the old Admin Console, in the left menu click on Users, then Active Users and then next to the Active Directory Synchronization title click Manage and there was my Deactivate option, along with similar status indicators to what I saw in the new Admin Console:

 

 

We click on Deactivate and we get a confirmation screen:


We click Deactivate Now and, finally, we've deactivated Directory Synchronization.  As usual, we're back at our Active User screen which tells us that Directory Synchronization could take up to 72 hours to take effect.  From my experience, it actually happens much quicker than this.


PowerShell

Alternatively, we could simply use PowerShell to get the current status of the synchronization process and disable it.  Here is the process you can follow:
  1. Launch the Windows Azure Active Directory Module for Windows PowerShell (right click the icon and select Run as Administrator).
  2. Type Connect-MsolService to connect to your tenant.  When prompted, login with your administrator credentials.
  3. Type (Get-MsolCompanyInformation).DirectorySynchronizationEnabled to get the current state of the directory synchronization process.  Don't forget the brackets.  If the sync process is enabled it will return True.
  4. To disable the sync process type Set-MsolDirSyncEnabled -EnableDirSync $false.
  5. When prompted to confirm select Y.

You may then type the same command as step 3 to confirm that it was been disabled.  You should get False returned at this point.

(Get-MsolCompanyInformation).DirectorySynchronizationEnabled

Enjoy.
   -Antonio




Wednesday, June 15, 2016

UPDATES: Office 365 Groups - Name Conflicts with Site Collections and Planner

I ran into an interesting situation today when working with Office 365 Groups related to how they are named that I wanted to share.  I had heard that there could be a name conflict that occurs between an Office 365 Group and a SharePoint Online site collection, so I wanted to test this out and understand the user's experience.  Big thank you to Brittany Kwait who contributed to testing these scenarios!

UPDATE 1: In working with the new Microsoft Planner, which was recently released as a new Office 365 experience, you'll also find that it creates an Office 365 Group as part of a new plan.  See below for some additional context into how Office 365 Groups are created and named as part of a Plan. 

UPDATE 2:  Microsoft recently announced here that new administration capabilities are coming to Office 365 Groups, including the ability to configure a Naming Policy in Azure Active Directory for Office 365 Groups.  According to Microsoft, this policy will allow administrators to configure a policy for appending text to the beginning or end of a group’s name and email address no matter where the group is created.  As well, administrators will be able to configure a list of specific blocked words that can’t be used in group names and rely on the native list of thousands of blocked words to keep their directories clean.  This feature is still roadmap and there isn't a committed timeframe yet for release, but I'm hopeful that it will help to address some off the naming experience inconsistencies.

Test 1: Create a New Group

Within the Office 365 portal I accessed by mail using the Outlook Web App and I created a new Group named "testgroup".  I did not click on Files right away in the Office 365 Group interface. 


I left my shiny new Group and navigated to the SharePoint Online admin console.  Here I created a new site collection and named it "testgroup" and gave it the URL https://maiolabs.sharepoint.com/sites/testgroup.  Everything worked fine!  My site collection was created without issue or error, using the name I gave it, which is the same as the Office 365 Group name I had chosen.  Where was the conflict?

I navigated back to my Group, and this time I clicked on Files.  At this point, I immediately got the screen which tells me "We're setting up...".

After a few minutes I got access to the space that was being created within the Group to store my files.  Of course, when an Office 365 Group is created, a OneDrive for Business site collection is created in which group members will store their files.  Now I began to understand what was going on.  The site collection associated with the Group does not get created until you click on the Files tab in the Group interface.  Its important to also note that the OneDrive for Business site collection that gets created in this case is a hidden site collection.

Once my Group space for storing files was created, I got the OneDrive for Business interface as I expected and checked the URL of the site.  It was:

https://maiolabs.sharepoint.com/sites/testgroup53/Shared%20Documents/Forms/AllItems.aspx

Notice the URL doesn't say "testgroup"?  It says "testgroup53".  I found that interesting but nothing conclusive yet.

Test 2: Create another New Group

This time I went back to my Outlook Web App and created another group named "testgroup2".  The Group was created fine as expected and I immediately clicked the Files tab to create the hidden site collection that would be associated with my Group. That also completed fine, and I checked my URL for that site collection and it was:

https://maiolabs.sharepoint.com/sites/testgroup2/Shared%20Documents/Forms/AllItems.aspx

Notice this time, the URL contains the actual Group name without any additional numbers tacked onto the end.  Interesting... Now I returned to the SharePoint Online admin console and created another site collection, this time named "testgroup2" and I ensured my URL was  https://maiolabs.sharepoint.com/sites/testgroup2.  Now I got the error I expected...


The site collection already exists.  Please enter a different address.

Conclusion

As I continued through the process, it was fine for the site collection name to be the same as that of an Office 365 Group.  However, the site collection cannot have the same URL as the OneDrive for Business site collection that is associated with a Group.  This makes sense - whenever an Office 365 Group is created and its OneDrive for Business site collection initialized, a OneDrive for Business site collection is created within SharePoint Online and of course you cannot have the same URL pointing to 2 different site collections.

Its interesting to note that if a site collection already exists with a particular URL and I then click Files in a Group to initiate my Group's OneDrive for Business site collection, Office 365 Groups will alter the URL so that it is unique and doesn't conflict with any site collections. However, this doesn't happen the other way around - if I create a site collection with the same name and URL of an existing Office 365 Group, I get an error and no automatic modifications to the site collection's URLs are made.  This also makes sense - we often want our SharePoint site collection to have a specific URL.

Improvements

What could be improved is the fact that the OneDrive for Business site collection associated with a Group is hidden.  To a SharePoint Online admin who is simply trying to create a new site collection, they may get this error and look at the list of site collections to see which other site collection has the same URL and not see any in their list which conflicts.  Yes the SharePoint admin can simply alter the URL, but they may want the URL to be something specific.  This may also cause them to spend significant time investigating the issue and open a support ticket with Microsoft.  This situation could be made even worse by the fact that, once Groups are enabled in your organization and by default everyone in the organization can create one or multiple Groups, you'll end up with many hidden site collections with no control over how they are named.  So the possibility of a conflict between an existing Group URL and a new site collection could be high.  This is especially true if you get a significant adoption of Office 365 Groups and also use SharePoint Online site collections.

I am encouraged by the fact that, as announced on May 4, later this year Microsoft will be launching the ability to associate a real SharePoint team site with an Office 365 Group.  With that, I'm hopeful that SharePoint Online admins will get real visibility into which sites are associated with which Office 365 Groups, and avoid this naming/URL conflict.

UPDATE: Office 365 Planner - A Connection to Groups

[Thanks again to Brittany Kwait for this update!]

Microsoft recently released a new service within Office 365 called Planner.  Planner allows teams to quickly organize, plan and track work projects and tasks using a highly visual experience: a task board that you might be familiar with from Agile/Scrum methodologies or solutions like Trello.  In using Planner, when you create a new "Plan"  Planner will automatically create a new Office 365 Group that will be associated with the Plan.  The Group will be named the same as the Plan.



If you then try to create an Office Group with the same name, in this case you'll get an error:


Here we get another interesting inconsistency - if you remember, when we tried to create a Group that was the same name as a site collection, the URL was simply automatically adjusted to be unique as part of the Group creation process.  No error appeared.  When we try to create a Group now that's the same name as a Plan, we get an error.  The same will probably happen if we try to create a Group that's the same name as another Group.  These aren't major issues - I just find it nice to know about and expect the inconsistency.

Once again, my point here is that I hope in the future, the new features we are told are coming for Office 365 Groups (Naming Policy, Team Sites associated with Groups) will help us control naming, and have Groups, Plans and site collections all work well together for administrators and end users. 

Enjoy your Groups! ...and Plans!
   -Antonio

Tuesday, June 14, 2016

Vulnerability: SharePoint 2010
MS16-054 CRITICAL - Addressed in May 2016 CU

In May 2016, Microsoft released a CRITICAL security bulletin related to vulnerabilities in Microsoft SharePoint Server 2010.  The vulnerabilities are identified as Remote Code Execution issues.  Full details can be found here: https://technet.microsoft.com/en-us/library/security/ms16-054.

Versions of Microsoft Office are also affected: 2007, 2010, 2013, 2013RT, 2016 and Mac Versions 2011 & 2016.  Microsoft SharePoint Foundation 2010 is not affected by this issue. 

The following services within the identified SharePoint version(s) are specifically affected:

1. Microsoft SharePoint Server 2010
    • Word Automation Services on Microsoft SharePoint Server 2010 Service Pack 2

    2. Microsoft Office Web Apps Server 2010 Service Pack 2
    • Microsoft Office Web Apps 2010 Service Pack 2

    Background

      According to the official Microsoft Bulletin the following is a summary of the vulnerability:

      This security update resolves vulnerabilities in Microsoft Office. The vulnerabilities could allow remote code execution if a user opens a specially crafted Microsoft Office file. An attacker who successfully exploited the vulnerabilities could run arbitrary code in the context of the current user. Customers whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.  The security update addresses the vulnerabilities by correcting how Office handles objects in memory, and by correcting how the Windows font library handles embedded fonts.

      Security Resources


      • CU UPDATE: a SharePoint Server 2010 Cumulative Update addressing these vulnerabilities and other issues is available for SharePoint Server 2010 through the May 2016 Cumulative Update. 

      • WORKAROUND: There are no workarounds identified specifically related to Microsoft SharePoint Server 2010.  There are several workarounds related to one of the vulnerabilities identified in the security bulletin which involve preventing users from opening untrusted RTF files by implementing registry customizations.

      • REPORTED EXPLOITS: According to Microsoft, at this time there are no reported exploits that have occurred using these vulnerabilities.

      Vulnerability Details

      Multiple remote code execution vulnerabilities exist in Microsoft Office software when the Office software fails to properly handle objects in memory. There are several vulnerabilities listed in this bulletin, most of which apply only to Microsoft Office.  However, 2 are specifically related to Microsoft SharePoint 2010 and details regarding these are available at the National Vulnerability Database:

      Additional notes from Microsoft:

      An attacker who successfully exploited the vulnerabilities could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

      Exploitation of the vulnerabilities requires that a user open a specially crafted file with an affected version of Microsoft Office software. In an email attack scenario an attacker could exploit the vulnerabilities by sending the specially crafted file to the user and convincing the user to open the file. In a web-based attack scenario an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) that contains a specially crafted file that is designed to exploit the vulnerabilities. An attacker would have no way to force users to visit the website. Instead, an attacker would have to convince users to click a link, typically by way of an enticement in an email or Instant Messenger message, and then convince them to open the specially crafted file. The security update addresses the vulnerabilities by correcting how Office handles objects in memory.

      Monday, June 13, 2016

      Vulnerability: SharePoint 2007, 2010 and 2013
      MS16-042 CRITICAL - Addressed in Apr 2016 CU

      I'm a little behind in blogging about recently released Microsoft Security Bulletins for SharePoint, but I'll attempt to catch up a bit here...

      In April 2016, Microsoft released a CRITICAL security bulletin related to vulnerabilities in Microsoft SharePoint Server 2007, 2010 and 2013.  In all identified versions, the vulnerabilities found are identified as Remote Code Execution issues.  Full details can be found here: https://technet.microsoft.com/library/security/MS16-042.

      Versions of Microsoft Office are also affected: 2007, 2010, 2013, 2013RT, 2016 and Mac Versions 2011 & 2016.  Microsoft SharePoint Foundation 2010 and Foundation 2013 are not affected by this issue. 


      The following services within the identified SharePoint version(s) are specifically affected:

      1. Microsoft SharePoint Server 2007 (MOSS)
      • Excel Services on Microsoft SharePoint Server 2007 Service Pack 3 (32-bit editions)
      • Excel Services on Microsoft SharePoint Server 2007 Service Pack 3 (64-bit editions)

      2. Microsoft SharePoint Server 2010
        • Excel Services on Microsoft SharePoint Server 2010 Service Pack 2                 
        • Word Automation Services on Microsoft SharePoint Server 2010 Service Pack 2
        UPDATE: For SharePoint Server 2010 specifically, this update was superseded by the May 2016 cumulative update which fixes an additional security vulnerability. My post on that update can be found here: http://www.trustsharepoint.com/2016/06/vulnerability-sharepoint-2010-ms16-054.html.

        3. Microsoft SharePoint Server 2013
        • Word Automation Services on Microsoft SharePoint Server 2013 Service Pack 1

        4. Microsoft Office Web Apps Server 2010 Service Pack 2
        • Microsoft Office Web Apps 2010 Service Pack 2

        5. Microsoft Office Web Apps Server 2010 Service Pack 2
        • Microsoft Office Web Apps Server 2013 Service Pack 1

        Background

          According to the official Microsoft Bulletin the following is a summary of the vulnerability:

          This security update resolves vulnerabilities in Microsoft Office. The most severe of the vulnerabilities could allow remote code execution if a user opens a specially crafted Microsoft Office file. An attacker who successfully exploited the vulnerabilities could run arbitrary code in the context of the current user. Customers whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.  The security update addresses the vulnerabilities by correcting how Office handles objects in memory.

          Security Resources



          • WORKAROUND: There are no workarounds identified specifically related to Microsoft SharePoint Server at this time.  There are several workarounds related to one of the vulnerabilities identified in the security bulletin which involve preventing users from opening untrusted RTF files by implementing registry customizations.

          • REPORTED EXPLOITS: According to Microsoft, at this time there are no reported exploits that have occurred using these vulnerabilities.

          Vulnerability Details

          Multiple remote code execution vulnerabilities exist in Microsoft Office software when the Office software fails to properly handle objects in memory. There are several vulnerabilities listed in this bulletin, most of which apply only to Microsoft Office.  However, 2 are specifically related to the identified versions of Microsoft SharePoint and details regarding these are available at the National Vulnerability Database:

          Additional notes from Microsoft:

          An attacker who successfully exploited the vulnerabilities could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

          Exploitation of the vulnerabilities requires that a user open a specially crafted file with an affected version of Microsoft Office software. Note that where the severity is indicated as Critical in the Affected Software and Vulnerability Severity Ratings table, the Preview Pane is an attack vector for CVE-2016-0127. In an email attack scenario an attacker could exploit the vulnerabilities by sending the specially crafted file to the user and convincing the user to open the file. In a web-based attack scenario an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) that contains a specially crafted file that is designed to exploit the vulnerabilities. An attacker would have no way to force users to visit the website. Instead, an attacker would have to convince users to click a link, typically by way of an enticement in an email or Instant Messenger message, and then convince them to open the specially crafted file. The security update addresses the vulnerabilities by correcting how Office handles objects in memory.

          Wednesday, June 8, 2016

          SOLD OUT: Microsoft BUILD Tour Canada June 10 - Register to Watch It LIVE

          In just a couple of days, Microsoft BUILD Tour Canada will be returning for 2016. 

          Unfortunately the onsite in person event is now SOLD OUT!  You can still watch it LIVE and experience all the great Microsoft speakers on some new Microsoft technologies that have just been announced. 

          Make sure you register for the live stream here: LIVE STREAM Microsoft BUILD Tour Canada. 


          This is an awesome, free event that I highly recommend!  Its become really popular year after year!  You'll get:
          • Deep Dives on the top announcements from Microsoft's annual BUILD conference
          • It’s all about new technology: Sessions, Demos and Coding exercises
          • Helps customers prepare their skillsets, app and software businesses for the future using the latest Microsoft technologies
          • Delivered by Engineers from Microsoft HQ
          • Unlike the general Build Conference, this event is completely free event!

          You'll find a number of great sessions including:
          • What's new in Windows 10 and the Universal Windows Platform
          • How to Use a single codebase and adaptive UX to target PC, mobile, Xbox and HoloLens, while connecting to the broader internet of things
          • How to Use Xamarin and Microsoft's cloud services to build rich cross platform experiences with the skills you already have
          • How to Extend your existing Win32/.NET and websites to leverage the latest Universal Windows Platform capabilities




          Thursday, May 19, 2016

          Overcoming Threats and Vulnerabilities in Your SharePoint Environments

          Thank you to everyone that came out to the Atlanta SharePoint User Group meeting on May 16th!  We had a great turnout and it was really nice to talk with everyone.

          You can find my presentation here:



          During the presentation I did a demonstration of the DLP capabilities within Office 365 SharePoint Online, and I discussed the DLP capabilities within SharePoint 2016 server.

          We saw SharePoint Online DLP policies applied to documents containing sensitive data (credit card numbers in this case) to provide policy tips for some documents, and to block access to other documents.  We provided policy tips to documents containing between 1 and 4 credit card numbers, and we blocked access to documents containing more than 5 credit card numbers.  This worked very well - as discussed it took between 15 and 30 minutes for SharePoint Online policies to be applied to new documents that were uploaded to a small library in my tests. For SharePoint Server 2016, this same test took approximately 14 hours to discover the sensitive content and apply the same DLP policies.  If you're wondering, I did have a default continuous crawl configuration in place for the RTM version of SharePoint 2016 server during these tests.

          A related question that came up was whether SharePoint Online DLP policies apply to list items which contain sensitive data as well.  Well, after running a couple of tests in the last few days unfortunately the DLP policies are not applied to list items containing credit card numbers.  I will continue to run tests and report back here any findings I hvae.

          Although I didn't demo the new DLP policies within SharePoint Server 2016, you can find my presentation on DLP within SharePoint 2016 Server on my blog here:



          ...and you can find my webcast with a demonstration of DLP within SharePoint 2016 server here:



          Enjoy.
             -Antonio

          Thursday, May 12, 2016

          Don't Count Content Out of Your Security Audit:
          ECM Must Be In!

          ECM or Enterprise Content Management are the systems in our enterprise which store and manage corporate content. We often think of these systems as applications like SharePoint, Documentum or FileNet, but they can also represent network file shares, NAS drives and custom internal web sites or applications. ECM systems can now exist on premise within data centers that we manage; through a cloud provider like Microsoft Office 365 or Amazon Web Services (AWS); or through a hybrid combination of both. They have grown within most organizations to store sensitive data and to represent critical infrastructure that employees rely on to accomplish day to day work.

          We rely on cyber security audits to evaluate the safety of our corporate environments. Cyber security audits give us an indication of our security posture and identify areas of improvement for cyber defense. As part of an audit, we typically look at things like network security, firewall configuration, communication protocols, intrusion detection -- systems which protect us from external threats, email phishing, malware and URLs leading to malicious websites. A security audit certainly must include these functions; however, ECM systems are often overlooked due to the specific domain knowledge required to properly evaluate all of the systems which make up the corporate ECM. Considering the criticality and often large quantity of data stored in our ECM, it’s important to consider why that is and how we can leverage what we know to facilitate inclusion of ECM systems in a cyber security audit.

          An ECM is typically made up of multiple enterprise applications working together to efficiently store and provide access to content.  They surface a robust set of capabilities to bring additional business value to the organization. These systems are often overlooked in audits due to the specific domain knowledge required to properly evaluate all of the systems which make up the corporate ECM.

          Microsoft SharePoint is a great example – it is a web application with a large set of built in document management features, sitting on top of SQL Server for content storage, surfaced through IIS for web access, with responsive pages for mobile access, deployed to a farm of servers with firewalls, proxies or a combination of both. It can be connected to other systems for authentication, retrieving business data and integration with reporting or business intelligence tools. It integrates with Active Directory for identity management, people search and user profiles which surfaces presence data and user attributes. Custom solutions can also be deployed to SharePoint to fulfill a specific business needs through the robust APIs it makes available. It provides a forms and workflow engine, allowing organizations to gain efficiency through business process automation. It can be configured with an enterprise class search farm to efficiently index content and provide lightning fast search. Search can include content within SharePoint and outside of SharePoint, like file shares. These features may be used to provide an intranet for collaboration, an extranet to interact with partners, a public facing web site or any combination of these. Finally, enterprises typically don’t have just one such SharePoint environment – you often see development, staging and production environments, along with a separate environment for disaster recovery.

          This is really just a small sample of capabilities provided by SharePoint, but represents what general ECM systems look like and what we hope to get out of them. With this in mind and considering all of the systems involved in providing such a robust set of services, a security audit can seem daunting.

          An ECM security audit does require some domain specific knowledge of many of these systems, however we find that the security review process often comes down too many of the same questions or areas of investigation that are used in reviewing other systems, such as:
          • Can we identify all repositories that store enterprise content?
          •  Do we know what types of data are sensitive and do we know where it resides? Do we need to scan repositories for data that is sensitive data from a compliance or risk perspective? Essentially, this is data that puts the organization at risk should a data breach occur, either inadvertently or maliciously. This can be data such as PII, PCI, PHI, MNPI (material non-public information), CPNI (customer proprietary network information), etc.
          • Are data owners for all repositories defined, in particular those storing sensitive data? Are data owner responsibilities clearly defined and are data owners aware of those responsibilities? Do those responsibilities include approving and denying requests for access?
          • Does the organization have record retention policies and schedules? Does the organization have a classification policy? Are information handling and acceptable use policies clearly defined for each type of sensitive data, and are end users educated about these policies on a regular basis? Is it clear to end users when they are working with sensitive data and how to handle it? Are these policies enforced or automated?
          •  Is the process for requesting access to data clearly defined and are end users aware of the process they must use? Are all access requests logged? Are access reviews performed on a regular basis, in particular for privileged or administrative users?
          •  Does the organization have an information governance plan and a governance committee? Does the governance plan cover specific practices related to the ECM system?
          • Do you have the right team in place to manage the ECM? Does the team have enough people and do they have the right skill sets or certifications? Your ECM administrative team needs the appropriate skills to manage it from strategic and tactical perspectives, from a security perspective and from the point of view of the business users.
          •  Is an activity monitoring and reporting system in place? Do those systems interact appropriately with the various components making up the ECM environment?
          • Are the servers making up the corporate ECM environment security hardened?
          These questions typically make up the core aspects of an ECM security audit. The only questions that require specific domain knowledge are the last question, and perhaps the second to last. All others can apply to all ECM environments regardless of the systems involved or integrated. These questions apply to many different corporate systems -- they provide us with insight into which data is sensitive to the business, where it resides, who is responsible, how access is controlled, how policies are enforced, and finally how the system is secured and monitored.

          Due to the criticality of the data stored within ECMs and the fact that typically a majority of employees in the enterprise access and rely on the ECM to accomplish daily work, including the corporate ECM in a cyber security audit is not only recommended but a requirement. As well, we can often leverage what we already know to ask the right questions to help us determine the security posture of our environment and where improvements may be necessary.

             -Antonio

          Tuesday, May 10, 2016

          Data Loss Prevention in SharePoint Server 2016

          Thank you to everyone that attended my webinar on April 28th on Data Loss Prevention in SharePoint 2016.  We had a great turn out.  As I said in the web cast, Microsoft is bringing great features from SharePoint Online like the Compliance Center to the on premise world with SharePoint Server 2016.  This is an excellent advancement for our on premise SharePoint deployments.  My webinar was a review or tour of the Data Loss Prevention features we now have for our on premise deployments with SharePoint 2016.

          Introduction

          Today we're constantly hearing about or experiencing threats to our business, and in particular to our business data.  To protect the business and its reputation, or to comply with business standards or industry regulations, organizations need to protect their sensitive corporate data and put in place measures to prevent its disclosure.  Sometimes that disclosure is inadvertent, or accidental. Sometimes its intentional or malicious.  In either case, a data loss prevention solution (or DLP) is one one of the necessary solutions to this problem.  SharePoint 2016 now includes a robust Data Loss Prevention capability that can help us protect that data.

          More specifically, when we talk about data loss prevention we're talking about automated systems which scan our data for keywords, regular expressions and patterns looking for specific types of data, and then either reporting or enforcing policies on that data.  This includes many different types of data, including:
          • Personally Identifiable Information (PII): passport numbers, social security numbers, tax identification numbers or even drivers licenses
          • Payment Credit Information (PCI or PCI DSS): credit card numbers
          • Financial Data: debit card numbers, bank account numbers, SWIFT codes or routing numbers
          • Health Insurance Data: medical record numbers, policy numbers, patient information
          If we look back, data loss prevention has been a long time feature of Office 365.  However, until recently it was only available in Exchange Online with policy tips and policy enforcement.  In mid-2015, Microsoft announced that the Office 365 Compliance Center would include DLP for SharePoint Online and OneDrive for business, and that solution was released to the various Office 365 tenants through the last part of 2015 and into early 2016.  Now, with the imminent release of SharePoint 2016 Server we also have this capability for our SharePoint on premise deployments.

          Prerequisites

          You need the following prerequisites in place before configuring the SharePoint 2016 DLP within the new Compliance Center:

          • Create a Search Service Application (mandatory)
            • Start the search service, Define a crawl schedule, Perform a full crawl
            • Must have a healthy search index and crawl for DLP policies to be effectively applied
          • Configure out-going email (recommended)
          • Turn on Usage Reports (recommended)
          • Create the eDiscovery or Compliance Center site collections (mandatory)
            • eDiscovery - for DLP queries to identify where sensitive data exists
            • Compliance Policy Center - for DLP policies to monitor and enforce policies
            • One or the other is mandatory - you can create both, but both are not mandatory
          • Assign the organization's Compliance Team with permissions to access the eDiscovery and/or Compliance Center site collection(s) through the Site Collection Members group

            Issue Follow-up: DLP Policy Enforcement Time & List Items

            Some of you will remember that there was an issue with the enforcement of the DLP policies in the library that I was demoing during the presentation.  I was showing a library with a document that contained 5 credit card numbers and the blocking policy was enforced on that document.  However, there were 5 other documents that had 1 credit card number each in which the 'policy tip' policy (or monitoring and warning policy) was not getting enforced on those - even after waiting 12 hours.

            Well, after waiting 14 hours the 'policy tip' policy final got applied to those 5 additional documents.  Considering those documents contained a credit card number, and my understanding is that the policy templates which check for credit cards are considered high priority internally, I would have expected those to be enforced sooner.  

            Please note: I was launching full crawls and the timer jobs which are supposed to enforce DLP policies manually over and over, to no avail.  

            What I have read, that it can take up to 24 hours for DLP policies to be enforced, is obviously true.  If I had a 1000s of users, with millions of documents, and users updating documents adding/removing sensitive information all the time, I could understand the 24 hour wait time.  But I added 5 documents into 1 library, in a farm of 20 documents total, with only 1 user using the farm - in this case I would have expected faster performance.  Enforcing DLP policies is often time sensitive and waiting 24 hours can mean in some situations that sensitive information is already exposed.

            As well, one of the tests I was running in my farm was if the DLP policies get enforced on list items.  Even after waiting over 24 hours, we can see that the DLP policies are not applied to the list items in this list containing sensitive information (credit card numbers) even after waiting 5+ days and ensuring that full crawls are successfully run and all associated timer jobs are also successfully run:


            Presentation and Recording

            The presentation slide deck can be found here:



            The recording to last Thursday's webinar can be found here:


            Final Thoughts

            Data loss prevention is just 1 critical part of securing our sensitive data.  This includes identifying sensitive data, monitoring its usage and enforcing polices which control its usual and disclosure.

            • The fact that SharePoint 2016's DLP uses the search index is both a blessing and can cause issues - traditional SharePoint DLP systems have had challenges accessing and scanning content from outside of SharePoint and using the search index allows the DLP capability to operate as quickly and efficiently as possible.
            • If something is not in the search index, it will not be found by your DLP policies.  So, the freshness of your search index and the health of your search crawls will affect how effectively your DLP policies are applied.


            The DLP capability within SharePoint 2016 is a great start!  However, I would like to see it evolve particularly in the following areas:

            • Apply DLP policies to list items, in addition to documents.  I have seen several incidents in the field where clients store sensitive information in list item metadata columns.
            • More policy templates
              • Exchange Online has 80 templates and SharePoint online has 51; SharePoint 2016 on premise has only 10.
              • Especially include health related policy templates, looking for HIPAA and medical related sensitive information.
            • Customizable sensitive data types - you can do this in many other DLP systems now.
            • Today policies are location based (which site collection it resides in) and condition based (what sensitive data types are included and the number of instances.  I would like to see event based policies included as well - like enforcing policies upon upload, upon adding an item, upon deleting an item, upon editing an item, etc.
            • More actions available for policies, like encrypt content with IRM upon download.
            • One compliance center for all site collections, including OneDrive for Business (MySites), across all web applications.  We can do this today with the eDiscovery Center in SharePoint 2016 and in SharePoint Online with OneDrive for Business in Office 365 - why can we not do this in the SharePoint 2016 Compliance Center.
            • More control over when policies are run - the ability to say "Evaluate all policies now" as opposed to running timer jobs and guessing which is the right timer job to run and getting no results when you run them all.
            • Document matching capability - allow us to specify a library of documents which are compared to documents in the system as part of a DLP policy, along with a required percentage of match for each document for a policy to fire.  This would help us prevent disclosure off executive communications, intellectual property, documents that follow a common format, etc.

            Finally, I encourage everyone to starting learning about and testing the SharePoint 2016 eDiscovery DLP queries and the Compliance Center's DLP policies.  You do need to test DLP policies in a TEST or STAGING farm (or TEST site collection if you don't have a separate farm) before deploying them to a PRODUCTION environment because they often need tweaking and you don't want to do that while Production users are trying to access data they need.  And one more time... ensure you have a healthy search index and crawl: if something isn't in the search index it will not be found by the DLP policies you put in place.

            Enjoy.
               -Antonio

            Wednesday, May 4, 2016

            The Future of SharePoint Security and Governance

            May the 4th Be With You

            Today is typically set aside to celebrate Star Wars movies and culture that many of us have enjoyed for years.  I'm hoping to take in one of the Star Wars movies with my family this evening, once the kids finish their homework of course.

            In other important news...
            Today Microsoft announced the general availability of SharePoint Server 2016!

            Microsoft also announced major new directions that we're going to see for SharePoint over the coming year!  People that read my ramblings know that I focus much of my work on security, so I'd like to share some of the security related capabilities that are included in Microsoft's roadmap for SharePoint. Microsoft has also reaffirmed their commitment to security, privacy and compliance with some significant new capabilities in their roadmap.

            Dynamic Conditional Access Policies

            One major new feature we're going to see is dynamic conditional access policies that administrators can define, allowing them to control the content that users can access based on the user's identity, the application or device they're using and their network location.

            Administrators will be able to effectively prevent users from accessing high-security files in SharePoint from a mobile device or home network which the organization doesn't control, but allow the user to access those files from a corporate laptop.

            Microsoft Windows Server 2012 has had this capability for years with its Dynamic Access Control (DAC) capability where you can define policies based on attributes in a user's identity (ex. security clearance) and metadata associated with a document (ex. its classification) and have those policies automatically enforced on Windows file servers.  It typically required use of the Windows File Classification Infrastructure (FCI).  As well, some third party security tools have layered these types of security policies on top of on premise SharePoint deployments in the past.

            From a security perspective, it will be fantastic to see this or a similar capability finally making its way to SharePoint.

            Site Classification

            In an update later this year, customers will be able to classify SharePoint sites so that security policies are scoped and enforced on all content in the site. When creating a new site, whether a team site or a publishing site, you'll be able to select the classification of the site. A site's classification is typically related to the sensitivity of the content you plan to store or present within the site, which will be displayed right below the site's name by default. This will really help users to understand when they are accessing sites with sensitive corporate data.

            This feature sounds simple, but its extremely significant because it allows customers to identify where sensitive data exists in their environment. Identifying where sensitive data lives is traditionally the first battle you fight, when trying to protect your sensitive corporate data. This is a great advancement in improving the governance of our SharePoint environments.

            Hybrid SharePoint Insights - Hybrid Activity Monitoring and Reporting

            Between the fall of 2015 and early 2016, Microsoft released the activity monitoring and reporting features within SharePoint Online and OneDrive for Business. This is a great capability for either monitoring user activity within your tenant, or performing forensic analysis into data breaches. I wrote an article about this capability here: Securing Office 365 with Activity Monitoring.

            By the end of 2016, Microsoft will release a preview of Hybrid SharePoint Insights which will aggregate data from both your on premise SharePoint 2016 environment and your SharePoint Online/OneDrive for Business tenant. This will allow you to monitor and report on user activity from both your on premise and Office 365 environments through one easy to use interface.

            Bring Your Own Encryption Keys

            We've have heard over the last year about how Microsoft encrypts all content stored within SharePoint Online and OneDrive for Business with a complex system that partitions data, uniquely encrypts each partition with a different key, randomly distributes and stores those encrypted partitions in Azure Storage Blobs, encrypts the keys themselves and stores those in a master key store and rotates all keys every 24 hours.  I've written about this myself here:  How Does Microsoft Protect Our Data in Office 365.  This is already happening in Office 365 and its completely transparent to customers.

            What's new is that later this year customers will be able to bring their own encryption keys to further lock down their data, preventing even Microsoft technical staff running the Office 365 service from accessing your data.  These continued efforts continue to help protect our data and our privacy.

            Data Loss Prevention Improvements

            I recently gave a webinar on the new SharePoint 2016 data loss prevention feature which can be found here: Data Loss Prevention in SharePoint 2016. Later this year you will be able to apply data loss prevention policies down to the site level. Today you can only apply those policies at the site collection level. This will allow us to get more specific about where and which content data loss prevention policies are applied to.

            External Sharing Improvements

            In Office 365, you can now whitelist and blacklist specific domains for external sharing. As well, later this year we'll be able to set an expiry period for external sharing, so content is only shared externally for a specific period of time.

            Other Exciting Additions - New Mobile Experience, Team Sites...

            There are many other welcome new additions planned over the coming year including a new SharePoint Mobile app experience, allowing users to easy access news from across the company, the sites that people use and access most, quick links to important pages and a list of their coworkers or those they collaborate most with.  This new app apparently uses Microsoft's investments in machine learning and the Office Graph to help surface the most relevant content and people for you, and present that ahead of less relevant information.  This sounds a lot like a mobile version of Delve doesn't it?!   The new mobile app will be available towards end of June 2016 for iOS, with Android and Windows versions coming later this year.  The OneDrive mobile app will also be getting enhancements through machine learning to provide users with suggestions of useful content through both OneDrive for Business and SharePoint.

            As well, team sites will get a new home page which gives users a quick look at team sites which they are part of, along with updates that have been recently made to those sites.  The idea here being that users can more quickly get to the work and sites that are more relevant to them at that moment.

            There's tons of other exciting updates... within Office 365, we hear that SharePoint team sites will be coming together with Office 365 groups as well - whenever a new Office 365 group is created, a new team site will be created as well. As a result, you'll be able to share team sites within Office 365 groups with external users through the Office 365 external sharing feature. This is a nice addition, but can create some security issues as well if you don't have appropriate governance in place.

            We will likely see these updates come out through Microsoft's new SharePoint 2016 Feature Packs planned over the next year.

            May the 4th be with you!
               -Antonio

            Sunday, April 17, 2016

            The Dawn of Transparency


            Last week we saw Uber publicly release its first Transparency Report (https://transparencyreport.uber.com/) and they've committed to release one every 6 months.  This has actually been happening for a few years.  Google began this trend for major tech companies in 2010, followed by Twitter in 2012 and now we have a number of other companies doing the same:



            A transparency report is a public statement issued by a company, on some sort of regular basis, that discloses aggregated data (not individual instance data) about requests for user information or content. These requests are made by governmental or regulatory bodies, as well as law enforcement agencies. Transparency reports are focused on a specific period of time and typically include how frequently these agencies request data and the types of responses provided. They also include under which authority the requests were made such as subpoena, search warrants, court order or emergencies.  Disclosing a transparency report helps the general public understand the scope and authority by which regulatory bodies are permitted to access personal information that we would typically consider private.

            In the last 6 months of 2015, Uber reports that it handled 415 requests for private data from various law enforcement agencies.  It provided at least a portion of the data requested in approximately 85% of cases.  Out of those requests 368 came from state run agencies, while 47 were from federal agencies.  As a result of these requests, 408 riders and 205 drivers were impacted.  As part of its report, Uber states that it makes it a policy to protect passenger privacy and requires valid and sufficient legal process from official government agencies before disclosing any information about its customers. It typically attempts to narrow the scope of data requests, which it is successful doing in some cases.

            I find the release of transparency reports significant!  It means we now have major tech companies, who request and use our personal information every day, releasing information to the public that clearly describe how they handle requests for that private data.  This helps to put pressure on those technology companies retrieving our data to securely store and protect that data, and it shows that they are making attempts to do just that.  This also allows us as consumers of online services to understand the scope of government requests and to watch the trends - to see if these requests are increasing.  Finally, it sheds a light on a practice that would otherwise be kept secret, and it encourages us to put pressure on our governments and law enforcement agencies to handle our personal data with the sensitivity and care it deserves.

            Consider a very simple scenario where a law enforcement agency requests data from an online service about an illegal activity related to a person named 'John Smith'.  What if your name is also 'John Smith' and you happen to use the same service?  Your personal data may get lumped in with the data provided.  You want law enforcement to be able to do its job of course.  However, you would also like to think that the data provided is under some sort of legal retention policy so after a specific amount of time, once the legal case is closed, your data is permanently deleted and you're no longer inadvertently associated with the case.  Unfortunately, many organizations take the stance of keeping data around forever, just in case.  You would like to think that the agency is taking appropriate steps to control access to that data, and storing it securely so it cannot be inappropriately exposed while in their hands.  However, agencies may not necessarily have (or follow) policies that define how personal data should be handled and secured.  You would also like to think a law enforcement agency will not disclose your data to other government agencies, but we have no guarantee of that. 

            Last week we also had Microsoft announce that they are suing the US Justice Department for its frequent use of gag orders preventing it from telling people when the government obtains a warrant to read their emails.  Microsoft states that the gag order statute in the Electronic Communications Privacy Act of 1986, as employed today by the courts, is unconstitutional.  According to Microsoft, the practice violates the Fourth Amendment right of its customers to know if the government searches or seizes their property, and it breaches the company’s First Amendment right to speak to its customers.  Although the case could be in the courts for months or years, Microsoft is trying to start a public debate about the frequent use of secrecy orders in government investigations.  Microsoft reminds us that they do not own the data within their service - that the customers own their data and Microsoft is simply the custodian of that data.  Their position here very much is in line with that statement.

            My personal information in many ways is my identity and I want to make sure my government does everything it can to protect it.  I for one, as a security-minded person, applaud Uber, Google, Yahoo, Facebook, Twitter, Apple, Microsoft and others for these efforts towards transparency!  The transparency report is an excellent practice which allows us to get an initial view into how personal data is accessed by our governments, regulatory bodies and law enforcement agencies.  We can begin to debate how much personal information governments should be allowed to access and what they must do with it.  Finally we can start to work with these organizations to ensure that they put in place appropriate security policies and privacy controls to better protect our personal information and identities.

            Monday, April 4, 2016

            Securing Office 365: Activity Monitoring

            Thanks to everyone that attended my session this weekend at SharePoint Saturday San Antonio.  Thank you also to the organizers of this great event!  I really enjoyed giving the session on Office 365 Activity Monitoring and was very happy that the audience was so engaged!  Great Questions!
            My slides can be found here on SlideShare: 



            If you'd like to download the presentation please click the link just below the embedded presentation.  Those who have seen my previous posts on this blog will see that I previously posted a presentation on this topic.  Microsoft has updated the Activity Monitoring feature in the Office 365 service in the last 2 months and this presentation is updated to take those updates into account.


            As mentioned, Activity Monitoring is just 1 important part of securing our enterprise content management environments, but its not a "set it and forget it" activity.  Making real use of activity monitoring to help improve the security of our systems requires the right policies and procedures in place, and it requires active management and regular review of the logs.  It also requires getting the logs into some form that is not too labor intensive to retrieve, format and review.  I typically recommend the following policies:
            • Review privileged user (administrator) access quarterly
            • Review user access annually
            Depending on the number of users in your environment, the annual access review may or may not be very practical so you may have to find some ways to make it practical, like:
            • Taking a sample of users
            • Developing some automated scripts or code which extract specific anomalies in the logs, like if you've identified where sensitive content exists and looking specifically for access to those areas
            There are lots of other ways to make this practical, but it will likely require some serious work to put these practices into place in your specific business environment.


            There were some really good questions about how you might use PowerShell to extract specific details out of the activity logs.  I'm working on a simple script to do just that now, which I'll try to post later this week.


            Enjoy.
               -Antonio



            Saturday, March 12, 2016

            Vulnerability: SharePoint 2010 and 2013 - Security Bulletin MS16-029 IMPORTANT - Mar 2016 CU

            This week Microsoft released an important security bulletin related to vulnerabilities in Microsoft SharePoint 2010 and 2013, as well as Microsoft Office versions 2007, 2010, 2013, 2013RT, 2016 and 2011 & 2016 for Mac.  Full details on the vulnerabilities can be found here: https://technet.microsoft.com/en-us/library/security/ms16-029.

            The following services within the listed versions of SharePoint are specifically affected:

            1. Microsoft SharePoint 2010
              • Word Automation Services on Microsoft SharePoint Server 2010 Service Pack 2


              2. Microsoft SharePoint 2013
                • Word Automation Services on Microsoft SharePoint Server 2013 Service Pack 1


                3. Microsoft Office Web Apps Server 2010 Service Pack 2
                • Microsoft Office Web Apps 2010 Service Pack 2

                  4. Microsoft Office Web Apps Server 2013 Service Pack 1
                  • Microsoft Web Apps Server 2013 Service Pack 1

                  Background Summary (from Microsoft's Bulletin)

                    Full details on the vulnerabilities can be found here: https://technet.microsoft.com/en-us/library/security/ms16-029. According to the official Microsoft Bulletin the following is a summary of the vulnerability:

                    The most severe of the vulnerabilities could allow remote code execution if a user opens a specially crafted Microsoft Office file. An attacker who successfully exploited the vulnerabilities could run arbitrary code in the context of the current user. Customers whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

                    A security feature bypass vulnerability exists in Microsoft Office software due to an invalidly signed binary. An attacker who successfully exploited the vulnerability could use a similarly configured binary to host malicious code. A defender would then not be able to rely on a valid binary signature to differentiate between a known good and a malicious binary. To successfully exploit this vulnerability, an attacker would have to have write access to the target location that contains the invalidly signed binary. The attacker could then overwrite the original file with their own malicious file and wait for an application, or user, to trigger the malicious binary.

                    The security updates provided by Microsoft address the vulnerabilities by:
                    • Providing a validly signed binary
                    • Correcting how Office handles objects in memory

                    Security Resources



                    • WORKAROUND: There is a workaround available for the Microsoft Office Memory Corruption Vulnerability.  Details of the workaround involve disabling the OLE Package function in Outlook and available at the Microsoft link provided.  The workaround would likely only assist with protecting Microsoft Office installations on desktops and not SharePoint installations from this vulnerability.

                    • REPORTED EXPLOITS: According to Microsoft, at this time there are no reported exploits that have occurred using these vulnerabilities.

                    Additional details regarding the SharePoint related vulnerabilities are available at the National Vulnerability Database at the following links: