Web Report refactor #2264
domwhewell-sage
started this conversation in
Ideas
Replies: 1 comment
-
|
I like this idea, but it might be a while before I get to it. I honestly didn't know people were really using the web report, I think it could definitely be improved and a screenshot would be perfect. I'd probably wait until we replace gowitness with whatever our permanent screenshot solutions will be. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I was looking to open an issue to have
WEBSCREENSHOTincluded in the web_report output for eachURL.However it also occurred to me that Code assets (
CODE_REPOSITORY&MOBILE_APP) could be included aswell i.e.Web Assets:
URLWEBSCREENSHOTTECHNOLOGYFINDINGVULNERABILITYCode Assets:
CODE_REPOSITORYFINDINGVULNERABILITYMOBILE_APPFINDINGVULNERABILITYI think to do this the current iteration of the html report needs to be refactored? The output module should only need to consume
URL,CODE_REPOSITORYandMOBILE_APPevents then for each of those crawl down the chain to add any of the other events it comes across.What do you think? I know you guys are working on a bbot server this could be something to save for that
Beta Was this translation helpful? Give feedback.
All reactions