Debunking common misconceptions about no-code security automation


Is “no-code automation” the latest buzzword in cybersecurity? A hot trend that looks promising but has no legitimate legs to stand on? Or is no-code automation the evolution of security automation we’ve been waiting for that can improve the productivity and efficiency of SecOps teams?

In my 15 years as a security practitioner, I found no-code automation was what I wanted for my teams. I’ve seen capable, competent security practitioners spend most of their days performing monotonous, repeatable tasks; they were security analysts, not coders, so they had to rely on developers to create automation for them. It took time, and more time if they wanted to improve or repeat the process.

That’s why I created the no-code platform I’ve always dreamed of for my team. We’ve been pioneering no-code automation since 2018 and have spent a lot of time discussing the concept with security operations teams. Although no-code automation frees teams to be more impactful, productive, and creative, there is still confusion about what it is and what benefits it can bring. Here are the most common misconceptions we hear and what the truth is about no-code automation.


“I could just write a script to do that.”


You can just write a script, if you know how to do it. But security practitioners often lack this skill, which means they have to outsource their automation creation to others. Also, the easy part with code is writing it the first time. The hard part is deployment, security upgrades, maintenance, release management, and the downtime that comes after.

No-code automation maintains workflow automation with the security team and is as easy as dragging and dropping actions into a scenario. The absence of code also allows technical users, capable of writing code, to focus on the essentials: the workflow.


“It’s not powerful enough for our workflow.”


No-code automation platforms provide the building blocks for security teams, who can then design the workflows they need, from simple login confirmations to complex, all-encompassing vulnerability management.

Much like how you can build almost anything from a small number of LEGO bricks, there’s no cap on how complex a security analyst can put together, or how many of steps. Moreover, with half of the analysts saying that what they don’t like about their job is the time spent on mundane tasks, automation is needed more than ever.


“Automation means getting rid of team members.”


From what I’ve seen, this happens very rarely in practice.

First, those who automate their tasks then acquire that as a skill, and analysts who begin to automate then go on to make those processes more effective and efficient. What also happens is that when analysts start automating their tasks, it frees them up to focus their energy and attention on high-impact work, like improving the organization’s security approach. , the deployment of new technologies or the awareness and training of other teams.

Additionally, due to the ease of use of no-code automation, analysts can maintain and evolve their workflows, which is especially beneficial as processes and threats continue to evolve. Automation unlocks the potential of team members, and team members who are engaged and excited about their work stick around.


“Automation will make rash decisions when remediating.”


Automation is not necessarily all or nothing, as many may assume. Instead, good automation platforms make it easy to put a human on top of important decisions.

Instead of automating black-and-white remedial actions like blocking an account after a suspicious login, ask the affected user or an analyst for their human judgment first. This can easily be done by automating Slack messages – “Did you recently log in from a certain location?” – and automating responses – “Yes, that was me” or “No, that wasn’t” – to continue the workflow.


“The no-code automation platform should have a built-in case management tool.”


Many security teams have used SOAR platforms that include automation, and also offer other organizational tools such as case management or collaboration. But we’re at a point where teams are moving away from big box stacks to single tools that are best at what they do, like JIRA, Slack, and others. Why would it be any different with a no-code platform that only focuses on workflow?


Misconceptions about new technologies arise because teams are so used to one way of doing things that they view new tools and processes through a single lens. But the benefits of no-code automation mean it’s more than just a buzzword or fad; indeed, it is the next phase in the evolution of security. If you’re ready to bring the power of no-code automation to your organization, here are five steps to take:

Step 1: Evaluate your options. Find vendors with named customers you respect and demonstrable experience solving your use cases.

Step 2: Run a POC (proof of concept) process. Instead of choosing a simple workflow, choose the most complicated and difficult one out there for a realistic understanding of capabilities.

Step 3: Buy the best tool. Consider the pricing model, not just the price.

Step 4: Build workflows iteratively. Start small with prototypes and MVPs. Expand part-by-part workflows to cover edge and corner cases. Deploy the simplest usable version to production first.

Step 5: Deployment is just the beginning. Continue to maintain and evolve the workflow in production. As your business processes and threats are constantly changing, so should your workflow.

Founder at Teetha platform that allows anyone to automate repetitive security workflows without writing a single line of code.


Comments are closed.