Let’s defend ourselves!

Maybe not yourself, but your organization! Smile

Ignite have recently ended with a lot of news from Microsoft. One of biggest news around threat detection and protection is the latest integration of all security solutions for our M365 environment. Based on my own as well as my company’s experiences this is a success factor for identifying and prevent intrusions before they do harm.

Lets do an example to explain this a little bit more.

Think of your environment like this:


Most of us still have an on-premises environment including local Active Directory, servers and clients. We got a cloud environment with Office 365 and Azure Active Directory and we maybe got other cloud services as well.

Then we have our security solutions that protects our clients/servers, our cloud solutions, and our identities. All these solutions can identify different kind of threats and give us alerts that could be really critical, or just be the daily noise of non-critical alerts.

Lets do some examples

  • What if we have a user where we see authentication alerts like unfamiliar sign-ins, impossible travels etc.? Of course, this could be a false positive because he is using his own new VPN service.
  • What if the same user is trying to access local resources that he doesn’t use to, for instance in a unusual time in the middle of the night. This could be a false positive alerts because he have a new role and working late.
  • What if the same user running advanced PowerShell commands on his company device? He might be taking a PowerShell course.
  • What if he downloading a lot of files from a SharePoint/Team site? He may be planning to work offline.
  • What if he sending highly confidential files to a private email address? I don’t add any suggestion here, but you may be interested in the newly released Insider Risk Management as well ?

I do think that you got the idea. If any of these alerts have been raised there could be a non-critical alert. But if we are seeing a combination of alerts from different services there is a really high risk that we got something critical going on. When it comes to preventing an attack, it is extremely time critical and going through different kind of alerts often takes too much time.

Microsoft have now released the Microsoft 365 Defender that is not only getting alerts from all these different security solutions, it is doing much more…


The Microsoft 365 Security -portal generate automated incidents based on all these security solutions. Gives us one single portal that helps us prioritize and getting insights in the most ongoing critical alerts and risks for the moment. In several cases the generated incidents can mitigate the attack automatically or make it easier to take the correct action manually to prevent the attack. What is also time consuming is to identify what a bad guy have been doing during a period, all these integrations are helpful in these scenarios!

For the more experienced security administrators, there is also Advanced Hunting with virtually unlimited possibilities. My colleagues who work for Onevinn’s MDR service have been working on this for a long time and are building impressive threat-hunting queries towards all these services and also more services. This is often a critical proactive step during an ongoing attack

Microsoft have also chosen to rename a lot of these services to complete the Defender story:

  • Microsoft Defender for Office 365 – Office 365 Advanced Threat Protection (Office ATP)
    Protect our collaboration services from Exchange Online to Teams
  • Microsoft Defender for Identity – Azure Advanced Threat Protection (Azure ATP)
    Identifies threats in our local environments based on signals from our domain controllers
  • Microsoft Defender for EndPoint – Microsoft Defender Advanced Threat Protection (Defender ATP)
    Detect and response on threats on your endpoints, from computers, tablets, cellphones to servers
  • MCAS, Microsoft Cloud App Security still have the same name. MCAS protect our cloud apps, Office 365 and other 3-party cloud apps. MCAS also integrates with Azure Active Directory Identity Protection that protect our identities in Azure AD. All of these important signals from our cloud identity and our connected cloud apps are shared with Microsoft 365 Defender.

How to get started?

Just go to https://security.microsoft.com
If any of the above services are in use, you ready to onboard your tenant.
Find more information on Microsoft docs

Publicerat i Microsoft Defender, Threat Protection | Märkt | Lämna en kommentar

Revoke access to sensitive emails

Microsoft has started to roll out a lot of new features related to Information Protection. A  requested feature that was rolled out last week is the possibility to revoke protected emails that are sent externally.

As in the cases with new functionality, this feature has started to be rolled out in the cloud service, Outlook online!

Let me show how you how this works:

The senders experience

