# Assets

Collects asset inventory data from Rapid7 InsightVM, including IP addresses, hostnames, operating systems, services, and vulnerability counts.

**Sync Type: Full Sync**

## Prerequisites

Before connecting Monad to Rapid7 InsightVM, you need:

1. An active Rapid7 InsightVM console with network API access enabled
2. A console user account with **Global Read** permissions
3. The base URL of your InsightVM console, including the port (default `3780`)

## Authentication

Rapid7 InsightVM uses HTTP Basic authentication. Monad uses the console username and password to authenticate every API request.

1. Log in to your InsightVM console.
2. Navigate to **Administration > Users**.
3. Create a dedicated service account (recommended) or use an existing account.
4. Ensure the account has the **Global Read** built-in role, or a custom role with at minimum read access to assets.
5. Note the username and password — you will enter these in the Monad configuration.

## Configuration

The following configuration defines the input parameters.

### Settings

| Setting | Type | Required | Description |
| ------- | ---- | -------- | ----------- |
| Base URL | string | Yes | Base URL of the InsightVM console, including host and port (e.g. `https://insightvm.example.com:3780`). |
| Skip TLS Verification | boolean | No | Disable TLS certificate verification. Enable when the console uses a self-signed or private-CA certificate. Defaults to `false`. |
| API Rate Limit | object | No | Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See [API Rate Limiting](../../../guides/rate-limiting) for the field format, limits, and how to choose a value. |

### Secrets

| Secret | Type | Required | Description |
| ------ | ---- | -------- | ----------- |
| Username | secret | Yes | InsightVM console username. The account must have global read access. |
| Password | secret | Yes | InsightVM console password. |

## Setup Walk-through

1. **Gather credentials** — follow the Authentication section above to identify or create a service account with Global Read access.

2. **Find your Base URL** — note the full URL of your InsightVM console, including the port number (e.g. `https://insightvm.example.com:3780`).

3. **Create the input in Monad**:
   - Open your Monad workspace and navigate to **Inputs**.
   - Click **Add Input** and select **Rapid7 — Assets**.

4. **Fill in the configuration**:
   - Enter the **Base URL** of your InsightVM console.
   - Enter the **Username** and **Password** for the service account.
   - If your console uses a self-signed TLS certificate, enable **Skip TLS Verification**.

5. **Save and test** — click **Test Connection**. Monad will call the InsightVM assets API and confirm the credentials are valid.

6. **Activate** — once the connection test passes, enable the input. Monad will page through the full asset inventory on each scheduled run.

## Troubleshooting

### Common Issues

1. **Authentication Errors (401)**
   - Verify the username and password are correct.
   - Ensure the account has not been locked or disabled in InsightVM.
   - Confirm the account has the **Global Read** role or equivalent permissions.

2. **TLS / Certificate Errors**
   - If your console uses a self-signed or private-CA certificate, enable **Skip TLS Verification** in the connector settings.
   - For production environments, consider importing the CA certificate into your trust store instead.

3. **Connection Refused / Timeout**
   - Verify the **Base URL** is reachable from the Monad network, including firewall rules on port `3780` (or whichever port your console uses).
   - For Monad SaaS, ensure your firewall allows inbound connections from Monad's IP addresses:
     - see [Monad egress IP addresses](../../guides/egress-ip-addresses.mdx)

4. **Empty Results**
   - Confirm that assets exist in the InsightVM console and have been scanned.
   - Check the pipeline logs for any API response errors.

5. **Slow or Incomplete Syncs**
   - InsightVM asset inventories can be large. The connector pages through results at 500 records per request.
   - If a run is interrupted, the connector will resume from the last completed page on the next scheduled run.

## Related Articles

- [Rapid7 InsightVM REST API Documentation](https://help.rapid7.com/insightvm/en-us/api/index.html)
- [Rapid7 InsightVM Assets](https://help.rapid7.com/insightvm/en-us/api/index.html#tag/Asset/operation/getAssets)

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