{"id":62440,"date":"2022-05-02T11:45:00","date_gmt":"2022-05-02T15:45:00","guid":{"rendered":"https:\/\/jumpcloud.com\/?p=62440"},"modified":"2024-01-26T15:27:28","modified_gmt":"2024-01-26T20:27:28","slug":"conditional-access-policies-examples","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/conditional-access-policies-examples","title":{"rendered":"Examples of Conditional Access Policies"},"content":{"rendered":"\n

Think back to the last fraudulent call or email that made it past your spam filter. How could you tell it was fake? Maybe they called at a weird hour, or the name in the email address didn\u2019t match the signature, or you didn\u2019t recognize the area code. Or maybe your car doesn\u2019t actually have an extended warranty. <\/p>\n\n\n\n

Whatever the reason, your spam filter didn\u2019t catch the fraud, but you did. Why?<\/p>\n\n\n\n

Humans are great at picking up on contextual clues. Computers don\u2019t do so on their own; they have to be programmed to recognize them.<\/p>\n\n\n\n

That\u2019s how conditional access policies<\/a> work. They use a set of contextual clues \u2014 like what locations and devices are considered \u201cnormal\u201d for a login \u2014 to apply the appropriate amount of contextual <\/em>security to a login attempt. This means more security for suspicious attempts, and less friction for typical and expected ones. Essentially, conditional access automates the human intuition that enables you to spot suspicious activity and applies it to the authentication process.<\/p>\n\n\n\n

Let\u2019s dive deeper into how they work and explore some of the most common examples and use cases of conditional access policies. <\/p>\n\n\n\n

\n