Feature request : Structured and Reusable “Affected Components” Section

[MTlyx]

Hello,

I would like to suggest an improvement regarding how “Affected Components” are handled in findings.

Currently, affected components (such as hosts or services) need to be entered manually for each finding. Instead, I would like to request the possibility to define a structured list of components in the template settings (for example within Sections).

The idea would be:

• Add a dedicated “Affected Components” section in the template configuration.
• Allow defining machines/components there.
• Each machine could optionally be associated with a port and/or service.
• These predefined components would then be reusable in findings.
• In a finding, the “Affected Components” field would work like the CWE selector: a dropdown list where one or multiple predefined components can be selected.

This would:

• Improve consistency across the report
• Avoid repetitive manual input
• Reduce formatting mistakes
• Make reporting more structured and efficient

[MWedl]

Hi, SysReptor currently does not natively support mapping affected components to a predefined list. However, here are some suggestions to achieve a similar behavior using existing features.

You could customize your design to create a custom affected_components2 field (and delete the built-in one) with type list[combobox] (instead of list[string]). Comboboxes suggest values used in other findings. You need to write the affected component only once in the first findings to use it, in following findings it gets suggested in a dropdown selection.

Note that combobox values are strings. If you need a mapping to a affected component objects defined in a separate section, you could achieve that during PDF rendering. The idea is to define a affected_components_definition field as list[object[id, host, port, ...]] and reference the id via comboboxes in findings. The resolution of the mapping from id -> object can be done in the desing's HTML+Vue template via JavaScript expressions, which is executed during PDF rendering. This solution, however, is more complex and I recommend to stick to just comboboxes if this is sufficient for you.