Like the title say. It would be really cool to integrate the container hacking content into Samurai. Put's a bit ahead of the curve as container security continues to gather attention.
At first I'm thinking that we could have 3 target containers:
One to show how bind mounting the docker socket is a terrible idea
One to show how containers with too many kernel capabilities can be abused
The simple web target I built or we modify one of the dockerized targets to allow for a pivot through the docker socket post web app exploitation
I have been exploring Kubernetes and LXD lately as well. I don't have any of that stuff quite fleshed out yet though. But once I do it would be possible to add that in there as well.
I like what @mgillam suggested at one point. A sort of optional way to configure how Samurai builds. That way if somebody is only trying to show some web stuff, they just build the web stuff and not all the container stuff too, and vice versa.
Like the title say. It would be really cool to integrate the container hacking content into Samurai. Put's a bit ahead of the curve as container security continues to gather attention.
At first I'm thinking that we could have 3 target containers:
I have been exploring Kubernetes and LXD lately as well. I don't have any of that stuff quite fleshed out yet though. But once I do it would be possible to add that in there as well.
I like what @mgillam suggested at one point. A sort of optional way to configure how Samurai builds. That way if somebody is only trying to show some web stuff, they just build the web stuff and not all the container stuff too, and vice versa.