<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Break Glass on JanBakker.tech</title><link>https://janbakker.tech/tags/break-glass/</link><description>Recent content in Break Glass on JanBakker.tech</description><generator>Hugo</generator><language>en-US</language><copyright>Jan Bakker</copyright><lastBuildDate>Sun, 05 Jul 2020 09:25:47 +0000</lastBuildDate><atom:link href="https://janbakker.tech/tags/break-glass/index.xml" rel="self" type="application/rss+xml"/><item><title>Use Power Automate as your Conditional Access Police Department</title><link>https://janbakker.tech/use-power-automate-as-your-ca-police-department/</link><pubDate>Sat, 04 Jul 2020 07:10:42 +0000</pubDate><guid>https://janbakker.tech/use-power-automate-as-your-ca-police-department/</guid><description>&lt;p&gt;Last week, I was working on a &#10;&lt;a href="https://janbakker.tech/microsoft-secure-score-series-14-designate-more-than-one-global-admin/"&gt;new blog for the Secure Score Series&lt;/a&gt; regarding global admin and break glass accounts. I came to the point where I was thinking of possible scenarios that could go wrong with these accounts. What if someone accidentally added these users to a certain group? What if that group would be triggered in some policy or maintenance tasks? A lot of these actions can be discovered using Microsoft Cloud App Security and Azure Monitor. This way, you will be alerted when someone touches the accounts in any way, or if the account is used to sign-in.&lt;/p&gt;</description></item></channel></rss>