Trust Center

The controls behind the platform.

Holistic AI helps enterprises govern their AI. We hold ourselves to the standard of evidence we ask of them: our security programme is independently audited, and the underlying reports, certificates and policies are available to customers and prospects under a mutual NDA.

92/93

ISO 27001 Annex A controls in scope

4/5

SOC 2 Trust Services Criteria examined

0

Nonconformities at our 2026 certification audit

39

Documents available under mutual NDA

ISO/IEC 27001:2022

SOC 2 Type 2

UK GDPR

ISO/IEC 42001 — audit scheduled

Here you can review the frameworks we are certified against, the controls we operate, and the documents we hold. The documents themselves are released only after a mutual NDA is in place — use request access and tell us which ones you need.

Annex A coverage

92 of 93 in scope

A.5Organisational controls

37 of 37 controls in scope

A.6People controls

8 of 8 controls in scope

A.7Physical controls

14 of 14 controls in scope

A.8Technological controls

33 of 34 controls in scope

1 excluded as not applicable

Controls in scope per ISO/IEC 27001:2022 Annex A theme, as set out in our Statement of Applicability. A.8.30 Outsourced development is the single exclusion — we do not outsource development. Certification runs on a three-year cycle with annual surveillance audits in between; our certification audit closed with no nonconformities and no opportunities for improvement raised.

What each framework covers

Control domainISO 270011SOC 22
Organisational securityCoveredCovered
People securityCoveredCovered
Infrastructure securityCoveredCovered
Product securityCoveredCovered
Access controlCoveredCovered
Data and privacyCoveredCovered
Incident response and continuityCoveredCovered
  1. ISO/IEC 27001 coverage reflects the Annex A controls listed in our Statement of Applicability. A.8.30 Outsourced development is excluded as not applicable.
  2. SOC 2 coverage reflects the Security, Availability, Confidentiality and Privacy criteria. Processing Integrity was not among the criteria examined.

Compliance

ISO/IEC 27001:2022

Certified

Information security management system supporting the development and deployment of the Holistic AI platform.

SOC 2 Type 2

Report available

Design and operating effectiveness across Security, Availability, Confidentiality and Privacy.

UK GDPR & Data Protection Act 2018

Compliant

Holistic AI Limited is the data controller where personal data is provided directly through our website — the Information Commissioner’s Office (ICO) is our supervisory authority. Under a customer MSA we act as data processor. Full wording

ISO/IEC 42001

In progress

AI management system. We do not hold this certification today; work towards it is under way and we will update this page once it is certified.

Subprocessors

View all
AWS

Amazon Web Services · Cloud infrastructure and data hosting

UK · US

GCP

Google Cloud Platform · Cloud infrastructure (US customers)

US

WO

WorkOS · Authentication and user management

US

SG

Twilio SendGrid · Transactional email

US

Transfers outside the UK and EEA are covered by the transfer safeguards in our standard Data Processing Agreement.

Frequently asked

View all
How do I get access to your audit reports?

Request access and tell us which documents you need. We send our standard mutual NDA for e-signature, or use the one already in place with your company, and grant access once it is signed.

Do you train models on customer data?

No. We do not use customer data to train models. We do not build or train models of our own — the platform assesses and governs the AI systems our customers build or buy, and does not learn from the data it handles.

I found a security bug. How do I report it?

Email we@holisticai.com with enough detail for us to reproduce it. We acknowledge every report and keep you updated until it is resolved. Please do not access data that is not yours or degrade the service for others while testing.

Security programme

Controls we operate

Certification is a point in time. These are the practices that keep the controls working in between audits — all of them examined during our ISO/IEC 27001:2022 certification audit. Each control is annotated with the Annex A control or management-system clause it implements, so a reviewer can trace a statement back to the standard.

Organisational security4 controls

Information Security CommitteeA.5.2, A.5.4

Senior management, engineering and operations, legal and information security review the ISMS at least annually.

