Nodeware Setup Beta

Connect Nodeware to let Junto review each customer's vulnerability scanning: the overall risk score, assets with findings by severity, which devices a CVE affects, OS patch status, recent alerts, network sensor health, and generated reports. With approval, the agent can also rescan an asset to verify a fix, pause or resume scanning on a device, set an asset's display alias, and request a new report.

Junto supports one Nodeware configuration per organization. Connect your partner API token once, then map Nodeware customers to Junto companies so the agent can retrieve each customer's data.

Prerequisites

• A Junto Admin or Owner account
• A Nodeware partner account with access to the customers you want to connect
• A Nodeware partner API token
• Customer companies in Junto, imported from your PSA, to map to Nodeware customers

Step 1: Get Your Partner API Token

1. Sign in to the Nodeware partner portal.
2. Generate or copy your partner API token.
3. Store it securely. A partner token reaches every customer under your Nodeware account, so treat it like an administrator credential.

Step 2: Configure in Junto

1. Go to Settings > Integrations > Nodeware.

2. Click Add configuration.

3. Complete the form:

   Field	What to enter
   API token	The partner API token from Step 1

4. Click Create. Junto validates the token against Nodeware before saving and encrypts it when stored.

5. Click Test connection on the configuration card. A successful test shows Connection successful with the number of customers the token can reach, and the button briefly reads Connected.

The Nodeware service address is fixed, so there is nothing to enter beyond the token. The Active switch appears when you edit the configuration later; new configurations are active by default.

Step 3: Map Companies

1. Click Company mapping on the configuration card to open the Nodeware company mapping dialog.
2. For each Junto company, select its Nodeware customer. Each option shows the customer's name and asset count.
3. Click Save mappings.

You can also click Run auto-map. Exact name matches are applied automatically; similar names are presented as suggestions that you can Confirm or Dismiss. Save any manual selections before running auto-map.

Each Junto company can map to one Nodeware customer, and each Nodeware customer can be selected only once; a customer already mapped elsewhere is shown as already mapped and cannot be chosen. To remove a mapping, set the row back to Select Nodeware customer... and save. An unmapped company cannot use the Nodeware tools, and the agent will say so.

If the dialog shows No companies found, import companies from your PSA first. If a Nodeware customer is missing from the list, confirm that your partner token can reach it in Nodeware.

What the Agent Can Do

Capability	What Junto can do	Risk level
Customer overview	Read the customer's overall vulnerability score and asset totals (internal, external, scanned, monitored, online)	Low
Asset inventory	List every asset Nodeware knows for the customer (agents, sensor-discovered devices, and external hosts) with type, score, last seen, and last vulnerability scan; filter by hostname or alias, recently changed reports, or recently seen devices	Low
Asset search	Find assets by CVE, asset type, or recently changed report, returned most severe first with severity totals, OS patch status, and top findings	Low
Asset details	Inspect one asset's host details, tags, scan state, score and score change, OS patch status, and findings by severity with the vendor's solution, recommendation, and reference links	Low
Asset CVEs	Read the CVEs currently open on an asset and every CVE ever seen on it with first and last seen dates	Low
Alerts	List alerts for a time window (default 7 days, up to 90 days, or down to the minute) such as new vulnerabilities and newly seen devices	Low
Sensors	List the customer's network sensors with status, network, version, and scan activity, or inspect one sensor	Low
Reports	List generated reports with their file formats, see which report types can be generated, and get a time-limited download link	Low
Rescan asset	Ask Nodeware to rescan one asset now instead of waiting for the next scheduled scan	Low
Update asset alias	Set an asset's display alias, for example the user's name or the RMM device name	Low
Generate report	Request a new report for the customer in one of the available report types, such as executive, patch, top vulnerabilities, or inventory	Low
Pause or resume scanning	Pause vulnerability scanning on one asset, or resume it	Medium

All write actions require technician approval before execution. Read-only tools do not require approval.

Pausing or resuming scanning and updating an asset alias require the Operator role or higher. When a technician requests one of these actions, the approval is routed to a member with that role. Pause or resume scanning is available only in supervised contexts such as Explore chat; it is not offered to runbooks that run without a technician.

Scope and Reporting

