Replies: 3 comments 2 replies
-
|
Those are quite many smaller components or functionalities sticked together, and the problem is that all of them are quite specialized. We will be working on a plugin system in H2 which might allow those features to still be implemented. |
Beta Was this translation helpful? Give feedback.
-
|
That would be absolutely awesome. If you like I can split out this into multiple discussion items. Or would you like me to refine them in this thread into separate RFCs?
Unixerius B.V.
Bolderweg 2, kamer E.26, 1332 AT, Almere
KVK 63637456
…________________________________
From: Aron Molnar ***@***.***>
Sent: Wednesday, June 19, 2024 12:05:08 PM
To: Syslifters/sysreptor ***@***.***>
Cc: Tess Sluijter-Stek ***@***.***>; Author ***@***.***>
Subject: Re: [Syslifters/sysreptor] In-app overview of findings per customer (Discussion #272)
Those are quite many smaller components or functionalities sticked together, and the problem is that all of them are quite specialized.
We will be working on a plugin system in H2 which might allow those features to still be implemented.
—
Reply to this email directly, view it on GitHub<#272 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXLLXPJG7GLHJWFBKXJMJ33ZIFJVJAVCNFSM6AAAAABJRRGQ3WVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQMJVHAYDG>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
No thats good as it is. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome!
So far, your team has done nothing but impress my colleagues with your response times and effectiveness!
Unixerius B.V.
Bolderweg 2, kamer E.26, 1332 AT, Almere
KVK 63637456
…________________________________
From: Aron Molnar ***@***.***>
Sent: Thursday, June 20, 2024 7:37:01 AM
To: Syslifters/sysreptor ***@***.***>
Cc: Tess Sluijter-Stek ***@***.***>; Author ***@***.***>
Subject: Re: [Syslifters/sysreptor] In-app overview of findings per customer (Discussion #272)
No thats good as it is.
We might split it in the future if parts are implemented.
—
Reply to this email directly, view it on GitHub<#272 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXLLXPIPOB6AMV2M3GRMRSDZIJS73AVCNFSM6AAAAABJRRGQ3WVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQMRUGUZDG>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you! We're very happy to hear that. |
Beta Was this translation helpful? Give feedback.
-
Tieing this suggestion in with the suggestion of having a Customer object -> #36
It wouldn't just be great to group engagements/reports per customer. It would also be awesome if we can get an in-app overview of all pentest findings reported for this customer. That will make it easier to for example find everything we've ever reported, or to make a quick update to the right finding.
Plus, management just really likes it when we can offer a most recent overview of which pentest findings we have and what their status is with the customer (if we know).
It also hinged on findings have a unique ID that auto-increments, which I believe was requested elsewhere.
In short a table per customer like:
| Finding ID | Engagement / Project | Date reported | Type | Severity / CVSS | Summary description | Latest status |
| MM-SS-2024-01 | Scary Shack | 01/01/2024 | Injection | 8.9 | Unauthenticated SQL injection on login page | Open |
| MM-SS-2024-02 | Scary Shack | 01/01/2024 | Injection | 7.8 | Authenticated SQL injection on product search page | Open |
Beta Was this translation helpful? Give feedback.
All reactions