Skip to main content
Version: 1.6

Security rules section

The system lets you create exclusion 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 temporarily or permanently ignore specific types of issues based on their priority or other criteria.

Security rules

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

info

Security rules apply to issues after scanning finishes (when you start the scan from TRON.ASOC) and the system receives a report with the scan results. For more information, see Scan results.

Security rules table structure​

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

ColumnDescription
NameName or identifier of the security rule
CategoryCategory of the issue to which the rule applies
SourceScanning source to which the rule applies
CVEUnique vulnerability identifier in the CVE database
CWECWE code (Common Weakness Enumeration)
StatusRule activity status
Number of usesNumber of times the rule has been used
Expiration dateDate when the rule stops applying
ScopeProject scope

You can hide the columns you don't 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