Docs

Policies and suppressions

This guide explains how to distinguish accepted exceptions from untracked regressions.

WindowsmacOSLinux
PoliciesSuppressionsFindingsSecurity

How policy packs, premium rules, suppression workflow, and operator intent should work together in the current product.

  • Suppression workflow intent
  • Why notes matter
  • Plan-linked policy surface
  • How suppressions affect later review
Applies to
WindowsmacOSLinux
Covers
PoliciesSuppressionsFindingsSecurity

Policies and suppressions

Why suppressions exist

Suppressions exist because some findings are:

  • known
  • accepted
  • temporary
  • out of scope for the current owner

What a good suppression should capture

A useful suppression records:

  • what is being suppressed
  • why it is being suppressed
  • enough operator context to understand it later

What suppressions should not do

Suppressions should not:

  • erase the historical existence of the issue
  • hide an unknown problem without review
  • become the default response to noisy findings