Skip to main content
Version: 1.5.1

Customization

In the Customization section, users can:

  • add, edit, or delete statuses for security issues;
  • add, edit, or delete transitions between statuses;
  • import or export statuses and transitions between statuses;
  • add, edit, or delete project layer templates;
  • add, edit, or delete project fields.

The section contains the following subsections:

  • Status model subsection;
  • Project layer templates subsection;
  • Project fields subsection.

Status model subsection​

This subsection contains two tabs:

  • Statuses tab;
  • Transitions tab.

Statuses tab​

This tab displays a list of user-defined statuses for security issues. The status table contains the following columns:

  • Status name—the name and description of the status
  • Category—specifies whether the status is open or closed. The system includes the following status categories:
  • Open—an open security issue status, for example, New
  • Closed—a closed security issue status, for example, Fixed
info

The system must have at least one status in each category because these statuses show whether a security issue is active and are used to collect statistics for reports and dashboards. To enforce this requirement, the system doesn't allow users to delete the New and Fixed statuses.

  • Universal transitions—specifies whether users can transition to the status from any other status
  • Transitions—the number of related transitions
info

When users select the number of transitions, the system opens a page with a list of related transitions. If the number of transitions is 0 but the universal transition is enabled for the status, the value appears in gray. If the number of transitions is 0 and the universal transition is disabled for the status, the value appears in red. This indicates that users can't assign the status to a security issue because it isn't part of the status workflow.

By default, the system includes the following statuses:

  • New—a newly detected issue that requires review
info

The system automatically assigns the New status to issues it detects for the first time.

  • In progress—the issue is being worked on, analyzed, or fixed
  • Manual—the issue requires manual review because automatic detection isn't sufficient
  • Confirmed—the issue has been confirmed and requires remediation
  • False-positive—a false detection; no issue exists
  • Duplicate—a duplicate of an existing issue
  • Suppressed—the issue was excluded by a security rule
  • Risk accepted—the risk has been accepted, so remediation isn't required
  • Fixed—the issue has been resolved
info

The system automatically assigns the Fixed status to issues it doesn't detect during the next scan.

  • Reopen—the issue was detected again
danger

The Duplicate, False-Positive, and Suppressed by security policy indicators (in the detailed security issue information) aren't issue statuses. Using these indicators doesn't change the issue status. To work with these indicators as statuses, we recommend using the corresponding statuses and, if necessary, adding custom statuses to the status model.

Statuses

Transitions tab​

The Transitions tab displays a list of user-defined transitions from one status to another as part of the status model for security issues. The transition table contains the following columns:

  • Transition—the name of the transition
  • From—the status or statuses from which the transition is configured.
  • To—the status or statuses to which the transition is configured.
  • Groups—specifies which groups can use the transition. If no values are specified, all system users can use the transition.
caution

By default, the system doesn't include any configured transitions. Users can transition between the default system universal statuses.

Transitions

Project layer templates subsection​

The Project layer templates subsection contains a list of user-defined templates for project layers. The table lists all templates with the following characteristics:

  • Template—the template name and description;
  • Layer type from the following options:
    • Landscape;
    • Network segment;
    • Orchestrator;
    • Namespace;
    • Service;
    • Gateway;
    • Release;
    • Virtual machine;
    • Container;
    • Pod;
    • Docker;
    • Storage;
    • Database;
  • Information fields—the number of additional fields or field groups displayed on the Information tab in the template;
  • Requirements—the number of additional requirements or requirement groups displayed on the Requirements tab in the template, if applicable.

Project layer templates

Project fields subsection​

In the Project fields subsection, users can create, configure, and delete user-defined project fields. By default, the system includes only system fields:

  • Project code;
  • Project name;
  • Description;
  • Tags.

Project fields