Appearance
DefensX Setup
Connect DefensX to let Junto investigate DNS and browser security for your customers. The agent can review a customer's DNS, web, credential, and file-transfer activity, check which DefensX agents and browser extensions are in use, read policies and custom URL rules, and see top categories, blocked sites, and cyber resilience scores. With approval, it can also add or remove URL rules, manage your partner policy templates, change a customer's timezone, and provision new DefensX customers.
Junto supports one DefensX configuration per organization. Connect your DefensX Partner account once with an API key, then map each Junto company to its DefensX customer so the agent works with the right customer's data.
Prerequisites
- A Junto Admin or Owner account
- A DefensX Partner account with access to the API Keys page in the Partner Dashboard
- Customer companies in Junto, imported from your PSA, to map to DefensX customers
Step 1: Create a Partner API Key in DefensX
- Sign in to the DefensX Partner Dashboard.
- Open the API Keys page and generate a new key for Junto.
- Copy the key and store it securely.
The agent can only do what the key permits. Use a key with access to your customers so Junto can discover them for mapping. Access to activity logs, admin users, and changes depends on the key's permissions in DefensX. If you restrict the key to specific IP addresses, Junto may not be able to connect; create the key without an IP restriction.
Step 2: Configure in Junto
Go to Settings > Integrations > DefensX.
Click Add configuration.
Complete the form:
Field What to enter API key The Partner API key from Step 1 Active Leave enabled to make the integration available to the agent. Turn it off to remove access without removing the configuration. Click Create configuration. Junto verifies your partner account before saving the key, so an invalid key is rejected with an error in the dialog. On success the button shows Saved and a Configuration saved notice confirms your DefensX Partner account is connected.
Junto encrypts the key when it is stored and never displays it again. The Partner API configuration card shows when it was created and an Active or Inactive badge. Add configuration is disabled once a configuration exists.
Step 3: Test the Connection
Click Test connection. The result reports three checks separately:
- DefensX is reachable -- the DefensX service responded.
- Partner account verified -- the key belongs to a valid partner account.
- Customer discovery available -- the key can list your customers, with the number it found.
A passing test doesn't prove the key can read every log or make every change. Those depend on the key's permissions in DefensX. The test only reads data and changes nothing in DefensX.
Step 4: Map Companies
Each Junto company maps to one DefensX customer, and each customer belongs to only one Junto company. An unmapped company cannot use the DefensX customer tools.
- Click Manage company mappings to open Map companies to DefensX customers.
- Select a Junto company, then its DefensX customer. Customers already mapped to another company are marked (already mapped).
- Click Save mapping. Repeat for each company.
Mappings are explicit; Junto never maps companies automatically by name. Your partner account's own customer record can't be mapped to a customer company. Selecting a company that is already mapped shows its current customer, so you can change it and save again. To remove a mapping, click Remove next to it under Existing mappings, then Confirm removal.
Manage company mappings is available only while the configuration is Active. New DefensX customers, including ones the agent creates, must be mapped here before the agent can work with them.
What the Agent Can Do
Customer Reads
| Capability | What Junto can do | Risk level |
|---|---|---|
| Customer details | Read the mapped customer's name, enabled state, domains, and timezone | Low |
| Agents | List DefensX agents installed for the customer with hostname, platform, version, role, last seen, and whether each was uninstalled | Low |
| Deployments | List the customer's deployment configurations. Deployment tokens are left out | Low |
| Deployment credentials | Retrieve the token for one selected deployment, for example to install the agent. Minimum role Admin | Low |
| Users and groups | List the customer's DefensX users and groups | Low |
| Browser extensions | List browser extensions seen at the customer with reputation and user counts, or only low-reputation extensions | Low |
| Activity logs | Read DNS, web (browser extension and mobile), credential, file transfer, consent, remote browser isolation, and audit events for a time window. Defaults to the last 24 hours, and reaches back up to 90 days | Low |
| Top categories and sites | See the top 20 web categories, hostnames in a category, uncategorized and blocked hostnames, blocked categories, and sites where credentials were entered or blocked | Low |
| Cyber resilience | Read the customer's resilience scores and its 10 riskiest users | Low |
| Policies | List the customer's policies with their targets and precedence, and read one policy's configuration | Low |
| Custom URL rules | List the customer's custom URL groups, search groups by hostname, and read the rules in a group | Low |
| Subscription usage | Read current or historical subscription usage and per-user usage detail. Minimum role Admin | Low |
| Reference lists | List DefensX products, message templates, and web filter categories | Low |
Partner Reads
These tools work across your partner account rather than one customer, so they're available only in an organization-wide Explore chat.
| Capability | What Junto can do | Risk level |
|---|---|---|
| Partner status and customers | Read your partner account status and customer count, list your DefensX customers, and read your partner account's own customer record | Low |
| Partner admin users | List your partner admin accounts with their admin level and enabled state. Minimum role Admin | Low |
| Policy templates | List your partner policy templates and read one template's settings, including whether it has changes waiting to be deployed. Reading a template's settings has a minimum role of Admin | Low |
| Partner URL groups | List and search your partner-level custom URL groups and read their rules | Low |
Changes
| Capability | What Junto can do | Risk level |
|---|---|---|
| Change customer timezone | Set or clear the mapped customer's timezone | Medium |
| Create URL group | Create a private custom URL group for the mapped customer | High |
| Delete URL group | Delete one of the customer's private URL groups and all of its rules | High |
| Add URL rules | Add up to 1,000 rules to one of the customer's private URL groups in one request, up to 5,000 rules per group | High |
| Delete URL rule | Remove one rule from one of the customer's private URL groups | High |
| Delete policy | Delete one of the customer's policies. Default policies are refused | High |
| Create, update, or delete policy template | Create a partner policy template, change selected settings on one, or delete one that isn't assigned to customers. Organization-wide Explore chat only | High |
| Create partner URL group | Create a partner-level URL group, either private or shared with every customer's policies. Organization-wide Explore chat only | High |
| Create customer | Provision a new DefensX customer with a subscription. Requires the Billing Admin flag. Organization-wide Explore chat only | High |
All write actions require technician approval before execution. Read-only tools do not require approval. Every write tool ships with a Minimum role of Technician and Approval set to Always. Except for the timezone change, DefensX changes are always confirmed by a person: their approval cannot be set to Automatic or Per session. Admins can change either setting per tool under Tool Policies.
Scope and Reporting
- Customer context: Customer tools work 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 first.
- Where tools are available: DefensX tools are available in Explore, ticket chat, and through your connected MCP client. Partner tools need an organization-wide Explore chat. DefensX isn't used during automatic ticket triage or in runbooks.
- Activity is observed evidence: DNS logs normally leave out allowed queries, and web logs cover browser extension and mobile activity. An empty log doesn't prove an application or site isn't in use, and activity isn't a complete software inventory.
- Fixed time windows: For a long export, the agent keeps the same start and end time on every page so results stay consistent. Audit log history depends on your DefensX subscription.
- Top lists aren't totals: Category and hostname statistics return the top 20 only, and cyber resilience lists the 10 riskiest users, not every user.
- Inherited groups are read-only: Shared URL groups a customer inherits from your partner account appear in its lists, but the agent can only change the customer's own private groups.
- Templates aren't deployed automatically: Saving a policy template doesn't push it to customers. The agent reports whether the template has changes waiting to be deployed; deploy it from DefensX.
- Request pacing: Junto paces its requests to DefensX, so large exports can take a little time.
Changes and Approvals
The approval request names the customer, or your partner account for partner changes, and exactly what will change. For a policy template, it previews the settings being changed and says when more settings are included than it can show. Free-form text such as names and URLs is left out of the template preview.
Before asking for approval, Junto re-reads the target to confirm it belongs to the customer: a URL group must be one of the customer's own private groups, a rule must belong to that group, and a policy must not be a default policy. It checks again before running. If the company mapping, the DefensX connection (including a replaced API key), or the target itself changes after approval, Junto stops the action and asks for fresh approval.
After a change, Junto reads the result back from DefensX and reports whether it was confirmed. If DefensX doesn't confirm the outcome, the agent checks the current state before suggesting anything else and never resends a change automatically. When adding URL rules, any rules DefensX rejects are listed individually.
These aren't available through Junto: creating or editing customer policies, adding or removing rules in existing partner URL groups, deleting partner URL groups, deploying or assigning policy templates, and listing the users of a browser extension. Use DefensX for those.
Example requests:
- "What DNS activity did DefensX block for Acme in the last 24 hours?"
- "Which DefensX agents at Acme haven't been seen in the last week?"
- "Does Acme have any low-reputation browser extensions installed?"
- "Show me Acme's top blocked categories this week and its cyber resilience score."
- "Which URL rules are in Acme's allow list for the accounting portal?"
- "Add portal.example.com to Acme's private allow-list group."
- "Change Acme's DefensX timezone to America/Chicago."
- "List our DefensX policy templates and tell me which have changes waiting to deploy."
Managing the Connection
- Replace the key: Click Edit, enter the new key in API key, and click Update configuration. Leave the field blank to keep the saved key. A new key for the same partner account keeps your company mappings, but pending approvals must be requested again.
- Connect a different partner account: Remove every DefensX company mapping first, then replace the key. Junto refuses a key for a different partner account while mappings exist.
- Pause the integration: Click Edit, turn off Active, and save. The configuration and mappings remain saved, the agent loses access, and Manage company mappings is disabled until you reactivate.
- Remove the integration: Click Delete and confirm. This removes the saved key and all DefensX company mappings from Junto. Your DefensX account is unchanged.
Troubleshooting
- The key is rejected when saving, or "Partner account verification failed": Check that the key hasn't been deleted in DefensX and belongs to a partner account. Replace it if needed.
- "Customer discovery is unavailable": The key can't list your customers. Check its access in the DefensX Partner Dashboard, then test again.
- No customers in the mapping dialog: Add the customer in DefensX, then click Retry customer discovery.
- "DefensX customer is already mapped to another company": Each customer can belong to only one Junto company. Remove the other mapping first.
- "Remove DefensX company mappings before connecting another partner account": The new key belongs to a different partner account. Remove the existing mappings, then save the key again.
- Manage company mappings is disabled: The configuration must be Active. Click Edit, turn on Active, and save.
- The agent says a company is not mapped: Open Manage company mappings and map that company to its DefensX customer.
- "The DefensX key does not permit this operation": The key lacks permission for that data or change in DefensX. Update the key's permissions, or use a key that has them.
- "DefensX rejected the activity window": Choose a more recent time range. Activity logs reach back up to 90 days, and audit history depends on your subscription.
- A partner tool isn't offered in a customer chat: Partner tools need an organization-wide Explore chat.
- A URL rule change was refused: The group is inherited from your partner account or isn't one of the customer's own private groups. Change shared groups in DefensX.
- A policy template can't be deleted: It's still assigned to customers. Unassign it in DefensX first.
- "DefensX is rate limited": Wait a moment and try again.
- "The DefensX outcome is unknown": DefensX didn't confirm whether the change was applied. Ask the agent to check the current state before requesting the change again.