# Vulnerabilities

Fetches vulnerability records from Lansweeper Cloud, including CVE details, risk scores, and affected asset information.

**Sync Type: Incremental**

## Prerequisites

Before connecting Monad to Lansweeper, you need:

1. An active Lansweeper Cloud account with access to the sites you want to collect vulnerability data from.
2. A **Personal Access Token** with permission to read vulnerability data from the target sites.

## Authentication

Lansweeper uses Personal Access Tokens (PATs) to authenticate API requests.

### Creating a Personal Access Token

1. In your Lansweeper Site, select **Settings** (bottom-left corner).
   > If you are using the new Lansweeper Platform Experience, select your profile image in the top-right corner, then select **Account settings**.
2. Select **Developer tools** → **API clients** → **Add new API client**.
3. Select **Personal Access Token**.
4. Enter an API client name and optionally a description.
5. From the **Integrations** dropdown, select **Other** and enter a custom integration name (e.g., `monad`).
6. Select an expiration time for the token.
7. Select which sites you want to grant API access to.
8. Copy the generated token to your clipboard — it is only shown once.

### Refreshing a Token

1. In your Lansweeper Site, select **Settings** (bottom-left corner).
2. Select **Developer tools**.
3. Select your PAT client from the list.
4. Select **Refresh token** → **Yes**.
5. Copy your token to your clipboard, then select **Done**.

## Configuration

The following configuration defines the input parameters.

### Settings

| Setting | Type | Required | Description |
| ------- | ---- | -------- | ----------- |
| Backfill Start Date | string | No | Date to start fetching data from. If not specified, only vulnerabilities from the current time onward are collected. |

### Secrets

| Secret | Type | Required | Description |
| ------ | ---- | -------- | ----------- |
| Personal Access Token | secret | Yes | Long-lived bearer token for the Lansweeper API. Obtain it from Lansweeper Cloud Settings → Developer tools. |

## Troubleshooting

### Common Issues

1. **Authentication Errors (401 / 403)**
   - Confirm the Personal Access Token is correct and has not been revoked.
   - Verify the token was copied in full with no extra whitespace.
   - Regenerate the token in Lansweeper Cloud Settings → Developer tools if needed.

2. **No Sites Returned**
   - Ensure the Lansweeper account associated with the token has access to at least one site.
   - Check within Lansweeper Cloud that the account is authorized for the target sites.

3. **Empty Results**
   - Confirm that the target sites have vulnerability data in Lansweeper Cloud.
   - If a **Backfill Start Date** was set, verify the date range includes vulnerabilities that exist in the system.
   - Check the pipeline logs for any parse errors on the API response.

4. **Missing Historical Data**
   - If no **Backfill Start Date** is specified, only vulnerabilities from the current time onward are collected. Set a backfill date to retrieve historical records.

## Related Articles

- [Lansweeper Data API Quickstart](https://developer.lansweeper.com/docs/data-api/get-started/quickstart)
- [Lansweeper Vulnerabilities API Reference](https://developer.lansweeper.com/docs/data-api/reference/vulnerabilities)
- [Lansweeper Vulnerability Management Guide](https://developer.lansweeper.com/docs/data-api/guides/vulnerabilities)

## Sync frequency

By default this input polls approximately every 10 seconds, with each sync beginning after the previous one completes. A cron schedule configured on the pipeline overrides this cadence. See [Input Sync Frequency](../../guides/sync-frequency) for details.