Montag, 12. August 2019

Don’t make me think about IT Security


This is what end-users say about IT-Security. If you are an Admin or Data Security Officer, you have to think about IT Security.
Microsoft provides super useful info and material about this topic. In real world scenarios we often had to find out where to start. And also, for this Microsoft offers a walkthrough:


I put all the stuff together in a small Excel workbook and extend it with some further licensing info.
All important information for your IT security strategy is summarized in this Excel. In column 1 you will find the respective scenario, column 2 gives you an overview and column 3 the details on the topic. Columns 4 and 5 contain further information and details on licensing.



DOWNLOAD Excel workbook!

Mittwoch, 7. August 2019

Updates & News around Microsoft Information Protection

In the last couple of weeks Microsoft release a bunch of new features / versions for Information Protection and Unified Labeling:
  • New features & functions with Microsoft Cloud App Security and Azure Information Protection
  • Azure Information Protection unified labeling client
  • Update to Unified labeling

Cloud App Security and Azure Information Protection

Cloud App Security and the integration with Azure Information Protection is not new. If you are already migrated to Office 365 unified sensitivity labels and if you did not migrate your existing classification labels you need to know:  Creating new labels in the Office 365 Security and Compliance Center, Cloud App Security will only use the preexisting labels configured in the Azure Information Protection portal.

Integrating Azure Information Protection into Cloud App Security you get the ability to:
  • apply classification labels as a governance action to files that match specific policies
  • view all classified files in a central location
  • investigate according to classification level, and quantify exposure of sensitive data over your cloud applications
  • create policies to make sure classified files are being handled properly
This integration is focusing to scenarios like:
  • Visibility on sensitive data in managed cloud apps
  • Compliance / Risk Enforcement
    • Apply label to documents in cloud apps repositories
    • Prevent storage of highly sensitive documents in the cloud
  • Sensitive data reporting in AIP analytics space
  • Detect anomalous access
  • Block download of sensitive document from specific locations or non-compliant device
  • Block upload of sensitive documents

You need both a Cloud App Security license and a license for Azure Information Protection. Then Cloud App Security syncs the labels from Azure Information Protection. This action is performed every hour.
Scanning the files:
  • Automatic scan: all new or modified files are added to the scan queue and will be scanned, classified and protected
  • File policy to search for classification labels: these files are added to the scan queue for classification labels

After you enable Azure Information Protection on Cloud App Security, all new files that are added to Office 365 will be scanned and you can create new policies within Cloud App Security that apply classification labels automatically.
More Details: How to integrate Azure Information Protection with Cloud App Security

Azure Information Protection unified labeling client

Highlights of version 2.2.19.0:
  • Support for labels that are configured for user-defined permissions for Word, Excel, PowerPoint, and File Explorer
  • Support for advanced settings with PowerShell for the Security & Compliance Center
  • New cmdlet New-AIPCustomPermissions to create an ad-hoc policy for custom permissions
  • New parameters added to Set-AIPFileClassification:-WhatIf and -DiscoveryInfoTypes so that this cmdlet can run in discovery mode without applying labels

Download and further information: Version 2.2.19.0

Actually, we have two management portals which are supported by different clients:
  1. Azure Information Protection:
    • Azure Information Protection client (classic)
    • Azure Information Protection scanner
    • Microsoft Cloud App Security

  1. Unified labeling in Office 365 Security & Compliance Center:
    • Azure Information Protection unified labeling client
    • Microsoft Cloud App Security
    • Office apps for MacOS, Android and iOS
    • Information Protection SDK and applications based on it like Adobe Acrobat
    • Coming Soon:
      • SharePoint Online
      • Office Online, Outlook Mobile for iOS and Android
      • Built-in labeling in Office for Windows
      • Azure Information Protection scanner

Update to Unified labeling

Unified labeling is not activated per default and Azure Information Protection labels can be used only by the Azure Information Protection client. To make labels available in the Office 365 Security & Compliance Center and to use the unified labeling client you need to Activate that integration:

Before you activate unified labeling, check in Office 365 that you don't have labels that have the same name or display name as your labels in Azure Information Protection. Note that Azure Information Protection labels will be automatically renamed so that migration can succeed. Once activated you cannot deactivate unified labeling for your tenant. Learn more about the migration process.

