The first step in configuring the Data Register is Creating Security Posture Policies . In Forcepoint DSPM, the Data Register is the governance workspace where an organization defines and manages its most important data assets, commonly described as “crown jewels.” Forcepoint’s Data Register structure lists three main areas in order: Security Posture Policies , Data Asset Inventory , and Review Status , making Security Posture Policies the starting point for register configuration.

A Security Posture Policy creates the formal representation of a governed data asset. The documented workflow is to navigate to Policy Center > Data Register > Security Posture Policies , click Add new Security Posture Policy , and define required details such as Asset Name , Department , Data Owner , and Data Mapping using a GQL query.

The other choices are not the first Data Register configuration step. Pattern Matching belongs to detection and classification logic, not Data Register setup. Data Mapping is important, but it is configured under Compliance Hub as the framework for Data Asset Inventory metadata fields. Reviewing policies in the Data Asset Inventory occurs after policies and asset definitions exist. References/topics: Policy Center, Data Register, Security Posture Policies, Data Asset Inventory, Data Mapping, Data Ownership .

A detector in Forcepoint DSPM is a rule-based classification component used during scanning to identify files whose content or path matches defined detection logic. The correct answer is B because detectors are designed to locate specific patterns, words, or expressions and then contribute to classification/tagging outcomes. Forcepoint describes Detector Groups in AI Mesh as components where “detectors assess both the file path and its contents using rule-based logic, such as regular expressions and keywords,” returning a match when the content fits the defined patterns.

This is distinct from AI classifiers, which infer sensitive-data meaning from broader semantic or machine-learning signals. Detectors are the more deterministic mechanism: they look for defined indicators such as a keyword, phrase, regular expression, or path element. Forcepoint release notes also describe detector functionality as allowing content or path search when creating a detector, including an example where adding the word Archive to a detector can tag files located in an Archive folder.

The other options confuse detectors with unrelated platform functions. Detectors do not create credential tags specifically, optimize network throughput, block files for speed, or increase storage capacity. References/topics: Detectors, Pattern Matching, AI Mesh, Classification Tags, Content and Path Search .