Configuring LastPass Connectors

This connector allows Stellar Cyber to ingest logs from LastPass and add the records to the data lake. It integrates with the LastPass API to get Reporting events.

LastPass Enterprise is required. Make sure that you have a LastPass Enterprise subscription plan.

Stellar Cyber connectors with the Collect function (collectors) may skip collecting some data when the ingestion volume is large, which potentially can lead to data loss. This can happen when the processing capacity of the collector is exceeded.

Connector Overview: LastPass

Capabilities

Collect: Yes
Respond: No
Native Alerts Mapped: No
Runs on: DP
Interval: Configurable

Collected Data

Content Type	Index	Locating Records
Reporting	Syslog	msg_class: lastpass_reporting msg_origin.source: lastpass msg_origin.vendor: lastpass msg_origin.category: pw_mgmt

Domain

https://lastpass.com/enterpriseapi.php

Response Actions

N/A

Third Party Native Alert Integration Details

N/A

Required Credentials

Account Number/CID, API Secret/Provisioning Hash

Let us know if you find the above overview useful.

Adding a LastPass Connector

To add a LastPass connector:

Obtain credentials
Add the connector in Stellar Cyber
Test the connector
Verify ingestion

Obtaining LastPass Credentials

Before you configure the connector in Stellar Cyber, you must obtain the following LastPass credentials:

Account Number/CID. The CID is your LastPass account number, which is located on the adoption dashboard of the new Admin Console.
API Secret/Provisioning Hash. The API secret is also known as your provisioning hash, which is located on the Enterprise API page of the new Admin Console.

Adding the Connector in Stellar Cyber

To add a LastPass connector in Stellar Cyber:

Log in to Stellar Cyber.
Click System | Integration | Connectors. The Connector Overview appears.
Click Create. The General tab of the Add Connector screen appears. The information on this tab cannot be changed after you add the connector.

The asterisk (*) indicates a required field.
Choose Web Security from the Category drop-down.
Choose LastPass from the Type drop-down.
For this connector, the supported Function is Collect, which is enabled already.
Enter a Name.

This field does not accept multibyte characters.
Choose a Tenant Name. The Interflow records created by this connector include this tenant name.
Choose the device on which to run the connector.
(Optional) When the Function is Collect, you can apply Log Filters. For information, see Managing Log Filters.
Click Next. The Configuration tab appears.

The asterisk (*) indicates a required field.
Enter the Account Number/CID.
Enter the API Secret/Provisioning Hash.
Choose the Interval (min). This is how often the logs are collected.
Choose the Content Type you would like to collect. The logs for Reporting are supported.
(Optional) Choose the Query Delay (min). You can configure this delay to account for latency associated with querying events. For example, some data may not be available to query from LastPass for 60 minutes.
Click Next. The final confirmation tab appears.
Click Submit.

To pull data, a connector must be added to a Data Analyzer profile if it is running on the Data Processor.

The new connector is immediately active.

Testing the Connector

When you add (or edit) a connector, we recommend that you run a test to validate the connectivity parameters you entered. (The test validates only the authentication / connectivity; it does not validate data flow).

For connectors running on a sensor, Stellar Cyber recommends that you allow 30-60 seconds for new or modified configuration details to be propagated to the sensor before performing a test.

Click System | Integrations | Connectors. The Connector Overview appears.
Locate the connector that you added, or modified, or that you want to test.
Click Test at the right side of that row. The test runs immediately.

Note that you may run only one test at a time.

Stellar Cyber conducts a basic connectivity test for the connector and reports a success or failure result. A successful test indicates that you entered all of the connector information correctly.

To aid troubleshooting your connector, the dialog remains open until you explicitly close it by using the X button. If the test fails, you can select the button from the same row to review and correct issues.

The connector status is updated every five (5) minutes. A successful test clears the connector status, but if issues persist, the status reverts to failed after a minute.

Repeat the test as needed.

Display sample messages...

If the test fails, the common HTTP status error codes are as follows:

HTTP Error Code	HTTP Standard Error Name	Explanation	Recommendation
400	Bad Request	This error occurs when there is an error in the connector configuration.	Did you configure the connector correctly?
401	Unauthorized	This error occurs when an authentication credential is invalid or when a user does not have sufficient privileges to access a specific API.	Did you enter your credentials correctly? Are your credentials expired? Are your credentials entitled or licensed for that specific resource?
403	Forbidden	This error occurs when the permission or scope is not correct in a valid credential.	Did you enter your credentials correctly? Do you have the required role or permissions for that credential?
404	Not Found	This error occurs when a URL path does not resolve to an entity.	Did you enter your API URL correctly?
429	Too Many Requests	This error occurs when the API server receives too much traffic or if a user’s license or entitlement quota is exceeded.	The server or user license/quota will eventually recover. The connector will periodically retry the query. If this occurs unexpectedly or too often, work with your API provider to investigate the server limits, user licensing, or quotas.

For a full list of codes, refer to HTTP response status codes.

Verifying Ingestion

To verify ingestion:

Click Investigate | Threat Hunting. The Interflow Search tab appears.
Change the Indices to Syslog. The table immediately updates to show ingested Interflow records.