Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Ever wonder if you're getting the most out of intelligent workflows? Tines' workflow capability matrix (WCM) gives you a complete view of what's possible. The matrix enables you to audit your existing workflows and discover new ideas. By covering core capabilities across security and IT operations, the WCM ensures you're considering the full range of opportunities available. Capabilities covered in the matrix include.

With the self-hosted release of v34.7.0, Tines can send Open Telemetry (OTEL) traces to observability stacks that support OTEL ingestion. Tines provides documentation on how to configure this new feature, but this first article will focus on how to use it. In this series, we will.

See how Torq harnesses AI in your SOC to detect, prioritize, and respond to threats faster. Request a Demo Security teams are being asked to move faster and handle more complexity, while the threats they defend against are increasingly AI-assisted. When I wrote about VoidLink in January, my point was simple: you cannot fight machine-speed threats with human-speed defense. Attackers are using AI to code, adapt, and scale attacks while humans are still grinding away doing the heavy lifting in the SOC.

When SOAR emerged around 2015, it was trying to solve a real problem: SOC analysts were drowning in manual, repetitive tasks across disconnected tools. SOAR promised to connect those tools, automate the workflows between them, and give analysts their time back. For a while, it mostly delivered. That era is long dead.

There’s a growing acceptance that AI is no longer optional in security. That battle is largely won. The more interesting question — and the one I keep getting asked — is what we actually believe AI should be responsible for, and where human authority must ultimately sit.