“If you’re not red teaming, you’re just daydreaming.” – Red Team Journal

Next Becoming Odysseus Session

We’ve scheduled an online session of the full two-day “Becoming Odysseus” course for Nov. 17–18. We update each session based on what we learned from the last one, and the November session will feature more case-study work and a series of mini-decision games. You can find more information on the course here, and click here to register.
      Also, for those who haven’t heard, Micah Zenko’s book Red Team will be published Nov. 3. Visit the Amazon page to learn more and catch Dr. Mateski’s blurb for the book.

‘Let’s Game This!’

Since 1997 I’ve called for more and better red teaming. I’ll continue to do so, but I also believe we must red team the practice itself. In this spirit, I offer a cautionary argument in three parts:

  1. Reciprocal action is the essence of conflict and competition.
  2. Much if not most red teaming inadequately addresses reciprocal action.
  3. Wargaming better exercises the dialogue of reciprocal action.

Read on …

Baubles and Gems

We build and run wargames for a variety of reasons: to explore new (and “new” old) concepts, to expose decision makers to new ideas, and to train decision makers to think under pressure, among other things. Now and then, a wargame also reveals a potentially worrisome course of adversary action, one that the game’s sponsors would do well to consider.
      Here are two 20th century examples. In each case, the game’s players brought to light a course of action the scenario’s real-world “players” later exploited to great effect. Read on …

‘A Short Introduction to Red Teaming (2015)’

I am moving the format of the “Becoming Odysseus” course slides away from the current old-school, text-heavy approach to something much more modern. Rather than consign the introduction slides to the dustbin of red teaming history, I’m sharing them with RTJ readers. The concepts are still valid even if the visual layout is a bit out-of-date. And just to be clear, the new yet-to-be-unveiled format is still fairly conservative (lest anyone accuse me of being a “Dedicated Follower of Fashion“!).

Short Intro Cover

‘Open-Door’ Security?

We are beginning to hear more and more about the potential security challenges inherent in the nascent Internet of Things (IoT). Here’s an intriguing and readable IEEE article on the topic from Jonathan Margulies, Director of Analytics at Qmulos. As red teamers, we should be thinking about what our headlong rush toward IoT might really mean for our clients and ourselves.

New from Dr. Bunker

The U.S. Army’s Strategic Studies Institute has published a new monograph by RTJ advisor Dr. Robert Bunker titled Terrorist and Insurgent Unmanned Aerial Vehicles: Use, Potentials, and Military Implications. The monograph is of interest to red teamers not simply because of its topic but also because Dr. Bunker applied red teaming to his analysis.

One Reason We Fail to Red Team

Why doesn’t everyone red team all the time? Experienced red teamers can no doubt cite a range of reasons, but today we want to highlight just one (from Colin S. Gray): we don’t account for the adversary because it’s very difficult to do everything else we need to do and reason about an opaque and elusive opponent. As Gray puts it, military commanders Read on …

A Fun Example of Free Crowd-Sourced Red Teaming

This story about unicycle delivery drones caught my eye this morning. It’s an innovative application of a balancing capability similar to that found in the Segway. By the time I finished the article, I was already red teaming the concept and thinking that the developer should do the same. As I read the comments, however, I realized that the readers were doing it for them. It’s a great example of how even an untrained crowd can generate red teaming ideas rapidly. If the developer is savvy, he’ll take note of the free feedback when the idea is still in the concept phase.