> ## Documentation Index > Fetch the complete documentation index at: https://hilt.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Trust & Security > Hilt's trust model: customer-owned single-tenant deployment, least-privilege access, transparent data handling, and defense in depth. Hilt is **Data Movement Governance (DMG)** that runs inside your own cloud account. (Historically this category was often called data detection and response, or DDR.) Your telemetry, the analytics database, and the dashboard live in infrastructure Hilt provisions in your account, and Hilt operates the platform without standing access to it. This section documents how that model protects your data and gives security reviewers the detail needed to evaluate Hilt against a vendor questionnaire. *** ## Trust principles * **Customer-owned infrastructure and data.** Every deployment is single-tenant, provisioned in your cloud account (AWS, GCP, Azure, or Ali Cloud). Telemetry, the analytics store, and the dashboard stay in your account. * **No covert egress.** Collector telemetry has one destination: the ingest endpoint in your account, reached over private networking. Nothing leaves your account except the anonymized export pipeline, which — when approval is enabled (the default) — you review and approve before each transfer. * **Least privilege, approval-gated access.** Hilt engineers hold no standing access to your environment. Access happens only through your approval workflow and is logged. * **Transparency.** What the collector observes (and what it never observes) is documented and enforced in the collector itself. File contents are captured only when you opt a host into content inspection. * **Defense in depth.** Controls layer across network (private subnets, private link), identity (role-based access, team scoping), encryption (TLS 1.2+, KMS at rest), and application (event filtering, audit logging). *** ## Architecture at a glance Collectors on your hosts stream metadata-level telemetry over private networking to an ingest endpoint in your account. Events are buffered, enriched, scored, and stored in an analytics database, then surfaced in a dashboard, all within your cloud boundary. The only path out of your account is the anonymized export pipeline, a core component of every deployment that runs on a daily schedule and, with approval enabled (the default), requires your approval before each transfer. For the component map, per-cloud service list, and a data-flow diagram, see [Architecture and data flow](https://hilt.ai/docs/trust-security/architecture.md). *** ## Control summary | Control area | Implementation | Responsibility | | :- | :- | :- | | Deployment model | Single-tenant in your cloud account, provisioned with Terraform | Hilt provisions, you grant scoped access | | Network isolation | Private subnets, private link ingest, no public ingress | Shared | | Encryption in transit | TLS 1.2+ on external/ingress connections; private networking internally | Hilt | | Encryption at rest | Cloud-provider-managed encryption (KMS / SSE) on storage | Hilt design; keys in your account's KMS (CMKs optional) | | Data residency | Telemetry stays in your cloud account | Hilt design, you own the account | | Identity and access | Dashboard role-based access with team scoping | You | | Hilt engineer access | Approval-gated, time-bound, logged, no standing access | Shared | | Data collection | Metadata only by default; optional Linux content inspection is off unless you enable it | Hilt design | | Data export | Anonymized, reviewable before transfer | You (approve each export) | | Response controls | Quarantine and custom detection rules | You | *** ## Shared responsibility Hilt operates the platform; you own the cloud account it runs in. Responsibilities split as follows. | Area | Customer | Hilt | | :- | :- | :- | | Cloud account security | Secure and monitor the account, IAM, and org guardrails | Operate only within the scope you grant | | Network configuration | Configure firewall and routing per the deployment guide | Provide requirements, provision the private ingest | | Collector deployment | Deploy and upgrade collectors (or enable auto-update) | Provide artifacts, guides, and the auto-update agent | | Platform infrastructure | Approve maintenance windows | Provision, patch, upgrade, and monitor platform components | | Dashboard user management | Create users, assign roles and teams | Provide the role-based access model | | Encryption keys | Provider-managed by default; supply a CMK if you require one | Enable provider encryption on platform storage | | Data export approval | Review the manifest, approve or delete each export | Provide the pipeline and anonymization controls | | Incident response | Report incidents, act on findings, quarantine hosts | Investigate platform issues and notify you | *** ## In this section * [Architecture and data flow](https://hilt.ai/docs/trust-security/architecture.md): single-tenant model, component map, per-cloud services, network boundaries, and a data-flow diagram. * [Data collection and handling](https://hilt.ai/docs/trust-security/data-handling.md): what the collector captures, what it never captures, filtering, retention, and the export summary. * [Access and identity](https://hilt.ai/docs/trust-security/access-control.md): dashboard authentication, role-based access, team scoping, audit logging, and the Hilt engineer access model. * [Encryption and key management](https://hilt.ai/docs/trust-security/encryption.md): TLS in transit, KMS at rest, certificate handling, and key ownership. * [Security operations](https://hilt.ai/docs/trust-security/operations.md): software supply chain, patching, monitoring, backups, and change management. * [Compliance and legal](https://hilt.ai/docs/trust-security/compliance.md): frameworks, audit reports available under NDA, subprocessors, and data processing roles. * [Incident response and vulnerability disclosure](https://hilt.ai/docs/trust-security/incident-response.md): how to report incidents and vulnerabilities, and what to expect in return. *** ## Reporting a security issue To report a suspected incident or a vulnerability in Hilt, contact your Hilt representative or account team. See [Incident response and vulnerability disclosure](https://hilt.ai/docs/trust-security/incident-response.md) for the process and what information to include. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.