Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Global Secure Access supports network content filtering through file policies. This feature helps you safeguard against unintended data exposure and prevents inline data leaks to generative AI applications and internet destinations. By extending data protection capabilities to the network layer through Global Secure Access, network content filtering enables your organization to enforce data policies on network traffic in real time. You can discover and protect files shared with unsanctioned destinations, such as generative AI and unmanaged cloud apps, from managed endpoints through browsers, applications, add-ins, APIs, and more.
The network content filtering solution brings together Microsoft Purview's data classification service and the identity-centric network security policies in Global Secure Access. This combination creates an advanced network-layer data security solution, Data Loss Prevention (DLP), that's identity-centric and policy-driven. By combining content inspection with real-time user risk evaluation, you can enforce granular controls over sensitive data movement across the network without compromising user productivity or security posture.
High-level architecture
This article explains how to create a file policy to filter internet traffic flowing through Global Secure Access.
Important
The network content filtering with file policies feature is currently in PREVIEW.
This information relates to a prerelease product that might be substantially modified before release. Microsoft makes no warranties, expressed or implied, with respect to the information provided here.
Scenarios included in this preview
This preview supports the following key scenarios and outcomes for HTTP/1.1 traffic:
- By using Basic file policy, you can block files based on supported file MIME types.
- By using the Scan with Purview action in file policy, you can audit and block files based on:
- Microsoft Purview sensitivity labels
- Sensitive content in the file
- The user's risk level
- You can generate Data Loss Prevention (DLP) admin alerts for rule matches.
Important
This preview supports network content filtering only for files over HTTP/1.1. It doesn't support network content filtering for text.
Prerequisites
To use the File Policy feature, you need the following prerequisites:
- A valid Microsoft Entra tenant.
- Licensing for the product. For details, see the licensing section of What is Global Secure Access. If needed, you can purchase licenses or get trial licenses.
- A valid Microsoft Entra Internet Access license.
- A valid Microsoft Purview license, required for Scan with Purview inspection.
- You must set up pay-as-you-go billing to use Scan with Purview.
- You can use basic file policy without a Purview license.
- A user with the Global Secure Access Administrator role in Microsoft Entra ID to configure Global Secure Access settings.
- A Conditional Access Administrator role to configure Conditional Access policies.
- The Global Secure Access client requires a device (or virtual machine) that is either Microsoft Entra ID joined or Microsoft Entra ID Hybrid joined.
Initial configuration
To configure file policies, complete the following initial setup steps:
- Enable the Internet Access traffic forwarding profile and ensure correct user assignments.
- Configure the Transport Layer Security (TLS) inspection policy.
- Install and configure the Global Secure Access client:
- Install the Global Secure Access client on Windows or macOS.
Important
Before you continue, test and ensure your client's internet traffic is routed through Global Secure Access. To verify the client configuration, see the steps in the following section.
- Select the Global Secure Access icon and select the Troubleshooting tab.
- Under Advanced Diagnostics, select Run tool.
- In the Global Secure Access Advanced Diagnostics window, select the Forwarding Profile tab.
- Verify that Internet Access rules are present in the Rules section. This configuration might take up to 15 minutes to apply to clients after enabling the Internet Access traffic profile in the Microsoft Entra admin center.
- Install the Global Secure Access client on Windows or macOS.
- Confirm access to web applications you plan for file policies.
Configure a file policy
To configure a file policy in Global Secure Access, complete the following steps:
- Create a file policy.
- Link the file policy to a security profile.
- Configure a Conditional Access policy.
Create a file policy
- Sign in to the Microsoft Entra admin center as a Global Secure Access Administrator.
- Browse to Global Secure Access > Secure > File policies.
- Select + Create Policy. Pick the options that fit your needs.
- On the Basics tab:
- Enter the policy Name.
- Enter the policy Description.
- Select Next.
- On the Rules tab:
- Add a new rule.
- Enter the Rule name, Description, Priority, and Status as appropriate.
- Select the appropriate option for the Action menu:
- For Matching conditions, select the appropriate Activities and Content types.
- Select + Add destination and configure the destinations.
- Select Next.
- On the Review tab, review your settings.
- Select Create to create the policy.
Note
If you choose the Scan with Purview action, you must also configure a corresponding DLP policy in Microsoft Purview that targets inline web traffic. Without a matching Purview DLP policy, the file policy can't inspect file content or enforce allow or deny decisions. For details, see the example walkthrough and Learn about Microsoft Purview Network Data Security.
Link the file policy to a security profile
- Browse to Global Secure Access > Secure > Security profiles.
- Select the security profile you want to modify.
- Switch to the Link policies view.
- Configure the link file policy:
- Select + Link a policy > Existing File policy.
- From the Policy name menu, select the file policy you created.
- Keep the default values for Position and State.
- Select Add.
- Close the security profile.
Configure a Conditional Access policy
To enforce the Global Secure Access security profile, create a Conditional Access policy with the following configuration:
- Sign in to the Microsoft Entra admin center.
- Browse to Identity > Protection > Conditional Access.
- Select + Create new policy.
- Name the policy.
- Select the users and groups to apply the policy to.
- Set the Target resources to All internet resources with Global Secure Access.
- Configure the Network, Conditions, and Grant sections according to your needs.
- Under Session, select Use Global Secure Access Security Profile and select the security profile you created.
- To create the policy, select Create.
For more information, see Create and link a Conditional Access policy.
The file policy is successfully configured.
Test the file policy
Test the configuration by attempting to upload or download files that match the file policy conditions. Verify that the policy settings block or allow the actions.
Example: Block sensitive PDF uploads to ChatGPT
This example walks through an end-to-end test scenario that blocks a PDF file containing sensitive data (such as credit card numbers or Social Security numbers) from being uploaded to ChatGPT.
Step 1: Configure the file policy destinations
When you create or edit your file policy rule, add the following destinations to match ChatGPT file upload traffic:
https://chatgpt.com/backend-api/files(add as URL)https://chatgpt.com/backend-api/files/process_upload_stream(add as URL)*.oaiusercontent.com(add as FQDN)
For Content types, select PDF (and other file types you want to inspect).
Tip
Web applications often use multiple URLs and FQDNs under the hood. Use browser developer tools or network traffic analysis to identify the correct upload endpoints for your target destination. For ChatGPT, the URLs listed here are the endpoints used for file upload operations.
Step 2: Configure a Purview DLP policy (for Scan with Purview action)
If you select Scan with Purview as the file policy action, you must also configure a corresponding Microsoft Purview DLP policy to inspect the file content and make the allow or deny decision.
- In the Microsoft Purview portal.
- Follow the steps in Use Network Data Security to help prevent sharing sensitive information with unmanaged AI to create a new DLP policy.
- In the Cloud apps step, search for and add ChatGPT.
- Configure the DLP rule to detect the sensitive information types you want to block (for example, credit card numbers or Social Security numbers).
- Set the rule action to Block.
- Save and apply the policy.
For more information about Purview DLP policies for network traffic, see Learn about Microsoft Purview Network Data Security.
Note
Network DLP with Global Secure Access integration is currently in preview. Global Secure Access forwards matching upload traffic to Microsoft Purview for content inspection. Purview evaluates the content against your DLP policy and returns an allow or deny decision. Global Secure Access then enforces the result.
Step 3: Validate the policy
- On a managed device with the Global Secure Access client installed, open a browser and go to ChatGPT.
- Prepare a test PDF file that contains sensitive data, such as sample credit card numbers or Social Security numbers. You can use a sample file from dlptest.com.
- In ChatGPT, attempt to upload the test PDF file.
- Verify that the upload is blocked. ChatGPT displays an error message because Global Secure Access prevented the file transfer.
- To confirm the block, check the traffic logs in the Microsoft Entra admin center under Global Secure Access > Monitor > Traffic logs.
Known limitations
- Network content filtering doesn't support text. It only supports files.
- Multipart encoding isn't supported, so file policy doesn't work for such applications. For example, Google Drive uses multipart encoding for file upload.
- Compressed content is detected in ZIP format. The content isn't decompressed.
- True file type detection might not be 100% accurate.
- Destination applications that use WebSocket, such as Copilot, aren't supported.
- Top level and second level domains don't support wildcards (like
*,*.com,*contoso.com) while configuring FQDNs.
Monitoring and logging
To view traffic logs:
- Sign in to the Microsoft Entra admin center as at least a Reports Reader.
- Select Global Secure Access > Monitor > Traffic logs.