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

# Security Overview

> An overview of the controls and practices Doris uses to protect customer data.

Doris processes sensitive sales conversations, deal data, and CRM information. We treat security as a core product requirement. This trust center provides a high-level overview of our security practices and is intended for general information only. Customer-specific commitments are governed by contract.

## Security at a Glance

<CardGroup cols={2}>
  <Card title="Infrastructure Security" icon="shield-halved" href="/security/infrastructure">
    Cloud-native architecture on Microsoft Azure with WAF, private networking, and edge protection.
  </Card>

  <Card title="Application Security" icon="lock" href="/security/application">
    Authentication, rate limiting, input validation, and multi-tenant data isolation.
  </Card>

  <Card title="Data Protection" icon="database" href="/security/data-protection">
    Encryption at rest, transport security, and managed key handling for core service data.
  </Card>

  <Card title="Compliance" icon="file-certificate" href="/security/compliance">
    GDPR-focused practices, sub-processor transparency, and assurance posture.
  </Card>

  <Card title="Incident Response" icon="bell" href="/security/incident-response">
    Customer notification, documented response procedures, and security event logging.
  </Card>
</CardGroup>

## Security Practices

| Area                  | Standard                                                                                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Encryption at rest    | Encryption is enabled for primary production data stores, with additional protections applied to selected sensitive credentials |
| Encryption in transit | Supported service connections require TLS 1.2 or higher, with newer protocols used where available                              |
| Incident response     | Customer notification for confirmed notifiable incidents is handled in line with applicable law and contract terms              |
| Data residency        | Primary hosting is in Microsoft Azure UK South, subject to service configuration and approved subprocessors                     |
| Data deletion         | Data retention and deletion follow contractual terms, operational safeguards, and backup lifecycle requirements                 |
| Assurance             | Our security program is aligned to common control frameworks and continues to mature over time                                  |

## Architecture Principles

* **Defence in depth** — Layered controls are applied across edge, application, network, and storage boundaries
* **Least privilege** — Access is scoped using managed identities, roles, and approval-based controls
* **Private by default** — Backend connectivity is designed to minimize unnecessary public exposure
* **Encryption by default** — Production data is encrypted at rest and in transit across supported service paths
* **Auditable operations** — Security-relevant events are logged and monitored to support investigation and review

<Info>
  Questions about our security practices? Contact us at [security@meetdoris.com](mailto:security@meetdoris.com).
</Info>