devattackops

TLDR; Now that we have a container image registry, we can leverage the power of Docker Compose to deploy “containers as a configuration” to hosts. Check out the Artifacts section to see some examples. Disclaimer: If you have not read DevAttackOps Part 1 or Part 2, you should start there. We will be building off the concepts of those posts in this post. Welcome to part 3 of the DevAttackOps series where I talk about all things regarding Red Team infrastructure automation!...

TLDR; Building CI/CD pipelines for containers is not as daunting as it seems. For GitLab specifically, I have included a GitLab CI/CD configuration to automatically build and deploy your custom container images in the Artifacts section. Disclaimer: If you have not read DevAttackOps Part 1, you should start there. We will use the Cobalt Strike container we built in that post in following examples. Welcome to part 2 of the DevAttackOps series where I talk about all things regarding Red Team infrastructure automation....

TLDR; Building containers for Red Team applications is easy. I have included a Cobalt Strike Dockerfile for you in the Artifacts section. So here is my first actual blog post. In this series, I am going to talk about how Red Teams can use the same tools used by developers to both simplify Red Team infrastructure and generally make your life easier. In Part 1, I will be talking about why Red Teams should use containers in their workflows....