Skip to main content
Version: 1.6.1

The “Security rules” section

The system lets you create exception rules for working with results in the product. The Security rules section is designed to manage security rules that apply to vulnerabilities and other security issues in projects. This lets you ignore specific types of issues temporarily or permanently based on their priority or other criteria.

Security rules

The section is designed to manage rules that apply to vulnerabilities and other security issues in projects.

info

Security rules apply to issues after scanning is complete (when you start the scan from TRON.ASOC) and the scan results report is available. For more information, see Scan results.

Security rules table structure​

Security rules appear in a table in the Security rules section. The table includes the columns listed below.

ColumnDescription
NameThe name or identifier of the security rule
CategoryThe category of issue to which the rule applies
SourceThe scanning source to which the rule applies
CVEThe unique vulnerability identifier in the CVE database
CWEThe CWE code (Common Weakness Enumeration)
StatusThe rule's activity status
Number of usesThe number of times the rule has been applied
Expiration dateThe date when the rule expires
ScopeThe scope of projects

You can hide the columns you need, except for the Name column, and reorder them.

Filtering security rules​

You can configure which security rules appear by using the following filters:

  • Created—the period when the security rule was created; configure it with the From and To fields using the DD.MM.YYYY format;
  • Updated—the period when the security rule was updated; configure it with the From and To fields using the DD.MM.YYYY format;
  • Expiration—the period when the security rule expires; configure it with the From and To fields using the DD.MM.YYYY format;
  • Category;
  • Source;
  • CVE;
  • CWE;
  • Status.

Security rule filters