Skip to main content
Version: 1.7

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;
  • Project layer templates;
  • Project fields.

Status model subsection​

This subsection contains two tabs:

  • Statuses;
  • Transitions.

Statuses tab​

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

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

At least one status from each category must exist because the categories show whether a security issue is active and support statistics collection for reports and dashboards. For this reason, the system doesn't allow you to delete the New, Fixed, and Reopen statuses.

  • Universal transitions—indicates whether you can transition to the status from any other status;
  • Transitions—the number of associated transitions.
info

When you select the number of transitions, the system opens a page that displays a list of associated 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 you can't assign the status to a security issue because it isn't part of the status workflow.

The system includes the following statuses by default:

  • New—a newly detected issue that requires review
info

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

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

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

  • Reopen—the issue was detected again
danger

The Duplicate, False-Positive, and Covered 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, use the corresponding statuses and, if necessary, add custom statuses to the status model.

Statuses

Transitions tab​

The Transitions tab displays a list of custom transitions from one status to another within the status model for security issues. The transitions 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—indicates 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 configured transitions. You can transition between the default universal system statuses.

Transitions

Project layer templates subsection​

The Project layer templates subsection contains a list of custom templates for project layers. The table displays all templates with the following characteristics:

  • Template - the name and description of the template;
  • Layer type from the following options:
    • Landscape - Landscape;
    • Network segment - Network segment;
    • Orchestrator - Orchestrator;
    • Namespace - Namespace;
    • Service - Service;
    • Gateway - Gateway;
    • Release - Release;
    • Virtual machine - Virtual machine;
    • Container - Container;
    • Pod - Pod;
    • Docker - Docker;
    • Storage - Storage;
    • Database - 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, when applicable.

Project layer templates

Project fields subsection​

In the Project fields subsection, you can create, configure, and delete custom project fields. By default, the system includes only system fields:

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

Project fields