Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

AI adoption in security has soared. But for many teams, manual work and burnout remain stubbornly high. To understand why, and what security teams must do next, we partnered with Sapio research to survey more than 1,800 security leaders and practitioners worldwide for our Voice of Security 2026 report. We wanted to learn how teams are using AI and automation, how the role of security is evolving, and how professionals believe AI will impact their careers. The data is revealing.

At Tines, we recently faced a significant engineering challenge: our output_payloads table in PostgreSQL was rapidly approaching 17TB on our largest cloud cluster, with no signs of slowing down. Once a table reaches PostgreSQL’s 32TB table size limit, it will stop accepting writes. This table holds event data, in the form of arbitrary JSON, which is critical to powering Tines workflows. Given the criticality of the data, we couldn’t risk any disruptions to it.

At Tines, we understand different systems and environments require different deployment options. Some organizations require extra guardrails to access and manage their systems and data. Those operating in regulated industries or the government sector often require self-hosted or on-prem solutions to ensure their networks are secure and compliant. Tines is unique in many ways, but one of our biggest differentiators is that our intelligent workflow platform can be deployed in the cloud or self-hosted.

AI is everywhere, but without a consistent and secure way to connect it to real systems, it remains fragmented, difficult to govern, and hard to scale. Today, we’re introducing your AI interaction layer. Tines unifies AI agents, copilots, and Model Context Protocol (MCP) servers and clients in a single, secure environment. It gives teams a practical way to connect AI to systems and put it to work seamlessly across operations.

Early in the year, we introduced multiple drafts for Change Control. This feature enables builders to work on the same project simultaneously, each within their own draft environment. The upside? Agents were the talk of the town in 2025. Tines CEO Eoin Hinchy shared his thoughts on how they could help end muckwork, and shortly after, we launched the AI Agent action.

Every IT Operations team knows the feeling: the alert storm hits, dashboards light up, and another late-night scramble begins. You fix the issue, document it, and brace for the next one. The pattern repeats; not because your team lacks skill or visibility, but because the systems you rely on don’t move as fast as the infrastructure they manage. Downtime doesn’t start when systems fail. It starts when signals go unanswered.

IT and security teams are stuck between two bad options: over-automate on noisy, incomplete data and risk eroding trust, or avoid automation and drown in manual triage. With surging data volumes and increasingly complex stacks, both choices drive alert fatigue, longer MTTD/MTTR, and analyst burnout. Tines and Cribl offer an alternative vision.

Security and IT professionals know the pattern all too well: workplace stress peaks in the weeks leading up to major holidays. Teams face pressure to close out projects, meet year-end deadlines, and handle increased workloads with reduced staff. And to top it off, cyber threats don’t take holidays. In fact, attackers often exploit this exact window of vulnerability.

Patch management is one of those responsibilities everyone agrees is essential, yet very few teams feel confident about. The organizations I speak with every week are not struggling because they lack urgency or awareness. They are struggling because the environment around patching has changed dramatically.

Tines is vendor-agnostic and interoperability is core to our intelligent workflow platform. With each iteration of AI agents in Tines, we’re extending that interoperability. Today, that includes MCP support in the AI Agent action.