Use tags and annotations
Compose security policies with surgical precision using tags and annotations
Use tags and annotations
Tags and annotations are the building blocks of precise policy composition in Threatmatic. They allow you to group and label resources dynamically, so policies stay accurate as your environment changes.
Tags vs. annotations
| Tags | Annotations | |
|---|---|---|
| Purpose | Classify and group resources | Attach metadata for policy context |
| Applied to | Devices, users, circuits, applications | Policies, flows, events |
| Used in policy | As scope or match targets | As conditions or audit context |
| Example | env=prod, role=contractor | reason=exception, ticket=INC-1234 |
Working with tags
Apply a tag to a device
- Go to Devices and click a device name
- Under Tags, click Add Tag
- Enter a key-value pair (e.g.
env=prod) or a simple label (e.g.contractor) - Click Save
Tags can also be applied in bulk:
- Select multiple devices using the checkbox
- Click Bulk Actions → Add Tag
Apply a tag to a user group
- Go to Organization → Identity → Groups
- Click a group name
- Under Tags, click Add Tag
Use tags in a policy rule
When creating a policy rule, set the Scope or Match field to a tag:
- Scope:
tag: env=prod— applies the rule to all production devices - Match:
tag: application=custom-erp— matches traffic to/from a tagged application
Tags are evaluated dynamically — if a device's tags change, policies update automatically.
Working with annotations
Add an annotation to a policy
- Go to Policies and open a policy
- Click Annotate
- Add key-value pairs (e.g.
owner=security-team,review-date=2025-Q3)
Annotations appear in audit logs and exports, making it easy to trace policy decisions back to their business context.
Add an annotation to an exception
When creating an Allow rule that overrides a Block rule, document the reason:
- Add the
Allowrule - Click Annotate Rule
- Enter
reason=approved-exceptionandticket=INC-1234
Annotations are free-form but consistent conventions across your team make
audit reviews significantly faster. Consider defining a standard set of
annotation keys (e.g. owner, reason, expires, ticket).
Next steps
How is this guide?
Last updated on