Apply Device Policies on SaaS Applications
This article will show you how to enable device-based access control policies on a SaaS application using Banyan's Zero Trust security framework
This guide primarily refers to OIDC-enabled SaaS Applications. However, Banyan also supports SAML-enabled SaaS Applications and the same steps can be extended to SAML-enabled SaaS Applications.
«««< Updated upstream For this quick start guide, we have a public internet-facing web application - commonly called a Software-as-a-Service (SaaS) Application - that supports user authentication using OpenID Connect (OIDC). ======= For this quick start guide, we have a public internet-facing web application - commonly called a Software-as-a-Service (SaaS) Application - that supports user authentication using OpenID Connect (OIDC).
We assume your end users have been added to your Banyan directory, and that they have the latest Banyan Desktop or Mobile App installed on devices from which they will access the Jenkins application.
The setup for this quick start guide is as follows:
The SaaS Application we’ll secure supports OpenID Connect (OIDC) for authentication.
We have the SaaS Application’s authentication Redirect URL (aka Callback URL) and have rights to configure its OIDC settings.
Note: Banyan is NOT a primary Identity Provider; instead the Banyan TrustProvider component federates to your organization’s Identity Provider upon every login. Banyan then evaluates security posture against access policies.
We will add a security policy to the SaaS Application in 4 steps.
Step 1. Create a Policy for SaaS App Access
1.1 Navigate to Secure Access > Policies > Create New Policy and create a new Policy using the template Web Policy.
1.2 Name the policy
Also set the policy attributes for minimal controls:
- Only allow access from the following role: ANY
- Only allow users and devices with the following Trust Levels: No Trust Level - ignore TrustScore
Step 2. Create the SaaS Application
2.1 Navigate to Manage Services > SaaS Applications > + Publish SAAS APPLICATION.
Banyan Federatedto route to Banyan first.
2.3 Name the SaaS App
quickstart-saas-app and set the attributes:
- select the authentication protocol to be
- set the
Redirect URLto the well-known Redirect URL provided by the SaaS application you are securing
You can also configure device policies on SAML-enabled SaaS Applications.
2.4 Attach the
quickstart-user-saas policy we had previously created and set enforcement mode to
2.5 Click Register. The next screen will give you the details you need to enter into your SaaS App.
Step 3. Configure your OIDC-enabled SaaS App to use Banyan for authentication
3.1 Fill in the data from Banyan Command Center for the SaaS App you are securing.
Step 4. Navigate to the SaaS App and login in via OIDC
4.1 Now, you can navigate to your SaaS App and authenticate. You will be taken to your Identity Provider to login while, behind the scenes, Banyan is evaluate device posture and enforcing your security policies.
And, that’s it! You You have created a Zero Trust policy for your OIDC-enabled SaaS App.
Last modified: Sep 23, 2021