Security Advisory Application
Explanation
The Security Advisory Application lets a security team track its advisories up to their disclosure, as described for its users. An administrator sets it up so that advisories stay private until they are disclosed, imports them from GitHub, and provides the release dates its embargo dates are computed from.
Advisory Spaces
The application uses two spaces, set in its configuration:
- the security entries space holds the advisories and must be viewable only by the security team;
- the disclosed entries space holds the public copies of the disclosed advisories and must be viewable by everyone.
Release Dates
The application reads the release dates of the patched versions, from which it computes the embargo dates, from the Release Notes Application, which is installed with it, and otherwise from the extension repositories, for Maven packages.
GitHub Import
Once a day, the application imports the security advisories of the GitHub repositories set by an administrator, with a GitHub token for each organization.
Administering the application:
- Set Up the Security Advisory Application restricts the spaces and configures the security group, the embargo duration and the GitHub import.
- Map GitHub Users to XWiki Users lets imported advisories get an assignee.
- Security Advisory Configuration describes every setting of the administration section.
More
To find more about the current topic, you can search or use the table below and filter the columns to narrow your choices.