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

# Senteon

> Let Neo agents read each endpoint's Senteon hardening status, compliance, drift and alarms on your hardening, CIS and compliance tickets

Senteon hardens Windows endpoints: its agent applies a CIS-based configuration baseline, checks each setting, corrects drift, and raises an alarm when a setting drifts or fails to apply. Connect it once with an API key, and Neo agents can read the tenants the key reaches.

Senteon's Public API is read-only, so Neo reads Senteon and changes nothing in it. A change to a baseline, an exception or an endpoint stays in the Senteon Command Center.

## What Neo can do with Senteon

* On an endpoint hardening, CIS or compliance ticket, find the PC or server the ticket names by host name in the customer's tenant, and write an internal note: its status, configuration health, baseline, how many managed settings are on target, and its active alarms with the settings that drifted or failed to apply
* Answer for a whole customer: how many endpoints are active, offline or waiting for a setup step, which ones drifted, and the customer's alarms
* Give the technician the context to open the endpoint in Senteon: the Command Center link, the tenant, the host name and the endpoint's id
* Read a customer's hardening numbers for a review or a QBR

## Each ticket stays with its customer

One Senteon key reaches every tenant it may read. On a ticket that names a company, Neo sends a call only for the tenant that company is mapped to, and refuses the list of every tenant. Every answer is cut to the tenant the call names, and Neo reads an endpoint's compliance only after it confirms the endpoint is in that tenant, because host names repeat across tenants. A cross-tenant read runs from a chat with Neo or a scheduled agent.

## Your customers are mapped to companies

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

Matching uses the tenant name, with its hyphens and underscores read as spaces (`Contoso_Dental` matches "Contoso Dental"): exact, then after stripping a legal-form suffix (Ltd, Inc, LLC), and last an AI match for the long tail.

**A name that matches exactly one of your PSA companies, 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 tenants 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 [Senteon API](https://docs.neoagent.io/agents/tools/security/senteon-api.md) for the permission groups.

## Next steps

> [card] [Connect Senteon](https://docs.neoagent.io/integrations/senteon/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.