---
title: "Enterprises"
updated: "2026-11-16"
url: "https://www.etheon.com/solutions/enterprises"
---

# Enterprise AI software development

AI software in large companies. We build AI into the systems you run, through your security review and your procurement. We hold SOC 2 Type II, ISO 27001 and CSA STAR.

|  | 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 |

[Request security brief](https://www.etheon.com/solutions/enterprises?start=1&service=security-review)

### A security review with Etheon. What your team sends, what we answer and the evidence at each step.

#### What it is

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.

#### What we do

- We answer your questionnaire.
- We send our security brief.
- We share the SOC 2 Type II report under NDA.

#### How we do it

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.

#### Questions

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

We answer yours, in the format your security team uses.

**Can we see the SOC 2 Type II report?**

Yes, under NDA. Ask for it with your questionnaire.

**Who on our side takes part?**

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

#### What you get

- The security brief.
- Your questionnaire, answered.
- The SOC 2 Type II report, under NDA.
- The DPA.
- The subprocessors list.

#### Related

- [The security brief](https://www.etheon.com/solutions/enterprises?detail=security-brief#security-brief)
- [Compliance](https://www.etheon.com/company/trust#compliance)
- [Data processing agreement](https://www.etheon.com/legal/dpa)

### A pilot with real users. Success criteria agreed first, then a decision on the rollout.

#### What it is

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, so the decision to roll out rests on evidence.

#### What we do

- A pilot with a small group of real users.
- Success criteria agreed before it starts.

#### How we do it

1. Pick the group: A small group of real users, and the work they will do with it.
2. Agree the criteria: What success looks like, and how it is measured, before the pilot starts.
3. Run it: In your environment, inside the limits your security review set.
4. Measure: The criteria checked against real use, with your team.
5. Decide: Roll out, change course or stop, on the report.

#### Questions

**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.

**What happens after the pilot?**

You decide on the report: roll out, change course or stop. A rollout follows with a runbook, training and a handover.

**Who joins from our side?**

The problem's owner, the users in the group, and an engineer who knows your systems.

#### What you get

- A pilot plan.
- The agreed criteria.
- A report on them.

#### Related

- [How we work: launch](https://www.etheon.com/company/how-we-work#launch)
- [A security review with Etheon](https://www.etheon.com/solutions/enterprises?detail=security-review#security-review)

## The evidence pack. What your security reviewers can read, and how to get each document.

- SOC 2 Type II report (Report). Under NDA. [Request](https://www.etheon.com/solutions/enterprises?start=1&service=security-review&tab=soc-2-report)
- ISO 27001 certificate (Certificate). Public, link pending.
- CSA STAR (Registry entry). Public, link pending.
- Security brief (Brief). On request. [Request](https://www.etheon.com/solutions/enterprises?start=1&service=security-review&tab=security-brief)
- Pen-test summary (Summary). Under NDA. [Request](https://www.etheon.com/solutions/enterprises?start=1&service=security-review&tab=pen-test-summary)
- Data processing agreement (Agreement). Public. [Read](https://www.etheon.com/legal/dpa)
- Subprocessors (List). Public. [Read](https://www.etheon.com/legal/subprocessors)
- Architecture overview (Overview). Per project. [Request](https://www.etheon.com/solutions/enterprises?start=1&service=security-review&tab=architecture-overview)

[Trust](https://www.etheon.com/company/trust#compliance)

### The security brief. How we protect your data, code and models, in one document your reviewers can read.

#### What it is

A security brief is the document a supplier gives a security team before a review: how data, code and models are protected, who can reach them and what is certified.

#### What we do

- We describe how your data, code and models are protected.
- We name who can reach them, and how each access is logged.
- We list the certifications we hold.
- We keep the brief current as our controls change.

#### Questions

**Who receives the brief, and under what terms?**

The people who review us for your company. Where the brief holds confidential detail, it comes under an NDA.

#### What you get

- The brief, on request.

#### Related

- [Security](https://www.etheon.com/company/trust#security)
- [Compliance](https://www.etheon.com/company/trust#compliance)

## Fits your estate. The systems your AI software must work with.

Your AI software

- Identity: Single sign-on with SAML or OIDC; users and roles provisioned by SCIM.
- Logging and SIEM: Audit events sent to the tools your security team watches.
- Data platforms: Your warehouse as the source, with access by role.
- ERP and CRM: Read and write through their own APIs, within limits you set.
- Service desk: Hand-offs to a person as tickets, with the context attached.
- Cloud accounts: Deployed in your own account and region.

### Identity. Single sign-on with SAML or OIDC; users and roles provisioned by SCIM.

#### What it is

Identity is how your AI software knows who is signed in and what each person may see and do, using the accounts and roles your company already manages.

#### What we do

- Single sign-on with SAML or OIDC.
- Users and roles provisioned by SCIM.
- Least-privilege roles.
- Audit logs.

#### How we do it

1. Connect your identity provider: Single sign-on with SAML or OIDC, set up with your IT team.
2. Map the roles: Your groups to the roles the software allows, least privilege first.
3. Provision by SCIM: Users and roles created and removed from your directory.
4. Log every access: Sign-ins and role changes in the audit log your security team reads.

#### Questions

**Does it work with our identity provider?**

If your provider speaks SAML or OIDC, yes. Most company identity providers do.

**Who decides what each person can see?**

You do. Your groups map to the roles the software allows, and a change in your directory reaches it through SCIM.

**Can our security team see who signed in?**

Yes. Every sign-in and role change is in the audit log.

#### Stack and tools

- Identity providers
- Directory provisioning
- Role-based access control
- Audit logging

#### Related

- [Access](https://www.etheon.com/company/trust#compliance-access)
- [Cloud security](https://www.etheon.com/services/cloud?detail=security#security)

## Pilot to program. A quarter of governance after the pilot.

- Delivery review: Weekly
- Steering: Monthly
- Security review: Quarterly
- Roadmap: Quarterly

- [Trust](https://www.etheon.com/company/trust): Security, privacy and transparency
- [Work](https://www.etheon.com/work): What we built for our clients