If I have protected an email to external recipients and I realize that this was a misstake or some other reason that the email needs to be revoked (prevented to be accessed).

I can go to my Sent-folder (In Outlook -online). There I will see an option (for protected emails that are sent to external users) to Remove external access for the specific email.

image image

When I click on “Remove external access” I get a prompt to confirm this action.


When the email is revoked, I can see in the specific email that this email is not accessible for external recipients anymore.


Recipient experience

The external recipient who got the email and try to read it will have the following experience.

When the recipient tries to access the protected email (hosted by the senders Exchange Online)

image image

He will get a message after signing in, that this email has been revoked by the sender.


Requirements and explanation of how it works

As you may understand by the above screen shoots, this works for emails protected by Office 365 Advanced Message Encryption. I have explained this concept earlier in this swedish article.
But let’s do a recap about what’s happening when you protect an email. In the same way as for almost 20 years ago when AD RMS was introduced, the protected email will end up in a protected format. A rights protected message with the file format .rpmsg. To be able to read (decrypt) this message there are two requirements:

1. The recipient needs to have an email application who understand the RPMSG-format to render this message

2. The recipient needs to be able to authenticate himself to Azure Active Directory

If these two requirements are fulfilled, this gives a really nice experience where the protected email is rendered in Outlook among the other emails, and the recipient does not need any additional step to access this protected email. But to be able to create a solution that make it possible to access a protected email without any requirements on the sender’s side, there is a plan B.

The protected email (the specific rpmsg-file) will be cached (by default in 90 days) in the senders Exchange Online environment. If either of the two requirements above is not met, the result for the recipient will end up with a customizable message. This email contains a link where the recipient can log on to the sender’s Exchange Online to read the email (and any attached document or pdf).

One great benefit with this is that the email remains in the sender’s tenant and the recipient can reply and have a secure email communication that is only stored in the recipient’s environment. And now, we also got another great benefit… These kinds of emails can now be revoked by the sender and an administrator(s)!

If there is a business need to require revocation possibilities, this behavior can be enforced for all external emails. As always when it comes to Information Protection the decisions need to come from the business itself!

When you have gathered all your business needs you can read more about license agreements and administrative routines for email revocations on Microsoft docs

Publicerat i Microsoft Information Protection | Märkt | Lämna en kommentar

Double Key Encryption (DKE) for Microsoft Information Protection

This week Microsoft Ignite starts. One of the biggest news around Microsoft Information Protection is the new encryption technology. This is meant to be the new Hold Your Own Key (HYOK) option that will replace the alternative to use AD RMS. The new technology is called Double Key Encryption (DKE), simply because it uses two keys to protect your data—one key in your control, and the other one is your Azure RMS key. Viewing data protected with Double Key Encryption requires access to both keys. Compared to AD RMS (that is built on the local Active Directory) DKE are using Azure AD. In the same way as Azure RMS information can be protected to both internal as well as external users.

The content that is being encrypted with DKE is protected with your own key (where ever the content is stored). You have a lot of options for your own key, that is running on a web service that can be stored where ever you want. Access to this key is definied by you, which give you a lot of possibilities to meet different business requirements.
The concept is still that Microsoft doesn’t have access to this key and therefor none of the online services from Microsoft will work. No support of Office Online apps/Microsoft Teams or actions like co-authoring or eDiscovery/content search is available.

This technology is built into the Modern Office, also called Office ProPlus that will have support to encrypt and decrypt with DKE. In the first release this will only work on Office for Windows, but the plan is to release this to all kind of platforms (iOS, Mac, Android etc.) The goal is to support email encryption as well (with the requirement to use the modern Outlook app) but for now, DKE only supports Office Documents, Excel files and PowerPoints.

In the same way as HYOK with AD RMS this is only meant to be use for certain highly confidential information. Information that have this specific business encryption/access requirements.


I will not keep trying to explain this technology more in text Have a lock at this video where I explain the concept and everything you need to know about the encryption and decryption with DKE.

