{"id":48760,"date":"2020-12-16T07:00:00","date_gmt":"2020-12-16T12:00:00","guid":{"rendered":"https:\/\/jumpcloud.com\/?p=48760"},"modified":"2024-02-02T13:28:56","modified_gmt":"2024-02-02T18:28:56","slug":"zero-trust-conditional-access","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/zero-trust-conditional-access","title":{"rendered":"Get Zero Trust Ready with JumpCloud Conditional Access"},"content":{"rendered":"\n
As the world moves to remote work, the perimeter of security has drastically changed. More and more employees are relying on home networks or personal devices to connect to corporate resources. People are now accessing resources from any device and from anywhere outside of their corporate domain. This activity has given rise to the domainless enterprise<\/a>\u2014a central cloud directory service, which serves as the hub for securely connecting users and their devices to the IT resources they need to accomplish their jobs. <\/p>\n\n\n\n As we evolve how we work, we also need to change how we secure the IT environment. Zero Trust<\/a> is the concept of \u201ctrust nothing, verify everything,\u201d and it fundamentally shifts how security is implemented in an organization. With a Zero Trust model, access is granted when:<\/p>\n\n\n\n The process of continuous verification can be complex and time-consuming. <\/p>\n\n\n\n With the release of Conditional Access<\/a>, JumpCloud customers now have an easier path to implement the core foundations of a Zero Trust model. By managing identities, networks, and devices all from a single cloud directory platform, JumpCloud empowers admins to verify three key access points: a user’s identity, the network they\u2019re on, the device they\u2019re using. By establishing trust of these key elements, IT admins can then establish flexible verification rules through JumpCloud\u2019s new Conditional Access Policies:<\/p>\n\n\n\n Conditional Access Policies enable IT admins to customize their approach to access and security by combining these steps into different policy levels.<\/p>\n\n\n\n Conditional Access allows admins to combine individual policies into global access verification schemes for your organization or can be applied at a group level. Here are some of the use cases we\u2019ve heard from our customers.<\/p>\n\n\n\n At JumpCloud, a device is considered a user\u2019s gateway to all access. To provide secure access through devices, admins install the JumpCloud agent on any devices that are required to be managed and controlled by the organization. Through the agent, admins can distribute security configurations (policies), manage user accounts and their credentials, and apply core security settings such as enabling full disk encryption and MFA. <\/p>\n\n\n\n With these procedures performed by the agent, JumpCloud can verify trust through the automatic installation of a JumpCloud-issued certificate. This certificate verifies the machines that are known and trusted by the organization and are part of the organizations\u2019 conditional access verification requirements when authenticating to resources. <\/p>\n\n\n\n To distribute certificates to your devices, go to Conditional Policies > Settings > Conditional Policies Settings > Device Certificates<\/strong> and toggle Global Certificate Distribution<\/strong> to ON<\/strong>. With certificates in place, the admin can configure Conditional Access Policies by specific user groups if desired. When a policy applies to a user, JumpCloud will verify that the user logging into the User Portal matches the user in the certificate, then the device is considered \u201ctrusted.\u201d <\/p>\n\n\n\n JumpCloud\u2019s Conditional Access allows an admin to combine a set of trust elements (identities, devices, and networks) into an \u201cAccess Policy.\u201d For example, if a user is accessing their User Portal from a known IP address and a device with a JumpCloud-issued certificate, they\u2019re allowed access without MFA. However, in the case where there\u2019s more than one policy that applies to a user, JumpCloud will enforce the strictest policy. Here\u2019s the order from the most strict to the least:<\/p>\n\n\n\n In the case where no policy applies to a user, JumpCloud offers a Global Policy <\/strong>to provide broad coverage as a default. This is a policy that takes effect when no other policy applies. By default, it\u2019s configured to respect the configuration in the \u201cMulti-Factor Authentication Settings\u201d section of the User – Details page for each user.<\/p>\n\n\n\n As this setting is user specific, you may want to configure the Global Policy to override the setting by choosing one of the three other options. To do this, you need to go into the \u201cConditional Policies Settings\u201d page, go to \u201cConditional Policies\u201d and select the Settings<\/strong> button:<\/p>\n\n\n\n From here, choose one of the following:<\/p>\n\n\n\n If you\u2019re an existing customer, you may have experienced a situation where a user was locked out unless they were in an enrollment period. This often resulted in admin intervention. Now, when a Conditional Access Policy<\/a> requires MFA and the user has not set up an MFA factor, the user will be denied access, but allowed to self-enroll in any of the enabled MFA factors.<\/p>\n\n\n\n Conditional Access has been a top request from customers, making the launch of JumpCloud Conditional Access<\/a> an important milestone. You can also look forward to more features coming soon such as:<\/p>\n\n\n\n If you don\u2019t already have a JumpCloud account, you can create one for free<\/a>, manage up to 10 users and 10 devices, and test drive the full platform, including Conditional Access. You can follow the guided simulation<\/a> to get started with Conditional Access. Use 10 days of premium, in-app 24×7 chat support with our support engineers to get the most out of your new account.\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":" JumpCloud Conditional Access provides an easier path to implement a Zero Trust model. Read how, and start a free 30 Day Trial today.<\/p>\n","protected":false},"author":119,"featured_media":48761,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_oasis_is_in_workflow":0,"_oasis_original":0,"_oasis_task_priority":"","inline_featured_image":false,"footnotes":""},"categories":[2337],"tags":[],"collection":[2775],"platform":[],"funnel_stage":[3016],"coauthors":[2551],"acf":[],"yoast_head":"\n\n
Using Conditional Access to Enable Zero Trust<\/h3>\n\n\n\n
\n
How do I use Conditional Access Policies in my organization?<\/h3>\n\n\n\n
\n
How exactly is a device determined to be trusted?<\/h3>\n\n\n\n
How are Conditional Access Policies enforced?<\/h3>\n\n\n\n
\n
What if no policies apply to a user?<\/h3>\n\n\n\n
\n
\n
What happens when a policy requires MFA, but the user hasn\u2019t configured MFA yet?<\/h3>\n\n\n\n
What\u2019s next with Conditional Access?<\/h3>\n\n\n\n
\n
Test Drive JumpCloud <\/h2>\n\n\n\n