Update dashlord.yml - disable zap & nmap modules #177
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The fact of openly publishing information that could assist malicious actors in attacking systems raises real questions in terms of cyber risk management. It would seem more appropriate to only publish certain sensible elements on a private Dashlord space with authentication. requested.
Of course, anyone can run a Zap or nmap scan, but these scans are noisy and detectable. The current state of the beta.gouv.fr instance of Dashlord tends to facilitate attackers by helping them target vulnerable and easily compromisable assets. That's why we're requesting the deactivation of these scans for now.