LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
View All Services
Solutions
BY INDUSTRY
BY REGULATION
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
We reduce cyber risk and fortify organizations
Awards and Accolades
Recognition by analysts and media outlets
LevelBlue SpiderLabs
Global researchers, ethical hackers, and responders
LevelBlue Security Operations Platforms
Unprecedented security visibility and control
Security Colony
Access to cybersecurity threat protection resources
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Register
Login
Resources
BLOGS
UPCOMING
MEDIA & ASSETS
NOTICES
HELP
Loading...
Loading...

LevelBlue Knowledge Base

Home » Knowledgebase » WebMarshal » HOWTO: Applying Microsoft Tenant Restrictions with WebMarshal

HOWTO: Applying Microsoft Tenant Restrictions with WebMarshal

Expand / Collapse
Show/Hide Article Tools


This article applies to:

  • WebMarshal

Question:

  • How do I configure WebMarshal to apply Azure AD (Entra) tenant restrictions?

Background:

Microsoft tenant restrictions allow you to determine which tenancies of cloud applications can be accessed from within an organization (where the web access is forced through a gateway like WebMarshal). This feature can be used to control access to all apps that send the user to Azure AD for single sign-on.

Procedure:

  1. Add URL category Microsoft Auth Services
  2. Add the following URLs to this category (both HTTP and HTTPS):
    • login.microsoft.com
    • login.microsoftonline.com
    • login.windows.net
  3. Ensure that WebMarshal HTTPS inspection is enabled globally and HTTPS rules specify inspection for the category Microsoft Auth Services
  4. Create a standard rule 
    Where the URL is a member of Microsoft Auth Services 
    Rewrite Headers
    • Add a header to client requests Restrict-Access-To-Tenants with a comma separated list of tenant domains, for example: mycompany.onmicrosoft.com,contoso.com
    • Add a header to client requests Restrict-Access-Context with value of the Tenant ID of your domain (get this from Entra/Azure AD settings at https://entra.microsoft.com/ as described in the Microsoft article Restrict access to a tenant)
    • It is also possible to choose the users that this rule will apply to.
  5. Continue to name the rule for example Add MS Headers, and save the rule.
  6. Commit WebMarshal configuration.
Requests to the Microsoft services will have the headers added as specified.

Notes:

For more details of the tenant restriction feature, see the Microsoft article linked.

To contact Trustwave about this article or to request support:

Rate this Article:
     

Related Links



Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster.


Execution: 0.031. 9 queries. Compression Disabled.
Powered by InstantKB.NET