<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloudappsecurity on Anything About IT</title><link>https://www.verboon.info/tags/cloudappsecurity/</link><description>Recent content in Cloudappsecurity on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 09 Jan 2019 21:11:35 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/cloudappsecurity/index.xml" rel="self" type="application/rss+xml"/><item><title>How to monitor your Azure AD emergency account with Cloud App Security</title><link>https://www.verboon.info/2019/01/how-to-monitor-your-azure-ad-emergency-account-with-cloud-app-security/</link><pubDate>Wed, 09 Jan 2019 21:11:35 +0000</pubDate><guid>https://www.verboon.info/2019/01/how-to-monitor-your-azure-ad-emergency-account-with-cloud-app-security/</guid><description>&lt;p&gt;As a best practice you should have at least one or two emergency accounts in your Azure Active Directory. You would use these accounts in the event where due to a configuration mistake you inadvertently locked yourself out of the Azure Active Directory or when for some reason you can&amp;rsquo;t use MFA that should be enabled on all administrative accounts.&lt;/p&gt;
&lt;p&gt;For more guidance about creating emergency accounts I suggest you read &lt;a href="https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-emergency-access"&gt;Manage emergency access accounts in Azure AD&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>