Skip to content

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.

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.

The path to a signed project
Your teamThe 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.
EtheonQuestions, 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
  1. Your team
    The problem's owner and one engineer join.
    Etheon
    Questions, then a written use-case brief.
    Evidence
    • Use-case brief
  2. Your team
    Your security team sends its questionnaire.
    Etheon
    Our security brief, and your questionnaire answered.
    Evidence
    • Security brief
    • SOC 2 Type II report, under NDA
    Read more: Security review
  3. Your team
    Legal and procurement review the terms.
    Etheon
    Our DPA, subprocessors and services agreement.
    Evidence
    • DPA
    • Subprocessors
  4. Your team
    A small group of real users.
    Etheon
    A pilot with success criteria agreed first.
    Evidence
    • Pilot plan
  5. Your team
    Your teams take over, or we stay on.
    Etheon
    A runbook, training and a handover.
    Evidence
    • Runbook

Enterprise AI software development · The path to a signed project · 1 of 2

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 reviewWhich systems, data and people the project will touch.
  2. Answer in writingEvery question of your questionnaire, each with its evidence.
  3. Share the evidenceThe security brief, and the SOC 2 Type II report under NDA.
  4. Meet your reviewersA call to walk through the answers and anything still open.
  5. Close the findingsEach 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

Get started with Etheon Tell us your use case and timeline. We reply within one business day.

Enterprise AI software development · The path to a signed project · 2 of 2

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 groupA small group of real users, and the work they will do with it.
  2. Agree the criteriaWhat success looks like, and how it is measured, before the pilot starts.
  3. Run itIn your environment, inside the limits your security review set.
  4. MeasureThe criteria checked against real use, with your team.
  5. DecideRoll 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

Get started with Etheon Tell us your use case and timeline. We reply within one business day.

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

Enterprise AI software development · The evidence pack

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

Get started with Etheon Tell us your use case and timeline. We reply within one business day.

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

Enterprise AI software development · Fits your estate

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 providerSingle sign-on with SAML or OIDC, set up with your IT team.
  2. Map the rolesYour groups to the roles the software allows, least privilege first.
  3. Provision by SCIMUsers and roles created and removed from your directory.
  4. Log every accessSign-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

Get started with Etheon Tell us your use case and timeline. We reply within one business day.

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

A quarter of governance
w1w2w3w4w5w6w7w8w9w10w11w12
Delivery review WeeklyYesYesYesYesYesYesYesYesYesYesYesYes
Steering MonthlyYesYesYes
Security review QuarterlyYes
Roadmap QuarterlyYes

Get started with Etheon

Tell us your use case and timeline. We reply within one business day.

Trust

Security, privacy and transparency

Trust

Work

What we built for our clients

View all work