Lansweeper
Connect Lansweeper Cloud to RAD Security and query your whole asset inventory, including servers discovered by on-premises installations.
RAD Security connects directly to the Lansweeper Cloud Data API with a personal access token and imports every asset of one Lansweeper site into the lansweeper_assets data type: workstations, servers, network devices and cloud assets, with their operating system, hardware, installed software, services, owners and more.
The data is what Lansweeper reports and nothing more. RAD adds no verdicts of its own (no "is a server" flag, no "has EDR" flag), so you can build those rules in queries and dashboards over the raw fields, and see exactly why an asset matched.
Read-only integration. RAD only reads assets and the site's linked installations. It never changes anything in Lansweeper.
Early access. This integration is enabled on request. Ask your RAD Security contact to turn it on for your workspace; until then the Lansweeper card is not listed.
Prerequisites
- A Lansweeper Cloud site (Lansweeper Sites). On-premises-only Lansweeper installations must be linked to a cloud site first.
- Permission to create a personal access token in Lansweeper
- A RAD Security workspace with integration permissions
What RAD stores
| Object | RAD data type | One row per | Refreshed |
|---|---|---|---|
| Assets | lansweeper_assets | asset (Lansweeper asset key) | full pass every 4 hours |
Each row carries, as Lansweeper reports them:
- Identity: name (verbatim), normalized
hostname(short, lowercase),fqdn, IP address,mac(upper-case, colon-separated), serial number, domain, asset type and sub-type, scanner types, asset groups - Operating system: caption, version, build number, product type, service pack, install date, end-of-support date, organizational unit path
- Hardware: manufacturer, model, system manufacturer and product name, volumes (drive letter, file system, free space, encryption)
- Software and services: the installed software (name, publisher, version) and the services (caption, path, state, start mode), as parallel arrays — entry i of each
software_*array is one installed product - People and place: the last logged-on user (
user_name,user_domain), contact, location, department, branch office, building, local users and groups (with admin-group membership) - Relations and lifecycle: related assets (parent and child keys), warranty and purchase dates, cloud provider, region and environment
- Activity: first seen, last seen, last updated, uptime
- Reconciliation:
reconciled_source_ids, the asset keys Lansweeper retired when it merged duplicates into this asset
The data type is queryable in the Evidence Room, dashboard widgets, the data API and radbot.
The Zscaler integrations (Internet Access, Digital Experience, Client Connector) normalize hostname the same way, so it joins across them. Use it to find assets that one product sees and another does not.
Step 1: Create a personal access token in Lansweeper
Open the API clients page
In Lansweeper, open Account settings > Developer tools > API clients and choose Personal Access Token.
Grant the site and permissions
Give the token access to the site you want RAD to import, with read access, and tick View installations.
View installations lets RAD see whether an on-premises installation is linked to the site. Without it the import still works, but RAD cannot tell you whether servers discovered on-premises are reaching the cloud site — the most common reason a server count is lower than expected.
Choose an expiry and copy the token
Pick an expiry date and note it. Lansweeper shows the token only once: copy it before you close the dialog.
Step 2: Configure in RAD Security
Open Data Sources > Integrations > Asset Inventory, add the Lansweeper integration and fill in the fields.
| Field | Required | Value |
|---|---|---|
| Personal Access Token | Yes | The token from Step 1 |
| Site ID | No | The Lansweeper site to import. Leave it empty when the token can read exactly one site. If it can read several, verification lists them so you can pick one. |
| Token expiry date | No | The expiry you chose, as YYYY-MM-DD. Lansweeper does not expose a token's expiry, so RAD can only warn you before the token stops working if you enter it here. |
What verification does
Saving the integration checks that the token is accepted, that it can read the site (or lists the sites it can read when you left Site ID empty), and whether the site has a linked on-premises installation. The installation check never fails verification; it is reported as unknown when the token lacks View installations.
Once the status shows Connected, the first pass begins. A site of a few thousand assets is imported in a few minutes.
Reading the data
The latest pass is the inventory
Every pass rewrites every asset it reads, stamped with the time the pass started. An asset Lansweeper no longer reports is not deleted; it stops being rewritten and drops out of windowed reads. The default view shows the last 24 hours, which always contains the latest complete pass.
The key can change
Lansweeper issues a new asset key when it reconciles duplicates, for example an on-premises scan and a cloud scan of the same machine. The new asset lists the retired keys in reconciled_source_ids, so a decision you recorded against an old key can be carried forward.
Values are kept as Lansweeper reports them
Fields whose format Lansweeper does not document (uptime, volume free space, service pack numbers) are stored as the text Lansweeper sends. Booleans such as a disabled local user or an encrypted volume are read leniently (true, 1, yes).
Sync cadence and API budget
| What | Cadence |
|---|---|
| Full inventory pass | every 4 hours |
| Page size | 100 assets per call |
Lansweeper allows 150 requests a minute and 2,000 an hour. RAD paces itself below the per-minute limit instead of reacting to it, and an inventory of a few thousand assets takes tens of requests per pass.
A pass that sees less than half of the previous one is held back once. That pattern is far more often a lost permission or an unlinked installation than half the estate being decommissioned, and accepting it would age out every asset it missed. A second consecutive shrunken pass is accepted as real.