Do you write code? Do you have code? Do you ever stay awake at night wondering how evil hackers might steal it all for nefarious purposes? Are you interested in learning some super 1337 skills for yourself? Well, you’re in luck. Two evil hackers are ready to share and teach you few tricks they have used during live Red Team engagements to penetrate network defenses and find unexpected entry points. Join us in hacking the Gibson in this hands on workshop that will teach Penetration Testing skills and mitigations specifically tailored for the development community.

This Red Team workshop will provide students perspective and hands on experience with attack simulation tactics used to uncover vulnerabilities, also known as Red Teaming. Students can expect to cover topics such as social engineering (human manipulation), pivoting through network environments, attacking build pipelines, bypassing authentication, and looting systems for secrets.

Takeaways:

• Into to the Concept of Red Teaming
• Story Time: Social Engineering
• Social Engineering Mitigations
• Concepts of post exploitation and system looting
• Lab: Abusing Github CLI
• Lab: Bypassing Jenkins Google Authentication
• Lab: Abusing the Jenkins Script Console and Shelling your first box
• Mitigating the Jenkins Script Console Issues
• Lab: Abusing build jobs to Shell that box again
• Mitigating Controls and the Concept of Least Privilege
• Challenge Lab: Competitive Post Exploitation / Looting Lab

It is easy to think that securing a product relies on writing code without vulnerabilities and it's true that this is a very important aspect, but a secure product relies on more than just the code written. To an attacker every aspect involved in the development process, from the human element to the build pipeline, is fair game. In this talk we'll take a candid look at the real tactics, with examples, used to compromise and backdoor seemingly secure products by exploiting the humans and systems that create them.