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.
Security rules apply to issues after scanning finishes (when launched from TRON.ASOC) and the scan results report is received. 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 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 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 active status |
| Number of uses | The number of times the rule was applied |
| Expiration date | The date when the rule stops applying |
| Scope | The scope of projects |
Users can hide columns they don't need, except for the Name column, and change their order.
Filtering security rules
Users 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. Use the
DD.MM.YYYYformat for the values. - Updated—the period when the security rule was updated; configure it with the From and To fields. Use the
DD.MM.YYYYformat for the values. - Expiration date—the period when the security rule expires; configure it with the From and To fields. Use the
DD.MM.YYYYformat for the values. - Category
- Source
- CVE
- CWE
- Status