The correct answer is A. Not contain . In Forcepoint DSPM, detector creation uses inclusion and exclusion logic to control what should trigger a detector match. The Contain field defines the positive match criteria: the keywords, phrases, regular expressions, extensions, or path terms that the detector should search for. The Not Contain field provides the negative condition: terms or criteria that should be ignored even when the broader detector logic would otherwise match.

Forcepoint’s DSPM documentation for Content Detectors states that if there are terms the detector should ignore, they are set in the Not Contain field. The same concept appears in Path Detectors , where administrators define the search method, populate Contain with triggering terms, and then use Not Contain to exclude terms from matching.

This matters operationally because detectors can otherwise generate excessive or misleading matches. For example, a detector looking for payroll-related content may include “salary” or “compensation” in Contain , while excluding harmless template, archive, or test terms in Not Contain . Not Add , Except , and Exclude are not the documented detector-configuration field names. References/topics: Administration > Detectors, Content Detectors, Path Detectors, Contain/Not Contain logic, AI Mesh detector contribution .