reNgine-ng is an automated reconnaissance framework for web applications with a focus on highly configurable streamlined recon process via Engines, recon data correlation and organization, continuous monitoring, backed by a database, and simple yet intuitive User Interface.
GNU General Public License v3.0
12
stars
6
forks
source link
feat(ui): Grouping in a tree structure - Let's be very organised #50
At the moment it is quite confusing how Rengine is organized.
Example:
Targets menu do not have grouped assets in a tree structure, currently you have for example target a.com with Project X, target b.com with Project Y, after you have target c.com with project X again and so on.
This is not so productive, because you cannot see the entire structure of that asset (tree structure).
Proposed Suggestion
Think how easy it would be if every asset from Target Menu, for example a.com to be listed in a left sidebar and when you click a.com on right side to have everything of that target:
Recent scan (with date)
Target Summary
Subscan History (badge with: not scanned yet > filter by: show scanned / not scanned)
All subdomains
All Endpoints
Scan Findings
Initiate Scan
Thus the Scan History & Vulnerabilities menu which basically displays global results from all assets can be moved e.g. to the Global Overview, or reordered to be directly listed in the main Dashboard.
This is how the big players organise structure > tree structure: think Burp Pro, for example (in the Burp Target menu you have everything in a tree structure). SOCRADAR does the same, and the examples can go on.
Jira & Confluence (the masters of organization) also organize in a tree structure (Issue Navigator).
My opinion is that we do not have to reinvent the wheel.
Is there an existing feature or issue for this?
Expected feature
Proposed by @carboncrystal
At the moment it is quite confusing how Rengine is organized.
Example: Targets menu do not have grouped assets in a tree structure, currently you have for example target a.com with Project X, target b.com with Project Y, after you have target c.com with project X again and so on. This is not so productive, because you cannot see the entire structure of that asset (tree structure).
Proposed Suggestion
Think how easy it would be if every asset from Target Menu, for example a.com to be listed in a left sidebar and when you click a.com on right side to have everything of that target:
Thus the Scan History & Vulnerabilities menu which basically displays global results from all assets can be moved e.g. to the Global Overview, or reordered to be directly listed in the main Dashboard.
This is how the big players organise structure > tree structure: think Burp Pro, for example (in the Burp Target menu you have everything in a tree structure). SOCRADAR does the same, and the examples can go on. Jira & Confluence (the masters of organization) also organize in a tree structure (Issue Navigator).
My opinion is that we do not have to reinvent the wheel.
SOCRADAR screens
Alternative solutions
No response
Anything else?
No response