Jannik Hollenbach

Hi sorry for the slow response, yes that is definitely an issue, thank you for raising an issue 👍 We haven't seriously considered that there might be scans which can...

> I understand it would impose a significant change, but how feasible would it be to generate the presigned-urls lazily whenever a Scan finishes as opposed to when it starts?...

Hi 👋 Thank you for the the feedback, yes we are also a bit fed up with this limitation, see the disclaimer on the API Spec Page of the ScheduledScan:...

I'm not sure I understand that correctly. If Nikto doesn't find a robots.txt it doesn't create a result file? Even if Nikto identified other findings?

ah ok, not sure if that is a bug on our end or on nikto's. Would recommend to switch to nuclei for that , at least for the moment: `nuclei...

Haven't tested this, but should this work with the normal elasticsearch hook? API should be largely the same, as far as I know.

Good catch, from my side basically a short yes to all three points 🙂 Ideally all three would behave the same on all of these subjects. On the first point,...

@cfarrend Ahh interessting, I was always just looking at the chart on Artifact Hub (https://artifacthub.io/packages/helm/minio/minio) which hasn't been updated in a while, but it seems that they have since migrated...

Related: It is possible to define extended resources for for resource limits: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#extended-resources This should probably be possible to use to fit most of the requirements of this issue.

Hi 👋 That is a interesting proposal. What happens in the case that the remote target goes down during the scan is currently undefined / completly dictated by the behavior...