This post is inspired by an idea (and a visual) from my esteemed colleague Toby Bussa.
It reflects our view that while you have TWO major routes to security orchestration, automation and response (SOAR) success, only one of them is in fact “right” for most organizations. And the other is “right” for a very select few of elite organizations, and in fact “wrong” and painful for most others.
Here:
Essentially, you have TWO DOORS TO SOAR.
- “Automation / orchestration first” – this path leads most to ruin, but it did lead some enlightened elite organization to raging success with SOAR
- “Workflow / case management first” – thus path is unglamorous, but it is the one where we see more success for most mainstream organizations that are seeking to adopt SOAR.
There you have it, pick the door and go.
And, no, we are not doing any new SOAR research at this time, and there are no solid plans to do so. Perhaps next year?
Blog posts related to SOAR:
- SOAR-native SOC, Can This Work?
- SOAR Webinar Questions – Answered
- Our Security Orchestration and Automation (SOAR) Paper Publishes
- SOAR and Ticketing: Friends, Frenemies or the Same thing?
- SOAR and “Curve-jumping” in Security Operations
- SOAR: Magic or Mundane?
- SOAR Research Coming … Brace for Impact!!
- SOAR research is coming! (by Augusto)
- Security: Automate And/Or Die?
- Security Without Security People: A [Sad] Way Forward?
Comments are closed
1 Comment
I’m a fan of defining policies and processes, automating them, and orchestrating series of them. This is the pragmatic approach that helps security people safely embrace automation and overcome organizational silos.