Enforcement

After you approve a policy, choose where Tero enforces it. Some options apply on the next sync or provider API update, while others hand the work to your engineers.

Enforce at edge

Execute policies before data leaves your network. Drop, sample, transform, or redact data.

Enforce in provider

Configure exclusion filters and routing rules through the provider API.

Open PRs

Fix instrumentation at the source. Tero opens the PR, your team reviews.

Create tickets

Assign work to engineers in Linear or GitHub Issues.

Notify

Alert teams in Slack or email.

Set SLOs

Quality targets for teams to meet. Track progress over time.

Choose an enforcement method

Method	Resolution	Reversible	Best for
Enforce at edge	Next sync	Reversible	Most policy categories
Enforce in provider	Provider API	Reversible	No Edge deployed
Open PRs	Variable	Reversible	Code-level fixes
Create tickets	Variable	N/A	Human decisions needed
Notify	Variable	N/A	Awareness
Set SLOs	Ongoing	Reversible	Long-term tracking

Tero recommends an enforcement method for each policy category. You can override, combine, or change later.

Overview Enforce at edge

Introduction

Issues

Master Catalog

Policies

Integrations

Reference

Enforce at edge

Enforce in provider

Open PRs

Create tickets

Notify

Set SLOs

Choose an enforcement method

Enforce at edge

Enforce in provider

Open PRs

Create tickets

Notify

Set SLOs

​Choose an enforcement method

Choose an enforcement method