Get Started with Infection Monkey, Open Source Security Tool
swimm.io
swimm.io
"It is non-intrusive, with no impact on your network." (from https://www.guardicore.com/infectionmonkey/)
Having a quick look at the site some of the modules it can use are brute-force password guessers which could cause account lockouts quite easily, depending on how they're used.
Also in my moderately long experience of pentesting (~15 years) even quite innocuous seeming actions can negatively impact systems under review (I've knocked over whole networks with standard port scanning, taken out a website with a ' character in a login box, seen another website taken out by being spidered etc)
This isn't to knock this tool in particular, just expressing a general wariness of tooling which claims to be able to fully automate a process and do so with zero risk.
Customers in this case need to realize that some pain is in their best interest. If the dentist cannot drill, he cannot help.
Of course, everyone should have a robust environment which can withstand any testing.
However, particular where a tool like this is intended to run constantly in an environment, I think the Ops teams would want to know whether there was a risk of an outage due to its use.
>The Monkey, is a proprietary tool that infects random machines in the target environment and propagates to them.
Is the Monkey different thing than Infection Monkey or is it actually not open source? Or is the term "proprietary" used only as buzzword?
https://github.com/guardicore/monkey
It sounds like it’s self contained, because according to the FAQ: “The Infection Monkey does not require internet access to function.”
My guess is the author of the Swimm article got confused or mis-stated the proprietary aspect. Perhaps they were thinking of a paid GuardiCore tool with additional functionality.