> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# ConnectSecure

> Let Neo agents put a device's vulnerabilities and missing patches on its ticket, open tickets for new critical findings, and sum up a client's risk

ConnectSecure (formerly CyberCNS) is a vulnerability and attack-surface management platform for MSPs. Its agents and probes scan each client's devices, Active Directory, firewalls and external domains, and it reports each vulnerability with its severity, EPSS and CISA KEV status, the missing patches and the fix. Each of your clients is a ConnectSecure company. Connect it, and Neo agents can bring that data to the ticket, to your PSA and to your QBRs.

## What Neo can do with ConnectSecure

* **Risk on the ticket:** find the device a ticket names by name or IP, and add its critical and high vulnerabilities, missing patches and fixes to the ticket
* **New critical findings:** a scheduled agent opens one PSA ticket per client for new critical and high vulnerabilities, and adds later findings to the same ticket while it is open
* **QBR and risk summaries:** a client's vulnerability counts and trend, risk score, top vulnerabilities, top fixes and compliance results, and ConnectSecure's own PDF reports
* **Assets:** devices with their software, ports, users and protection status, and the ConnectSecure agents and probes
* **Act on a finding:** rescan a device, patch an application or the OS, or suppress a finding with a reason and an end date, as you allow

See [ConnectSecure API](https://docs.neoagent.io/agents/tools/security/connectsecure-api.md) for the permission groups.

## Your companies are mapped to your PSA companies

Neo matches your ConnectSecure companies to the companies in your PSA and keeps the mapping on the ConnectSecure card's **Organization Mapping** tab, refreshed on each PSA metadata sync.

When ConnectSecure's own PSA integration maps a company to a PSA company with the same name, Neo uses that mapping. Otherwise matching uses the company name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Next comes the company's domain against a PSA company's website. Last comes an AI match for the long tail.

**ConnectSecure's own mapping, a name match, or one you confirm, is handed straight to your agents.** A domain match or an AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync.

On a ticket, an agent works in ConnectSecure only on the company mapped to the ticket's company, and ConnectSecure's settings stay out of reach. A company with no mapping that agents can use gets no ConnectSecure calls until you set or confirm one on the tab. Agents with no ticket, such as a chat or a scheduled report, reach every company.

## A template for new critical findings

The **ConnectSecure Vulnerability Tickets** template runs every weekday morning on Autotask and ConnectWise. It reads the critical and high vulnerabilities ConnectSecure found since the last run and keeps one open ticket per client that lists them, worst first.

## Next steps

> [card] [Connect ConnectSecure](https://docs.neoagent.io/integrations/connectsecure/connecting-to-neo.md)
>
> Copy your pod's address and a user's API key, and save them in Neo.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.