Skip to content

Violations

Violations record operations outside the effective policy. Observe mode allows and reports them. Enforce mode denies where hooks support it and can terminate tasks by default. ENDURA_SENSOR_KILL_TASK=false disables termination, retaining direct denial.

Investigate a Violation

Filter by outcome, pipeline, process, and time; search, sort, select columns, paginate, or export CSV. Build/workload details show related violations. Open an event for expression, outcome, process ancestry, run context, timestamps, and policy.

Repeated events are deduplicated. Unique selects the latest signature per pipeline for build violations or per workload for workload violations; it does not mean a single occurrence.

Operators can delete in-scope violations; Administrators can delete any. Export audit records first.

Permit a Build Violation

Permitting changes policy, without suppressing or changing historical events. It requires an assigned pipeline policy and its owner or an Administrator; workloads are excluded.

  1. Select up to 1,000 violations from one pipeline.
  2. Choose exact, parent, or wildcard rule scope.
  3. Review/edit the diff, enter a change description, validate, and apply.

Team Server verifies pipeline membership and policy validity, then creates a new version. See proposal scopes.