> ## 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 API

> Read a client's or a device's vulnerabilities, missing patches, risk score and compliance from ConnectSecure, open tickets for new critical findings, and run scans and patches

The common uses are a ticket about a device, where the agent adds the device's ConnectSecure vulnerabilities, missing patches and fixes to the ticket, and a scheduled agent that opens one PSA ticket per client for new critical and high vulnerabilities.

> [!NOTE]
>
> Automatically enabled when you configure ConnectSecure permissions in your agent workflow.

## What It Does

* Find a device by name, IP or company, and read its vulnerabilities with severity, CVSS, EPSS and CISA KEV status, its missing patches and the fix for each
* Read a client's vulnerability counts and trend, risk score, top vulnerabilities and top fixes, for a ticket or a QBR
* Read compliance results per framework and check, and create ConnectSecure's own PDF reports
* Read the ConnectSecure agents and probes, Active Directory reports and firewall data
* Start a scan, patch applications or the OS now or later, and suppress a finding with a reason and an end date
* Read and change ConnectSecure's settings: discovery, scan credentials (their secrets hidden), alert rules, baselines, tags and PSA integrations

## Permission Groups

| Group | Access levels | Covers |
| - | - | - |
| Companies | Disabled, Read Only, Read/Write | Your clients in ConnectSecure with their statistics, and the tickets ConnectSecure opened |
| Assets and Agents | Disabled, Read Only, Read/Write | Devices, their software, ports, users and protection status, ConnectSecure agents and probes, Active Directory and firewall reports |
| Vulnerabilities and Suppressions | Disabled, Read Only, Read/Write | Vulnerabilities, missing patches, remediation plans, risk scores, attack-surface findings, and suppressions |
| Scans and Patching | Disabled, Read Only, Read/Write | Scan jobs, scheduled scans and patch settings; starting a scan and patching |
| Compliance and Reports | Disabled, Read Only, Read/Write | Compliance results and assessments, and ConnectSecure's standard reports |
| Settings and Integrations | Disabled, Read Only, Read/Write | Discovery settings, scan credentials, alert rules, ticket templates, baselines, tags, PSA integrations and users |

Neo always asks a technician before it deletes a company, updates an asset, or changes a scan credential, the discovery settings, which credential a probe uses where, a PSA integration's credential or rule, or a scheduled scan, whatever the group's approval setting. It never reads the agent uninstall secret, and a patch must name the applications it installs. Passwords and keys in ConnectSecure's answers are hidden from the agent. On a ticket, the agent works only on the ConnectSecure company mapped to the ticket's company.

## Setup

See [Connecting ConnectSecure to Neo](https://docs.neoagent.io/integrations/connectsecure/connecting-to-neo.md).


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