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

# TridentStack

> Let Neo agents read each endpoint's TridentStack health, updates, CVEs and compliance on your security and patching tickets, and install or restart with your approval

TridentStack Control is patch management, vulnerability detection and compliance for Windows and Linux endpoints. Its agent on each endpoint reports health, applicable updates, installed software, CVEs and compliance scores, and installs the updates your policies and deployment rings approve. Connect it once with an API key, and Neo agents can read and act across the customer Organizations the key reaches.

## What Neo can do with TridentStack

* On a security, patching, vulnerability or compliance ticket, find the PC or server the ticket names by hostname in the customer's Organization, and write an internal note: its health, pending critical and security updates, failed installs, deployment status, top CVEs (known exploited first) and compliance drift
* Read a CVE across a customer's endpoints, and the update that fixes it
* Rescan an endpoint or evaluate its compliance again after a fix
* Install updates or restart an endpoint, with a technician's approval under the Helpdesk preset. Changing an update or configuration policy needs the IT Admin or Full Automation preset, or Read / Write on that policy group
* Read a customer's patch, vulnerability and compliance numbers for a QBR or a report

## Each ticket stays with its customer

One TridentStack key reaches every Organization the person who created it can see. On a ticket that names a company, Neo sends a call only inside the Organization that company is mapped to, and refuses the list of Organizations and any call on your main account. Those run from a chat with Neo or a scheduled agent.

## Installs and restarts ask first, by default

The Helpdesk preset reads everything and runs scans on its own, and asks a technician before Neo installs updates, restarts an endpoint or changes its settings; it changes no policy. IT Admin installs and restarts on its own, and asks before a vulnerability exception, a compliance exemption or an account setting. Removing an endpoint from TridentStack always asks, whatever the agent's settings, because TridentStack then stops patching and scanning it. So does replacing a whole settings, enrollment token, application or policy record, because a field the change leaves out could clear a stored password.

## Secrets stay out of the run

Neo hides each enrollment token's value, and any stored password or secret in a settings answer, before the agent or a script reads it. Neo also refuses a change that would send one of those hidden values back, so a stored password is never overwritten.

## Your customers are mapped to companies

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

Matching uses the Organization name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC), and last an AI match for the long tail. Your default Organization, named after your account with "(Default)" at the end, matches your own company. An archived Organization gets no new match.

**A name that matches exactly one of your PSA companies, as it is or after stripping a legal-form suffix, or a match you confirm, is handed straight to your agents.** An AI match waits for you on the Organization Mapping tab. A name two of your PSA companies share, or two Organizations that match one company, is left unmapped until you set it. Confirm or correct each there; a mapping you set by hand survives every later sync.

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

## Next steps

> [card] [Connect TridentStack](https://docs.neoagent.io/integrations/tridentstack/connecting-to-neo.md)
>
> Create an API key and save it in Neo.


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