Armada (@armadaops) header
Armada (@armadaops) profile picture

Armada is the advanced technical services arm of @risk3sixty

Joined October 2025
Photo by Armada (@armadaops)Photo by Armada (@armadaops)Photo by Armada (@armadaops)Photo by Armada (@armadaops)Photo by Armada (@armadaops)Photo by Armada (@armadaops)Photo by Armada (@armadaops)Photo by Armada (@armadaops)Photo by Armada (@armadaops)
Armada retweeted
Replying to @armadaops
2
2
31
1,018
Red Team, Ready?!? Can you get into our magnetic case with your social and sec skills? What about upping your tactical skills? You're ready 👀. We know you are 🦾. Come see us!
3
39
1,966
DISTRICTCON YEAR 1 is in full swing! We heard from Winnona DeSombre, our Founder & Director, and Opening Keynote Ian Levy 🪩
1
5
1
27
3,022
Vibes are high as we prep for DistrictCon!! See you tomorrow 😎
1
7
1
28
3,195
We are planning to proceed according to schedule on Saturday, January 24. Given the developing weather situation, we are evaluating adding a virtual component to Sunday, January 25. We are making preparations for this option and are working through the logistics for this. We appreciate your patience as we navigate the situation! More updates to come.
We are aware of the developing weather situation in D.C. on January 24-25 (during our conference). We are planning to proceed and are continuing to monitor the situation. We encourage attendees to use caution transiting to and from the conference in the case of inclement weather. We will continue to monitor local weather reports, and take into account local guidelines and recommendations. We will communicate any scheduling changes out immediately if the situation changes! ☃️
4
1
10
3,083
risk3sixty's @armadaops team is heading to @DistrictCon as a Silver Sponsor next week. We’ll be in the Village of Villages with Cory Wolff, our Director of Offensive Security. Let's connect and talk real-world attack surface management. Find us and say hello!
1
1
1
2
866
Penetration tests are point-in-time. Exposures change daily. In ASM Field Guide Part 2, Cory Wolff breaks down why ASM is continuous + validated and why it covers more than “known assets” Watch: youtu.be/FW-W3kZdWw0 #Cybersecurity #PenTesting
1
64
Thank you, Philly! Huge shoutout to everyone who stopped by the Red Team Village at @BSidesPhilly. We loved meeting you, learning with you, and seeing the community show up with so much talent and energy. And major congrats to our RTV CTF winners — you crushed it. 🏆🔴🐉 See you at the next one!
6
20
1,811
Traditional penetration testing show you point-in-time. Your attack surface changes every day. Join Part 2 of our ASM Field Guide Series to learn why ASM now beats traditional penetration testing for real-world external risk reduction. Register: risk3sixty.com/webinars/asm-…
1
1
113
Replying to @BSidesPhilly
@BSidesPhilly Great CyberSec Conference
2
113
I'm releasing research soon detailing a technique to take over Kubernetes clusters. It allows running arbitrary commands in EVERY pod in the cluster using only a commonly granted "read only" RBAC permission. Oh and it's not logged by Kubernetes AuditPolicy 👀
6
34
3
204
40,580
A penetration tester got root access to our Kubernetes cluster in 15 minutes. Here's what they exploited. The attack chain: - Found exposed Kubernetes dashboard (our bad) - Dashboard had view-only service account (we thought this was safe) - Service account could list secrets across all namespaces - Found AWS credentials in a secret - Used AWS credentials to access EC2 instance profile - Instance profile had full Kubernetes admin via IAM - Used kubectl to create privileged pod - Escaped to node - Root access to entire cluster What we thought we did right: - Dashboard was read-only - Secrets were encrypted at rest - Network policies were in place - Regular security updates What we missed: - Dashboard shouldn't be exposed at all - Service accounts need principle of least privilege - Secrets shouldn't contain AWS credentials (use IRSA instead) - Pod Security Policies weren't enforced - Node access wasn't hardened The fix took 2 weeks: - Removed Kubernetes dashboard entirely - Implemented IRSA for all pod AWS access - Applied strict PSPs/Pod Security Standards - Audit all RBAC permissions - Regular penetration testing Cost: $24K for the pentest Value: Prevented what could have been a catastrophic breach
74
336
34
3,096
220,269
Coolest website you will see today.. What is your lesser known gem? godbolt.org/
2
7
30
6,648
We're officially announcing our speakers DistrictCon Year 1! Check out our incredible lineup: districtcon.org/speakers
1
14
7
40
25,566