Skip to main content

Data Sensitivity

Data Sensitivity labels roll up other labels into an ordered scale of critical, high, moderate, low, or unrestricted. This helps analysts and policies focus on the most important data first. In DSPM EA you can use any existing labels (Data Type, Data Provenance, Data Pattern, or custom label sets) to define how sensitivity should be assigned.

What you can do​

  • Start from Cyberhaven defaults for each sensitivity level, then adjust them to fit your environment.
  • Open a sensitivity label to see its rule definition, current matches, and unique locations.
  • Edit a label definition to add or remove label conditions such as specific Data Types together with a provenance requirement.
  • Enable or disable a label while you test changes and use the Test and tune dialog to preview results.
  • Add OR groups when you need more than one rule set to trigger the same sensitivity level.
  • Use sensitivity labels in reporting or policies to prioritize investigations.

Edit definitions and Test and tune​

  • Use Edit definition to add or remove conditions. Each condition can reference Data Type, Data Provenance, Data Pattern, or custom labels. Add values for each condition so the rule knows what to match.
  • Use AND when all listed conditions must be true. Example: Data Type is any of Financial Documents and Data Provenance is Internal.
  • Use OR when any one block of conditions can trigger the label. Build separate blocks and place OR between them to support multiple paths.
  • Switch between UI and CEL if you want to enter an expression instead of picking values from the list.
  • Keep a label Enabled while testing so you see how matches change. Disable it if you want to save a draft without applying it.
  • In Test and tune, review the rule, try different condition blocks, and save updates when the previewed behavior matches your intent.

Changes take effect as soon as you save, so you can refine mappings based on observed results.

Limitations​

  • The five level scale is fixed in EA, but the rules that map labels to those levels are configurable.