Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • FortiDLP Policies Reference Guide

    Home FortiDLP Policies 8.0.0 FortiDLP Policies Reference Guide
    8.0.0
    8.0.0
    7.1.2
    7.1.1
    7.1.0
    7.0.0

    URL patterns: origin (Preview)

    URL patterns: origin (Preview)

    Note

    To enable this Preview feature, contact Fortinet Support.

    The origin-tracking URL patterns parameter, available in the File origin parameters or Attachment origin parameters template sections, enables you to set URL conditions for triggering detections considering a file's web origin.

    The URL patterns parameter lets you define a list of URL patterns for protected websites, from which downloaded files are monitored to prevent exfiltration. For comprehensive information about how to specify patterns, see the website URL patterns parameter section.

    Note

    The origin-tracking URL patterns parameter cannot be used to define an allowlist or a denylist like the website URL patterns parameter.

    Some policy templates can be configured to generate detections considering a file's web origin and destination.

    Example

    For example, using the Sensitive file uploaded template, you could create a policy to prevent sensitive files that are stored on a corporate Google Drive from being uploaded to any website as follows.

    In the Website parameters section:

    • Leave the URL patterns parameter empty. This will raise a detection upon attempted uploads to any website. Additionally, if upload blocking is enabled, all uploads will be blocked.

    In the File origin parameters section:

    • For the URL patterns parameter, either type a custom value or select an asset that matches your corporate Google Drive, such as drive.google.com/drive.
    Previous
    Next

    URL patterns: origin (Preview)

    URL patterns: origin (Preview)

    Note

    To enable this Preview feature, contact Fortinet Support.

    The origin-tracking URL patterns parameter, available in the File origin parameters or Attachment origin parameters template sections, enables you to set URL conditions for triggering detections considering a file's web origin.

    The URL patterns parameter lets you define a list of URL patterns for protected websites, from which downloaded files are monitored to prevent exfiltration. For comprehensive information about how to specify patterns, see the website URL patterns parameter section.

    Note

    The origin-tracking URL patterns parameter cannot be used to define an allowlist or a denylist like the website URL patterns parameter.

    Some policy templates can be configured to generate detections considering a file's web origin and destination.

    Example

    For example, using the Sensitive file uploaded template, you could create a policy to prevent sensitive files that are stored on a corporate Google Drive from being uploaded to any website as follows.

    In the Website parameters section:

    • Leave the URL patterns parameter empty. This will raise a detection upon attempted uploads to any website. Additionally, if upload blocking is enabled, all uploads will be blocked.

    In the File origin parameters section:

    • For the URL patterns parameter, either type a custom value or select an asset that matches your corporate Google Drive, such as drive.google.com/drive.
    Previous
    Next