Publicerat i Microsoft Information Protection | Märkt | Lämna en kommentar

Auto-labeling for Office Online services

Last week Microsoft released a new function to be able to act on data-at-rest information in Teams (SharePoint and OneDrive). In my previous article about how to prevent information leakage when inviting external guests into Teams, we had a scenario for “Project Delta”. The business case was to be able to share the project information in a secure way to all internal and external project members. There was also a requirement to restrict internal sensitive information to invited guests.

This article is about how to automatically identify and protect information. In many cases we already have existing sensitive information without correct classification and protection at rest. For local files we have had the AIP Scanner for a while that is able to both identify certain information as well as label this information with the correct information classification and protection (when needed). For data stored in the cloud (Office 365) we have had the possibility to identify the same information with the build in solutions in Compliance Center. What we now have is possibility to also apply classification and protection automatically, to identified files in the cloud.

Let’s go back to the previous business case for “Project Delta”.

When it comes to identify information all the different solutions use “Sensitive info types” from the Compliance portal. Here we have the built-in information types that includes everything from financial, privacy to medical and health information. imageWe also have possibilities to create our own information types.
In this example we have a project with a defined project number (that is used for example in document templates). We have created a sensitivity info type that looks for this number.

The result from this will show us (under Data classification in the Compliance portal) how many files we have in Office 365 that includes information related to Project Delta.

image image


The new auto-labeling feature gives us the possibility to take action on this information.
Auto-labeling is found under Information Protection in the Compliance portal


A new policy gives us the possibility to act on predefined information types or create a custom policy.


We then specify the location for the information we want to automatically apply labels to.


For each of these locations we can create specific rules with conditions. In our case we want to identify everything that include Project Delta information and apply protection to it.


Another scenario would be more advanced rules for instance to only label Project Delta information that is being shared externally.

We then choose what Label we want to apply for identified information. Where we choose the Label for Project Delta.

When we turn on this policy it will start in simulation mode. This help us ensure that we apply the label to correct information.

We can then go back and review which files have been identified and ensure that the policy is properly configured.


When we are ready, we can turn on the policy.


The result will be that identified Project Delta information in all these locations will be automatically classified and protected to only the members of the project.


Other solutions to identify Project Delta information based on this sensitivity info type

  • Auto-Labeling in Office that can auto apply a label or recommend the end-user to apply the correct labelimage

  • Scan local file shares and SharePoint servers with the AIP Scanner.
    The scanner uses the same sensitivity info types and gives a view of all local files including Project Delta information.

The AIP scanner have a couple of news as well. Let’s keep that for a coming article

Publicerat i Microsoft Information Protection | Märkt | Lämna en kommentar

Information Protection reduces the risk with guest invites into Teams

I have met a lot of customers who have hesitated to enable the possibility to invite external guests into Teams (and SharePoint/OneDrive). In all cases the concern is about information leakage. “What if our users invite others that are getting access to sensitive information”?


The solution in all these scenarios are classification and protection.

If the information is classified correctly with protection for sensitive information, we can mitigate the risks of information leakage.

Let’s take an example with this scenario.

The business requirements

This organization wants to be able to invite external guests.

They have a couple of projects that needs to include external users that also need to be able access sensitive project information.

They also have internal information that needs to be blocked for the external users. There are also internal SharePoint and Team sites that can’t allow external guests at all.

The Solution

Let’s start with the last business requirement where we need to define which sites that should allow external invites.
Based on Classification of the site itself we are able to define if external invites are allowed or not. In this scenario, Confidential sites allow external invites while Secret sites do not.
More about what’s behind the scene can be read in my previous post

image image

Let’s focus on an example for a sensitive project that should only be accessible for the project members (both internal and external users).

This is Project Delta

Project leader, Peter can invite members (because this is classified Confidential site) and in this case he invites an external account via Azure AD B2B.

The external users get an invite and are able to access this Team site.



