Connectors 101


Vulcan Cyber's platform feeds from your existing security tools - vulnerability scanners, cloud providers, ticketing, SCA/SAST/DAST, and more. Connectors are Vulcan's way to communicate with those tools.

Each connector represents a security tool and by configuring a connector, Vulcan will connect to those tools and relevant data will be ingested to the platform.

In case you are using a tool that Vulcan doesn't have a dedicated connector type, you can use the Vulcan Report Connector, which enables users to upload CSV format files

Connector types

There are several connector types.

Each connector type has its unique capability: vulnerability scanner, asset inventory, ticketing system and patching tool. More detailed info can be found in Connectors and Supported Integrations

Process flow

Connector transitions through different states from the moment you configure it, through the moment its capabilities are ready to be used in Vulcan Platform.

The following illustration represents the transition between connectors’ states:

Connecting - The connector is verifying connection and pulling relevant data.

Synced - Connector finished pulling data and waiting for Vulcan's internal processes.

Processing - Vulcan's internal processes running on data to provide all Vulcan's capabilities.

Connected - The connector finished its run and the user can view data and start remediating using Vulcan.

Error - The connector runs into an issue that is preventing from it finishing its run.

Error types

There can be 3 types of common connector errors:

1. Configuration error – there can be two reasons for configuration errors to occur:

1.1. Possible problem 1: The credentials provided by the customer do not work

Note: In order to make sure that the connector is set as it should be, please use the “test connectivity” button located on the connector addition page

1.2. Possible problem 2: The configured user doesn’t have the right permission for a required action

How to solve:

- Find out whether the connecting issue is derived from the permission or the configuration error, which can be located in the connector’s log (Go to Connectors >> Choose a connector > Log)

- Update the permission according to the required permission and specified connector as mentioned in the user guide here

2. Syncing error – connection error between Vulcan and external vendors

How to solve:

- Contact our support or your CS manager

3. Processing error – Data ingestion error on the Vulcan side

How to solve:

- Contact our support or your CS manager

Did this answer your question?