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.

The section is designed to manage rules that apply to vulnerabilities and other security issues in projects.
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.
| Column | Description |
|---|---|
| Name | The name or identifier of the security rule |
| Category | The category of issue to which the rule applies |
| Source | The scanning source to which the rule applies |
| CVE | The unique vulnerability identifier in the CVE database |
| CWE | The CWE code (Common Weakness Enumeration) |
| 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 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.YYYYformat; - Updated—the period when the security rule was updated; configure it with the From and To fields using the
DD.MM.YYYYformat; - Expiration—the period when the security rule expires; configure it with the From and To fields using the
DD.MM.YYYYformat; - Category;
- Source;
- CVE;
- CWE;
- Status.
