Swimlane Reviews

We are using Swimlane for automation purposes and security orchestration.

We are using Swimlane's Playbook Automation. One of the major playbooks that we use in Swimlane is for phishing email automation, so whenever there is a phishing email delivered to a user inbox, Swimlane will automatically sandbox that.

We integrate Swimlane with third-party tools such as CrowdStrike, VirusTotal, URL Proofpoint, and all other different tools we have, so that we get various enrichment of any alerts to make sure that the analyst doesn't spend much time doing manual tasks and gets all the information from the tools in the Swimlane console itself.

We use the case management feature in Swimlane as well. This case management feature is helpful because, in security, we don't want our security incidents to be visible to end users. For example, if I am using ServiceNow, I have to impose many restrictions on the backend table to ensure that whatever incidents are created and written into that table are not available to any end users or other IT team members. We use case management for that purpose so that our security alerts are isolated and only the security team has visibility on them. Whenever we need any remediation, we integrate it with ServiceNow, so if I need to raise a remediation ticket for re-imaging the system, we can create a ticket in ServiceNow from the Swimlane console or from the case management itself with all the proper information.

We do utilize the analytics aspect in Swimlane, and we use their Hero AI module as well.

We also use customizable dashboards in Swimlane because many clients, including CISOs, whom we manage need an executive-level view of what is happening over Swimlane. We create dashboards for them that provide proper information, such as how many alerts were created, what was the mean time to triage, and mean time to respond; we cover all these as KPI metrics in the executive dashboard.

The biggest advantage of Swimlane for us is that it saves time, which in turn helps us in cost-saving.

One of the disadvantages of Swimlane is that to manage the platform, we need hardcore developers. We have recently seen new products such as Tines and Blink Ops coming into the market, where a person with a good knowledge of APIs and JSON format can manage the platform and create playbooks. Even a security analyst can create some playbooks on those platforms. However, on Swimlane, it's difficult for security analysts since they must mandatorily know Python to create the playbooks.

In terms of pricing, Swimlane is on the slightly expensive side.

Swimlane is scalable in general, but there are some limitations. It involves maintenance overhead because you need a complete engineer who knows the product in and out to scale it for the on-prem environment, while in a SaaS model, it works without many problems.

Installation can be quite complex, especially when we have to use Kubernetes, and if we need to create load balancing. In those situations, it requires a good engineer to deploy the platform.

In relation to bugs, sometimes the enrichment playbook we have does not enrich the alert, resulting in missing details, so in those scenarios, the automation team has to manually run the playbook again.

Improvements could be made in terms of quality, particularly.

I have been working with Swimlane for almost seven years.

Swimlane is scalable in general, but there are some limitations. It involves maintenance overhead because you need a complete engineer who knows the product in and out to scale it for the on-prem environment, while in a SaaS model, it works without many problems.

I would rate technical support from Swimlane a seven on a scale where ten is the best.

Positive

Installation can be quite complex, especially when we have to use Kubernetes, and if we need to create load balancing. In those situations, it requires a good engineer to deploy the platform.

We see these savings approximately close to 30-35%.

In terms of pricing, Swimlane is on the slightly expensive side.

We have recently seen new products such as Tines and Blink Ops coming into the market, where a person with a good knowledge of APIs and JSON format can manage the platform and create playbooks. Even a security analyst can create some playbooks on those platforms. However, on Swimlane, it's difficult for security analysts since they must mandatorily know Python to create the playbooks.

I would rate Swimlane a seven out of ten as a product.

We are using it for a SOAR platform at a Cyber Security company which is MSSP. We are providing services to other companies, and we are utilizing it as a SOAR platform.

It has not impacted our organization positively, as we are using it primarily as a ticketing system. Normally, there should be some AI platform to include it and add alert traffic or other functionality, but it currently serves just as a ticketing system, which is not perfect.

I have used many different SOAR platforms, and I think Swimlane needs to upgrade and improve itself significantly.

