Skip to content

docs(psirt): who can use PSIRT, and why the permission beats the role #15741

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Maffooch merged 1 commit into from
Aug 19, 2026
Merged

docs(psirt): who can use PSIRT, and why the permission beats the role #15741

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions docs/content/psirt/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,36 @@ If the entries are visible but locked, that is the other gate: the licence.
PSIRT needs the **PSIRT Advisory Engine** entitlement, and a locked entry
explains what to ask for.

## Who can use PSIRT

Three things admit a user, and only one of them needs to be true:

- the **PSIRT** configuration permission,
- a global **Maintainer** or **Owner** role, or
- superuser.

**Prefer the configuration permission.** A global Maintainer role is write access
to every asset in the instance, so granting it to give somebody PSIRT hands them
the rest of the product as well. The PSIRT permission grants PSIRT and nothing
else.

It comes in two halves, assignable separately from **Settings → User Management**
on a user or — more usefully — on a group:

| Permission | Admits |
|---|---|
| **View PSIRT** | Reading every PSIRT surface: the advisory queue, exposure verdicts, cases, components, rules. |
| **Change PSIRT** | Everything View admits, plus writing: suppressing advisories, authoring feed and matching rules, opening cases, publishing advisories. |

View is genuinely read-only. An analyst who should see whether you are affected,
without being able to suppress an advisory or publish one, gets View alone.

The licence is checked *before* any of this and is not a permission: with no
**PSIRT Advisory Engine** entitlement, PSIRT is closed to everyone including
superusers.

The permission appears in the picker only when the PSIRT feature flag is on.

## How it fits together

1. **[Advisory Feeds](feeds/)** — choose which publishers to poll. Every source
Expand Down
Loading