Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Friday Flows 35: Tines Workbench showcase

Tines Workbench is here, a true evolution in how automation and AI is leveraged within operations for security and IT. If you missed it, Workbench is a Tines-powered AI chat interface where you can take action and access proprietary data in real-time, privately and securely. In this episode of Friday Flows, Cameron welcomes security researcher Michael Tolan, who showcases Workbench's capabilities by focusing on a suspicious Okta login.

Introducing Workbench | Product spotlight

In this webinar, Rosie Halpin, Product Manager, introduced Workbench, the new Tines-powered AI chat interface. Workbench was purpose-built to power real-time orchestration across your work (in Tines or any other system) in a secure and private way. What we covered: We're excited to share more about how we’re continuing to invest in AI that makes teams more compliant, secure, and better connected as a business – all without increasing your risk. Watch the webinar to learn more about bringing your tools, teams, and systems together with Workbench.

Friday Flows Episode 31: Analyze Elastic alerts, block IPs, and notify in Slack and Tines Cases

FRIDAY FLOWS #31 - Analyze Elastic alerts, block, IPs, and notify in Slack and Tines Cases Personally, my favourite partners to work with. Elastic and Tines go hand in hand technology wise. Whether you're using Elastic for SIEM, Cloud Security, Endpoint, or outside security like Observability, Tines acts as the automation glue for those tools. I hope you enjoy today's episode with Michael Tolan and as always, check out the Tines community edition in the comments to play around with this specific story and more.

Friday Flows Episode 32: Beyon Cyber: An MSSP Journey from Traditional SOAR to Tines

FRIDAY FLOWS #31 - Beyon Cyber: An MSSP Journey from Traditional SOAR to Tines For any MSSPs out there, this is a really interesting deployment we did with Beyon. Service Providers will look to use SOAR as backend automation for their services. However, traditional SOARs can create their own problems. Requiring dedicated Dev teams to deploy & write automation. Not allowing customisable integration ability outside the box and ultimately being very resource-intensive to maintain.