hakbot-origin-controller
hakbot-origin-controller copied to clipboard
hakbot
Vendor-Neutral Security Tool Automation Controller (over REST)
Is it possible to trigger a Nessus authenticated scan by providing the credentials dynamically in the Json-body? If not, would this be a useful feature request?
When Servers (providers) are not available, Hakbot jobs will fail. This is normal. Once the servers are up again, it would be very handy if we could re-trigger the failing...
In my case I was idle for more than 24 hours. But the session is still active and the user is still logged in. It would be great if we...
Being an automation tool, it is crucial to have a timeout/watchdog to prevent Jobs running endless and so preventing other Jobs to be executed. Even when the security providers support...
Currently, if the hakmaster logs in they see jobs from all teams without any way to know what scans belong to what teams. This is a ticket to provide visibility...
Currently, all remote instances are defined in a global property file. This file should continue to provide global options, but Hakbot should allow the creation and management of remote instances...
The current provider only accept username/password via the session login. This is a ticket to add access key and secret key for authentication as an option (not to replace)
In addition to creating a war, the release process should output a dockerfile and push each release to docker hub.
Add support for Slack and Microsoft Teams via plugin APIs. Requires #13