• Customer context: Every tool operates on one mapped company at a time. The agent addresses companies by their Junto name and never by a Nodeware customer identifier. Assets and sensors must belong to the mapped customer; a device from another customer is refused before any approval prompt.
• Severity levels: Junto classifies each finding on its CVSS-style score as critical (9.0 and above), high (7.0 and above), medium (4.0 and above), low (above 0), or info (0). Info findings are fingerprint and inventory results such as OS detection, open ports, and confirmed patches, not vulnerabilities.
• Score: A customer with no score has not completed its first scan. Junto reports that as "not yet scanned," not as a perfect or failing score.
• Search results: Asset search returns every matching asset in one call, including devices that have been offline for a long time. The minimum severity only limits which top findings are shown, not which assets are returned. Searches are capped at 1,000 matching assets, asset details at 50 findings, and alerts at 100; narrow the filters when a result is marked truncated.
• Patch status: Nodeware reports the installed versus available OS patch level only. It does not deploy patches. Pair Nodeware with your connected RMM: the agent matches the Nodeware asset to the RMM device by hostname, IP, or MAC address, deploys the fix through the RMM's own tools, then rescans in Nodeware to verify. Without an RMM, the agent recommends the fix and documents it on the ticket rather than claiming remediation.
• Reports: Report generation is asynchronous. A requested report appears in the report list once Nodeware has built it, usually within a minute for a customer that has been scanned. Download links expire about an hour after they are issued; ask again for a fresh link. The agent shares the link rather than pasting report contents.
• Read-only areas: The integration does not add or remove customers, activate or deactivate sensors, decommission or delete assets, add external assets, or apply scan credentials. Make those changes in Nodeware.

Rescans, Scan Pauses, and Aliases

A rescan is queued, not immediate. After requesting one, ask Junto to reread the asset's findings or CVEs once the scan has finished; the last vulnerability scan time changes when it completes. A paused asset is not scanned, so resume scanning first if needed.

Pausing scanning stops vulnerability detection on that device until it is resumed, so new findings will not be reported. Use it only for a stated reason, such as a maintenance window or a fragile device the scan disrupts, and record when scanning will resume. If the asset is already in the requested state, nothing is changed. Junto confirms the new state after the change; if Nodeware does not confirm it, check the asset in Nodeware before asking again.

An alias can be replaced but never cleared, and it is limited to 100 characters, so choose it deliberately.

Example requests:

• "What is Acme's Nodeware vulnerability score, and which hosts have critical findings?"
• "Which of Acme's devices are affected by CVE-2024-3400?"
• "Show the findings on ACME-FS01 with the recommended fixes."
• "Is ACME-FS01 behind on OS patches?"
• "What Nodeware alerts did Acme get in the last seven days?"
• "Are Acme's Nodeware sensors online and scanning?"
• "Rescan ACME-FS01 now that the patch is deployed, then confirm the CVE is gone."
• "Generate an executive report for Acme and send me the download link when it is ready."

Managing the Connection

• Update the token: Click Edit, enter the replacement token in API token, and click Update. Leave the field blank to keep the stored token. Junto validates the new token before saving and removes any mappings to customers the new token cannot reach, so review your company mappings afterward.
• Pause the integration: Click Edit, turn off Active, and click Update. The configuration and mappings remain saved.
• Remove the integration: Click Delete, then confirm Delete in the Delete configuration dialog. This permanently removes the stored token and all Nodeware company mappings from Junto.

Only one configuration can exist per organization; Add configuration is unavailable while one exists.

Troubleshooting

• Nodeware rejected the API token: The token is invalid or has been revoked. Check it in the Nodeware partner portal and enter it again.
• Could not connect to Nodeware: Nodeware could not be reached. Check your network connectivity and try again.
• Company is not mapped to a Nodeware customer: Open Company mapping, select the customer for that company, and save.
• Asset or sensor not found for this company: The device does not belong to the mapped customer, or the identifier is stale. Ask the agent to list the customer's assets or sensors and try again.
• Customer missing from the mapping list: Confirm that your partner token can reach the customer in Nodeware, then close and reopen the dialog to refresh the list.
• Mappings disappeared after changing the token: A new token drops mappings to customers it cannot reach. Map those companies again.
• Record not found: If the mapped customer itself no longer exists under your partner account, remap the company to a current Nodeware customer.
• Report not listed yet: The report is still generating. Ask again after a minute. If the download link has expired, ask for a fresh one.
• Another change to this asset's scanning is in progress: Two scan-state changes were requested at once. Reread the asset's scan state before trying again.
• Assets stopped updating: Check the customer's sensors. A disconnected or deactivated sensor stops discovery for its network, and an agent asset with an old last-seen time is offline or uninstalled.