Compliance tags in Forcepoint DSPM are used to associate detected data patterns with regulatory or compliance obligations. The correct answer is B because these tags help the platform identify files and data objects that may fall under privacy, security, or industry-specific regulatory regimes. Forcepoint’s pattern-matching terminology defines Compliance as tags that help organizations conform to regulatory regimes, and gives the example of applying tags such as GDPR/PII to a Social Security number pattern so related documents can be identified.
Operationally, this means a pattern is not only detecting a technical string, such as a national identifier, payment card number, or health-related value; it is also attaching compliance meaning to the match. That compliance context can then support classification, filtering, analytics, remediation prioritisation, and audit evidence. Forcepoint also states that when adding a new pattern, selected Classification, Compliance, and Distribution values can override machine-learning model output during scans, making the assigned tags authoritative for scan results.
The other options are adjacent but incorrect. User monitoring and reporting are downstream analytics activities, encryption policy management is not the core purpose of pattern compliance tagging, and user credentials are handled through identity and access management workflows. References/topics: Pattern Matching, Compliance Tags, Classification Model, AI Mesh, Regulatory Data Identification .
