René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"➹ Encrypt / Anonymize all positive password for \"positive\" NCrack credential findings","articleBody":"\u003c!--\r\nThank you for reporting an issue in our documentation 🙌\r\n\r\nBefore opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.\r\n--\u003e\r\n\r\n**Is your feature request related to a problem? Please describe.**\r\nThe [NCrack Bruteforce](https://docs.securecodebox.io/docs/scanners/ncrack) scanner is great to identify weak credentials for services (like SSH) deployed in a given infrastructure environment. But the credential findings itself maybe can be a problem if they are public accessible in a vulnerability management 🤔.\r\n\r\n**Describe the solution you'd like**\r\nIt would be great to implement a new configuration option which enables the security tester (DevSecOps) to configure if the identified credential findings must be encrypted / anonymized. \r\n\r\n```yaml\r\nscannerJob:\r\n  secureFindings:\r\n     enabled: true\r\n     type: anonymize\r\n```\r\n\r\n**Describe alternatives you've considered**\r\n\u003c!-- A clear and concise description of any alternative solutions or features you've considered. --\u003e\r\n\r\n**Additional context**\r\n\u003c!-- Add any other context or screenshots about the feature request here. --\u003e\r\n","author":{"url":"https://github.com/rfelber","@type":"Person","name":"rfelber"},"datePublished":"2020-11-17T11:49:02.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/209/secureCodeBox/issues/209"}