Skip to content

five-c: Create extended policy rules set #411

Closed

Description

@pombredanne

Create extended rules set using the engine to support one workflow.
Deploy for test usage

Activity

  1. self-assigned this
    on Jul 6, 2026
  2. moved this to In progress in 00-AboutCodePlanneron Jul 6, 2026
  3. tdruez commented on Jul 24, 2026

    @tdruez
    Contributor

    Extended policy rules set implemented in:

    Changes

    • Three new vulnerability rules covering vulnerability detection, unresolved triage, and stale high-risk vulnerabilities
    • Configurable parameters per rule (minimum risk score, maximum days unaddressed) resolved from the per-dataspace configuration
    • detected_date field added to package-vulnerability links to track when a vulnerability was first recorded
    • Inventory filter by policy rule to show only packages that triggered a specific rule, shared across the product relation filtersets
    • Compliance tab badge updated to "triggered" with color reflecting the highest violation severity (red for error, yellow for warning)
    • Violation table ordering follows the rule registry order rather than alphabetical
    • Violation count on the dashboard now excludes obsolete rule types no longer present in the registry

    New extended policy rules

    Rule Severity Description
    Vulnerability Detected Error Packages with at least one known vulnerability, with an optional minimum risk score
    Vulnerability Unresolved Warning Packages with known vulnerabilities and no completed vulnerability analysis
    Vulnerability Stale Error Packages with high-risk vulnerabilities unaddressed beyond a configured number of days

    All rules count the number of affected packages in a product. A rule triggers when that count exceeds the configured threshold (default: 0, meaning any match triggers).

    Screens

    Screenshot 2026-07-24 at 09 23 15 Screenshot 2026-07-24 at 09 23 46 Screenshot 2026-07-24 at 09 24 07
  4. pombredanne commented on Jul 29, 2026

    @pombredanne
    MemberAuthor

    Thanks!

  5. moved this from Done to Reviewed in 00-AboutCodePlanneron Jul 29, 2026
  6. moved this from Reviewed to Done in 00-AboutCodePlanneron Aug 3, 2026
  7. moved this from Done to Reviewed in 00-AboutCodePlanneron Aug 4, 2026
  8. moved this from Reviewed to Validated in 00-AboutCodePlanneron Aug 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions