ConnectSecure

Overview

ConnectSecure (formerly CyberCNS) is a vulnerability and compliance management platform built for MSPs. It scans client environments with Lightweight and Probe agents, scores risk, tracks remediation, checks compliance frameworks (PCI, HIPAA, CIS, Essential Eight, ...), and monitors the external attack surface.

The Bumblebee integration is read-only reporting: it queries companies, risk scores and posture rollups, assets and agent coverage, vulnerabilities (including CVE lookups), problems and remediation plans, compliance results, and external scan findings. It never triggers scans, patches, or any other write operation.

Prerequisites & Setup

Before setting up the ConnectSecure integration, you need:

Your pod URL — the host you land on after signing in, e.g. https://pod401.myconnectsecure.com
Your tenant name — a lowercase identifier found on the Organization page
An API key (Client ID + Client Secret) generated for a portal user

Find your Pod URL

Sign in to ConnectSecure and wait until you land on the dashboard. The pod URL is https:// plus the host now shown in the address bar.

The host you sign in through is not always your pod. Authentication happens on a shared login host and then redirects you to the pod that actually holds your data. Only the address bar after the redirect is the pod URL — using the login URL produces credentials that never authorize.

Format rules:

Must start with https://
No path — do not append /w/authorize or anything after the host

	Value
✅	`https://pod401.myconnectsecure.com`
❌	`pod401.myconnectsecure.com` (no scheme)

Find your Tenant Name

Open the Organization page in the ConnectSecure portal and copy the tenant name shown there. Enter it exactly as it appears, in lowercase.

The tenant name is case-sensitive and lowercase. It is an identifier, not your company's display name — Acme fails where acme works. Bumblebee sends it verbatim inside the authorization token and cannot correct the casing for you.

Do not take the tenant name from anywhere else. The value in the sign-in host, on your user profile page, and on the dashboard home are all different from the tenant name the API expects. Only the Organization page is authoritative.

Generate an API key

Sign in to your ConnectSecure portal
Go to Global → Settings → Users
Open the three-dot action menu next to the user the key should belong to and select API Key
Copy the revealed Client ID and Client Secret

The API key inherits the permissions of that user — use a dedicated read-only user where possible. Trial accounts may not expose the API Key menu yet; contact ConnectSecure support to enable API access. See the vendor's V4 API Information page for details.

Configure in Bumblebee

Go to the Integrations page in Bumblebee
Select ConnectSecure
Enter your Pod URL, Tenant Name, Client ID, and Client Secret
Save the configuration
Run a test request (e.g. list companies) from the validation card

list_companies — List client companies; the anchor for everything else (resolve a company name to its company_id, then filter other queries with it).
query_company_stats — Per-company posture rollups. Resources: company_stats (asset/vulnerability/problem/compliance counts, scan times), risk_score (risk score per company).

Assets (1 tool)

query_assets — Asset inventory and agent coverage. Resources: asset_view, assets, asset_stats, agents, asset_ports_view, asset_software, cert_info_view (SSL certificates incl. expiry), os_pending_patches.

Vulnerabilities (1 tool)

query_vulnerabilities — Vulnerability findings. Resources: application_vulnerabilities, vulnerabilities_details, asset_wise_vulnerabilities, asset_critical_vulnerabilities, cve_report (lookup by CVE id via the cve argument).

Problems & remediation (1 tool)

query_problems_remediation — Problem rollups and remediation tracking. Resources: problems_summary, problem_group_summary, problems_summary_group_by_companies, remediation_plan_by_company, remediate_records, remediation_velocity_company.

Compliance (1 tool)

query_compliance — Compliance posture. Resources: types (available frameworks), asset_compliance_report_data (needs asset_id + company_id), compliance_check_count, compliance_maturity, compliance_asset_info.

Attack surface (1 tool)

query_attack_surface — External exposure. Resources: attack_surface_domain, attack_surface_results, external_asset_externalscan, external_asset_ports_data, external_asset_vulnerabilities, external_asset_ssl_attack.

Directory services (1 tool)

query_directory_services — AD / Azure AD (Entra ID) reporting. List resources: ad_users_view, ad_computers_view, ad_groups_view, ad_gpos_view, ad_ous_view, ad_roles, ad_password_policies, ad_user_licenses, azure_licenses, azure_secure_score, azure_ad_logs. Detail resources (need company_id plus object_guid and/or source): ad_basic_info, ad_group_users, ad_group_computers, get_user_details, get_computer_details.

Example prompts

"What's the risk score for each of my companies in ConnectSecure?"
"Show the critical vulnerabilities for Acme Corp, most exploitable first"
"Which assets are missing an agent, and which have pending OS patches?"
"Summarize Acme's external attack surface and SSL weaknesses for the QBR"
"List Acme's AD users with password issues, and what's their Microsoft Secure Score?"