Swimlane's search bar is not working effectively, and there is no option to differentiate between two cases at the same time. When cases become incidents, they should be marked with a different color to visualize escalations better. Our platform has some issues that do not disappear, and they have an unsupportive team. Their AI functionality exists but is not helpful. Sometimes there are glitches and problems with performance.

I have been using it for almost two years.

Swimlane has experienced problems with bugs and breakdowns.

My impressions of Swimlane's scalability are average. We are using it for different customers, and while we have numerous clients, the scalability is adequate.

I would rate their support a three out of ten due to both knowledge and response time.

Neutral

We are currently looking for different SOAR platforms.

The initial setup was moderately complex but manageable.

We implemented it ourselves without using an integrator or reseller.

I am evaluating other options at the moment.

Swimlane is in the middle class range in terms of expense.

I am not the decision maker, but I do not think it is worth the money to have as a tool.

I would not recommend using Swimlane.

On a scale of 1-10, I rate this solution a 5.

My main use case for Swimlane is security automation workflows, automating most of the daily SOC workflows, especially ticketing, alerting, and reporting.

The main workflow I automated with Swimlane that helped my team was connecting our SIEM, which is mainly Splunk, to a ticketing system, specifically Jira, with Swimlane in the middle. It automatically gets alerts or notable use cases from the SIEM, processes them through Swimlane, and sends them to Jira, performing a lot of logic and automation, including DFIR and automatic response to specific threats that can be automated.

The best features Swimlane offers are the flexibility of writing your own Python code and the existing workflows with a marketplace for the most known workflows, which is great because you can quickly use workflows similar to those in other solutions.

Swimlane has positively impacted my organization by saving a lot of time, reducing all the manual work that the SOC used to do, and improving response times. It saved about ten minutes for every alert that comes out, and we get hundreds of alerts, meaning it saved many hours every day.

Customizing workflows or scripts in Swimlane was a bit challenging, perhaps too challenging because of how the code base is structured. When writing a new custom Python script for a Swimlane workflow, I had to follow their specific template, which was annoying due to the lack of good documentation at the time. I had to understand how their SDK worked to write Python based on that for defining inputs, values, and outputs to test everything.

To improve Swimlane, I suggest more documentation, more flexibility, and ease in developing new custom workflows and modifying existing ones.

Support from Swimlane is very nice, great, and very supportive. The user interface is solid and does not need updates, but improving the development experience for custom workflows would be beneficial, as edge cases often create issues when building things. Apart from that, Swimlane excels in what it does.

Other improvements Swimlane might need include taking a closer look at the open-source community, as adopting some of that simplicity and flexibility would be beneficial to have.

I have been working in my current field for two years.

Swimlane was somewhat stable; the version we had was kind of buggy, but support indicated we just needed to do updates to resolve the issues, though we did not perform the updates.

Swimlane's scalability was adequate to some extent, but then it needed a DevOps engineer to maintain it properly, which we lacked. The Kubernetes cluster became hard to maintain because it required a dedicated DevOps engineer to manage the workloads.

Customer support was very helpful and responsive; once I had a disaster, and they provided assistance within the same hour. I would rate customer support a ten.

We chose another solution after Swimlane.

We have seen a return on investment; with the same number of engineers, we now handle double the number of customers, even with the new, larger customers requiring dedicated teams, thanks to the automation we implemented in Swimlane leading to the need for fewer employees.

My experience with pricing, setup cost, and licensing was positive; I was the one maintaining it, not the one who deployed it, but the pricing was very nice with a great discount.

We evaluated options like FortiSOAR, XSOAR, Splunk SOAR, and IBM SOAR before choosing Swimlane.

My advice for others considering using Swimlane is to ensure it is the right fit for you and to have someone capable of managing the Kubernetes cluster if you use it on-premises. If not, it is great to have it on the cloud, and you will definitely need people who understand Python for writing custom workflows. I would rate this solution a seven overall.