When we look at all stored information on this Teams site the user can easily see how each of these files are classified.

Based on the classification we also have protection and access control of these files.


The external user is able open information classified and protected to Project Delta


If he downloads these documents the local copy will be protected and only accessible for Project Delta members


The external user will also have access to default classified Business documents but will be restricted from accessing classified Confidential or secret information that is protected for internal use only



The Setup

In the background we have the following setup


There is an Office 365 group that was created in the back end by default when the Project Delta Team was created.
This group also gives access to the same SharePoint site that is used for this Project Delta Team.


This group is then used to give access to information protected by the Project Delta label


With this setup we support the project leader to follow the business requirements.

Based on the site classification he can create a Teams site that allows invites of external guests. Hi can also make sure that information for the Delta project is limited only for the project members that also include his invited guest. By classifying information as Confidential Peter can choose if information should be available for Project Delta.



Peter can also classify information as Confidential and define if the information should be restricted to “Internal” users. This prevent all external guests to access any of this content.


In the next article we going to go through how we can support Project Delta, to automatically identify and protect their information as soon as it being stored in Microsoft/Office 365. This with the recently released “Auto Classification” that helps us act on data-at rest in the cloud. Stay tuned!

Publicerat i Microsoft Information Protection | Märkt | 1 kommentar

Classify SharePoint sites, Teams and Groups

The demands to have a mobile way to work grows all the time. In the time of writing this article the biggest motivation is the current spread of the Covid 19 virus. More companies start using Teams, SharePoint Online and Office 365 groups as tools to access information, coworking and sharing information in or outside the organization. Information Classification and Protection is as always a mayor player when it comes to the mobile work to prevent information leakage.

The possibility to classify information grows. One of the latest update to the MIP story is the possibility to classify Teams, SharePoint sites and Office 365 groups. All these services got different settings that control if the service:

– Is Private/Public (Allows external invites)

– Only allow the owner to add members

– Allow full, limited or block access for unmanaged devices

Based on the above control settings the business (information owner) can decide what settings that meets their information classification.
A classified Team or SharePoint site will show the end users what kind of classification / sensitivity the specific site have, as well as enforcing the defined access control setting.

Classify site and teams


Let’s have a look how to get started and how this will affect the end user in the following video:


The attentive reader may have seen in the above picture that the word document is classified with a different classification/label than the SharePoint site. A classified Teams, SharePoint site will not affect document that are stored or created from this site. The purpose of the classification is to show the sensitivity for the end user of the site itself, as well as preventing information leakage by restricting permissions to different actions.

To be able to restrict different action for an unmanaged/unsanctioned device a Conditional Access policy need to be defined for the affected users, to the cloud app Office 365, with app enforced restriction for the session

image image

If there is a need to enforce a specific classification for the documents as well this can be done today by using Microsoft Cloud App Security or Auto-Labeling, but that is another (coming) article

Publicerat i Microsoft Information Protection | Märkt | 1 kommentar

Trainable classifier

I usually blog only in Swedish but will from now on mix articles based on the content in Swedish or English. In this case it’s quite easy to choose since this article is about a new fantastic technic that can help your organization to find patterns in your information which can be basis for information classification. For now, this only works for information in English.

Why and when should we have use of trainable classifiers?

Today we can choose to either let the author of the information decide the correct information classification/label or we can automatically detect content like word, phrases or expression types that decide the correct information classification.

For example, if the document includes everything from predefined information types like credit card numbers, social security numbers to organization specific types, like project names or unique identifiers of drawings or recipes, it can be automatically classified. The classification can result in encryption or other data loss prevention technics.

But what if the organization can´t identify what´s unique for certain information? For example, if there have been projects that are working with sensitive information around a new invention but doesn’t have anything that is unique for all these documents?
The trainable classifier is meant just for these kinds of cases. Based on machine learning it can identify patterns by looking at existing documents. Basically, you point out a location that includes this information. Once it processes files in the location, you test the result by giving it a mix of both matching and non-matching documents and manually help the classifier to reduce the false positive predictions.

