MDR coverage gaps next to asset inventory
Devices that are in your RMM but have no ESET Inspect license show as an MDR coverage gap alongside warranty, patch status, and backup coverage on the same asset row.
Endpoint Security integration
See which devices are ESET-protected, what threats have fired, and MDR coverage gaps — next to every ticket, backup job, and RMM alert.
In Beta
Vectis + ESET Connect is in Beta. We built this connector against ESET Connect’s published API documentation (verified endpoints in scripts/audit/known-endpoints/eset.json). It’s fully connectable today — credentials save and syncs run. Because ESET Connect doesn’t offer a public sandbox for us to live-test against, the first paying customer who connects it is the de-facto live validator. If you’re considering Vectis with ESET Connect and want to be the validator, talk to us.
What Vectis syncs
Vectis syncs every managed device from ESET Connect — protection status, agent version, and the active ESET product tier (ESET Inspect for MDR vs ESET Protect for standard AV). Detection events (threat name, severity, affected path, SHA-1 hash) are pulled and linked to the device and customer. If your account includes ESET Inspect, incidents and their linked detections sync as well.
What you can do
Resolve ESET detections from the Vectis alert card without opening the ESET console. Move a device to an ESET quarantine group via a rule — useful for automatically isolating a device when a critical detection fires. If your account includes ESET Inspect, you can close incidents from Vectis. Vectis does not support triggering on-demand scans or network isolation — those are not available in the ESET Connect REST API.
Honest about the limits
ESET Connect covers ESET cloud-managed endpoints only — ESET PROTECT On-Premises uses a different API and is not supported. Incidents (ESET Inspect) require the ESET Inspect subscription tier; without it, Vectis shows detections but no incident groupings. MDR enrollment status is inferred from the activeProducts field — a device licensed for ESET Inspect counts as MDR-covered. On-demand scans and network isolation are not available via the ESET Connect REST API.
How it correlates
ESET Connect on the customer account hub alongside every other system you run — not a standalone dashboard. A few of the most common shapes this takes:
Devices that are in your RMM but have no ESET Inspect license show as an MDR coverage gap alongside warranty, patch status, and backup coverage on the same asset row.
When a high-severity ESET detection fires on a customer device, the alert card surfaces the detection detail and lets you open a PSA ticket pre-populated with the device name, threat name, and SHA-1 hash.
A device with ESET ATTENTION_REQUIRED or ATTENTION_RECOMMENDED status lowers the customer's EDR coverage posture score, appearing on the customer health strip alongside MFA and backup findings.
Setup snapshot
Go to Admin → Integrations and click Add connection under Endpoint Security → ESET Connect. Enter your ESET Connect account email, password, and select your region (the region appears in your ESET Connect portal URL — e.g. us.esetconnect.eset.systems is US). Vectis obtains an OAuth token and syncs your managed devices immediately. Customer matching uses the device grouping structure in your ESET Connect account — devices in groups named for a customer map automatically; unmatched devices appear in the unassigned list for manual linkage.
# In the Vectis hub, add the connector:
category Endpoint Security
vendor ESET Connect
status Read + WriteOther Endpoint Security integrations
Pricing
ESET Connect is available on every Vectis tier — $299/mo and up. See pricing
Also reachable over MCP — bring your own client → /mcp