The “Security rules” section

The system lets you create exclusion rules for working with results in the product. The Security rules section is for managing security rules that apply to vulnerabilities and other security issues in projects. You can use these rules to temporarily or permanently ignore specific types of issues based on their priority or other criteria.

This section is for managing rules that apply to vulnerabilities and other security issues in projects.

info

Security rules apply to issues after a scan finishes, if you run the scan from TRON.ASOC, and you receive a report with the scan results. 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 shown below.

Column	Description
Name	The name or identifier of the security rule
Category	The category of issue to which the rule applies
Source	The scan source to which the rule applies
CVE	The unique vulnerability identifier in the CVE database
CWE	The CWE (Common Weakness Enumeration) code
Status	The rule's activity status
Number of uses	The number of times the rule has been applied
Expiration date	The date when the rule expires
Scope	The project 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 using the From and To fields. Enter values in the DD.MM.YYYY format;
• Updated—the period when the security rule was updated; configure it using the From and To fields. Enter values in the DD.MM.YYYY format;
• Expiration—the period when the security rule expires; configure it using the From and To fields. Enter values in the DD.MM.YYYY format;
• Category;
• Source;
• CVE;
• CWE;
• Status.