Let’s have a look in the compliance portal to find out more.

Trainable classified can be found under Data classification in Microsoft 365 compliance portal


Before you can start using this function in needs to scan your content and this can take up to 2 weeks to finish. I tried this in two different tenants and for our production tenant where we had a lot of data it took 8 days and in our test tenant with less data it took 12 days.

When the analytics is done you will find 6 predefined classifiers.


For instance, I can see high value of looking for “Threat” that detects a specific category of offensive language text containing threats to commit violence or do physical harm or damage to a person or property. One example of action here would be to identify and block email and chat with this kind of information.

Create a trainable classifier

Let’s create our own trainable classifier. The requirement is that the content needs to be stored in SharePoint Online. The file types that are supported are listed here. It needs to be 50 files at least, where the latest 500 files are the once that will be scanned (if the location includes more files).

I had no more imagination than sending up 50+ RMS logs which I changed the file format to .txt to be able to crawl these files. This is just for testing and demonstration but a business need here could be that sensitive log data needs to identified and retained for a specific time.


The syntax in those two fields is very strict and needs to be as follows:


As you can see in the following picture it can take up to 24 hours to analyze the content. You need to be patience testing this.


…after 3 hours I was able to start testing my classifier



I started out with creating two word documents, one with RMS log data and another one with only some characters from a log and other data that shouldn’t be identified as a RMS log. I uploaded these to another folder in SharePoint and added this location



The work wasn’t done after reviewing 2 files.. The portal now showed the following


As you can read under Classified accuracy above, It’s recommended (and also required) to test 200 items at least.

I uploaded 200+ files with a mix of correct logs and other type of log files and continued with the review.
When this was done it was possible to publish my classifier



I now have a new classifier ready to use that is showed together with the pre defined classifiers created by Microsoft.


Start using trainable classifier

Lets have a look in different types of action that can be taken based on the trainable classifier.

It can be used to auto-label a sensitivity label for Office apps:

image image

The end user experience will be that, as soon as RMS log data is added to an Office document it will recommend (or automatically) change label and protect the file.


The classifier can be used as condition for a Retention Label (that can retain or delete content).
For now I had to use the classic Security & Compliance portal to be able to choose a trainable classifier as a condition for a Retention Label.


I can then create a Data Loss Prevention policy based on this retention label for SharePoint, OneDrive, Teams etc. To be able on act on data at rest in Office 365.


You can find more information and examples here

Trainable Classifier is another good example of technics that can help de business to identify and act on sensitive information. As always, it´s important to include the organizations information owners and appointed CISO or equivalent role in this work.

Publicerat i Microsoft Information Protection | Märkt | Lämna en kommentar

M365 Compliance nyheter Data classification

Arbetet fortsätter att konsolidera och centralisera både övervakning och möjligheten att ta åtgärd av verksamhetens information.

Vi har tidigare skrivit om hur alla loggar av klassificerad och skyddad informationclip_image001 centraliserats till den klassiska Azure Information Portalen. Den här klassiska portalen är fortfarande den portal som ger mest insikt idag. Där emot är och kommer detta fortsätta vara ”Public Preview” och alltså aldrig bli det Generally available (GA). Anledningen till detta är att all fortsatt utveckling går mot Microsoft Compliance Portalen. Vi kommer få se en hel del nyheter under det kommande året i den här Compliance portalen.

På samma sätt som att vi idag konfigurerar Unified Labels och kan skräddarsy egna informationstyper från den här portalen kan vi även följa upp hur dessa används. I nuläget är det mest information från data som lagras och hanteras av Office 365. Vi kan följa upp vilka informationsklassifikationer/labels som används mest och se vilka informationstyper (både fördefinierade och egna) som förekommer både i nya och lagrade filer.


Sensitive info types

