Trust & Security

Zero trust needs evidence, not a slogan.

Holiday verifies every tool call against the AI identity and the requesting user, enforces trust rules outside the model and records every action. This page explains what is implemented, what is configurable and what remains in progress.

Request security documentation Explore governance Explore AI Security

Implemented trust architecture

Trust rules live outside the model.

The model can request an action, but it cannot grant itself access. Holiday makes and records the authorization decision in the application layer.

Dual verification

Every tool call is checked against both the AI identity’s authority and the requesting user’s permissions.

Scoped connections

AI operating inside Holiday uses approved connections assigned to its role rather than inheriting a person’s credentials.

Separate environments

Each customer receives a separate, single-tenant environment with its own business data and operating boundaries.

Attributable activity

AI actions are tied to the requesting person, digital employee or specialist and retained in an audit trail for review.

Data protection

Protected by infrastructure, not instructions.

Business data is stored in a secured, single-tenant PostgreSQL environment in the customer’s selected AWS region. These protections sit beneath the application, so data security never depends on a model following a prompt.

Encrypted: Database storage and backups are encrypted at rest using AES-256, while database traffic is protected in transit using TLS.
Isolated: The database operates on private networks with restricted, authenticated access rather than public database exposure.
Least privilege: Access is limited across people, application services and database operations according to the permissions required.
Recoverable: Automated, encrypted backups support recovery without moving data outside the protected customer environment.

Identity and sign-in

Authentication is separate from AI authority.

Holiday uses Amazon Cognito user pools for user authentication. A stable Cognito identity maps to the user and permissions configured inside that customer’s Holiday environment.

Amazon Cognito supports software-token MFA and federation with SAML and OpenID Connect identity providers. MFA enforcement and enterprise SSO federation are deployment-specific options and are confirmed during implementation; they are not represented here as enabled for every customer by default.

Authentication establishes who the person is. Holiday still checks that person’s permissions and the AI identity’s authority before a tool call can proceed.

NIST SP 800-207 principle mapping

How Holiday applies zero-trust principles.

This is an architectural mapping, not a NIST certification or a claim that Holiday implements every control in a customer’s wider enterprise environment.

Per-request decisions: Authorization is evaluated for each tool call rather than being assumed from an earlier model or user session.
Least privilege: People, digital employees and specialists receive only the systems, records and actions assigned to their roles.
Identity before location: Access depends on identifiable users and AI roles, not trust based only on network location or asset ownership.
Continuous evidence: Activity records support review, governance reporting and changes to access when business requirements change.

Hosting and data residency

Choose where the Holiday environment is hosted.

Customer environment

Each customer environment is hosted individually on AWS in a supported region selected during implementation. Business data is not held alongside another customer’s data.

AI processing

AI processing locations depend on the model providers the customer selects. Where regional processing is required, the selected provider and model must support it.

Assurance status

Clear about what is complete and in progress.

Holiday is undergoing ISO/IEC 27001 certification, with its audit scheduled for late 2026. Holiday is not describing itself as certified before that process is complete.

Current sub-processors include AWS for hosting, infrastructure and Cognito authentication; Cloudflare for web delivery, edge services and secure network tunnels; and the AI model providers selected by each customer.

Security documentation and deployment-specific control details are available during evaluation.

Security review topics

The details buyers need to assess.

Deployment-specific evidence and control details are available during evaluation. The following summary states the current public position without implying controls that have not been agreed for a customer environment.

Encryption: Holiday’s AWS deployment uses encrypted database and attachment storage at rest, with encrypted connections including hostname-verified TLS for database traffic.
Audit retention and export: The standard customer export includes audit logs at no charge. Active retention periods and any SIEM delivery requirements are agreed for the customer environment during evaluation.
Penetration testing: Current testing coverage, cadence, remediation status and any available reports can be reviewed under appropriate confidentiality during evaluation.
Incident response: Suspected data incidents are investigated and assessed. Customer notification follows applicable law and agreed contractual requirements; process details are available during evaluation.
Leaving Holiday: Unless another arrangement is agreed, customer data remains available for export for 30 days after termination. Holiday may then delete the production environment and customer data, while residual backups expire through ordinary rotation.
Security documentation: Architecture, sub-processor, identity and deployment-specific control details are available during evaluation and can be handled under appropriate confidentiality.

Review the architecture

Bring your security questions.

We will walk through identity, permissions, hosting, model providers and the controls that apply to your proposed environment.

Contact Holiday