|
By Tines
Security and IT leaders face a contradictory mandate: move faster with AI and automation while maintaining governance over every action that touches production systems, user accounts, and sensitive data. Most tools force a choice between two failure modes. Either the workflow runs autonomously, and the team hopes nothing breaks, or every action requires manual approval and analysts spend their shifts rubber-stamping low-risk steps until oversight disappears behind a green-checkmark audit trail.
|
By Tines
AI agents don't behave like the playbooks security and IT teams have spent years building. They form intent, select tools at runtime, and chain actions across systems in sequences nobody pre-authored. This means dropping an LLM into an existing automation sequence and expecting it to act like a smarter playbook is the fastest route to ungoverned, unpredictable outcomes.
Compliance teams know the pattern well: tracking down a missing access review sign-off at 11 p.m. the night before an audit, piecing together evidence from spreadsheets, email threads, and the gap between HR and IT. Access reviews keep appearing in SOC 2 exceptions, and the controls usually aren't the problem. The manual processes around them are. Many teams respond by buying a dedicated GRC (Governance, Risk, and Compliance) platform. Traditional GRC tools are structured repositories.
|
By Tines
A security engineer spends three weeks building an AI agent that triages phishing reports. The demo lands well. Then it hits the security review queue, and the questions start: Which tools can it call? What happens if it misclassifies? Who approves an account lockout at 2 a.m.? Where are the logs? Three more weeks pass, and the agent is still sitting in staging. This is the pattern most teams run into. The agent works, but the governance story doesn't.
|
By Tines
Enterprise automation keeps running into the same wall. Teams inherit tools built for a tidy world, then deploy them into one where alerts arrive at odd hours, APIs change without warning, and the "obvious" next step depends on context no playbook anticipated. The usual response, buying a platform, scripting every scenario, and bolting on an AI copilot, leaves the on-call engineer debugging the automation instead of the incident.
For IT teams, a meaningful share of every week disappears into manual, repetitive work: account provisioning, password resets, data reconciliation across systems. IT workflow automation coordinates these multi-system processes through event-driven triggers, conditional logic, and API-level integration, all under IT's governance umbrella. These workflows span multiple systems and route through identity providers.
|
By Tines
Most enterprise teams already run some form of workflow automation. The question is whether it can hold up when an AI step makes decisions within the chain, an auditor asks for a trail, and three teams need to build on each other's work without stepping on governance. That is where consumer-grade tools and enterprise-grade platforms part ways. The gap is architectural, not a feature lag, which is why it cannot be retrofitted.
|
By Tines
Network security stacks are stronger than ever: visibility is high, threat detection is improving, and AI adoption is widespread, with 99% of SOCs using it in some capacity. But despite these advances, network security teams face many of the same operational challenges as before. Incidents still escalate. Responses are slow. Analysts remain overwhelmed and burnt out. The issue isn’t detection – it’s what happens next.
Security and IT teams know the pattern: work spans dozens of tools that don't talk to each other, and people closest to the problem spend more time stitching together information than acting on it. Whether the job is provisioning access, triaging an anomaly, or closing out an incident, the reality is fragmented handoffs and brittle scripts. The data backs this up.
|
By Tines
AI agents are showing up across every team's stack faster than the systems to coordinate them. Cross-team work that depends on five tools and three approvals tends to break in the handoffs between them, and most teams patch those breaks with manual stitching, fragile scripts, or alerts that age in a queue until someone notices. Workflow orchestration is the coordination layer that closes those gaps.
|
By Tines
Restrict access to AI tools and you curb innovation. Open it up and security risks multiply. And then there's a third problem: approved tools behaving in unapproved ways. Security and IT leaders are navigating a new and fast-moving problem - employees using AI to build workflows, automations, and agents faster than anyone can track or govern. The question isn't whether it's happening. It's what to do about it.
|
By Tines
Automatically detect when user connectivity degrades in Netskope ADEM and respond instantly with an AI-powered Slack chatbot. In this five-minute flow, we walk through how to monitor Netskope ADEM experience scores for key users and trigger proactive outreach via Slack when performance drops. You'll see how Tines pulls scores on a schedule, creates a case when a threshold is breached, uses an LLM to craft a personalised Slack message, and deploys a Virtual Assistant to help the user troubleshoot in real time.
|
By Tines
AI makes building look easy. That’s the trap. Without a secure, well-designed foundation, workflows break, costs spike, and systems grow fragile. CTOs and CISOs from leading organizations discuss what breaks without a secure foundation, and how to build AI systems that hold up at scale. This session goes deep on the real-world tradeoffs between speed, risk, and trust.
|
By Tines
If your security team is managing insider risk or data loss investigations in Code42, keeping Jira and your inbox in sync is tedious. This story from the Tines library solves that by automating the full export process end-to-end. In under five minutes, you'll see how Tines lists all open Code42 cases, deduplicates them to avoid repeat alerts, downloads each full case export as a zip file, creates a pre-populated Jira ticket with key case details, attaches the export to that ticket, and emails it directly to the relevant recipient.
|
By Tines
Manage security alerts from multiple EDR customers automatically. See how Tines ingests, enriches, and responds to CrowdStrike and SentinelOne detections in one workflow. If you're managing EDR platforms for multiple customers, keeping on top of alerts across separate tenants is a nightmare. This story pulls alerts from CrowdStrike and SentinelOne, normalizes the data, and automatically opens a Tines Case all without hardcoding a single credential.
|
By Tines
Tired of manually triaging SentinelOne alerts and copying details into Jira? This story from the Tines library automatically pulls unresolved SentinelOne threats daily, filters out duplicates, and creates detailed Jira tickets for every net-new incident — so your team can focus on responding, not chasing alerts.
|
By Tines
Watch the Spring 2026 lookback video to see how the team at Tines is working hard to enhance the way you scale your intelligent workflows through AI and automation.
|
By Tines
Automate SMS phishing triage with AI — employees upload a screenshot, and Tines handles the rest in under 5 minutes. When employees forward suspicious texts, security teams still have to manually review screenshots, extract indicators, and route cases. This Five Minute Flow shows how to automate the entire process using the Tines AI action with Claude Sonnet — from employee submission to SOC case creation, IOC enrichment, and escalation when multiple employees report the same threat.
|
By Tines
Automate employee onboarding across BambooHR, Okta, Google Workspace & Microsoft 365 in minutes with Tines. Manually provisioning accounts across four platforms every time someone joins the company is slow, inconsistent, and easy to get wrong. In this Five Minute Flow, we walk through a Tines story that automates the entire onboarding process — from a daily BambooHR report through to account creation in Okta, Google Workspace, and Office 365, plus automatic Microsoft Teams channel access.
- June 2026 (17)
- May 2026 (21)
- April 2026 (9)
- March 2026 (13)
- February 2026 (13)
- January 2026 (7)
- December 2025 (11)
- November 2025 (9)
- October 2025 (7)
- September 2025 (13)
- August 2025 (8)
- July 2025 (10)
- June 2025 (8)
- May 2025 (18)
- April 2025 (27)
- March 2025 (7)
- February 2025 (7)
- January 2025 (14)
- December 2024 (6)
- November 2024 (8)
- October 2024 (13)
- September 2024 (15)
- August 2024 (14)
- July 2024 (16)
- June 2024 (13)
- May 2024 (11)
- April 2024 (25)
- March 2024 (15)
- February 2024 (10)
- January 2024 (6)
- December 2023 (5)
- November 2023 (8)
- October 2023 (11)
- September 2023 (9)
- August 2023 (6)
- July 2023 (5)
- June 2023 (6)
- May 2023 (3)
- April 2023 (8)
- March 2023 (6)
- February 2023 (6)
- January 2023 (10)
- December 2022 (4)
- November 2022 (8)
- October 2022 (16)
- September 2022 (6)
- August 2022 (4)
- July 2022 (8)
- June 2022 (4)
- May 2022 (8)
- April 2022 (11)
- March 2022 (10)
- February 2022 (10)
- January 2022 (1)
- December 2021 (2)
- November 2021 (1)
- October 2021 (1)
- September 2021 (1)
- August 2021 (1)
- July 2021 (7)
The world’s best companies – from startups to the Fortune 10 – trust Tines with their mission-critical security workflows.
Security and operations teams are too often stuck doing manual, repetitive tasks, and we want to change that. Tines is an automation platform designed to allow anyone to automate any manual task, regardless of complexity. No apps, plugins, or custom code required.
Tines customers automate an average of 20 workflows in year one. Build classic SOAR capabilities like endpoint detection & response and phishing response, solve needs like employee onboarding and Slack bots, and automate complex workflows unique to your business – all in the same tool.
With 1,000+ template options for common security actions, Tines is power and simplicity through direct integration with your existing tools.