We spend a lot of time engaging with our user community on social media, Slack and Discord, sometimes engaging directly in those threads and sometimes via DM, email or on video calls. The idea is that you bring your own tools and techniques to Cobalt Strike and use those. Cobalt Strike’s defaults are easily fingerprinted and that’s by design. The obvious danger is that once they’re inevitably fingerprinted, we’d get stuck in an endless loop of fixing those issues rather than working on new features. Raphael also cautioned against adding cutting edge, out of the box evasion techniques to Cobalt Strike. That’s our mantra: Stability and Flexibility.
#COBALT STRIKE BEACON LIST FILES SOFTWARE#
He was excited to see a team of experienced, professional software engineers being built around the product to provide the stability and we’ve continued to add flexibility over the past few releases – for example, with the recent sleep mask kit and user defined reflective loader kit. One of the many things that he instilled in me is that the fundamental principles of Cobalt Strike are stability and flexibility. I spent about a year working closely with Raphael after HelpSystems acquired Strategic Cyber, amongst other things being educated on what makes Cobalt Strike so special. For the most part we’ve continued that tradition, but I’d like to spend a little time being a bit more transparent about our future development plans, before dropping back into the shadows. That was his way of building excitement for each release. He preferred to play his cards close to his chest and only revealed the details about each release when it went live (and he didn’t give much warning about the release date, either). Historically, Raphael Mudge, the creator of Cobalt Strike, didn’t typically talk about the Cobalt Strike roadmap publicly.