This is all quite offensive … 

So, Red, Blue, Purple… what’s next ? eggshell-white-hat ?

Offensive security essentially is simulating real world attacks driven by context rather than scope (ideally) the context being crime simulation and available options, 

This isn’t a Pentest, but some common execution models below highlight what you might benefit from and why, … but don’t worry we can always pick one of the remaining 16.8 million colours remaining and add ‘-team’ to it.  

Blue

Let’s look at the current way of thinking, what the organisational biases are, protected and exposed areas, let’s revisit and validate known controls and make sure logging monitoring and alerting is as it should be or as it could be, let’s see where defenced at each layer begin and end and deal with the residual. 

Common work in this area has been to build out security teams into a service desk mentality and it’s depth reflective of available resource, in-house skill and supporting technology.

 

Red

Cry havoc let loose the dogs of cyber-war.

Red work is all offensive, but really falls under client goals, are you testing a entry point, a process, a pre-accepted risk, or validating existing controls actually work as a effective defence or deterrent, all these questions can be answered from offensive security. 

The only question worth asking at this point is: ‘What’s the scenario ?’ because, yes, CTUS can help. and if we can’t help… we can help, we have a network of security associates that have availability and the CTUS seal of approval when our availability is thin. 

Purple

Red + Blue collaboration, who would have thought !

This is usually done onsite, attacking existing controls, fine tuning or creating standard operating procedures, purple work for CTUS has traditionally been project based for deployments of security appliances or new infastructure or parenting a existing security team and playing devils advocate with a positive proactive outcome in mind.