---
title: "What a security review with Etheon looks like"
updated: "2026-11-17"
url: "https://www.etheon.com/company/news/what-a-security-review-with-etheon-looks-like"
authors: "Etheon"
published: "2026-11-17"
type: "news"
---

# What a security review with Etheon looks like

What your security team sends, what we answer and the evidence at each step: the questionnaire, our security brief, the SOC 2 Type II report under NDA.

A security review is how your security team checks a supplier before any of your data reaches it: a questionnaire, the supplier's answers and the documents behind them. With Etheon, your team sends its questionnaire, we answer it, and we share the SOC 2 Type II report under NDA. We hold [SOC 2 Type II, ISO 27001 and CSA STAR](https://www.etheon.com/company/trust#security).

## Where does the review sit in the project?

Second, after the first call and before legal, procurement and a pilot. Each step has its evidence:

| Step | First call | Security review | Legal and procurement | Pilot | Rollout |
| --- | --- | --- | --- | --- | --- |
| Your team | The problem's owner and one engineer join. | Your security team sends its questionnaire. | Legal and procurement review the terms. | A small group of real users. | Your teams take over, or we stay on. |
| Etheon | Questions, then a written use-case brief. | Our security brief, and your questionnaire answered. | Our DPA, subprocessors and services agreement. | A pilot with success criteria agreed first. | A runbook, training and a handover. |
| Evidence | Use-case brief | Security brief, SOC 2 Type II report, under NDA | DPA, subprocessors | Pilot plan | Runbook |

## Do you answer our questionnaire, or send your own?

We answer yours, in the format your security team uses. The review runs in five steps:

1. Scope the review: which systems, data and people the project will touch.
2. Answer in writing: every question of your questionnaire, each with its evidence.
3. Share the evidence: the security brief, and the SOC 2 Type II report under NDA.
4. Meet your reviewers: a call to walk through the answers and anything still open.
5. Close the findings: each open point answered, or agreed as a term of the contract.

Your security team takes part, with whoever owns the data the project touches. Legal and procurement join at the next step.

## What evidence can our reviewers read?

| Document | Kind | How to get it |
| --- | --- | --- |
| SOC 2 Type II report | Report | Under NDA, on request |
| ISO 27001 certificate | Certificate | Public |
| CSA STAR | Registry entry | Public |
| Security brief | Brief | On request |
| Pen-test summary | Summary | Under NDA, on request |
| Data processing agreement | Agreement | [Read the Data processing agreement](https://www.etheon.com/legal/dpa) |
| Subprocessors | List | [Read the Subprocessors](https://www.etheon.com/legal/subprocessors) |
| Architecture overview | Overview | Per project, on request |

## What is in the security brief?

How your data, code and models are protected, who can reach them and how each access is logged, and the certifications we hold. We keep the brief current as our controls change. It goes to the people who review us for your company; where it holds confidential detail, it comes under an NDA.

## What happens to our data?

- Stored in the region you choose. Your data and its backups stay there.
- Reached only by the roles you approve. Every access is logged and can be reviewed.
- Encrypted in transit and at rest, with your own keys if you want them.
- Kept as long as you set. Retention is configured per workspace.
- Exported or deleted when you ask. Deletions reach the backups too.

We never train models on your data without your opt-in. Your data stays isolated from other clients.

## Does it work with our identity provider?

If your provider speaks SAML or OIDC, yes. Single sign-on runs through SAML or OIDC, users and roles are provisioned by SCIM, your groups map to the roles the software allows, least privilege first, and every sign-in and role change is in the audit log your security team reads.

## Does the pilot use our real data?

It uses the data your security review allows, in your environment. Where real data is not allowed, we agree a safe sample first. A pilot puts the software in front of a small group of real users for a set time, measured against criteria agreed before it starts. On its report you decide: roll out, change course or stop.

## What happens after the pilot?

A rollout follows with a runbook, training and a handover. For the first quarter after the pilot, governance runs on a fixed rhythm: a delivery review weekly, steering monthly, a security review and the roadmap quarterly.

To start, ask for the security brief with your questionnaire, from our [Enterprises page](https://www.etheon.com/solutions/enterprises#evidence). How we protect data on every project is on [Trust](https://www.etheon.com/company/trust#security). We reply within one business day.