{"id":4422,"date":"2021-01-06T09:37:32","date_gmt":"2021-01-06T07:37:32","guid":{"rendered":"https:\/\/www.msb365.blog\/?p=4422"},"modified":"2023-06-23T13:01:12","modified_gmt":"2023-06-23T11:01:12","slug":"microsoft-sensitivity-labeling","status":"publish","type":"post","link":"https:\/\/www.msb365.blog\/?p=4422","title":{"rendered":"Sensitivity Labeling with Microsoft"},"content":{"rendered":"

For almost a year now, we have had to deal with the COVID-19 pandemic. Many of us can work from home, but unfortunately not all.<\/p>\n

From a CISO\u2019s point of view, one of the challenges is to ensure that internal company documents remain internal and are not duplicated without permission.<\/p>\n

Microsoft offers \u201cSensitivity Labels\u201d for this purpose. These are individually configurable on various levels.<\/p>\n

On the one hand, you can define what they should be called, but also what should happen when a document is labeled and who is entitled to a label.<\/p>\n

In this article I will briefly explain how a label can be created \u2013 including various options.<\/p>\n

\u00a0<\/p>\n

Create a label<\/h3>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
In the first step, we log in with our admin account at https:\/\/protection.office.com\/<\/a> and then navigate to Classification and Sensitivity labels<\/strong>.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
Here we can create a new label with Create a label<\/strong><\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
In the first step of the wizard we define the name of the label.<\/p>\n

We also define a display name<\/strong> that will be visible to the end users, and a description for users and admins.<\/strong><\/td>\n

\"\"<\/a><\/td>\n<\/tr>\n
Under Scope<\/strong> we can decide whether files and mails should be encrypted with the corresponding label. In this example we select this option<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
The next step is about how the label should behave on files and mails. Here we can decide who has access to the encrypted messages and also whether we want to configure a watermark.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
If we select both options, as in this example, further sub-configurations are added to the wizard.<\/p>\n

The first is encryption.
\nHere we can decide whether the authorisation should be assigned immediately.
\nWe can also define how long a file or mail should be available. This can be an exciting option for HR labels, for example.<\/p>\n

As a last point, we can also define here whether files or mails should also be available offline, if so, a time period can also be defined.<\/td>\n

\"\"<\/a><\/td>\n<\/tr>\n
Next, we should define who is authorised to use this label. To do this, we continue with Assign permission<\/strong>.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
Personally, I always recommend using groups rather than individuals. This simplifies the management a lot.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
We can search for groups and select the appropriate one.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
The next step is content marking.<\/p>\n

Here we define which watermark<\/strong> we want to use for our label.<\/td>\n

\"\"<\/a><\/td>\n<\/tr>\n
In this example we use 2 variants, on the one hand the watermark which is visible diagonally across the document.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
Next we can also configure a header<\/strong> text<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
The third step is used for the auto labelling option. If this option is enabled, all files and mails that match the configuration will be labelled automatically after this label is published.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
Finally, a review of the configuration is shown and the label can be created.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
If everything is in order, you can continue with the next steps.<\/p>\n

The label is now created, but not yet published<\/strong>.<\/td>\n

\"\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\u00a0<\/p>\n

Creating the Label Policy<\/h3>\n\n\n\n\n\n\n\n\n\n\n
We now see the newly created label, which still has to be published.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
After the label is selected, a window with several options appears. Here we select Publish label.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
Here we select the appropriate label.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
Selection of which groups the label should be deployed to.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
Further configuration for managing the label.<\/p>\n

As an example, it must be confirmed if the label is to be removed or replaced.<\/td>\n

\"\"<\/a><\/td>\n<\/tr>\n
Name for the policy and a description.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
As with creating the label, a review is displayed before the policy is created.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n
The policy is now created and the label rolled out.<\/p>\n

The next time the end user opens an office application, the label is available depending on the authorisation.<\/td>\n

\"\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\u00a0<\/p>\n

Applying the Policy<\/h3>\n\n\n\n
In the following screenshot we see a Word document where our new label is visible under Sensitivity and can be used accordingly.<\/td>\n\"\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\u00a0<\/p>\n

Overview<\/h3>\n\n\n\n
To get an overview of which labels are used how often, we can go to Data classification<\/strong> on the portal at<\/p>\n

https:\/\/compliance.microsoft.com\/<\/a> and get an overview there.<\/td>\n

\"\"<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\u00a0<\/p>\n

I have only described the most important basic functions in this article, but there are some more interesting options for sensitivity labelling. I will describe these in a later article.<\/p>\n

However, after this article you should currently be able to create and use sensitivity labels.<\/p>\n","protected":false},"excerpt":{"rendered":"

For almost a year now, we have had to deal with the COVID-19 pandemic. Many of us can work from home, but unfortunately not all. From a CISO\u2019s point of view, one of the challenges is to ensure that internal company documents remain internal and are not duplicated without permission. Microsoft offers \u201cSensitivity Labels\u201d for […]<\/p>\n","protected":false},"author":1,"featured_media":4454,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[1923],"tags":[],"class_list":["post-4422","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-365"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/4422","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4422"}],"version-history":[{"count":9,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/4422\/revisions"}],"predecessor-version":[{"id":5170,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/4422\/revisions\/5170"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/media\/4454"}],"wp:attachment":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4422"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4422"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4422"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}