Knowledge Base
Browse Docs
  • Introduction
    1. DefensX
    2. DNS & Web Filtering
    3. Zero Trust Files
    4. Zero Trust Credentials
    5. ADWare Protection
    6. Remote Browser Isolation
    7. Secure Browser Extension
    8. Secure Mobile Browser
  • Management
    1. Role-Based Access Control
  • Deployment
    1. Deployment via RMM
    2. Operating System Agent
    3. Deployment via GPO
    4. Deployment via Intune
    5. VDI and Terminal Servers
    6. Windows Manual Deployment
    7. Mac MDM Deployment
    8. Mac Manual Deployment
    9. Network Deployment
    10. Secure Mobile Browser
    11. Bypass Option
    12. AI Protections
    13. SaaS Restrictions
    14. Bookmark Manager
  • Secure Access (ZTNA)
    1. Configuration
  • Integrations
    1. Azure AD
    2. Identity Providers
    3. SIEM
  • Policy Management
    1. Configuring Policies
    2. Configuring Consents
  • Questions & Answers
    1. Licensing
    2. Incognito Mode
    3. Onboarding
    4. Active Directory
    5. Group Synchronization
    6. Agent
    7. Conflicting Softwares
    8. Reporting
    9. Virtual Desktops
    10. Using the Backend
    11. DNS & Web Filtering
  • Training Videos
    1. Onboarding Videos
    2. Attack Scenarios
    3. MSP Admin Training Series
  • MSP Automation
    1. Overview
    2. External Notifications
    3. Integrations
    4. Partner API
ONLINE DOCUMENTATION

SaaS Application Restrictions

In this document
  • How it works?
  • Enabling Google GSuite Restrictions
  • Enabling Microsoft O365 Restrictions

You can use SaaS Application Restrictions with vendors including Google GSuite, Microsoft O365 which provide methods to limit access to their services by Domain or Tenant ID values.

How it works?

You can configure Saas Restrictions in the backend, from Settings → SaaS Restrictions menu.

When you have enabled a SaaS Restriction, according to the type of the application installed, DefensX extensions append a specific HTTP header to every request sent to the related cloud application.

For example, if you enabled GSuite restrictions and only provided to example.com as allowed domains, DefensX extensions append X-GooGApps-Allowed-Domains: example.com in every request to *.google.com and gmail.com. When Google GSuite receives a request from a client that is using this header, it stops working for domains other than the included ones in the received header (https://groups.google.com/g/k12appstech/c/B1fsGYePm34).

Similarly, Microsoft also has a feature to restrict access by Tenant ID or the domain itself (https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/tenant-restrictions).

Tip
Configuration changes will be populated to the clients in a maximum of 5 minutes period. If you want to speed up the process of testing it, we recommend left-clicking on the top-right DefensX extension icon in the browser and clicking on the Policy Refresh icon.

Enabling Google GSuite Restrictions

gsuite

In order to enable Google GSuite restrictions, first toggle the checkbox on the right-hand side and enter your allowed domains into the list. You can enter as many domains as you want.

Enabling Microsoft O365 Restrictions

ofis

In order to enable Microsoft O365 restrictions, first toggle the checkbox on the right-hand side and enter your allowed domains or Azure Tenant ID values into the list. You can enter as many domains/tenant id as you want.

www.defensx.com
Secure Industries, Inc 101 Avenue of The Americas, Floor 9 New York, NY 10013