Det här ger oss bra möjlighet att stötta verksamheten och göra utredningar, både runt färdiga standardiserade informationstyper (kreditkortsnummer, pass, person-nummer osv) samt skräddarsydda informationstyper. Vi kan skapa avancerade regler baserat på allt ifrån ord, meningar eller mönster av information (regular expression). Baserat på dessa informationstyper kan vi sedan söka igenom vår data för att få insikt i olika typer av frågeställningar. Exempelvis hur många dokument:

– förekommer med GDPR relaterade uppgifter

– innehåller kreditkortsuppgifter

– innehåller information om kommande uppköp

– innehåller information om börsnotering

… listan kan göras lång och baseras på vilka behov som finns.


Content explorer

För att lista data som innehåller dessa informationstyper används Content explorer. En första vy ger oss en inblick i hur många filer som uppmärksammats med de mest förekommande informationstyperna. På samma sätt listas även de mest nyttjade informationsklasserna (Sensitivity labels). Vi får en tydlig bild över vilka Office 365 tjänster (Exchange, SharePoint, OneDrive) som innehåller de här informationstyperna eller klassificerad information. Den här listan kommer växa under året med fler källor.

Exemplet här listar vilka filer som innehåller personnummer och redovisar hur många av dessa som förekommer i verksamhetens e-post (Exchange), SharePoint eller OneDrive image

Rättigheter och spårbarhet

Vidare har vi även möjlighet att se detaljer och se aktuella data som innehåller den här informationen. Första frågan som de flesta organisationer ställer sig här rör både privacy och governance, vem kan se det här och hur kan vi styra/kontrollera vilka som har den här möjligheten.

Redan nu finns flera tekniker på plats för att kontrollera tillgång till denna vy.

En global administratör kan inte se några detaljer. Utan möts av följande:


Precis som det redovisas finns det två olika rättigheter som ger olika typer av rättigheter till detta.
”Content Explorer List Viewer” Den här rättigheten ger en insikt i vilka dokument/tjänster som innehåller dessa informationstyper/klasser.

Administratören kommer så långt att den kan identifiera på filnamn över filer som innehåller en viss typ av information/klass. Där efter tar det stopp.


Genom att tilldela administratören även rättigheterna ”Content Explorer Content Viewer” ges full insikt där även de dokument som innehåller den här typen av information eller klassning redovisas.


Med andra ord vill vi hålla koll på vilka administratörer som innehar rättigheterna ”Content Explorer Content viewer” och se till att konton med denna roll inte är permanent administratör utan använder PIM eller dylikt för att skydda och kontrollera behörigheten till den här typen av information.
Det här är fortfarande insider preview och är en funktion i Office 365 E5.

Agera på identifierade risker

Baserat på vad som identifierat kan vi sedan använda olika typer av tekniker för att agera och exempelvis skapa en DLP Policy som antingen krypterar innehållet eller motverkar tillgång till filerna för vissa användare

Vill du också testa på den här funktionen, kan du ansöka om att vara med i denna preview och mycket annat här: https://aka.ms/mip-preview

Rekommenderat är att du gör detta i en test-tenant. Som alltid måste CISO (eller motsvarande verksamhetsroll) involveras innan detta tas i skarp drift.

Publicerat i Microsoft Information Protection | Märkt , | Lämna en kommentar

Kritiska sårbarheter i RDGW och CryptoAPI

Det är alltid viktig att hålla sig uppdaterad runt nya identifierade sårbarheter för sina system och se till att dessa blir patchade så snart som möjligt. Under gårdagen släpptes två extremt viktiga uppdateringar som bör vara högsta prioritet att få ut på alla berörda system.

