Key Terms and Concepts

An account created to enable access to the Turbine UI or API. The administrator role in Turbine has access to all tenants, roles, groups, permissions, applications, reports, records, etc. The administrator role and permissions can be narrowed to meet business needs.

Agents perform actions from playbooks, and then send those results back to the Turbine engine. Agents wait to accept jobs to execute actions from Turbine but will not initiate actions themselves to simplify network configuration.

A preconfigured set of fields and layout specifications for Turbine. Applets are appended to an existing application form layout and are designed to allow users to easily update and expand their existing applications.

A form layout in Turbine for configuring applets.

A user-defined template for collecting, storing, and organizing your data. All automated activities and decisions are driven by how your application stores data. You also manage workflow from within applications.

A form layout in Turbine for configuring applications.

Reusable, structured, and vendor-specific collections of data that contribute to the success of Turbine actions. Assets allow users to create a reusable set of values that can be applied to actions as inputs in playbooks. Assets can be for a specific connector, or created as a custom asset which can be applied to any action inputs. Assets are most useful for standardizing and securing configurations.

An ordered collection of values of the same data type. Values vary based on the action connector and/or assets, and may include, but are not limited to: IP addresses, file names, URLs, etc.

A report or HTML object that is associated with a dashboard. You can have multiple cards on a single dashboard.

A visual, graphic representation of record and application data.

Compare the values on either side of the operator.

The ability to add context to a playbook input property.

Decision-points in the business processes programmed into workflow.

Stable, reliable connections for any API in a customer's environment.

Variables that hold a variety of contextual information relating to the current playbook, its invocation parameters, and executed actions.

A visual display of records, reports, and charts associated with the applications in the workspace. A workspace can have multiple dashboards.

The dashboard available to a user upon log in. The default is administrator-defined.

A dynamic value for string property types allows you to add context and/or repeats to a playbook property or expression.

Case management, low-code playbooks, solutions, and components that increase security operation center (SOC) team efficiently at machine-speed.

A value, or series of values, stored in an application.

A collection of defined users.

One-way or bidirectional communication between two or more systems.

The execution of a programmed action, including the inputs and resulting outputs from that action. A job is to an action what a playbook run is to a playbook.

Turbine's integrated content distribution platform. Content includes solutions, components, and connectors.

A measure of the average time it takes for an organization to detect a security breach or incident.

The time it takes to fully resolve an incident or a security concern and restore systems.

Security orchestration is the integration of disparate security tools and platforms to enable automated incident response.

A playbook is a set of rules describing a series of actions to be executed and the set of triggers that should execute those actions.

A single task within a playbook. The action includes all details necessary for the execution of the task.

Conditional statements coded into an action or trigger within a playbook.

A set of inputs to a playbook that map action properties or triggers.

A playbook that calls another playbook as an action.

Playbook outputs are the promoted responses and/or results from a playbook's actions.

A playbook that calls another playbook.

The outcome, as well as the activity, of a single execution of a playbook.

A Turbine component that hosts sensors and is capable of funneling issues detected from sensors.

Data types in playbook actions: string, number, integer, Boolean, object, array, null, date, date & time, password, code.

A single entry within an application. In Turbine terminology individual cases, events, alarms, alerts, etc. are generalized as application records.

Allows customers to connect internal applications and systems to Turbine without the need to configure multiple VPNs or complex networks.

A consolidated list of records.

A user-defined set of user and/or group permissions.

A conduit programmed to receive and forward event information.

Collects, aggregates, and then identifies, categorizing and analyzing incidents and events.

Use Swimlane Solution Packages (SSPs, file extension .ssp) to import or export a collection of playbooks, assets, applications, etc. into a Swimlane Turbine system.

A rule in a playbook describing which events and under what conditions a playbook should execute.

An account created to enable access to the Turbine UI or API. The user role differs from the administrator role in Turbine and typically has limited access to administrator role functionality.

Expand actionability by enabling products, vendors, and services to push real-time communication into Turbine

Communications between Swimlane Turbine (RabbitMQ) and the remote agents are over TLS-secured WebSockets on port 443. This streamlines the deployment of Turbine and prevents the need for additional hostnames or infrastructure.

A series of conditional decision points and resulting actions that automate the presentation of record fields and layout.

A single task within workflow, manually defined to respond to a conditional decision point.

Decision-points programmed into workflow.