Swimlane is used for tasks that need multiple task owners. For instance, with bank applications, if you're opening a new account or need KYC, the application might undergo several stages - from submission to bank manager approval, back to verification, and finally to signers for signature purposes. Swimlane allows the movement of tasks to multiple users, being assigned to a single person, a specific user, a group of people, or a customized role.

Moreover, once a task is assigned using Swimlane, it's visible on the portal of each group member, allowing any of them to perform an action on the task.

Swimlane's persisting feature makes managing tasks very easy. When a task is assigned, it remains visible to all members it's assigned to, making it easy to manage and follow. Its integration within Appian allows tasks to stay active and notify users regularly.

Another benefit is it reduces workload with minimal coding, requiring just drag-and-drop for setting assignments. It's both time and manpower efficient.

Swimlane should enhance its integration features beyond the current task assignment, reaction, and persistence capabilities. It should support integrations with multiple signals or queues.

Additionally, Swimlane's tight coupling with Appian standalone applications limits its scalability. It should be exposed so external clients can use it without needing a local setup. This would improve its dynamic adaptability and scalability.

I have been working with Appian for around 8 years.

If you have already used your tool inside any Appian Studio, which is already built on Appian technology, then the Swimlane will be available to it, and it's a component you can integrate very easily. It is just a drag and drop thing. Drag and drop and assign some values.

If the event is written correctly, then Swimlane is a hundred percent accurate. It will always determine which person to assign, and what to do, for that claiming thing. I haven't seen any production issue or anything coming up because of Swimlane.

Swimlane is not scalable because it is not exposed. Currently, it's a manual component that requires configuration through coding. If it were exposed or ported to a cloud platform, it could achieve better scalability. Swimlane should have the capability to be moved out of Appian and integrated with other platforms.

Appian community is there for technical support. You can raise a ticket or incident, and it gets addressed based on priority. Additionally, working with a firm that has a dedicated person for support is beneficial.

If the primary support contact is unable to assist, tickets must be created within the Appian community, though sometimes response times extend for weeks.

Positive

If we consider options outside of Appian, Java has many similar solutions, but within Appian, the task assignment capability is uniquely provided by Swimlane.

For the initial setup, the licensing needs to be handled appropriately. Existing applications wanting integration must have their process structures within Appian, as Swimlane isn't exposed. A process image is necessary in Appian to use Swimlane, which can be a drawback.

The best part of Swimlane is the persistent notifications and its ease of integration, requiring minimal coding. While it lacks response features, it can be integrated with messaging or queue services to achieve this. Any incident response requires additional integration since Swimlane itself doesn't react to incidents.

Real-time data in terms of persistence is configurable, and without config, tasks persist indefinitely until completion. If using Appian versions below 11, integration features for Swimlane aren't available. By default, Swimlane lacks built-in intelligence, needing coding for integration.

Although the Swimlane is beneficial and reduces manpower requirements, it's hindered by its lack of exposure. If exposed through services or endpoints, its functionality could be accessed without needing a local standalone application.

On a scale of one to ten, this solution deserves a rating of nine.

We have been using Swimlane for security automation within our company. All the ingestions, automations, and everything within our department goes through Swimlane.

Swimlane is easy to start with, as it requires minimal prior knowledge to get started. It is flexible, providing room for users to set up specific incident response flows. Additionally, its integration capabilities allow connections to various platforms, enhancing its usability. Swimlane has helped reduce analyst time, contributing to operational efficiency.

There is a need for enhanced version control in Swimlane. Currently, our version does not support it, making it tough to move changes between environments during significant updates. Furthermore, despite being advertised as a no-code tool, it remains code-reliant, demanding users to build solutions through coding.

We have been using Swimlane for the past three years.

I would rate the stability of Swimlane as a seven. We encountered issues requiring multiple restarts, which suggests that stability could be optimized further.

Swimlane is very scalable, and I would rate it a nine. We did not encounter issues even when managing thousands of alerts, as scalability is only limited by our instance's server capacity.

Swimlane's technical support is very good. They are attentive, responsive, and work to resolve issues efficiently.

Neutral

