<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alex Fields on Medium]]></title>
        <description><![CDATA[Stories by Alex Fields on Medium]]></description>
        <link>https://medium.com/@itpromentor?source=rss-7202e9f16eb3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*v4AYisBlpLH7PD-nWT6-DA.jpeg</url>
            <title>Stories by Alex Fields on Medium</title>
            <link>https://medium.com/@itpromentor?source=rss-7202e9f16eb3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:31:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@itpromentor/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Unboxing Microsoft Defender for Business, Part 1: Simplified configuration process]]></title>
            <link>https://medium.com/re-office-365/unboxing-microsoft-defender-for-business-part-1-simplified-configuration-process-62b95e6e168c?source=rss-7202e9f16eb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/62b95e6e168c</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[microsoft-365-business]]></category>
            <category><![CDATA[defender-for-business]]></category>
            <category><![CDATA[managed-it-services]]></category>
            <category><![CDATA[defender-for-endpoint]]></category>
            <dc:creator><![CDATA[Alex Fields]]></dc:creator>
            <pubDate>Mon, 17 Jan 2022 03:11:26 GMT</pubDate>
            <atom:updated>2022-01-30T13:41:29.701Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eKfAF-voNW6clR20.png" /></figure><p>I have been playing with the <a href="https://www.itpromentor.com/introducing-mdb/">new product</a> this past month since getting access to the preview. If you have not yet had a chance to see Microsoft Defender for Business in action, then read along! To get your hands on a copy of this product yourself, the preview sign-up is here: <a href="https://aka.ms/MDB-Preview">https://aka.ms/MDB-Preview</a>.</p><p>Once you have the preview activated in your tenant, you will assign the licenses, just as you would for any other product (however, note that in the future of General Availability, this product will be included in your Microsoft 365 Business Premium license, so no need to assign additional licenses in that case).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Vdqy67ZFSAXARt_3.png" /></figure><p>To activate the product, visit the Microsoft 365 Defender security center: <a href="https://security.microsoft.com/">https://security.microsoft.com</a> and go to <strong>Settings &gt; Endpoints</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YwruFEOZvM2uuKl-.png" /></figure><p>You should be greeted with the first-run wizard experience. Click <strong>Get Started</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OQmubms_iUuEwo0C.png" /></figure><p>In order to get the “Automatic onboarding” option on this next page, you must have a minimum of three devices already enrolled with Microsoft Endpoint Manager. They do not all have to be Windows devices, but only Windows devices will be automatically onboarded during this setup process. In my demo tenant, I have four devices, so I just barely clear the requirement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ov9lByNHm_-uCCTF.png" /></figure><p>Without the minimum number of devices, you would see the manual onboarding process screen, which looks something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JzgpuvtZzGuBudU3.png" /></figure><p>In this case you can just expand each option for more instructions about the onboarding process, which you would need to complete yourself, later. I will proceed with the assumption that you will qualify for <strong>Automatic onboarding</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4kI_R_GAD6S8NVf3.png" /></figure><p>If you are like most of us, you probably already have some policies in Microsoft Endpoint Manager scoped to users and devices in your organization. You can either continue using MEM to deploy your Microsoft Defender policies, or, you can switch to using the Microsoft Defender for Business “ <strong>simplified configuration process</strong>.” What is that?!</p><p>It just means the polices for Microsoft Defender will be managed right here in the Microsoft 365 Defender security center, rather than via the Endpoint Manager portal. Understand that whichever way you choose to manage your policies is up to you; in many ways this is just an aesthetic choice.</p><p>The policies in the security center will be somewhat simplified with fewer options exposed, and it is not recommended to deploy both policy types (just choose one or the other method, not both). For the purposes of this walkthrough, I will select the option to deploy my policies with the <strong>MDB simplified configuration process</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VrSSwzNDAjCsA9-7.png" /></figure><p>If you have pre-existing policies that are going to conflict with the settings deployed by the simplified configuration process, then you will see a message at the bottom of the next screen telling you so, and highlighting which policies need to be removed (deleted) before proceeding. When you have successfully removed the policies, you should be able to go “Back” and then return forward again to this page, and see the message at the bottom clear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l68Fv5lKs10Xx8_N.png" /></figure><p>I am going to leave the selection on the first option, to apply the default security policies against all devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SKHg1NTxez4zMIqv.png" /></figure><p>Then you can simply review the information on this last page and click <strong>Submit</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1mNFFLOtcs-9EtBG.png" /></figure><p>Now that we have completed the onboarding wizard, let’s review what has been done.</p><h3>What happened?</h3><p>The first thing that the wizard did was to automatically create the connection that is required between Intune (Endpoint manager) and Microsoft Defender for Business, and that includes the onboarding policy in the Endpoint manager portal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hQD4Q3zTjmuGdivU.png" /></figure><p>For example, if you return to <strong>Settings &gt; Endpoints</strong>, and then find <strong>Advanced features </strong>in the Defender portal, you will find the <strong>Microsoft Intune connection</strong> has been turned <strong>On</strong>. (Some other items in here have already been enabled for you as well, such as <strong>Automated Investigation</strong>, <strong>Tamper protection</strong>, <strong>EDR in Block mode</strong>, and others).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pTKxSmVhaL0UHs4a.png" /></figure><p>As well, in the Endpoint manager portal ( <a href="https://endpoint.microsoft.com/">https://endpoint.microsoft.com</a>), we find under <strong>Endpoint security &gt; Endpoint detection &amp; response</strong>, there is the <strong>Default EDR policy for all devices</strong>. With these items in place, all of your Windows devices have been automatically onboarded.</p><p>From the Microsoft 365 Defender portal ( <a href="https://security.microsoft.com/">https://security.microsoft.com</a>) navigate to <strong>Device configuration</strong> under <strong>Endpoints</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q1aSP4honFI-EDoD.png" /></figure><p>At the time of this writing, the preview only includes two <strong>Windows client</strong> policies: <strong>Next-generation protection</strong> (i.e. Antivirus) and <strong>Firewall</strong>. In the future, I hope we will have additional policies such as <strong>Attack surface reduction</strong> and others. I assume that we may also see additional tabs for other client devices, eventually. But today, the settings put in place are limited to what you see here. These would roughly correspond with the policies you find in the MEM portal under <strong>Endpoint Security &gt; Antivirus</strong>, and <strong>Endpoint Security &gt; Firewall</strong>, respectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2Xwoac0fWwVw-o8h.png" /></figure><p>Some other notes about these default policies: you can edit these policies, or create new policies using <strong>Add</strong>, but it is not possible to delete the default policies created by the wizard. It appears that the way it works is the default policies will take the lowest order of precedence, so if another higher-ranked policy is added, then those settings would be applied. If a device does not fall in scope for a higher-ranked policy, then the settings in the default policy would still hold. Most SMB organizations will likely only need one policy, targeted against all devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/0*zM4S8WelBBoOzHUd.png" /></figure><p>If you do choose to edit the settings, you will find common options like turning on Real-time protection, Block at first sight, network protection, and enabling protection against potentially unwanted apps. Further down you can schedule a daily scan, and at the bottom of the policy you can make Antivirus exceptions as needed by process, file extensions, or folder paths.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mxVD-zmCstTR0pRu.png" /></figure><p>The firewall policy is even simpler: it is just set up to <strong>Block </strong>incoming connections by default for Domain, Public, and Private networks, and then it gives you a place at the bottom to add rules to allow for connections as needed.</p><h3>How do I feel about it?</h3><p>In general I feel extremely good about this product. It is the best thing we could have hoped for this past year, with respect to the Microsoft 365 Business Premium SKU. But I am hopeful that we see a few more improvements in this experience before it goes to General Availability:</p><ol><li>Additional onboarding options, especially for personal devices (macOS, iOS/iPadOS, and Android). For example, did you know that we technically have a <a href="https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/zero-touch-onboarding-of-microsoft-defender-for-endpoint-on-ios/ba-p/3038045">zero-touch deployment option for iOS devices</a> now? Would be great to include mobile device onboarding in the automated onboarding options someday.</li><li>More policies in the Defender portal: ASR rules, Application Control, Device Control, and Application Guard come to mind right away.</li><li>More clarity on the decision to use the MDB “simplified” policies in the Defender portal versus sticking with MEM. For example, why not just have the policies in the Defender portal automatically deploy corresponding policies in MEM, so that the same object could be viewed from both places? This would reduce confusion, I believe, and keep a more consistent experience as well, for those who have worked with the enterprise product.</li></ol><p>These small scruples aside, I think we’re off to a fantastic start.</p><h3>Additional onboarding notes</h3><p>As we saw, the onboarding wizard takes care of your Windows devices for you, but if you want to get non-Windows devices into MDB, then you have to do that yourself after the fact. You can always review the manual onboarding instructions at any time from <strong>Settings &gt; Endpoints &gt; Onboarding</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RSxbzs3zVBP-7ZpT.png" /></figure><p>Just select your operating system at the top to learn how to deploy Defender on other device platforms. For iOS and Android, this basically means downloading the <strong>Defender Endpoint</strong> app from your app store, and signing in. As I mentioned, iOS also has a <a href="https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/ios-install?view=o365-worldwide#auto-onboarding-of-vpn-profile-simplified-onboarding">zero-touch method</a> now. There is a different download package for macOS entirely (not in the app store unfortunately), and that can be applied either <a href="https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/mac-install-manually?view=o365-worldwide">manually</a> or <a href="https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/mac-install-with-intune?view=o365-worldwide">via Intune</a>.</p><p>Hopefully that gives you enough direction to get started with this product. I suspect there may be changes to the experience before it goes to GA, so we will keep an eye on that. In later articles of this series, we will explore additional features in Microsoft Defender for Business, starting with Threat and Vulnerability Management.</p><p><em>Originally published at </em><a href="https://www.itpromentor.com/unboxing-microsoft-defender-for-business-part-1-simplified-configuration-process/"><em>https://www.itpromentor.com</em></a><em> on January 17, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62b95e6e168c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/unboxing-microsoft-defender-for-business-part-1-simplified-configuration-process-62b95e6e168c">Unboxing Microsoft Defender for Business, Part 1: Simplified configuration process</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The three opportunities for MSP’s moving forward]]></title>
            <link>https://medium.com/re-office-365/the-three-opportunities-for-msps-moving-forward-d9bb6ab6070?source=rss-7202e9f16eb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9bb6ab6070</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[security-compliance]]></category>
            <category><![CDATA[managed-it-services]]></category>
            <category><![CDATA[cloud-native]]></category>
            <dc:creator><![CDATA[Alex Fields]]></dc:creator>
            <pubDate>Fri, 30 Jul 2021 15:54:00 GMT</pubDate>
            <atom:updated>2021-09-20T22:18:05.498Z</atom:updated>
            <content:encoded><![CDATA[<p>The writing has been on the wall a while now; with a mass exodus to cloud services such as Microsoft 365 from traditional on-premises infrastructure, it was only a matter of time before those selling MSP services had to either evolve or die off. And with <a href="https://us-cert.cisa.gov/ncas/current-activity/2021/07/04/cisa-fbi-guidance-msps-and-their-customers-affected-kaseya-vsa">recent high-profile attacks</a> against traditional MSP platforms like Kaseya, plus the recent announcement about <a href="https://techcommunity.microsoft.com/t5/small-and-medium-business-blog/announcing-microsoft-365-lighthouse-for-managed-service/ba-p/1698181">Microsoft 365 Lighthouse for MSPs</a>, we finally have more providers scratching their heads and wondering whether the old ways aren’t on their way out after all. One of my friends and fellow MVP, Amy Babinchak, runs an MSP that <a href="https://www.thirdtier.net/2021/07/06/managing-an-msp-without-an-rmm/">does not even use an RMM</a>. Amazing? Or is that the direction we are heading in general?</p><p>The sea change that is coming is not just being driven by <em>security </em>concerns, either. Yes, cybersecurity is one major area of opportunity (and still the one I receive the most inquiries about), but the Cloud-First, Mobile-First era we are in is much larger than say, the ‘Zero Trust’ conversation. Modernizing our approach to security is but one facet of a larger puzzle, and I hope to draw out some of what the future might look like, from the perspective of Managed Services, here today.</p><p>I believe that we are now at a time in our history where we have never had greater opportunity to expand our service offerings and provide more <em>value </em>to customers than ever before. In fact, it is difficult to impossible for me to list all of the various projects, products, and services that one could build even just leveraging Microsoft 365 and Azure (to say nothing of the other tech vendors out there). Instead, I will try to distill the three major <em>categories </em>of opportunity, as I see it, for the Managed Services Provider, especially if they work in the Microsoft space.</p><h3>Modern Management</h3><p>If you manage a Microsoft environment, with Windows desktops, email in Office 365 Exchange Online, document collaboration taking place in OneDrive and SharePoint Online, and meetings and teamwork taking place in Teams, then why not tie your management tools into the same infrastructure? The benefits are many (Conditional Access is but one that we harp on here at ITProMentor.com). You can even tie your phone system into a Teams-integrated solution in this case, so that voice, messaging, voicemails, meetings, etc. can all live in one place. The more you simplify and consolidate, the more life gets easier for admins and users alike.</p><p>When all the pieces of productivity, communication, software deployment, and asset management are connected and working together (something Microsoft refers to as “Native Management,” then you can expect faster boot times, smoother operations, stronger security, and more satisfied end users. At least, this is what the marketing says (it is backed by Microsoft’s own telemetry and data). Some folks doubt this amounts to anything in the real world, but look: I have yet to see MSP’s bringing the full experience home to their customers, so how can you knock it until you give it an honest go?</p><p>Looking at it another way, modernizing your management and consolidating functions into as few vendors as possible has certain efficiency benefits simply in terms of total cost of ownership: training, software licensing, fewer points of management and so on. While we know this is intuitively correct, we still resist it for some reason. I believe that this is born mostly from an inability to distinguish between what is merely a cost (e.g. utility bill) and what is actually value-added benefits from a customer’s perspective. Many of my MSP customers are still obsessed with finding the “best of breed” in each area, even if those areas are not really <em>valued </em>by customers. For example: your customer doesn’t care which endpoint security solution you use, as long as you have ways of monitoring their endpoints and keeping them reasonably protected.</p><p>I now work with a few MSP’s who are getting OK at implementing new pieces of the puzzle like Intune (usually in addition to everything else they are doing), but not many (yet) are really jumping ship from a traditional toolset and embracing a fuller expression of “Native Management” as Microsoft defines it. This takes more commitment and work, but in the end it will pay dividends. Why? Because everything you are outsourcing is the commodity stuff that you don’t want to be doing anyway. Like I said, your customer just wants stuff to be fast and safe to use, and for their service providers to be responsive to any issues as they crop up. Simple, yes? Then do not over complicate things by trying to architect and manage your own management infrastructure: you can literally lease it from Microsoft for free (well, more accurately the infrastructure is just included in the price paid for a subscription), but unless you are managing it then your customer experiences none of its benefits.</p><h3>Digital Transformation</h3><p>The opportunity that probably represents the largest piece of the financial pie is the one that is still the most ignored amongst MSP’s at large, and I have no idea why. I can only assume that they have so long been pre-occupied with infrastructure and management (much of which we can outsource and simplify now per the conversation above), that they simply remain blind to this massive pile of future cash waiting to flow into the pockets of those willing to lead the way and take the risks.</p><p>As I mentioned, Modern Management is an inevitability because it is basically a commodity; there is nothing the customer values less than the infrastructure. They don’t care how or why their tech works, they just want it to work with as little interruption as possible, and of course, to remain reasonably safe while doing so. This also implies that the customer is going to be more miserly in spending money on this category. So what <em>does </em>the customer care about then? What would make them want to loosen the purse strings, so to speak, and spend more money with you? Simple, my friends: you need to help them get more value from their data, apps, and services!</p><p>Most MSP’s pretty much ignore the ins and outs of the businesses they serve. They were good at Microsoft, or Citrix, or whatever technologies were supporting their customers’ businesses, but what the customer did with that technology was ultimately something that lived behind a big curtain; MSP’s didn’t really care to peek behind it either. Well, time to ditch that mentality. Your new pitch is: <em>Look Mr. or Mrs. Customer, I can slap this new technology in place for you, but how will you get any benefit from it unless I can teach you how to use it in your business more effectively?</em> <em>For that, I need to see how you work today with your clunky old tools, so I can recommend something even better using this new toolbox.</em></p><p>This type of engagement has existed for a long time with platforms like Dynamics; there have been application integrators for decades, just as there have been MSPs. But shifting into the productivity space, understand that your work will of necessity include discovery and consulting time, as well as training and projects, and most likely, on-going support and maintenance of any solutions that are taught and built alongside with the customer. Even just in terms of better collaboration using modern tools like Teams and SharePoint, to say nothing of PowerApps, PowerAutomate, PowerBI and so on. Many organizations are seriously underutilizing their modern software subscriptions, or do not understand what is possible (and that goes for MSPs as well, which is part of the problem).</p><h3>Cybersecurity and Compliance Management</h3><p>The third category is one that I have (so far) spent most of my time with here at ITProMentor.com. This is an area that has been extremely hot among MSPs for a few years now, however, I still find that the majority of them are doing very poorly with it. This is mostly due to the fact that they are “product focused” and lack a comprehensive approach to security and compliance. In my courses, I encourage providers to follow a formal cybersecurity framework such as NIST or its simpler cousin, CIS.</p><p>Now I place both Security and Compliance into a single bucket here, but of course some will argue with me that these are distinct practices. Certainly; I just think that it is somewhat simpler to abstract to three major categories rather than four, especially because of how I view the overall picture. You see, modernizing management is basic level stuff (infrastructure, remember?), while Digital Transformation delves into the applications and business processes support “add-ons” which get layered on top. Cybersecurity and Compliance are necessary at every level; whether your work is focused on infrastructure, or on apps &amp; services, there is always a need to keep things secure and compliant (both within the bits and bytes of the tech, as well as in the real-world policies, processes, and procedures).</p><p>Here in the United States, we do not have that many compliance requirements (relatively speaking). Unless you are in a specific industry like Financial Services or Healthcare, or if you do contract work with the DoD, for example, you can pretty much do whatever you want and accept or mitigate risks to your own tolerance level. But I would not expect this to last, especially with the major cybersecurity incidents that have been in the news lately, and which are affecting businesses of all sizes, private and public sectors alike. Even though we do not have formal legislation yet, we can see the outlines starting to form; the <a href="https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/">Biden administration</a> has proposed some initial steps via executive order, and I suspect that any proposed legislation at the national level in the wake of these nation-state cyber attacks will have bipartisan support.</p><p>While it is true that compliance doesn’t necessarily equal security, the thrust of most compliance requirements is usually related to staying more secure. So as I tell my customers, if you do cybersecurity really well, then you will find it is much easier to meet compliance requirements when and where they crop up (now and in the future). Helping organizations understand the risks they face and tracking their progress against a formal plan is an area that is still underserved. Most MSPs still think about security in terms of reselling endpoint security software or some other set of security products; you want to go beyond this thinking and help establish a permanent out-sourced CISO function and SOC services for your customers. Then on top of that, help them build a compliance management practice that they participate in maintaining (every organization should have a compliance officer as well as someone who is responsible for interfacing with any security &amp; compliance vendors such as MSSPs).</p><h3>In a nutshell</h3><p>Perhaps you will think that my framework is too simple. It is deceptively simple, perhaps, only because this is a fairly high-level abstraction. There is a lot of stuff to work on here, just within the areas I have shared! And MSP’s who want to thrive in the new world will need to embrace and excel in at least one of these three categories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DeNWCSRroMMbO1m7" /></figure><p>Some people imagine a fourth category that is purely business consulting of some type. Well, that’s fine if you want to pursue it, but just understand that I think “pure consulting” is a bit of a vague prospect for someone whose purpose has traditionally been tied to the <em>technology </em>that enables small and mid-sized businesses to do whatever it is they do. In other words, I think you are just starting a different business in that case (not Managed Services). If you <em>are </em>going to start a so-called <em>pure</em> business consulting practice then you have to get more concrete: come up with a very clearly defined benefit (i.e. measurable outcome) that you are delivering. In my mind, instead, it makes more sense to stick with focusing on how <em>technology </em>can be used to help businesses accomplish whatever it is they already do, but better, easier, in less time, with less risk, or whatever.</p><p>Last, if you believe that there are opportunities I have not seen, which are not captured in some way by one of these three categories, then I would love to hear your thoughts in the comments, below.</p><p><em>Originally published at </em><a href="https://www.itpromentor.com/the-three-opportunities-for-msps-moving-forward/"><em>https://www.itpromentor.com</em></a><em> on July 30, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9bb6ab6070" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/the-three-opportunities-for-msps-moving-forward-d9bb6ab6070">The three opportunities for MSP’s moving forward</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fast and Free Incident Response Tools in Microsoft 365]]></title>
            <link>https://medium.com/re-office-365/fast-and-free-incident-response-tools-in-microsoft-365-1379af53c827?source=rss-7202e9f16eb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1379af53c827</guid>
            <category><![CDATA[microsoft-365-business]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[powershell-script]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[azure-active-directory]]></category>
            <dc:creator><![CDATA[Alex Fields]]></dc:creator>
            <pubDate>Fri, 09 Jul 2021 11:19:00 GMT</pubDate>
            <atom:updated>2021-07-25T10:08:46.014Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/0*EItlOk-pk0QaS7tv" /></figure><p>As part of the <a href="https://squareone365.teachable.com/p/squareone-summer-of-cyber-security-series">SquareOne Summer Security Series</a>, our group recently explored the topic of <a href="https://squareone365.teachable.com/p/june-2021">Incident Response in Microsoft 365</a>. This was a very well-received course, and I felt a blog post was in order to cover off on some of the important content from that segment, which I think everyone should have in their back pocket, especially if their daily work revolves around serving SMB customers.</p><p>Now the ideal scenario would be for every single small business to have a Managed Security Services agreement, and as part of that agreement, I would want them to have a Security Information and Event Management (SIEM) platform such as Azure Sentinel in place to capture audit log data. This kind of setup makes incident response MUCH easier for those of us who actually have to respond to cybersecurity events. But we do not live in a fantasy world, do we? No, we live in the real world, and especially in the SMB market, such fancy agreements and high-tech tools are rarely available (though I hope this changes over time).</p><p>Even if you are one of those oddballs who is ahead of the curve, and you actually offer decent managed security services (this is still incredibly rare according to my research), you will likely still run into situations with prospects or otherwise, where you will need to work with whatever data you can get natively from the cloud services, without any other products or tooling in place. So to that end, I wanted to share with my readers some of the tools I have been using when called upon to help with responding to incidents in a Microsoft 365 environment.</p><h3>The PowerShell Modules</h3><p>There are three basic PowerShell modules I recommend that everyone have installed in order to work effectively with audit data in Microsoft 365.</p><ol><li><a href="https://www.powershellgallery.com/packages/HAWK">Hawk module</a>: <strong>Install-Module Hawk</strong></li><li><a href="https://www.powershellgallery.com/packages/ExchangeOnlineManagement">Exchange Online Management module (V2)</a>: <strong>Install-Module ExchangeOnlineManagement</strong></li><li><a href="https://www.powershellgallery.com/packages/AzureADIncidentResponse/">Azure AD Incident Response module</a>: <strong>Install-Module AzureADIncidentResponse</strong></li></ol><p><em>Note: You will also need to have the </em><a href="https://docs.microsoft.com/en-us/microsoft-365/enterprise/connect-to-all-microsoft-365-services-in-a-single-windows-powershell-window?view=o365-worldwide"><em>Azure AD module and MSOnline module</em></a><em> installed.</em></p><p>The amount of data you can access with these free tools varies depending on the subscription level of your tenant, and also on whether you have <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/turn-audit-log-search-on-or-off?view=o365-worldwide">enabled the Unified Audit Log</a>. For most SMB customers, we are seeing tremendous adoption of the Microsoft 365 Business Premium subscription. I do not recommend anything less than this to my customers, as it is dollar for dollar the best value in the cloud, and it even includes Azure AD Premium P1. With this subscription you will have <strong>30 days </strong>of audit data available from Azure Active Directory (with Business Standard or Basic plans you will only have 7 days).</p><p>As mentioned, you should also be enabling the Unified Audit Log using the <a href="https://docs.microsoft.com/en-us/powershell/exchange/connect-to-exchange-online-powershell?view=exchange-ps#connect-to-exchange-online-powershell-using-modern-authentication-with-or-without-mfa">Exchange Online Management</a> module:</p><p><strong>Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true</strong></p><p>This is not on by default, but once you have turned it on, the Unified Audit Log will allow you to capture and store up to <strong>90 days </strong>of audit data from the services in Microsoft 365 (e.g. including Azure AD, Exchange, SharePoint, Teams, etc.). If you have Microsoft 365 E5 subscriptions then you actually get 365 days by default, with the ability to create audit log retention policies up to 10 years if you wish. But again, this option doesn’t exist for most SMB customers (E5 is almost 3x the price of Business Premium).</p><p>How you use the PowerShell modules, and what steps you take to respond to incidents will generally depend on what is being reported: what is it that happened which caused us to say, “ <em>Wait, we’re in incident response mode now?</em> “ But for most of the incidents I have been involved with, I find that the steps follow this pattern:</p><h3>Step 1. Gather data and highlight low-hanging fruit, form hypotheses</h3><p>The best way to gather data up front, regardless of what other tools you have at your disposal, is to run the Hawk module. There are two major functions and a couple of dozen minor functions included with this module.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FSScjwM2W7ZK5s4e" /></figure><p>The two you want to key in on are <strong>Start-HawkTenantInvestigation</strong> and <strong>Start-HawkUserInvestigation</strong>, each of these basically run all the other functions and output the resulting data into a directory of your choosing. If you have specific users you are interested in already as part of your incident, you can execute the user investigation for them, but I generally always execute the tenant investigation also, regardless of what else we know about when we start.</p><p>You will be get a few prompts to sign in, specify an output directory, as well as a timeframe you are interested in investigating (90 days is the default but this window is dependent on having the Unified Audit Log enabled). Once the gathering is done, in your output directory you will have several files to review. There is a txt file called <strong>_Investigate.txt</strong> that is worth checking out, because it will highlight anything especially risky, such as mailbox forwarding, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ETSJy639YlZPyDrD" /></figure><p>Then under the <strong>Tenant </strong>folder, you would find output that was gathered using the tenant investigation, and under any folder named for the users of interest, you would find the output relating to the individual users you investigated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/0*W_3SmJXFtFI7ZqlY" /></figure><p>You can use this information to highlight interesting facts, like who are the admins, who has impersonation rights, what are the transport rules, have their been any forwarders set up, what apps and permissions are in the environment, etc. These facts can help you to supplement the other facts of which you are already aware (again, why are you investigating). Once you have this initial information, you can start to form some hypotheses or “guesses” about where to look next. Proceed to the next step after your initial analysis.</p><p><em>Note: Another way you can use this module is during assessments or as part of normal maintenance visits to a tenant: be sure you have a known “baseline” of the output, and then investigate changes to things like admin roles and applications as needed.</em></p><h3>Step 2. Get more granular and follow the breadcrumbs, prove your hypotheses</h3><p>Now the Hawk module is great because it will give you a bunch of information quickly, but most often it is not enough on its own. For example, Hawk will output all of the Enterprise apps connected to your Microsoft 365 environment with a list of permissions that have been consented for each app, but you will probably want to see <em>who </em>authorized these permissions, and <em>when</em>. Another example: it will also spit out a listing of the members belonging to admin roles in your org, but you may want to find out what other activities those accounts have performed around the time of the incident. For these types of inquiries, you would need to hunt for more evidence in the audit data.</p><p>Using the Exchange Online Management module, you can <a href="https://docs.microsoft.com/en-us/powershell/module/exchange/search-unifiedauditlog?view=exchange-ps">search the audit log</a> (again, up to 90 days for most subscriptions). The search results can be piped to output via Export-Csv or Out-GridView. What you are searching for will vary depending on what you want to know. For example, you might want to search for all the events performed by a certain user account, or perhaps you want to investigate all of the events related to a particular IP address. You can see examples of each using these scripts on GitHub:</p><p>This is similar to using the Security &amp; Compliance center (or new Compliance center) to perform an audit log search (e.g.: <a href="https://compliance.microsoft.com/auditlogsearch">Audit — Microsoft 365 compliance</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qOn5QbAlXHFfVXrD" /></figure><p>You will notice however that the PowerShell search returns results much faster, and allows for better queries. For example in the web UI there is no option to search by IP address, and they do not give you all the possible activity types. Take a look at an example of the syntax required to look at specific records that match the activity “Add user” which comes from the Azure Active Directory activity log:</p><p><strong>Search-UnifiedAuditLog -StartDate 05/15/21 -EndDate 06/15/21 -RecordType AzureActiveDirectory -Operations (“Add user.”)</strong></p><p>When you use the PowerShell cmdlet, you can specify the <strong>record types </strong>( <a href="https://docs.microsoft.com/en-us/office/office-365-management-api/office-365-management-activity-api-schema#auditlogrecordtype">see a list of types here</a>) as well as the <strong>operations </strong>within those types ( <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/search-the-audit-log-in-security-and-compliance?view=o365-worldwide#audited-activities">see the list of operations here</a>), and I have found several that are not represented in the webUI for some reason.</p><p>I also have a few things that I am interested in sniffing out during almost <em>any </em>investigation (for example, whether someone has modified admin roles, whether anyone has added or modified users, apps, or devices, etc.), and for that I have another script which will output several csv files describing different activities by type:</p><p>I usually will search (Ctrl-F) within the csv file for the content I am interested in. For example if I have identified an application that I think is suspicious, I will search for that application name to see if it has been recently added or modified (these events will turn up in the audit log).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Tf_WgLr7SjyrsoZ2" /></figure><p>I cannot really do that type of searching until I get the audit data out of the portal, unfortunately. I find that PowerShell makes this whole thing much easier, by allowing me to parse out specific events into different files, and then I can browse the data more closely on my own. Some people take the output files and upload them into something like <a href="https://docs.microsoft.com/en-us/azure/data-explorer/data-explorer-overview">Azure Data Explorer</a>, and you can do that if you want to. I just use low-tech tools like “ <em>Find</em>” and (where it makes sense) copy-and-paste into Notepad to make it more readable (it is admittedly difficult to read <em>all </em>the audit data in Excel).</p><p>Now unfortunately, not everyone has the Unified audit log enabled when disaster strikes, so in that case, you may need to switch over to using the <em>other </em>PowerShell module I mentioned: the Azure AD Incident Response module. Again this is my second choice since you only get 30 days without the Unified audit log (provided you have Azure AD Premium P1). This module contains several different functions; all of them start with Get-AzureADIR(something). For example:</p><ul><li><strong>Get-AzureADIRSignInDetail</strong>: this function will return sign-in data</li><li><strong>Get-AzureADIRAuditActivity</strong>: this function can return activity log data</li></ul><p>There are many other functions, which you can browse simply by typing Get-AzureADIR and then pressing tab to rotate through the rest of the functions, but many of them basically rely on the two I listed above, and just output a sub-set of data from either the sign-in log or the activity log. For instance, there is a function called <strong>Get-AzureADIRUserLastSignInActivity</strong>, which will return just the <em>last</em> sign-in event for users in the tenant. You can also use some additional parameters to just see stale sign-ins (if the las sign-in is beyond a threshold of say 30 days).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/0*O1j-6M6LYW58yf_0" /></figure><p>For any function you might be interested in, you can always type Get-Help {Function} -Examples to see examples of how these are used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nBZth2YQYsgH8fh0" /></figure><p>Some of the scripts that I use and provide as examples are:</p><p>Those last two will loop through any users assigned Azure AD administrative roles and output sign-in and activity data, respectively. There are a bunch of other functions too, and I have included a few other interesting outputs from the various Azure AD IR functions in this script:</p><p>I find that the output from this tool is a bit easier to read than the output from the Unified Audit Log, whether going to Export-Csv or Out-GridView. But you should explore the module more on your own. Completing these steps will help you to confirm your hypotheses and/or expand the scope of your investigation (for instance you might start out looking at a particular account of interest, but through your investigation of sign-ins, IP addresses, and activity information, find additional users or apps that are potentially compromised).</p><h3>Step 3. Remediation</h3><p>How you remediate the incident depends on what you found in the preceding steps. For example, you might have to delete an application, or remove some permissions. You might also need to reset a user’s password and/or clean up their devices. It all depends on what happened during the incident and what you found in your investigation. One script that I will use when cleaning up compromised user accounts is:</p><p>This will give you the option to disable accounts and registered devices, and also an option to reset passwords and re-enable accounts and devices. Last, you can loop through all the admins and reset passwords for privileged users (excluding the current account and up to one other you specify).</p><p>But there are many other things you may need to do during this phase. One other resource I can recommend: Incident Response Playbooks by Microsoft ( <a href="https://aka.ms/IRPlaybooks">https://aka.ms/IRPlaybooks</a>). They currently publish three common scenarios: phishing, password spray, and app consent abuse. Each contains a nice flowchart and some detailed step-by-steps for accomplishing various tasks, like searching for and removing malicious emails using content search.</p><h3>Limitations</h3><p>Obviously there is little to no tooling included for stuff like endpoints and local area network devices (or even traditional Active Directory), without upgrading to other subscriptions such as Microsoft 365 E5 or purchasing add-ons individually like Defender for Identity, Defender for Endpoint, etc. But the point is that you will still be able to investigate and remediate certain types of cyber incidents impacting Microsoft 365 customers, regardless of their subscription level. Also I want to stress the limitations on your time horizon based on your subscription level. Business Premium is the bare minimum I recommend to any customer, and of course you absolutely must get the Unified audit log turned on for the full 90 days of visibility.</p><p>In the future, as more SMB’s out there ditch their on-premises infrastructure and move more and more of their workloads into Microsoft 365 and other SaaS apps, it is increasingly important to link as many of those services to Azure AD as possible; by setting up SSO for all of your various corporate apps, you will have one place to enforce security policies (i.e. Conditional Access) and also to investigate and hunt across the audit data when there is a suspected breach event.</p><p>Ideally, we would see more service providers standardizing on Azure Sentinel for every managed customer. There are a few out there who have figured this out (especially because this is one of the areas where we <a href="https://azure.microsoft.com/en-us/blog/build-a-scalable-security-practice-with-azure-lighthouse-and-azure-sentinel/">already have multi-tenant support</a>). Not to mention, data <em>ingestion </em>is free for many Microsoft cloud services (but to be clear there is still a cost to Azure Sentinel). But all of that is a topic for another day.</p><p><em>Originally published at </em><a href="https://www.itpromentor.com/fast-and-free-incident-response-tools-in-microsoft-365/"><em>https://www.itpromentor.com</em></a><em> on July 9, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1379af53c827" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/fast-and-free-incident-response-tools-in-microsoft-365-1379af53c827">Fast and Free Incident Response Tools in Microsoft 365</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple Sensitivity Label design for the SMB]]></title>
            <link>https://medium.com/re-office-365/simple-sensitivity-label-design-for-the-smb-142097eb5f7d?source=rss-7202e9f16eb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/142097eb5f7d</guid>
            <category><![CDATA[sensitivity-labels]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[data-classification]]></category>
            <category><![CDATA[security-and-compliance]]></category>
            <category><![CDATA[data-protection]]></category>
            <dc:creator><![CDATA[Alex Fields]]></dc:creator>
            <pubDate>Fri, 11 Jun 2021 14:45:00 GMT</pubDate>
            <atom:updated>2021-06-12T14:50:40.909Z</atom:updated>
            <content:encoded><![CDATA[<p>In the <a href="https://www.itpromentor.com/cisv8-assessment-tool/">recent updates to the CIS Controls</a> (v8), one of the most noticeable changes was the re-prioritization of <strong>Data Protection</strong> (now Control #3, up from #13 previously). This control calls out a number of safeguards: inventory of sensitive data and data classification is among them. <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/sensitivity-labels?view=o365-worldwide">Sensitivity labels</a> can help an organization to solve for these safeguards.</p><p>Even before the CIS updates landed, I had been seeing an increase in requests and questions related to Sensitivity labels. It is easy to see why: <a href="https://www.itpromentor.com/behold-the-power-of-labels/">Sensitivity labels are amazing</a>! But of course, there are still <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/sensitivity-labels-sharepoint-onedrive-files?view=o365-worldwide#limitations">several known limitations</a> with them, so it is important to go in with eyes open. Now, for those of you curious about implementing labels in your own organization, you might be asking, “ <em>What is a good ‘default</em>’ <em>data classification scheme? What labels should I create for users to start?</em> “</p><p>Excellent question. There is of course no one single ‘best practice’ or ‘right answer’ here. But there are a few <em>wrong </em>answers. The most important point: you must not overcomplicate the labels in your organization. The simpler, the better I always say, and not just with regard to labels! The first time I began consulting on Sensitivity labels, the organization I was working with wanted to implement something on the order of 40+ labels. That’s a mess, and nobody is going to understand what labels to use when with that many choices.</p><h3>Keep it simple</h3><p>You don’t necessarily need to reinvent the wheel. You can always start small, and grow later. For customers who do not know where else to start, but want a way to begin identifying and protecting their most sensitive information, I suggest a simple set of labels such as the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/0*XwLV-qOJXXVncM7T" /></figure><p>This is a very basic classification scheme that will allow any organization to start separating their data into categories by sensitivity, and this helps satisfy a few safeguards under CIS Control #3, Data Protection:</p><p><em>CSC #3.2: Establish and maintain a data inventory. Inventory sensitive data, at a minimum. Review and update inventory annually, at a minimum, with a priority on sensitive data.</em></p><p>Notice that the order of the labels matters. Your most sensitive label should be listed <em>last </em>in the list. This is because the software will know to prompt users for a justification when they attempt to “downgrade” sensitivity (if you have enabled that option).</p><p>Some prefer to include a <em>Highly Confidential</em> label as well; the distinction between <em>Confidential </em>and <em>Highly Confidential </em>is where I find most people get confused (so I just leave it out). If you do choose to implement both of these higher-sensitivity classifications, I suggest making a clear distinction for end users. For example, data that should absolutely <em>not </em>be shared externally under any circumstances, even accidentally. Every org possesses at least some data that would be considered “toxic” or very bad if it were to leak. <em>That </em>is what you want to reserve your highest sensitivity for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Mm1HDUpD4Wp_wlJ0" /></figure><p>You can also have “sub-labels” and these will work much in the same way: you want to go in order from widest audience/least restrictive settings at the top, to most private/more restrictive at the bottom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TPFUhIqd_zwknME-" /></figure><p>I will describe how I configure these “starter” labels, but first we have to do a little work to set the stage.</p><h3>Step 1. Prepare for labels</h3><p>Before you even create your first label, go and turn on labels for OneDrive and SharePoint so you can have these superpowers available in the web as well as the client apps (note there can still be <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/sensitivity-labels-sharepoint-onedrive-files?view=o365-worldwide#limitations">limitations</a> when using them online). From the <strong>Compliance center</strong> ( <a href="https://compliance.microsoft.com/">https://compliance.microsoft.com</a>), go to <strong>Information protection </strong>and find the yellow banner, then click <strong>Turn on now</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ch7H7IlT8voBwdIt" /></figure><p>You must also enable labels for <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/sensitivity-labels-teams-groups-sites?view=o365-worldwide#enable-this-preview-and-synchronize-labels">Groups and Sites</a> so that you can classify containers like Teams and SharePoint Sites rather than just files. You can use <a href="https://github.com/vanvfields/Microsoft-365/blob/master/Azure%20AD/Enable-SensitivityLabelsForGroups.ps1">this PowerShell script</a> to get that done quickly.</p><p><em>Note: You must have the </em><a href="https://www.powershellgallery.com/packages/AzureADPreview/"><em>Azure AD Preview PowerShell module</em></a><em> and the </em><a href="https://www.powershellgallery.com/packages/ExchangeOnlineManagement/"><em>Exchange Online Management PowerShell module</em></a><em> installed in order to run that script; and yes, you will be prompted to sign-in twice, as you must connect both to Azure AD and the Security and Compliance center.</em></p><h3>Step 2. Plan Settings for Groups and Sites</h3><p>If you ran the script, then when you go to create or modify your labels you will notice that you have the option to configure settings for labels when they are applied to <strong>Files &amp; emails</strong>, and also when they are applied to <strong>Groups &amp; sites</strong>. Let’s start by planning our settings for the latter, first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VPNPli2w5Ly4oiDy" /></figure><p>For <strong>Groups &amp; sites</strong>, I recommend publishing the “top level” of labels only (do not configure any Group/Site settings on your sub-labels). There are not that many different settings to manipulate for Groups and Sites, so there should be no reason to have a large multiplicity of labels here. Not to mention, it just <em>looks </em>cleaner in apps like Teams (for some reason they don’t have a great way to display the sub-labels yet and it just looks awful).</p><p>Here is what I recommend using for settings:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/0*lMYcv1FGdZgRJKPJ" /></figure><p>Simply edit each of the labels, and proceed through the wizard, indicating that you want to configure settings for <strong>Groups &amp; sites</strong>. Then make the selections indicated in the table.*</p><p>Again, if you choose to implement <strong>Highly Confidential</strong> as a further privacy distinction, then the “no external sharing” line would generally be drawn at that last label. In that case I would still allow external users for <strong>Confidential </strong>groups &amp; sites, but restrict the site’s sharing settings so that everyone has to authenticate (e.g. New and Existing guests, or Existing guests only) and therefore we will always have an audit trail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*27sErCXfInmHzigi" /></figure><p>* <em>Note: in my experience, many organizations have not yet adopted Intune and Device Compliance via Conditional Access, therefore I would not include</em> <em>the Conditional Access settings such as Limited web access or Block access until the device on-boarding has been completed. However, check out the new integration with </em><a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/sensitivity-labels-teams-groups-sites?view=o365-worldwide#more-information-about-the-dependencies-for-the-authentication-context-option"><em>Conditional Access authentication context</em></a><em>; this would allow you to require stronger access controls for sensitive groups and sites.</em></p><h3>Step 3. Plan Settings for Documents and Email Messages</h3><p>Next we should define the settings that we want to apply to Files &amp; Emails. Here I am only going to define settings for the sub-labels, not any of the top-level labels (the top-level labels can still be applied to files, it just doesn’t do anything special like encryption or content marking). You can of course choose to do things differently; this is just my “starter kit” approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/0*-HF16UjB9BtKtdG4" /></figure><p>The <em>External </em>sub-label can be used to share protected (read: encrypted) files and email messages with any user inside or outside the organization, including guests who sign-in with a one-time passcode. In Outlook, this has a similar effect to the Encrypt-Only template.</p><p>The <em>Internal </em>label, by contrast, can only be shared with individuals <em>inside </em>the organization. Even if a file or message were to be accidentally sent to the wrong person (external to the org), that recipient would not be able to open and work with the data.</p><p>I include the Recipients Only (Do Not Forward) option just so that users have the ability to send messages that can be read and replied to, but not forwarded, copied, or printed. So some additional restrictive permissions get applied to the message and attachments in that case (this label is only available in Outlook).</p><p>You can optionally include another level above <em>External </em>called “ <em>Anyone</em>” or “ <em>Not Protected</em> “ which does not apply any encryption, but perhaps still maintains a header marking or similar. This would make it easier to share certain confidential information, as it does not require the end user to authenticate in order to read the document or message. If that describes a use case in your org, then by all means you can add another sub-label and promote it up to the top of the list under “Confidential.”</p><h3>Step 4. Publish the labels</h3><p>Once you have the labels all created according to your plan, you can publish the labels using a label policy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/0*MnnZZhzaUeA5g7Qv" /></figure><p>I keep this as simple as possible, and just assign all labels to all users. Policy settings are up to the organization’s preference. Remember: if you later added more classifications such as Highly Confidential or Top Secret, you can always publish those with another policy at that time (and sometimes a new label might only be published to a specific group of people, e.g. “Management team”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VKts_0Y818Y-ea98" /></figure><p>For example, I generally always require users to provide justification to remove or downgrade a label. Optionally, you can set a default label for files and emails, as well as for groups and sites. Or alternatively choose to <em>require </em>a label for each (personally I would not implement both of those options: either apply a default label or require a label, but not both). Requiring labels can be a good path for the SMB, where most will not have access to automatic labeling (a feature locked behind the more expensive E5 subscription). This will force users to pick a label for any file created or modified moving forward.</p><p>You could also provide a “help page” for users (just use a Communication site in SharePoint), which can be a nice touch and give them a place to go for more detailed descriptions of each classification along with some examples. The same site can be used to communicate other policies such as Data Retention, Personal Mobile Device Policy, and so on. And that brings us to the final step!</p><h3>Step 5. Train users (a.k.a. data owners)</h3><p>The step that everyone forgets!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4DVKB2k_Qv_YpHjJ" /></figure><p>If you do not train your end users, then your implementation will fail. Success is measured by adoption! Data Protection is the responsibility of <em>all </em>members in an organization. We can implement some technical “stuff” like labels and label policies to make the task easier, but at the end of the day the responsibility falls on your people. They need to understand the importance of data classification, and protecting sensitive information in particular.</p><p>I recommend that you offer live instruction (can be done over Teams) with Q+A time at the end, and be sure to offer it multiple times to catch different schedules. Record the events for playback. Then update/refresh the training annually. This can be one part of a larger <strong>Security Awareness and Skills Training Program</strong> (Critical Security Control #14).</p><h3>Conclusion</h3><p>This is obviously a very simple classification scheme, but that is why I love it so much. Most SMB’s that I work with have no experience with Data Classification at all, and currently have trouble separating sensitive from non-sensitive or internal from external datasets easily. They would normally rely on segmenting data by containers and ACL’s in the past, which certainly has its limits in today’s modern workplace.</p><p>The “starter” set of labels that I have laid out above dramatically improves the situation for any SMB with limited cybersecurity or compliance resources, and is pretty easy to adopt, as well. In some orgs, there will be more compliance requirements which may suggest more or different labels, but this is a really good first step.</p><p>Later this year I will launch a Data Protection Starter Kit. This product will include scripts, written guides and policy templates, training decks with example video instruction, and Statements of Work to implement several Data Protection and Data Governance features in Microsoft 365, of which Sensitivity Labels will be just one aspect.</p><p>When it launches, I will be sure to announce it. Stay tuned.</p><p><em>Originally published at </em><a href="https://www.itpromentor.com/simple-sensitivity-labels/"><em>https://www.itpromentor.com</em></a><em> on June 11, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=142097eb5f7d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/simple-sensitivity-label-design-for-the-smb-142097eb5f7d">Simple Sensitivity Label design for the SMB</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Updates to the CIS Controls and Free Microsoft 365 Assessment Workbook]]></title>
            <link>https://medium.com/re-office-365/updates-to-the-cis-controls-and-free-microsoft-365-assessment-workbook-1702cd7c074d?source=rss-7202e9f16eb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1702cd7c074d</guid>
            <category><![CDATA[cis-controls]]></category>
            <category><![CDATA[free]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[assessment-tools]]></category>
            <dc:creator><![CDATA[Alex Fields]]></dc:creator>
            <pubDate>Thu, 20 May 2021 14:33:44 GMT</pubDate>
            <atom:updated>2021-05-20T15:11:14.314Z</atom:updated>
            <content:encoded><![CDATA[<p>I know my community is already familiar with the CIS Critical Security Controls, as well as the <a href="https://www.itpromentor.com/cis-controls-4m365/">free assessment workbook</a> that I adapted from <a href="https://www.auditscripts.com/free-resources/critical-security-controls/">AuditScripts</a> to apply to Microsoft 365 environments. This week, the Center for Internet Security released updates to the framework (we are now on v8). You can <a href="https://www.cisecurity.org/controls/v8/">download the new controls here</a>, and if you want to see the recent webinar covering these updates, <a href="https://cisecurity.wistia.com/medias/9qnuy1s5vb">go here</a>.</p><h3>Updated for Cloud</h3><p>This is a particularly important update for Microsoft 365 customers, and any cloud-first, mobile-first organization who operates primarily out of SaaS-based applications. Why? Because one of the goals with v8 was to modernize the Critical Security Controls for this type of environment! The result is surprising!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L1bAtbpcc8FEVFDV" /></figure><p>That’s right! We actually have <em>fewer </em>controls; the list has shrunk from 20 to 18. What happened? Well, a number of the controls that pertained to legacy network and server infrastructure have been collapsed (e.g. Limitation of Ports and Protocols, Secure Configuration of Network Devices, Boundary Defense, Wireless Access Control). It is not that these have been completely discarded, but in some cases the sub-controls (now referred to as “Safeguards” in v8) have just been moved under new headings such as Network Infrastructure Management. We also have a brand new control (#15) covering Service Provider Management, to address all the cloud services that we have to manage these days!</p><h3>A New Emphasis on Data Protection and Identity + Access Control</h3><p>One really significant difference I want to highlight is the re-ordering of certain controls. The CIS framework prioritizes the list of Safeguards for you; so the logic goes that you must establish inventory and control of hardware assets (#1) and software assets (#2) before you can proceed to later steps (you cannot protect what you don’t know you have). Therefore the first two controls have not really changed much; what is more noticeable is that Data Protection has been advanced all the way up to #3 on the list!</p><p>Establishing a secure configuration for devices and applications has moved up to #4 (previously #5) and now we have Account Management in position #5, and Access Control Management at #6. Therefore <strong>Identity </strong>has moved up the scale as well (some of these identity-related Safeguards were located way down in control #16 previously).</p><p>If you think about the tools that are included with Microsoft 365 Business Premium and Enterprise plans, and specifically within the Enterprise Mobility + Security suites, you will see how well Microsoft tracks with the “cloud-first” updates to this framework. Microsoft Endpoint Manager (Intune) and Azure AD Conditional Access can help you accomplish control of hardware and software, secure configuration, and strong authentication and access controls. Azure Information Protection can cover most of the requirements under Data Protection.</p><p>But I should also highlight that Microsoft 365 cannot address <em>every </em>Safeguard within the new control framework. In fact, pretty much everything from #11 on down to #18 would require working <em>outside </em>the Microsoft 365 suite of tools (and some of it is policy &amp; procedure, versus some kind of technical control or feature, anyway).</p><h3>No More Categories (Focus on the Implementation Groups!)</h3><p>In version 7, we still had “Categories” such as Basic, Foundational, and Organizational. That concept is now retired, and there is more emphasis placed on the <strong>Implementation Groups</strong> which were first introduced in v7. Implementation Group 1 ( <strong>IG1</strong>) is a “Basic Cyber Hygiene” or “Baseline” set of Safeguards for any Small or Mid-sized Enterprise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L176zwf3c40ppiOa" /></figure><p>Interestingly, even though we have fewer controls overall, we have more Safeguards within IG1 (previous version had 43 sub-controls, we are now at 56). However, if you are a Managed Services Provider, you should be looking to adopt IG2 or even IG3 for your own organization. Why? Because you manage a lot more complexity and may have differing risk profiles among your customer base (see the description for IG2). Not only that, but you are a bigger target for more advanced attacks (e.g. the recent Solorigate supply chain attack). That having been said, most of your <em>customers </em>will probably benefit greatly just by adopting IG1.</p><h3>Conclusion</h3><p>I participated in a recent <a href="https://www.youtube.com/watch?v=jzQO8Bd_MR0">webinar with Acronis</a>, and one of the questions from the audience was, “ <em>Where does the responsibility of the MSP end the responsibility of the MSSP begin?</em>” Today these are still (potentially) separate entities, but in my view, that distinction cannot continue for very long. It is past time to open our eyes to the sharp increase in advanced attacks that we have seen against MSP’s and other IT vendors. If you are not on your way to implementing a formal framework such as CIS or NIST CSF to a pretty high degree within your own business, then it is unlikely you will still be <em>in </em>business 5 years from now. You can outsource some MSSP functions of course: detections, Incident Response and so on, but however you build it, you have to be ready to offer a <em>full </em>spectrum cybersecurity solution to your customers. There is no room for “Bronze/Silver/Gold” packages here: everyone gets advanced security, full stop.</p><p>Now, if you stuck with me to the end of this article, here is your reward: the <a href="https://itpromentor-my.sharepoint.com/:x:/p/alex/EfQLU2Ysc7JBuU5itZLOu_cB91GuPTe1_u1hpCtkZ7pVKw?e=6RITZQ">updated Assessment Workbook for Microsoft 365</a>. This tool contains all the Safeguards from the CIS Controls IG1. As a bonus, I am also including a worksheet for the Australian Cyber Security Centre’s <a href="https://www.cyber.gov.au/acsc/view-all-content/publications/strategies-mitigate-cyber-security-incidents">Strategies for Mitigating Cyber Security Incidents</a> (this is the larger framework from which the <a href="https://www.itpromentor.com/essential-8-microsoft-365/">Essential Eight</a> is derived).</p><p><em>Originally published at </em><a href="https://www.itpromentor.com/cisv8-assessment-tool/"><em>https://www.itpromentor.com</em></a><em> on May 20, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1702cd7c074d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/updates-to-the-cis-controls-and-free-microsoft-365-assessment-workbook-1702cd7c074d">Updates to the CIS Controls and Free Microsoft 365 Assessment Workbook</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Choosing (and implementing) your strategy for personal devices]]></title>
            <link>https://medium.com/re-office-365/choosing-and-implementing-your-strategy-for-personal-devices-ced8925fcb82?source=rss-7202e9f16eb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ced8925fcb82</guid>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[endpoint-security]]></category>
            <category><![CDATA[microsoft-intune]]></category>
            <category><![CDATA[microsoft-365-business]]></category>
            <category><![CDATA[byod]]></category>
            <dc:creator><![CDATA[Alex Fields]]></dc:creator>
            <pubDate>Fri, 16 Apr 2021 17:13:12 GMT</pubDate>
            <atom:updated>2021-04-16T17:19:22.692Z</atom:updated>
            <content:encoded><![CDATA[<p>In a <a href="https://www.microsoft.com/security/blog/2021/04/13/secure-unmanaged-devices-with-microsoft-defender-for-endpoint-now/">recent Microsoft blog</a> announcing some cool new discovery features in <a href="https://techcommunity.microsoft.com/t5/microsoft-defender-for-endpoint/endpoint-discovery-navigating-your-way-through-unmanaged-devices/ba-p/2248909">Microsoft Defender for Endpoint</a>, there is an interesting (but hardly surprising) statistic shared: your users are 71% more likely to be infected on an unmanaged device.</p><p>Now the thrust of the article is around discovering assets in your environment that are not yet being managed and exposing them, so that you can more easily remediate (even automating that remediation in some cases). Obviously these are all E5 features targeted heavily toward the Enterprise, but the message should not be lost on those of us in the SMB space. <a href="https://www.itpromentor.com/endpoints-matter-1/">Device management</a> is not something you should ignore.</p><p>In my personal experiences serving the SMB and helping others who are doing the same, right now the largest concern is around personal devices. Not just mobile devices, but also laptops and desktops, especially after last year’s Mass Exodus from the office, and dramatic shift toward working from home (or you know, wherever… for example, I just got back from spending a couple of months at a remote ranch in the southwest U.S.).</p><p>Anyway, to that end, I think it is massively important for us to be reaching out to our customers and really highlighting this problem. We have many options for reducing risk when it comes to personal devices, even in the Business Premium subscription:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5J-Lw4WnnAV3b66z" /></figure><p>Obviously the least amount of risk (far right side of this image) would mean blocking all access on personal devices. This may not even be feasible for some SMB customers, of course. We are seeing year-over-year increases in demand for BYOD, and after the pandemic lock downs kicked in last year, this number increased suddenly and dramatically. The speed with which we were forced to react to these new demands meant that we did not always have time to address security concerns in making this transition work, and work quickly.</p><p>So if you haven’t yet, please circle back around with your customers and revisit this issue. Even after folks return to pre-pandemic conditions and habits, I suspect there will still be many lingering personal devices out there that are unmanaged and connecting to corporate data and resources.</p><h3>What do I recommend?</h3><p>As regards the other options for management (which still allow for access to company apps and data), we have:</p><ul><li><strong>MAM </strong>— Allows for client app access but provides very little in terms of device-based security or controls</li><li><strong>MDM </strong>— Also allows for client app access and provides more capabilities (e.g. push your endpoint security policies and agents down to the devices)</li><li><strong>Limited web-only access</strong>: Does not allow client app access, and prevents data (e.g. email attachments, OneDrive files, etc.) from being downloaded over the web.</li></ul><p>My personal favorites right now are MAM for mobile devices, and MDM for MacOS/Windows 10 laptops and desktop computers. MAM for iOS and Android technically still gives us “Conditional Launch” settings for the applications whereby the app will not launch if the device is jailbroken or rooted, or cannot meet a minimum OS level. You can even <a href="https://techcommunity.microsoft.com/t5/intune-customer-success/microsoft-defender-for-endpoint-risk-signals-available-for-your/ba-p/2186322">integrate MAM with Defender for Endpoint</a> now, so that the threat level on the device can prevent application launch.</p><p>We do not have equivalent capabilities with MAM on Windows (and zero MAM capabilities on MacOS). Therefore, I still lean toward MDM for laptops and desktops, so that we can further reduce risk through device-based controls and pushing our security software/agents down. As well, we still see more threats such as malware and ransomware on laptops and desktops that lead to major incidents and business disruption. I have not personally come across similar for mobile devices yet (not to say these things don’t exist, I just haven’t heard of it yet in the customers that I serve).</p><p>So for now that is where things stand for me.</p><h3>Setting up your preferred option</h3><p>Most folks still do not set up the various options correctly in Microsoft Endpoint Manager, so let us cover off on the configuration for each quickly.</p><h4>Enrollment restrictions</h4><p>The first decision that comes to bear on these options is whether to allow personal devices to be enrolled with the Intune service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PmrsnCPzD3GDKPV-" /></figure><p>If you are choosing to go with the MAM option, or the web-only option, you would need to configure the Device enrollment restrictions to <strong>Block </strong>personal device enrollment. Do this from <strong>Devices &gt; Enroll devices &gt; Enrollment restrictions</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Cjjr0mFOS9YvbMuE" /></figure><p>You can either edit the default ( <strong>All Users</strong>) Device type restrictions policy, or you can <strong>Create</strong> your own restriction policy for specific users and groups. For example, you might have different restrictions defined for different types of workers (frontline, Ops, etc.).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/0*O0gfAIhoAAl_n2ka" /></figure><p>Pro tip: If you choose to target individual users and groups, then be sure to also edit that Default policy and set all the platforms to <strong>Block </strong>for personal enrollment (so that you are only explicitly allowing it for specific groups). That way someone doesn’t slip through the cracks if they don’t belong to one of the other defined user groups.</p><h4>Autoenrollment settings</h4><p>The next item up is <strong>Autoenrollment</strong>. This applies to Windows 10 in particular. You can set up “autoenrollment” experiences for other device platforms (e.g. Apple Business Manager for Company-owned iOS devices), but for Windows 10 we have a choice to make between asking devices to be managed by MAM-only or MDM.</p><p>Windows MAM policies turn on a feature called <a href="https://www.itpromentor.com/wip-done-right-1/">Windows Information Protection</a>. These policies, in my opinion, are not that great for unmanaged devices. But you can still apply the MAM policies if you want to, even if the device is being managed. And, since managed devices allow us to do slightly better with these policies (e.g. protect non-enlightened apps), I would argue there is no good reason not to enroll for MDM (even if you want to use Windows Information Protection on top of that).</p><p>Anyway, navigate to <strong>Devices &gt; Enroll devices &gt; Windows enrollment &gt; Automatic enrollment</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7pQAj-hoHDuIbOYB" /></figure><p>There are two ‘scope’ options here; one is for MDM and one for MAM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1023/0*o40XqYzharu6Aof7" /></figure><p>Here is the meaning of these scope options:</p><ol><li>If you configure only the MDM scope, then the users you target with that policy will automatically go down the MDM enrollment path when they Azure AD Join (corporate) or Azure AD Register (personal).</li><li>If you configure both the MDM and MAM user scope, then the users who are targeted in the MAM scope will automatically go down the MAM enrollment path instead of MDM on<strong> personal devices only</strong>. Corporate devices (Azure AD Join) will always prefer the MDM enrollment over MAM.</li></ol><p>Therefore, as you can probably guess, I never configure the MAM scope (because I push all my customers toward full management via MDM).</p><h4>Intune policies</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5Oa0Jkh_2ValRtM2" /></figure><p>After the autoenrollment is done then it is time to set up the policies that will enforce your desired settings. For MAM, this means deploying App Protection policies (these are your MAM policies). Find them from <strong>Apps &gt; App protection policies</strong>. When you work with Windows 10, you can deploy these <em>Without enrollment </em>(just MAM and no MDM) or <em>With enrollment</em> (when you also leverage MDM for management).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aC7MBZQjX-HY3w9v" /></figure><p>When you go down the MDM path, as I recommend especially for Windows and MacOS, then you need to define at minimum a <strong>Compliance policy</strong> ( <strong>Devices &gt; Compliance policies</strong>) that will measure whether the device meets certain requirements that you get to define, such as minimum OS, antivirus, firewall, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bigdYs1xSHEMddXS" /></figure><p>Optionally you can enforce other settings and profiles on the device, but a compliance policy is the minimum. And note: Windows 10 devices should be at least <strong>Pro</strong> (no home editions) whether you are doing MAM <em>or </em>MDM.</p><h3>Conditional Access</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IuUtVeskrizAwo5p" /></figure><p>Last move to <strong>Devices &gt; Conditional Access</strong>. When you are enforcing MAM, you should at least require <a href="https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/howto-conditional-access-policy-all-users-mfa">Multi-factor Authentication (MFA)</a>. You may also want to require the users to accept a <a href="https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/terms-of-use">Terms of Use</a> describing the company’s policy around corporate information on personal devices, although this is optional. And, when you are targeting MAM against mobile devices (iOS and Android only), then you can also <a href="https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/app-based-conditional-access">enforce the use of managed applications</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PKqmVUNKRu1stfE5" /></figure><p>Skipping over MDM for the moment, to enable the limited web access option, we have a ‘ <strong>Session</strong>’ access control called <a href="https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/concept-conditional-access-session#application-enforced-restrictions">App enforced restrictions</a> and a couple of commands that you need to run via PowerShell: one for <a href="https://docs.microsoft.com/en-us/sharepoint/control-access-from-unmanaged-devices#limit-access-using-powershell">SharePoint and OneDrive</a>, and the other for <a href="https://aka.ms/owalimitedaccess">Exchange Online</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3OfgX171l_5jILu9" /></figure><p>A warning about this: when you run the commands for SharePoint Online it automatically creates CA policies for you <strong>and enables them</strong>, which I find sort of annoying. Exchange Online does not do this. (So you have to go create a policy anyway; I wish this was consistent behavior between SPO and EXO. I prefer to create these policies myself, so that would be my vote, and just give us a little reminder in the PowerShell output after running the command, or if you are going to autogenerate policies then leave them disabled for crying-out-sideways).</p><p>Now when it comes to MDM, you would want to enforce device compliance for <em>at least</em> mobile app and desktop client access (since these apps sync data to the local device). You can optionally choose to target browsers as well under <strong>Conditions &gt; Client apps</strong> in your policy. And if you are <em>blocking </em>personal device enrollment and you only want corporate owned and managed devices to access the cloud apps and data, then you would need to choose both client apps and web browsers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ln6yqklG8nzq9RnX" /></figure><p><em>Aside: You can import my </em><a href="https://github.com/vanvfields/Microsoft-365/blob/master/Azure%20AD/Baseline-ConditionalAccessPolicies.ps1"><em>recommended baseline conditional access policies </em></a><em>to ease this work and make the policy creation more repeatable with less chance for error</em>.</p><h3>Conclusion</h3><p>In the E5 subscription we technically have even more options with Microsoft Cloud App Security and <a href="https://docs.microsoft.com/en-us/cloud-app-security/proxy-deployment-aad">Conditional Access App control policies</a>, but most SMB’s will be well served even without those options, and sticking to the ones we discussed here.</p><p>I wish I didn’t have to harp on this point so much but I hear from folks all the time who get themselves into bad situations because they ignored device management. I have personally been called to help on two different incidents since the start of the pandemic where a personal device was the initial entry-point for an attacker. And if you have ever worked on incident response, you know that one of the most frustrating parts of the job is needing to fix visibility issues before you can even start the <em>real </em>IR work. When sh*t hits the fan, as they say, we defenders <strong>much</strong> prefer to have the proper tools in place <em>before </em>we get started on response and clean-up efforts. It adds a lot of cost, uncertainty, and extends business interruption when we do not have an accurate inventory from the start. And remember that statistic from Microsoft: you are much less likely to be infected on a managed device anyway, so go out and get this stuff done with your customers. It’s good money, and good work.</p><p><em>Originally published at </em><a href="https://www.itpromentor.com/personal-device-options/"><em>https://www.itpromentor.com</em></a><em> on April 16, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ced8925fcb82" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/choosing-and-implementing-your-strategy-for-personal-devices-ced8925fcb82">Choosing (and implementing) your strategy for personal devices</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Moving to Microsoft 365 means getting to know your data (and your business)]]></title>
            <link>https://medium.com/re-office-365/moving-to-microsoft-365-means-getting-to-know-your-data-and-your-business-c803ddf50dd5?source=rss-7202e9f16eb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c803ddf50dd5</guid>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[microsoft-365-migration]]></category>
            <category><![CDATA[data-governance]]></category>
            <category><![CDATA[file-server]]></category>
            <category><![CDATA[data-migration]]></category>
            <dc:creator><![CDATA[Alex Fields]]></dc:creator>
            <pubDate>Fri, 02 Apr 2021 13:06:00 GMT</pubDate>
            <atom:updated>2021-04-06T20:13:02.821Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Rw03A56Yk_lhFJGu" /></figure><p>Through my website’s <a href="https://www.itpromentor.com/contact/">contact form</a>, I still hear about botched migrations to Microsoft 365 on a regular basis. This is usually due to exactly one problem: ignorance about the process, as well as ignorance about the datasets being migrated, as well as ignorance about the various tools that we have in Microsoft 365. All of this ignorance translates to pain that was 100% completely avoidable. The <em>pain</em> is what I most often hear about when people come to me asking if they can hire my help to clean up a mess that they themselves created.</p><p>What’s worse, I fear, is what I <em>don’t </em>always hear about. There are plenty of folks out there who already think they are the smartest people in the room ( <em>but do they realize how large of a room </em><strong><em>the world </em></strong><em>is?</em>); so when they attempt to implement one of these solutions for themselves or their customers and they have a bad experience, they ultimately conclude that it was the <em>software</em>, and not them, that was the problem. This preserves their image in the eyes of the customer, and of course reinforces their own “self illusions.” I see evidence of this phenomenon in several circles/groups online. They will sometimes even get validation from others who are likewise ignorant and had a similar experience. It is difficult to help these folks (they obviously don’t need it).</p><p>But I can still help some of the <em>other </em>people. You know: the ones who remember that there is always someone out there who knows more about something than they do.* Anyway, for <em>those</em> individuals, I am going to host a <a href="https://squareone365.teachable.com/p/april-2021">two-part live instruction class</a> on <em>properly </em>preparing for and migrating data to Microsoft 365. This includes some key governance decisions as well as notes on end-user adoption strategies.</p><p>But look, I have written volumes about this topic on this website already, so you might be able to just glean what you need that way. I recommend <a href="https://www.itpromentor.com/five-rules-of-fields/">starting here</a>. No pressure to join this class or anything. And to members of my <a href="https://squareone365.teachable.com/p/microsoft-365-practice-development">Practice Development group</a>: you already have access (this is a topic that was picked by the group).</p><p>Today I just want to emphasize one important piece of the puzzle, and explain why I think a lot of migrations go poorly.</p><h3>The magic no longer happens ‘behind the curtain’</h3><p>For more than two decades now, migrations have been done “behind the curtain” so to speak. What do I mean by that? Well, up until now, the person moving the data did not need to know anything about the data they were moving. It was not required to have any knowledge about the data inside the file shares, for instance, or the various shared mailboxes and public folders inside of an Exchange database. Users would just be told to stay off the network, and expect a short interruption while data was copied or moved over the weekend. And when they come in on Monday, the job would be done; the magic all happened behind the IT curtain.</p><p>The IT folks just had to understand the <em>infrastructure </em>that supported the existence of these things. They knew how to move a mailbox or a file share using tools like EAC, PowerShell, Robocopy, or whatever. And that was all fine and good.</p><p>But if you are moving from old-world infrastructure into a brand-new modern cloud-based information system, knowledge about the <em>data </em>is much more important than knowledge about <em>tools</em>. That having been said, you also need to understand the limitations of the new architecture and the tools that support it. For example, do not attempt to put all of your files into a single library (a common mistake). We have different repositories for different types of data now, and we are moving toward a flatter, wider structure in general, rather than a hierarchy that is nested and deep.</p><p>So the fact that we are moving into an alien-seeming structure means that we have to spend more time learning what it is that end users are doing day-in and day-out. By doing so, you will be able to guide the movement of this data into the most appropriate place in the cloud. What used to take place inside a Public Folder database might live in an Outlook Group (or even in Teams) for example. What used to show up as a drive letter might make more sense now as a library in a Communications site, or as files within a Teams channel. <a href="https://www.itpromentor.com/how-to-customize-permissions-in-teams/">It depends</a>.</p><p>Understanding the data <em>structure </em>and the <em>purpose </em>of various datasets is therefore more important than which tool you ultimately choose for copying data (and there are a lot of good ones out there now).</p><h3>The future is bright</h3><p>But this implies you can no longer spend your days hiding out in the server closet. You have to go mix and mingle with the general user population, and get to know what it is they do, and the challenges they face as they attempt to adopt all these strange new tools like Microsoft Teams, OneDrive for Business, or SharePoint Online. The key point is that both groups have something to learn from each other in this exchange: the users need to learn about the new technology, and IT needs to learn more about the data (specifically the business context in which that data is showing up).</p><p>Having a better understanding of ‘what is out there’ will also come in handy as you apply governance and help the organization to make decisions on how they want to customize their environment and meet compliance requirements. So unlike migrations from file server A to file server B, or whatever Exchange version to vNext, this <em>should</em> be a much more engaged migration that involves more players and helps the IT department or Service Provider get to know their customers better. It is a win-win situation, and done right the exercises will help build more trust and mutual understanding, <em>and </em>open more opportunities to add value in the future.</p><p><em>*I am also not suggesting that I’m Mr. Know-It-All here. Perhaps in some limited areas, yes. But there are plenty of topics that I know very little about, and therefore, even I must look to the experts. For example, almost everything in the real world that doesn’t involve sitting in front of a computer.</em></p><p><em>Originally published at </em><a href="https://www.itpromentor.com/get-to-know-data/"><em>https://www.itpromentor.com</em></a><em> on April 2, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c803ddf50dd5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/moving-to-microsoft-365-means-getting-to-know-your-data-and-your-business-c803ddf50dd5">Moving to Microsoft 365 means getting to know your data (and your business)</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[There is no panacea, there is no silver bullet]]></title>
            <link>https://medium.com/re-office-365/there-is-no-panacea-there-is-no-silver-bullet-5577fb4a88bf?source=rss-7202e9f16eb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/5577fb4a88bf</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[microsoft-365-business]]></category>
            <category><![CDATA[sensitivity-labels]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <dc:creator><![CDATA[Alex Fields]]></dc:creator>
            <pubDate>Tue, 09 Mar 2021 13:35:46 GMT</pubDate>
            <atom:updated>2021-03-30T06:31:40.222Z</atom:updated>
            <content:encoded><![CDATA[<p>I had a really interesting question come up during one of my recent <a href="https://www.itpromentor.com/courses/">online courses</a>. One of the participants asked whether device management, and even MAM (application-based management) were necessary anymore, now that we have stuff like MIP and <a href="https://www.itpromentor.com/behold-the-power-of-labels/">Sensitivity Labels</a>. I was taken aback by this question and I think that it is important to address it more thoroughly and for a broader audience.</p><p>Actually, I have been seeing this idea crop up in some other places as well, though sometimes under slightly different context. For example, some MSP’s out there are selling some flavor of a hosted VDI solution, whether via WVD, VMware, or whatever, and they often tell their customers (foolishly) that they should just use whatever endpoints they want to connect to the remote environment, and that they do not need to manage those endpoints. Users’ physical devices, they suggest, are basically disposable, and have no meaning since “everything is secured in the cloud.”</p><p>In my opinion, any provider who tells you something like this is either just dangerously ignorant, or they are being highly irresponsible with their service and their customer’s data. Or most likely, both. These examples here (the Sensitivity labels and the VDI provider), are basically coming down to the same error: they assume that some particular solution is <em>the</em> solution and that nothing else is needed to ensure the Confidentiality, Integrity, and Availability (CIA) of the business services and information.</p><p>But if that were really true then we could all just stop implementing any cybersecurity or compliance frameworks because hey, we already bought/implemented this one product so, you know, we’re good! Let’s just shut down NIST, CIS, CISA, CCCS, NCSC, ACSC and any other organizations out there dedicated to keeping our infrastructure and data safe.</p><h3>Layered approach to security</h3><p>But of course, we don’t live in a fantasy land. We live in the real world, so it turns out that no one product or solution can really cover every single concern or scenario. When you look at a big bundle such as Microsoft 365, which includes many different security products, even if you really took the time to implement every single feature, would you be 100% safe? No. You can never be 100% safe. Only saf<em>er</em>. This is as true in cybersecurity, as real life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L591pQ2SuiLVFWcd" /></figure><p>One way we can easily demonstrate this is by considering the diagram above. We have many layers to consider in our cloud-based information services architecture. We have the identity layer (and MFA is still our best defense for identity-based attacks), then the service layer (such as Office 365 Exchange Online), and then we have devices which connect to that service, and client applications as well as data (data may live in the service but it can also be synced or downloaded via a browser or client app). If an attacker can successfully infiltrate any one of those layers they have a shot at achieving their ultimate goals.</p><p>Microsoft 365 bundles are mindful about providing us with some safeguards/protections for each one of the major layers. And implementing more of them will certainly help you to meet certain compliance requirements or security controls, reduce risk, and so on. But to be clear, there is no such thing as a silver bullet. Even in the Mighty Microsoft 365.</p><h3>How hackers are wired</h3><p>Many times you are protecting against different risks at different layers. But for example, a sensitivity label will not protect you if your identity is compromised, or if your device is compromised. When you work with the data, it is <em>un</em> encrypted and exposed. If there is an attacker dwelling on your device, they can see what you see. Or, consider stuff like Windows Information Protection, Attack Surface Reduction, or even full AppLocker (whitelisting). Did you know that these safeguards can be bypassed if an attacker has local administrator rights on the machine?</p><p>It goes on and on. Even the <a href="https://www.microsoft.com/security/blog/2019/10/03/password-doesnt-matter-mfa-does/">often-boasted effectiveness of MFA</a> will be eroded over time as attackers find new ways around it. Already, I have seen instances in the wild this past year where an end user was tricked into granting access even with MFA enabled for their account.</p><p>You have to understand how hackers are wired; they aren’t like most people. And I use the word <em>hacker</em> here and not <em>attacker </em>because the good guys do this stuff too and thereby help to make our systems even better. Anyway, when a hacker runs into some barrier, they don’t just throw up their hands and say, “<em>Oh well, I guess they got me.</em>” No. They pivot, and find a new way. “<em>There is always another way</em>,” could be a good mantra for these types.</p><p>But again, you can likewise always find ways to reduce your risk, and, the saying goes, you make yourself a more expensive target in the process. Even the bad guys are “on the clock” so to speak, and they have to be practical about how they spend their time earning that dishonest paycheck. If the payout does not seem likely to match the effort, they will eventually move on to the next target.</p><p>Plus, wouldn’t you at least want to <em>try</em> and implement <em>something </em>rather than nothing? Sure, an attacker might trick someone into helping them past this barrier or that, but it is still a barrier nonetheless, and oftentimes the barriers will hold, or one will hold even while another crumbles. In fact, I argue that a well-designed system following a solid framework is better because you end up pairing many of these protections together. For example, at the <em>human </em>layer you will want a security training program to reduce the chances of someone being tricked in the first place. So you can thereby reinforce protections you have implemented at other layers.</p><h3>Back to Sensitivity Labels</h3><p>I think I made my larger point here, so now let’s talk about this question of Sensitivity Labels. Yes, as I have mentioned before, <a href="https://www.itpromentor.com/behold-the-power-of-labels/">they can be a powerful tool</a> in your arsenal, but they do not, and cannot, replace your device management strategy. In fact, in some ways they <em>complement </em>a modern device management framework. For example, one of of the functions of a Sensitivity label when applied to a Site, Group or Team is that you can block downloads on unmanaged computers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NfxorvCqe4JPbFgK" /></figure><p>Or, consider Microsoft Cloud App Security: using this tool, we can choose to apply labels <em>only </em>if they are being downloaded to an unmanaged computer. <em>But why not just encrypt ALL the data?</em> <em>Couldn’t we just let the data fly around to any old device once it is encrypted?!</em></p><p>Again, encrypting files does not meet every cybersecurity control or protect you from every threat. There are reasons you may want to prevent certain files from being distributed and proliferated on outside devices, whether encrypted or not. By the same token, there are reasons you might not want to apply labels that encrypt data in every circumstance. When a file is encrypted it is harder to work with: it destroys some of the collaboration features in the process. The situation has improved recently with OneDrive and SharePoint, but it is not perfect and there are still <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/sensitivity-labels-sharepoint-onedrive-files?view=o365-worldwide#limitations">several well-documented limitations</a>.</p><p>But remember: even if all these limitations are eventually overcome, there is just no possible way that this one solution will ever be good enough to provide for your entire list of cybersecurity concerns or compliance requirements. Being able to distinguish between corporate managed and non-managed devices and apply different policies or protections based on this information is a huge benefit and a major piece of the modern management framework, in my opinion. I do not think it is going anywhere anytime soon.</p><p><em>Originally published at </em><a href="https://www.itpromentor.com/no-silver-bullet/"><em>https://www.itpromentor.com</em></a><em> on March 9, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5577fb4a88bf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/there-is-no-panacea-there-is-no-silver-bullet-5577fb4a88bf">There is no panacea, there is no silver bullet</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Devices or Users: When to target which policy type in Microsoft Endpoint Manager (Intune)]]></title>
            <link>https://medium.com/re-office-365/devices-or-users-when-to-target-which-policy-type-in-microsoft-endpoint-manager-intune-e851ce4b9795?source=rss-7202e9f16eb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/e851ce4b9795</guid>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[device-management]]></category>
            <category><![CDATA[microsoft-intune]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[endpoint-management]]></category>
            <dc:creator><![CDATA[Alex Fields]]></dc:creator>
            <pubDate>Fri, 29 Jan 2021 19:09:07 GMT</pubDate>
            <atom:updated>2021-02-02T10:44:30.814Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*f5q6mqX-sgSjbYk6" /></figure><p>A new reader question came across my desk the other day. In truth, it is not the first time I have answered this question, but I realized that I could probably repeat myself less if I simply write an article and publish it. The question is:</p><h4>When working in Microsoft Endpoint Manager (Intune), how do I determine whether to assign policies to devices or users?</h4><p>Before we describe the best practices here I think it is important to review a little bit of information about security groups. Groups in Azure AD come in five flavors:</p><ul><li>Microsoft 365 Groups (Users only)</li><li>Static Security groups comprised of Users</li><li>Static Security groups comprised of Devices</li><li>Dynamic Security groups comprised of Users</li><li>Dynamic Security groups comprised of Devices</li></ul><p>First, just know that you should use <em>Security</em> groups to assign policies and profiles within Intune (I would not use Microsoft 365 Groups). Eliminating that option right off the bat, let’s narrow it down further by determining when it would be best to recommend targeting Users vs. Devices.</p><p>Unfortunately, there is no one size fits all here; so we have to give the classic consultant answer: “It depends.” On what does it depend? A couple of factors:</p><ol><li>Are you trying to control an experience based on who the user is, or what device they are using?</li><li>What type of policy or profile are we working with?</li></ol><p>Let’s start with the second question first. The <em>type </em>of policy or profile you are working with may answer the question for you.</p><h3>Compliance policies</h3><p>When it comes to Compliance policies, I <em>always</em> target users. Is it possible to assign a compliance policy to a security group comprised of devices? Yes. But I do not recommend it. If you assign these policies to devices, you will find that there are two compliance results for every device (well, actually three if you include the built-in policy).</p><ol><li>The “system account” will receive a compliance status</li><li>The user who signs into the device will also receive a compliance status</li></ol><p>Unfortunately, this can lead to errors when it reports on the overall compliance of the device. I have even seen strange occurrences where both the user and the system account showed up as ‘Compliant,’ but the built-in compliance policy showed as ‘Not Compliant.’ This is even more confusing because literally the only thing that policy is measuring is whether there is a compliance policy being applied (and obviously <em>there</em> <em>is</em>). Because of these inconsistencies and issues, I do not recommend assigning Compliance policies to devices. Also notice that we are not given the option to assign to “ <em>All devices</em>” but only “ <em>All users</em> “ (unlike Configuration profiles).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cfNxuN4Ez-DtfEVq" /></figure><p>In general, I like to think of Compliance policies as the bare minimum that you would require for ANY endpoint to connect and start working with your systems. And so I do not have different compliance requirements for different types of devices. Whether they are corporate, personal, etc.-it doesn’t matter. Therefore I would normally just create one compliance policy for each device platform that I support, and then assign these to <strong>All users</strong>, or at least a security group that represents all of my <em>licensed</em> users (the members who are licensed to use Intune).</p><h3>Device Configuration and Endpoint Security profiles</h3><p>Next up: <em>Device Configuration</em> profiles (including <em>Update rings</em>) and <em>Endpoint Security</em> profiles. Here we return to our first question: Are you trying to control an experience based on <em>who</em> the user is, or which device they are using?</p><p>So the obvious use case for targeting devices is something like kiosk devices, or lab computers. No matter who sits down and logs into that machine, you want the experience to be identical. And it may be a different experience than what is expected when the user is picking up their <em>own </em>device (even to work with the same applications). In that case, you would want to create a device-based security group and apply the profiles accordingly.</p><p>Another use case for device targeting (using a Dynamic group) is where you have an organization that is managing a mix of corporate-owned and personal devices within the same device platform. For example, you might have corporate owned iPhones and some personal iPhones. In that case, there are likely different requirements for the one group versus the other. For example, your corporate profile might block manual unenrollment, whereas the personal profile would not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/831/0*3oO48xW4JLdAxahv" /></figure><p>Therefore, it makes sense to create two dynamic security groups: one that applies to <em>deviceOwnership = Personal </em>and the other to <em>deviceOwnership = Company</em>. When you assign your BYOD profiles, you would target the former group, and when you assign company profiles, you would target the latter.</p><p>One of the downsides to using dynamic security groups is that I have noticed it can sometimes take extra time (minutes to hours) for the membership to update. This normally isn’t too big of a deal and often will go unnoticed. But there are likely to be some helpdesk calls in your future that are resolved by nothing more than “waiting it out.”</p><h3>Applications</h3><p>Pretty much the same logic can be applied when you are assigning applications to devices. Should this user get the same applications <em>regardless </em>of which device they use? Or do they get a different set of apps depending on which device they are interfacing with?</p><p>The only thing to be mindful of is the difference between apps that you deploy as <em>Required </em>versus apps that you deploy as merely <em>Available</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z3PeY_7L8PL1wBEC" /></figure><p>If it is a <em>Required </em>application, it means that the app is not just ‘available’ in the company app store, but it will be automatically and forcefully installed over the air (the user has no choice in the matter). You will notice that in the case of <em>Required</em>, you can assign the application to devices <em>or </em>users, but for <em>Available</em> applications you may only assign those to <em>users</em>.</p><p>Generally speaking, I would only assign to the <em>device </em>in the instance of a kiosk or lab situation. Otherwise I target the users.</p><h3>App protection (MAM)</h3><p>Remember that App protections policies (a.k.a. MAM) can be used either with or without enrollment of the actual device. This already implies that you should be targeting user objects rather than device objects. When a user signs into an application, these policies are applied at the application layer, and the device does not really play into the equation.</p><h3>Conditional Access</h3><p>Similar to Compliance and App protection policies, I always target <em>users </em>here, and not devices. The first thing to note is that when you use the device-based controls such as <em>Compliant device </em>and <em>Hybrid Azure AD Joined device</em>, this will already cover the distinction between managed and unmanaged endpoints. I am usually only interested in restricting access if I have less control over an endpoint (or its applications in the case of MAM).</p><p>The second point is that when Conditional Access is being asked to evaluate device compliance, I like to have this tied to the same group of users for whom compliance is actually being measured. The devices are not being targeted by my Compliance policies, and therefore I will not be targeting the devices with my Conditional Access policies. I will target the appropriate users in both cases (e.g. those who are licensed to use the features).</p><h3>Autopilot profiles</h3><p>When you assign Autopilot profiles, the advice is the opposite from Compliance and Conditional Access. Here, the profiles are only assigned to <em>devices</em>, not users. Notice again that we can select specific device groups, or just choose <em>All devices</em> (but there is no <em>All users</em> option).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YkXiCc7cYCeN5PCg" /></figure><p>And that makes sense. Autopilot is all about pre-provisioning <em>devices</em>. While there is a lot more to autopilot, for the purposes of this discussion, this is all we have to say about it.</p><h3>Conclusion</h3><p>So there you have it, clear as mud, right? This table is a summary:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9QcYbkMP_iDLBlPp" /></figure><p>And in case you are curious about my “standard approach,” I normally target users for the majority of my policies and profiles (except Autopilot of course). I find that this keeps it very simple for SMB’s. For example, it is almost always the case that Windows devices are company-owned, while mobile devices are personal/BYOD. Therefore I just have BYOD-friendly policies assigned to all of the <em>users </em>to support their mobile devices (and macOS where the need exists), and then I have a ‘corporate’ baseline for Windows computers that I likewise apply to all the <em>users</em>. I normally only allow <em>web </em>access on personal Windows devices (if at all).</p><p>Nevertheless in some cases it becomes important to distinguish between personal and corporate devices. In those cases I would recommend using the dynamic device groups to tailor the policies to the BYOD vs. company-owned groups, as appropriate.</p><p><em>Originally published at </em><a href="https://www.itpromentor.com/devices-or-users-when-to-target-which-policy-type-in-microsoft-endpoint-manager-intune/"><em>https://www.itpromentor.com</em></a><em> on January 29, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e851ce4b9795" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/devices-or-users-when-to-target-which-policy-type-in-microsoft-endpoint-manager-intune-e851ce4b9795">Devices or Users: When to target which policy type in Microsoft Endpoint Manager (Intune)</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monitoring identity, cloud apps and email at different service tiers]]></title>
            <link>https://medium.com/re-office-365/monitoring-identity-cloud-apps-and-email-at-different-service-tiers-88fae85828d?source=rss-7202e9f16eb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/88fae85828d</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-app-security]]></category>
            <category><![CDATA[identity-protection]]></category>
            <category><![CDATA[azure-ad]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <dc:creator><![CDATA[Alex Fields]]></dc:creator>
            <pubDate>Tue, 12 Jan 2021 12:24:00 GMT</pubDate>
            <atom:updated>2021-01-13T06:20:40.328Z</atom:updated>
            <content:encoded><![CDATA[<p>Today I want to give you two ideas that you can take to your customers as new offerings. Some of you may already be doing some form of this, but based on my <a href="https://www.itpromentor.com/happy-new-year-2021/">recent survey results</a>, identity protection and monitoring in the cloud is still an area that is wanting for development.</p><p>The time for this conversation is ripe with the recent high-profile <a href="https://www.microsoft.com/security/blog/2020/12/18/analyzing-solorigate-the-compromised-dll-file-that-started-a-sophisticated-cyberattack-and-how-microsoft-defender-helps-protect/">Solorigate attack</a> that impacted so many customers, including several US government agencies. I suggest that we are living in an era now that <em>demands </em>a higher level of attention to the <a href="https://www.itpromentor.com/assume-breach/">entire attack kill chain</a>.</p><p>For a few years we have been hyper-focused on <em>preventing </em>bad stuff from happening in the first place: <a href="https://www.itpromentor.com/email-security-checklist/">Email protection</a>, <a href="https://www.itpromentor.com/mfa-the-easy-way/">Multi-factor authentication</a>, <a href="https://www.itpromentor.com/simpler-conditional-access/">Conditional Access</a>, <a href="https://www.itpromentor.com/limiting-privilege-is-a-process-not-an-event/">limiting admin privilege</a> and so on. And we cannot stop paying attention to those things, but we also must go further now and ask, “ <em>What if our defenses fail?</em> “ Because at some point, they probably will. Even with all the above-mentioned items in place.</p><p>Getting “post-breach” defenses activated can be viewed as a journey, rather than a single event. Ultimately you will have several different domains or “areas” to which you must apply higher scrutiny:</p><ul><li>Email and SaaS apps</li><li>On-premises network</li><li>Endpoints</li><li>WAN and VPN links</li><li>IaaS and PaaS environments</li><li>Physical environment</li></ul><p>I will suggest that we begin the journey at the top of this list, focusing on the corporate identity which is our passport to Email and cloud apps. There are so many ways to deliver better visibility into potential compromises, and of course we cannot cover them all here; when you first start going down this path, there is only so much you can accomplish with the limited time and resources you have, right? So let’s keep it simple, but try to get some good mileage from our efforts.</p><h3>Tier 1: Basic Email and Cloud App Monitoring</h3><p>In a Basic service tier we just need to cover a few essentials; the idea is to keep our costs low, and the start-up efforts minimal while still making forward progress against our goals.</p><p>With regard to Microsoft 365 subscriptions, you should first of all enable the <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/turn-audit-log-search-on-or-off?view=o365-worldwide">Unified audit log</a>, and then configure <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/alert-policies?view=o365-worldwide">Alert policies</a> in the Security &amp; Compliance center ( <a href="https://protection.office.com/alertpolicies">https://protection.office.com/alertpolicies</a>). These are also available now at the new Security admin center ( <a href="https://security.microsoft.com/alertpolicies">https://security.microsoft.com/alertpolicies</a>). These are the same policies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*snHf6pVrqYANrcXC" /></figure><p>There are a number of built-in policies already present here for most subscriptions. You will see some additional built-in policies with a subscription to Microsoft Defender for Office 365 P2 (available standalone or included with Office 365 E5 or the Microsoft 365 E5 Security add-on).</p><p>There are certain events worth knowing about, such as <strong><em>Creation of forwarding/redirect rules</em></strong>, or <strong><em>Suspicious email sending patterns</em></strong> . If you have the <a href="https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/enable-the-report-message-add-in?view=o365-worldwide">Report message add-in</a> deployed in your organization (and you ought to), then you can also enable the policy called <strong><em>Email reported by user as malware or phish</em></strong> (because no filter will catch 100%). This allows you to do some additional investigation if needed (aided by <a href="https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/automated-investigation-response-office?view=o365-worldwide">Automatic Investigation + Response</a> if you have that P2 subscription).</p><p>Be sure to configure all of the built-in alerts so that they go to your service desk/ticketing system. Optionally, you can configure additional custom events to monitor. You want real people to follow up with these events (note: some of the events categorized as “informational” are still important).</p><p>This is something that you can (and should) do right away, with little or no experience (you will learn by doing). But this does create additional work on the back end! When one of these alerts rolls in the door, you need to have someone available to react, evaluate, and remediate if necessary. That makes this a new service with MRR potential. Every single MSP out there should be doing this if they aren’t already.</p><p>Another simple thing you could do at this tier is enable some Dark web monitoring with a third-party service. For example, if your corporate credentials are exposed on the dark web, you can receive a notification about this event, which might indicate that it is time to force password changes for the impacted user(s).</p><h3>Tier 2: Identity Protection + Cloud App Security</h3><p>In our second service tier, the goal is to improve our detection capabilities (to capture more subtle activities and additional signals) <em>and </em>to automate some of our response and remediation efforts. But at this stage, we are not yet looking for a complex tool like a SIEM, which adds significant time and expense to your operations. For a happy middle ground I recommend Microsoft Cloud App Security (MCAS).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jIAnOceiBHd5_TLZ" /></figure><p>Similar to the alert policies that we have in the Security center, MCAS comes with many pre-canned alerts that we can enable. And some of these are really valuable: for example being able to alert on uncommon or unusual activities within cloud apps, or strange login activities like impossible travel (e.g. I sign in from Minneapolis, USA and then a few minutes later from Paris, France). However, MCAS has a few extra tricks up its sleeve that make it especially attractive to service providers and their customers.</p><p>First, we can include governance actions within our alert policies, so that when an alert is triggered by some event, we can have the system take certain actions to mitigate or remediate the situation before a human has to get involved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MefwpOhy_bYdcBQ4" /></figure><p>Second, we have the ability to use our own templates and customize the “from” address for email alerts. This makes it easier for our ticketing system to automatically associate alerts with our customers according to the sending email domain (be sure to add MailChimp’s information for <a href="https://mailchimp.com/help/about-email-authentication/">Email authentication </a>to your DNS records).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PTDfI-UzTd9k6dq4" /></figure><p>Third, we have the ability to add delegated admin access for our MSSP, so that as a service provider, we can quickly switch between customer instances of MCAS right from the native admin web UI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YVInBEp5v1bbxsEF" /></figure><p>You can add additional admin users to the customer’s instance from their portal under <strong>Settings &gt; Manage admin access</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9ELpFqeN8LiTFxqw" /></figure><p>But wait, there’s more. You can also connect third-party SaaS apps to MCAS for monitoring ( <strong>Settings &gt; App connectors</strong>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HqrhJRYkzcBIJkmu" /></figure><p>This tool can do even more for us paired with Azure AD Identity Protection and Microsoft Defender for Identity (which is a monitoring tool for your local Active Directory). A subscription bundle such as Enterprise Mobility + Security E5, or Microsoft 365 E5 Security, or the full Microsoft 365 E5 will contain all the requisite parts to give us what Microsoft dubs a “ <a href="https://techcommunity.microsoft.com/t5/microsoft-security-and/unified-secops-investigation-for-hybrid-environments/ba-p/360850">Unified SecOps investigationexperience.</a> “</p><p><em>Aside: My dream product from Microsoft would be an SMB package: “Microsoft 365 Defender for SMB” with Email, MCAS, Identity Protection and Endpoint all rolled into one. Similar to Microsoft 365 E5 Security but “right-sized” to fit the SMB market, and fully compatible with the Microsoft 365 Business Premium plan (the E5 Security bundle cannot be stapled on to a Business plan at this time).</em></p><p>Each of these tools is relatively easy to set up and use. For example, the Microsoft Defender for Identity installation is really simple; there is a download available from the portal at <a href="https://portal.atp.azure.com/">https://portal.atp.azure.com</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QvjLVRpXVgLOc1lC" /></figure><p>You just have to install this sensor and plug in the access key on each domain controller in your network. And just like that, you can export your security data to the cloud for analysis and alerting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DW-xk-MmEHOlpzGy" /></figure><p>Back in the MCAS portal under <strong>Settings &gt; Settings &gt; Threat protection</strong>, you can enable the integrations to <strong>Azure AD Identity Protection</strong> and <strong>Microsoft Defender for Identity</strong> with just a couple of clicks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rXyGxdBmLOifVX8j" /></figure><p>This will pull in data from Azure AD and on-premises AD (when you have the sensor installed), giving you end-to-end visibility over your hybrid identity picture. You will find additional alert policies automatically added (be sure to configure them as you have the others).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n1ET7W6mRX-Syoug" /></figure><p>As well, we get a really nice view of identity risk with dynamically updated “Investigation priority scores” (the higher a user’s score, the higher the probability is that this user is compromised). This will look at signals from on-prem AD, Azure AD and any other cloud apps you have connected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5CUXjmbsI-bgGKC6" /></figure><p>As a bonus, at this tier you do not really need a third-party service to monitor the dark web; Azure AD Identity Protection will do this for us (which also impacts each user’s risk score), and we can even configure the <a href="https://docs.microsoft.com/en-us/azure/active-directory/identity-protection/howto-identity-protection-configure-risk-policies">User risk policy</a> in Azure AD to automatically force password changes when these types of credential exposures are detected in the wild (resets are validated with MFA, of course).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bQwaUi-6nP_ydeGl" /></figure><p>Even though this solution includes a bit more automation, we also have a larger number of detections available (many of which are more subtle), and not all events can be “auto-healed.” So you should still plan to factor labor into your calculations for offering this service. I suggest you create bands such as:</p><p>Estimate that someone on your service desk needs to investigate or “triage” up to 5 incidents per month per 50 users at an average time of 15–20 minutes per incident. Then price accordingly. Run this model with a pilot group of customers willing to be guinea pigs for a couple of months. Some events may require more time, some may be less; adjust your offer as needed and then continue releasing to other rings from there.</p><p><em>Note: This is just “back of the napkin” stuff that is right off the top of my head; you should do your own work to create real offerings.</em> <em>Also note: I would suggest that a more serious breach event where an adversary has established persistence or dominance should turn into T&amp;M at your “Incident Response” rate (which may be higher than typical services).</em></p><h3>Discussing with customers: Security is a journey, not an event</h3><p>Through working with others, I have found that these steps are a “fast track” to tangible results and new revenue. When you discuss this journey with your customers, explain why we need to start moving toward a zero-trust model, where we assume that nothing can be trusted, and that we might be breached at any given moment (even right now). This requires a fundamentally new approach, and as part of that we want to be able to:</p><ol><li>Detect when someone is “inside the house” who does not belong, and</li><li>Contain and remove the unauthorized person(s) as quickly as possible</li></ol><p>What we have laid out above does not even include <a href="https://www.itpromentor.com/reader-question-do-you-recommend-defender-in-place-of-third-party-antivirus-or-security-tools/">endpoint security</a>, and specifically we haven’t discussed Endpoint Detection and Response (EDR). Obviously, I would recommend this component be on your roadmap as well. But remember that you don’t have to do everything at once, and what we’re discussing here today is just one <em>potential </em>path through the weeds: you are free to create your own journey!</p><p>Partly I chose to begin with the identity and cloud apps piece because this still accounts for about 81% of security breaches in the wild according to Microsoft (and I am certain email is at the top of this list). Therefore we should attempt to provide our customers with concrete solutions that we can spin up quickly in the cloud without needing to deploy new security software on servers and endpoints, or monkey around too much with on-prem hardware and appliances (these projects can be longer and more difficult).</p><p>I believe this is a very realistic starting point for new MSSP’s with only minor experience (i.e. if you consider yourself a “Baby SOC”).</p><p>For more information on these and other cybersecurity solutions built on the Microsoft cloud, check out my courses at <a href="https://squareonesecurity.teachable.com/p/microsoft-365-cybersecurity-bundle">SquareOne by ITProMentor.com</a>.</p><p><em>Originally published at </em><a href="https://www.itpromentor.com/identity-monitoring-tiers/"><em>https://www.itpromentor.com</em></a><em> on January 12, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88fae85828d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/monitoring-identity-cloud-apps-and-email-at-different-service-tiers-88fae85828d">Monitoring identity, cloud apps and email at different service tiers</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>