You can now more precisely control your HTTP DLP policies by specifying whether to scan the request or response body, helping to reduce false positives and target specific data flows.
In the Gateway HTTP policy builder, you will find a new optional selector called Body Phase. This allows you to define the direction of traffic the DLP engine will inspect:
- Request Body: Scans data sent from a user’s machine to an upstream service. This is ideal for monitoring data uploads, form submissions, or other user-initiated data exfiltration attempts.
- Response Body: Scans data sent to a user’s machine from an upstream service. Use this to inspect file downloads and website content for sensitive data.
For example, consider a policy that blocks Social Security Numbers (SSNs). Previously, this policy might trigger when a user visits a website that contains example SSNs in its content (the response body). Now, by setting the Body Phase to Request Body, the policy will only trigger if the user attempts to upload or submit an SSN, ignoring the content of the web page itself.
All policies without this selector will continue to scan both request and response bodies to ensure continued protection.
For more information, refer to Gateway HTTP policy selectors.
Source: Cloudflare



![External authentication methods (EAM) – Public preview update [MC1192252] 4 pexels apasaric 325185](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-apasaric-325185-150x150.webp)
![(Updated) New Copilot button in file previewer for OneDrive and SharePoint [MC1182707] 5 pexels googledeepmind 17486101](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-googledeepmind-17486101-150x150.webp)
![Microsoft Purview | eDiscovery - Metadata field enhancements in process reporting [MC1162273] 7 Microsoft Purview | eDiscovery – Metadata field enhancements in process reporting [MC1162273]](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-scottwebb-614227-96x96.webp)