Appearance
RoboShadow Setup Beta
Connect RoboShadow to let Junto investigate your customers' Windows devices and security posture. The agent can list a customer's devices, check what software is installed and which third-party upgrades are available, review CVEs and how to fix them, see which Windows updates are missing, and read antivirus, firewall, disk encryption, hardware, Microsoft MFA, and vulnerability scan reports.
The integration is read-only. Junto never deploys patches, starts scans, runs remediations, or changes settings in RoboShadow. Those stay in the RoboShadow portal.
Junto supports one RoboShadow configuration per organization. Connect your RoboShadow account once, then map each Junto company to its RoboShadow organization so the agent sees the right customer's data.
Prerequisites
- A Junto Admin or Owner account
- A RoboShadow account that can access the customer organizations you want the agent to read
- A RoboShadow API refresh token for that account
- Customer companies in Junto, imported from your PSA, to map to RoboShadow organizations
Step 1: Get a RoboShadow Refresh Token
Junto connects to RoboShadow with a refresh token issued for a RoboShadow user account. The agent can only see the organizations that account can access, so use an account that can see every customer you want to map.
- Ask RoboShadow support to issue an API refresh token for that account.
- Store the token securely. Junto only reads data with it.
Step 2: Configure in Junto
Go to Settings > Integrations > RoboShadow.
Click Add configuration.
Complete the form:
Field What to enter Refresh token The token from Step 1 Active Leave enabled to make the integration available to the agent. Turn it off to remove agent access without deleting the connection. Click Create configuration. Junto checks the token against RoboShadow before saving, so an invalid token is rejected with an error in the dialog. On success the button shows Saved and a Configuration created notice appears.
Junto encrypts the token when it is stored and never displays it again. The configuration shows that the refresh token is stored securely, when it was last updated, and an Active or Inactive status. Add configuration is disabled once a configuration exists.
Step 3: Test the Connection
Click Test connection. A successful test reports Connected to RoboShadow. Map companies to their organizations to enable reads. The test only reads which organizations the account can access and changes nothing in RoboShadow.
Step 4: Map Companies
Each Junto company maps to one RoboShadow organization, and each organization belongs to only one Junto company. An unmapped company cannot use the RoboShadow tools.
- Click Map companies.
- For each Junto company, select its RoboShadow organization, or leave it as Not mapped. An organization already chosen for another company can't be selected again.
- Click Save mappings and confirm the button shows Saved.
Map companies is available only while the configuration is Active. If a saved mapping shows Previously mapped organization (unavailable), the account can no longer access that organization; choose another organization or Not mapped before saving.
What the Agent Can Do
| Capability | What Junto can do | Risk level |
|---|---|---|
| Devices | List a customer's devices with operating system and version, online state, last scan time, pending reboot, and CVE and missing-update counts, or read one device's detail, including hardware, serial number, IP and MAC address, last boot, and health scores | Low |
| Installed software | List the applications installed on one device with vendor, version, and install date, including end-of-life flags | Low |
| Software inventory and upgrades | List software across the customer's devices, with versions, device counts, and available third-party (WinGet) upgrades, and drill into one application's installs | Low |
| Security summary | Read the customer's overall vulnerability and Windows update totals, such as how many devices have critical CVEs or need security updates or a reboot | Low |
| Vulnerabilities | List the customer's CVEs with CVSS and EPSS scores, known-exploited status, and affected device and application counts; group them by application, product, or device; or list the CVEs attributed to the applications on one device | Low |
| CVE fix guidance | For one CVE, see the affected devices, their installed application versions, and the matching WinGet upgrade | Low |
| Windows updates | See missing update counts and reboot status for every device, or list the specific updates missing on one device with update ID, category, and whether each is mandatory | Low |
| Remediation history | Review past remediation attempts with action, device, timing, and outcome, and the CVEs each attempt addressed. History defaults to the last 30 days | Low |
| Antivirus | Read antivirus coverage by device, detected threats, ransomware protection, and Windows Defender settings, or one device's antivirus status and threat history | Low |
| Firewall | Check firewall status for the domain, private, and public profiles across the customer's devices | Low |
| Hardware and disks | Read hardware inventory with operating system end-of-life flags, disk capacity and encryption status, and shared folders on a device's disks. Recovery keys are never returned | Low |
| Device details | List a device's services, local user accounts (including admin flags), and user profiles | Low |
| Microsoft MFA | List the customer's Microsoft accounts with MFA status and registered methods, Global Administrator flags, and whether security defaults are on | Low |
| Portal users | List who can access the customer's organization in RoboShadow and their permissions | Low |
| Vulnerability scans | List the customer's network vulnerability scans with status and counts, read a scan's summary, and list each scanned target's findings by severity | Low |
All RoboShadow tools are read-only. Read-only tools do not require approval: each ships with Approval set to Automatic and is visible to all staff. Admins can change either setting per tool under Tool Policies.
Scope and Reporting
- Customer context: Every tool works on one mapped company at a time. In a ticket chat, the agent uses the ticket's company. In an organization-wide Explore chat, name the company, or ask for a report across every company mapped to RoboShadow.
- Ownership checks: The agent only reads devices and scans that belong to the company's mapped RoboShadow organization. A device from another customer is refused, even if you supply its ID.
- Where tools are available: RoboShadow tools are available in Explore, ticket chat, and through your connected MCP client. They aren't used during automatic ticket triage or in runbooks.
- Windows inventory: Device, software, and update data covers the Windows devices RoboShadow manages.
- Upgrades aren't patches: An available WinGet upgrade means a newer version exists, not that it was installed. Remediation history describes past attempts, not the device's current state.
- Unknown isn't healthy: When RoboShadow reports no value for a status, the agent says the status is unknown rather than treating it as protected or compliant.
- Complete lists: Lists are returned 50 rows at a time by default, up to 100. The agent keeps paging before reporting totals, and summary samples are examples, not full inventories.
Example requests:
- "Give me a security summary for Acme from RoboShadow."
- "Which of Acme's devices have critical CVEs or need a reboot?"
- "What Windows updates is ACME-LT-042 missing?"
- "Is Google Chrome out of date anywhere at Acme, and is there an upgrade available?"
- "How do we fix CVE-2024-38063 on Acme's devices?"
- "Which Acme devices don't have BitLocker encryption on their system drive?"
- "Which Microsoft accounts at Acme don't have MFA enabled?"
- "Summarize the latest RoboShadow vulnerability scan for Acme."
Managing the Connection
- Replace the token: Click Edit, paste the new token into Refresh token, and click Update configuration. Leave the field blank to keep the stored token. Replacing the token clears every company mapping, so map companies again after saving.
- Pause the integration: Click Edit, turn off Active, and click Update configuration. The configuration stays saved, the agent loses access, and Map companies is disabled until you reactivate.
- Remove the integration: Click Disconnect and confirm. This removes Junto's saved refresh token and company mappings. Nothing changes in RoboShadow.
Troubleshooting
- The token is rejected when saving, or "RoboShadow denied access": The token may be invalid, revoked, or issued for an account without access to your organizations. Get a new token and update the configuration, then map companies again.
- An organization is missing from the mapping dialog: The account behind the token can't access it. Grant that account access in RoboShadow, or connect with a token for an account that can see it.
- Map companies is disabled: The configuration must be Active. Click Edit, turn on Active, and save.
- Saving mappings fails because settings or mappings changed: Someone else changed the configuration or mappings while the dialog was open. Close and reopen Map companies, then save again.
- The agent says a company is not mapped: Open Map companies and assign that company's RoboShadow organization.
- A device is reported as outside the company or not found: The device belongs to a different organization than the one mapped, or its ID changed. Check the mapping, or ask the agent to list the company's devices again.
- A report is unavailable: Some reports, such as ransomware protection, may not be available for every RoboShadow organization. The agent says so and uses the other antivirus reports instead.
- RoboShadow is temporarily unavailable or rate limited: Wait a moment and try again.
- The agent can't install an update or run a scan: The integration is read-only. Deploy patches and start scans in the RoboShadow portal.