Det är dels en uppdatering för Windows Remote Desktop Gateway (RD Gateway) där det identifierats en sårbarhet som gör det möjligt att ta sig in via en publicerad RD Gateway. Sårbarheten gör det möjligt att ta sig in via RDP mot tillgängliga system utan autentisering. Vi har redan hört flera verksamheter som blivit attackerade med den här metoden. Sårbarheten rör alla Server versioner från Windows Server 2012 till Windows Server 2019.
Patcha så snart som möjligt! Skulle det vara något som hindrar en uppdatering/omstart börja med att inaktivera den externa tillgången tills uppdateringen är på plats.
Läs mer om uppdateringen här https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2020-0609

Det har också identifierat en sårbarhet i Windows CryptoAPI (crypt32.dll) som gör det möjligt att skriva kod som ser ut att vara korrekt signerad av en pålitlig utgivare (ECC Certifikat). Det här gör det möjligt att ta sig förbi flera säkerhetssystem som förlitar sig på signerade applikationer och även för att göra man-in-the-middle attacker som baserar sin kryptering av dessa certifikat.
Sårbarheten berör både Windows Server från 2016 till de senaste releaserna samt Windows 10!

Patcha så snart som möjligt!
Läser mer om uppdateringen här: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0601

Patchar för båda sårbarheterna är inkluderade i januaris Cumulativa uppdatering:



Publicerat i Threat Protection | Märkt , , | Lämna en kommentar

Höj säkerheten i lokala ADt med Identity Security Posture

Advanced Threat Analytics (ATA) och dess motsvarighet med molnhantering Azure Advanced Threat Protection (Azure ATP) har förutom att detektera intrång i lokal infrastruktur också varit ett bra verktyg för att identifiera sårbarheter.

Sårbarheter kan vara allt ifrån svaga protokoll, felkonfigureringar till lösenord som går i klartext över våra nätverk. Det är inte helt ovanligt att det lokala Active Directoryt har uppgraderats succesivt utan att äldre protokoll och standarder har inaktiverats. Ofta finns det en osäkerhet vilka system som kan tänkas använda dom fortfarande och vilken påverkan det har för verksamheten att stänga ner dessa.

Identity Security Posture
För att få det underlag som oftast krävs för att göra en förändring finns nu en lösning, vid namn Identity Security Posture som redovisar sårbarheter och vilka tjänster, enheter och användare som påverkas.


Det här är en del av Microsoft Cloud App Security (MCAS) och förutsätter då att man integrerat Azure ATP med MCAS.


Identity Security Posture ligger som en ny tjänst under Investigate i MCAS och identifierar i nuläget följande sårbarheter:

· entities exposing credentials in clear text

· legacy protocols usage

· weak cipher usage

· unsecure Kerberos delegations

· Print spooler service on domain controllers

· dormant entities from sensitive groups

Respektive sårbarhet får en klassificering över hur kritisk den är för att stötta verksamheten att prioritera.

Genom att gå in på detaljer redovisas vilka objekt som är relaterade av sårbarheten och ger möjlighet att se detaljerna som Azure ATP identifierat.

Vi får även guidning över hur vi kan förhindra sårbarheten och möjligheten att via den här tjänsten få uppföljning om vi lyckats motverka den.

Som exempel har vi ofta detekterat att det går lösenord i klartext när vi börjat utreda en ny kund och första utmaningen handlar om att utreda vad som kommer påverkas i verksamheten om vi förhindrar detta. Tack vare den här lösningen får vi en insyn över vilka servrar och konton som är inblandade. På så sätt kan vi involvera tjänsteägare för att först lösa verksamhetsbehoven, för att sedan motverka sårbarheten. Exemplet nedan visar detaljer över vilka konton och servrar som använder RC4, DES och kan följa upp aktiviteterna som Azure ATP fångat upp.


Ett annat bra exempel handlar om våra känsliga konton med höga rättigheter. Exempelvis domänadministratörer eller andra känsliga konton. Här kommer oftast frågor som: Används fortfarande kontot eller när används det senast?

Här redovisas precis detta och ger oss underlag för att kunna ta ett beslut om kontot ska åtgärdas.


Publicerat i Threat Protection | Lämna en kommentar