-
Notifications
You must be signed in to change notification settings - Fork 179
Closed
Labels
scannerImplement or update a security scannerImplement or update a security scanner
Description
Is your feature request related to a problem? Please describe.
As an user i want to use test my ssh-server (or already found ssh port) based on best practices and given security policies with the secureCodeBox.
Some Best Practices on the topic ssh hardening can be found here:
- https://linux-audit.com/audit-and-harden-your-ssh-configuration/
- https://infosec.mozilla.org/guidelines/openssh
Describe the solution you'd like
There are already some ssh security scanners like:
Especially the mozilla ssh_scan seems to be a good candidate to implement.
It's well documented and has a active community. It supports JSON output and the possibility to add my own ssh check policy.
- See here for example video
- See here for example output
- See here for example policies
Additional context
A new ssh scanner could be combined with the existing port scanner (nmap) to check found ssh ports.
Steps to implement a new scanner
A general guide how to implement a new scanner is documented here
Must have
- Create a new public secureCodeBox repository for the scanner implementation
- Implement a new scanner microservice an reuse some of the existing stuff, if possible
- Check if there is a healthcheck for the microservice implemented
- Implement a new basic security process for the scanner
- Update the docker-compose files and integrate your new scanner there
- Update the user guide and developer guide
- Implement a integration test for the scanner here
Should have
- Update the CLI examples
- Update the Jenkins Pipeline examples
- Update the OpenShift Container Setup
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
scannerImplement or update a security scannerImplement or update a security scanner