Unified labeling: Activated

Depending on how many labels do you have the updated takes some time. After it is done you can manage your labels from either the Azure portal or the Office 365 Security & Compliance Center. The labels can be used by the Azure Information Protection client and by unified labeling clients.

Note: you must use the Publish option after the migration to make the labels available in the unified labeling clients. Otherwise the client is showing an error like this:





Montag, 24. Juni 2019

Objectives, Doings and Limitations with Azure Information Protection and BYOK


Sources:
·         BYOK pricing and restrictions

Overview
Azure Rights Management enables BYOK according to a model that Microsoft calls customer-managed tenant keys. This requires a customer to create an RSA 2048-bit key in their HSM and then export the key to the HSM in Microsoft's data center. This RSA key is then used to encrypt the document encryption keys used by Azure RMS. RSA 2048-bit keys correspond to 112-bit AES keys. This means that the AES 256-bit encryption provided by Azure RMS is really only 112 bits. The US government has advised against the use of AES encryption keys below 256 bits.


Overview about the necessary steps:

  • Create an HSM-based Azure Key Vault for a specific Azure region.
  • Generate your own key according to your IT policies. This requires e.g. Thales HSM, smartcards and support software.
  • Transfer the key from an HSM in your possession to HSMs owned and managed by Microsoft as provided by Azure Key Vault for your vault. This process ensures that your key never leaves the hardware protection boundary.
  • When you transfer your key to Microsoft, it remains protected by Thales HSMs. Microsoft has worked with Thales to ensure that the key cannot be recovered from Microsoft HSMs, and certificates are provided to ensure this.
  • Configuring Azure Information Protection to use the HSM-based key
  • Azure Key Vault's real-time usage protocols are available as an option. These can also be applied to BYOK to see exactly how and when the key is used with Azure Key Vault. Blob storage is required to store the logs.


BYOK vs. HYOK

The two scenarios and implementation differ fundamentally. HYOK is a kind of Azure RMS hybrid scenario. More details: https://docs.microsoft.com/de-de/azure/information-protection/faqs-rms#whats-the-difference-between-byok-and-hyok-and-when-should-i-use-them


Prerequisites, Restrictions & Limitations

Support and SLA

  • Support for billing and subscription management is provided free of charge.
  • Technical support is available through various Azure support models from €24.456/month for Developer and €84.33/month in the Standard version.
  • SLA: Microsoft guarantees that in at least 99.9% of cases, Key Vault transaction requests will be processed within 5 seconds.

Call to Action

  • Evaluate the actual advantages and disadvantages of BYOK in the context of your requirements and specifications in detail with the data protection officer and the involved departments.
  • Calculate the costs for the implementation, the required services and hardware as well as the operating costs. Based on this, you create a cost-benefit analysis.
  • Do you have other services that are already using BYOK with Azure?Did you use your own key for other scenarios and therefore want to implement AIP BYOK as well?
  • Does HYOK meet your requirements better?

Montag, 27. Mai 2019

Security Features Matrix in Office 365 and Azure

UPDATED VERSION 1.1. availible

  • The matrix gives you an overview about security feature in Microsoft cloud stack including info about:
  • focus-area of the feature
  • a overview description plus hyperlink for further information
  • info about how to license the feature.
Screenshot:



Download the complete Matrix: LINK

  • added Azure Sentinel PREVIEW


Further interesting and helpful links:




Freitag, 15. März 2019

Focusing Cloud App Security Policies to dedicated Objects


In CAS we can focus policies to dedicated object. For example, you have a SharePoint Online Site with sensitive content, and you will get informed if a user is doing a mass download.
We can use the “Mass download by a single user” template to set up a policy:

In the filter section if the policy select “edit and preview results”:

In the shown activities list search for the location or event ion which you will filter. In my demo I take https://sharepointtalk.sharepoint.com/teams/SearchDemo2:

Selecting “Activity Objects” opens a report with all objects and its ID´s. To filter on the SharePoint SiteCollection URL we need the second one:

Now we can use this ID as a filter: