Swimlane Turbine Security Automation

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 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.

Neutral

Positive