Add attack container about ecommerce-workshop HOT 4 CLOSED

This attack container should consist of two binaries so far:

gobuster and hydra.

This should also fix issue #74, unless we decide to have an instrumented version of logs, without proper parsing.

from ecommerce-workshop.

The attack container will also at some point after spin up need to do the following using a bash script. Use a leaked ssh-key ( bootstrapped with the environment ) in order to sign into one system running sshd and plant a new authorized_key. Then after some time wipe /var/log/secure log and zero out the unallocated space on the disk ( 10MB lets say ) using sudo dd if=/dev/zero of=tempfile bs=1m count=10. This will probably require adding sshd, an unprivileged user, sudo, and the dd binary to a system in the infrastructure.

from ecommerce-workshop.

The attack container will also at some point after spin up need to do the following using a bash script. Use a leaked ssh-key ( bootstrapped with the environment ) in order to sign into one system running sshd and plant a new authorized_key. Then after some time wipe /var/log/secure log and zero out the unallocated space on the disk ( 10MB lets say ) using sudo dd if=/dev/zero of=tempfile bs=1m count=10. This will probably require adding sshd, an unprivileged user, sudo, and the dd binary to a system in the infrastructure.

So this container needs to access another one in the cluster? Trying to figure out some implementation details here. The automation part sounds like a challenge given the ways we can deploy this system. My guess is we have to aim for docker-compose as the deploy/trigger mechanism since it'll be in Katacoda yes?

from ecommerce-workshop.

I think we can close this, @andrewkrug ?

from ecommerce-workshop.