Capture changes to a project's protected tags in project-level audit events

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Problem to solve

Protected tags allow control over who has permission to create tags as well as preventing accidental update or deletion once created. Each rule allows you to match either an individual tag name, or use wildcards to control multiple tags at once. Given the nature of these tags being protected, there's an inherent need to track the activity around these actions in audit events.

Intended users

• Cameron (Compliance Manager)
• Sidney (Systems Administrator)
• Sam (Security Analyst)

Proposal

Add protected tag events to audit events at the project level.

We should capture:

• Who created/modified/removed a protected tag
• Who changed allowed to create from X to Y

We may need separate issues to keep the scope small and iterative for this.

Further details