You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It would be nice if we could move the insights that are present available in the UI to each scanner instead. It would be much simpler to maintain and develop a scanner and add the insight for that directly into the scanner. As it is now, the development of a scanner requires both the scanner code and UI change.
Describe the solution you'd like
I propose enhancing the Scanner base class in strelka.py to support scanner-specific insights. Each scanner would maintain its own list of insights about the files it analyses, which would then be automatically included in the scanner's event output. Add an insights list attribute to the scanner base class. Then update the UI to read these insights instead of populating and have the logic for them in the UI.
By moving insights directly into scanners, we leverage the domain expertise of each scanner's code, improve maintainability, and make the system more extensible as new scanners will automatically contribute relevant insights.
Does this sound like something that is doable or am I missing something crucial?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It would be nice if we could move the insights that are present available in the UI to each scanner instead. It would be much simpler to maintain and develop a scanner and add the insight for that directly into the scanner. As it is now, the development of a scanner requires both the scanner code and UI change.
Describe the solution you'd like
I propose enhancing the Scanner base class in strelka.py to support scanner-specific insights. Each scanner would maintain its own list of insights about the files it analyses, which would then be automatically included in the scanner's event output. Add an insights list attribute to the scanner base class. Then update the UI to read these insights instead of populating and have the logic for them in the UI.
By moving insights directly into scanners, we leverage the domain expertise of each scanner's code, improve maintainability, and make the system more extensible as new scanners will automatically contribute relevant insights.
Does this sound like something that is doable or am I missing something crucial?
The text was updated successfully, but these errors were encountered: