In FortiSASE (built upon modern FortiOS 7.x architecture), configuring a regex-based DLP mechanism requires a bottom-up configuration approach due to object dependencies. First, you must create a DLP Data Pattern to define the exact Regular Expression. Second, this pattern is incorporated into a DLP Dictionary, which groups related data types for scanning. Third, you create a DLP Profile to serve as the container for your security policies. Finally, you configure a DLP Rule within that profile. The rule references the dictionary and dictates the enforcement action (e.g., block or log) when the regex is triggered. "DLP Sensor" is an incorrect distractor, as sensors were deprecated and merged directly into DLP Profiles starting in FortiOS 7.0.

FortiSASE Administration Guide, Section: Configuration > Security > Data leak prevention. Details the hierarchical configuration of data patterns, dictionaries, and profiles.

FortiOS 7.2 Administration Guide, Section: Security Profiles > Data leak prevention. Explains the creation order: DLP Data Types (Patterns) -> DLP Dictionaries -> DLP Profiles -> DLP Rules.

FortiOS 7.0 Release Notes, Section: Changes in default behavior > DLP. Documents the architectural change where the "DLP sensor" object was officially deprecated and merged into the "DLP profile," proving "DLP Sensor" is the invalid option for current FortiSASE deployments.