We previously used Splunk SOAR, but switched to Swimlane due to cost considerations. Swimlane was more cost-effective.

The initial setup of Swimlane is easy to learn but requires customers to design their solutions. Deployment of Swimlane took us three to four months, which involved migrating existing playbooks.

Around ten people from Swimlane and five from our team were involved in the implementation.

I wasn't part of the initial evaluation process. Still, we had some evaluations of other SOAR solutions within our company after migrating to Swimlane.

I would recommend Swimlane for those proficient with code and prepared for the maintenance efforts required. On a scale of one to ten, I rate Swimlane a seven.

My main use case for Swimlane is as a SOAR platform and for documentation. I use Swimlane for documentation by documenting all the alerts that we get and adding all of our documentation.

I appreciate the UI and the ease of usability that Swimlane offers. What stands out to me about the UI of Swimlane is how everything has a feature on the side that you can easily move around, which is quite convenient.

Swimlane has positively impacted my organization by helping us quickly work on alerts and document them. From being able to quickly work on alerts and document them, I have seen improved response times and efficiency since we are able to work very easily using the amazing UI and the tool.

Swimlane can be improved by being faster and quicker so it is easier for us and does not hang sometimes.

I have been using Swimlane for two and a half years, almost three years now.

On a scale of one to ten, I would rate Swimlane a nine. I chose nine because it is a pretty great tool and the only reason I did not give a full ten is because there is room for improvement and how it always should be.

Regarding Swimlane's AI capabilities, I have not used it so I cannot say anything about its governance and security. I cannot say anything about the accuracy and reliability of output since I have not used it yet.

My advice to others looking into using Swimlane is to keep an open mind; it might be a lot in the start, but it is an amazing tool. Give it some time, get used to it, get your hands dirty, and you will love this tool after a while. I have no additional thoughts about Swimlane, just keep improving, keep doing what you do, and you are doing a great job. My overall rating for Swimlane is nine out of ten.

Positive

Neutral

We use Swimlane as an alternative to Splunk Phantom which is a security orchestration, automation, and response (SOAR) solution.

The most valuable feature of the solution is the support.

The stability of the solution has room for improvement.

I would like Swimlane to provide a single space where we can go to code, build, and automate. Where we have a provision to create tables, playbooks, and tables to produce results, connect all the dots, and make the flow automated. This would make it much easier to navigate than having to jump to different places. I would like to have a single button to click that would start me on the journey of creating my own code from the ground up, from the workflow algorithm to the automation process. This would be simpler than what I had with Splunk Phantom, where I had to piece things together and connect the dots to get the full picture. With this new feature, I could create the full picture with just one button click.

I have been using the solution for one year.

The solution is stable but not to the level of my expectations.

I give the stability a seven out of ten.

I give the scalability a nine out of ten.

We decided to move to Swimlane and Palo Alto as our SOAR solutions, as they are the most promising solutions in the market and have received positive reviews from their current users. Additionally, the support they provide is excellent. We had extensive interaction with the Swimlane team for about three months before we decided to purchase the tool. They showed us all the needed features and provided us with direct access to their developers and engineers so that we could ask questions or discuss any use cases. They even gave us the opportunity to practice and test the tool for ourselves. This level of support and flexibility was a stark contrast to what we had experienced with Splunk Phantom, so we decided to go with Swimlane.

The initial setup is done by the Swimlane team within a few hours.

The implementation is completed by the Swimlane team.

I give the solution an eight out of ten. Swimlane is a great choice due to its scalability, support, stable versions, and upgrades. It is also not difficult to code with Swimlane, making it an even more attractive option. Connecting the dots is the only way to make the most of it, but that shouldn't be a deterrent from using Swimlane.

The Swimlane support takes care of all maintenance on their end, giving us at least one month's notice before making upgrades or performing any other necessary maintenance. They always do this at a predetermined time.

We have around 20 engineers and developers that are using the solution.

New users should first gain a basic understanding of SOAR automation, then get some hands-on practice and take a training course. After that, we should be able to get started with Swimlane easily, as the support is good.