Risk managementClause 6.1.2, 6.1.3

Risks are identified, assessed and treated under a documented policy, with a register maintained continuously.

Internal auditClause 9.2

An internal ISMS audit runs at least annually; findings and corrective actions are reviewed by management.

Policy managementA.5.1, A.5.37

All policies are version-controlled, reviewed annually and acknowledged by staff at onboarding.

People security4 controls

Background screeningA.6.1

New joiners are screened before access is granted.

Confidentiality agreementsA.6.2, A.6.6

All personnel are bound by confidentiality obligations and a code of business conduct.

Security awareness trainingA.6.3

Delivered at onboarding and refreshed on an ongoing basis.

Joiner, mover, leaverA.5.18, A.6.5

Access is provisioned and revoked through a documented process tied to employment status.

Infrastructure security6 controls

Cloud hostingA.5.23

Infrastructure runs on Amazon Web Services, in Europe (London) by default. US customers are hosted in US East (Ohio) or, where required, on Google Cloud Platform.

EncryptionA.8.24

Encrypted in transit (TLS 1.2+) and at rest (AES-256 via AWS KMS), with dedicated keys for credential storage and key rotation at least every 12 months, per our Encryption Policy.

Network securityA.8.20–A.8.23

Network segregation, secure network services and web filtering are in place.

Logging and monitoringA.8.15–A.8.17

System activity is logged and monitored, with clock synchronisation across systems.

Vulnerability managementA.8.8

Technical vulnerabilities are identified, tracked and remediated on a defined schedule.

Backup and redundancyA.8.13, A.8.14, A.5.30

Documented backup, recovery and disaster recovery procedures with redundant infrastructure, to a recovery objective of 72 hours. Data is replicated across multiple regions.

Product security6 controls

Secure development lifecycleA.8.25, A.8.28

Development follows a documented SDLC policy with secure coding standards and code review.

Environment separationA.8.31

Development, test and production environments are kept separate.

Security testingA.8.29

Security testing is performed during development and acceptance.

Penetration testingA.8.8, A.8.29

Independent penetration testing is performed annually. The executive summary is available under NDA.

Change managementA.8.32

Changes to production are reviewed, approved and tracked.

Access to source codeA.8.4

Repository access is restricted and reviewed.

Access control4 controls

Least privilegeA.5.15, A.8.3

Access is granted on a need-to-know basis and reviewed periodically.

Privileged accessA.8.2, A.8.18

Administrative rights are restricted, logged and separately approved.

Secure authenticationA.5.17, A.8.5

Platform sign-in, single sign-on and user directory management run through WorkOS. Access to systems holding customer data is restricted and reviewed under our Access Control Procedure.

Customer data accessA.5.15, A.5.18

Limited to a small number of authorised personnel under confidentiality obligations.

Data and privacy4 controls

Data residencyA.5.23, A.5.34

Customer data is hosted in the UK by default. US customers are hosted in the United States. Transfers are covered by the safeguards in our Data Processing Agreement.

Retention and deletionA.5.33, A.8.10

Data is retained only as long as necessary for the purpose it was collected for, or according to the timeline set out in the MSA. On termination or on request it is permanently deleted from storage, databases and backups under our secure deletion protocol.

Data classificationA.5.12, A.5.13

Information is classified, labelled and handled according to sensitivity.

Special category dataA.5.34

Not collected.

Incident response and continuity4 controls

Incident managementA.5.24–A.5.27

Documented policy and procedure covering detection, assessment, response and post-incident learning.

Customer notificationA.5.26, A.6.8

Confirmed incidents affecting customer data are notified within 72 hours, or within the timeline agreed in the MSA, under our Incident Management Procedure and Personal Data Breach Notification Policy.

Business continuityA.5.29, A.5.30

BCDR plans are documented and maintained for the platform.

Vendor riskA.5.19, A.5.20, A.5.22

Suppliers are assessed before onboarding and reviewed under our Vendor Management Procedure.

By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.